|
CICS® Transaction Gateway Programming Reference v1.1.0.0 | |||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
public interface RequestExit
All implementations of CICS Transaction Gateway RequestExit monitoring classes must implement the RequestExit interface.
Request level monitoring allows a 3rd party application to be called at significant points in the request flow through the Gateway daemon and Java client classes.
JavaGateway
(Java client) or Gateway daemon.ShutDown
to allow them to tidy up any external resources they have used.
A RequestExit object is defined by a class that implements the
RequestExit interface. A single RequestExit object is created for
each configured request level monitor. Each object receives
eventFired()
method calls at the start of the request (E1) and at the
end of the reply (E2) for each flow. These are shown by E1 and E2 on
the diagrams. Timestamps will be taken during the flow at T1, T2, T3
and T4 on the diagrams.
RequestReceived
- T1) is generated as a request
arrives at the Gateway daemon or Java client. The timestamp is
available in the properties on the call to the eventFired method with
RequestEvent of
RequestEntry
(E1).RequestSent
-
T2), when the reply
arrives back in the Gateway daemon or Java client
(ResponseReceived
- T3), and when the reply finally leaves the Gateway daemon or Java
client
(ResponseSent
- T4). These are available in the properties on
the call to the eventFired method with RequestEvent of
ResponseExit
(E2).The data provided by the eventFired method is read-only.
The RequestExit object will exist for the lifetime of the Gateway daemon or Java client, or until it throws an exception or run-time error. The eventFired method is called on the same thread as the request. All processing performed by the exit will impact the performance of the Gateway or Java client and should be kept to a minimum. An example exit (com.ibm.ctg.samples.requestexit.ThreadedMonitor.java) is provided to show how to off-load this processing to a separate thread.
Example implementations of the RequestExit interface can be found in the com.ibm.ctg.samples.requestexit.BasicMonitor and com.ibm.ctg.samples.requestexit.ThreadedMonitor class. The source for these can be found in \samples\java\com\ibm\ctg\samples\requestexit
Method Summary | |
---|---|
void |
eventFired(RequestEvent event,
java.util.Map<RequestData,java.lang.Object> data)
This method will be called for each defined MonitorEvent. |
Method Detail |
---|
void eventFired(RequestEvent event, java.util.Map<RequestData,java.lang.Object> data)
event
- at which the exit is calleddata
- read-only Map of monitoring data
|
©Copyright IBM Corp. 1994, 2014 Legal |
|||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |