APP10 Purpose:
APP10 allows users to query MESSAGING, MESSAGING and MESSAGING records. Users can cancel MESSAGINGs, modify or resend MESSAGINGs, or enter MESSAGING or MESSAGING records.
APP10 Servers send corrected MESSAGING reports to Matching Engines, or directly to TRS services when they correct MESSAGINGs.
Use the
following hyperlinks to jump to the desired section of APP10 documentation:
APP10_Monitoring_Considerations
APP10 Recovery Considerations:
Stopping/Restart
Processes:
-
Use NTM Control Utility - Service Control -
Process Controller to stop/restart processes.
- Use APP10 nodes only when moving between nodes. (Java code, FireDaemon and Host Specific references in JNLPs required.)
- When stopping/restarting APP10 processes:
1) Notify Operations and work in cooperation with them, as appropriate to situations.
2) Stop/Restart the APP10 process.
Refresh Sub Accounts Data:
- Use NTM Control Utility – Service Control - APP10 – Refresh Sub Accounts Data.
APP10 Symptom |
Impacts |
Response |
Node Crashes Evidenced by: - In Solarwinds (and outlook), node and processes will be reported down. |
Operations will not be able to query or administratively manage MESSAGINGs, MESSAGINGs or MESSAGING reports via APP10. Refer to: Server
Recovery - Opcon OMS APP10 DCSR.docx Server Specific Recoveries. |
1) Refer to: Server Recovery
- Opcon OMS APP10 DCSR.docx Server Specific Recoveries. 2) Notify Management. |
APP10 Monitoring Considerations:
Stats
Monitors: |
To Start: |
Key Indicators to
Monitor: |
Symptom: |
Response: |
Processes
facilitate MESSAGING and MESSAGING research and modification capabilities
with Matching Engines. |
PROD MENU: |
- Color of data in columns |
Data is RED. Process is either down or multicast data is not being
received by monitor. |
1) Check status of process |
Not all APP10 processes are displayed as expected. |
APP10 Service has not been started. |
|||
Msgs In and/or Msgs Out are zero when messages are
processed. |
No messages have been sent/received since that monitor has
been started. |