Oracle Communication Mediation Controller

Oracle Communication Mediation Controller Activity Guide

Edition 1.0

July 2012

Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Disclaimer This document contains proprietary information and is protected by copyright and other intellectual property laws. You may copy and print this document solely for your own use in an Oracle training course. The document may not be modified or altered in any way. Except where your use constitutes "fair use" under copyright law, you may not use, share, download, upload, copy, print, display, perform, reproduce, publish, license, post, transmit, or distribute this document in whole or in part without the express authorization of Oracle. The information contained in this document is subject to change without notice. This document is not warranted to be error-free. Restricted Rights Notice If this documentation is delivered to the United States Government or anyone using the documentation on behalf of the United States Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS The U.S. Government’s rights to use, modify, reproduce, release, perform, display, or disclose these training materials are restricted by the terms of the applicable Oracle license agreement and/or the applicable U.S. Government contract. Trademark Notice Oracle and Java are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

Table of Contents

Practices for Lesson 1 .....................................................................................................................................1-1 Lesson 1: Overview ........................................................................................................................................1-3

Practices for Lesson 2 .....................................................................................................................................2-1 Lesson 2: Overview ........................................................................................................................................2-3 Practice 2-1: Downloading Software and Documentation ..............................................................................2-4

Practices for Lesson 3 .....................................................................................................................................3-1 Lesson 3: Overview ........................................................................................................................................3-3 Practice 3-1: Installing Online Mediation Controller ........................................................................................3-4 Practice 3-2: Creating and Configuring a Domain ..........................................................................................3-8 Practice 3-3: Configuring Message Debug Logging .......................................................................................3-12

Practices for Lesson 4 .....................................................................................................................................4-1 Lesson 4: Overview ........................................................................................................................................4-3

Practices for Lesson 5 .....................................................................................................................................5-1 Lesson 5: Overview ........................................................................................................................................5-3 Practice 5-1: Integrating with BRM .................................................................................................................5-4 Practice 5-2: High Availability with BRM ........................................................................................................5-17

Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

Practices for Lesson 1 Chapter 1 - Page 1

Practices for Lesson 1 Chapter 1





Lesson 1: Overview

Practices Overview There are no practices for this lesson. But, you should already have created your environment using the instructions for creating a virtual machine in which you have installed and configured Oracle Enterprise Linux.










Lesson 2: Overview

Practices Overview In the following practice, you will navigate to the download site for the software and the documentation.



Practice 2-1: Downloading Software and Documentation

Overview In your practice environment the software and the documentation have already been downloaded. But, when you get back to your work environment, you might want to have your own copy of the software and the documentation. In this practice, you will navigate to the download site for the software and the documentation.

Tasks

Accessing the Oracle Software Delivery Cloud Many of the Oracle software and documentation packages are only available in the Oracle Software Delivery Cloud which requires that you have an account. 1. Log into the Oracle Software Delivery Cloud:

a. Start a web browser and go to http://edelivery.oracle.com. The welcome screen appears.

b. Click Sign In / Register. The log in screen appears.

Registering yourself with Oracle If you don’t have a web account for Oracle, you need to sign up to get access to the Oracle Software Delivery Cloud. 2. Register yourself with Oracle:

a. Click the Register link. The My Profile – Create User screen appears.

b. Fill in all the mandatory information. c. Expand the section called My Group Membership and select Oracle Technology

Network. d. Click Create.

The Verify Account screen appears. e. Click Continue.

The log in screen appears.

Logging into the Oracle Software Delivery Cloud 3. Supply your credentials:

a. In the Username field, enter the user name you have registered with Oracle. This is most probably your e-mail address.

b. In the Password field, enter the password for your Oracle account. c. Click Log In.

The Media Pack Search screen appears.

Finding the Downloads 4. List the correct media packs:

a. In the Select a Product Pack field, select Oracle Communications Applications. b. In the Platform field, select Linux x86-64.



c. Click Go. In the long list of media packs you should find Oracle Communications Service Broker 6.0 Media Pack and Documentation for Oracle Communications Service Broker Media Pack.

Downloading the Software 5. Simulate a download of the software:

a. Click Oracle Communications Service Broker 6.0 Media Pack. The Oracle Communications Service Broker 6.0 Media Pack screen appears.

b. Click Download for Oracle Communications Service Broker 6.0 Software. The File Download dialog box appears. If you didn’t already have the software available, you would now save the file in your machine. The file is compressed and needs to be unpacked.

c. Click Cancel.

Downloading the Documentation 7. Simulate a download of the documentation:

a. In your browser click the back button twice. Note: The back button is the arrow pointing to the left, usually available to the far left of the address filed in your browser.

b. Click Documentation for Oracle Communications Service Broker Media Pack. The Documentation for Oracle Communications Service Broker Media Pack screen appears.

c. Click Download for Oracle Communications Service Broker 6.0 Documentation. The File Download dialog box appears. If you didn’t already have the documentation available, you would now save the file in your machine. The file is compressed and needs to be unpacked.

d. Click Cancel.

