What is Oracle Communications Universal User Profile?

20-4 Oracle Fusion Middleware Administrators Guide for Oracle Virtual Directory cost-center information for the billing of the package, authorization allowing you to change the package routing, and addresses of the various facilities.

20.3 Oracle Communications Universal User Profile Diameter Adapters

In today’s telecommunications environments, subscriber information may be contained in a IMS-compliant Home Subscriber Service HSS. One feature of Oracle Communications Universal User Profile is the Diameter adapter. The Diameter adapter enables Oracle Communications Universal User Profile to: ■ Connect to 3GPP IP Multimedia Subsystem IMS Home Subscriber Systems that run over the Diameter protocol ■ Present a standardized service layer for subscriber identity information regardless of the information’s source This topic contains the following sections: ■ Enabling Support for Diameter Adapters ■ Creating and Configuring Diameter Adapters

20.3.1 Enabling Support for Diameter Adapters

Perform the following steps to enable Oracle Virtual Directory to support Diameter Adapters:

1. Use WLST to add schema.diameter.xml to the Oracle Virtual Directory server

settings by referring to the SchemaLocations entry in Configuring Oracle Virtual Directory Server Settings Using WLST on page 9-8.

2. In the ORACLE_INSTANCEconfigOPMNopmnopmn.xml file, add the

following, as one continuos string, to the end of the java-classpath property for the Oracle Virtual Directory server entry: :ORACLE_HOMEovddiameterlibwlssdiameter.jar:ORACLE_ HOMEovddiameterlibweblogic.jar:ORACLE_HOMEovddiameterlibxbean.jar

3. Reload the OPMN configuration by executing the following command:

ORACLE_INSTANCEbinopmnctl reload

4. Restart the Oracle Virtual Directory server.

20.3.2 Creating and Configuring Diameter Adapters

Perform the following steps to create and configure a Diameter Adapter: 1. Create a new Custom Adapter. Refer to Creating and Configuring Custom Adapters on page 18-1 for more information. 2. Select Diameter as Adapter Template in the New Custom Adapter dialog box and enter the appropriate Adapter SuffixNamespace. Click the Finish button. Note: The Client View browser cannot browse the namespace of Diameter adapter because it does not support subtree search scope with a objectclass= filter. Similarly, the Client View browser cannot browse a Join View adapter configured with a Diameter adapter as its primary adapter. Oracle Communications Universal User Profile 20-5 3. Go to the Plug-ins tab for the new Diameter adapter. Select DiameterAdapterPlugin and click the Edit button. The Edit Plug-in: DiameterAdapterPlugin dialog box appears.

4. Add the following configuration parameters Name: Value to the Parameters

table by selecting a parameter and clicking the Edit button. The remoterealm and remotePeers parameters are required. ■ interface : The type of Diameter interface used to connect to HSS. The default value is Sh. ■ listener : The hostname of the Oracle Communications Universal User Profile server and the port to listen on to receive messages from the HSS server, which is a requirement of the HSS protocol. The listener value must be in the form of aaa:host:port, for example aaa:ovd.oracle.com:3689. The port must be accessible through the firewall from the HSS server. 3869 is the default port for HSS client listener ports. ■ nosctp : Determines whether to disable SCTP transport. Supported values are true and false. The default setting is true. ■ localrealm : The realm of this custom Diameter adapter and can be any valid value for the HSS server. The default is us.oracle.com. The localrealm parameter is used as a key to map records for Oracle Communications Universal User Profile to the HSS server. ■ remoterealm required: Supplied by the HSS provider, it is the remoterealm value for the HSS server. ■ remotePeers required: The remotePeers value is the hostname and port to the HSS server. Both values are provided by the HSS server. The remotePeers value must be in the format of aaa:host:port, for example, aaa:hss.oracle.com:3868. The default port is 3868. Note: Currently, Sh is the only supported value for the interface configuration parameter. Notes: ■ The aaa string in the listener value is not a replaceable variable—it must be explicitly included. ■ Do not confuse the listener parameter for an Oracle Virtual Directory listener. Note: Refer to Enabling SCTP Transport for more information about using the nosctp option and enabling SCTP Transport. Note: Multiple values can be specified by separating each with the semicolon character ;. For example, aaa:127.0.0.1:3868; aaa:different-host:3939.