TWS / OMNIbus Integration

1. TWS / OMNIbus Integration Jason Cress Technical Sales Engineer IBM Tivoli Software Group

2. Agenda This presentation will be focused on integration between Tivoli Workload Scheduler and Netcool OMNIbus, specifically in the following capacities: • TWS fault management • ITM Agent Integration to OMNIbus • Standalone TWS integration (No ITM infrastructure) • Event-driven workload automation • Using the EIF gateway • Using triggers and the ‘sendevent’ command line utility

3. What is Tivoli Workload Scheduler? TWS is an enterprise scheduler for batch processing, “cron on steroids” • Disparate, heterogeneous, distributed environments • Unix variants, Windows, AS/400 and Mainframe • Planned and ad hoc/dynamic jobs • Consolidation and centralization of scheduling across the enterprise with a common user interface • Specific application scheduling: • SAP • PeopleSoft • Oracle

4. Example TWS Deployment • Master Domain Manager • Data stores for all the scheduling objects • Status and configuration for networks • Connectivity to operator consoles • Fault Tolerant Agent Master domain manager AIX Master Domain Manager DomainA DomainB • Domain Manager • Fault Tolerant Agent • Management Hub • Manages inter-workstation dependencies for the domain AIX Domain Manager DMA Fault tolerant agents • Fault Tolerant Agent • Launches its own jobs • Receives copy of Plan • Manages its own dependencies FTA1 FTA2 FTA3 FTA4 Linux OS/400 Windows AIX A simple ITWS network – The whole ITWS network is managed by one workstation called the master domain manager. 4

5. What is Netcool/OMNIbus? Netcool/OMNIbus is an enterprise event management system that provides automation and correlation capabilities • Centralized event console for alerts across the enterprise • Event de-duplication and correlation • Packaged integrations to many event sources through the use of probes • Packaged integrations to many 3rd party applications through the use of gateways (e.g. Service Desk/Trouble ticketing) • Netcool/Impact extends OMNIbus functionality by providing data abstraction to other outside sources for the purpose of event enrichment and advanced correlation

6. Netcool Probes/Monitors Inventory Data Networks DSAs SLA Systems Applications Desktop/WebTop Databases Voice Networks Impact RDBMS Database Gateway Management Systems Trouble Ticket Gateway Reporter End User Experience Transaction Monitoring Trouble Ticketing ObjectServer Security/Firewalls Non-IT Resources FailOver ObjectServer Example OMNIbus Deployment

7. TWS event integration TWS generates logfile entries upon various situations that arise within its environment. Some examples include: • Job Status Change / Abends / Failures • Job Late • Job Stream Late • Job Stream Completed • Job Submitted • Alerts that describe the health of the TWS environment itself (Batchman down, etc) • Status entries are written to the MDM event log. • Two methods of integration: • In environments with Tivoli Monitoring, you can leverage the ITM TWS Universal Agent • In absence of a Tivoli Monitoring infrastructure, you can leverage the OMNIbus logfile probe

8. ObjectServer TWS ITM integration By leveraging the ITM TWS UA, you can leverage your ITM infrastructure to collect TWS event data and integrate further with the OMNIbus EIF probe. Architecture: Situations Workspaces ITM Infrastructure TWS UA EIF Probe Master Domain Manager

9. TWS ITM integration continued By leveraging the ITM TWS UA, you can leverage your ITM infrastructure to collect TWS event data and integrate further with the OMNIbus EIF probe. The ITM TWS UA also provides Tivoli Enterprise Portal workspaces

10. ObjectServer OMNIbus integration using the Logfile Probe In the absence of an ITM environment, you can leverage the OMNIbus logfile probe to collect events directly from the MDM The probe is installed and configured to read events.log on the MDMs of interest, and the rules parse and classify the events. Example: Master Domain Manager Logfile Probe

11. Benefits of TWS -> OMNIbus alert integration By integrating TWS alerts in an OMNIbus environment, you can leverage common enterprise management strategies without having to configure a one-off integration between TWS other enterprise management systems: • Trouble Ticketing and Service Desk systems • Event enrichment using Impact • Common Escalation and Notification strategy

12. Event-driven Job Scheduling

13. Event-driven Job Scheduling Tivoli Workload Scheduler 8.4 and later provides powerful event-driven functionality that can: • Solve many workload automations scenarios • Perform on-demand workload automation • Carry out a pre-defined set of actions in response to events • Events can be raised based on: • Files on the system • Files created • Files deleted • Files changed • Messages written inside a file • Internal Tivoli Workload Scheduler Events • External, “generic” alerts* • External “generic” alerts are alerts that are generated from external systems including OMNIbus

