Integrating IBM Tivoli Workload Scheduler with Tivoli Products

332 Integrating IBM Tivoli Workload Scheduler with Tivoli Products

8.7 Design of the integration

Tivoli Workload Scheduler 8.2 comes with a product called TWS Plus Module

that configures the integration between TWS and Tivoli Enterprise Console. This

section describes the design of the integration.

Using a mechanism called a TEC logfile adapter, Tivoli Enterprise Console reads

entries from the event.log file that is located in the home directory of the

TWSuser user account on the Master Domain Manager of TWS. These entries

describe all the activities that occur in the scheduling network.

The location of the log file event.log is configured through a BmEvents.conf

configuration file. This file is the same file that is used to create the integration

with NetView. The following line in the file places the event.log file in the home

directory of TWS on milan, the MDM in the lab servers that we used for this book.

FILE=/opt/tws/m82/event.log

While other values can be used, you would have to manually configure the entire

integration with Tivoli Enterprise Console and would not be able to take

advantage of the TWS Plus Module.

The event.log file is truncated by the TWS batchman process during every

Jnextday. The size of the file depends upon the activity in the scheduling

network. Planning for 20 MB of disk space for this file is more than sufficient for

all but the largest and busiest scheduling networks of more than a hundred FTAs

with tens of thousands of jobs.

AFter the TEC logfile adapter is installed on the MDM, it runs from the endpoint

cache directory. The exact location of this directory depends upon options your

Tivoli Framework administrator selected during the installation of the endpoint

software and how the endpoint software was installed. For example, multiple

instances of the endpoint software can be installed on a single physical machine

under certain circumstances. Consult your Tivoli Framework administrator or

IBM service provider for details about the endpoint software installation on

servers in your scheduling network. In the lab server milan that we use for this

book, the cache directory was in the /opt/Tivoli/lcf/dat/1/cache/ directory path.

The TEC logfile adapter reads each line as it is appended to the event.log file,

interprets the line, and generates an event to send to the TEC server. A

configuration file is used by the TEC logfile adapter to determine where to send

Restriction: Changing where the event.log file is written or its name is not

recommended unless you are very familiar with Tivoli Enterprise Console and

are prepared to create and customize the integration manually.

Chapter 8. Integrating Tivoli Enterprise Console 333

the event. This configuration file is usually controlled from the TMR server. In the

lab that we use for this book, the TMR server is milan. When the event is

received by the TEC server, it is processed as any other TEC event.

Figure 8-2 shows the detailed steps that are involved in the event generation

process flow.

Figure 8-2 Event generation process flow

The steps that are involved in this process are:

1. The event generated at the source is characterized with an event number,

which is an identifier of the type of event information.

2. If the event number is one that is specified in the EVENT field of the

BmEvents.conf file, it is logged in the file that is specified in FILE field of the

BmEvents.conf file (in our lab environment, this was the event.log file).

3. The TEC logfile adapter reads this information inside the log file, formats it

using the structure that is stored in the FMT file (tecad_logfile.fmt), and

forwards it to the TEC event server using the TEC gateway.

4. On the TEC event server, the structure of the formatted information is

checked against the information that is stored in the BAROC files and, if

correct, is accepted. Otherwise, a parsing failure is generated.

5. When the event is accepted by the TEC event server, a check on possible

predefined correlation rules or automatic responses for that event number is