1.1.1.1 AlertAdapListenAlert
On receipt of an outgoing Alert message event, processing of the message is delegated to an AlertAdapProcessAlert. To listen to an alert, the deserializeTS() method is called on the MAP2Wrapper object which is a blocking call. Once the call is deblocked the alert details are obtained from the Message object. MAP2Wrapper and Message classes along with SerialConnector, MessageSerializer, NoServerException and Log classes constitute the Alerts Outbound Wrapper provided by MyAlert. This is done in the helper class AlertAdapProcessAlert.
1.1.1.2 AlertAdapListenAlertResp
This class extends from TIBCO MeventListener class and contains the callback logic for the response messages of the outbound alerts
1.1.1.3 AlertAdapListenProd
This class extends from TIBCO MeventListener class and contains the callback logic for the Product requests. Each Product request is subscribed on a different subject and has a separate method to process the request.
1.1.1.4 AlertAdapListenProv
This class extends from TIBCO MeventListener class and contains the callback logic for the Provisioning requests. Each Provisioning request is subscribed on a different subject and has a separate method to process the request.
1.1.1.5 AlertAdapListenCMS
This class extends from TIBCO MeventListener class and contains the callback logic for the CMS requests.
1.1.1.6 AlertAdapListenLAM
This class extends from TIBCO MeventListener class and contains the callback logic for the LAM requests.
1.2 Adapter implementation and configuration
Much of the approach for implementation and configuration of the Alert adapter has followed the standard TIBCO Adapter SDK methodology.
1.2.1 Log files
The log files follow the standard H3G approach.
1.2.1.1 Activity log
This log is written to the directory and filename defined by the “activity” file sink in the adapter configuration. It contains a simple summary of the traffic going through the adaptor (messages published and responses received).
For further information on the configuration of file sinks in TIBCO, see the TIBCO SDK online documentation.
1.2.1.2 Trace log
This log is written to the directory and filename defined by the “trace” file sink in the adapter configuration. Like the activity log, the trace log contains a record of all the traffic going through the adaptor. However, the level of detail recorded is configurable using the following pre-defined ‘roles’:
errorRole Messages that indicate a definite problem in the running of the adaptor.
warnRole Messages that indicate circumstances were not expected, but may not necessarily be an error.