IBM Support

Health monitor and JNDI cleanup in 8x release

Question & Answer


Question

Health monitor and JNDI cleanup in 8x release

Answer

In 8.0, JNDI cleanup is not required as every JVM has its own JNDI server. Unlike earlier versions, JNDI server is no more a Single Point of Failure (SPOF).

Health monitor will identify stale YFS_HEARTBEAT entries, and delete them as appropriate. Every JVM will update its own YFS_HEARTBEAT entries every to keep it alive.   Health monitor will not call jndi cleanup methods in 8x version as every JVM manages its own JNDI tree.

Health monitor functionality in 8.0 series.
- Monitor agent behavior, raise any configured alert if pending task count is above threshold set.
- Purge YFS_SNAPSHOT records older than threshold defined by * yfs.yantra.hm.purge.interval * property (default is 30 days)
- Monitor JMS queue and raise alerts if number of messages reach above threshold
- Monitor api performance
- Monitor app server/s behavior
- Flag stale heartbeat entry and purge stale records.


 

[{"Product":{"code":"SS6PEW","label":"IBM Sterling Order Management"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"Not Applicable","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}},{"Product":{"code":"SS6PEW","label":"IBM Sterling Order Management"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"Not Applicable","Platform":[{"code":"","label":""}],"Version":"","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Historical Number

FAQ3169

Document Information

Modified date:
16 June 2018

UID

swg21518231

Page Feedback