Initial Installation Procedure
The initial installation procedure consists of:
Installing the Database Component
Installation of the database component of Oracle Utilities Operational Device Management must be complete before you can proceed with the following sections. Refer to the “Initial Install” section in the Oracle Utilities Operational Device Management Database Administrator’s Guide, which provides instructions on installing the database component.
Installing the Application Components
A successful installation consists of the following steps:
Installing the Oracle Utilities Application Framework Application Component V4.5.0.0.0
This section describes how to install the application component of Oracle Utilities Application Framework, including:
Copying and Decompressing Install Media for the Oracle Utilities Application Framework Application Component
The Oracle Utilities Application Framework installation file is delivered in jar format for both Linux, UNIX and Windows platforms. If you are planning to install multiple Oracle Utilities Application Framework environments operated by different Oracle Utilities administrator user IDs, you must complete each of the following installation steps for each administrator user ID.
To copy and decompress the install media, follow these steps:
1. Login to the application server host with the Oracle Utilities Application Framework administrator user ID.
2. Download “Oracle Utilities Application Framework v4.5.0.0.0 Multiplatform” from Oracle Software Delivery Cloud.
3. Create a temporary directory such as c:\ouaf\temp or /ouaf/temp. (Referred to below as <TEMPDIR>.)
Note: This directory must be located outside any current or other working Oracle Utilities application environment. All files that are placed in this directory as a part of the installation can be deleted after completing a successful installation.
4. Copy the file “FW-V4.5.0.0.0-Multiplatform.jar” from the delivered package to the <TEMPDIR>. If you are using FTP to transfer this file, remember to use the BINARY option for the FTP transfer.
5. Decompress the file:
cd <TEMPDIR>
jar -xvf FW-V4.5.0.0.0-Multiplatform.jar
Note: You will need to have Java JDK installed on the machine used to (un)jar the application server installation package. Please install the JDK that is supported for the install on your platform to be able to use the jar command.
Java packages are located at: http://www.oracle.com/technetwork/java/archive-139210.html
A sub-directory named “FW.V4.5.0.0.0” is created. It contains the installation software for the Oracle Utilities framework application server.
Setting Permissions for the cistab file in Linux/UNIX for the Oracle Utilities Application Framework Application Component
Every Oracle Utilities Application Framework environment installed on a server must be registered in the /etc/cistab file located on that server. On Linux/UNIX servers, generally only the root user ID has write permissions to the /etc directory. Since the installation process is run by the Oracle administrator user ID (cissys), this user ID may not be able to write to /etc/cistab table.
The install utility checks permissions and if it identifies a lack of the necessary permissions, it generates a script in the <TEMPDIR>/FW.V4.5.0.0.0 directory named cistab_<SPLENVIRON>.sh. Run the generated script using the root account before continuing with the installation process. The script initializes the cistab file in /etc directory (if it is the first Oracle Utilities Framework application environment on the server) and registers a new environment.
The generated script also changes the owner of /etc/cistab file to the Oracle Utilities Framework administrator user ID, so that the next time a new environment is created by the same Oracle Utilities Framework administrator user ID, you do not need to run the generated script with the root user ID. Instead the install utility itself proceeds with the registration.
If you are reinstalling an existing environment, only the validation of /etc/cistab entry is done by the install utility, no new registration occurs. The install utility interactively instructs you about every step that needs to occur in each specific case.
If you are planning to upgrade an existing environment you should take a backup first. The installation utility does not create an automatic backup of the existing environment.
Installing the Oracle Utilities Application Framework Application Component
This section outlines the steps for installing the application component of Oracle Utilities Application Framework.
1. Login to the Application Server host as administrator user ID (the default is cissys on Linux/UNIX) or as a user with administrator privileges (on Windows).
2. Change directory to the <TEMPDIR>/FW.V4.5.0.0.0 directory.
3. Set the ORACLE_CLIENT_HOME and PATH variables as Oracle Client Perl is required to run the installer.
Linux/UNIX
export ORACLE_CLIENT_HOME=<ORACLE CLIENT INSTALL LOCATION>
export PERL_HOME=${ORACLE_CLIENT_HOME}/perl
export PATH=${PERL_HOME}/bin:$PATH
export PERL5LIB=${PERL_HOME}/lib:${PERL_HOME}/lib/site_perl:<OUAF
Installer Decompressed location/data/bin/perlib>
export PERLLIB=${PERL_HOME}/lib:${PERL_HOME}/lib/site_perl:<OUAF
Installer Decompressed location/data/bin/perlib>
export LD_LIBRARY_PATH=${ORACLE_CLIENT_HOME}/lib:$LD_LIBRARY_PATH
Windows Server
set ORACLE_CLIENT_HOME=<ORACLE CLIENT INSTALL LOCATION>
set PERL_HOME=%ORACLE_CLIENT_HOME%\perl
set PATH=%PERL_HOME%\bin;%PATH%
4. Start the application installation utility by executing the appropriate script.
If you are upgrading from V2.3.0.0.0, the -u option can be used (take a backup of $SPLEBASE before proceeding).
Linux/UNIX
ksh ./install.sh -u
Windows Server
install.cmd -u
Note: The upgrade install does not clean library files that were removed from the latest version.
If you are upgrading from V2.2.0.6.0 to V2.4.0.0.0, it is recommended to do a fresh installation.
Linux/UNIX
ksh ./install.sh
Windows Server
install.cmd
5. The Oracle Utilities Application Framework specific menu displays.
6. Follow the messages and instructions that are produced by the application installation utility.
The table below lists the mandatory configurable items. Where you see <Mandatory>, enter values suitable to your environment.
You can assign default values to the rest of the menu items.
************************************
* Environment Installation Options *
************************************
1. Environment ID, Roles, Third Party Software Configuration
Environment ID | <Default> |
Server Roles | batch, online |
Oracle Client Home Directory | <Mandatory for Initial Install> |
Web Java Home Directory | <Mandatory for Initial Install> |
Hibernate JAR Directory | <Mandatory for Initial Install> |
ONS JAR Directory | <Optional> |
Web Application Server Home Directory | <Mandatory for Initial Install> |
Additional JAR Directory | <Optional> |
2. Keystore Options
Import Keystore Directory | <Default> |
50. Environment Installation Options
Environment Mount Point | <Mandatory> |
Log Files Mount Point | <Mandatory> |
Environment Name | <Mandatory> |
Install Application Viewer Module | true |
Install Sample CM Source Code | true |
Each item in the above list should be configured for a successful install.
Choose option (1,2,50, <P> Process, <X> Exit):
Once you enter 'P' after entering mandatory input values in the above menu, the system populates another configuration menu.
***********************************************************
* Environment Configuration *
***********************************************************
1. Environment Description
Environment Description | <Mandatory> |
2. Business Application Server Configuration
Business Server Host | <Mandatory> - Hostname on which application being installed |
Business Server Application Name | SPLService |
3. Web Application Server Configuration
Web Server Host | <Mandatory> |
WebLogic SSL Port Number | <Mandatory> |
WebLogic Console Port Number | <Mandatory> |
Web Context Root | ouaf |
WebLogic JNDI User ID | <Mandatory> |
WebLogic JNDI Password | <Mandatory> |
WebLogic Server Name | myserver |
Web Server Application Name | SPLWeb |
Deploy Application Viewer Module | true |
Enable The Unsecured Health Check Service | false |
MDB RunAs User ID | <Optional> |
Super User IDs | <Mandatory> |
4. Database Configuration
Application Server Database User ID | <Mandatory> |
Application Server Database Password | <Mandatory> |
XAI Database User ID | <Mandatory> |
XAI Database Password | <Mandatory> |
Batch Database User ID | <Mandatory> |
Batch Database Password | <Mandatory> |
Web JDBC DataSource Name | <Optional> |
Database Name | <Mandatory> |
Database Server | <Mandatory> |
Database Port | 1521 |
ONS Server Configuration | <Optional> |
Database Override Connection String | <Optional> |
Character Based Database | false |
Oracle Client Character
Set NLS_LANG | AMERICAN_AMERICA.AL32UTF8 |
5. General Configuration Options
Batch RMI Port | <mandatory> |
RMI Port number for JMX Business | <optional> |
RMI Port number for JMX Web | <optional> |
JMX Enablement System User ID | <optional> |
JMX Enablement System Password | <optional> |
Coherence Cluster Name | <mandatory> |
Coherence Cluster Address | <mandatory> |
Coherence Cluster Mode | prod<Mandatory> |
Coherence Cluster Port | <Mandatory> |
6. OUAF TrustStore Options
Import TrustStore Directory | <Mandatory> for Prod |
Each item in the above list should be configured for a successful install.
Choose option (1,2,3,4,5,6 <P> Process, <X> Exit):
8. When the parameter setup is complete, proceed with the option P. The utility writes the configured parameters and their values into the configuration file.
9. Once the install or upgrade has finished, the installation log location is displayed on the screen. If the log does not list any error messages, the installation of the application component of Oracle Utilities Application Framework is complete.
Installing the Oracle Utilities Operational Device Management Component
This section describes how to install the application component of Oracle Utilities Operational Device Management, including:
Copying and Decompressing Oracle Utilities Operational Device Management Install Media
The Oracle Utilities Operational Device Management installation file is delivered in jar format for both Linux/UNIX and Windows platforms.
To copy and decompress the install media, follow these steps:
1. Log in to the application server host as the administrator user ID (default cissys). This is the same user ID that was used to install the Oracle Utilities Application Framework.
2. Download the Oracle Utilities Work and Asset Management v2.4.0.0.0 Multiplatform zip file from Oracle Software Delivery Cloud.
3. Create a <TEMPDIR> directory on the host server, which is independent of any current or other working Oracle Utilities Operational Device Management application environment.
This can be the same <TEMPDIR> used during the installation of the Oracle Utilities Application Framework.
4. Copy the file, WAM-V2.4.0.0.0-Multiplatform.jar, in the delivered package to a <TEMPDIR> on your host server. If you are using FTP to transfer this file, remember to use the BINARY option for the FTP transfer.
5. Decompress the file:
cd <TEMPDIR>
jar -xvf WAM-V2.4.0.0.0-Multiplatform.jar
For Windows installations, include the location of the JDK in your path before you execute the jar command.
A sub-directory named W1.V2.4.0.0.0 is created for both Linux, Unix and Windows platforms. The contents of the installation directory are identical for both platforms. The directory contains the install software for the application product.
Installing the Oracle Utilities Operational Device Management Application Component
Follow these steps to install the Oracle Utilities Operational Device Management application component:
1. Login to the application server host as the administrator user ID (default cissys).
2. Change directory:
cd <install_dir>
where <install_dir> is the location where the Oracle Utilities Application Framework v4.5.0.0.0 base application component is installed.
3. Initialize the environment by running the appropriate command:
Linux/UNIX
./splenviron.sh -e <ENV NAME>
Windows
splenviron.cmd -e <ENV NAME>
4. Change to the <TEMPDIR>/W1.V2.4.0.0.0 directory.
where <install_dir> is the Oracle Utilities Operational Device Management Application Component installation directory.
Note: On Linux/UNIX, make sure that you have the proper execute permission on install.sh.
UNIX
ksh ./install.sh
Windows Server
install.cmd
5. Initialize the environment by running the appropriate command:
Linux/UNIX
./splenviron.sh -e <ENV NAME>
Windows Server
splenviron.cmd -e <ENV NAME>
6. Generate the appviewer by following these steps.
a. Change the directory.
cd <install_dir>/bin
where <install_dir> is Oracle Utilities Work and Asset Management Application Component installation directory.
b. Run the script to generate the appviewer.
Linux/UNIX
ksh ./genappvieweritems.sh
Windows
genappvieweritems.cmd
Creating WebLogic Domain
Create the WebLogic native domain and deploy the application. For instructions refer to the Native Installation Oracle Utilities Application Framework (Doc ID: 1544969.1) document on My Oracle Support.
Creating Users (WAMUSER and ODMUSER)
To create WAMUSER and ODMUSER users:
Note: These steps must be executed after creating the domain.
1. Login to WebLogic Admin console as a Admin user.
2. Navigate to Security Realms > myrealm.
3. Click Users and Groups.
4. On the Users tab, click New.
5. On the Create a New User tab, enter the Name, Description, and Password details in the respective fields.
6. Click OK.
A new user is created.
7. Click Groups.
8. Add the user created in step 6 to cisusers group.