Recommended durable JMS client operation
Steps
1 |
Establish a JMS connection and subscription with the NFM-P; listen to JMS events, and buffer events locally. Nokia recommends that the OSS maintain two local buffer queues:
Note: The OSS must not begin processing the events from the second buffer until Step 3 is successfully completed. |
2 |
Initiate retrieval of inventory, the latest alarm list, or statistics and OAM test results using HTTP(S), or initiate retrieval of statistics and OAM log files via (S)FTP if any of the following occurs:
Note: While inventory is being retrieved, the OSS must continue to monitor the first buffer queue, as described in Step 1 . If the OSS detects connectivity loss with the NFM-P, or a loss of JMS events, the OSS should terminate the current inventory retrieval process, if possible. The internal buffer queues should be cleared. Perform exit procedures to gracefully unsubscribe and disconnect from the XML API. Then repeat the start-up procedures from Step 1 . |
3 |
After the inventory retrieval completes successfully, start listening to the events from the second buffer queue described in Step 1 . Continue to monitor the first buffer queue. |
4 |
If the OSS has to restart, the OSS should perform exit procedures to gracefully unsubscribe and disconnect from the XML API, then repeat the start-up procedures from Step 1 . The OSS may need to restart if the OSS detects one of the following:
See Monitoring a JMS connection in JMS communication for more information about JMS connection monitoring. End of steps |