Demo Installation Procedure
The demo installation procedure consists of:
Installing the Database Component
Installation of the database component of Oracle Utilities Market Settlements Management must be complete before you can proceed with the following sections.
For instructions to install the database component with pre‑populated demo data, refer to the Demo Install section in the Oracle Utilities Market Settlements Management Database Administrator’s Guide.
Installing Application Components
A successful installation consists of the following steps:
Installing the Oracle Utilities Application Framework V4.5.0.0.0 Application Component
This section describes how to install the application component of Oracle Utilities Application Framework V4.5.0.0.0, including:
Copying and Decompressing Install Media
The Oracle Utilities Application Framework V4.5.0.0.0 installation file is delivered in jar format for both UNIX and Windows platforms. If you are planning to install multiple Oracle Utilities Application Framework V4.5.0.0.0 environments operated by different Oracle Utilities administrator user IDs, you must complete each of the following installation steps for each administrator userid.
To copy and decompress the install media:
1. Login to the application server host with the Oracle Utilities Application Framework administrator user ID.
2. Download the 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: To execute the “jar” command install the Java JDK.
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 UNIX
Every Oracle Utilities Application Framework environment installed on a server must be registered in the /etc/cistab file located on that server. On 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>/App/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 it is your responsibility to take a backup prior to the installation process. The installation utility does not create a backup of existing environment.
Installing the Application Component
This section outlines the steps for installing the application component of Oracle Utilities Application Framework V4.5.0.0.0.
1. Login to the Application Server host as administrator (the default is cissys on UNIX) or as a user with Administrator privileges (on Windows).
2. Change directory to the <TEMPDIR>/App/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.
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/bin/perlib>
export PERLLIB=${PERL_HOME}/lib:${PERL_HOME}/lib/site_perl:<OUAF
Installer Decompressed location/bin/perlib>
export LD_LIBRARY_PATH=${ORACLE_CLIENT_HOME}/lib:$LD_LIBRARY_PATH
Windows:
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 running the appropriate script.
UNIX:
ksh ./install.sh
Windows:
install.cmd
The Oracle Utilities Application Framework specific menu appears.
5. Follow the messages and instructions that are produced by the application installation utility.
7. Below is the mandatory list of configurable items along with descriptions for a few 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 | <Mandatory> |
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 | <Mandatory> |
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 Port | <Mandatory> |
Coherence Cluster Mode | prod<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 Meter Data Management V2.5.0.0.0 Application Component
This section describes how to install the application component of Oracle Utilities Market Settlements Management, including:
Copying and Decompressing Install Media
The Oracle Utilities Market Settlements Management installation file is delivered in jar format for both UNIX and Windows platforms.
Download the installation package and proceed as follows:
1. Login to the application server host with the Oracle Utilities Application Framework administrator user ID.
2. Download the Oracle Utilities Meter Data Management V2.5.0.0.0 Multiplatform.zip 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. Unzip Oracle Utilities Meter Data Management V2.5.0.0.0 Multiplatform.zip to get the file MDM_V2.5.0.0.0.zip from the delivered package and copy to the <TEMPDIR>. If you are using FTP to transfer this file, remember to use the BINARY option.
5. Decompress the file:
cd <TEMPDIR>
unzip MDM_V2.5.0.0.0.zip
cd App
Preparing for the Installation
1. Login as Oracle Utilities Application Framework Administrator (default cissys).
2. Initialize the Framework environment that you want to install the product into.
UNIX
$SPLEBASE/bin/splenviron.sh -e $SPLENVIRON
Windows
%SPLEBASE%\bin\splenviron.cmd -e %SPLENVIRON%
3. Stop the environment if running.
Installing the Application Component
1. Run the install script.
Note: On UNIX, ensure that you have the proper execute permission on install.sh.
UNIX
ksh ./install.sh
Windows
install.cmd
2. Select menu item 8 to configure OSB.
Use the completed OSB configuration worksheet to assist you in this step. See the Appendix B: Installation and Configuration Worksheets.
3. Select menu item 9 to configure SOA.
Use the completed SOA configuration worksheet to assist you in this step. See the Appendix B: Installation and Configuration Worksheets.
4. Select menu item 10 to configure the SOA Configuration Plan.
Use the completed SOA Configuration Plan worksheet to assist you in this step. See the Appendix B: Installation and Configuration Worksheets.
5. When you are done with the parameter setup, choose option P to proceed with the installation.
Note: The rest of the menu items can be ignored if you are installing only MDM.
The installation of Oracle Utilities Market Settlements Management server is complete if no errors occurred during installation.
6. Generate the appviewer.
a. Change the directory.
cd <install_dir>/bin
where <install_dir> is the Oracle Utilities Market Settlements Management application component installation directory.
b. Run the script to generate the appviewer.
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) white paper on My Oracle Support.
The MDB user configured in Menu 3 during the Oracle Utilities Application Framework installation has to be created in the Oracle Utilities Application Framework application and WebLogic console, and should be part of the “cisusers” group.
Note: When starting Oracle Utilities Market Settlements Management for the first time, log into the WebLogic console and provide system access to the cisusers role. Use the following URL to access the WebLogic console application: http://<hostname>:<portname>/ console.