Summary In this practice, you have navigated to the download site for the software and the documentation. Even though you did not download the software or the documentation, you now have the appropriate privileges and know how to navigate the Oracle Software Delivery Cloud to do this when you get back to your work environment. Remember that if you registered an Oracle web account for yourself, you should check your e-mail inbox for a message from Oracle and follow the instructions therein for verifying you account.










Lesson 3: Overview

Practices Overview In these practices you will install the Online Mediation Controller, create a Mediation Controller domain and enable message debug logging.

Environment and Product Version The following practices have been tested on Oracle Enterprise Linux 5 using Oracle Database Express Edition (XE) version 11g and Oracle Communications Service Broker version 6.0.

Prerequisites You should already have:

• An installation of Oracle Enterprise Linux 5 • An installation of Oracle Database Express Edition (XE)



Practice 3-1: Installing Online Mediation Controller

Overview In this practice you will install the Online Mediation Controller in your practice environment.

Tasks

Preparing Your Operating System To effectively handle the garbage collection of incoming network traffic, you need to increase the size of the socket buffers to 2 MB. Make the change in the running system and also in the configuration files to make sure the settings are used after restart of your system. 1. Change the size of the socket buffers to 2 MB.

a. Open a terminal window and make sure you are logged in as oracle: $ whoami

oracle

b. Set the read memory size to 2MB:

$ sudo sysctl -w net.core.rmem_max=2096304

c. Set the write memory size to 2MB:

$ sudo sysctl -w net.core.wmem_max=2096304

d. Check that the values have been set:

$ sysctl -a | grep net.core

...

net.core.wmem_max = 2096304

net.core.rmem_max = 2096304

...

Note: Use this command after the first restart of you machine to verify that these values have been set permanently.

2. Make the configuration change of the socket buffers permanent. a. Open the sysctl.conf file for editing

$ sudo gedit /etc/sysctl.conf

b. Add the following to the end of the file:

###########

# Oracle Service Broker Recommended Values

net.core.rmem_max=2096304

net.core.wmem_max=2096304

########

c. Save the file and close the editor.



Preparing Your Environment 3. Prepare for installation.

a. Create the directory for the installation: $ cd

$ cd course

$ mkdir –p apps/OMC

b. Unpack the installation package:

$ cd installs/ocmc

$ unzip ocsb6001-linux_x86-64.zip

$ rm ocsb6001-linux_x86-64.zip

Installing Online Mediation Controller 4. Install Online Mediation Controller.

a. Start the installer: $ cd linux64/Disk1/install

$ ./runInstaller

The Welcome screen appears.

b. Click Next. An Error dialog appears. Note: Since Oracle Database XE is already installed, there is an Oracle inventory created which is owned by root. We will create a separate Oracle inventory.

c. Click OK. The Specify Inventory directory and credentials screen appears.

d. Click Browse and select the /home/oracle/course/installs/ocmc/oraInventory directory.

e. In the Specify Operating System group name field, select oinstall.

f. Click Next. The Select a Product to Install screen appears.

g. Select Online Mediation Controller and click Next. The Specify Home Details screen appears.

h. In the Name field, enter OMC

i. In the Path field, enter /home/oracle/course/apps/OMC.

j. Click Next.



The Register for Security Updates screen appears.

k. Deselect I wish to receive security updates via My Oracle Support.

l. Click Next. The Email Address Not Specified dialog box appears.

m. Click Yes. The Java Installation Option screen appears.

n. Click Next. The Java Selection screen appears.

o. Select Oracle JRockit and click Next. The Summary screen appears.

p. Click Install. After a while the Execute Configuration scripts screen appears.

q. Open a terminal window and execute the following script: $ sudo course/installs/ocmc/oraInventory/orainstRoot.sh

r. Return to the Execute Configuration scripts screen and click OK.

The End of Installation screen appears.

s. Click Exit. The Exit dialog appears.

t. Click Yes. The installer shuts down.

u. In the window where the installer was started, press the return key to get the prompt back.

Configuring Security By default, the settings that control security are enabled. These settings apply to the connections between the Administration Console and all managed servers. Before you patch the installation or use the domain creation script, you must either disable the security setting or set up the client and server certificate keystores on the host system. 5. Disable the security settings.

a. Open the configuration file common.properties for editing: $ cd

$ cd course/apps/OMC/ocsb60/admin_console/properties



$ gedit common.properties

b. Set the following security properties appropriately to disable security:

axia.ssl=false


d. Open the configuration file web.properties for editing:

$ gedit web.properties

e. Set the following security properties appropriately to disable security:

axia.basic.auth=false

org.eclipse.equinox.http.jetty.http.enabled=true

org.eclipse.equinox.http.jetty.https.enabled=false

f. Save the file and close the editor.

Configuring JMX Access The following configuration is necessary if you want to access the MBeans (the JMX server) from a remote machine. 6. Enable the JMX port in the start scripts for the administration console.

a. Open the script that sets the common flags and environment variables for starting the administration console: $ cd ..

$ gedit common.sh

b. Add the following as one line before the final java command line:

JAVA_OPTS=”${JAVA_OPTS} -Dcom.sun.management.jmxremote.port=7555 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false”

