Initial Installation Procedure
The initial 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, refer to the Initial 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.1.1 Application Component
This section describes how to install the application component of Oracle Utilities Application Framework V4.5.0.1.1, including:
Copying and Decompressing Install Media
The Oracle Utilities Application Framework V4.5.0.1.1 installation file is delivered as a zip file for both UNIX and Windows platforms. If you are planning to install multiple Oracle Utilities Application Framework V4.5.0.1.1 environments operated by different Oracle Utilities administrator user IDs, you must complete the following installation steps for each administrator user ID.
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.1.1 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 downloaded application zip file to the <TEMPDIR>.
5. Decompress the file.
cd <TEMPDIR>
unzip -q <INSTALL MEDIA ZIP FILE NAME>
A sub-directory with name “FW-V4.5.0.1.1” 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.1.1 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 Application Framework environment on the server) and registers a new environment.
The generated script also changes the owner of /etc/cistab file to the Oracle Utilities Application Framework administrator user ID, so that the next time a new environment is created by the same Oracle Utilities Application 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.1.1.
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 <TEMPDIR>/App/FW.V4.5.0.1.1.
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 executing 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 are 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 Javadocs | 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 Javadocs 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> |
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.
Configuration of Oracle Fusion Middleware Components on a Separate Server from Oracle Utilities Market Settlements Management
This section applies to an Oracle Utilities Smart Grid Gateway configuration in which Oracle Service Bus (OSB) or Oracle SOA Suite is installed on a separate host from the Oracle Utilities Application Framework’s host. In this configuration, the Oracle Utilities installation scripts must have access to the libraries in the OSB and SOA servers' directories to deploy OSB projects and SOA composites successfully.
Follow these procedures to configure access to a remote OSB server:
• Create a network share to the osb folder within the Middleware Home on the remote OSB server.
• Provide the following values for Menu Item 8 (OSB Configuration) during the installation for Oracle Utilities Market Settlements Management:
• OSB Home is the location of the OSB folder, accessed by way of network share.
• OSB Host Server is the host name of the OSB server.
• OSB Port Number is the port of the OSB admin server.
• OSB SSL Port Number is the port of the OSB SSL admin server.
• OSB Managed Server Port Number is the port of the OSB managed server.
• OSB Managed Server SSL Port Number is the port of the OSB SSL managed server.
Follow these procedures to configure access to a remote SOA Suite server:
• Create a network share to the SOA folder within the Middleware Home on the remote SOA Suite server.
• Provide the following values for Menu Item 9 (SOA Configuration) during the installation for Oracle Utilities Service and Measurement Data Foundation.
• SOA Home is the location of the SOA folder, accessed by way of network share.
• SOA Host Server is the host name of the SOA managed server.
• SOA Port Number is the port of the SOA managed server.
• SOA SSL Port Number is the port of the SOA SSL managed server.
Installing the Oracle Utilities Meter Data Management V2.5.0.1.1 Application Component
This section describes how to install the Oracle Utilities Meter Data Management, including:
To proceed with the Oracle Utilities Meter Data Management installation you need to be connected to the target Oracle Utilities Application Framework environment.
You must initialize the Oracle Utilities Application Framework environment. For detailed instructions, refer to the
Installing the Oracle Utilities Application Framework V4.5.0.1.1 Application Component section.
Copying and Decompressing the Install Media
The Oracle Utilities Meter Data Management installation file is delivered in jar format for both UNIX and Windows platforms.
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 Meter Data Management V2.5.0.1.1 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.1.1 Multiplatform.zip to get the file MDM_V2.5.0.1.1.zip from the delivered package and copy to the <TEMPDIR>. To use FTP to transfer this file, use the BINARY option.
5. Decompress the file:
cd <TEMPDIR>
unzip MDM_V2.5.0.1.1.zip
cd App
For UNIX and Windows platforms, a sub-directory named MDM.V2.5.0.1.1 is created. 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 Meter Data Management Application Component
To install the Oracle Utilities Meter Data Management application component:
1. Login to the application server host as Oracle Utilities Application Framework Administrator (default cissys).
2. Change directory:
cd <install_dir>/bin
where <install_dir> is the location where the Oracle Utilities Application Framework application component is installed.
3. Initialize the environment by running the appropriate command:
UNIX
./splenviron.sh -e <ENV NAME>
Windows
splenviron.cmd -e <ENV NAME>
4. Navigate to <TEMPDIR>/MDM.V2.5.0.1.1 directory.
5. 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
6. Choose option P to proceed with the installation.
Note: The rest of the menu items can be ignored if you are installing only Oracle Utilities Meter Data Management.
The Oracle Utilities Meter Data Management installation is complete if no errors occurred during the installation.
Configuration of Oracle Fusion Middleware Components on a Separate Server from Oracle Utilities Service and Meter Data Management
This section applies to an Oracle Utilities Smart Grid Gateway configuration in which Oracle Service Bus (OSB) or Oracle SOA Suite is installed on a separate host from the Oracle Utilities Application Framework’s host. In this configuration, the Oracle Utilities installation scripts must have access to the libraries in the OSB and SOA servers' directories to deploy OSB projects and SOA composites successfully.
Follow these procedures to configure access to a remote OSB server:
• Create a network share to the osb folder within the Middleware Home on the remote OSB server.
• Provide the following values for Menu Item 8 (OSB Configuration) during the installation for Oracle Utilities Service and Measurement Data Foundation:
• OSB Home is the location of the OSB folder, accessed by way of network share.
• OSB Host Server is the host name of the OSB server.
• OSB Port Number is the port of the OSB admin server.
• OSB SSL Port Number is the port of the OSB SSL admin server.
• OSB Managed Server Port Number is the port of the OSB managed server.
• OSB Managed Server SSL Port Number is the port of the OSB SSL managed server.
Follow these procedures to configure access to a remote SOA Suite server:
• Create a network share to the SOA folder within the Middleware Home on the remote SOA Suite server.
• Provide the following values for Menu Item 9 (SOA Configuration) during the installation for Oracle Utilities Market Settlements Management.
• SOA Home is the location of the soa folder, accessed by way of network share.
• SOA Host Server is the host name of the SOA managed server.
• SOA Port Number is the port of the SOA managed server.
• SOA SSL Port Number is the port of the SOA SSL managed server.
Creating WebLogic Domain
Create the WebLogic native domain and deploy the application. For instructions refer to Native Installation Oracle Utilities Application Framework (Doc ID: 1544969.1) on My Oracle Support.
The MDB user configured in Menu 3 during the Oracle Utilities Application Framework installation has to be created in the application and WebLogic console, and should be part of the “cisusers” group.
Note: When starting Oracle Utilities Meter Data Management for the first time, log into the WebLogic console and provide system access to the cisusers role.