7 Integrating with Oracle Business Activity Monitoring

Oracle Communications Marketing and Advertising can be set up to deliver real-time event data to Oracle Business and Activity Monitoring (BAM).

Overview

Marketing and Advertising servers continuously record basic information about their status through an internal event mechanism. An event is fired at designated times as the server functions, for example, whenever a request crosses module boundaries, specific methods are called, or exceptions are thrown. This event information is sent to the EDR Service, where it is processed using an XML-based filter, which separates them into types. The filters can also be used to transform the data in the original event, including adding other useful information.

Out of the box, there are three filters that produce three distinct types of data: Event Data Records, Charging Data Records, and Alarms. When the information has been processed by the filters, it is delivered to type-specific listeners. To communicate with Oracle BAM, Marketing and Advertising delivers a special version of the Charging Data Record modified for this purpose to an internal EDR listener which then publishes it to a JMS topic on a JMS server accessible to both it and Oracle BAM. These records describe both "Ad Served" and "Ad Impression" events. See Figure 7-1.

Figure 7-1 Publishing to JMS Topic

Description of "Figure 7-1 Publishing to JMS Topic"

Both Marketing and Advertising and Oracle BAM must be configured to communicate with this JMS server. These instructions cover only the Marketing and Advertising part of the process.

Configuring the Connection

Setting up Marketing and Advertising for delivering event information is done using the Administration console. For complete information see the BAM section of "Configuring the Web Application" in System Administrator's Guide, another document in this set.

Note:

The JMS topic JNDI name and JMS Connection Factory JNDI name values entered for the Marketing and Advertising and the Oracle BAM configurations must be identical.

JMS Message Content

Messages delivered to the JMS topic are of type javax.jmsTextMessage and are enclosed in a <MultiMessage> element with individual messages enclosed in a <PRE> element. Each individual message corresponds to a single Ad Impression or Ad Served event and is organized as key/value pairs:

<key1>value1</key1><key2>value2</key2>...<keyn>valuen</keyn>

The following information is sent:

Timestamp: The time of the event, as recorded on the Marketing and Advertising server, presented as a localized version of a Java Date
Campaign Id: The internal ID for the campaign in the system
Campaign Name: The name given the campaign when it was initiated
Advertiser Id: The internal ID for the Advertiser organization that initiated the campaign
Service Provider Id: The internal ID for the Ad Service Provider organization that is responsible for the Advertiser organization that initiated the campaign
Network Provider Id: The internal ID for the Network Provider organization that is responsible for the Connection Configuration used by the campaign
Price: The price paid for the message, in currency defined by the Marketing and Advertising server
Event Type: An enumeration. Either "Ad Served" or "Ad Impression". An "Ad Served" indicates that the message has been successfully delivered to the underlying network. An "Ad Impression" indicates that a Delivery Notification concerning the message has been received back from the underlying network
Category List: The types used to define demographic categories used to send bulk messages. The types depend on configuration, but could include such things as Age, Gender, and so forth
Subscriber List: The address of the subscriber who received the message
Delivery Notification Enabled: A boolean, indicates if Delivery Notification is enabled for this campaign