Configuring request monitoring for the Gateway classes

The configuration of the request monitoring exits for the Gateway classes uses a JVM property, or if using a resource adapter, a custom property.

The JVM property requestExits supports monitoring of base classes without modifying user application code. The resource adapter custom property RequestExits can be configured to allow individual definition of exits for connection factories. The precedents for the two properties are defined in the following table:
Table 1. JVM and resource adapter custom property precedents
JVM property set Custom property set Exits loaded from:
No No None
Yes No JVM property
No Yes Custom property
Yes Yes Custom property
Set the JVM property to enable a request monitoring exit:
-DrequestExits=fully_qualified_class_name  
For example:
java -DrequestExits=com.ibm.ctg.samples.requestexit.BasicMonitor com.ibm.ctg.samples.eci.EciB1  

You can define multiple exits by separating them with a comma:

-DrequestExits=first_exit_name,second_exit_name  
For example:
java -DrequestExits=com.ibm.ctg.samples.requestexit.BasicMonitor,com.ibm.ctg.samples.requestexit.ThreadedMonitor 
com.ibm.ctg.samples.eci.EciB1

Reference Reference

Feedback


Timestamp icon Last updated: Tuesday, 19 November 2013


https://ut-ilnx-r4.hursley.ibm.com/tg_latest/help/topic/com.ibm.cics.tg.doc//ctgunx/exitsjc.html