Ro online charging Web service
is a messaging interface to enable an application to send credit control
messages to an Online Charging System (OCS).
Before you begin
Before you begin, the following software
should be installed:
- A supported version of WebSphere® Application Server
Network Deployment
For a list of required WebSphere Application Server fixes,
refer to the readme file, WebSpheresoftwareForTelecomReadme.html,
on the QuickStart CD.
- One of the following supported databases:
IBM® DB2® Enterprise
Server Edition
Oracle Database
- Diameter Enabler base
Before you begin, the following
steps should be completed:
- Completed the environment preparation steps.
- Started the application server.
- Connected to the database.
Verify that you have the following files
needed for the installation:
- DHADiameterRoWebServiceEAR (in was_root/installableApps/ImsConnector)
Note: was_root is
the installation root directory for
WebSphere Application Server
Network Deployment.
By default, this directory is:
/usr/IBM/WebSphere/AppServer
/opt/IBM/WebSphere/AppServer
/opt/IBM/WebSphere/AppServer
- Diameter_Ro.properties (in was_root/installableApps/ImsConnector/properties)
- Log in to the server where WebSphere Application Server is
installed.
- Copy Diameter_Ro.properties to
the following directory:


was_profile_root/properties
Note: was_profile_root is
the directory for a
WebSphere Application Server
Network Deployment profile
called
profile_name. By default, this directory
is:
/usr/IBM/WebSphere/AppServer/profiles/profile_name
/opt/IBM/WebSphere/AppServer/profiles/profile_name
/opt/IBM/WebSphere/AppServer/profiles/profile_name
For example, AppSrv01.
- Open Diameter_Ro.properties in
a text editor.
- Find the OriginHostName property.
Type the host name to match the host name of the application server
where Diameter Enabler base is
installed. The OriginHostName must be
unique between a Diameter node and all of its peers. Typically, the
fully qualified domain name of WebSphere Application Server where Diameter Enabler is
installed can be used. However, if you are using vertical clustering,
then you must alter this name for each server on that cluster. This
value does not have to be identical to the fully qualified domain
name of WebSphere Application Server.
- Find the OriginRealmName property.
Type the realm name to match the realm of the application server where Diameter Enabler base is
installed.
- Find the HostIpAddress property.
Type the IP address where the Diameter Enabler base is
installed. If Diameter Enabler base is
installed on a multi-homed machine, the HostIpAddress should
be one of the network interfaces that is present on WebSphere Application Server.
- Find the ProxySupport property.
- Type true to enable proxy support
- Type false to turn off proxy support.
The default value is true. If you are not using proxy servers
in your environment, set the value to false. Because the proxy support
settings are independent for each Web service, you can enable proxy
support for one or more of the Web services.
- Log in to the Integrated Solutions Console:
- Open a browser and navigate to the following
URL: https://host_name:port/ibm/console.
Where:
- host_name is the fully qualified host name
of the server where the application or the network deployment manager
is deployed.
- port is the secured port used to access the
console. The default port is 9043.
Note: The default unsecured port is 9060.
If you use 9060, you must have "http" instead of "https" in the URL.
- Enter an administrator user ID and password. (Omit the password if security is
not enabled.)
- Click Log in.
- Install DHADiameterRoWebServiceEAR by
completing the following steps:
- In the navigation panel, click .
- Click Browse to
locate DHADiameterRoWebServiceEAR.
- Select Show me all installation
options and parameters.
- Click .
- Optional: If you are using
the subscribe and notification functions, click Step 3:
Provide options to perform the EJB Deploy.
- Deploy EJB option - Database type: Choose
your database:
DB2UDB_V91
ORACLE_V10G
- Database schema: Type your database user
name. This is the same user name used in Preparing the database section;
for example, if you are using the default DB2 user
name, type db2inst1.
- Optional: If you are using
the subscribe and notification functions, click Step 9:
Map data sources for all 2.x CMP beans, and click Browse to
select the Target Resource JNDI Name for the
module. The JNDI name was created in the Defining
the data source section.
- If security is enabled, click Step
13: Map security roles to users or groups, and select
the check box corresponding to Diameter_Role to
map the user and groups that you wish to grant access to the Ro online charging Web service.
- If security is enabled, click Step
14: Map RunAs roles to users, and map a user that is assigned
the Diameter_Role to the RunAs role. The RoNotification
EJB will run as this user when a notification is received.
Note: Any
future password changes need to be updated in this enterprise application's
settings as well.
- Click Step 15: Summary,
and verify all options have the correct values.
- Click Finish.
- Click Save to
save changes to the master configuration.
- In the navigation panel,
click .
- Select the check box corresponding
to DHADiameterRoWebServiceEAR.
- Click Start. You should receive the following message: Application DHADiameterRoWebServiceEAR on
server server_name and node node_name started
successfully.
- Verify Application status for DHADiameterRoWebServiceEAR is
started. After the application is started, Diameter Enabler base will
start to establish connections.