Note: This text is available for copying in the file JMX-snippet.txt which is located in the directory /home/oracle/course.


Summary You now have an installation of the Online Mediation Controller in your practice environment.



Practice 3-2: Creating and Configuring a Domain

Overview In this practice you will create a Mediation Controller domain that will be used in the upcoming practices.

Tasks

Creating a Domain for Online Mediation Practices 1. Prepare information to use when creating the domain.

a. Open a new terminal window and find out your IP address: $ ipget

10.0.2.15

b. Compute the specific multicast port number for your environment.

Take the last part of your IP address and add 25000. For example, if your IP address is 10.0.2.15, the port number to use is 25015. The specific multicast port number for your environment will be used when you create the domain.

2. Create the domain. a. Change to the directory for the admin console and start the domain creation wizard:

$ cd course/apps/OMC/ocsb60/admin_console

$ ./create_domain.sh

The list of Available Domains appears.

b. Enter the index for Online-Mediation-Controller and press return. The list of Available Online-Mediation-Controller Domain Types appears.

c. Enter the index for Unified and press return.

d. Enter the index for Service Availability and press return.

e. Enter the following path for the domain and press return: /home/oracle/course/apps/OMC/ocsb60/uniDomain

f. Disable domain SSL by entering false and press return.

g. Enter the multicast IP address of 224.1.2.3 and press return.

h. Enter your specific multicast port number. Using the example earlier in this practice,

you should enter 25015 and press return.

i. Enter the time to live, 2, for multicast and press return.



j. For the question, Should this domain be a hosted domain?, enter false and press return. Note: While the domain is created, you will see a number of warnings and informational messages.

Using the Web Administration Console The web administration console is typically used for remote administration and you will use it in this first configuration step to make sure you have seen it. 3. Start the web administration console for your domain:

$ ./web.sh ../uniDomain

4. Open the Administration Console

a. Start a web browser.

b. Go to the web address http://<IP address>:9000/console.

5. Examine the icons in the top tool bar: • The icon looking like a pencil is used to lock the configuration for exclusive edit. In the

practice instructions this icon will be referred to as Lock & Edit. • The red dot with a white X is used to Discard the configuration changes you have

done. • The green checkmark is used to Commit the configuration changes you have done. • Some configuration changes need to be done in offline mode and the green dot is used

to Switch to OFFLINE mode.

6. Configure the Managed Server a. In the top tool bar, click Switch to OFFLINE mode.

The Switching to OFFLINE mode dialog appears.

b. Click OK. The green dot turns gray to indicate that the server is in offline mode.

c. In the top tool bar, click Lock & Edit.

d. Expand OCSB, then Domain Management and click on Servers. An empty server list panel appears.

e. Click the green plus icon to add a new server. The Add Server dialog appears.

f. In the Name field, unified_1.

g. In the Port field, enter 9001 and click OK.



h. In the top tool bar, click Commit.

i. In the top tool bar, click Switch to ONLINE mode.

The grey dot turns green to indicate that the server is in online mode.

7. Shutdown the web administration console: a. Exit the browser.

b. In the terminal window where you started the web administration console, use ctrl-c to

stop the running process.

Starting the Standalone Administration Console The standalone administration console is typically used for local administration. 8. Start the standalone administration console for your domain:

$ ./start.sh ../uniDomain

After a while, the standalone administration console appears.

10. Examine the icons in the top tool bar and you will discover that they are the same as in the web administration console.

Configuring the Persistence Store You need to have a persistent store available if you want to enable the degraded mode service. This service will use the persistent storage to both store charging data records for replay as well as temporary subscriber profile information. 12. Configure the persistence store:

a. In the top tool bar, click Switch to OFFLINE mode. The Switching to OFFLINE mode dialog appears.

b. Click OK. The green dot turns gray to indicate that the server is in offline mode.

c. In the top tool bar, click Lock & Edit.

d. Expand OCSB, Domain Management, then Data Store and click on Persistent Stores. The Persistence Stores panel appears.

e. Click the Berkeley DB Store tab and click New. The New dialog appears.

f. In the Managed Server Name field, enter unified_1.

g. In the BDB enabled field, enter true.



h. In the BDB environment directory field, enter

/home/oracle/course/apps/OMC/ocsb60/uniDomain.

i. In the Address (host:port) field, enter <IP Address>:6000, for example 10.0.2.15:6000.

j. Click OK.

k. In the top tool bar, click Commit.

l. In the top tool bar, click on the grey dot to switch to online mode. The grey dot turns green to indicate that the server is in online mode.

Starting the Managed Server 13. Start the managed server.

a. Open a new terminal window and copy the managed server directory: $ cd course/apps/OMC/ocsb60

$ cp -R managed_server unified_1_server

b. Start the managed server:

$ cd unified_1_server

$ ./start.sh unified_1 file:///home/oracle/course/apps/OMC/ocsb60/uniDomain/initial.zip

The server is fully started when you see the message Server is now in state RUNNING level (300).

Summary You now have a configured and running domain for Service Broker.



Practice 3-3: Configuring Message Debug Logging

