Diameter Enabler base is
configured with a unique identity during the installation process.
However, changes in the network may require updates to the configuration.
Before you begin
If Diameter Enabler is
moved to a different server, the configuration should be updated.
Also if a proxy server is added to or removed from the network, the
configuration may need to be updated.
About this task
The unique identity of
Diameter Enabler is
defined using the
OriginHostName,
OriginRealmName,
and
HostIpAddress properties in the
Diameter_Rf.properties,
Diameter_Ro.properties,
and
Diameter_Sh.properties files.
Note: In case
of a clustered installation, repeat these steps for each node in the
cluster.
- Open the Diameter_Rf.properties in
a text editor. This file is located in 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 in a standalone environment,
or Custom01 as the name of a federated node profile in a clustered
environment.
- 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.
- Save the file and close it.
- Open the Diameter_Ro.properties in a text editor. The
file is located in the following directory:


was_profile_root/properties
- Repeat steps 2 through 6.
- Open the Diameter_Sh.properties in a text editor. The
file is located in the following directory:


was_profile_root/properties
- Repeat steps 2 through 6.
- Restart the Rf, Ro, and Sh applications to make the configuration
changes take affect.
- Log in to the Integrated Solutions Console.
- Navigate to the Enterprise applications page. in the console navigation tree.
- Select the check box for the DHADiameterRfWebServiceEAR,
the DHADiameterRoWebServiceEAR,
and the DHADiameterShWebServiceEAR applications.
- Click Stop.
- Click Start to restart the application.