Integrating IBM Tivoli Workload Scheduler with Tivoli Products

434 Integrating IBM Tivoli Workload Scheduler with Tivoli Products

Parameters

Table 9-38 lists the parameter that you can set for the HostAvail resource model.

Table 9-38 Parameter for HostAvail resource model

Logging

Table 9-39 shows the resource, context, and properties for which data can be

logged.

Table 9-39 Resources available for logging in HostAvail resource model

The SpaceUsed resource model does not use an MOF file.

9.7.10 TWS SpaceUsed (schedlog)

The design of the resource model for the space that is used in the schedlog

directory is the same as for the stdlist directory, as described in 9.7.9, “TWS

SpaceUsed (stdlist)” on page 430, except that during the configuration phase of

the resource model, you use a different parameter.

9.8 Implementation

As shown in Figure 9-1 on page 402, the Tivoli Management Region (TMR)

Server in the lab that we used for this book is installed on the TWS Master

Domain Manager (MDM) server milan. A Managed Node and Gateway are

installed on the TWS Domain Manager server paris. In our environment, we

installed the Tivoli Monitoring base component and the Tivoli Monitoring Web

Health Console server component on the same server (milan) because it was the

TMR server.

Parameter Description Default

DirPath Full directory path of directory to test. /tmp

Resource Context Properties

SpaceUsedDir SpaceUsed ScriptResult

The standard output from each

run of the space used test

script.

Note: All commands that we ran on the primary TMR, ITM, and MDM servers

shown in this section assumed that the Tivoli environment was already

sourced.

Chapter 9. Integrating Tivoli Monitoring 435

You source the Tivoli environment using the following command.

. /etc/Tivoli/setup_env.sh

Your Tivoli Framework administrator or IBM service provider might have

configured your shell environment to source the Tivoli environment each time

you log in.

9.8.1 Installing the integration

You install the integration between Tivoli Monitoring and TWS by ensuring that

Tivoli Monitoring is configured on all systems which impact the production

schedule that need to be monitored. The majority of the integration between

Tivoli Monitoring and TWS occurs during the configuration phase. See your Tivoli

Framework administrator or IBM service provider for details on how to verify the

configuration of the base installation of Tivoli Monitoring.

In the lab for this book, we determined that using the JRE that is supplied by IBM

yields the best results. This JRE was copied from the Tools disc of the Tivoli

Monitoring media. In our lab, we installed the IBM-supplied JRE files under the

directory /usr/java131-itm. It can also be installed using the wdmdistrib

command. For details, refer to IBM Tivoli Monitoring User’s Guide Version 5.1.2,

SH19-4569.

Multiple JREs can coexist without issue on the same system. Example 9-3

shows how we linked the JRE for Tivoli Monitoring. The linking procedure is not

necessary in some Tivoli Monitoring installation scenarios.

Example 9-3 Linking to the IBM-supplied JRE for Tivoli Monitoring

milan:/tivoli/media# wruntask -t DMLinkJre -l 'IBM Tivoli Monitoring Tasks' \

-E -h paris.itsc.austin.ibm.com -m 1800 -a "/usr/java131-itm/jre"

############################################################################

Task Name: DMLinkJre

Task Endpoint: paris.itsc.austin.ibm.com (ManagedNode)

Return Code: 0

------Standard Output------

****************************************************************

java version "1.3.1"

Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1)

Note: This procedure should have been performed for you if your Tivoli

Framework administrator installed Tivoli Monitoring on the systems that you

want to monitor. We present this example so that you can verify with your

Tivoli Framework administrator that this JRE has been linked on the servers

that are impacted by the production plan.

436 Integrating IBM Tivoli Workload Scheduler with Tivoli Products

Classic VM (build 1.3.1, J2RE 1.3.1 IBM AIX build ca131-20030630a (JIT enabled:

jitc))

****************************************************************

JRE is correctly installed.

JRE is a suitable version.

The JRE has been successfully linked.

------Standard Error Output------

############################################################################

The specific build string ca131-20030630a that is highlighted in red text in the

example indicates the exact JRE version that is bundled with Tivoli Monitoring.

Refer to the resources listed in “Related publications” on page 691 if you are

installing Tivoli Monitoring for the first time.

9.8.2 About the configuration

The majority of the integration between Tivoli Monitoring and TWS is performed

through the configuration of profile managers, profiles, subscribers, and resource

models. These are all objects within Tivoli Management Framework. The

remainder of the sections discuss the configuration tasks.

Tip: All of the configuration tasks included in this book have command line

interface equivalents. If you need to quickly configure many resource models

or need a way to duplicate the configuration activities (useful for disaster

recovery procedures, for example), we recommend that you use the

command line interface equivalents. See your Tivoli Framework administrator

or IBM service provider for details on how to use the command line for Tivoli

Monitoring.