Overview In this practice you will enable message debug logging by changing MBeans values through JMX. The practice describes three alternative tools to change the MBean values:

• MBean Player • JConsole • JRockit Mission Control

In this practice, all three alternatives are described. Select one of the alternatives and do the tasks for that alternative.

Tasks

Configure Logging – Using the MBean Player (Alternative 1)

Stopping the Servers If the administration or managed server is running, you need to stop them: 1. If the managed server is running, use ctrl-c to shut it down.

2. If the administration console is running, shut it down.

Verifying the Script 3. Examine the script and make sure the settings are correct:

a. Open a new terminal window and set the necessary environment variables: $ cd course

$ . ./setenv.sh

b. Examine the configure_logging.xml file and make sure the domainPath is set to

your domain directory: $ cd scripts

$ more configure_logging.xml | grep domainPath

<domainPath>/home/oracle/course/apps/OMC/ocsb60/uniDomain</domainPath>

Running the Script 4. Run the script:

$ ./runScript.sh configure_logging

Note: You will see a number of informational messages in the output, but you should not see any error messages.

Configure Logging – Using the JConsole (Alternative 2) The following tasks should NOT be done if you already used the MBean Player to configure logging.

Starting the Servers If the administration and managed server is not running, you need to start them:



5. Start the administration console for your domain: a. Open a new terminal window and set the necessary environment variables:

$ cd course

$ . ./setenv.sh OMC

b. Start the administration console:

$ cd apps/OMC/ocsb60/admin_console


6. Start the managed server.


$ . ./setenv.sh OMC

b. Change to the managed server directory:

$ cd apps/OMC/ocsb60/unified_1_server

c. Start the managed server:



Examine the Administration Console To make sure that you connect the JMX client to the administration console, you need to know the process ID for this server. 7. Find out the PID for the administration console:

a. Open a new terminal window and execute the following command: $ ps -ef | grep wcs.admin

The information about the administration console processes is shown.

b. The first number on the line describing the administration console is the process id. Write down this number. In the example shown below, the process id is 3433. oracle 3433 3431 5 11:58 pts/1 00:10:11 /opt/ocsb600/OMC/ocsb/jrrt/bin/java -Dwcs.admin -Dwcs.con…

Configure Logging 8. Start the JConsole and connect to the admin console process:

a. In the terminal window, start JConsole: $ jconsole

The JConsole: New Connection dialog appears.

b. In the list of local processes, click on the row containing the process id (PID) of the administration console that you looked up earlier and then click Connect.



Note: It is possible to run JConsole on a separate machine and remotely connect to the JMX port, 7555, that you configured earlier in this practice.

9. Enable Message Debugging a. Click the MBeans tab.

b. In the MBean tree, navigate into oracle, oracle.axia.cm.ConfigurationMBean,

oracle.axia.protocol.diameter, 2.0.1, diameterConfig, node[0], message-debug-enabled and select Attributes. The Attribute values panel appears.

c. Double-click false, change it to true and press tab.

10. Adding a Logger a. In the MBean tree, navigate into oracle, oracle.axia.cm.ConfigurationMBean,

oracle.axia.logging.log4jconfig, 2.0.1, log4jConfig, configuration[0], logger[7], Operations and select cloneIt. The Operation invocation panel appears.

b. Click cloneIt. The logger[8] object is created.

c. Navigate into logger[8], Attributes and select name. The Attribute value panel appears.

d. Double-click the current content of Value, change it to oracle.ocsb.app.rcc.mediation and press tab.

e. In the logger[8] tree, navigate into appender-ref[0] and select Attributes. The Attribute value panel appears.

f. Double-click the current content of Value, change it to file and press tab.

g. In the logger[8] tree, navigate into level and select Attributes. The Attribute value panel appears.

h. Double-click the current content of Value, change it to trace and press tab.

11. Shut down JConsole: a. From the Connection menu, select Exit.

Configure Logging – Using the JRockit Mission Control (Alternative 3) The following tasks should NOT be done if you already used the MBean Player or JConsole to configure logging.



Starting the Servers If the administration and managed server is not running, you need to start them: 12. Start the administration console for your domain:


$ . ./setenv.sh OMC

b. Start the administration console:

$ cd apps/OMC/ocsb60/admin_console


13. Start the managed server.


$ . ./setenv.sh OMC

b. Change to the managed server directory:

$ cd apps/OMC/ocsb60/unified_1_server

c. Start the managed server:



Examine the Administration Console To make sure that you connect the JMX client to the administration console, you need to know the process ID for this server. 14. Find out the PID for the administration console:

a. Open a new terminal window and execute the following command: $ ps -ef | grep wcs.admin

The information about the administration console processes is shown.

b. The first number on the line describing the administration console is the process id. Write down this number. In the example shown below, the process id is 3433. oracle 3433 3431 5 11:58 pts/1 00:10:11 /opt/ocsb600/OMC/ocsb/jrrt/bin/java -Dwcs.admin -Dwcs.con…

Configure Logging 15. Start JRockit Mission Control and connect to the admin console process:

a. In the terminal window, start JRockit Mission Control: $ jrmc

The Oracle JRockit Mission Control workspace appears.



