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:
Install OCECAS on the machine that will host your UDR domain.
Install OCECAS on the machines that will host your runtime domains.
Install OCECAS on the machine that will host your management domain.
Create your OCECAS database and schema by running the root.sh script 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:
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.
If you plan to create a domain immediately after installing OCECAS, 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.
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 17.
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".
Ensure that ORACLE_BASE and ORACLE_HOME are not defined in your environment.
Enter the following command to create the OCECAS database and schema:
./root.sh -d install
The script displays a series of prompts.
Note:
Do not run root.sh in a shell spawned as a sub-process; otherwise, 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. |
|
UNIX_GROUP |
Enter the name of the group to which the UNIX user belongs. The default Oracle database group name is dba. |
|
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. |
|
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. |
|
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. 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. You will be prompted to enter this password twice. |
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.
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 shows a sample version of a response.rsp 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=
See Oracle WebLogic Server Installation Guide for more information.
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 are installing OCECAS on the machine that will host the management domain, 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 "About the OCECAS Database Creation Script".
When prompted, enter passwords for the sdc user, SYS user, SYSTEM user, and SDC_ADMIN 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
Check whether the installer completed successfully by retrieving the exit codes, as described in "Returning Exit Codes to the Console".
During the OCECAS installation process, you must run the root.sh script on the machine that hosts the management domain.
The script creates the following:
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.
The root.sh script is located in Ocecas_home and uses the following syntax:
root.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. |
Now that OCECAS is installed, you need to create and configure the domains it requires. See "Creating and Configuring OCECAS Domains" for instructions.