This chapter describes how to run the Oracle Communications Evolved Communications Application Server (OCECAS) installation program.
Before you install OCECAS, complete all pre-installation tasks described in "OCECAS Pre-Installation Tasks".
After you complete all pre-installation tasks, install OCECAS by performing the following steps:
Run Oracle Universal Installer (OUI) to install OCECAS.
This includes installing OCECAS on the machine that will host your UDR domain, on the machines that will host your runtime domains, and on the machine that will host your management domain.
You can run the OCECAS installer in GUI mode or silent mode. Silent mode enables you to perform a non-interactive installation of OCECAS. Use silent mode to install OCECAS quickly on multiple systems.
For installation instructions, see the following sections:
Create and initialize the OCECAS and OPSS database repositories. The OCECAS database repository optionally can be remote – on a machine connected to the management domain:
If you installed Oracle database on the machine that hosts your management domain, you create the OCECAS and OPSS database repositories by running root.sh in the course of installing OCECAS.
If you installed Oracle database on a machine that is connected to your management domain, create your OCECAS and OPSS database repositories by running the sdc-db.sh script on that machine after installing OCECAS. See "Creating a Remote Database" for instructions.
Note:
This step initializes the OCECAS database repository but not the OPSS repository.Run the rcu utility to initialize the OPSS repository. See "Initializing the OPSS Repository" for instructions.
Note:
Typically, if you install OCECAS in GUI mode, you will run rcu in GUI mode. Likewise, if you install OCECAS in silent mode, you will run rcu in silent mode.Create and configure your OCECAS domains.
For information on creating and configuring your OCECAS domains, see "Creating and Configuring OCECAS Domains".
To run the installation program in GUI mode, the console attached to the machine on which you are installing the software must support a Java-based GUI.
To install OCECAS:
Log in to the machine on which you want to install OCECAS.
Download the OCECAS software from the Oracle software delivery website at:
Go to the directory where you downloaded the installation program and unzip the archive.
Launch the installation program by entering the following command from the JDK directory on your system:
java -jar ocecas_generic.jar
The installation program starts.
If no other Oracle products are installed on the system, the Installation Inventory screen appears. Specify the location where you want to create your central inventory. Make sure that the operating system group name selected on this screen has write permissions to the central inventory location.
For more information about the central inventory, see "Understanding the Oracle Central Inventory" in Oracle Fusion Middleware Installing Software with the Oracle Universal Installer.
If an Installation Inventory exists, the Installation Welcome screen appears.
Click Next.
The Installation Location screen appears.
Enter or browse to the directory in which to install the OCECAS software and then click Next.
The Installation Type screen appears.
Select Evolved Communications Application Server Installation, and then click Next.
The Prerequisite Checks screen appears.
The screen automatically tests your system to ensure that it meets all operating system and JDK software requirements:
A green check mark indicates that your system passed the prerequisite check.
A red circle indicates a problem. The bottom of the screen shows a short error message to help you troubleshoot the problem. Fix the error and click Rerun to perform the prerequisite checks again. To continue the installation without fixing the problem, click Skip.
Click Next.
The Security Updates screen appears.
If you already have a My Oracle Support account, use this screen to indicate how you would prefer to receive security updates: through email or through My Oracle Support.
If you do not have a My Oracle Support account and are sure that you want to skip this step, clear the check box and verify your selection in the follow-up dialog box.
Click Next.
The Installation Summary screen appears.
Verify the installation options you selected. If you want to save these options to a response file, click Save Response File and provide a location and name for the response file. Response files can be used later in a silent installation.
Note:
If you only want to save a response file, you can exit the installation now.Click Install to start the installation.
The Installation Progress screen appears, and a progress bar indicates the status of the installation process.
Note:
After the installation begins, if you click Cancel, the installation process stops but the files that are already copied are not removed.Click Next.
The Installation Instructions screen appears.
If you are installing OCECAS on a machine that will host a runtime or UDR domain, click Next and proceed to step 16.
If you are installing the Oracle database on a machine that is connected to the machine that will host the management domain, click Next and proceed to step 16. Then see "Creating a Remote Database".
If you are installing OCECAS on a machine that will host the management domain, open a command window and perform the following steps:
Log in as the ocecas user. See "Creating a UNIX User for Installing OCECAS".
Enter the following command to create the OCECAS database and schema:
./root.sh -d install
The script displays a series of prompts.
Warning:
Do not run root.sh in a shell spawned as a sub-process because the script will hang.
For more information about the root.sh script, see "About the OCECAS Database Creation Script"
At each prompt, answer the question and then press Enter. Table 5-1 describes each prompt.
Table 5-1 Root.sh Script Prompts
| Prompt | Description |
|---|---|
|
UNIX_USER |
Enter the name of the user you used to install the Oracle database software. Note that root.sh will not prompt for UNIX_USER if it is already set. |
|
UNIX_GROUP |
Enter the name of the group to which the UNIX user belongs. The default Oracle database group name is dba. Note that root.sh will not prompt for UNIX_GROUP if it is already set. |
|
ORACLE_BASE |
Enter the base directory of the Oracle database installation. The Oracle base directory is the initial portion of the installation path in a standard Oracle database installation. For example, /u01/app/oracle. Note that root.sh will not prompt for ORACLE_BASE if it is already set. |
|
ORACLE_HOME |
Enter the complete path to the Oracle database installation. For example, if ORACLE_BASE is /u01/app/oracle, ORACLE_HOME would be /u01/app/oracle/product/12.1.0/dbhome. Note that root.sh will not prompt for ORACLE_HOME if it is already set. |
|
sdc User Password |
Enter a password for the sdc user. The sdc user is the owner of the database that this script creates, and is used by OCECAS for all database operations. You will be prompted to enter this password twice. |
|
SYS User Password |
Enter the password for the Oracle database SYS user. The SYS user is an administrative user and is the owner of all database objects. For more information about the Oracle database SYS user, see "Administrative User Accounts" in Oracle Database Administrator's Guide. Note that you will be prompted to enter this password twice. |
|
SYSTEM User Password |
Enter the password for the Oracle database SYSTEM user. The Oracle database SYSTEM user is the master database administrator user with access to all of the database objects. For more information about the Oracle database SYSTEM user, see "Administrative User Accounts" in Oracle Database Administrator's Guide. You will be prompted to enter this password twice. |
|
SDC_ADMIN User Password |
Enter a password for the SDC_ADMIN user. The SDC_ADMIN user has the full set of administrator privileges and can create tables, views, triggers, and so on. You will be prompted to enter this password twice. |
|
sdc_opss user password |
Enter the password for the sdc_opss user. The sdc_opss user is the owner of the OPSS database schema. You will be prompted to enter this password twice. For more information about OPSS users, see Securing Applications with Oracle Platform Security Services. |
Ensure that the Oracle database listener is running.
To start the Oracle database listener, enter the following command:
DB_Oracle_home/bin/lsnrctl start
where DB_Oracle_home is the directory in which you installed the Oracle database software. For more information about starting the listener, see "Listener Control Utility" in Oracle Database Net Services Reference.
Initialize the OPSS repository by following the procedures in "Initializing the OPSS Repository".
Return to the GUI installer screen and click Next.
In the Installation Complete screen, perform one of the following:
Select the Automatically Launch the Configuration Wizard check box on this screen. After you click Finish to close the installer, the configuration wizard is started and you can begin to configure your domain. If you choose to do this, proceed to "Creating Domains Using the Graphical Domain Configuration Wizard".
Deselect the Automatically Launch the Configuration Wizard check box on this screen. After you click Finish to close the installer, manually start the configuration wizard to begin configuring your domain. If you choose to do this, proceed to "Starting the Domain Configuration Wizard".
Silent mode is a way of setting installation options once and then using those settings to duplicate the installation on many machines. The installation program reads your settings from a Response File that you create prior to beginning the installation. The installation program does not display any options during the installation process.
For general information about silent installation for Oracle products, see "Running the Installation Program in Silent Mode" in Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server.
The entries in the Response File (response.rsp) correspond to the prompts that you would see if you used GUI mode. You can create a response file by installing OCECAS in GUI mode and saving a response file in the process. You can continue the installation in GUI mode and save the response file for subsequent installations or you can stop once you've saved the response file and use it to perform a silent installation. You can also obtain a response file from someone else who has created one.
Incorrect entries in response.rsp can cause installation failures. To help you determine the cause of a failure, Oracle recommends that you create a log file when you start the installation.
The following example shows a sample version of a response.rsp file, which is a plain text file. Your input may be slightly different, depending on your installation.
[ENGINE]
#DO NOT CHANGE THIS.
Response File Version=1.0.0.0.0
[GENERIC]
#The oracle home location. This can be an existing Oracle Home or a new Oracle Home
ORACLE_HOME=Ocecas_home
#Set this variable value to the Installation Type selected. e.g. Session Design and Control.
INSTALL_TYPE=Evolved Communications Application Server
#Provide the My Oracle Support Username. If you wish to ignore Oracle Configuration Manager configuration provide empty string for user name.
MYORACLESUPPORT_USERNAME=
#Provide the My Oracle Support Password
MYORACLESUPPORT_PASSWORD=<SECURE VALUE>
#Set this to true if you wish to decline the security updates. Setting this to true and providing empty string for My Oracle Support username
will ignore the Oracle Configuration Manager configuration
DECLINE_SECURITY_UPDATES=true
#Set this to true if My Oracle Support Password is specified
SECURITY_UPDATES_VIA_MYORACLESUPPORT=false
#Provide the Proxy Host
PROXY_HOST=
#Provide the Proxy Port
PROXY_PORT=
#Provide the Proxy Username
PROXY_USER=
#Provide the Proxy Password
PROXY_PWD=<SECURE VALUE>
#Type String (URL format) Indicates the OCM Repeater URL which should be of the format [scheme[Http/Https]]://[repeater host]:[repeater port]
COLLECTOR_SUPPORTHUB_URL=
The silent installation program generates exit codes that indicate the success or failure of the installation. Table 5-2 describes these exit codes:
Table 5-2 Installation Program Exit Codes
| Code | Description |
|---|---|
|
0 |
Installation completed successfully. |
|
-1 |
Installation failed due to a fatal error. |
|
-2 |
Installation failed due to an internal XML parsing error. |
If you start the silent installation process from a script, you can have these exit codes displayed to the console. Example 5-1 shows a sample command file that runs the installation while in silent mode and echoes the exit codes to the console from which the script is executed.
rem Execute the installer in silent mode @echo off java -jar ocecas_generic.jar -silent -responseFile=/home/use/bin/response.rsp -log=logfilename @rem Return an exit code to indicate success or failure of installation set exit_code=%ERRORLEVEL% @echo. @echo Exitcode=%exit_code% @echo. @echo Exit Code Key @echo --------------- @echo 0=Installation completed successfully @echo -1=Installation failed due to a fatal error @echo -2=Installation failed due to an internal XML parsing error @echo.
To install OCECAS in silent mode:
Log in to the target system.
Download the OCECAS software from the Oracle software delivery website at:
Create a response file, as described in "About the Response File".
Go to the directory where you downloaded the OCECAS software.
Start the installer by entering the following command:
java -jar ocecas_generic.jar -silent -responseFile ResponseFile
The OCECAS Installer checks for all required software and writes errors to a log file if it detects any missing or unavailable components, or if there are any connectivity-related issues.
If you installed the Oracle database on a machine that is connected to the machine that will host the management domain, skip to step 7. After you finish installing OCECAS, see "Creating a Remote Database" for instructions on creating the Oracle database and schema.
If you are installing OCECAS on the machine that will host the management domain, and you installed the Oracle database on this machine, perform the following additional steps:
When prompted, run the root.sh script from the Ocecas_home directory:
root.sh -d install -u unixUser -g dbGroup -b oracleBaseDir -h DB_Oracle_home -i dbInstance
For more information about the script and its parameters, see "Script Syntax and Options".
When prompted, enter passwords for the sdc user, SYS user, SYSTEM user, SDC_ADMIN user, and sdc_opss user.
When the root.sh script completes, ensure that the Oracle TNSListener has started by entering the following command:
DB_Oracle_home/bin/lsnrctl start
Note that running root.sh initializes the OCECAS database but not the OPSS database. See "Initializing the OPSS Repository" to initialize the OPSS repository after completing this procedure.
Check whether the installer completed successfully by retrieving the exit codes, as described in "Returning Exit Codes to the Console".
As part of the OCECAS installation process, you must run the database creation script, which creates the following entities:
An Oracle database instance named SDC.
The OCECAS database schema.
A database user named sdc. This account is used to access the data in the SDC database.
A database administrative user named SDC_ADMIN. This user owns the database schema and has administrator privileges.
If you installed the Oracle database on the machine that hosts the management domain, you run the root.sh script while installing OCECAS. For information on the syntax and options see "Script Syntax and Options".
If you installed Oracle database on a machine that is connected by Transparent Network Substrate (TNS) or Java Database Connectivity (JDBC) to the machine that hosts your management domain, you must run the sdc-db.sh script instead of root.sh to create your remote Oracle database and schema. See "Creating a Remote Database" for instructions.
If you installed Oracle database on a machine that is connected to the machine that hosts your management domain, perform these steps to create the database and schema:
Locate the scripts directory. For example:
Ocecas_home/wlserver/csp/installation/scripts
Create a .zip file of the directory.
Copy the .zip file to the machine where the remote database is located and to a directory like that where it was originally located. For example:
Ocecas_home/wlserver/csp/installation/scripts
Unpack the .zip file.
Change directories to the location of the sdc-db.sh script. For example:
Ocecas_home/wlserver/csp/installation/scripts/sdc-db.sh
Run the sdc-db.sh script.
The syntax and options for running sdc-db.sh are the same as for root.sh. For information, see "Script Syntax and Options".
Note that running sdc-db.sh initializes only the OCECAS database. You must also initialize the OPSS database. See "Initializing the OPSS Repository" for instructions on initializing the OPSS repository.
The root.sh and sdc-db.sh scripts use the following syntax, where script is a placeholder for the name of the script:
script.sh -d install| remove -u unixUser -g dbGroup -b oracleBaseDir -h DB_Oracle_home -i dbInstance
The script accepts a number of command-line arguments. If you do not include any arguments, the script prompts for the required values. The script automatically prompts you for passwords for the sdc, sdc_admin, SYS, and SYSTEM user accounts.
Table 5-3 describes the command-line options for root.sh in detail.
Table 5-3 root.sh Command Line Options
| Command Flag | Description |
|---|---|
|
-d install|remove |
When set to install, the script creates an OCECAS Oracle instance. When set to remove, the script removes the OCECAS Oracle instance. |
|
-u unixUser |
The name of the UNIX user you used to install OCECAS and the Oracle database software. See "Creating a UNIX User for Installing OCECAS". |
|
-g dbGroup |
The name of the group to which the UNIX user belongs, for example, dba. |
|
-b oracleBaseDir |
The base directory of the Oracle database software. The Oracle base directory is the initial portion of the installation path that terminates before /product/12.1.0/dbhome in a standard Oracle database software installation. |
|
-h DB_Oracle_home |
The complete path to the Oracle database installation, for example, oracleBaseDir/product/12.1.0/dbhome. |
|
-i dbInstance |
The database instance number. |
The following steps are required to initialize Oracle Platform Security Services (OPSS) for OCECAS. These steps run a utility called rcu (repository creation utility).
OPSS stores its security information in its own schema in the database. You must create this schema and load the required data into the OPSS database before you create the WebLogic domains. Otherwise, the domains will not start.
You must complete these steps as follows:
After running root.sh and before step 15f when installing OCECAS in GUI Mode. See "Installing OCECAS in GUI Mode" for more information.
Or, after running root.sh and completing the procedure to install OCECASE in silent mode. See (UNKNOWN STEP NUMBER) "Installing OCECAS in Silent Mode" for more information.
Or after running sdc-db.sh to create a remote database, if you are creating a remote database. See "Creating a Remote Database" for more information.
Note:
You run this procedure on the machine where WebLogic is installed. The machine connects to the database, which may be on the same machine, or on a different machine, in which case it connects by way of the listener.Follow these steps to initialize the OPSS repository in GUI mode:
Ensure that the JAVA_HOME and ORACLE_HOME environment variables are set for your environment. If necessary, adjust the values shown in the following example to the values you are using:
su - ocecas JAVA_HOME=/usr/java/latest ORACLE_HOME=/middleware/ocecas/oracle/product/12.1.0 export JAVA_HOME ORACLE_HOME
If it is not already running, start the Oracle database listener by entering the following command:
DB_Oracle_home/bin/lsnrctl start
Locate rcu, the repository creation utility. For example:
cd Ocecas_home/oracle_common/bin
Note:
Ocecas_home is the same directory you chose in step 6 of "Installing OCECAS in GUI Mode" or that you specified in the Response file, if you are running the installer in silent mode.Run the following command to start the Oracle Repository Creation utility in graphical, interactive mode:
./rcu
On the Welcome screen, click Next.
On the Repository Creation Utility screen, select Create Repository option button and the sub-item System Load and Product Load option button. Then click Next.
On the Database Connection Details screen, enter the specified values for the following entries:
Table 5-4 Entries for Database Connection Details
| Entry | Value |
|---|---|
|
Database Type |
Select Oracle Database from the menu list. |
|
Host Name |
Enter the host name of your host. |
|
Port |
Enter port number 1521. |
|
Service Name |
Enter SDC. |
|
Username |
Enter sys. |
|
Password |
Enter the password for user sys. |
|
Role |
Select SYSDBA from the menu list. |
Then click Next.
On the Select Components screen, select the following schemas under Oracle AS Repository Components -> AS Common Schemas:
Audit Services
Audit Services Append
Audit Services Viewer
Oracle Platform Security Services
Then click Next.
On the Schema Passwords screen, enter and confirm the password to use for all schemas. Then click Next.
On the Map Tablespaces screen, review the list of components, which should include the following:
Audit Services
Audit Services Append
Audit Services Viewer
Oracle Platform Security Services
Common Infrastructure Services
Click Next.
On the Confirmation dialog, click OK to create the tablespaces.
On the Creating Tablespaces progress dialog, click OK when the operation has completed.
On the Summary page, click Create to create the listed components.
The Completion Summary screen appears once the components have been created.
Click Close on the Completion Summary screen to complete creation of the Oracle repository.
Initializing the OPSS repository in silent mode consists of the following two steps:
Creating the OPSS schema
Performing a data load to initialize the database
Perform these steps to create and load the OPSS repository in silent mode:
Ensure that the JAVA_HOME and ORACLE_HOME environment variables are set for your environment. For example:
su - ocecas JAVA_HOME=/usr/java/latest ORACLE_HOME=/middleware/ocecas/oracle/product/12.1.0 export JAVA_HOME ORACLE_HOME
Locate rcu, the repository creation utility. For example:
cd Ocecas_home/oracle_common/bin
Note:
Ocecas_home is the same directory you chose in step 6 of "Installing OCECAS in GUI Mode" or that you specified in the Response file, if you are running the installer in silent mode.Enter the following command to run rcu in silent mode:
rcu -silent -dataLoad -databaseType ORACLE -connectString localhost:1521:SDC -dbUser sys -dbRole sysdba -schemaPrefix SDC -component OPSS
When prompted, enter the password for user sys, followed by the password for sdc_opss.
Note:
The passwords for sys and sdc_opss must match the passwords you specified when running root.sh or sdc-db.sh. See Table 5-1 for more information.The following example shows sample output from running rcu in silent mode:
Please enter the database password(User:sys): Processing command line .... Repository Creation Utility - Checking Prerequisites Checking Global Prerequisites Please enter the schema password for [SDC_OPSS]: Repository Creation Utility - Checking Prerequisites Checking Component Prerequisites Repository Creation Utility - Data Load Repository Data Load in progress. Percent Complete: xxx Repository Creation Utility: Data Load - Completion Summary Database details: Host Name : localhost Port : 1521 Service Name : SDC Connected As : sys Prefix for (prefixable) Schema Owners : SDC RCU Logfile : Ocecas_home/oracle_common/rcu/log/logdir.2015-10-29_21-38/rcu.log Component schemas data loaded: Component Status Logfile Oracle Platform Security Services Success Ocecas_home/oracle_commonrcu/log/logdir.2015-10-29_21-38/opss.log
Now that OCECAS is installed, you need to create and configure the domains it requires. See "Creating and Configuring OCECAS Domains" for instructions.