Note: You might see a number of warnings in the terminal window, but JRockit Mission Control should start anyway.

b. If the Welcome tab is visible, close it.

c. If the JVM Browser is not visible, open the Window menu, select Show View and then JVM Browser. The JVM Browser tab appears.

d. Expand the Discovered and the Local folder and select the server with the process ID of the administration console.

e. In the toolbar, click the icon that has a red upwards pointing graph. The Mission Control console appears.

16. Enable Message Debugging a. In the vertical toolbar, click the MBeans icon.

b. In the MBean tree, navigate into oracle, oracle.axia.cm.ConfigurationMBean, 2.0.1,

diameterConfig, node[0], message-debug-enabled and select oracle.axia.protocol.diameter. The MBean Attributes tab appears.

c. Select message-debug-enabled and click the Inspect button. The Editing dialog appears.

d. In the only visible field, select true and click OK.

17. Adding a Logger a. In the MBean tree, navigate into oracle, oracle.axia.cm.ConfigurationMBean, 2.0.1,

log4jConfig, configuration[0], logger[7] and select oracle.axia.logging.log4jconfig. The MBean Attributes tab appears.

b. Click the Operations tab, select cloneIt and click Invoke. The Operation invocation status dialog appears.

c. Click OK. The logger[8] object is created.

d. Navigate into logger[8] and select oracle.axia.logging.log4jconfig.

e. Navigate into logger[8], Attributes, select name and click the Inspect button. The Editing dialog appears.



f. Change the value to oracle.ocsb.app.rcc.mediation and click OK.

Note: This will make sure that extra logging of online mediation messages are displayed in the log file.

g. In the logger[8] tree, expand appender-ref[0] and select oracle.axia.logging.log4jconfig. The MBean Attributes tab appears.

h. Select ref and click the Inspect button. The Editing dialog appears.

i. Change the value to file and click OK.

j. In the logger[8] tree, navigate into level and select oracle.axia.logging.log4jconfig. The MBean Attributes tab appears.

k. Select value and click the Inspect button. The Editing dialog appears.

l. Change the value to trace and click OK.

18. Shut down JRockit Mission Control: a. From the File menu, select Exit.

Summary In this practice you have enabled message debug logging by changing MBeans values through JMX.










Lesson 4: Overview

Practices Overview There are no practices for this lesson.










Lesson 5: Overview

Practices Overview In the first practice you will configure Online Mediation Controller to receive messages from a simulated IMS network and send these to a simulated Billing and Revenue Management system. This configuration will, in the next practice be extend for high availability.

Environment and Product Version The following practices have been tested on Oracle Enterprise Linux 5 using Oracle Database Express Edition (XE) version 11g and Oracle Communications Service Broker version 6.0.

Prerequisites You should already have:

• An installation of Oracle Enterprise Linux 5 • An installation of Oracle Database Express Edition (XE) • And installation of Online Mediation Controller • An Online Mediation Controller domain



Practice 5-1: Integrating with BRM

Overview In this practice, you will configure Online Mediation Controller with a connection to a simulated IMS network where charging requests will come in to be mediated and sent to a simulated charging system, as described in the image below.

Tasks

Starting the Managed Server and the Web Administration Console You will use a couple of scripts provided for you to start the managed server and the administration console. 1. Open a new terminal window and start the managed server:

$ cd course

$ ./startManagedServer.sh

2. Open a new terminal window and start the administration console for your domain:

$ cd course

$ ./startAdminConsole

Configuring the Connection to the IMS Network You will now configure the signaling tier to define your running Online Mediation Controller as a Diameter node and configure how other Diameter entities access it.



3. Click Lock & Edit.

4. Configure Online Mediation Controller as a Diameter node: a. Expand OCSB, Signaling Tier and select SSU Diameter.

The configuration panel appears on the right hand side.

b. Select the DIAMETER tab. The Diameter Configuration tab appears with the default diameter node selected. Also, the configuration panel for the node appears on the right hand side, with the General tab selected.

c. Enter the following values:

Realm myrealm.foo.com

Host myserver.foo.com

Port 3588

Watchdog Timeout 6000

Note: If the address field is left blank, the local host identity is used as the listen address.

5. Configure the default route for the Diameter node: a. Click the Default Route subtab.

b. In the Name field, enter My Diameter Server.

Note: This is just an administrative name without any significance or reference to anything else in the configuration.

6. Add a route for the Seagull client: a. Click the Routes subtab.

b. Click the green plus icon underneath the Route panel, to create a new node.

The fields for creating a new node appear.

c. Enter the following values:

Name route-aaa

Action relay

Realm aaa.origin.com

Application ID 4

d. Click the green plus icon at the bottom of the same panel to create a new server.

The New Data dialog appears.



e. In the Server field, enter aaa.seagull.client and click OK.

7. Configure the Seagull Client as a Diameter Peer: a. Click the subtab Peers.

b. Select Allow Dynamic Peers.

c. Click the green plus icon.

The New Data dialog appears.

d. Enter the following values and click OK:

Address 127.0.0.1

Host aaa.seagull.client

Port 3591

