|Oracle® Communications Marketing and Advertising System Administrator's Guide
Part Number E20558-01
This chapter describes how to manage and configure container services used by Oracle Communications Marketing and Advertising.
Container services are specialized extensions of the basic Oracle WebLogic Server container functionality that have been added to support network traffic managing and monitoring needs. They are part of Oracle Communications Services Gatekeeper.
These services include:
To access the settings for these services in the Administration console:
In the Domain Structure panel of the Administration console, expand the OCSG item.
Select the name of the server on which you want to mange and configure container services.
The Oracle Communications Services Gatekeeper panel appears.
Expand the Container Services item.
Select the service that you wish to configure
The EDR service controls the management details for event data records (EDRs), charging data records (CDRs) and alarms.
You can display and reset EDR-related statistics and set various attributes affecting EDRs, such as whether CDRs or alarms are persisted or how many EDRs are sent in a batch.
These operations and attributes are described in the Reference: Attributes and Operations for EDRService section of "Managing and Configuring EDRS, CDRs, and Alarms" in Oracle Communications Services Gatekeeper System Administrator's Guide at:
Marketing and Advertising uses a modified version of Services Gatekeeper to manage the traffic delivery aspect of the system. Traffic is delivered to and received from the network using specialized connectors called plug-ins, which are based on the type of traffic that is being delivered.
The Plug-in Manager is a utility for managing these plug-ins. This section gives a very high level overview of the tasks for which you will use the Plug-in Manager. For more detailed information, see "Managing and Configuring the Plug-in Manager" in Oracle Communications Services Gatekeeper System Administrator's Guide at:
You use the Plug-in Manager to:
You can create and specify individual routing for multiple instances of each plug-in type. This allows system owners the greatest possible flexibility in setting up and routing traffic.
When the system is first started up, there are only plug-in services. These services have service IDs. Before traffic can be routed to or from the network, active instances of these services must be created using the Plug-in Manager. You can use the listPluginServices operation to get a list of available services from which to create instances. You can then use the createPluginInstance operation to create a specific plug-in instance, which you must give a name. The name is used when routing is being set up.
For a detailed example of the individual steps involved in creating a plug-in instance, see Creating the EWS Bulk SMS Plug-in Instance.
After you have created the plug-in instances that your system will use, you must set up routes.
Plug-in routing matches the data in and associated with a traffic request with routing logic defined in a routing XML file. The result is the selection of the appropriate plug-in instance for the request.
Routing can be based on such parameters as destination address, the method being invoked in moving the message, and the source of the message, among others. Routing makes it possible to target a plug-in instance, and thereby a network node all based on data available in an individual request.
For information about routing, see the sections on plug-in routing logic in "Managing and Configuring the Plug-in Manager" in Oracle Communications Services Gatekeeper System Administrator's Guide at:
The SNMP service collects system generated alarms and distributes them as SNMP traps.
Using the SnmpService container service, you can add, delete and list trap receivers. You can also configure the attributes of the SNMP service. These operations and attributes are described in the reference section of that chapter.
For more information, see "Managing and Configuring the SNMP Service" in Oracle Communications Services Gatekeeper System Administrator's Guide at:
The SMPPService provides connectivity services for the Parlay X 2.1 Short Messaging/SMPP and Native SMPP communication services used to send and receive short messages.
See Setting Up the SMPP Server Service for information on how to configure this service.
The system maintains statistical information on usage in terms of the number of transactions handled over time.
Transactions are grouped into transaction types. Transaction types are used for calculating usage costs and for grouping reports. Transaction types are in turn grouped into categories. The StatisticsService lets you run statistics operations to get statistics and create reports as well and configure statistics service attributes.
For information about statistics reports, see "Managing and Configuring Statistics and Transaction Licenses" in Oracle Communications Services Gatekeeper System Administrator's Guide at:
The storage service helps optimize database access by creating one or more named stores.
The StorageService allows you to activate and deactivate the storage service by setting an attribute and to perform operations that provide you with information about stores in the domain.
For information about the storage service, see "Managing and Configuring the Storage Service" in Oracle Communications Services Gatekeeper System Administrator's Guide at:
Services Gatekeeper's storage service uses Oracle Coherence to provide cluster-wide storage. If Marketing and Advertising is running in a clustered environment, you need to configure Coherence. For information on how to do this, see "Configuring Coherence" in Oracle Communications Services Gatekeeper System Administrator's Guide at:
Delivery notifications coming from the network as a result of Application to Person (A2P) requests pose particular problems for routing. The Tier Routing service allows those notifications to be properly routed to the appropriate application.
The routing mechanism uses tier routes to identify how to route network-triggered requests. A tier route is identified by an index and defined by two parameters:
An endpoint expression that describes the destination to which to message is to be ultimately delivered
The name of the cluster for which the route is valid
The TierRoutingManager allows you to add, remove and list tier routes. For more information, see "Managing and Configuring the Tier Routing Manager" in Oracle Communications Services Gatekeeper System Administrator's Guide at:
Note:In this chapter, the term Service Enabler is roughly equivalent to the plug-in layer. The sections on the various Service Facades available in Oracle Communications Services Gatekeeper are not relevant to Oracle Communications Marketing and Advertising.
The trace service is based on Log4J, an Apache Java-based logging utility.
The log file is named default.log. Each service instance writes to this log file in the local file system of the server on which it executes. The trace service itself writes log files in the directory $DOMAIN_HOME/servers/server name/trace directory.
The trace service supports basic tracing in which the root logger rootdefault maintains the trace file. It also supports context tracing in which log messages are filtered based on the context of a request.
For more information about the TraceService, see "Managing and Configuring the Trace Service" in Oracle Communications Services Gatekeeper System Administrator's Guide at: