APP17 Purpose:
APP17 Fix Engine receives MESSAGING messages from APP01 and sends them to APP17 for actual trading.
They then receive related responses from these
services for processing and/or error handling.
Use the
following hyperlinks to jump to the desired section of APP17 documentation:
APP17_Monitoring_Considerations
APP17 Recovery Considerations:
Stopping/Restart
Processes:
-
Use NTM Control Utility - Service Control -
Process Controller to stop/restart processes.
- Use OMD nodes only when moving between nodes. (OMD NAT addresses must be configured/used by APP17.)
- When stopping/restarting APP17 processes:
1) Notify APP17 and work in cooperation with them, as appropriate to situations.
2) Stop the APP17 process.
3) If NOT moving APP17 to new node, skip to step 5.
a) If moving the APP17 to a new node, copy the day’s APP17 FIX engine files to alternate node:
a) Copy: \\data\{APP17}\*.log, *.body, *.header, *.seqnums, *.session file created for the day to the alternate node.
b) Copy: \\data\{APP17}\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 APP17 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 - TRF – Open OSF Channel to make OSF connection possible.
Close OSF Channel:
- Use NTM Control Utility – Service Control - TRF – Close OSF Channel to make OSF connection impossible.
Set Inbound Sequence Number:
- Use NTM Control Utility – Service Control - TRF – Set Inbound Sequence Number to set Inbound Sequence Number.
Set Outbound Sequence Number:
- Use NTM Control Utility – Service Control - TRF – Set Outbound Sequence Number to set Outbound Sequence Number.
Enable 29West Stats:
- Use NTM Control Utility – Service Control - TRF – Enable 29West Stats to start collection and display of LBM related stats.
Disable 29West Stats:
- Use NTM Control Utility – Service Control - TRF – Disable 29West Stats to stop collection and display of LBM related stats.
APP17 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 APP17Services.xml file within the disconnect message. |
APP17 is no longer able to receive MESSAGING messages or return responses to APP01. |
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. |
APP17 Monitoring Considerations:
Stats
Monitors: |
To Start: |
Key Indicators to
Monitor: |
Symptom: |
Response: |
Processes facilitate communications from to FINRA/NASDAQ Trade Reporting Facility
Destinations. |
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. |
|
|
|
InCount
does not match OutCount. |
We may not be processing as expected. |