Protocol tcp

8. Click Commit.

Configuring the Connection to the Billing and Revenue Management (BRM) system You will now configure the signaling tier to communicate with the PCP simulator which will simulate a running Oracle Communications Billing and Revenue Management (BRM) system.


10. Configure the connection pool for communication through PCP:

a. Expand OCSB and Signaling Tier, and select SSU PCP. The configuration panel appears on the right hand side.

b. Click the PCP tab and then the Connection pools subtab.

c. Click New.



The New dialog appears.


Pool Id 1

BRM CM host 127.0.0.1

BRM CM port 4444

BRM CM login id root.0.0.0.1

Max connections 4

Min connections 2

e. Click the Credential Store tab.

f. Enter the following values:

Key 1

Password password

g. Deselect One-way and click Set Password.

11. Configure SSU PCP Network Entity:

a. Expand OCSB and Signaling Tier, and select SSU PCP. The configuration panel appears with the SSU PCP and subtab PCP Network Entities selected.

b. Click New. The New dialog appears.

c. Enter the following values and click OK:

Name SSU_BRM_1

Alias BRM_1

Heartbeat ON

PcpPoolId 1

Response Timeout 20

Active Interval 30

Inactive Interval 60

12. Click Commit.



Configuring the Interworking Module for handling of Diameter Ro messages You will now configure and activate the Interworking Module (IM) for handling of Diameter Ro messages that comes into your Online Mediation Controller.


14. Add the R-IM-OCF:

a. Expand OCSB, Processing Tier, Interworking Modules and select IM Management. The configuration panel appears.



Type RIMOCF

Version 2.0.0.0

Name rimocf

A Message dialog appears. d. Click OK.

The rimocf interworking module appears in the IM Management tab.

15. Activate the IM: a. Select the rimocf interworking module.

b. Click Activate.

16. Click Commit.

Configure Incoming Routing Rule for Diameter Messages You will now configure the signaling tier to always send diameter messages to the newly configured R-IM-OCF module, as showed in the image below:



Note: It is actually possible to do the following configuration even though the R-IM-OCF module has not been defined. 17. Click Lock & Edit.

18. Configure Incoming Router Rule:

a. Expand OCSB and Signaling Tier, and select SSU Diameter. The configuration panel appears on the right hand side, with the tabs SSU Diameter, Routing and Incoming Routing Rules selected.

b. Click New.

The New dialog appears. c. Enter the following values and click OK:

Name rule-aaa

Priority 0

Module Instance ssu:rimocf.RIMOCF@ocsb

19. Click Commit.

Configuring the Interworking Module for mediation with the BRM System You will now configure and activate the Interworking Module (IM) for mediating charging messages to the PCP protocol.




21. Add the IM-OCF-PCP: a. Expand OCSB, Processing Tier, Interworking Modules and select IM Management.

The configuration panel appears.



Type IMOCFPCP

Version 2.0.0.0

Name imocfpcp

A Message dialog appears. d. Click OK.

The imocfpcp interworking module appears in the IM Management tab.

22. Activate the IM: a. Select the imocfpcp interworking module.

b. Click Activate.

23. Click Commit.


25. Configure IM-OCF-PCP Call Handling: a. Expand OCSB, Processing Tier, Interworking Modules and select imocfpcp.

The configuration panel appears with the Configuration tab and Call Handling subtab selected.

b. In the Event Handling field, select IEC.

c. Click Apply.

26. Configure IM-OCF-PCP Diameter Credit Control Application: a. Click the Diameter Credit Control Application subtab.

The AVPs subtab appears.

b. Enter the following values and click Apply:

Destination-Host AVP destination.host



Service-Context-Id AVP [email protected]

27. Configure IM-OCF-PCP Async Announcement Manager:

a. Click the Async Announcement Manager subtab. The General subtab appears.

b. In the MRF Alias field, enter mrfAlias and click Apply.

28. Configure IM-OCF-PCP Degraded Mode: a. Click the Degraded Mode subtab.

The degraded mode settings appear.

b. Enter the following values and click Apply:

On OCF Failure ALWAYS_REFUSE

29. Click Commit.

30. Configure Ro PCP Mediation:

Note: It is very important that the following steps are done in the exact order described. If you click Lock & Edit before opening the Opcode mapping subtab, you will not be able to expand the CCR tree. a. Click the Ro PCP Mediation tab and the Opcode mapping subtab.

b. Click Lock & Edit.

c. Expand the CCR[…] tree and select the AVP[461|0|…] node.

d. In the AVP value field, enter [email protected].

e. Click Commit.

Configuring the Orchestration Engine You will now configure static orchestration which sends all messages to the IM-OCF-PCP module.




32. Define static orchestration which sends all messages to the IM-OCF-PCP module:

a. Expand OCSB and Processing Tier, and select Orchestration Engine. The configuration panel appears with the Configuration tab and the General subtab selected.

b. For the Subscriber Profile Receiver, select OlpDefaultInfoReceiver and click Apply.

c. Click the Static Route OLP subtab.

d. In the Default Routing Targets field, enter “sip:imocfpcp.IMOCFPCP@ocsb” and click Apply. Note: The double quotes around the string need to be entered as well.

