This chapter provides instructions for Oracle Communications Evolved Communications Application Server (OCECAS) post-installation tasks.
Before continuing, complete the tasks in the following chapters:
After installing OCECAS and creating your domains, perform the following tasks:
Set up your OCECAS system for subscriber data. See "Setting up OCECAS for Subscriber Data".
Start your WebLogic Server administration and managed servers. See "Starting WebLogic Server Administration and Managed Servers".
Perform post-configuration tasks for your OCECAS domains. See "Post-Configuration Tasks for Your Domains".
To configure your runtime domain to communicate with a NoSQL-based UDR, see "Configuring Communication Between Your Runtime Domains and the UDR".
To configure your UDR domain to communicate with a NoSQL-based UDR, see "Configuring Communication Between Your UDR Domain and the UDR".
Create users for the Session Design Center (SDC) GUI. See "Creating Users for the SDC GUI".
Configure authentication. See "Configuring Authentication".
Configure SSL host name verification. See "Configuring SSL Hostname Verification".
Configure the Coherence security framework. See "Configuring the Coherence Security Framework".
OCECAS can retrieve subscriber data from an OCECAS subscriber server (ESS), which is a local NoSQL database often used in combination with a home subscriber server (HSS). Both ESS and HSS can serve as subscriber data stores, and you may also use both and federate the data between them.
The instructions in this section apply whether you are using the UDR domain, or just adding the NoSQL database to a runtime domain.
These tasks are required to obtain data from the ESS NoSQL database:
To install an OCECAS ESS by creating the NoSQL database in each runtime domain, see "Creating an ESS NoSQL Database".
To install the NoSQL client driver in each domain, see "Installing the ESS NoSQL Client Driver".
For more information about:
Using, changing, and provisioning the OCECAS data stores, see ”Working with Subscriber Data” in Evolved Communications Application Server Operator's Guide.
The NoSQL database software, see the Oracle NoSQL Database12c Release1 web site:
Securing your NoSQL database, see ”Securing the NoSQL Database” in Evolved Communications Application Server Security Guide.
NoSQL databases, see Oracle NoSQL Database Administrator's Guide 12c.
To store subscriber data in an ESS, create a NoSQL database on each machine that hosts an OCECAS runtime domain.
To see the list of supported NoSQL database software versions, see "Database Software".
To create a NoSQL database:
Log in to the target machine as the ocecas user. See "Creating a UNIX User for Installing OCECAS".
Download the Oracle NoSQL Database, Community Edition software from the Oracle Technology Network web site:
http://www.oracle.com/technetwork/database/database-technologies/nosqldb/downloads/nosql-downloads-1876643.html
Go to the directory where you downloaded the software, and unpack the archive file by entering the following command:
tar xfz kv-ce-3.0.14.gz
The kv-3.0.14 subdirectory is created.
Verify the installation by going to the kv-3.0.14 directory and entering the following command:
java -Xmx256m -Xms256m -jar lib/kvclient.jar
If installation was successful, you see something similar to the following:
12cR1.3.0.14 2013-11-11 12:09:35 UTC Build id: 912c25300b5e
For each runtime domain on your machine, copy the kvclient.jar file from the kv-3.0.14/lib directory to the Domain_home/lib directory:
cp kv-3.0.14/lib/kvclient.jar Domain_home/lib
Create your NoSQL database by running kvstore.jar. For example, to create and run a NoSQL database for testing purposes, enter the following command:
nohup java -jar kv-3.0.14/lib/kvstore.jar kvlite -host Hostname -store spr.data > nosql.log 2>&1 &
where Hostname is the name of the machine that is hosting your NoSQL database.
For more information, see "Installing Oracle NoSQL Database" in Oracle NoSQL Database Administrator's Guide.
To access subscriber data from your ESS, you must install the NoSQL Client driver on the management domain and each machine that hosts an OCECAS runtime domain. You must also modify the UDR view to query data directly from your ESS.
For details about the default view that OCECAS uses to configure subscriber data, see "Understanding How OCECAS Stores Subscriber Data" in Enhanced Communications Application Server Operator's Guide.
To see the list of supported NoSQL software versions, see "Database Software".
To install a NoSQL client driver:
Log in to the target machine as the ocecas user. See "Creating a UNIX User for Installing OCECAS".
Download the Oracle NoSQL Client Driver software from the Oracle Help Center website:
http://www.oracle.com/technetwork/database/database-technologies/nosqldb/downloads/nosql-downloads-1876643.html
Go to the directory where you downloaded the software, and unpack the archive file by entering the following command:
tar xfz kv-client-3.0.14.gz
The kv-3.0.14 subdirectory is created.
Verify the installation by going to the kv-3.0.14 directory and entering the following command:
java -Xmx256m -Xms256m -jar lib/kvclient.jar
If installation was successful, you see something similar to the following:
12cR1.3.0.14 2013-11-11 12:09:35 UTC Build id: 912c25300b5e
For each domain on your machine, copy the kvclient.jar file from the kv-3.0.14/lib directory to the Domain_home/lib directory:
cp kv-3.0.14/lib/kvclient.jar Domain_home/lib
Modify the view to query data directly from your ESS NoSQL database. For more information, see "Working with Subscriber Data" in Evolved Communications Application Server Operator's Guide.
After installing and configuring the domains, start the necessary servers on each domain:
To start the Administration Server:
Log in to the target system.
Go to the Domain_home/bin directory.
Enter the following command:
./startWebLogic.sh
If your domain uses a production startup mode, you are prompted for the login credentials of the Administrator user.
You can create a boot identity file to bypass the need to provide a user name and password when starting the Administration Server in production mode. For more information, see "Creating a Boot Identity File for an Administration Server" in Oracle Fusion Middleware Administering Server Startup and Shutdown for Oracle WebLogic Server.
For more information about starting the Administration Server, see "Starting and Stopping Administration Server" in Oracle Fusion Middleware Administering Oracle Fusion Middleware.
To start Node Manager:
Log in to the target system.
Go to the Domain_home/bin directory.
Enter the following command:
nohup ./startNodeManager.sh > nm.out&
Oracle recommends that you install Node Manager to run as a startup service, which allows Node Manager to start up automatically each time the system restarts. For more information about installing a per domain Node Manager service, see "Running Node Manager as a Startup Service" in Oracle Fusion Middleware Administering Node Manager for Oracle WebLogic Server.
Before starting a managed server for the first time, copy the Domain_home/security/SerializedSystemIni.dat file from the Administration Server to the same directory on each managed server.
To start a managed server:
Log in to the target system.
Go to the Domain_home/bin directory.
Enter the following command:
./startManagedWebLogic.sh managed_server_name admin_server_url
where:
managed_server_name is the name of the managed server that you want to start.
admin_server_url is the full URL of the Administration Server, as provided on the Configuration Success screen.
For more information about starting managed servers, see "Starting and Stopping Managed Servers" in Administering Oracle Fusion Middleware.
The following post-configuration tasks are required for the domains you have created:
Set your environment
Disable basic authentication
Create the EvolvedCommunicationUsers group. All user accounts that you create for the SDC GUI must belong to this group.
To configure your domain:
Log in to the machine that hosts the administration server for the domain.
Go to the Domain_home directory.
Set up the WLST environment:
. bin/setDomainEnv.sh
For more information, see http://docs.oracle.com/cd/E24329_01/web.1211/e24491/using_wlst.htm#WLSTG254.
Enter the following command:
java weblogic.WLST bin/setup.py
The script requires various configuration parameters, which it tries to obtain from the following sources, in order:
A properties file in the same directory as the setup.py script.
An environment variable
Directly from the user
Table 7-1 describes the parameters that the script requires. You can set these in a file called script.properties , a default version of which is created as part of the domain. You can also create them in an environment variable whose name has the form ECAS_group_setting, for example ECAS_db_host. If a setting is not provided in the file or in the environment variable, the script prompts the user for it.
| Parameter | Description |
|---|---|
|
admin.url |
The URL of the administration server. For example: t3://localhost:7001. |
|
admin.username |
The username for logging into the administration server. |
|
admin.password |
The password for logging into the administration server. |
|
mgmt.host |
The hostname of the management server. |
|
mgmt.username |
The username for logging into the management server. |
|
mgmt.password |
The password for logging into the management server. |
|
ldap.password |
The password to set for the embedded LDAP server. |
|
gui.username |
The name of a user to create for logging into the GUI (Session Design Center) or the REST API. |
|
gui.password |
The password to use for the GUI (Session Design Center) or the REST API user. |
|
db.host |
The hostname of the OCECAS database server. |
|
db.password |
The password for the OCECAS database user. |
|
realm |
The diameter realm that OCECAS will be part of. |
|
hss.hosts |
A comma-separated list of HSS definitions. Each entry has the form: address:hostname:port. For example: hss1:abc.com:localhost:3866, hss2.abc.com:localhost:3868. |
|
hss.realm |
The diameter realm that HSS is in. |
|
ocs.hosts |
A comma-separated list of OCS definitions. |
|
ocs.realm |
The diameter realm that the OCS is in. |
|
cdf.hosts |
A comma-separated list of CDF definitions. |
|
cdf.realm |
The diameter realm that CDF is in. |
You must perform this task only if you are using a NoSQL-based UDR, rather than a separate HSS.
These instructions explain how to configure communication between a runtime domain and the default NoSQL database as an ESS.
To configure communication between a runtime domain and the default NoSQL ESS:
Log in to the target machine.
Go to the Domain_home/lib directory.
Create a link to the NoSQL kvclient jar file. For example:
ln -s NoSQL_home/lib/kvclient.jar ./kvclient.jar
where NoSQL_home is the directory in which you installed the NoSQL client driver or installed the NoSQL database software. See "Setting up OCECAS for Subscriber Data" for more information.
Go to the Domain_home/config/custom directory.
Open the csp.xml file in a text editor.
Configure an <adapter> element to specify the ESS NoSQL database. The default database name is nosql1, and is of type NoSQLProvicerFactory. You can use these default values or change them for your implementation.
<name> is set to a name for the database.
<helper-host> is set to the host IP address and port number for your NoSQL database.
<store-name> is set to spr.data.
<adapters>
<no-sql-adapter>
<name>nosql1</name>
<helper-host>IP_address:port_no</helper-host>
<store-name>spr.data</store-name>
</no-sql-adapter>
</adapters>
Save and close the file.
Restart this domain to make your changes take effect.
Note:
Your ESS requires more configuration to work. For details, see "Advanced Configuration of Your ESS Subscriber Data Store" in Enhanced Communications Application Server Operator's Guide.You must perform this task only if you are using a NoSQL-based UDR, rather than a separate HSS.
To configure communication:
Log in to the target machine.
Go to the Domain_home/lib directory.
Create a link to the NoSQL kvclient jar file. For example:
ln -s NoSQL_home/lib/kvclient.jar ./kvclient.jar
where NoSQL_home is the directory in which you installed the NoSQL client driver or installed the NoSQL database software. See "Setting up OCECAS for Subscriber Data" for more information.
Go to the Domain_home/config/custom directory.
Open the csp.xml file in a text editor.
Ensure that the following elements are set correctly:
name is set to the correct name.
helper-host is set to the correct host IP address and port number for your NoSQL database.
store-name is set to spr.data.
<adapters>
<no-sql-adapter>
<name>nosql1</name>
<helper-host>IP_address:port_no</helper-host>
<store-name>spr.data</store-name>
</no-sql-adapter>
</adapters>
Save and close the file.
The domain setup script, setup.py, creates one user for logging in to the SDC GUI, but you can create more users to meet system requirements.
For more information about the SDC GUI, see "About the Session Design Center" in Evolved Communication Application Server Concepts.
To create a user for the SDC GUI:
Log in to the machine that hosts the management domain.
Ensure that your Administration Server has been started.
Navigate to the Administration Console and log in with your administrator user name and password:
http://hostname:port/console
where hostname is the IP address or name of the machine that hosts your management domain and port is the Administration Console access port number for your management domain.
In the Domain Structure pane on the left side, click Security Realms.
The Summary of Security Realms page appears.
In the Realms table, click myRealm.
The Settings for myrealm page appears.
Click the Users and Groups tab, and then click the Users subtab.
Click New.
The Create a New User page appears.
In the Name field, enter the user name for accessing the SDC GUI.
In the Password and Confirm Password fields, enter the password for the SDC GUI user.
Click OK.
In the Users table, click the SDC GUI user name that you created in step 8.
The Settings for UserName page appears.
Click the Groups tab.
In the Available pane, select EvolvedCommunicationUsers.
Click the right arrow button to move EvolvedCommunicationUsers to the Chosen pane.
Click Save.
Restart the Administration Server to make your changes take effect.
Configure OCECAS to provide authentication through an LDAP server or Oracle Identity Manager (OIM). For more information, see "Managing User Entities" in Evolved Communications Application Server System Administrator's Guide.
If you will be utilizing OCECAS service centralization or need to integrate with an MSC not enhanced for IMS Centralized Services (ICS), you have installed OCCAS-SC with the IM-PSX ETSI plugin.
You must complete the following configuration tasks to integrate OCCAS-SC with OCECAS:
Configure SSU SIP and SSU SS7 for OCCAS-SC. for information, see "Configuring a SIP Signaling Server Unit" in Oracle Communications Service Broker Signaling Server Units Configuration Guide.
Configure the Orchestration Engine for OCCAS-SC. For information, see Oracle Communications Service Broker Orchestration User's Guide.
Create instances of IM-SCF CAP2, IM-PSX ETSI plugin, and IM-ASF. For information, see "Setting Up IM-SCF CAP Phase 2", "Setting Up IM-ASF SIP", and "Setting Up IM-PSX ETSI Plugin" in Oracle Communications Service Broker Modules Configuration Guide.
Configure OCCAS-SC to use the IM-PSX ETSI plugin to pass messages from the HLR and the MSC to OCECAS, and from OCECAS to the HLR and the MSC.
To configure the IM-PSX ETSI plugin, see "Configuring OCECAS and OCCAS-SC Integration".
For additional information and configuration, see "Circuit Switched UE Origination" and "About Configuring IMS Centralized Services" in Oracle Communications Evolved Communications Application Server System Administrator's Guide.
Configure OCCAS-SC-related items in the OCECAS Administration console.
For information, see "About Configuring OCECAS for an MSC Not Enhanced for ICS" and "About Configuring IMS Centralized Services" in Oracle Communications Evolved Communications Application Server System Administrator's Guide.
Secure connections between OCCAS-SC and OCECAS (recommended only).
For information, see "Implementing OCECAS Security", particularly "Securing Ports", in Oracle Communications Evolved Communications Application Server Security Guide.
Provision subscribers in the HLR to ensure that the MSC triggers OCCAS-SC.
For information, see "About Configuring IMS Centralized Services" in Oracle Communications Evolved Communications Application Server System Administrator's Guide.
Provision the HLR to ensure that changes to Supplementary Service data are sent in MAP-NOTE-SUBSCRIBER-DATA-MODIFIED messages to OCCAS-SC.
After installing OCCAS-SC and the IM-PSX ETSI plugin, you must configure them to interact with each other and also configure SS7 protocol operations for NoteSubscriberDataModified, AnyTimeModification, and SendRoutingInfo.
These configuration procedures are specifically for enabling integration of OCCAS-SC and the IM-PSX ETSI plugin with OCECAS for ICS support. To complete the general configuration steps for integrating OCCAS-SC and the IM-PSX ETSI plugin, see "Setting Up IM-PSX ETSI Plugin" in Oracle Communications Service Broker Modules Configuration Guide.
To Configure the IM-PSX ETSI Plugin:
In the OCCAS-SC Administration Console, click the Platform tab.
In the OCSB tree, expand the Processing Tier and Interworking Modules nodes.
Click the impsxetsiplugin instance.
In the configuration panel, click the Configuration tab and then the General tab.
In the Local Alias text box, enter the SSN alias configured in SS7 SS7 Sigtran.
Click the Session Handling tab.
Enter the values shown for the fields listed in Table 7-2:
To configure SS7 protocol for NoteSubscriberDataModified in IM-PSX ETSI Plugin:
Go to axiaConsole in the OCCAS-SC Administration Console. For example:
https://ipadress:9000/axiaConsole
Where ipaddress is the IP address or hostname of the OCCAS-SC Administration Console.
Click the Domain Configuration tab.
Select Configuration MBeans, then com.convergin.wcs.osgi.im.psx.etsi.plugin.
Select 6.1.0, then IMPSXETSIPLUGIN, then ModuleInstance[0], then AseEncoding.
Click addOperation.
Expand the operation[0] node and set the attributes to the values shown in Table 7-3.
To Configure SS7 Protocol for AnyTimeModification in IM-PSX ETSI Plugin:
Go to axiaConsole in the OCCAS-SC Administration Console. For example:
https://ipadress:9000/axiaConsole
Where ipaddress is the IP address or hostname of the OCCAS-SC Administration Console.
Click the Domain Configuration tab.
Select Configuration MBeans, then com.convergin.wcs.osgi.im.psx.etsi.plugin.
Select 6.1.0, then IMPSXETSIPLUGIN, then ModuleInstance[0], then AseEncoding.
Click addOperation.
Expand the operation[1] node and set the attributes to the values shown in Table 7-4.
To configure SS7 protocol for SendRoutingInfo in IM-PSX ETSI Plugin:
Go to axiaConsole in the OCCAS-SC Administration Console. For example:
https://ipadress:9000/axiaConsole
Where ipaddress is the IP address or hostname of the OCCAS-SC Administration Console.
Click the Domain Configuration tab.
Select Configuration MBeans, then com.convergin.wcs.osgi.im.psx.etsi.plugin.
Select 6.1.0, then IMPSXETSIPLUGIN, then ModuleInstance[0], then AseEncoding.
Click addOperation.
Expand the operation[2] node and set the attributes to the values shown in Table 7-5.
If your installation is configured to use Secure Socket Layer (SSL) support, set the host name verification to None by using the WebLogic Server Administration Console.
To configure SSL host name verification:
Start your OCECAS Administration Server if it is not already running.
Navigate to the WebLogic Server Administration Console, and log in with your administrator user name and password:
http://hostname:port/console
where hostname is the name of your OCECAS server and port is the Administration Console access port number.
In the Domain Structure pane, expand Environment, and then click Servers.
In the Summary of Servers pane, click the Configuration tab.
For each of your servers in the Servers table, do the following:
Click the server name in the table, for example, AdminServer.
In the Settings for ServerName pane, click the SSL tab.
Expand the Advanced settings at the bottom of the pane.
From the Hostname Verification list, select None.
Click Save.
No restart is required after making this change.
If you created a clustered domain, enable the Coherence Security Framework. For instructions, see "Enabling the Oracle Coherence Security Framework" in Securing Oracle Coherence.
If you encountered any configuration issues, see "Troubleshooting an OCECAS Installation".