Configuring the SIM Notification Registry parameters in the cell

To create or modify the notification events, you can create a new or edit an existing Notification Registry Internal instance in the cell. You can specify the notification events to search for and also specify the clients to forward the events. You can also delete an instance of the Notification Registry Internal.

You can configure a Notification Registry Internal instance in the cell using the Administrator console of TrueSight Infrastructure Management.

To configure the Notification Registry Internal parameters

1. Open the Administrator console of the Infrastructure Management Server.
2. On the Administration tab, click Dynamic Data Editor tab.
3. Select the cell for which you want to create or edit or delete a  Notification Registry Internal instance.
4. Navigate to Data > Cell Data, and click Notification Registry Internal as shown in the following image:
   
5. Right-click and select:
   1. New if you want to create a new Notification Registry Internal instance in the cell.
   2. Edit to modify an existing Notification Registry Internal instance in the cell.
   3. Delete to delete an existing Notification Registry Internal instance in the cell.

6. If you are creating a new instance or editing an instance, refer the following table to set the registry parameters of the Notification Registry Internal instance.

   Parameter	Description
   Client Data	Allows you to define a rule set for the SIM notification events that your client is registered to receive. For example, if you set this parameter to IBRSD, the rule could search for the text IBRSD in the client_data field to determine whether it is a state change requested by IBRSD.
   Clients	A comma-separated list of clients where the notification must be sent. The clients in the list must be defined in mcell.dir. By default, the cell name is listed as the client in mcell.dir. Do not change the mcell.dir file if you are sending events internally.
   Requested Notifications	A comma-separated list of SIM notification events for which notification is requested: COMPONENT_CHANGE COMPONENT_DELETE COMPONENT_OVERWRITE RELATIONSHIP_CHANGE RELATIONSHIP_DELETE
   Notification Mode	Specifies how the slot values that have not changed are reported in the SIM notification event. This parameter can be set to one of the following values: DELTA: The slots whose values do not change are reported with their default values, not their current values. The default value is an empty string for symbolic values and -1 for numeric values. See the .baroc class definition of the SIM notification event for the default slot values. FULL: The current values of all slots are reported, including those that have not changed.
   Notifications at Registration	Instructs the cell whether to send the current component state at the moment of registration. This parameter can be set to one of the following values: YES: Instructs the cell to send the current component state at the moment of registration. NO: Instructs the cell not to send the current component state at the moment of registration.
   Asset Filter	Specify a class name. The state change notifications are generated only for the configuration items of the specified class or a subclass.
   Causal Event Notification Mode
   Impact Status Propagation	This parameter can be set to one of the following values: YES: Ensures that all causes of the status change notifications are sent to the client. NO: Ensures that only the cause that triggered the specified status change notification is sent to the client.
   Severity Notification Mode	Important Information This parameter is supported only if you have installed TrueSight Infrastructure Management server 11.3.02 or later versions. This parameter can be set to one of the following values: YES: Additional incident events are created whenever the Severity value changes. NO: This ensures that additional incident events are not created whenever the Severity value changes. Note: Additional incident events are created when there is a transition from higher severity to lower severity, even though the IBRSD policy rules do not match the severity criteria. For example, if the policy rule states that an incident should be created when the severity status is Critical, additional incidents are being created when the severity transitions from Critical to Major, Major to Minor etc.

7. Click OK to save the changes.

Related topics

Out-of-the-box event management policies