![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
Included in the product is an “exported” BusinessWorks project, packaged as Mainframe_Tracker_Example_V1R2.zip, for BusinessWorks developers. This project, which you can import, demonstrates the processes that monitor Tracker Server messages, as follows:
• Listener Process for ALERTS
• Listener Process for JOBS
−
• Listener Process for SYSLOGReceives the Tracker Server-published Rendezvous messages for the monitored SYSLOG activities and saves them to a file.
• Receives the Tracker Server-published Rendezvous response messages for the RESEND request sent by the ReSend Process for the monitored JOBs and saves them to a file.
• ReSend ProcessPublishes a RESEND request to the Tracker Server for a resend of the current active messages of monitored JOBs.A BusinessWorks project is available as a template for processing the messages. To use that project, you must first update the global parameters (see Table 24) to synchronize with their Tracker Server parameters.
Table 24 Global Parameters The location of the Rendezvous daemon, which matches the one to which the Tracker Server components are connected, for example, tcp:rvdaemon.tibco.com:7500. Default: 7555 Default: tibtrk.usermsg The subject name to which the Tracker Server publishes the message on the related job.Default: tibtrk.jobstep The subject name to which the BusinessWorks process is listening for the resend activity.Default: tibtrk.resend.reply.BW The subject name to which the Tracker Server listens for RESEND requests.Default: tibtrk.resend.request The subject name to which the Tracker Server publishes all SYSLOG messages of interest.Default: tibtrk.logmsg Default: c:\temp\trackerWhen you start the BusinessWorks Project for job messages or other business needs, first obtain a list of the currently active JOBs monitored by the Tracker Server by sending a RESEND request message to the subject name tibtrk.resend.request through the ReSend Process. The following then occurs:
1. The Tracker Server sends the response messages back to the subject name tibtrk.resend.reply.BW, which is defined as the global variable TrackerResendReplySubject in the BusinessWorks Project.
2. After sending all the active messages, the Tracker Server waits one second and then sends a last message with a field named MSGCOUNT, which is the total number of messages sent for the RESEND request.
3. The Listener Process for RESEND builds a temporary file for each job. For each message within a job it receives, the process saves a record to the file.
4. When the end-of-job message arrives, the process executes the process User End-of-Job Process Definition and then deletes the related temporary file. The records from the temporary file are then permanently written to a file called JOB.xml in the TrackerTempDir directory.Subsequently, the Tracker Server publishes the monitored job messages, which are received by the Listener Process for JOBS from tibrk.jobstep, defined as the global variable TrackerJOBSTEPSubject in the BusinessWorks Project. For each message it receives, the process saves a record to the file.When the end-of-job message arrives, the process executes the process User End-of-Job Process Definition and then deletes the related temporary file. The records from the temporary file are then permanently written to a file named JOB.xml in the TrackerTempDir directory.The BusinessWorks process Listener Process for SYSLOG shows an example of the monitored SYSLOG messages published by the Tracker Server to the subject named tibtrk.logmsg. For each message it receives, the process writes a record to a file named SYSLOG.xml in the TrackerTempDir directory.The BusinessWorks process Listener Process for ALERTS shows an example of the monitored alert messages published by the Tracker Server to the subject named tibtrk.usermsg. For each message it receives, the process writes a record to a file named ALERT.xml in the TrackerTempDir directory.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |