BMC Event Adapters MAP files

This section contains detailed information about the map files that BMC Event Adapters use and the structure of these map files.

Defining the BMC Event Adapters MAP files

When an event is read by an adapter, the adapter must convert the event from its internal representation, such as a Perl hash, into the cell-compatible format, the BAROC language. The structure of the conversion is controlled by a special configuration file, the MAP file. Each adapter uses its own MAP file to produce cell events.

BAROC classes for adapters are defined in the mcxa.baroc file, which is installed in the default Knowledge Base of each cell Event Processor. The adapters create a copy of this file in the installationDirectory\pw\server\etc directory. This file also contains classes for standard events sent by msend and mposter.

Default MAP files

Location of MAP files on various platforms is as follows:

• On UNIX platforms, MAP files are located in the installationDirectory/pw/server/etc directory.
• On Windows platforms, MAP files are located in the installationDirectory\pw\server\etc directory.

The following table lists the default names for the MAP files of the different BMC Event Adapters.

Default MAP files

Custom maps and map-related files

If you want to expand the map functionality beyond that offered by the default maps, you can create custom map files that produce the event formats that you require.

To use a MAP file other than the default, specify the path and name of the map file as the value of the MapFile parameter in the adapter specification in the mcxa.conf file. For example:

MapFile = mymap.map

MAP file structure

The structure of a MAP file is line-oriented. Each line can be one of the six (6) types of recognized statements:

• A comment
• A define statement
• An input variables statement
• An initialization statement
• A default class statement
• A class statement