Chapter 10. Integrating Tivoli Business Systems Manager 561
The event parser takes the data from the event recognizer and creates a table for
the formatter-forwarder to pass to TBSM. Each message ID from the event
parser is a key in another table that returns the following data:
򐂰 Parsing Mode
򐂰 TBSM Class Name
򐂰 TBSM Resource Names
򐂰 TBSM Text
򐂰 TBSM State
򐂰 TBSM Alert
򐂰 TBSM Priority
The adapter driver uses the hash table to format and forward the events to TBSM
through the formatter-forwarder using the data described above.
10.4 Configuration of the log adapter
Six configuration files are located in the installation directory (typically
/opt/Tivoli/IMfTWS):
򐂰 AdapterEnv.conf
򐂰 DriverPlugIns.conf
򐂰 DB_Server.conf
򐂰 localadapter.conf
򐂰 Log.conf
򐂰 TWSConf.conf
These files configure the adapter with data that includes the name of the
interface being enabled, the location of the adapter database, where the TBSM
database resides, the log adapter information, and what environment variables
need to be considered.
Two other files, CollectorInfo.txt and TbsmObjectCache.properties, contain
private cache parameters for the adapter driver and are not used for
configuration.
562 Integrating IBM Tivoli Workload Scheduler with Tivoli Products
10.4.1 AdapterEnv.conf
This configuration file contains environment variables that are used by the
adapter driver. You need to update the host name parameter with the short name
of the TWS server, without the domain name. The maximum length of the
resource name (which includes the host name) is 54 characters. Figure 10-4
shows the Enterprise ITSO_Redbook_Project with events from server milan
under it. Example 10-1 shows the updated AdapterEnv.conf file.
Figure 10-4 ITSO_Redbook_Project Enterprise and the milan Batch Schedule Set
Example 10-1 AdapterEnv.conf
[Adapter Env]
ipnw_name_default=UNKNOWN
sep=$(space)
term=~
singlequote=_
prefix=W
Hostname=milan
TWSInstance=m82
...
Chapter 10. Integrating Tivoli Business Systems Manager 563
10.4.2 DriverPlugIns.conf
The DriverPlugIns.conf file contains the configuration for the interfaces that the
driver implements. The Enterprise parameter in this file requires the Enterprise
name under which you would like the batch schedule sets and their resources to
be displayed on the TBSM physical hierarchy. Normally, it is the only setting that
needs to be changed in this configuration file. Figure 10-4 on page 562 shows
the Enterprise ITSO_Redbook_Project with events arriving from server milan.
Example 10-2 shows the updated DriverPlugIns.conf file.
Example 10-2 DriverPlugins.conf
[PLUG IN]
PluginName=TWS
CycleTime=120
MaxSecBack=-1
Enterprise=ITSO_Redbook_Project
#C1=---- COLLECTOR DATA ----
CollectorMode=inline
CollectorClassPath=.
CollectorClassName=com.ibm.tbsmadapter.TWSCollector
#C2=---- TOKENIZER DATA ----
TokenizerMode=inline
TokenizerClassPath=.
TokenizerClassName=com.ibm.tbsmadapter.TWSTokenizer
#C3=---- RECOGNIZER DATA ----
RecognitionMode=inline
RecognitionClassPath=.
RecognitionClassName=com.ibm.tbsmadapter.DefaultRecognizer
10.4.3 DB_Server.conf
The DB_Server.conf contains configuration settings that need to connect to the
TBSM database (via JDBC) where the rules are located. Update all of the
appropriate parameters with the information that is required to access the TBSM
SQL server (such as user ID, password, and SQL server name.). The user sa or
equivalent should be the user ID that you enter in this file. Example 10-3 shows
the DB_Server.conf file.
Example 10-3 DB_Server.conf
[ADAPTER DRIVER]
Server=tokyo
User=sa
Password=xyzzy
JdbcUrl=jdbc:microsoft:sqlserver://
JdbcClass=com.microsoft.jdbc.sqlserver.SQLServerDriver
564 Integrating IBM Tivoli Workload Scheduler with Tivoli Products
Update the JdbcUrl and JdbcClass parameters with the appropriate JDBC
information as shown in Example 10-4. The default values point to the default
settings for the Microsoft JDBC driver.
Example 10-4 JDBC URL/Class Parameters
JdbcUrl=jdbc:microsoft:sqlserver://
JdbcClass=com.microsoft.jdbc.sqlserver.SQLServerDriver
10.4.4 localadapter.config
The localadapter.config files contains data (such as host names) that are related
to the TWS machine on which the adapter is running and the host name of the
TBSM Common Listener server.
To configure your adapter to communicate with the TBSM Common Listener,
make the following changes to localadapter.config:
򐂰 Replace localhost in the transport base properties lines with the local
host name or IP address of the system that contains the adapter. In our
example, Example 10-5 on page 565, the name is milan. You should also
change the following fields in this section:
transport.local.ip.address
transport.request.address
transport.response.address
򐂰 Replace localhost in the MQe transport properties section with the IP
address or local host name of the system where the TBSM Common Listener
is running. In our example, Figure 10-5 on page 565, the name is phoenix.
Note: Because the file contains the database the user ID and password, it
should be encrypted with the following command on UNIX systems:
./bin/DBServerEncryptor.sh
Use the following command for Windows systems:
.\bin\DBServerEncryptor.bat
The command generates a file called _DB_Server.conf. The original file
DB_Server.conf can be safely deleted when the command completes.
Important: Update the host name parameters in the localadapter.config file
with the short host name (without the domain name) or the dotted-decimal IP
address only. Ensure that you place the correct host name (adapter or
common listener system) in each field.

Get Integrating IBM Tivoli Workload Scheduler with Tivoli Products now with O’Reilly online learning.

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