APP19 Purpose:
APP19 Fix Engine receives MESSAGING messages from MESSAGING sending SITE 1 and sends them to APP01 via OMS for actual trading.
APP19 Fix Engines can also send to APP02, APP03 or APP04 if SITE 1 route them there using fix tags, but typically they are sent to APP01.
APP19 Fix Engines then receive related responses from
these services for processing and/or error handling.
Use the
following hyperlinks to jump to the desired section of APP19 documentation:
APP19_Monitoring_Considerations
APP19 Recovery Considerations:
Stopping/Restart
Processes:
-
Use NTM Control Utility - Service Control -
Process Controller to stop/restart processes.
- When moving between nodes:
1) ALTERNATE NODES are not defined for APP19 services.
2) DR NODES must be allocated un-natted nodes.
No node can support more than one natted address at the same time.
- When stopping/restarting APP19 processes:
1) Notify MESSAGING sending SITE 1 involved and work in cooperation with them, as appropriate to situations.
2) Stop the APP19 process.
3) If NOT moving APP19 to new node, skip to step 5.
a) If moving the APP19 to a new node, copy the day’s APP19 FIX engine files to alternate node:
a) Copy: \\data\{APP19}\*.log, *.body, *.header, *.seqnums, *.session file created for the day to the alternate node.
b) Copy: \\data\{APP19}\Global.* file created for the day to the alternate node.
c) If the target folder does not exist on the new node, you must first either create the folder, or copy the entire folder.
d) If these files are not moved before the process restarts on the new node, there will be a chance of sequence number miscommunications between the MESSAGING sending firm involved and .
4) Start the APP19 process.
5) Open the channel for the process affected and confirm MESSAGING sending firm connects as expected.
Open OSF Channel:
- Use NTM Control Utility – Service Control - APP19 – Open OSF Channel to make OSF connection possible.
Close OSF Channel:
- Use NTM Control Utility – Service Control - APP19 – Close OSF Channel to make OSF connection impossible.
Set Inbound Sequence Number:
- Use NTM Control Utility – Service Control - APP19 – Set Inbound Sequence Number to set Inbound Sequence Number.
Set Outbound Sequence Number:
- Use NTM Control Utility – Service Control - APP19 – Set Outbound Sequence Number to set Outbound Sequence Number.
Enable 29West Stats:
- Use NTM Control Utility – Service Control - APP19 – Enable 29West Stats to start collection and display of LBM related stats.
Disable 29West Stats:
- Use NTM Control Utility – Service Control - APP19 – Disable 29West Stats to stop collection and display of LBM related stats.
APP19 Symptom |
Impacts |
Response |
Firm disconnects or Logs out of session Evidenced by: - EMT message saying {firm} is disconnected and/or {firm} is logged out. - Stats monitor shows disconnected in status column. {Firm} will be further identified in EMT message by including “LocalFixId” and “RemoteFixID” as configured in APP19Services.xml file within the disconnect message. |
APP19 is no longer able to receive MESSAGING messages or return responses to MESSAGING sending SITE 1. |
1) Contact firm. 2) Work with firm and/or Technical Services as necessary to isolate cause of issues and resolve them. 3) Stop/Restarts of affected application service may help resolve the issue. |
APP19 Monitoring Considerations:
Stats
Monitors: |
To Start: |
Key Indicators to
Monitor: |
Symptom: |
Response: |
Processes facilitate communications from MESSAGING
Sending SITE 1 to fix engine for
special routing (via OMS to APP01, Away Market Destinations or APP04). |
PROD MENU: |
- Color of data in columns |
Data is RED. |
Process is either down or multicast data is not being
received by monitor. |
|
|
|
Status is Disconnected or Open |
Firm is not connected. |
|
|
|
Write Queue is non-zero values and not reducing as
expected. |
Firm may not be processing as expected. |
Stats Monitors: |
To Start: |
Key Indicators to Monitor: |
Symptom: |
Response: |
Processes facilitate
communications from MESSAGING Sending SITE 1 to fix engine for special routing (via OMS to APP01,
Away Market Destinations or APP04). |
PROD MENU: |
- Color of data in columns |
Data is RED. |
Process is either down or
multicast data is not being received by monitor. |
No data is displayed. |
No data has been generated between
MESSAGING Sending Firm and fix engine.
|
|||
Aggregate InCount (by service
name) is not less than, or equal to aggregate (by service name) OutCount. |
Firm may not be processing as
expected. |
Stats Monitors: |
To Start: |
Key Indicators to Monitor: |
Symptom: |
Response: |
Processes facilitate
communications from MESSAGING Sending SITE 1 to fix engine for special routing (via OMS to APP01,
Away Market Destinations or APP04). |
PROD MENU: |
- Color of data in columns |
Data is RED. |
Process is either down or
multicast data is not being received by monitor. |
Not all APP02 processes are
displayed as expected. |
APP02 Service has not been
started. |
|||
Msgs In and/or Msgs Out are zero. |
No messages have been
sent/received since that monitor has been started. |
Stats Monitors: |
To Start: |
Key Indicators to Monitor: |
Symptom: |
Response: |
Processes facilitate
communications from MESSAGING Sending SITE 1 to fix engine for special routing (via OMS to APP01,
Away Market Destinations or APP04). |
PROD MENU: |
- Color of data in columns |
Data is RED. |
Process is either down or
multicast data is not being received by monitor. |
Not all APP19 or OMS processes are
displayed as expected. |
APP19 or OMS Service has not been
started or hasn't processed any messages since monitor has been started. |
|||
Status is not CONNECTED. |
Messages cannot be sent from
source to destination unless IPC channel is connected. |
|||
Queue size is non-zero value and
not decreasing as expected. |
Messages cannot be sent from
source to destination unless IPC channel is connected. |
Stats Monitors: |
To Start: |
Key Indicators to Monitor: |
Symptom: |
Response: |
Processes facilitate
communications from MESSAGING Sending SITE 1 to fix engine for special routing (via OMS to APP01,
Away Market Destinations or APP04). |
PROD MENU: |
- Color of data in columns |
Data is RED. |
Process is either down or
multicast data is not being received by monitor. |
Not all APP19 or FMR processes are
displayed as expected. |
APP19 or FMR Service has not been
started or hasn't processed any messages since monitor has been started. |
|||
Status is not CONNECTED. |
Messages cannot be sent from
source to destination unless IPC channel is connected. |
|||
Queue size is non-zero value and
not decreasing as expected. |
Messages cannot be sent from
source to destination unless IPC channel is connected. |