416 Tivoli Business Systems Manager Version 2.1: End-to-End Business Impact Management
cannot automatically convert certain values of the GEM_InstFiltering columns.
Table 12-1 shows the values not supported by the migration script.
Table 12-1 Distributed rules not supported by the migration script
The preceding values represent distributed rules that must be added manually
into the ABS engine.
The migration process we followed consists of these steps:
1. Convert the distributed rules to the Automatic Business System format using
the migrateToAbs.ksh script.
2. Manually add the distributed rules that are not supported to the output file
generated by the preceeding step.
3. Load the modified output file into the database with the absConfig.ksh script.
4. Disable the distributed rules, setting the enable_gem_auto_lob parameter to
no in the GEM_Options table.
The migrateToAbs.ksh command syntax is explained in detail in the
Business Systems Manager: Administrator’s Guide
, GC32-0799. This script calls
GEM_InstFiltering column Value
memTest when = 0
or more then one symbol
exclusive when <> 0
priority when <> 0
Note: The GEM_InstFiltering table is preloaded with all the filtering definitions
for all the default IBM Tivoli Business Systems Manager class IDs from G000
to G02C. The migration process takes in all the data stored in that table, so the
migration output file would contain a filtering criteria for each class
represented in the table.
In our example we have deleted all the rows of the GEM_InstFiltering table
other than those representing the filtering criteria that we inserted with the
addpvToLOB.sh command. Now our output file contains just the criteria for the
classes we are interested in putting into our BSV. This selection could be also
done within the output file itself to eliminate each section’s unneeded criteria.