To enable the BMC Impact Integration Web Services server to receive events from a BMC Impact Manager cell and pass the events on to a subscribing client, you must perform one of the following:
The Propagate rule or event propagation policy specifies that the BMC Impact Manager cell propagates events to the IIWSGatewayServer event listener residing on the BMC Impact Integration Web Services server.
For example, if one IIWSGatewayServer event listener is receiving events from three BMC Impact Manager cells, then each instance must specify a Propagate rule or an event propagation policy.
For more information about event propagation rules, see Propagate rules.
The following figure depicts three BMC Impact Manager cells that are sending events to the IIWSGatewayServer event listener. You define a Propagate rule or an event propagation policy for each instance, specifying the IIWSGatewayServer event listener as the destination of the event.
Event propagation: many instances to one server
If multiple IIWSGatewayServer listeners are receiving events from multiple Impact Manager cells, then for each IIWSGatewayServer listener, you add a Propagate rule or specify an event propagation policy. The following figure depicts this example:
Event propagation: many instances to many servers
In the preceding figure, two BMC Impact Integration Web Services servers, Zebra and Giraffe, receive events from three BMC Impact Manager cells. Each cell must have a Propagate rule or an event propagation policy that specifies the IIWSGatewayServer event listener or listeners that receive the events. In this example, each cell has to define a rule or policy for both servers.
Tip
When defining your Propagate rule or event propagation policy, ensure that you specify the name of the IIWSGatewayServer entry exactly as it is defined in the mcell.dir file.
This section describes sample Propagate rules and describes how to manually add a Propagate rule to the cell's KB. For information about creating an event propagation policy or about Propagate rules, see Propagate rules.
The following is an example of how you could write a Propagate rule that would propagate each event:
propagate to_IIWSGatewayServer: EVENT ($EV) to IIWSGatewayServer END
If you are using the same selector criteria and sending the same events to multiple BMC Impact Integration Web Services servers (multiple IIWSGatewayServer entries IIWSGatewayServer1 and IIWSGatewayServer2, for example), then your Propagate rule could look like the following example:
propagate to_IIWSGatewayServer: EVENT ($EV) to_all IIWSGatewayServer1, IIWSGatewayServer2 END
If you are using different selector criteria to send different events to each BMC Impact Integration Web Services server, then you would write a different Propagate rule for each IIWSGatewayServer. If you are sending different events to IIWSGatewayServer1 and IIWSGatewayServer2, your Propagate rules could look like the following example:
propagate to_IIWSGatewayServer1: EVENT ($EV) to IIWSGatewayServer1 END propagate to_IIWSGatewayServer2: EVENT ($EV) to IIWSGatewayServer2 END
You can add any valid Propagate rule to the KB of a BMC Impact Manager cell to propagate events to the BMC Impact Integration Web Services server.
The task of creating a Propagate rule includes the following procedures that you must perform in the order presented:
Add the new Propagate rule syntax to the file.
You can give the file any name and include comments. Your file would look similar to the following example.
#------------------------------------------------------------- #Impact Manager #Copyright 1998-2007 BMC Software, Inc. All rights reserved. #Filename : mc_IIWSGatewayServer.mrl #------------------------------------------------------------- # This rule propagates events to the IIWSGatewayServer residing on the # BMC Impact Integration Web Services server. # propagate to_IIWSGatewayServer: EVENT ($EV) to IIWSGatewayServer END
Note
You can add to the KB of the BMC Impact Manager cell any valid Propagate rule that propagates events to the IIWSGatewayServer.
mccomp manifest.kb
On Microsoft Windows:
NET STOP mcell_
cellName
NET START mcell_
cellName
On Linux or Solaris:
mkill -n
cellName
mcell -n
cellName