Messages related to events

The ObjectServer sends events to the BMC Remedy Action Request System. You can see these events in a log file using DEBUG mode.

Overview

The Java Gateway for BMC Remedy ARS uses the mapping file, bmc_remedy.map, to determine how to map fields in ObjectServer tables to fields in a BMC Remedy ARS request. The bmc_remedy.map file contains a number of CREATE MAPPING commands each of which maps specific ObjectServer table fields to fields in a BMC Remedy ARS request.

SeeMapping for more information on mapping and the bmc_remedy.map file.

Setting the level of debug messages

Use the MessageLevel property to specify the reporting level for gateway log file messages. Use the MessageLog property to specify the location of the gateway message log file.

See the IBM Tivoli Netcool/OMNIbus Probe and Gateway Guide for more information on these properties.

Example log file containing debug messages related to events (BMC Remedy ARS field ID numbers)

The following example shows a sample log file that contains debug messages related to the events that the ObjectServer sends to BMC Remedy ARS. These debug messages are the result of the gateway using the bmc_remedy.map file to map specific ObjectServer table fields to fields in a BMC Remedy ARS request. This example shows the debug messages with the BMC Remedy ARS ID numbers.

The numbers that follow provide explanations of specific lines of the sample log file:

14/09/01 10:20:14: Debug: [Request consumer 1] Calling createEntry for alert  1 
14/09/01 10:20:14: Debug: [Request consumer 1] SOGValues :  2 
536870914=LondonMachineMon4Systems;  3 
536870913=5510;  4 
536870944=London;
536870915=;
536870932=Simnet Probe;
536870939=MachineMon;
536870918=Systems;
536870931=;7=4;
536870916=Machine has gone offline;
536870946=1409563197;
536870912=1409563197;
536870917=1409563197;
536870935=1409563197;536870938=0;
536870941=0;536870940=1;
536870945=3300;
536870942=0;
536870934=;
536870933=0;
536870922=5510;
536870923=RAVINE;
  1. This debug message indicates that the gateway called the createEntry method, which creates a new entry in the specified BMC Remedy ARS form on the specified BMC Remedy ARS server.
    Note: The createEntry method is part of the AR System API.
  2. This debug message indicates that the values that follow are the Simple OMNIbus Gateway (SOG) values associated with BMC Remedy ARS fields in the request. Specifically, the StatusMap, defined in bmc_remedy.map, is the main map for alerts.status entries. The StatusMap maps Tivoli Netcool/OMNIbus alert fields to their corresponding BMC Remedy ARS fields.

    See Mapping for more information on the StatusMap.

  3. The 536870914 BMC Remedy ARS field maps to the ObjectServer table field called @Identifier (as defined in the StatusMap in the bmc_remedy.map file). In this alert example, the SOG value for this field is LondonMachineMon4Systems.
    Note: It is not possible to know that the 536870914 BMC Remedy ARS field maps to the ObjectServer table field called @Identifier just by looking at the debug messages. However, it is possible to make the appropriate mapping between the fields by checking the StatusMap in the bmc_remedy.map file.
  4. The 536870913 BMC Remedy ARS field maps to the ObjectServer table field called @Serial (as defined in the StatusMap in the bmc_remedy.map file). In this alert example, the SOG value for this field is 5510.
    Note: It is not possible to know that the 536870913 BMC Remedy ARS field maps to the ObjectServer table field called @Serial just by looking at the debug messages. However, it is possible to make the appropriate mapping between the fields by checking the StatusMap in the bmc_remedy.map file.

Example log file containing debug messages related to events (BMC Remedy ARS field names)

The following example shows a sample log file that contains debug messages related to the events that the ObjectServer sends to BMC Remedy ARS. These debug messages are the result of the gateway using the bmc_remedy.map file to map specific ObjectServer table fields to fields in a BMC Remedy ARS request. This example shows the debug messages with the BMC Remedy ARS field names (as defined in the omnibus.def file) instead of the BMC Remedy ARS field ID numbers as in the previous example.

The numbers that follow provide explanations of specific lines of the sample log file:

14/09/16 13:12:14: Debug: [Request consumer 2] Entry contents :  1 
Identifier=TokyoMachineStats4Stats;  2 
Serial=957;  3 
Node=Tokyo;
Node Alias=;
Manager=Simnet Probe;
Agent=MachineStats;
Alert Group=Stats;
Alert Key=99% full;
Status=4;
Summary=Diskspace alert;
State Change=1410859573;
FirstOccurance=1410451826;
LastOccurance=1410859573;
InternalLast=1410859573;
Poll=0;
Type=0;
Tally=13710;
Class=3300;
Grade=0;
Location=;
Acknowledged=0;
ServerSerial=957;
ServerName=NCOMS;
  1. This debug message indicates that the values that follow are the Simple OMNIbus Gateway (SOG) values associated with BMC Remedy ARS fields in the request. Specifically, the StatusMap, defined in bmc_remedy.map, is the main map for alerts.status entries. The StatusMap maps Tivoli Netcool/OMNIbus alert fields to their corresponding BMC Remedy ARS fields.

    See Mapping for more information on the StatusMap.

  2. The Identifier BMC Remedy ARS field maps to the ObjectServer table field called @Identifier (as defined in the StatusMap in the bmc_remedy.map file). In this alert example, the SOG value for this field is TokyoMachineStats4Stats.
    Note: It is not possible to know that the Identifier BMC Remedy ARS field maps to the ObjectServer table field called @Identifier just by looking at the log messages. However, it is possible to make the appropriate mapping between the fields by checking the StatusMap in the bmc_remedy.map file.
  3. The Serial BMC Remedy ARS field maps to the ObjectServer table field called @Serial (as defined in the StatusMap in the bmc_remedy.map file). In this alert example, the SOG value for this field is 957.
    Note: It is not possible to know that the Serial BMC Remedy ARS field maps to the ObjectServer table field called @Serial just by looking at the log messages. However, it is possible to make the appropriate mapping between the fields by checking the StatusMap in the bmc_remedy.map file.