216 Tivoli Business Systems Manager Version 2.1: End-to-End Business Impact Management
11.Select the Log On tab, as shown in Figure 7-6.
Figure 7-6 Tivoli BSM Event Enablement Properties window
12.Select This account and enter the user ID and password that you created in
step 4.
13.Repeat steps 10 through 12 for the Tivoli BSM Task Server service.
The task server runs tasks within the Tivoli Management Framework; therefore,
the user ID that we have chosen within Windows to run the Task Server must be
associated with a Tivoli administrator on the Tivoli Management Framework.
1. Open a Tivoli desktop and select Administrators as per Figure 7-7 on
page 217. Right-click Administrators and select Open.
Chapter 7. TEC components integration 217
Figure 7-7 TME Desktop of Administrator window
2. Right-click the icon for the selected administrator. Select Edit Logins.
3. Type the login name you are using to run the task server.
4. Press enter. The new user ID should appear under Current Login Names.
5. Click Change & Close.
7.2.3 Updating the TEC event classes and rules
In order for TEC to understand which events to forward to IBM Tivoli Business
Systems Manager, we must make some modifications to the rulebase and event
classes. A script has been provided during installation that will do most of the
work for you. If the new rules cause problems in your environment, you can
modify and add each one of the classes and rulebases manually.
218 Tivoli Business Systems Manager Version 2.1: End-to-End Business Impact Management
The script used to configure TEC is called ihsttec.sh and it is found on the Tivoli
Enterprise Console server machine in the %BINDIR%TDSEventService
directory. We ran the script, and an excerpt from the result is shown in
Example 7-1.
Example 7-1 Output from running ihsttec.sh
C:Tivoliinw32-ix86TDSEventService>bash
bash$ ./ihsttec.sh
###########################################################
Creating GemEvent rules data base.
ATTENTION:
If you are installing multiple TMRs, have you updated
this file to include the defaults for your
Topology Server?
Input Rules Base Name?
Output Rules Base Name?
Routing rules?
The file name is C:/Tivoli/bin/w32-ix86/TDS/EventService/ihsttec.sh
If you have not done so, please terminate now and reexecute.
###########################################################
Press Enter to continue or "q" to quit.
Will this copy of Event Enablement forward events to
Global Enterprise Manager (GEM)?
Enter 'Y' if GEM will be used.
Enter 'N' if GEM will not be used.
The default is: N
n
Please enter the name of the TEC Rules Base to copy
as a starting point for creating the GemEvent rules base.
If no name is entered we will use the name: Default
NewDefault
Do you want this TEC to forward APM events to Event Enablement?
Enter 'Y' to forward events.
Enter 'N' to not forward events.
The default is: N
y
Should TEC status changes (ACK, RESPONSE, CLOSED) associated
with APM Threshold events be sent to TBSM?
If no is specified, then APM Threshold events will be
automatically closed in TEC when they are received.
Enter 'Y' send status events to TBSM.
Enter 'N' to not send status event to TBSM.
Chapter 7. TEC components integration 219
The default is: Y
y
Do you want this TEC to forward DM monitors to Event Enablement?
Enter 'Y' to import the ihstdmon.rls file.
Enter 'N' to not import the ihstdmon.rls file.
The default is: N
y
Does your TEC receive OS/390 events from TBSM using the
TEC EIF interface?
Enter 'Y' if this feature is configured.
Enter 'N' if this feature is not used..
The default is: N
n
Do your DM profiles include NT Monitoring Collections?
Enter 'Y' if the do.
Enter 'N' if they do not.
The default is: N
y
--> Does NewDefault contain a partial collection of
--> NT Monitoring Collection classes?
--> Enter 'Y' if you want any missing NT classes added to GemEvent.
--> Enter 'N' if you do not want any missing NT classes added to GemEvent.
--> The default is: N
y
Do your DM profiles include Windows/2000 Monitoring Collections?
Enter 'Y' if the do.
Enter 'N' if they do not.
The default is: N
y
--> Does NewDefault contain a partial collection of
--> Windows/2000 Monitoring Collection classes?
--> Enter 'Y' if you want any missing Windows/2000 classes added to GemEvent.
--> Enter 'N' if you do not want any missing Windows/2000 classes added to
GemEv
ent.
--> The default is: N
y
Do your DM profiles include OS/2® Monitoring Collections?
Enter 'Y' if the do.
Enter 'N' if they do not.
The default is: N
n
220 Tivoli Business Systems Manager Version 2.1: End-to-End Business Impact Management
Do your DM profiles include UNIX Monitoring Collections?
Enter 'Y' if the do.
Enter 'N' if they do not.
The default is: N
Do your DM profiles include Univeral Monitoring Collections?
Enter 'Y' if the do.
Enter 'N' if they do not.
The default is: N
n
Do your DM profiles include OS/400® Monitoring Collections?
Enter 'Y' if the do.
Enter 'N' if they do not.
The default is: N
n
Create the GemEvent Rules Base
Checking to see if GemEvent exists
Rule Base Name
--------------
We have not included the entire output from the running of this script because of
its length and the repetitive nature of loading class files. However, it can be seen
that this script creates a new rulebase called GemEvent by copying the rules and
classes from a specified rulebase (in our case it was called NewDefault) using
the options that we selected. We also have a profile called ClassicSentryProfile,
which contains classic DM monitors that forward events to IBM Tivoli Business
Systems Manager. This script’s completion results in the new rule base called
GemEvent, shown in Figure 7-8 on page 221.
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.