33. Click Commit.

Testing the Configuration 34. Start the PCP simulator:

a. Open a new terminal window and check the port number for the PCP simulator: $ cd course/pcpsimulator

$ more pcpsimulator.sh | grep CM_PORT=

CM_PORT=4444

b. Start the PCP simulator:

$ ./pcpsimulator.sh

35. Restart the managed server:

a. In the terminal window where the managed server is running, use ctrl-c to shut it down.

b. Press up arrow and return to start the managed server again.



36. In the terminal window where the PCP Simulator is running, you should see a heartbeat message every 30 seconds, similar to the text showed below: • The first part is what the PCP Simulator receives, the fields listed after the row that

contains Opcode 11, inFL: • The last part is what the PCP Simulator returns, the fields listed after the row that

contains Opcode 11, outFL: Thread 17: Opcode: 11, inFL:

0 PIN_FLD_OP_CORRELATION_ID STR [0] "1:sdp:Unkn..."

0 PIN_FLD_PASSWD_CLEAR STR [0] "XXXX"

0 PIN_FLD_LOGIN STR [0] "root.0.0.0.1"

0 PIN_FLD_POID POID [0] 0.0.0.1 /ser...

0 PIN_FLD_TIMEOUT_IN_MS INT [0] 5000

0 PIN_FLD_CM_PTRS ARRAY [0] alloc 1, used 1

1 PIN_FLD_CM_PTR STR [0] "127.0.0.1 4444"

0 PIN_FLD_TYPE ENUM [0] 1

Thread 17: Opcode: 11, outFL size: 1

Thread 17: Opcode: 11, outFL :

0 PIN_FLD_POID POID [0] 0.0.0.1 /ser...

Thread 17: Opcode: 11 start...------------------OutFL bytes=68

Thread 17: Opcode: 11 nnn, total data sent=68

Thread 17: Opcode: 11 done.=================================

37. Use Seagull to send a Diameter Credit Control Request (CCR) through the managed server

to the PCP simulator: a. Open a new terminal window and check the configuration of the Seagull client:

$ cd course/diameterlab/config

$ more conf.client.xml | grep dest=

You should find the following in the output: dest=127.0.0.1:3588

b. Open the scenario file that you are going to use: $ cd ../scenario

$ gedit ccr_query_bal.xml

c. Examine the Capabilities Exchange Request, the CER, and the placeholder for the

answer, the CEA.

d. Examine the Credit Control Request, the CCR, and the placeholder for the answer, the CCA.

e. Close the editor.



f. Run the scenario: $ cd ../run

$ ./run_ccr.sh ccr_query_bal

Stop all the running processes 38. In the terminal window where the PCP Simulator is running, use ctrl-c to shut it down.

39. In the terminal window where the managed server is running, use ctrl-c to shut it down.

40. Shut down the administration console.

Verify the successful result of the Credit Control Request 41. Examine the output from Seagull:

In the output from Seagull, it should report a total of two successful calls. Note: Both the CER and the CCR are calls sent from Seagull to the Online Mediation Controller.

42. Open the log file produced when you ran the Seagull scenario: $ gedit seagull-client.<date & time>.log

43. Browse through the log file. You should find the following sections:

