4.1 Creating an Event Manager Adapter

Create only one Event Manager adapter on each machine.

For information about the Experience Manager adapter properties, see Creating an Event Manager Adapter in the Operations Center 5.6 Event Manager Guide.

To create an Event Manager adapter:

  1. In the Explorer pane, expand the Administration root element.

  2. Right-click Adapters, then select Create Adapter to open the Create Adapter dialog box:

  3. Click the Type drop-down list, then select Event Manager.

    A default name of the Event Manager adapter (Adapter: Operations Center Event Manager™) displays in the Name field. Default adapter properties specific to the Event Manager display in the Properties table.

  4. In the Name field, replace the default name with one that defines your system.

  5. Enter values for the Event Manager properties in the Properties table:

    AddAgentElements: If True, all Event Manager agents (EMS) appear in the hierarchy and never time out. If False, the EMS agents appear only when they are generated via alarms and they time out like an ordinary alarm.

    AgeOutTime: If there are no open alarms, and the element’s condition hasn’t changed in the last n seconds, and the element has no children, then the element disappears from the display after the specified time (where n is the number of seconds). If another alarm is generated for this element, the element reappears. The default is 300.

    • AgeOutTime < 0: Never age out.

    • AgeOutTime = 0: Age out immediately.

    • AgeOutTime > 0: Age out after specified time expires.

    AlarmColumns: A comma-separated list that determines which alarm columns display and the order that the alarm items (date and time, rule, and so on) display in the Alarms view. The default is:


    For Alarm column aliasing you can assign new names to alarm columns using the format:


    For example, Class=Rule displays rule data in a column named Class.

    A list of all the possible Event Manager AlarmColumns: Number, AssignedTo, Class, Description, EnRouteTo, Group, InitDateTime, Priority, Rule, and SuppressAutomations.

    AutomationsOnReload: This property is only meaningful if Event Manager Alarm Persistence is enabled. This adapter property configures the behavior of reloaded alarms regarding the Alarm Create type of event automations.

    When the Event Manager Alarm server starts up, it marks alarms read in from the persistent alarm store as “reloaded.”

    If True, reloaded alarms fire Alarm Create type of event automations. The default is False.

    HierarchyFile: A file in the /OperationsCenter_install_path/database/ directory that contains an XML description of the hierarchy of elements that is built beneath the element that represents the adapter. The default is examples/EveHierarchy.xml.

    Before modifying the hierarchy file, copy the example file to the /OperationsCenter_install_path/database directory and change the location reference. This protects changes from being overwritten during software updates. For information, see Using the HierarchyFile in the Operations Center 5.6 Adapter and Integration Guide.

    NonClearableRules: A comma-separated list of rule names. No users are allowed to close an alarm generated by one of the named rules. This is desirable for certain classes of alarms that the system creates and destroys, and in cases where allowing users to close alarms is undesirable.

    Script.onError: Enter a script that executes if the adapter fails for any reason. The script can print the reason for the failure as a “msg”; for example:


    Script.onInitialized: A script that executes when the adapter first initializes. All the Script.nnn properties are optional.

    Script.onStarted: A script that executes when the adapter starts, either manually or automatically when the Operations Center server starts.

    Script.onStopped: A script that executes after manually stopping the adapter.

    Server: The hostname of the server where the management software is installed. The default is com.mosol.ORB.Eve.AlarmServer.

    StylesheetFile: The stylesheet file to apply against the HierarchyFile as a style markup and produce the final output. It is located in the /OperationsCenter_install_path/database directory.

    UseAlarmTimesForCondition: Specifies the date and time stamp to use for any alarm data stored by the data warehouse. If True (the default), the date and time information originates directly from the alarm information. If False, the date and time is when the Operations Center server received the alarm.

  6. Click Create.

  7. To start the adapter whenever the Operations Center server starts, leave the Start Adapter Automatically check box selected.

  8. Click Start in the Commands section to start the adapter.

    After the adapter starts, the Close button becomes available.

  9. Click Close to close and exit the dialog box.

    The new adapter displays in the list of elements in the Explorer pane, under Administration > Adapters.