Appendix A. Using Tivoli Dynamic Workload Broker with Enterprise Workload Manager 637
In order for Tivoli Dynamic Workload Broker to find this library, the native
library path must be edited to include the directory of the appropriate library
listed above.
For AIX: The LD_LIBRARY_PATH environment is used to define the native
library path (that is, LD_LIBRARY_PATH=/usr/lib).
For Windows: The directory containing the JNI™ library should be defined
by the PATH environment variable (that is,
PATH=%PATH%;<ewlm_root>\ms).
For SLES 9: The directory containing the JNI library should be defined by
the PATH environment variable (that is, PATH=/usr/lib).
If the IBM JNI native library could not be found, the Tivoli Dynamic
Workload Broker agent will be not ARM instrumented. More information
can be found in the appropriate ARM-related documentation from the
Enterprise Workload Manager InfoCenter at:
http://publib.boulder.ibm.com/infocenter/eserver/v1r2/index.jsp
Enterprise Workload Manager classification of Tivoli
Dynamic Workload Broker jobs
Enterprise Workload Manager will report unclassified Tivoli Dynamic Workload
Broker work without any configuration from the administrator. However,
Enterprise Workload Manager classifies work in the enterprise environment to
understand management importance, identify work for goal setting, and to
provide more detailed reporting. In order to classify work being done in different
applications, Enterprise Workload Manager must first understand the information
each instrumented application will expose for classification. This is provided in an
Application filter xml file (named TDWB Agent.xml) currently available from
Enterprise Workload Manager or Tivoli Dynamic Workload Broker product teams.
638 Getting Started with Tivoli Dynamic Workload Broker Version 1.1
This file must be imported into the Enterprise Workload Manager Control Center
by using the Import button on the Applications panel (the Applications panel is
reached by using the Applications link under Set up). See Figure A-5.
Figure A-5 Importing TDWB_Agent.xml
Import the file named TDWB Agent.xml, as shown in Figure A-6. Tivoli Dynamic
Workload Broker agent can be found at the following path in the Tivoli Dynamic
Workload Broker Server directory space:
<server_installation_directory>/EWLM/samples
Figure A-6 TDWB_Agent.xml path
After the Tivoli Dynamic Workload Broker application file has been imported, you
will then see it in the list of applications. This step will also allow the Tivoli

Get Getting Started with Tivoli Dynamic Workload Broker Version 1.1 now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.