• Configuration data, which describes the configuration of the Seagull client. • Send [[CER, which describes the sent Capabilities Exchange Request. • Received [[CER, which describes the received Capabilities Exchange Answer. • Send [[CCR, which describes the sent Credit Control Request. • Received [[CCR, which describes the received Credit Control Answer.

44. Examine the Credit Control Answer. If you browse through the result, you should see that: • Result-Code is set to 2001, which means that the call was successful. • Check-Balance-Result is set to 1, which is what the PCP Simulator returns.

45. In the window where the PCP Simulator was running, you should find output similar to the text showed below: • The first part is what the PCP Simulator receives, the fields listed after the row that

contains Opcode 4104, inFL: • The last part is what the PCP Simulator returns, the fields listed after the row that

contains Opcode 4104, outFL: Thread 13: Opcode: 4104, inFL:

0 PIN_FLD_POID POID [0] 0.0.0.1 /nnn

0 PIN_FLD_MSID STR [0] "0049100080"

0 PIN_FLD_PROGRAM_NAME STR [0] "Matrix"

0 PIN_FLD_AUTHORIZATION_ID STR [0] "unified_nnn"



0 PIN_FLD_TELCO_INFO SUBSTRUCT [0] alloc 0, used 0

0 PIN_FLD_OBJ_TYPE STR [0] "gsm"

0 PIN_FLD_IMSI STR [0] "0049100080"

0 PIN_FLD_EXTENDED_INFO SUBSTRUCT [0] alloc 1, used 1

1 PIN_FLD_GSM_INFO SUBSTRUCT [0] alloc0, used 0

0 PIN_FLD_OP_CORRELATION_ID STR [0] "1:sdp:nnnn"

Thread 13: Opcode: 4104, outFL size: 4

Thread 13: Opcode: 4104, outFL :

0 PIN_FLD_RESULT ENUM [0] 1

0 PIN_FLD_POID POID [0] 0.0.0.1 /nnn

0 PIN_FLD_BALANCES ARRAY [840] alloc 4, used 4

1 PIN_FLD_RESERVED_AMOUNT DECIMAL [0] 1

1 PIN_FLD_CREDIT_LIMIT DECIMAL [0] 3

1 PIN_FLD_CURRENT_BAL DECIMAL [0] 2

1 PIN_FLD_AVAIL... DECIMAL [0] 99

0 PIN_FLD_RATING_STATUS ENUM [0] 0

Thread 13: Opcode: 4104 start...------------OutFL bytes=272

Thread 13: Opcode: 4104 nnn, total data sent=272

Thread 13: Opcode: 4104 done.=================================

46. In one of your already open terminal windows, open the log file for the managed server:

$ cd

$ cd course/apps/OMC/ocsb60/unified_1_server

$ gedit server.log

47. Browse through the log file and you should find all the messages that you have seen earlier

in this practice. Search for the text Capabilities-Exchange-Request and from there and downwards you should find the following in the log file: • The Capabilities Exchange Request (CER) • The Capabilities Exchange Answer (CEA) • The Credit Control Request (CCR) • The PCP Request with opcode 4104 • The PCP Response with opcode 4104 • The Credit Control Answer (CCA)

48. If you want to run the test again, start the PCP Simulator first, then the managed server and finally Seagull. You don’t have to start the administration console to be able to run the scenario.



Summary In this practice, you have configured the Online Mediation Controller to act as a Diameter node and communicate with Seagull, which simulates an IMS network. You have also configured communication with the PCP Simulator that simulates a Billing and Revenue Management (BRM) system.



Practice 5-2: High Availability with BRM

Overview In this practice, you will extend the previous configuration to simulate that you have two BRM connection managers available. You will configure an additional PCP connection pool and network entity. You will start a second PCP simulator and test the configuration with Seagull.

Tasks

Starting the Managed Server and the Web Administration Console 1. Open a new terminal window and start the managed server:

$ cd course

$ ./startManagedServer.sh

2. Open a new terminal window and start the web administration console for your domain:

$ cd course

$ ./startAdminConsole

Configuring a Second Connection to the BRM System You will now add a second connection pool for communication with the BRM system. This simulates that the BRM system has two separate communication managers (CM) configured. Usually these CM’s are available at separate machines as well. Note that you will not have to do any configuration changes to the IM-OCF-PCP module. Unless you limit which PCP network entities to use, all of them will automatically be used.




4. Configure a second connection pool for communication through PCP: a. Expand OCSB and Signaling Tier, and select SSU PCP.

The configuration panel appears on the right hand side.

b. Click the PCP tab and then the Connection pools subtab.

c. Click New. The New dialog appears.


Pool Id 2

BRM CM host 127.0.0.1

BRM CM port 4445

BRM CM login id root.0.0.0.1

Max connections 4

Min connections 2

e. Click the Credential Store tab.

f. Enter the following values:

Key 2

Password password

g. Deselect One-way and click Set Password.

5. Configure SSU PCP Network Entity:

a. Expand OCSB and Signaling Tier, and select SSU PCP. The configuration panel appears with the SSU PCP and subtab PCP Network Entities selected.



Name SSU_BRM_2

Alias BRM_2

Heartbeat ON



PcpPoolId 2

Response Timeout 20

Active Interval 30

Inactive Interval 60

6. Click Commit.

Starting the PCP Simulators 7. Start the PCP simulators:

a. Open a new terminal window and from the Terminal menu, select Set Title. The Set Title dialog appears.

b. In the Title field, enter PCP 1 and click Close. The title of the terminal window is changed.

c. Start the first PCP simulator: $ ./pcpsimulator1.sh

d. Open a new terminal window and set the title to PCP 2.

e. Start the second PCP simulator:

$ ./pcpsimulator2.sh

8. Restart the managed server:

a. In the terminal window where the managed server is running, use ctrl-c to shut it down.

b. Press up arrow and return to start the managed server again.

9. In the terminal windows where the PCP Simulators are running, you should see a heartbeat message every 30 seconds.

Testing the Configuration 10. Use Seagull to send a Diameter Credit Control Request (CCR) through the managed server

to the PCP simulators: a. Open a new terminal window and set the title to Seagull.

b. Run the scenario:

$ cd course/diameterlab/run

$ ./run_ccr.sh ccr_query_bal

c. Examine which PCP Simulator that got the request.



d. Run the scenario again and you should see that the other PCP Simulator got the

request.

e. Use ctrl-c to stop one of the PCP simulators.

f. Run the scenario a couple of times and you should see that the running PCP Simulator now takes care of all the messages.

g. Restart the PCP Simulator that you stopped.

h. Run the scenario a couple of times and you should now see that the requests are again distributed between both the PCP Simulators.

Summary In this practice, you have extended the previous configuration to simulate that you have two BRM connection managers available. You have configured an additional PCP connection pool and network entity. You have started a second PCP simulator and tested the configuration with Seagull.

Documents

Oracle Communication Mediation Controller