FIX Integrated Control Center is an application providing out-of-the-box monitoring and administration capabilities for FIX Edge and any applications embedding FIX Antenna C++, FIX Antenna Java, FIX Antenna .Net. FIXICC is a Java-based standalone application which run on any platform.
Hardware
CPU | Minimum 1.0 GHz | Recommended 2.6 GHz |
Memory Disk Space | 512 Mb 50 Mb | 2 Gb 200 Mb |
Software
FIXICC and FIXICC Agent are standalone applications, which can be installed along with FIXEdge or separately.For more details on how to install these applications without FIXEdge refer to 'Manual Installation' section
FIXICC installation
Installation from zip archive
Unzip fixicc-x.y.z.zip file into any folder on machine.
(Skip this step if you install FIXICC v. 2.9.16 or higher)
Place license file (fixaj2-license) into FIXICC root directory (for examle, C:\Users\User\FIXICC).
Start FIXICC via 'fixicc.exe' file from FIXICC 'bin' directory.
Installation from the Setup Wizard
FIXICC can also be installed using Setup Wizard:
FIXICC Agent installation
Installation from zip archive
Installation from the Setup Wizard
FIXICC Agent can also be installed using Setup Wizard:
If FIX Edge, FIXICC and FIXICC agent were installed together, FIX Edge parameters are already pre-configured (for more details on accomplished configuration refer to 3.1). If FIXICC and FIXICC agent are installed separately from FIX Edge or any other server, the following parameters should be configured manually.
Add new Admin session with the following parameters to 'engine.properties' of the monitored application (FIXEdge or generic server):
# Flag to enable or disable monitoring. Valid values are true and false Monitoring.Enable = true # The list of administrative sessions separated by comma. Monitoring.AdminSessionNames = AdminClient # TargetCompId value of administrative session # The parameter is required Monitoring.AdminSession.AdminClient.TargetCompId = AdminClient # The FIX protocol version of administrative session # If the protocol version from logon message (MsgType=A) is different, connection is rejected. # Allowed values: FIX40, FIX41, FIX42, FIX43, FIX44, FIX50, FIXT11 # The parameter is required Monitoring.AdminSession.AdminClient.Version = FIX44 # The expected Username value of administrative session # If the field value from logon message (MsgType=A) is different, connection is rejected. Monitoring.AdminSession.AdminClient.Username = user # The Expected Password value of administrative session # If the field value from logon message (MsgType=A) is different, connection is rejected. Monitoring.AdminSession.AdminClient.Password = pass # Intraday logout tolerance mode of administrative session Monitoring.AdminSession.AdminClient.IntradayLogoutToleranceMode = true # Force SeqNum reset mode of administrative session Monitoring.AdminSession.AdminClient.ForceSeqNumResetMode = true # Ignoring of 'SeqNum too low' at incoming Logon message of administrative session Monitoring.AdminSession.AdminClient.IgnoreSeqNumTooLowAtLogon = true |
Note: Admin session parameters should be unique for each agent - server administration connection.
In order to adjust FIXICC Agent configuration, refer to ('conf') folder.
Refer to 'agent.properties' file and verify correctness of specified below parameters:
# Server type which server this agent. # Supported 3 different server types: # FIXEdge - FIXEdge server. # FIXAC - FIX Antenna C++/.Net # FIXAJ - FIX Antenna Java 2 TypeServer = FIXEdge # Agent listen port # This parameter specifies TCP/IP port on which FIXICC Agent engine listens for connections from FIXICC #GUI Clients. # Valid values: available TCP/IP port number AgentServerPort = 8005 # Server home path. # This parameter define path to directory where FIXEdge is installed. All relative paths will be linked with it. # NOTE: working only with TypeServer=FIXEdge ServerHome = D:\\Users\\mquser\\Documents\\B2BITS\\FIXEdge # Start server script # NOTE: working only with TypeServer=FIXEdge StartFile = bin\\FixEdge1.service.run.bat # Stop server script # NOTE: working only with TypeServer=FIXEdge StopFile = bin\\FixEdge1.service.stop.bat # FIX Antenna configuration file # This parameter define path to related FIX Antenna configuration file. EngineProperty = FixEdge1\\conf\\engine.properties # FIXEdge configuration file # This parameter define path to related FIX Antenna configuration file. # NOTE: working only with TypeServer=FIXEdge FIXEdgeFileSettings = FixEdge1\\conf\\FIXEdge.properties # FIXEdge Business Layer config file # This parameter defile path lo BL_Config.xml # NOTE: working only with TypeServer=FIXEdge FIXEdgeBL_FileConfig = FixEdge1\\conf\\BL_Config.xml # Url with sharable data log. This path is used by FIXEye for log browsing. # It is recommended to specify the full path here LogUrl = D:\\Users\\mquser\\Documents\\B2BITS\\FIXEdge\\FixEdge1\\log\\ #Remote host name or IP address of the engine which will be used by Agent to connect. EngineConnectionDetails.RemoteHost = 127.0.0.1 # set ID that will be used as SenderCompID in administration session between FIXICC Agent and FIXEdge # (tag 49). This ID should be equal to Monitoring.AdminSession.AdminClient.TargetCompId from #engine.properties of FIXEdge. EngineConnectionDetails.AdminSession.SenderCompID = AdminClient # set ID that will be used as TargetCompID in administration session between FIXICC Agent and FIXEdge # (tag 56). NOTE, for FIXEdge, FIXAntenna C++ and FIXAntenna .Net this ID should be always set to #"FIXADMIN", for FIXAntenna Java this is a configurable parameter. EngineConnectionDetails.AdminSession.TargetCompID = FIXADMIN # set username that will be used in Logon message of administration session between FIXICC Agent and #FIXEdge (tag 553). This ID should be equal to Monitoring.AdminSession.AdminClient.Username from #engine.properties of FIXEdge. EngineConnectionDetails.AdminSession.Username = user # set password that will be used in Logon message of administration session between FIXICC Agent and #FIXEdge (tag 554). This ID should be equal to Monitoring.AdminSession.AdminClient.Password from #engine.properties of FIXEdge. EngineConnectionDetails.AdminSession.Password = pass |
Verify correctness administrative session parameters in 'fixengine.properties'.
# Name of the custom package. This property is using for the extending the count of admin-commands. autostart.acceptor.targetIds= # Storage directory, could be either absolute path (like /tmp/logs or c:\fixengine\logs) storageDirectory=logs # provide fast in-memory storage, but during session restart all messages will be lost storageFactory=com.epam.fixengine.storage.InMemoryStorageFactory #Sets queue mode. This property makes sense only if FilesystemStorageFactory is set. #Set to "false" for persistent queue (slower but no messages will be lost), "true" for in-memory queue (faster #but less safe, some messages may be lost). inMemoryQueue=true # Maximum message size supported by this FIX engine instance. The parameter must be integer and not #negative. Should be set to a greater than expected maximum message by approximately 1-5%. maxMessageSize=1024000 # Toggle on/off the validation of incoming messages according to the base of custom dictionaries. validation=false # This parameter allow to automatically resolve sequence gap problem (for example, when there is every #day #sequence reset). Supported values: #Recommended value - Always - session will send logon with 34= 1 and 141=Y every times (during #connection and reconnection). #OneTime - session will send logon with 34= 1 and 141=Y only one time (during connection). #Never - this means that user can sets the 34= 1 and 141=Y from session parameters by hand.forceSeqNumReset=Always |
Number of agent folder copies should be equal to number of FIXICC Agent instances you are going to use on this machine. Multiple FIXICC Agent instances can be used on single machine, for example to monitor several FIXEdge instances installed on this machine.
In such case, change the following properties in 'wrapper.conf' file: wrapper.console.title, wrapper.ntservice.name and wrapper.ntservice.displayname (Note, their values should be unique across all FIXICC Agent instances).
I.e., 3 FIXICC Agent instances residing on the same machine can be called: "FIXICC - Agent Server #1", "FIXICC - Agent Server #2" and "FIXICC - Agent Server #3".
Where instance #1 will have the following properties in 'wrapper.conf' file:
wrapper.console.title=FIXICC - Agent Server #1 wrapper.ntservice.name=FIXICC - Agent Server #1 wrapper.ntservice.displayname=FIXICC - Agent Server #1 |
Important: "fixicc-agent.bat install" command can be run only after these changes are made and absence of duplicated service names is verified.
Please note: 'agent.properties' should also be changed according to new servers parameters.
In order to run FIXICC installed as a standalone application use executable file (fixicc.exe) located in FIXICC 'bin' directory. Servers configured during FIX Edge installation will be displayed under 'Servers' on the left hand side of FIXICC GUI.
If FIXEdge, FIXICC and FIXICC agent were installed all together, FIXICC is already pre-configured to monitor relevant FIXEdge (this was accomplished during installation process, see 3.1 for more details).
In this case, installed server will be displayed under 'Servers' on the left hand side of FIXICC GUI.
If FIXICC and FIXICC Agent were installed separately from FIX Edge or any other server, FIXICC should be configured manually. See below for more details.
Please note:
FIXICC offers two methods of connecting to the server: direct access and access via FIXICC agent. Differences in server configuration for both methods will be described in this section.
See below administration session parameters used in FIX Antenna Java (see 'fixengine.properties' file):
autostart.acceptor.targetIds=admin
autostart.acceptor.admin.login=admin
autostart.acceptor.admin.password=admin
autostart.acceptor.admin.ip=*
autostart.acceptor.admin.fixServerListener=com.epam.admintool.AdminTool
Select required server from the 'Servers' list and depending on preferred connection type:
• click “Connect” button or go to “Server → Connect” context menu option to establish a direct connection to the server.
or
• connect via FIXICC agent. The algorithm remains the same, but FIXICC Agent should be started before clicking the “Connect” button.
You need specify admin session password:
1) Monitoring.AdminSession.AdminClient.Password (for direct access mode);
2) EngineConnectionDetails.AdminSession.Password (for FIXICC + FIXICC Agent mode).
Please note, the following operations are supported only via the FIXICC Agent:
• Managing engine configuration
• Managing session
• Administrating server
Once you have successfully connected to the server, it can be started by clicking “Start Server” button or navigating to “Server → Start Server” submenu.
You can also do right mouse click on required server and select “Start Server” from popped up context menu.
All servers added to FIXICC are listed on the right side of the window in a table view.
The following health statuses are indicated for each monitored server in the 'Status' column and next to the server in the 'Servers' list:
Double click on a server from the 'Servers' list expands list of pre-configured sessions and add-on components (for FIXEdge only; add-on components include Transport Adaptors, Handlers, etc).
You can edit details of any added server using right‐click menu for relevant server and selecting “Edit Server”.
All changes will be applied only after you reconnect to modified server. |
FIXICC allows direct (right from the application) configuration of server you are connected to via FIXICC Agent. The following settings can be accessed:
Each set of configuration parameters can be loaded for selected server via corresponding 'Server' submenu option or via right-mouse-click menu.
Or use the following toolbar buttons:
The file will be opened in the right panel as a plain editable text document.
When you finish editing the configuration click the “Deploy Server Configuration” button or select the corresponding option from the 'Server' submenu.
Relevant configuration file will be overwritten and the previous version backed‐up as engine_YYYYMMDD‐HHmmss.properties where YYYYMMDD‐HHmmss is a time stamp of file modification.
In addition to the automatic back‐up, it is highly recommend to update revision number to avoid possible difficulties in tracking the change history.
Important: all changes will be made for selected Server.
In order to stop the server, select it from 'Servers' list and and click "Stop Server” button or go to “Server → Stop Server” context menu.
You can also do right mouse click the required server and select “Stop Server” from the context menu.
After 'Stop server' command was given to the server, it will gracefully close all open FIX session, stop all running Transport Adaptor(s) and Handler(s), disconnect from any middle-ware (the last two are FIXEdge specific) and then stop the process. |
In order to disconnect from the server, select it from 'Servers' list and and click "Disconnect” button or go to “Server → Disconnect” context menu.
You can also do right mouse click the required server and select “Disconnect” from the context menu.
Disconnection from the server will not affect its operation. If server was up and running before disconnection attempt was performed, it will continue running. If it was stopped, will remain stopped. |
Select the required server from the list and click the “Remove Server” button or go to “Server → Remove Server” to remove it from the list.
You can also right click the required server and select “Remove Server” from the context menu.
You should disconnect from the server before removing it from the list of servers. |
Server removal will not affect its operation. If server was up and running before it was removed from the list of monitored servers, it will continue running. If it was stopped, will remain stopped. |
You can import and/or export server configuration from/to a file. This can be handy when backing‐up your configuration or sharing it with someone else. You can either go to “File” submenu or do right mouse click on a selected server to select the required option.
You can clean the server’s logs (the files are located in folder log of server) if FIXICC is connected to server via FIXICC Agent. Select the required server from the list and click the “Clean Logs” button or go to “Server → Clean Logs”.
Once server is added, you will be able to view, configure and manage FIX sessions. This section describes what can be done to a FIX session.
All possible actions are available in the 'Session' submenu and 'Session Administration' toolbar.
Note, “View → Toolbars” context menu item can be used to hide/unhide this toolbar.
In order to add new FIX session, select necessary server and click “Add Session” button or go to “Session → Add session to server” context menu item.
The same can also be achieved via right mouse click on selected server and referring to 'Add Session to the Server' menu item.
By default, only mandatory fields should be specified:
Any session configuration can be saved as default by clicking “Save as default” button to create new session with pre-defined custom parameters.
New sessions can be added so:
|
To establish several sessions with the same SenderCompId and TargetCompId, both Initiator and Acceptor should create several session objects which differ from each other by SessionQualifier property. SessionQualifier property on the Initiator side must be the same as SessionQualifier property of the corresponding session on acceptor side. When Initiator connects to Acceptor, it sends SessionQualifier along with SenderCompId and TargetCompId in logon message. The SessionQualifier tag in the Logon message is optional and can be configured in the engine.properties file. When Acceptor receives logon message with the SessionQualifier it searches for a registered session with SessionId corresponding to received TargetCompId, SenderCompId, and SessionQualifier. If the session is found it is associated with the incoming connection, otherwise, the connection is rejected.
If the user creates a session by passing only SenderCompId and TargetCompId parameters (without SessionQualifier), the SessionId structure is created and stored internally with empty qualifier_ property. If Acceptor registers a session without session qualifier it won't accept any incoming connection with session qualifier defined in logon message. And vice versa, if Acceptor has registered a session or several sessions with qualifiers, it won't accept connections from Initiators without SessionQualifier.
Also SessionQualifierTag is available for defining a tag containing SessionQualifier name (LogonMessageSessionQualifierTag parameter in FIXEdge.properties).
Refer to: How to use SessionQualifier
The following optional parameters can be set:
This tab allows you to manage sequence numbers by doing the following:
This tab allows specifying properties for user authentication at logon as well as data encryption settings.
Allows specifying backup connection to assure the uninterrupted information exchange. Check the corresponding box and specify the following:
Note: if the primary connection is a SSL connection, then backup connection will use the same SSL parameters (certificate, protocols) as the primary connection (specified in the SSL tab). |
Custom FIX Logon (MsgType = 'A') message can be specified in this tab.
Old-style Scheduler tab
New-style Scheduler tab was introduced in FIXICC 2.10.1 with FIXEdge 6.0. Since FIXEdge 6.0 if you want to keep Old-style Scheduler tab in FIXICC, you should not specify FIXICC.Schedules property equal to true in the FIXEdge.properties configuration file. |
This tab allows specifying scheduled tasks for FIX sessions (functionality is available for FIX Edge only)
It is possible to switch between custom and default scheduler. In order to do so, switch between "Session starts/stops with the server (according to default scheduler)" and "Session starts/stops according to scheduler”.
For custom scheduler you can configure:
New-style Scheduler tab
New-style Scheduler tab was introduced in FIXICC 2.10.1 with FIXEdge 6.0. Since FIXEdge 6.0 to activate New-style Scheduler tab functionality in FIXICC you should specify FIXICC.Schedules property equal to true in the FIXEdge.properties configuration file. |
This tab allows to define the schedule for the FIX session in a new, more flexible format (functionality is available for FIXEdge only).
All the date/time properties of schedule are defined in CRON format. CRON expressions have the following syntax:
Support of the CRON expressions is limited by quartz. In particular, specifying both a day-of-week and a day-of-month values is prohibited (you'll need to use the '*' character in one of these fields). The only note here is that '*' character is used instead of '?' character in compare with quartz. |
It is possible to switch between existing schedules, define custom session schedule or choose default settings:
When choose <Inherit from default>, no schedule is specified and default properties will be applied. If default properties are not specified in FIXEdge.properties, FIX Session will be started/stoped with the server.
When choose <Custom Settings>, you can configure Start/Connect/Disconnect/Terminate time. All the properties from this section can be defined in both CRON format and standard HH:MM format.
Start time, connect time, disconnect time, terminate time and days off fields should be defined as CRON expressions. |
Several CRON expressions can be assigned for Start/Connect/Disconnect/Terminate time and Days off, they should be delimited by semicolon. |
At least one of the properties StartTime/ConnectTime/DisconnectTime/TerminateTime must be specified. |
The options below can be specified for all the schedules:
After the option is chosen, it will be immediately applied either for new created session or edited existing non-active session.
SSL can be enabled for both Acceptor and Initiator FIX Sessions, however
|
You can enable SSL by checking 'SSL' checkbox in the main parameters.
When SSL checkbox is checked you can choose
Configuring SSL certificate
Verification of SSL private key
Match between private key and server certificate will be checked if "Check private key" option is selected.
In order to start certain FIX session, select it and click the “Start Session” button or go to “Session → Start Session” menu to start it.
The same can be done via right mouse click on selected session and selection of “Start Session” option from the context menu.
In order to access all sessions configured for particular server, navigate to the left side of FIXICC GUI and double click on necessary server in the "Servers" list. This will expand list of all configured FIX sessions for the server and display their summary on the right side of the window.
The following real-time session statuses are displayed next to each session under 'FIX' umbrella of monitored FIX server and in the “Status” table column of FIX session details and/or FIX sessions summary tab(s):
Status | Icon | Tooltip | Description |
---|---|---|---|
Green | Session is established | Session is up and running | |
Blue | Session is established to backup host | Session is connected to backup host/port | |
Yellow | Connecting | Session is connecting/waiting for incoming connection | |
Black | Session is planned | Start Time of the session hasn't come yet | |
Red | Session is not active | Session is not running |
To drill down to session details double click on FIX Session of your interest either in the table or in the list of sessions. Detailed view of selected FIX session will be displayed in the new tab on the right side of the FIXICC GUI.
Session updates are sent automatically. In order to set updates frequency and response waiting time, go to “Edit → Options” and select the FIXICC tab.
"F5" hot key can be used at any time to request latest FIX session statuses update. |
Right‐click the required session on the list and select “Edit Session” from the context menu to edit session details.
Ability to edit sessions is supported by FIX Edge only and requires session being not started. Otherwise, session restart is required to apply the changes. |
In order to restart certain session, select it and and click the “Restart Session” button in "Sessions" toolbar or go to “Session → Restart Session” menu option.
The same can be done via right mouse click on necessary session followed by selection of “Restart Session” item from the context menu.
After session restart, sequence numbers will be treated according to the 'Force SeqNum Reset Mode' defined in the 'Sequence Numbers' tab of 'Session' details. |
Selected FIX session ca be stopped using “Stop Session” button in 'Sessions' toolbar or via “Session → Stop Session” menu option.
The same can be done via right mouse click on necessary FIX session followed by selection of “Stop Session” item from the context menu.
FIX Antenna does not support offline work with sessions, so it will be deleted from the list once is stopped. |
Selected FIX session ca be removed from the server using “Remove Session” button in 'Sessions' toolbar or via “Session → Remove Session” menu option.
The same can be done via right mouse click on necessary FIX session followed by selection of “Remove Session” item from the context menu.
In case of FIXEdge, such action removes selected session from the 'FIXEdge.properties' file too. |
Similar actions can be used to remove multiple sessions. In order to do so, select necessary sessions holding 'Ctrl' button and use the most convenient way to remove these sessions. |
To remove all configured FIX sessions from the server, click the “Remove All Sessions” button in 'Sessions' toolbar or go to “Session → Remove All Sessions” menu option.
In case of FIXEdge, such action removes all FIX sessions from the 'FIXEdge.properties' file too. |
Extended session functionality can be accessed via 'Session' sub-menu and/or 'Session Administration Extension' toolbar.
Note, “View → Toolbars” context menu item can be used to hide/unhide this toolbar.
This feature is available only if backup connection settings are specified via 'Advanced Settings' for the FIX session.
It is possible to change and/or reset sequence numbers for any FIX Session configured at the server.
Change Sequence Numbers
In order to do so, select required session, click the “Set Sequence Numbers” button in the toolbar or go to “Session → Set Sequence Numbers” menu item and then adjust sequence numbers by checking relevant check box and entering a new value.
Note: It is possible to change both Incoming and Outgoing Sequence Numbers at once or just one of them.
Reset Sequence Numbers
To reset sequence numbers for selected session, click the “Reset Sequence Numbers” button in the toolbar or go to “Session → Reset Sequence Numbers” menu item.
Both features are also accessible via right mouse click on selected FIX session. |
FIXICC allows specifying any FIX message(s) to be sent by server via selected FIX session.
This can be achieved so. Click “Send Message” button in the toolbar or go to “Session → Send Message” menu item to open a 'Send message' form, enter FIX message and click 'OK'. 'Cancel' button discards attempt to sent the message and closes the window.
FIX message can be entered either:
Besides that, it is possible to send preset session level messages:
via corresponding 'Send Test Request' and 'Send Heartbeat' buttons in the toolbar or 'Session → Test Request' and 'Session → Heartbeat' menu items.
The same can be also done using right mouse click for selected FIX session. |
Session Log browsing functionality is available in the 'Session' menu and 'Session Administration Extension' toolbar.
Note, “View → Toolbars” context menu item can be used to hide/unhide this toolbar.
To use this feature you have to have FIX Log Analyzer – FIXEye installed. Make sure this component is installed before proceeding. |
Open log-files
It is possible to open all log files at once or only incoming or outgoing ones.
Once necessary action is chosen, FIX Log Analyzer – FIXEye will launch.
The same can be also done using right mouse click for selected FIX session and choosing necessary option in 'View Session Logs' context sub-menu |
Search in log-files
FIXICC also allows fast data search in FIX log files. In order to do so, select a required session and then
First messages from incoming log-file, then from outgoing log-file will be shown.
Schedules level was introduced in FIXICC 2.10.1 with FIXEdge 6.0. Since FIXEdge 6.0 to activate Schedules functionality in FIXICC you should specify FIXICC.Schedules property equal to true in the FIXEdge.properties configuration file. |
Once server is added, you will be able to view, configure and manage Schedules. This section describes what can be done to a Schedule.
Schedules which are assigned to at least one session are colored. In opposite, schedules which are not assigned to any session are not colored. |
All the date/time properties of schedule are defined in CRON format. CRON expressions have the following syntax:
Support of the CRON expressions is limited by quartz. In particular, specifying both a day-of-week and a day-of-month values is prohibited (you'll need to use the '*' character in one of these fields). The only note here is that '*' character is used instead of '?' character in compare with quartz. |
Add new schedule
"Add a new schedule" can be chosen from the context menu of the Schedules item:
After clicking on this option, form for adding new schedule will appear:
Schedule can be assigned to the specific session using New-style Scheduler tab.
Name of the schedule should be unique. One schedule can be assign to several sesions. If time zone is not specified explicitly, local time will be applied.
Start time, connect time, disconnect time, terminate time and days off fields should be defined as CRON expressions. |
Several CRON expressions can be assigned for Start/Connect/Disconnect/Terminate time and Days off, they should be delimited by semicolon. |
At least one of the properties StartTime/ConnectTime/DisconnectTime/TerminateTime must be specified. |
Schedule details can be opened by double clicking on the specific schedule from the Schedules list:
Schedule editing can be chosen in the schedule's context menu:
After clicking on this option, editing form will appear:
Schedule name can't be edited once created. |
Start time, connect time, disconnect time, terminate time and days off fields should be defined as CRON expressions. |
Several CRON expressions can be assigned for Start/Connect/Disconnect/Terminate time and Days off, they should be delimited by semicolon. |
At least one of the properties StartTime/ConnectTime/DisconnectTime/TerminateTime must be specified. |
Schedule removal can be chosen in schedule's context menu:
After clicking on this option, confirmation dialog will appear. After confirmation the corresponding schedule will be removed.
You can remove only the schedule which is not assigned to any of the sessions. Otherwise you will get the following error: |
Permission management is available only if B2BITS Security Service is installed and is running. It is available for user with administration rights only. Users with guest-type will not have access to these settings.
User’s permission management functionality is available in the “Edit → Permissions…” submenu.
Add User
To add new user, click the “Add User” button, fill out the form with relevant data and click 'OK'. Clicking 'Cancel' will discard entered settings
User Modification
The following can be done to already defined FIXICC user:
Select user from the list and click the “Edit Permissions” button to open permissions management window.
Server Permissions
To assign user with necessary permissions, go to 'Server Permissions' tab, select necessary Server and set new permissions to be granted. The same approach can be used to limit user permissions. Full access to the server can be granted selecting “All” option.
Note: Context menu (right mouse click on the servers list) contains Remove/Add item elements.
Session Permissions
In addition to server-wide, user can be granted session-level permissions. In order to do so, go to 'Server Permissions' tab, select Server and necessary Session and then set necessary permissions to be granted.
The same approach can be used to limit user permissions. Full access to the FIX sessions at the server can be granted selecting “All” option.
Note: Context menu (right mouse click on the servers list) contains Remove/Add item elements.
Session Group Permissions
In order to set permissions to manage group of FIX sessions, go to 'Group Permissions' tab, select necessary group and set permissions to be granted to this group.
The same approach can be used to limit group permissions. Full access to the FIX sessions at the server can be granted selecting “All” option.
Note: Context menu (right mouse click on the servers list) contains Remove/Add item elements to Remove/Add group.
Note, FIX session can be added to necessary security group via “Security Groups” field on 'Security' tab.