Using the BMC TrueSight Opearations Manager actor adapter
The actor adapter for BMC ProactiveNet Performance Management performs the following operations on BMC Service Impact Management (BMC SIM) cells:
- Creates, updates, retrieves, and annotates events
- Enables and disables the maintenance mode
The adapter operations target BMC ProactiveNet Performance Management cells.
Each request to the adapter starts a sequence of requests and responses between the adapter and BMC ProactiveNet Performance Management. When an adapter receives a request, the following sequence occurs:
- The adapter looks up the IP address of the host cell in the mcell.dir file local to the TrueSight Orchestration peer. For details about the mcell.dir file, see #Communicating with a BMC ProactiveNet Performance Management cell.
- The adapter opens a client connection to the cell specified in the request or the default cell specified in the adapter configuration.
- The adapter registers itself with the server by issuing a register request.
- The BMC Impact Administration Server acknowledges the registration request. The adapter receives the acknowledgment asynchronously when the underlying API invokes the processAnswer() callback method.
- The adapter sends the actual query request to the server. The server returns the response to the query with the processAnswer() callback method.
- The adapter sends additional requests and operations if required, and the server returns the responses to these requests with the same processAnswer() callback method.
- The adapter closes and unregisters requests. The BMC ProactiveNet Performance Management server acknowledges these requests.
- The adapter closes the client connection.
- The adapter collates all the responses from the server and returns the adapter response to the caller.
- Adapter requests can target different BMC ProactiveNet Performance Management cells. The adapter creates and closes a new connection for each request.
The adapter converts the requests into Basic Recorder of Objects in C (BAROC) formatted queries that a BMC ProactiveNet Performance Management cell understands.
The BAROC format is a proprietary BMC ProactiveNet Performance Management query language.
Communicating with a BMC ProactiveNet Performance Management cell
To communicate with a BMC ProactiveNet Performance Management cell, the adapter's underlying APIs, IMAP, and IMCOMM API require access to the mcell.dir file. The mcell.dir file for the BMC Event Management application is located at installHome\pw\server\etc in the BMC Impact Administration Server installation directory.
You can use the mcell.dir file on the application (BMC ProactiveNet Performance Management) side as a reference to create or copy the mcell.dir file required by TrueSight Orchestration, which is then placed on the TrueSight Orchestration peer on which the adapter is enabled. The path to access this local file must be present in the adapter configuration.
The mcell.dir file contains the following cell definitions:
- cell name
- encryption key
The host2 and port2 fields in the mcell.dir file are used in high-availability setups for specifying secondary cells.
If the cell name changes on the application (BMC ProactiveNet Performance Management) side, you must make corresponding changes in the mcell.dir file in BEM and the copy of the mcell.dir file that is local to the TrueSight Orchestration peer to ensure that the actor adapter continues to communicate with the cell.
You must disable and re-enable the adapter after the changes are made to the mcell.dir file local to the TrueSight Orchestration peer.
In case you also use the monitor adapter and change the cell name on the application (BMC ProactiveNet Performance Management) side, you must set up event monitoring for the new cell again as described in Setting up events for the TrueSight Orchestration Monitor Adapter for BMC ProactiveNet Performance Management.