Mapping customized field names
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
IDENTIFIERID instead of the default
IDENTIFIER, you must perform this task. You
create a database view and map back to the actual field names.
About this task
To map customized columns in your Historical Event Database, complete the following steps.
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_STD. The data types for Db2 are
SE_HISTORICALEVENTS_Db2under ObjectServerHistoryDb2ForNOI data source.
RELATEDEVENTS.RE_MAPPINGSrecords 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
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 (
- Save the Event Analytics configuration. You can now use the mapped fields for Event Analytics.