Any customized field names in the Historical Event Database must be mapped to the
corresponding standard field names in Netcool®/Impact. You do
this by creating a database view to map to the standard field names.
Before you begin
You must perform this task if you have customized table columns in your Historical Event Database. For example, if you have defined
columns called SUMMARYTXT and IDENTIFIERID instead of the default
names SUMMARY and IDENTIFIER, you must perform this task. You
create a database view and map back to the actual field names.
About this task
The steps documented here are for a Db2® database. The procedure is similar for an Oracle database. To map customized columns in your Historical Event Database, complete the following
steps.
Procedure
-
Use the following statement to create the view and point the data types to the new view.
DROP VIEW REPORTER_STATUS_STD;
CREATE VIEW REPORTER_STATUS_STD AS SELECT SUMMARYTXT AS SUMMARY, IDENTIFIERID AS IDENTIFIER, * FROM REPORTER_STATUS;
-
Change the data types from
REPORTER_STATUS to
REPORTER_STATUS_STD. The data types for Db2 are AlertsHistoryDb2Table and SE_HISTORICALEVENTS_Db2 under
ObjectServerHistoryDb2ForNOI data source.
-
Delete
RELATEDEVENTS.RE_MAPPINGS records from the table:
DELETE FROM RELATEDEVENTS.RE_MAPPINGS WHERE TRUE;
-
Run the Event
Analytics
Configuration wizard to configure the Netcool/Impact properties to use for Event
Analytics.
-
On the Historical event database configuration screen, connect to the
database and then select the REPORTER_STATUS_STD (view) from the
History table drop-down menu as the Table name for
Event
Analytics.
-
When using any other columns that were mapped in the view, for example
Summary
for SUMMARYTXT, use the new value in any of the wizard screens. In this case use
Summary.
For example, when adding fields to the report in the Configure report
fields screen, use the values mapped in the view (Identifier or
Summary).
-
Save the Event
Analytics
configuration. You can now use the mapped fields for Event
Analytics.