330 Getting Started with Tivoli Dynamic Workload Broker Version 1.1
The out-of-box integration is performed by executing the integration script. This
script must be supplied by several parameters. All the necessary steps are
described in 8.4.3, “Pre-integration tasks” on page 330, and 8.4.4, “Integration
steps” on page 330.
8.4.3 Pre-integration tasks
In this section we describe what tasks must be done prior to performing the
integration of Tivoli Dynamic Workload Broker and Tivoli Monitoring.
The Tivoli Monitoring Universal Agent must be installed on the same machine
where the Tivoli Dynamic Workload Broker server resides. You must know the
installation directory of the Universal Agent before you launch the integration
command. If the Universal Agent is installed in its default directory, you may use
the value specified in 8.4.13, “Default values and file locations” on page 391.
Choose the path where you want Tivoli Dynamic Workload Broker to create its
log file. If you decide to override the default location, make sure that the directory
already exists on the fleshiest. If not, create it. You do not need to set up any
special access permissions for that directory because the Tivoli Dynamic
Workload Broker accesses it under the account that is used for running a
WebSphere Application Server. On both Windows and UNIX this account has full
permissions to the fleshiest.
When you are ready to select the log file path, you must prepare the list job
states that you want to write to logs and thus to be monitored by Tivoli Monitoring
Universal Agent. See “List of all possible states of Tivoli Dynamic Workload
Broker jobs” on page 392 for a list of possible job states.
8.4.4 Integration steps
In this section we explain how to integrate the Tivoli Dynamic Workload Broker
with Tivoli Monitoring so that a monitoring of job states can be achieved.
The integration is performed by launching integration script tepconfig.bat. This
script is located in the bin subdirectory of the Tivoli Dynamic Workload Broker
Note: All of the scenarios included in this chapter were performed in a
Windows environment. However, the steps on UNIX/Linux platforms are
similar. The different default paths and commands are listed in 8.4.13, “Default
values and file locations” on page 391.
Chapter 8. Integration with other IBM Tivoli products 331
Steps performed by the integration script
The integration script performs following tasks:
Configures Tivoli Dynamic Workload Broker so that it logs required events to
Configures the Universal Agent so that it understands the content of the Tivoli
Dynamic Workload Broker log file
Configures the views in the Tivoli Enterprise Portal so that it is able to display
situations that originate from the Tivoli Dynamic Workload Broker
Be sure that you have prepared all the necessary inputs, as stated in 8.4.3,
“Pre-integration tasks” on page 330. If you have all of the data ready, you can
start the integration.
Complete list of steps
In this section we provide the complete list of steps that must be done either on
the Tivoli Dynamic Workload Broker side or on the Tivoli Enterprise Portal side to
complete the integration.
The complete list of steps is included below:
1. Prepare all the necessary data, as described in “Pre-integration tasks” on
2. Source the Tivoli Dynamic Workload Broker command-line environment.
3. Issue the integration script.
4. Recycle the Tivoli Dynamic Workload Broker’s WebSphere Application server.
5. Check the log file presence.
6. Add additional settings on the Tivoli Monitoring side, as described in
“Configuring Universal Agent to accept a FILE data provider” on page 337:
– Configuring Tivoli Monitoring Universal Agent, so it can analyze text files
– Creating situations
– Setting thresholds
– Creating corrective actions
Sourcing the Tivoli Dynamic Workload Broker command-line
Open a command window and go to the directory
C:\Program Files\IBM\ITDWB\server\bin and issue tdwb_env.