1. Developer's Guide
  2. Integrating BRM with Enterprise Applications
  3. Building a Connector Application

31 Building a Connector Application

Learn how to set up enterprise applications to access Oracle Communications Billing and Revenue Management (BRM) event data by using a connector application for Enterprise Application Integration (EAI) Manager.

Topics in this document:

Building a Connector Application

To provide access to BRM event data for enterprise applications, you need to build a module connector application that handles transaction management and transformation schemes specific to your environment.

The EAI DM calls the functions listed in Table 31-1 when it starts, processes event data, and shuts down. You must implement these functions in your connector application.

Table 31-1 Functions Called by EAI Data Manager

Function Description

AbortTransaction

Called by the EAI DM after the transaction is cancelled in BRM.

CommitTransaction

Called by the EAI DM after BRM commits the transaction to its database.

FreeGlobalContext

Called when the EAI DM process is shutting down.

GetGlobalContext

Called from a connector application to access the context initialized with InitializeGlobalContext.

Initialize

Called by the EAI DM when it starts.

OpenTransaction

Called by the EAI DM before it calls PublishEvent.

PrepareCommit

Called by the EAI DM when BRM is about to commit the transaction to the database.

PublishEvent

Called by the EAI DM when there is a business event to be published.

SetIdentifier

Called from the connector application to set a return identifier for a published business event.

Shutdown

Called by the EAI DM when it shuts down.

The plugin_flist.c and plugin_xml.c files in the BRM_home/sys/dm_eai directory provide sample implementations of the EAI functions in flist and XML format.

After you build your connector application, configure EAI Manager. See "Configuring EAI Manager".