Sample configuration files and alert-handler scripts  Additional information

Chapter 5: Configuring and Using Alerts

Sending OT-XML alerts to a cluster

In addition to sending OT-XML alerts to alertd from WebSphere MQ messaging queues, e-Biz Impact 5.4 also allows a cluster to access OT-XML alerts from messaging queues using ODL.

To enable e-Biz Impact ODL to access WebSphere MQ message queues you:

  1. Configure nnsyreg.dat to define transport properties.

  2. Develop and configure an ODL acquisition AIM (MQAcq) to acquire data from WebSphere MQ message queues. Use clot objects to define OT instances and implement OT calls through ODL, then define these instances to access the desired data.

  3. Develop and configure an ODL router application.MQAcq and MQDel applications work with router applications, rather than an SFM, to route messages or alerts to or from WebSphere MQ message queues. A router is an SFM running in “router only” mode. Configuration options for router properties are similar or identical to SFM properties. However, no log file maintenance is provided for routers; the router is responsible only for synchronous routing of the message, not storage.

  4. Develop and configure an ODL delivery AIM (MQDel) that accepts a transaction from a router and delivers it to the specified WebSphere MQ message queue. You must also copy the <install directory>/ImpactServer-5_4/include/IMPACT/MQBRIDGE/mqdel.prj to the working directory for the application instance. A sample nnsyreg.dat file is also provided in the directory.





Copyright © 2005. Sybase Inc. All rights reserved. Additional information

View this book as PDF