WebSphere brand IBM WebSphere IP Multimedia Subsystem Connector, Version 6.2

Configuring Rf accounting Web service

You need to configure Rf accounting Web service to work in your environment.

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.

  • Diameter Enabler base
  • Rf accounting Web service
Verify that you have the following file needed:
  • Diameter_Rf.properties (in was_root/installableApps/ImsConnector/properties)
    Note: was_root is the installation root directory for WebSphere Application Server Network Deployment. By default, this directory is:
    • AIX /usr/IBM/WebSphere/AppServer
    • Linux /opt/IBM/WebSphere/AppServer
    • Solaris /opt/IBM/WebSphere/AppServer
About this task
You must complete the following steps on each federated node that belongs to the cluster.
  1. Log in to the server where WebSphere Application Server is installed.
  2. Copy Diameter_Rf.properties to the following directory:
    • AIXLinuxSolaris 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:
    • AIX /usr/IBM/WebSphere/AppServer/profiles/profile_name
    • Linux /opt/IBM/WebSphere/AppServer/profiles/profile_name
    • Solaris /opt/IBM/WebSphere/AppServer/profiles/profile_name

    For example, Custom01.

  3. Optional: If you are using vertical clustering, copy Diameter_Rf.properties, and rename the file based on the cluster member name. You must have a separate Diameter_Rf.properties for each cluster member. Each file must have a unique name and unique information within the file. Naming the file based on the cluster member name associates the configuration file with the cluster member. For example, for a cluster member named diameter0, name the configuration file Diameter_Rf.properties.diameter0. For a cluster member named diameter1, name the configuration file Diameter_Rf.properties.diameter1.
  4. Open Diameter_Rf.properties in a text editor.
  5. 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.
  6. Find the OriginRealmName property. Type the realm name to match the realm of the application server where Diameter Enabler base is installed.
  7. 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.
  8. 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.



Terms of use
(C) Copyright IBM Corporation 2009. All Rights Reserved.