14. Sending events from OMNIbus to TWS for Workload Automation Two methods are available for generating alerts from OMNIbus into TWS: • By leveraging the OMNIbus EIF gateway, you can filter and forward alerts from OMNIbus to TWS • Using the ‘sendevent’ command-line utility and OMNIbus triggers and exec actions, you can also forward alerts

15. OMNIbus EIF Gateway Integration The gateway for Tivoli EIF is used to forward events from IBM Tivoli Netcool/OMNIbus to applications that accept events in EIF Format The Gateway consists of a reader component and a writer component. The reader extracts alerts from the OMNIbus based on a pre-defined filter, and the writer component forwards the alert to a pre-defined destination. The EIF gateway is a Uni-directional gateway, inserts and updates to alerts in OMNIbus are forwarded, but changes in the EIF in the source Object Server**

16. ObjectServer EIF Gateway Integration Status mapping for writer: CREAT MAPPING StatusMap ( Workstation = @Node MyParam = @Summary … ); The status mapping configuration maps Object Server fields to EIF slot values The filter definition defines which alerts are sent across the gateway to the EIF listener on TWS Filter definition for writer: CREATE FILTER TWS_ALERTS AS ‘AlertGroup = \’TWSForward\’’ START READER EIFReader CONNECT TO NCOMS USING FILTER TWS_ALERTS EIF Listener Master Domain Manager Forwarded Filtered Alerts EIF Gateway

17. ObjectServer OMNIbus trigger using ‘sendevent’ command line The sendevent command line utility forwards alerts to an EIF listener, passing event attributes as command line parms # sendevent Tip GenericEventPlugIn MyParam=‘LogMessage’ Workstation = ‘Frodo’ Substitute alert fields (i.e. @Node, @Summary) in the command execution in the trigger action EIF Listener Master Domain Manager

18. TWS Configuration to consume generic events In order for TWS to consume and perform actions on events originating from OMNIbus, the following steps must be taken: • Download the generic event provider to a local file using the eventdef command • Add custom event types to define properties and attributes • Upload modified generic event provider using the eventdef command • In the TDW Console, define a generic event rule, and define the custom event types and properties or values that will trigger the rules • Deploy the rules • As soon as the event is received by the TWS event processing server, it triggers the rule and executes any defined actions for the rule

19. Example Event Definition <event baseAliasName="genericEvt" scope="Generic"> <complexName displayName=”MyEvent" name=”MyEvent"></complexName> <displayDescription>The event is sent when the specified expression is matched.</displayDescription> <property type="string" required="true" wildcardAllowed="true" multipleFilters="true" minlength="1"> <complexName displayName=”Parameter" name=”MyParam" /> <displayDescription>The value of parameter 1</displayDescription> </property> <property type="string" required="true" wildcardAllowed="false" multipleFilters="false" minlength="1"> <complexName displayName="Workstation" name="Workstation" /> <displayDescription>The workstation for which the event is generated.</displayDescription> </property> </event>

20. Steps to associate a TWS action with our alert definition • After modifying and reloading the event definition XML using the eventdef command, your new event definition “MyEvent” will appear in the Generic event section of the Custom event menu. • In the TWDC, navigate to the Events menu item, and select “MyEvent” • Create a new event rule, name it “MyEventRule”, and populate the “Parameter” text field box with an asterisk wildcard(*), and “Frodo” in the “Workstation” text field box • Next, define the action using the “Message Logger”, specifying the message text and severity. • Upon running the ‘sendevent’ command, or receipt of a matching alert from the EIF gateway, the event rule criteria is evaluated and the action is fired.

21. Resources and reference Event-driven workload automation reference: http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/topic/com.ibm.tivoli.itws.doc_8.5.1/dqx2evntdrivworkauto.htm#dqx2evntdrivworkauto General gateway configuration guide: http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_OMNIbus.doc/omn_pdf_prgw_master_73.pdf EIF gateway reference: http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_OMNIbus.doc/gateways/tivoli_eif/tivoli_eif/wip/concept/tveifgw_intro.html TWS 8.5.1 documentation: http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/topic/com.ibm.tivoli.itws.doc_8.5.1/ic-homepage.html Setting up the TWS Tivoli Monitoring Agent: http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/topic/com.ibm.tivoli.itws.doc_8.5.1/dqx2awsisitminteg.htm#dqx2awsisitminteg OMNIbus Information: http://www-01.ibm.com/software/tivoli/products/netcool-omnibus/

22. THANK YOU