Chapter 5: Configuring and Using Alerts

Sample nnsyreg.dat_mqs file

After creating an IBM WebSphere MQ queue manager named QMALERTS and queues under that manager named PENDING, HISTORY, and ERROR, you can use the sample ims54alertg and ims54alertd configuration files already discussed in this chapter or the following OT configuration file to configure your transport.

The following code is a sample of the external OT configuration file nnsyreg_msq.dat, which is intended for use with IBM WebSphere MQ.

# File:    nnsyreg_mqs.dat

# Purpose: Sample Open Transport (OT) config for OT

# MQ Series driver

# Usage indicated above each stanza.

# Copy/append to nnsyreg.dat in working dir or

# dir specified by NNSY_ROOT environment variable

# Context for transports

     OTContext.OTI_Context

     NNOT_CTX_EMULATE_TM = TRUE

     NNOT_CTX_ENFORCE_TX = TRUE

     NNOT_CTX_DEFAULT_TIL_ID = DefaultTransport

# Identifies the MQS series queue manager by name (QMALERTS)

Session.OTI_Queuing

     NNOT_SHARED_LIBRARY		= dbt26mqs

     NNOT_FACTORY_FUNCTION	= NNMQSSessionFactory

     NNMQS_SES_OPEN_QMGR	= QMALERTS

# Default tranport information

Transport.DefaultTransport

     NNOT_FACTORY_FUNCTION = NNMQSQueueFactory

     NNOT_SHARED_LIBRARY = dbt26mqs

     NNOT_TIL_OPEN_SESSION_ID = OTI_Queuing

# The alert message input transport. Queue name PENDING

Transport.AlertsIn

     NNOT_FACTORY_FUNCTION	= NNMQSQueueFactory

     NNOT_SHARED_LIBRARY = dbt26mqs

     NNOT_TIL_OPEN_SESSION_ID = OTI_Queuing

     NNOT_TIL_OPEN_TSI = PENDING

# The optional alert message history log. Queue name HISTORY

Transport.AlertLog

     NNOT_FACTORY_FUNCTION = NNMQSQueueFactory

     NNOT_SHARED_LIBRARY = dbt26mqs

     NNOT_TIL_OPEN_SESSION_ID = OTI_Queuing

     NNOT_TIL_OPEN_TSI = HISTORY

# The place where malformed alert messages are sent.  Queue name ERROR

Transport.AlertError

     NNOT_FACTORY_FUNCTION = NNMQSQueueFactory

     NNOT_SHARED_LIBRARY = dbt26mqs

     NNOT_TIL_OPEN_SESSION_ID = OTI_Queuing

     NNOT_TIL_OPEN_TSI = ERROR

To use this configuration as is, create an IBM WebSphere MQ messaging queue manager named QMALERTS, and create queues under that manager named PENDING, HISTORY, and ERROR.

The Transport.Alerts stanza identifies the related properties for the PENDING queue. In the alertg configuration file, the key TransportName has the value AlertsIn, which specifies the PENDING queue. The net effect of running alertg with the combined sample configurations is to place an alert message in the queue named PENDING. The HISTORY and ERROR queues are used only by alertd.

Sample nnsyreg_file.dat using a file driver

View this book as PDF