11 Managing and Configuring Traffic Users

To enable the delivery mechanism to accept messages for delivery, the entities that are sending those messages must have accounts on the delivery mechanism system.

These accounts are for users called traffic users, because they send traffic through the system. Their accounts allow for authentication with the system. The account ids are also supplied in event data records (EDR)s and charging data records (CDRs) for use in billing and system troubleshooting. For an overview of the entire account system in Oracle Communications Services Gatekeeper Accounts and SLAs Guide at:

http://download.oracle.com/docs/cd/E16625_01/doc.50/e16617/toc.htm

Account Structure

Account structures are arranged in a hierarchy.

At the base is the application instance, which is associated with the username (also called an application instance ID) and password that are used to authenticate with Oracle Communications Service Gatekeeper.

The application instance belongs to an application account.

The application account, in turn, belongs to a service provider account.

The application account also belongs to an application group and the service provider belongs to a service provider group.

In the standard installation of Services Gatekeeper, the application group and the service provider group are associated with Service Level Agreements (SLAs) that define contractual Quality of Service (QoS) and maximum throughput levels, but the modified version of Services Gatekeeper provided with Marketing and Advertising does not use either account or service provider level SLAs. However, if you are using an existing standard instance of Services Gatekeeper, you should set up all accounts in the normal way for that system, including setting up all levels of SLAs.

Setting Up a Traffic User for Marketing and Advertising

The messages that make up marketing campaigns are sent by the OCSG Client module in Marketing and Advertising. This client module must be provisioned with a set of accounts for sending messages through the modified Services Gatekeeper.

For the OCSG Client module to function, you must set up:

• The Application Instance

• The Application Account and the Service Provider Account

• The Application Group and the Service Provider Group

The Application Instance

To set up an application instance for the OCSG Client module, follow the instructions in "Managing Application Instances" in Oracle Communications Services Gatekeeper Accounts and SLAs Guide at:

http://download.oracle.com/docs/cd/E16625_01/doc.50/e16617/sla_instances.htm#i1118793

The Application Account and the Service Provider Account

To set up the application account and the service provider account for the OCSG Client module, follow the instructions in "Managing Service Provider and Application Accounts" in Oracle Communications Services Gatekeeper Accounts and SLAs Guide at:

http://download.oracle.com/docs/cd/E16625_01/doc.50/e16617/sla_accounts.htm#i1120919

The Application Group and the Service Provider Group

To set up the application group and the service provider group for the OCSG Client module, follow the instructions in "Managing Groups" in Oracle Communications Services Gatekeeper Accounts and SLAs Guide at:

http://download.oracle.com/docs/cd/E14148_01/wlcp/ocsg41_otn/spappmgmt/groups.html

It is not necessary to set up SLAs for this group set unless you are using an overlay installation.

Setting Up Traffic Users for Ad Space Owners

The messages that are used in advertising campaigns originate outside of the system either from an application that is offering space in its own messages (called an ad space owner) or from subscribers who send messages to those applications that Marketing and Advertising intercepts. These are called, respectively, Application to Person (A2P) campaigns or Person to Application (P2A) campaigns. An application that is involved in either of these scenarios must also have a full set of related account structures in Services Gatekeeper.

To enable ad space owners to interact with the delivery mechanism, you must set up:

• The Application Instance

• The Application Account and the Service Provider Account

• The Application Group and the Service Provider Group

The Application Instance

To set up an application instance for each ad space owner/application, follow the instructions in "Managing Application Instances" in Oracle Communications Services Gatekeeper Accounts and SLAs Guide at:

http://download.oracle.com/docs/cd/E16625_01/doc.50/e16617/sla_instances.htm#i1118793

The Application Account and the Service Provider Account

To set up the application account and the service provider account for each ad space owner/application, follow the instructions in "Managing Service Provider and Application Accounts" in Oracle Communications Services Gatekeeper Accounts and SLAs Guide at:

http://download.oracle.com/docs/cd/E16625_01/doc.50/e16617/sla_accounts.htm#i1120919

The Application Group and the Service Provider Group

To set up the application group and the service provider group for each ad space owner/application, follow the instructions in "Managing Groups" in Oracle Communications Services Gatekeeper Accounts and SLAs Guide at:

http://download.oracle.com/docs/cd/E14148_01/wlcp/ocsg41_otn/spappmgmt/groups.html

It is not necessary to set up SLAs for this group set.

Setting Up A Global Node SLA

Marketing campaigns, which send messages to subscribers in bulk, use an internal budget mechanism to monitor the load that the system is sending to the network at any given time. The rules for what the system can send to each network node are established through the use of a Global Node SLA, which is an XML file that defines the conditions under which individual network nodes can be used.

To set up a Global Node SLA, follow the instructions in "Defining Global Node and Service Provider Group Node SLAs" in Oracle Communications Services Gatekeeper Accounts and SLAs Guide at:

http://download.oracle.com/docs/cd/E16625_01/doc.50/e16617/sla_defnodes.htm#i1122622