Previous Topic Next topic Print topic

Micro Focus Enterprise Developer 2.3 Update 2 for Eclipse > Programming > Mainframe Programming > IMS Support > Deploying IMS Applications > WebSphere MQ Support > IMS Trigger Monitoring > Configuring Enterprise Server for WebSphere MQ Trigger Monitors

Configuring Enterprise Server for WebSphere MQ Trigger Monitors

The Enterprise Server region must be configured for both IMS and JES. For JES, you must define a batch initiator to process “class A” jobs. You need to ensure that enough initiators are defined for the job class to run all instances of the trigger monitor plus any other submitted jobs that will run under that class.

You also need to generate a PSB for the trigger monitor and create an XA resource to allow MPP applications to interface with IBM WebSphere MQ. A sample PSB definition file, csq4trmn.psb is included in the %ProgramFiles(x86)%\Micro Focus\Enterprise Developer\src (Windows) or $COBDIR/src/enterpriseserver/ims/mq (UNIX) folder.

The path to any IMS MPP transactions that are started by the Trigger Monitor must be present on the IMS TM Application Path.

If you have not installed the IBM MQ client or server in the default location, you must use the ES_MQ_LIB environment variable (or the ES_MQ_LIB_T environment variable for threaded environments) to identify the full name including the path of the IBM MQ library appropriate to your platform.
Important: In AIX environments the library is an object inside a shared object. For example 
ES_MQ_LIB="/usr/mqm/lib64/libmqmxa64.a(libmqm64.o)"
In addition, you must also:
  • Enable MQ listener support in Enterprise Server Administration
  • Define an MQ listener to monitor the appropriate initiation queue
Parent topic: IMS Trigger Monitoring
Previous Topic Next topic Print topic