Oracle Utilities Meter Data Management

Installation Guide

E80249-02

April 2017(Updated July 2017)

Oracle Utilities Meter Data Management Installation Guide

Copyright © 2000, 2017 Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Introduction

This chapter provides an overview of the installation of Oracle Utilities Meter Data Management.

•

Installation Overview

•

Application Architecture

•

Installation Components

•

Installation Types

•

Media Pack Components

Installation Overview

Installing Oracle Utilities Meter Data Management involves the following steps:

1.

Review the different tiers of the application architecture as described in the Application Architecture section of this chapter.

2.

Understand the hardware requirements for installing the application and the supported platforms for the application and database servers as described in the Supported Platforms and Hardware Requirements section.

Note: The installation and administration of the database server tier is described in detail in the document Oracle Utilities Meter Data Management Database Administrator Guide.

3.

Plan your installation as described in the Planning the Installation section. This chapter includes lists of the required software for each supported combination of operating system and application server.

4.

Install all required third-party software as described in the Installing Prerequisite Software section.

5.

Install the database as described in the Oracle Utilities Meter Data Management Database Administrator Guide.

6.

Install the framework for the application.

7.

Install the Oracle Utilities Service and Measurement Data Foundation for the application.

8.

Install Oracle Utilities Meter Data Management.

9.

Follow the installation guidelines described in the Additional Tasks section.

The following diagram provides an overview of the steps that need to be taken to install and configure Oracle Utilities Meter Data Management:

Refer to My Oracle Support for up-to-date additional information on Oracle Utilities Meter Data Management installation.

Application Architecture

The Oracle Utilities Meter Data Management application is deployed on multiple tiers.

Please see the Oracle Utilities Meter Data Management Server Administration’s Guide for a more detailed description of the application architecture and individual tiers.

Tier 1: Desktop/Client, or Presentation Tier

This tier is implemented in a browser-based client. Users use a desktop client Web browser to log in to and use the Oracle Utilities Meter Data Management application. Note also that a desktop machine running Microsoft Windows and the Oracle client is required to perform some of the Oracle Utilities Meter Data Management product installation steps.

Tier 2: Web Application Server, Business Application Server, Batch Server Tier

This tier is implemented in a Web application server, business application server, or the batch server. The business application component can be installed as part of the Web application server, or as a separate component. Except where explicitly noted, most of the Oracle Utilities Meter Data Management installation documentation assumes that the Web application and business application servers reside together. The batch infrastructure will also run within this tier. You can have multiple batch server instances that serve the application.

Tier 3: Database, or Persistence Tier

This tier is implemented in a database server. The database server stores data maintained by the Oracle Utilities Meter Data Management application. More specifically, the database tier contains the data server files and database executables that physically store the tables, indexes, and other database objects for your system.

Installation Components

The Oracle Utilities Meter Data Management product installation consists of the following components:

•

Database Components

•

Oracle Utilities Application Framework database

•

Oracle Utilities Service and Measurement Data Foundation database

•

Oracle Utilities Meter Data Management database

•

Application Components

•

Oracle Utilities Application Framework application

•

Oracle Utilities Service and Measurement Data Foundation application

•

Oracle Utilities Meter Data Management application

For a successful installation, you must install ALL of the above components.

Installation Types

The first step in the installation procedure is to determine the installation type that meets your business requirements. The following are the possible installation types:

•

Initial Installation - A base installation, typically used for a production environment.

•

Demo Installation - A base installation with pre-populated demo data, typically used for demonstration or training purposes.

•

Upgrade Installation - An upgrade installation from version 2.1.0.3.0 and 2.2.0.0.0 to version 2.2.0.1.0.

Please see Recommendations for Creating a Production Environment for information about which installation type is appropriate for a production environment.

The following sections describe these installation types in detail.

Initial Installation

This installation type is applicable when installing Oracle Utilities Meter Data Management for the first time or from scratch. For an initial install, you must install all of the following components:

•

Database components

Refer to the "Initial Install" section of the Oracle Utilities Meter Data Management Database Administrator’s Guide for more information.

•

Application components

•

Oracle Utilities Application Framework application

•

Oracle Utilities Application Framework Single Fix Pre-Requisite Rollup for Oracle Utilities Service and Measurement Data Foundation

•

Oracle Utilities Service and Measurement Data Foundation application

•

Oracle Utilities Meter Data Management application

Refer to chapter " Installing Oracle Utilities Meter Data Management - Initial Installation " for the steps involved in installing each of the above components.

Demo Installation

This installation type is applicable when installing a demo application of Oracle Utilities Meter Data Management for demonstration or training purposes. For a demo install, you must install all of the following components:

•

Demo Database components

Refer to the "Demo Install" section of the Oracle Utilities Meter Data Management Database Administrator’s Guide for more information.

•

Application components

•

Oracle Utilities Application Framework application

•

Oracle Utilities Application Framework Single Fix Pre-Requisite Rollup for Oracle Utilities Service and Measurement Data Foundation

•

Oracle Utilities Service and Measurement Data Foundation application

•

Oracle Utilities Meter Data Management application

Refer to chapter " Installing Oracle Utilities Meter Data Management - Demo Installation " for the steps involved in installing each of the above components.

Upgrade Installation

This installation type is applicable when upgrading Oracle Utilities Meter Data Management from version 2.1.0.3.0 and 2.2.0.0.0 to version 2.2.0.1.0.

Note: If you have a version prior to 2.1.0.3.0, you must install 2.1.0.3.0 before upgrading to 2.2.0.1.0.

For an upgrade, you must upgrade all of the following components:

•

Database components

Refer to the "Upgrade Install" section of the Oracle Utilities Meter Data Management Database Administrator’s Guide for more information.

•

Application components

•

Oracle Utilities Application Framework application

•

Oracle Utilities Application Framework Single Fix Pre-Requisite Rollup for Oracle Utilities Service and Measurement Data Foundation

•

Oracle Utilities Service and Measurement Data Foundation application

•

Oracle Utilities Meter Data Management application

Refer to chapter " Upgrading Oracle Utilities Meter Data Management " for the steps involved in upgrading each of the above components.

Recommendations for Creating a Production Environment

For a production environment, Oracle recommends that you complete the Initial Installation installation type. If there is any custom configuration that needs to be migrated from a development or "gold" environment into production, the migration can be done by using the Configuration Migration Assistant (CMA). Please refer to the appendix "Configuration Migration Assistant" in the Oracle Utilities Meter Data Management Configuration Guide for more details about CMA.

Oracle does not recommend creating a production environment by using the Demo Installation installation type, or by cloning an existing Demo installation.

Media Pack Components

The Oracle Utilities Meter Data Management Media Pack consists of the following packages:

Documentation Packages

•

Oracle Utilities Meter Data Management V2.2.0.1.0 Quick Install Guide

•

Oracle Utilities Meter Data Management V2.2.0.1.0 Release Notes

•

Oracle Utilities Meter Data Management V2.2.0.1.0 Supplemental Documentation

•

Oracle Utilities Meter Data Management V2.2.0.1.0 User Documentation

•

Oracle Utilities Meter Data Management V2.2.0.1.0 Install Documentation

•

Oracle Utilities Meter Data Management V2.2.0.1.0 User Documentation

Installation Packages

•

Oracle Utilities Meter Data Management V2.2.0.1.0 Reports

•

Oracle Utilities Meter Data Management V2.2.0.1.0 Demo

•

Oracle Utilities Meter Data Management V2.2.0.1.0 Multiplatform

•

Oracle Fusion Middleware 12c (12.1.3.0.0) WebLogic Server and Coherence

•

Oracle Fusion Middleware 12c (12.2.1.1.0) WebLogic Server and Coherence

Supported Platforms and Hardware Requirements

This section gives an overview of the tiers on which the product is implemented, and shows each of the operating system/server combinations that the product is certified for. It includes:

•

Software and Hardware Considerations

•

Operating Systems and Application Servers

•

Hardware and Web Browser Requirements

•

Application Server Memory Requirements

•

Support for Software Patches and Upgrades

Software and Hardware Considerations

There are many factors that can influence software and hardware decisions. For example, your system may have to satisfy specific performance, availability, or scalability requirements, or to support running in a language other than English. These business requirements, together with the chosen system architecture, should be used in initial software and hardware planning.

Some of the questions that you should answer before beginning the installation include:

•

On which hardware platform and operating system will Oracle Utilities Meter Data Management be deployed?

•

On which Web server product will Oracle Utilities Meter Data Management deploy?

•

On which database product will Oracle Utilities Meter Data Management deploy?

•

Do you plan to deploy multiple Oracle Utilities Meter Data Management instances on the same physical server?

•

How do you plan to deploy Oracle Utilities Meter Data Management?

•

Web/application/database on the same physical server

•

Web/application on one server and database on separate server

•

Each component on its own server

For detailed descriptions of various deployment architecture choices that may aid in planning, please see the document Oracle Utilities Application Framework Architecture Guidelines, available on My Oracle Support (Article ID 807068.1).

The final hardware and software decisions must comply with the specific requirements of Oracle Utilities Meter Data Management, as described in the rest of this chapter.

Operating Systems and Application Servers

The table below details the MINIMUM operating system and application server combinations on which this version of Oracle Utilities Meter Data Management is supported.

Operating System and Web Browser

(Client)

Operating System

(Server)

Chipset

Application Server

Database

Microsoft Windows OS 7, 8.1, 10

(Internet Explorer 11,

Firefox ESR 45)

AIX 7.1 TL01+

AIX 7.2 TL00+

POWER

WebLogic 12.1.3.0+

WebLogic 12.2.1.1+

Oracle 12.1.0.1+

Oracle Linux 6.5+, 7.x

(based on Red Hat Enterprise Linux )*

x86_64

WebLogic 12.1.3.0+

WebLogic 12.2.1.1+

Oracle 12.1.0.1+

Oracle Solaris 11

SPARC

WebLogic 12.1.3.0+

WebLogic 12.2.1.1+

Oracle 12.1.0.1+

Windows Server 2012 R2

(Not supported in production)

x86_64

WebLogic 12.1.3.0+

WebLogic 12.2.1.1+

Oracle 12.1.0.1+

Refer to the Product Support Matrix (Doc ID 1454143.1) on Oracle Support to determine if support for newer versions of the listed products have been added.

Please note the following:

•

Version numbers marked with a "+" are the MINIMUM version supported. That version and all future 4th digit updates will be supported.

Example : Oracle 12.1.0.1+ means that 12.1.0.1 and any higher 12.1.0.x versions of Oracle are supported.* An "x" indicates that any version of the digit designed by the "x" is supported.

Example : Linux 7.x indicates that any version of Linux 7 (7.0, 7.1, 7.2 etc) will be supported.

Windows Server

•

Windows Server is not supported for Production environments. Wherever Windows Server is referenced within this guide, it is supported for Test or Development environments only.

WebLogic Server

•

WebLogic Server Standard and Enterprise Edition 12.1.3.0+ are supported for both embedded and native installations. Starting at Weblogic 12.2.*, embedded installations will be not be supported. Only the native installation will be supported.

•

WebLogic Server Enterprise Edition is required if using application clustering.

•

Customers must download Oracle WebLogic Server from the Oracle Software Delivery Cloud.

Oracle Database Server

The following Oracle Database Server editions are supported:

•

Oracle Database Enterprise Edition

•

Oracle Database Standard Edition

Note : Oracle Database Enterprise Edition and the Partitioning and Advanced Compression options are strongly recommended in all situations.

Oracle VM Support

This version of Oracle Utilities Meter Data Management is supported on Oracle VM Server for x86 for supported releases of Oracle Linux and Microsoft Windows operating systems.

Refer to My Oracle Support knowledge base article 249212.1 for Oracle's support policy on VMWare.

Hardware and Web Browser Requirements

Client Side Hardware Requirements

Configuration

Processor

Memory (RAM)

Monitor (Display)

Minimum

Pentium IV - 2.0 GHz

1024 MB

1024X768**

16-bit Color

Recommended*

Pentium IV -3.0+ GHz,

(or)

any Core 2 Duo

(or)

any Athlon X2

2048 MB

1280X1024**

32-bit Color

* The Recommended configuration supports better performance of the client.

** To reduce the amount of scrolling required for pages that are longer than 768 or 1024 pixels, consider placing a monitor into vertical position (with narrow side on the bottom).

Web Browser Requirements

The web browsers listed below are supported when used on each of the operating systems indicated:

Browsers

Windows OS

Internet Explorer 11

Firefox ESR 45

Microsoft Windows OS 7, 8.1, 10 (64-bit)

Application Server Memory Requirements

For each application server environment a minimum of 4 GB of real memory is required, plus 6 GB of swap space. The approximate disk space requirements in a standard installation are as follows (the size represents the MINIMUM required):

Location

Size

Usage

$SPLEBASE

minimum

This is the location where the application and

framework get installed.

Startup, shutdown and other online log files are stored here. The size and space that is used should be monitored because various debugging options can significantly affect the size of log files.

$SPLAPP

minimum

This location is used for storing batch log files and output from batch jobs. The size of this space should be influenced by which batches are run and how often, and the amount of debugging information that is collected.

Location of the application web work files on the web servers

minimum

This location is used by various web server vendors to expand the application. It should be considered when installing these products.

Refer to the individual web server documentation to determine the location of the temporary files.

Installation Temporary Area

4 GB

The application gets installed from this location. You need enough space to un-compress the files and install the application.

Oracle Data Area

4 GB minimum

This location is where the Oracle database data files are stored. The size of this space should be based on the requirements of the production environment. For an initial or demo database install 4 GB should be sufficient.

Support for Software Patches and Upgrades

Due to the ongoing nature of software improvement, vendors will periodically issue patches and service packs for the operating systems, application servers and database servers on top of specific versions that Oracle products have already been tested against.

If it is necessary to apply an upgrade, please do so in a test environment that is running on the same platform as your production environment prior to updating the production environment itself. The exception to this is Hibernate software version 4.1.0. This version should not be upgraded.

Always contact Oracle Support prior to applying vendor updates that do not guarantee backward compatibility.

Planning the Installation

This chapter provides information for planning an Oracle Utilities Meter Data Management installation, including:

•

Before You Install

•

Prerequisite Software List

•

Installing Prerequisite Software

•

Readiness Checklist

Before You Install

Refer to My Oracle Support for up-to-date additional information on Oracle Utilities Meter Data Management installation.

Embedded vs Native/Clustered Installation

By default, Oracle Utilities Application Framework uses Oracle WebLogic in embedded mode. This means the Oracle WebLogic installation is essentially pointed to the Oracle Utilities Application Framework product installation and the executables of Oracle WebLogic are only used to execute the code. This has the advantage of being simple and quick to implement with the Oracle Utilities Application Framework generating a simple configuration for Oracle WebLogic to use.

If you want to take advantage of more advanced WebLogic features such as high performance (multiple managed servers) and high availability (clustering) configuration, do not use the embedded install. Rather, use the native/clustered installation which allows you to deploy the Oracle Utilities Application Framework JEE components within Oracle WebLogic, as you would with other JEE applications.

Application Server Clustering

If you are considering application server clustering, refer to the following whitepaper, available on My Oracle Support, for additional information:

•

Implementing Oracle ExaLogic and/or Oracle WebLogic Clustering (Doc ID: 1334558.1)

•

IBM WebSphere Clustering for Oracle Utilities Application Framework (Doc ID: 1359369.1)

Additional information about Weblogic clustering can be found at http://docs.oracle.com/cd/E17904_01/web.1111/e13709/toc.htm .

Native Mode in WebLogic

If you plan on using the Oracle Utilities Application Framework in native mode within Oracle WebLogic (as opposed to embedded mode), refer to the whitepaper Native Installation Oracle Utilities Application Framework (Doc Id: 1544969.1) on My Oracle Support.

Directory Names

Directory cannot contain whitespace characters.

Prerequisite Software List

Before you install Oracle Utilities Meter Data Management, you must install prerequisite software.

Refer to the respective installation documentation of the software for instructions on downloading and installing.

Prerequisite Software for Database Server

The prerequisite software for the database component of Oracle Utilities Meter Data Management is as follows:

•

Oracle Database Server 12.1.0.1+ - This is required for installing the database component of the Oracle Utilities Meter Data Management product. Oracle Database Enterprise Edition version of the database server is supported.

Note: Oracle Database Enterprise Edition and the Partitioning and Advanced Compression options are strongly recommended in all situations.

Prerequisite Software for Application Server

The prerequisite software for the application component of Oracle Utilities Meter Data Management is as follows:

•

Oracle Database 12c Client

•

JDK 1.8.0_102+ (64-bit)

•

Oracle WebLogic 12c (12.1.3.0+) or Oracle WebLogic 12c (12.2.1.1+)

•

Hibernate 4.1.0 Final

Web Browser Requirements

The web browsers listed below are supported when used on each of the operating systems indicated:

Browsers

Windows OS

Internet Explorer 11

Firefox ESR 45

Microsoft Windows OS 7, 8.1, 10 (64-bit)

Installing Prerequisite Software

This section describes the software that needs to be installed for each of the supported operating system and application server combinations, including:

•

AIX 7.1 TL01+/AIX 7.2 TL00+ Application Server

•

Oracle Linux 6.5+, 7.x or Red Hat Linux 6.5+, 7.x Operating System

•

Oracle Solaris 11 Application Server

•

Windows Server 2012 R2 Application Server

AIX 7.1 TL01+/AIX 7.2 TL00+ Application Server

This section describes the software requirements for operating the application using the AIX application server.

Supported Application Servers

Operating System

Chipset

Application Server

AIX 7.1 TL01+/

AIX 7.2 TL00+

POWER 64-bit

Oracle WebLogic 12c (12.1.3.0+) 64-bit version or

Oracle WebLogic 12c (12.2.1.1+) 64-bit version

Web/Application Server Tier

AIX 7.1 TL01 Operating System Running on Power5 and Power6 Architecture

UNIX Administrator User ID

The following user groups and accounts have to be created to install and administer the application

Description

Default Value

Customer Defined Value

Oracle Utilities Meter Data Management Administrator User ID

cissys

Oracle Utilities Meter Data Management User Group

cisusr

Note : It is recommended that you change the default values for security reasons.

Throughout this document the administrator user id is often referred to as the "cissys" user id. You should substitute that with the customer defined user id when not using the default value. After the initial install, the software should always be managed using that user id.

By default, the cissys userid is the only one given access to the installed files.

1.

Create a group called cisusr (user group).

2.

Create a user called cissys. and a primary group cisusr. Set the primary shell for the cissys user to Korn Shell.

The shell scripts use the ">" to overwrite shell functionality. Your operating system may be configured to not allow this functionality by default in the users shell.

To avoid file access permission problems when executing scripts, consider placing the following command into cissys profile script:

set +o noclobber

Security Configuration

Various options exist to secure a system. In this application all files will be created with the minimum permissions required to ensure that group-readable, group-writable and group-executable files will have the correct user groups and to restrict the permissions available to legitimate users. In this way, a low privileged end user cannot directly edit configuration files and thereby bypass application security controls.

The following users and group categories must be defined to implement this security. For demonstration purposes the following users and groups will be used. These users must be created according to industry standards (including password policies). All users should be created with a default umask of 022 to ensure files created during normal operation have the correct permissions.

Please replace these users and groups for your installation defaults:

User

Group

Description

cissys

cisusr

This user will be used to install the application and to apply patches. This user will own all the application files. The same care should be taken with this user ID as if it is 'root'. This user will be able to add, delete and modify and files within the application.

cisadm

cisusr

Administrative and Operation functions will be available to this user. This user will be able to stop and start the application and batch processes, but will not have access to modify any file other than generated log files

cisoper

-------

Low level operator. This user will only be able to read logs files and collect information for debugging and investigative purposes. Care should be taken in production to disable debugging as debugging information could contain potential sensitive data which this user should not have privy to.

Note: The Oracle Client and WebLogic should be installed as the user who will stop and start the application. For example, if you plan to run the application as the install user these components must belong to cissys.

Oracle Client 12c — Runtime Option

Install the Oracle Client as described in the Oracle Client installation documentation. Use the cissys account to install the Oracle Client. If another user installs the Oracle Client, make sure the cissys user ID has the proper execute permissions.

For the cissys user ID, ensure that the environment variable ORACLE_CLIENT_HOME is set up, and that ORACLE_CLIENT_HOME/perl/bin is the first Perl listed in the cissys account’s PATH variable.

IBM Java Software Development Kit version 8.0 SR15 64-bit, IBM SDK, Java Technology Edition, Version 8.0

Installation of Java is a prerequisite for using Oracle WebLogic as an application server.

At the time of release, AIX Java packages could be obtained from:

http://www.ibm.com/developerworks/java/jdk/aix/service.html

The web server requires the 64-bit Java platform in order to function. The main prerequisite for the web server is the version of Java mentioned above.

For the Administrator userid (cissys), ensure that the environment variable JAVA_HOME is set up, and that "java" can be found in cissys' PATH variable.

Hibernate 4.1.0 FINAL

You must install Hibernate 4.1.0 before installing Oracle Utilities Meter Data Management.

To install Hibernate 4.1.0 external jar files to the Hibernate 3rd party jars depot:

1.

Create a Hibernate jar external depot:

export HIBERNATE_JAR_DIR=<Hibernate 3rd party jars depot>

2.

Download the hibernate-release-4.1.0.Final.zip file from:

http://sourceforge.net/projects/hibernate/files/hibernate4/

3.

Click the "4.1.0.Final" link to download the zip file.

4.

Extract the contents of the archive file:

jar xvf hibernate-release-4.1.0.Final.zip

Note : You must have Java JDK installed on the machine to use the jar command. Be sure to install the JDK that is supported for your platform.

5.

Copy the jar files to your Hibernate jar directory ($HIBERNATE_JAR_DIR) using the following commands:

cp hibernate-release-4.1.0.Final/lib/optional/

ehcache/ehcache-core-2.4.3.jar $HIBERNATE_JAR_DIR

cp hibernate-release-4.1.0.Final/lib/optional/

ehcache/hibernate-ehcache-4.1.0.Final.jar $HIBERNATE_JAR_DIR

cp hibernate-release-4.1.0.Final/lib/required/

hibernate-commons-annotations-4.0.1.Final.jar $HIBERNATE_JAR_DIR

cp hibernate-release-4.1.0.Final/lib/required/

hibernate-core-4.1.0.Final.jar $HIBERNATE_JAR_DIR

cp hibernate-release-4.1.0.Final/lib/required/

hibernate-jpa-2.0-api-1.0.1.Final.jar $HIBERNATE_JAR_DIR

cp hibernate-release-4.1.0.Final/lib/required/

javassist-3.15.0-GA.jar $HIBERNATE_JAR_DIR

cp hibernate-release-4.1.0.Final/lib/required/

jboss-transaction-api_1.1_spec-1.0.0.Final.jar $HIBERNATE_JAR_DIR

6.

Another package needs to be downloaded in order to get the jboss-logging-3.3.0.Final.jar. Download the hibernate-search-5.5.4.Final-dist.zip file from: https://sourceforge.net/projects/hibernate/files/hibernate-search/

7.

Click the "5.5.4.Final" link to download the zip file.

8.

Extract the contents of the archive file:

jar xvf hibernate-search-5.5.4.Final-dist.zip

9.

Copy the jboss-logging-3.3.0.Final.jar file to your Hibernate jar directory ($HIBERNATE_JAR_DIR) using the following command:

cp hibernate-search-5.5.4.Final/dist/lib/required/jboss-logging-3.3.0.Final.jar to $HIBERNATE_JAR_DIR

Oracle WebLogic 12c (12.1.3.0+) 64-bit

Oracle WebLogic software can be downloaded from the Oracle web site. This application server will run as a 64-bit application.

•

Download and install 64-bit Java (as documented above) before installing WebLogic.

•

Download and install WebLogic Server 12c (12.1.3.0+).

Oracle WebLogic 12c (12.2.1.1+) 64-bit

Oracle WebLogic software can be downloaded from the Oracle web site. This application server will run as a 64-bit application.

•

Download and install 64-bit Java (as documented above) before installing WebLogic.

•

Download and install WebLogic Server 12c Infrastructure Installer (12.2.1.1+).

Oracle Linux 6.5+, 7.x or Red Hat Linux 6.5+, 7.x Operating System

This section describes the software requirements for operating the application using the Oracle Linux or Red Hat Linux application server.

Supported Application Servers

Operating System

Chipset

Application Server

Oracle Enterprise Linux 6.5+, 7.x (64-bit; based on Red Hat Enterprise Linux (64-bit))

x86_64

Oracle WebLogic 12c (12.1.3.0+) 64-bit

or

Oracle WebLogic 12c (12.2.1.1+) 64-bit

Oracle Linux or Red Hat Enterprise Linux Operating System Running on x86_64 64-bit Architecture

UNIX Administrator User ID

The following user groups and accounts have to be created to install and administer the application:

Description

Default Value

Customer Defined Value

Oracle Utilities Meter Data Management Administrator User ID

cissys

Oracle Utilities Meter Data Management User Group

cisusr

Note: It is recommended that you change the default values for security reasons.

Throughout this document the administrator user id is often referred to as the "cissys" user id. You should substitute that with the customer defined user id when not using the default value. After the initial install, the software should always be managed using that user id.

By default, the cissys userid is the only one given access to the files installed.

1.

Create a group called cisusr (user group)

2.

Create a user called cissys. Primary group cisusr. Set the primary shell for the cissys user to Korn Shell.

The shell scripts use the ">" to overwrite shell functionality. Your operating system may be configured to not allow this functionality by default in the users shell.

To avoid file access permission problems when executing scripts, consider placing the following command into cissys profile script:

set +o noclobber

Security Configuration

Various options exists to secure a system. In this application all files will be created with the minimum permissions required to ensure that group-readable, group-writable and group-executable files will have the correct user groups and to restrict the permissions available to legitimate users. In this way, a low privileged end user cannot directly edit configuration files and thereby bypass application security controls.

The following users and group categories must be defined to implement this security. For demonstration purposes the following users and groups will be used. These users must be created according to industry standards (including password policies). All users should be created with a default umask of 022 to ensure files created during normal operation have the correct permissions.

Please replace these users and groups for your installation defaults:

User

Group

Description

cissys

cisusr

This user will be used to install the application and to apply patches. This user will own all the application files. The same care should be taken with this user ID as if it is 'root'. This user will be able to add, delete and modify and files within the application.

cisadm

cisusr

Administrative and Operation functions will be available to this user. This user will be able to stop and start the application and batch processes, but will not have access to modify any file other than generated log files

cisoper

-------

Low level operator. This user will only be able to read logs files and collect information for debugging and investigative purposes. Care should be taken in production to disable debugging as debugging information could contain potential sensitive data which this user should not have privy to.

Note: The Oracle Client and WebLogic should be installed as the user who will stop and start the application. For example, if you plan to run the application as the install user these components must belong to cissys.

Oracle Client 12c — Runtime Option

Install the Oracle Client as described in the Oracle Client installation documentation. Use the cissys account to install the Oracle Client. If another user installs the Oracle Client, make sure the cissys user ID has the proper execute permissions.

For the cissys user ID, ensure that the environment variable ORACLE_CLIENT_HOME is set up, and that ORACLE_CLIENT_HOME/perl/bin is the first Perl listed in the cissys account’s PATH variable.

Oracle Java Development Kit Version 8.0 Update 102+

At time of release, Oracle Java packages could be obtained from:

http://www.oracle.com/technetwork/java/archive-139210.html

The Oracle WebLogic Server requires the 64-bit version. The main prerequisite for the web server is the version of Java mentioned above.

For the userid cissys, ensure that the environment variable JAVA_HOME is setup, and that java_home/bin and java_home/lib can be found in cissys' PATH variable.

Note: JDK 8.0 Update 102 or higher version is required for Weblogic12c (12.1.3.0+ and 12.2.1.1+).

Hibernate 4.1.0 FINAL

You must install Hibernate 4.1.0 before installing Oracle Utilities Meter Data Management.

To install Hibernate 4.1.0 external jar files to the Hibernate 3rd party jars depot:

1.

Create a Hibernate jar external depot:

export HIBERNATE_JAR_DIR=<Hibernate 3rd party jars depot>

2.

Download the hibernate-release-4.1.0.Final.zip file from:

http://sourceforge.net/projects/hibernate/files/hibernate4/

3.

Click the "4.1.0.Final" link to download the zip file.

4.

Extract the contents of the archive file:

jar xvf hibernate-release-4.1.0.Final.zip

Note : You must have Java JDK installed on the machine to use the jar command. Be sure to install the JDK that is supported for your platform.

5.

Copy the jar files to your Hibernate jar directory ($HIBERNATE_JAR_DIR) using the following commands:

cp hibernate-release-4.1.0.Final/lib/optional/

ehcache/ehcache-core-2.4.3.jar $HIBERNATE_JAR_DIR

cp hibernate-release-4.1.0.Final/lib/optional/

ehcache/hibernate-ehcache-4.1.0.Final.jar $HIBERNATE_JAR_DIR

cp hibernate-release-4.1.0.Final/lib/required/

hibernate-commons-annotations-4.0.1.Final.jar $HIBERNATE_JAR_DIR

cp hibernate-release-4.1.0.Final/lib/required/

hibernate-core-4.1.0.Final.jar $HIBERNATE_JAR_DIR

cp hibernate-release-4.1.0.Final/lib/required/

hibernate-jpa-2.0-api-1.0.1.Final.jar $HIBERNATE_JAR_DIR

cp hibernate-release-4.1.0.Final/lib/required/

javassist-3.15.0-GA.jar $HIBERNATE_JAR_DIR

cp hibernate-release-4.1.0.Final/lib/required/

jboss-transaction-api_1.1_spec-1.0.0.Final.jar $HIBERNATE_JAR_DIR

6.

Another package needs to be downloaded in order to get the jboss-logging-3.3.0.Final.jar. Download the hibernate-search-5.5.4.Final-dist.zip file from: https://sourceforge.net/projects/hibernate/files/hibernate-search/

7.

Click the "5.5.4.Final" link to download the zip file.

8.

Extract the contents of the archive file:

jar xvf hibernate-search-5.5.4.Final-dist.zip

9.

Copy the jboss-logging-3.3.0.Final.jar file to your Hibernate jar directory ($HIBERNATE_JAR_DIR) using the following command:

cp hibernate-search-5.5.4.Final/dist/lib/required/jboss-logging-3.3.0.Final.jar to $HIBERNATE_JAR_DIR

Oracle WebLogic 12c (12.1.3.0+) 64-bit

Oracle WebLogic software can be downloaded from the Oracle web site. This application server will run as a 64-bit application.

•

Download and install 64-bit Java (as documented above) before installing WebLogic.

•

Download and install WebLogic Server 12c (12.1.3.0+).

Oracle WebLogic 12c (12.2.1.1+) 64-bit

Oracle WebLogic software can be downloaded from the Oracle web site. This application server will run as a 64-bit application.

•

Download and install 64-bit Java (as documented above) before installing WebLogic.

•

Download and install WebLogic Server 12c Infrastructure Installer (12.2.1.1+).

Oracle Solaris 11 Application Server

This section describes the software requirements for operating the application using the Oracle Solaris 11 application server.

Supported Application Servers

Operating System

Chipset

Application Server

Oracle Solaris 11 (64-bit)

SPARC

Oracle WebLogic 12c (12.1.3.0+) 64-bit version

or

Oracle WebLogic 12c (12.2.1.1+) 64-bit version

Oracle Solaris 11 Operating System Running on SPARC-based 64-bit Architecture

UNIX Administrator User ID

The following user groups and accounts have to be created to install and administer the application:

Description

Default Value

Customer Defined Value

Oracle Utilities Meter Data Management Administrator User ID

cissys

Oracle Utilities Meter Data Management User Group

cisusr

Note : It is recommended that you change the default values for security reasons.

Throughout this document the administrator user id is often referred to as the "cissys" user id. You should substitute that with the customer defined user id when not using the default value. After the initial install, the software should always be managed using that user id.

By default, the cissys userid is the only one given access to the files installed.

1.

Create a group called cisusr (user group)

2.

Create a user called cissys. Primary group cisusr. Set the primary shell for the cissys user to Korn Shell.

The shell scripts use the ">" to overwrite shell functionality. Your operating system may be configured to not allow this functionality by default in the users shell.

To avoid file access permission problems when executing scripts, consider placing the following command into cissys profile script:

set +o noclobber

Security Configuration

Various options exists to secure a system. In this application all files will be created with the minimum permissions required to ensure that group-readable, group-writable and group-executable files will have the correct user groups and to restrict the permissions available to legitimate users. In this way, a low privileged end user cannot directly edit configuration files and thereby bypass application security controls.

The following users and group categories must be defined to implement this security. For demonstration purposes the following users and groups will be used. These users must be created according to industry standards (including password policies). All users should be created with a default umask of 022 to ensure files created during normal operation have the correct permissions.

Please replace these users and groups for your installation defaults:

User

Group

Description

cissys

cisusr

This user will be used to install the application and to apply patches. This user will own all the application files. The same care should be taken with this user ID as if it is 'root'. This user will be able to add, delete and modify and files within the application.

cisadm

cisusr

Administrative and Operation functions will be available to this user. This user will be able to stop and start the application and batch processes, but will not have access to modify any file other than generated log files

cisoper

-------

Low level operator. This user will only be able to read logs files and collect information for debugging and investigative purposes. Care should be taken in production to disable debugging as debugging information could contain potential sensitive data which this user should not have privy to.

Note: The Oracle Client and WebLogic should be installed as the user who will stop and start the application. For example, if you plan to run the application as the install user these components must belong to cissys.

Oracle Client 12c — Runtime Option

Install the Oracle Client as described in the Oracle Client installation documentation. Use the cissys account to install the Oracle Client. If another user installs the Oracle Client, make sure the cissys user ID has the proper execute permissions.

For the cissys user ID, ensure that the environment variable ORACLE_CLIENT_HOME is set up, and that ORACLE_CLIENT_HOME/perl/bin is the first Perl listed in the cissys account’s PATH variable.

Oracle Java Development Kit Version 8.0 Update 102+

This software is only required for Oracle WebLogic installations.

At the time of release, the Oracle Java packages used in the test cycle were downloaded from:

http://www.oracle.com/technetwork/java/archive-139210.html

The Oracle WebLogic Server requires the 64-bit version. The main prerequisite for the web server is the version of Java mentioned above.

For the userid cissys, ensure that the environment variable JAVA_HOME is setup, and that java_home/bin and java_home/lib can be found in cissys' PATH variable.

Note: JDK 8.0 Update version 102 or higher is required for WebLogic12c (12.2.1.1+).

Hibernate 4.1.0 FINAL

You must install Hibernate 4.1.0 before installing Oracle Utilities Meter Data Management.

To install Hibernate 4.1.0 external jar files to the Hibernate 3rd party jars depot:

1.

Create a Hibernate jar external depot:

export HIBERNATE_JAR_DIR=<Hibernate 3rd party jars depot>

2.

Download the hibernate-release-4.1.0.Final.zip file from:

http://sourceforge.net/projects/hibernate/files/hibernate4/

3.

Click the "4.1.0.Final" link to download the zip file.

4.

Extract the contents of the archive file:

jar xvf hibernate-release-4.1.0.Final.zip

Note : You must have Java JDK installed on the machine to use the jar command. Be sure to install the JDK that is supported for your platform.

5.

Copy the jar files to your Hibernate jar directory ($HIBERNATE_JAR_DIR) using the following commands:

cp hibernate-release-4.1.0.Final/lib/optional/

ehcache/ehcache-core-2.4.3.jar $HIBERNATE_JAR_DIR

cp hibernate-release-4.1.0.Final/lib/optional/

ehcache/hibernate-ehcache-4.1.0.Final.jar $HIBERNATE_JAR_DIR

cp hibernate-release-4.1.0.Final/lib/required/

hibernate-commons-annotations-4.0.1.Final.jar $HIBERNATE_JAR_DIR

cp hibernate-release-4.1.0.Final/lib/required/

hibernate-core-4.1.0.Final.jar $HIBERNATE_JAR_DIR

cp hibernate-release-4.1.0.Final/lib/required/

hibernate-jpa-2.0-api-1.0.1.Final.jar $HIBERNATE_JAR_DIR

cp hibernate-release-4.1.0.Final/lib/required/

javassist-3.15.0-GA.jar $HIBERNATE_JAR_DIR

cp hibernate-release-4.1.0.Final/lib/required/

jboss-transaction-api_1.1_spec-1.0.0.Final.jar $HIBERNATE_JAR_DIR

6.

Another package needs to be downloaded in order to get the jboss-logging-3.3.0.Final.jar. Download the hibernate-search-5.5.4.Final-dist.zip file from: https://sourceforge.net/projects/hibernate/files/hibernate-search/

7.

Click the "5.5.4.Final" link to download the zip file.

8.

Extract the contents of the archive file:

jar xvf hibernate-search-5.5.4.Final-dist.zip

9.

Copy the jboss-logging-3.3.0.Final.jar file to your Hibernate jar directory ($HIBERNATE_JAR_DIR) using the following command:

cp hibernate-search-5.5.4.Final/dist/lib/required/jboss-logging-3.3.0.Final.jar to $HIBERNATE_JAR_DIR

Oracle WebLogic 12c (12.1.3.0+) 64-bit

Oracle WebLogic software can be downloaded from the Oracle web site. This application server will run as a 64-bit application.

•

Download and install 64-bit Java (as documented above) before installing WebLogic.

•

Download and install WebLogic Server 12c (12.1.3.0+).

Oracle WebLogic 12c (12.2.1.1+) 64-bit

Oracle WebLogic software can be downloaded from the Oracle web site. This application server will run as a 64-bit application.

•

Download and install 64-bit Java (as documented above) before installing WebLogic.

•

Download and install WebLogic Server 12c Infrastructure Installer (12.2.1.1+).

Windows Server 2012 R2 Application Server

This section describes the software requirements for operating the application using the Windows application server.

Supported Application Servers

Operating System

Chipset

Application Server

Windows Server 2012 R2 (64-bit)

x86_64

Oracle WebLogic 12c (12.2.1.1.0+) 64-bit version

or

Oracle WebLogic 12c (12.1.3.0+) 64-bit version

Oracle Client 12c — Runtime Option

Install the Oracle Client as described in the Oracle Client installation documentation. Use the cissys account to install the Oracle Client. If another user installs the Oracle Client, make sure the cissys user ID has the proper execute permissions.

For the cissys user ID, ensure that the environment variable ORACLE_CLIENT_HOME is set up, and that ORACLE_CLIENT_HOME/perl/bin is the first Perl listed in the cissys account’s PATH variable.

Oracle Java Development Kit Version 8.0 Update 102+

This software is required for the Oracle WebLogic Installation.

At time of release, Oracle Java packages could be obtained from:

http://www.oracle.com/technetwork/java/archive-139210.html

The Oracle WebLogic Server requires the 64-bit version. The main prerequisite for the web server is the version of java mentioned above.

For the userid cissys, ensure that the environment variable JAVA_HOME is setup, and that java_home/bin and java_home/lib can be found in cissys' PATH variable.

Note: JDK 8.0 Update version 102 or higher is required for WebLogic12c (12.1.3.0+ or 12.2.1.1.0).

Hibernate 4.1.0 FINAL

You must install Hibernate 4.1.0 before installing Oracle Utilities Meter Data Management.

To install Hibernate 4.1.0 external jar files to the Hibernate 3rd party jars depot:

1.

Create a Hibernate jar external depot:

export HIBERNATE_JAR_DIR=<Hibernate 3rd party jars depot>

2.

Download the hibernate-release-4.1.0.Final.zip file from:

http://sourceforge.net/projects/hibernate/files/hibernate4/

3.

Click the "4.1.0.Final" link to download the zip file.

4.

Extract the contents of the archive file:

jar xvf hibernate-release-4.1.0.Final.zip

Note : You must have Java JDK installed on the machine to use the jar command. Be sure to install the JDK that is supported for your platform.

5.

Copy the jar files to your Hibernate jar directory ($HIBERNATE_JAR_DIR) using the following commands:

cp hibernate-release-4.1.0.Final/lib/optional/

ehcache/ehcache-core-2.4.3.jar $HIBERNATE_JAR_DIR

cp hibernate-release-4.1.0.Final/lib/optional/

ehcache/hibernate-ehcache-4.1.0.Final.jar $HIBERNATE_JAR_DIR

cp hibernate-release-4.1.0.Final/lib/required/

hibernate-commons-annotations-4.0.1.Final.jar $HIBERNATE_JAR_DIR

cp hibernate-release-4.1.0.Final/lib/required/

hibernate-core-4.1.0.Final.jar $HIBERNATE_JAR_DIR

cp hibernate-release-4.1.0.Final/lib/required/

hibernate-jpa-2.0-api-1.0.1.Final.jar $HIBERNATE_JAR_DIR

cp hibernate-release-4.1.0.Final/lib/required/

javassist-3.15.0-GA.jar $HIBERNATE_JAR_DIR

cp hibernate-release-4.1.0.Final/lib/required/

jboss-transaction-api_1.1_spec-1.0.0.Final.jar $HIBERNATE_JAR_DIR

6.

Another package needs to be downloaded in order to get the jboss-logging-3.3.0.Final.jar. Download the hibernate-search-5.5.4.Final-dist.zip file from: https://sourceforge.net/projects/hibernate/files/hibernate-search/

7.

Click the "5.5.4.Final" link to download the zip file.

8.

Extract the contents of the archive file:

jar xvf hibernate-search-5.5.4.Final-dist.zip

9.

Copy the jboss-logging-3.3.0.Final.jar file to your Hibernate jar directory ($HIBERNATE_JAR_DIR) using the following command:

cp hibernate-search-5.5.4.Final/dist/lib/required/jboss-logging-3.3.0.Final.jar to $HIBERNATE_JAR_DIR

Oracle WebLogic 12c (12.1.3.0+) 64-bit

Oracle WebLogic software can be downloaded from the Oracle web site. This application server will run as a 64-bit application.

•

Download and install 64-bit Java (as documented above) before installing WebLogic.

•

Download and install WebLogic Server 12c (12.1.3.0+).

Oracle WebLogic 12c (12.2.1.1+) 64-bit

Oracle WebLogic software can be downloaded from the Oracle web site. This application server will run as a 64-bit application.

•

Download and install 64-bit Java (as documented above) before installing WebLogic.

•

Download and install WebLogic Server 12c Infrastructure Installer (12.2.1.1+).

Readiness Checklist

The following checklist guides you through the installation process of Oracle Utilities Meter Data Management. The details for each step are presented in subsequent chapters.

1.

Confirm that the recommended hardware is ready. Refer to Supported Platforms and Hardware Requirements for more details.

2.

Install prerequisite software. Refer to the Prerequisite Software List for more details.

3.

Ensure that you have downloaded the Oracle Utilities Meter Data Management V2.2.0.1 components.

4.

Go through the Installation and Configuration Worksheets to understand the configuration menu.

5.

Determine the type of the installation:

•

Initial Installation - For initial installation follow the instructions mentioned in chapter Installing Oracle Utilities Meter Data Management - Initial Installation .

•

Demo Installation - For demo installation follow the instructions mentioned in chapter Installing Oracle Utilities Meter Data Management - Demo Installation .

•

Upgrade Installation - For upgrade installation to V2.2.0.1, follow the instructions mentioned in chapter Upgrading Oracle Utilities Meter Data Management .

6.

Perform post-installation tasks.

Installing Oracle Utilities Meter Data Management - Initial Installation

This chapter provides instructions for installing Oracle Utilities Meter Data Management from scratch. This chapter includes:

•

Before You Install

•

Initial Installation Procedure

•

After the Installation

•

Operating the Application

Before You Install

Refer to My Oracle Support for up-to-date additional information on Oracle Utilities Meter Data Management.

Initial Installation Procedure

The initial installation procedure consists of:

•

Database Component Installation

•

Application Components Installation

Database Component Installation

Installation of the database component of Oracle Utilities Meter Data Management must be complete before you can proceed with the following sections. Refer to the Initial Install section of the Oracle Utilities Meter Data Management Database Administrator’s Guide, which provides instructions on installing the database component.

Application Components Installation

A successful installation consists of the following steps:

•

Installing the Oracle Utilities Application Framework V4.3.0 Service Pack 4 (4.3.0.4.0) Application Component

•

Installing Oracle Utilities Application Framework V4.3.0.4.0 Single Fix Prerequisite Rollup for SMDF V2.2.0.1.0

•

Installing Oracle Utilities Service and Measurement Data Foundation V2.2.0.1.0 Application Component

•

Installing the Oracle Utilities Meter Data Management V2.2.0.1.0 Application Component

Installing the Oracle Utilities Application Framework V4.3.0 Service Pack 4 (4.3.0.4.0) Application Component

This section describes how to install the application component of Oracle Utilities Application Framework V4.3.0 Service Pack 4, including:

•

Copying and Decompressing Install Media

•

Setting Permissions for the cistab file in UNIX

•

Installing the Application Component

Copying and Decompressing Install Media

The Oracle Utilities Application Framework V4.3.0 Service Pack 4 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.3.0 Service Pack 4 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, follow these steps:

1.

Log in to the application server host with the Oracle Utilities Application Framework administrator user ID.

2.

Download the Oracle Utilities Meter Data Management V2.2.0.1.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.2.0.1.0 Multiplatform.zip to get the file MDM_V2.2.0.1.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 for the FTP transfer.

5.

Decompress the file:

cd <TEMPDIR>

unzip MDM_V2.2.0.1.0.zip

cd App

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 ../App/FW.V4.3.0.4.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.3.0.4.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 ../App/FW.V4.3.0.4.0.

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

5.

The Oracle Utilities Application Framework specific menu appears.

6.

Follow the messages and instructions that are produced by the application installation utility.

7.

Select each menu item to configure the values. For detailed description of the values, refer to Appendix B : Installation and Configuration Worksheets .

8.

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. Third Party Software Configuration

Oracle Client Home Directory: <Mandatory>

Web Java Home Directory: <Mandatory>

Child JVM Home Directory:

COBOL Home Directory:

Hibernate JAR Directory: <Mandatory>

ONS JAR Directory:

Web Application Server Home Directory: <Mandatory>

ADF Home Directory:

OIM OAM Enabled Environment:

2. Keystore Options

Store Type: JCEKS

Alias: ouaf.system

Alias Key Algorithm: AES

Alias Key Size: 128

HMAC Alias: ouaf.system.hmac

Padding: PKCS5Padding

Mode: CBC

50. Environment Installation Options

Environment Mount Point: <Mandatory> - Install Location

Log Files Mount Point:<Mandatory> - ThreadPoolWorker Logs

Location

Environment Name:<Mandatory>

Web Application Server Type: WLS

Install Application Viewer Module: true

Each item in the above list should be configured for a successful install.

Choose option (1,2,50, <P> Process, <X> Exit):

9.

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

WebLogic Server Name: myserver

Business Server Application Name: SPLService

MPL Admin Port Number: <Mandatory> - Multipurpose Listener

Port

MPL Automatic startup: false

3. Web Application Server Configuration

Web Server Host: <Mandatory>

WebLogic SSL Number: <Mandatory>

WebLogic Console Port Number: <Mandatory>

WebLogic Additional Stop Arguments:

Web Context Root: ouaf

WebLogic JNDI User ID: <Mandatory>

WebLogic JNDI Password: <Mandatory>

WebLogic Admin System User ID: <Mandatory>

WebLogic Admin System Password: <Mandatory>

WebLogic Server Name: myserver

Web Server Application Name: SPLWeb

Deploy Using Archive Files: true

Deploy Application Viewer Module: true

Enable The Unsecured Health Check Service: false

MDB RunAs User ID:

Super User Ids: SYSUSER

4. Database Configuration

Application Server Database User ID: <Mandatory>

Application Server Database Password: <Mandatory>

MPL Database User ID: <Mandatory>

MPL 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: <Mandatory>

JDBC Database User ID: <Mandatory>

JDBC Database Password: <Mandatory>

Database Name: <Mandatory>

Database Server: <Mandatory>

Database Port: <Mandatory>

ONS Server Configuration: <Mandatory>

Database Override Connection String: <Mandatory>

Character Based Database: <Mandatory>

Oracle Client Character Set NLS_LANG: AMERICAN_AMERICA.AL32UTF8

5. General Configuration Options

Batch RMI Port: <Mandatory> - RMI port

for batch

RMI Port number for JMX Business:

RMI Port number for JMX Web:

JMX Enablement System User ID:

JMX Enablement System Password:

Coherence Cluster Name: <Mandatory> - Unique

name for batch

Coherence Cluster Address: <Mandatory> - Unique

Multicast address

Coherence Cluster Port: <Mandatory> - Unique

port for batch cluster

Coherence Cluster Mode: <Mandatory> - prod

6. SSL Certificate Keystore

Certificate Keystore Type: CUSTOM

Identify Keystore File:

Identify Keystore File Type: jks

Identify Keystore Password:

Identity Private Key Alias:

Trust Keystore File:

Trust Keystore File Type: jks

Trust Keystore Password:

Trust Private Key Alias:

7. OUAF TrustStore Options

Import TrustStore Directory:

Store Type: JCEKS

Alias: ouaf.system

Alias Key Algorithm: AES

Alias Key Size: 128

HMAC Alias: ouaf.system.hmac

Padding: PKCS5Padding

Mode: CBC

Each item in the above list should be configured for a successful install.

Choose option (1,2,3,4,5,6,7, <P> Process, <X> Exit):

10.

When you are done with the parameter setup, proceed with the option P. The utility writes the configured parameters and their values into the configuration file.

11.

Once the install has finished, the installation log location appears 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. You can now install Oracle Utilities Service and Measurement Data Foundation as described in the following section.

Installing Oracle Utilities Application Framework V4.3.0.4.0 Single Fix Prerequisite Rollup for SMDF V2.2.0.1.0

1.

Navigate to ../App/FW43040_Rollup.

2.

Refer to the Readme.txt inside 'FW43040_Rollup' file for instructions on installing the Oracle Utilities Application Framework V4.3.0.4.0 Prerequisite Single Fixes.

These patches are also available for download separately from My Oracle Support.

See Appendix E for a list of the patches contained in the rollup.

Installing Oracle Utilities Service and Measurement Data Foundation V2.2.0.1.0 Application Component

This section describes how to install the application component of Oracle Utilities Service and Measurement Data Foundation, including:

•

Copying and Decompressing Install Media

•

Installing Oracle Utilities Service and Measurement Data Foundation V2.2.0.1

•

Configuration of Oracle Fusion Middleware Components on a Separate Server from Oracle Utilities Service and Measurement Data Foundation

Copying and Decompressing Install Media

The installation file is delivered in jar format for both UNIX and Windows platforms.

The Oracle Utilities Service and Measurement Data Foundation is delivered as a separate installation package Please refer to the Supported Platforms and Hardware Requirements chapter for installation details regarding the database and operating system versions supported for the Service and Measurement Data Foundation. Also see the section Installing Prerequisite Software for prerequisite third-party software installation instructions.

Download the installation package and proceed as follows:

1.

Log in to the host server as the Oracle Utilities Application Framework administrator user ID (default cissys). This is the same user ID that was used to install the Oracle Utilities Application Framework.

2.

Navigate to ../App/SMDF.V2.2.0.1.0.

Installing Oracle Utilities Service and Measurement Data Foundation V2.2.0.1

This section outlines the steps for installing the Service and Measurement Data Foundation:

Preparing for the Installation

1.

Log on as Oracle Utilities Service and Measurement Data Foundation 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.

UNIX

$SPLEBASE/bin/spl.sh stop

Windows

%SPLEBASE%\bin\spl.cmd stop

Installing the Application

1.

Execute the script:

UNIX

ksh ./install.sh

Windows

install.cmd

Note: On UNIX, ensure that you have the proper execute permission on install.sh

The configuration menu for the Oracle Utilities Service and Measurement Data Foundation Application appears.

2.

Select menu item 8 to configure OSB.

Use the completed OSB configuration worksheet to assist you in this step. See the Service and Measurement Data Foundation 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 Service and Measurement Data Foundation Installation and Configuration Worksheets.

4.

Select menu item 10 to configure the SOA Configuration Plan.

Use the completed SOA Configuration Plan (MDF) worksheet to assist you in this step. See the Installation and Configuration Worksheets.

5.

When you are done with the parameter setup, choose option P to proceed with the installation.

Installation of Oracle Utilities Service and Measurement Data Foundation Application Server is complete if no errors occurred during installation.

Configuration of Oracle Fusion Middleware Components on a Separate Server from Oracle Utilities Service and Measurement Data Foundation

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:

Note: Use the completed OSB configuration worksheet to assist you in this step. See the Installation and Configuration Worksheets.

•

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.

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.

Note: Use the completed SOA configuration worksheet to assist you in this step. See the Installation and Configuration Worksheets.

•

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.2.0.1.0 Application Component

This section describes how to install the application component of Oracle Utilities Meter Data Management, including:

•

Installation Prerequisite

•

Copying and Decompressing Install Media

•

Installing the Application Component

To proceed with the Oracle Utilities Meter Data Management installation you need to be connected to the target Oracle Utilities Service and Measurement Data Foundation application environment. See the detailed installation instructions in the following section.

You must initialize the Service and Measurement Data Foundation environment. For detailed instructions see the Preparing for the Installation section.

Installation Prerequisite

Oracle Utilities Service and Measurement Data Foundation 2.2.0.1 must be installed prior to installing Oracle Utilities Meter Data Management 2.2.0.1.

Copying and Decompressing 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, follow these steps:

Log in to the application server host as the Oracle Utilities Application Framework administrator user ID (default cissys). This is the same user ID that was used to install the Oracle Utilities Application Framework.

Installing the Application Component

Follow the steps below to install Oracle Utilities Meter Data Management application component:

1.

Log in to the application server host as Oracle Utilities Meter Data Management Administrator (default cissys).

2.

Change directory:

cd <install_dir>/bin

where <install_dir> is the location where the Oracle Utilities Service and Measurement Data Foundation 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.

If the environment is running, stop it by running the appropriate command:

UNIX

./spl.sh stop

Windows

spl.cmd stop

5.

Navigate to .. <TEMPDIR>/MDM.V2.2.0.1.0 directory.

6.

Execute the install script:

Note: On UNIX, ensure that you have the proper execute permission on install.sh.

UNIX

ksh ./install.sh

Windows

install.cmd

Choose option P to proceed with the installation (you don't need to change anything).

Installation of the Oracle Utilities Meter Data Management Server is complete if no errors occurred during the installation.

7.

Start up the environment. Run the following command:

UNIX

spl.sh start

Windows

spl.cmd start

Follow the message on the screen and review the logs in $SPLSYSTEMLOGS directory to ensure that the environment was started successfully.

If the startup failed, identify the problem by reviewing the logs. Resolve any issues before attempting to restart the environment.

Note : The first time you start Oracle Utilities Meter Data Management, you need to log into the WebLogic console and give system access to cisusers role. The WebLogic console application can be accessed through the following URL: http://<hostname>:<portname>/console.

After the Installation

After completing the installation, verify the following:

1.

Verify installation logs created under decompressed installer location for any errors.

2.

Confirm installation logs do not contain any errors.

3.

Confirm all the configurations are correct. Refer to Appendix B : Installation and Configuration Worksheets for details.

4.

Confirm that the database is ready.

5.

Start the application server. For instructions, refer to Appendix C : Common Maintenance Activities .

6.

To operate the application, refer to the following section.

Operating the Application

At this point your installation and custom integration process is complete. Be sure to read the Oracle Utilities Meter Data Management Server Administrator’s Guide for more information on further configuring and operating the system.

Installing Oracle Utilities Meter Data Management - Demo Installation

This chapter provides instructions for setting up a demo application of Oracle Utilities Meter Data Management useful for demonstration or training purposes. It includes:

•

Before You Install

•

Demo Installation Procedure

Before You Install

Refer to My Oracle Support for up-to-date additional information on Oracle Utilities Meter Data Management.

Demo Installation Procedure

The demo installation procedure consists of:

•

Database Component Installation

•

Application Components Installation

Database Component Installation

Installation of the database component of Oracle Utilities Meter Data Management must be complete before you can proceed with the following sections. Refer to the section " Demo Install" of the Oracle Utilities Meter Data Management Database Administrator’s Guide, which provides instructions on installing the database component with pre-populated demo data.

Application Components Installation

A successful installation consists of the following steps:

•

Installing the Oracle Utilities Application Framework V4.3.0 Service Pack 4 (4.3.0.4.0) Application Component

•

Installing Oracle Utilities Application Framework V4.3.0.4.0 Single Fix Prerequisite Rollup for SMDF V2.2.0.1.0

•

Installing Oracle Utilities Service and Measurement Data Foundation V2.2.0.1.0 Application Component

•

Installing the Oracle Utilities Meter Data Management V2.2.0.1.0 Application Component

Installing the Oracle Utilities Application Framework V4.3.0 Service Pack 4 (4.3.0.4.0) Application Component

This section describes how to install the application component of Oracle Utilities Application Framework V4.3.0 Service Pack 4, including:

•

Copying and Decompressing Install Media

•

Setting Permissions for the cistab file in UNIX

•

Installing the Application Component

Copying and Decompressing Install Media

The Oracle Utilities Application Framework V4.3.0 Service Pack 4 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.3.0 Service Pack 4 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, follow these steps:

1.

Log in to the application server host with the Oracle Utilities Application Framework administrator user ID.

2.

Download the Oracle Utilities Meter Data Management V2.2.0.1.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.2.0.1.0 Multiplatform.zip to get the file MDM_V2.2.0.1.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 for the FTP transfer.

5.

Decompress the file:

cd <TEMPDIR>

unzip MDM_V2.2.0.1.0.zip

cd App

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 ../App/FW.V4.3.0.4.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.3.0.4.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 ../App/FW.V4.3.0.4.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 executing the appropriate script:

UNIX :

ksh ./install.sh

Windows :

install.cmd

5.

The Oracle Utilities Application Framework specific menu appears.

6.

Follow the messages and instructions that are produced by the application installation utility.

7.

Select each menu item to configure the values. For detailed description of the values, refer to Appendix B : Installation and Configuration Worksheets .

8.

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. Third Party Software Configuration

Oracle Client Home Directory: <Mandatory>

Web Java Home Directory: <Mandatory>

Child JVM Home Directory:

COBOL Home Directory:

Hibernate JAR Directory: <Mandatory>

ONS JAR Directory:

Web Application Server Home Directory: <Mandatory>

ADF Home Directory:

OIM OAM Enabled Environment:

2. Keystore Options

Store Type: JCEKS

Alias: ouaf.system

Alias Key Algorithm: AES

Alias Key Size: 128

HMAC Alias: ouaf.system.hmac

Padding: PKCS5Padding

Mode: CBC

50. Environment Installation Options

Environment Mount Point: <Mandatory> - Install Location

Log Files Mount Point:<Mandatory> - ThreadPoolWorker Logs

Location

Environment Name:<Mandatory>

Web Application Server Type: WLS

Install Application Viewer Module: true

Each item in the above list should be configured for a successful install.

Choose option (1,2,50, <P> Process, <X> Exit):

9.

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

WebLogic Server Name: myserver

Business Server Application Name: SPLService

MPL Admin Port Number: <Mandatory> - Multipurpose Listener

Port

MPL Automatic startup: false

3. Web Application Server Configuration

Web Server Host: <Mandatory>

WebLogic SSL Number: <Mandatory>

WebLogic Console Port Number: <Mandatory>

WebLogic Additional Stop Arguments:

Web Context Root: ouaf

WebLogic JNDI User ID: <Mandatory>

WebLogic JNDI Password: <Mandatory>

WebLogic Admin System User ID: <Mandatory>

WebLogic Admin System Password: <Mandatory>

WebLogic Server Name: myserver

Web Server Application Name: SPLWeb

Deploy Using Archive Files: true

Deploy Application Viewer Module: true

Enable The Unsecured Health Check Service: false

MDB RunAs User ID:

Super User Ids: SYSUSER

4. Database Configuration

Application Server Database User ID: <Mandatory>

Application Server Database Password: <Mandatory>

MPL Database User ID: <Mandatory>

MPL 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: <Mandatory>

JDBC Database User ID: <Mandatory>

JDBC Database Password: <Mandatory>

Database Name: <Mandatory>

Database Server: <Mandatory>

Database Port: <Mandatory>

ONS Server Configuration: <Mandatory>

Database Override Connection String: <Mandatory>

Character Based Database: <Mandatory>

Oracle Client Character Set NLS_LANG: AMERICAN_AMERICA.AL32UTF8

5. General Configuration Options

Batch RMI Port: <Mandatory> - RMI port

for batch

RMI Port number for JMX Business:

RMI Port number for JMX Web:

JMX Enablement System User ID:

JMX Enablement System Password:

Coherence Cluster Name: <Mandatory> - Unique

name for batch

Coherence Cluster Address: <Mandatory> - Unique

Multicast address

Coherence Cluster Port: <Mandatory> - Unique

port for batch cluster

Coherence Cluster Mode: <Mandatory> - prod

6. SSL Certificate Keystore

Certificate Keystore Type: CUSTOM

Identify Keystore File:

Identify Keystore File Type: jks

Identify Keystore Password:

Identity Private Key Alias:

Trust Keystore File:

Trust Keystore File Type: jks

Trust Keystore Password:

Trust Private Key Alias:

7. OUAF TrustStore Options

Import TrustStore Directory:

Store Type: JCEKS

Alias: ouaf.system

Alias Key Algorithm: AES

Alias Key Size: 128

HMAC Alias: ouaf.system.hmac

Padding: PKCS5Padding

Mode: CBC

Each item in the above list should be configured for a successful install.

Choose option (1,2,3,4,5,6,7, <P> Process, <X> Exit):

10.

When you are done with the parameter setup, proceed with the option P. The utility writes the configured parameters and their values into the configuration file.

11.

Once the install has finished, the installation log location appears 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. You can now install Oracle Utilities Service and Measurement Data Foundation as described in the following section.

Installing Oracle Utilities Application Framework V4.3.0.4.0 Single Fix Prerequisite Rollup for SMDF V2.2.0.1.0

1.

Navigate to ../App/FW43040_Rollup.

2.

Refer to the Readme.txt inside 'FW43040_Rollup' file for instructions on installing the Oracle Utilities Application Framework V4.3.0.4.0 Prerequisite Single Fixes.

These patches are also available for download separately from My Oracle Support.

See Appendix E for a list of the patches contained in the rollup.

Installing Oracle Utilities Service and Measurement Data Foundation V2.2.0.1.0 Application Component

This section describes how to install the application component of Oracle Utilities Service and Measurement Data Foundation, including:

•

Copying and Decompressing Install Media

•

Installing Oracle Utilities Service and Measurement Data Foundation V2.2.0.1

Copying and Decompressing Install Media

The installation file is delivered in jar format for both UNIX and Windows platforms.

The Oracle Utilities Service and Measurement Data Foundation is delivered as a separate installation package. Please refer to the chapter Supported Platforms and Hardware Requirements for installation details regarding the database and operating system versions supported for the Service and Measurement Data Foundation. Also see the section Installing Application Server Prerequisite Software for prerequisite third-party software installation instructions.

1.

Log in to the application server as the Oracle Utilities Application Framework administrator user ID (default cissys). This is the same user ID that was used to install the Oracle Utilities Application Framework.

2.

Navigate to ../App/SMDF.V2.2.0.1.0.

Installing Oracle Utilities Service and Measurement Data Foundation V2.2.0.1

This section outlines the steps for installing the Service and Measurement Data Foundation.

Preparing for the Installation

1.

Log on as Oracle Utilities Service and Measurement Data Foundation 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.

UNIX

$SPLEBASE/bin/spl.sh stop

Windows

%SPLEBASE%\bin\spl.cmd stop

Installing the Application

1.

Execute the script:

UNIX

ksh ./install.sh

Windows

install.cmd

Note: On UNIX, ensure that you have the proper execute permission on install.sh

The Configuration menu for the Oracle Utilities Service and Measurement Data Foundation Application appears.

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 SMDF SOA Configuration Plan.

Use the completed SOA Configuration Plan (SMDF) 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.

Installation of Oracle Utilities Service and Measurement Data Foundation Application Server is complete if no errors occurred during installation.

Installing the Oracle Utilities Meter Data Management V2.2.0.1.0 Application Component

This section describes how to install the application component of Oracle Utilities Meter Data Management, including:

•

Installation Prerequisite

•

Copying and Decompressing Install Media

•

Installing the Application Component

To proceed with the Oracle Utilities Meter Data Management installation you need to be connected to the target Oracle Utilities Service and Measurement Data Foundation application environment. See the detailed installation instructions in the following section.

You must initialize the Service and Measurement Data Foundation environment. For detailed instructions see the Preparing for the Installation section.

Installation Prerequisite

The Oracle Utilities Service and Measurement Data Foundation 2.2.0.1.0 application must be installed prior to installing Oracle Utilities Meter Data Management 2.2.0.1.0.

Copying and Decompressing Install Media

The Oracle Utilities Meter Data Management installation file is delivered in jar format for both UNIX and Windows platforms.

Download the installation package and proceed as follows:

1.

Log in to the application server host as the Oracle Utilities Application Framework administrator user ID (default cissys). This is the same user ID that was used to install the Oracle Utilities Application Framework.

2.

Navigate to ../App/MDM.V2.2.0.1.0.

Preparing for the Installation

1.

Log on as Oracle Utilities Service and Measurement Data Foundation 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.

UNIX

$SPLEBASE/bin/spl.sh stop

Windows

%SPLEBASE%\bin\spl.cmd stop

Installing the Application Component

1.

Execute the install script:

Note: On UNIX, ensure that you have the proper execute permission on install.sh.

UNIX

ksh ./install.sh

Windows

install.cmd

Choose option P to proceed with the installation.

Installation of Oracle Utilities Oracle Utilities Meter Data Management Server is complete if no errors occurred during the installation.

2.

Start up the environment. Run the following command:

UNIX

spl.sh start

Windows

spl.cmd start

Follow the message on the screen and review the logs in $SPLSYSTEMLOGS directory to ensure that the environment was started successfully.

If the startup failed, identify the problem by reviewing the logs. Resolve any issues before attempting to restart the environment.

Note : The first time you start Oracle Utilities Meter Data Management, you need to log into the WebLogic console and give system access to cisusers role. The WebLogic console application can be accessed through the following URL: http://<hostname>:<portname>/console.

Upgrading Oracle Utilities Meter Data Management

This release supports the following upgrade paths:

•

Oracle Utilities Meter Data Management version 2.1.0.3.0 or 2.2.0.0.0 to version 2.2.0.1.0.

Note: If you have a version prior to 2.1.0.3.0, you must install 2.1.0.3.0 before upgrading to 2.2.0.1.0.

This chapter includes:

•

Before You Upgrade

•

Upgrade Procedure

•

Operating the Application

Before You Upgrade

Review the list of operating system, application server and database server combinations that this version of Oracle Utilities Meter Data Management is certified to operate on, in the Chapter 2 : Supported Platforms and Hardware Requirements .

For further assistance, contact My Oracle Support before you upgrade.

Note: If you are upgrading a previously installed application server, it is recommended that you make a backup before you start the upgrade procedure. The upgrade installation will remove your existing environment including your configurations.

Upgrade Procedure

The upgrade installation procedure consists of:

•

Database Component Upgrade

•

Application Components Upgrade

Database Component Upgrade

Upgrade of the database component of Oracle Utilities Meter Data Management must be complete before you can proceed with the following sections. Refer to the section " Upgrade Install" of the Oracle Utilities Meter Data Management Database Administrator’s Guide, which provides instructions on upgrading the database component.

Application Components Upgrade

A successful upgrade consists of the following steps:

•

Upgrading the Oracle Utilities Application Framework V4.3.0 Service Pack 4 (4.3.0.4.0.0) Application Component

•

Installing Oracle Utilities Application Framework V4.3.0.4.0 Single Fix Prerequisite Rollup for SMDF V2.2.0.1.0

•

Upgrading the Oracle Utilities Service and Measurement Data Foundation Application Component to V2.2.0.1.0

•

Upgrading the Oracle Utilities Meter Data Management Application Component to V2.2.0.1.0

Upgrading the Oracle Utilities Application Framework V4.3.0 Service Pack 4 (4.3.0.4.0.0) Application Component

This section describes how to upgrade the application component of Oracle Utilities Application Framework, including:

•

Copying and Decompressing Install Media

•

Setting Permissions for the cistab file in UNIX

•

Upgrading the Application Component

Copying and Decompressing Install Media

The Oracle Utilities Application Framework V4.3.0 Service Pack 4 installation file is delivered in jar format for both 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 userid.

To copy and decompress the install media, follow these steps:

1.

Log in to the application server host with the Oracle Utilities Application Framework administrator user ID.

2.

Download the Oracle Utilities Meter Data Management V2.2.0.1.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 the file Oracle Utilities Meter Data Management V2.2.0.1.0 Multiplatform.zip to get the MDM_V2.2.0.1.0.zip 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>

unzip MDM_V2.2.0.1.0.zip

cd App

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 ../App/FW.V4.3.0.4.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 upgrade process. The installation utility does not create a backup of existing environment.

Upgrading the Application Component

This section outlines the steps for installing the application component of Oracle Utilities Application Framework V4.3.0.4.0.

Note: Customers who have a version prior to 2.1.0.3.0 must install 2.1.0.3.0 before upgrading to 2.2.0.1.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 bin folder.

cd <install_dir>/bin

where <install_dir> is the location where the Oracle Utilities Service and Measurement Data Foundation Base 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.

Stop the environment, if running:

UNIX

$SPLEBASE/bin/spl.sh stop

Windows

%SPLEBASE%\bin\spl.cmd stop

5.

Change directory to ../App/FW.V4.3.0.4.0.

NOTE : While installing the FW V4.3.0.4.0 from the previous environment to V2.2.0.1.0, the install utility removes the existing environment and re-creates the environment. Take a backup before you proceed with installing FW V4.3.0.4.0 to retain any configurations for future reference.

6.

Start the application installation utility by executing the appropriate script:

UNIX :

ksh ./install.sh

Windows :

install.cmd

7.

The Oracle Utilities Application Framework specific menu appears.

8.

Follow the messages and instructions that are produced by the application installation utility.

9.

Select each menu item to configure the values. For detailed description of the values, refer to Appendix B : Installation and Configuration Worksheets .

10.

The following is the mandatory list of configurable items 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. Third Party Software Configuration

Oracle Client Home Directory: <Mandatory>

Web Java Home Directory: <Mandatory>

Child JVM Home Directory:

COBOL Home Directory:

Hibernate JAR Directory: <Mandatory>

ONS JAR Directory:

Web Application Server Home Directory: <Mandatory>

ADF Home Directory:

OIM OAM Enabled Environment:

2. Keystore Options

Store Type: JCEKS

Alias: ouaf.system

Alias Key Algorithm: AES

Alias Key Size: 128

HMAC Alias: ouaf.system.hmac

Padding: PKCS5Padding

Mode: CBC

50. Environment Installation Options

Environment Mount Point: <Mandatory> - Install Location

Log Files Mount Point:<Mandatory> - ThreadPoolWorker Logs

Location

Environment Name:<Mandatory>

Web Application Server Type: WLS

Install Application Viewer Module: true

Each item in the above list should be configured for a successful install.

Choose option (1,2,50, <P> Process, <X> Exit):

11.

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

WebLogic Server Name: myserver

Business Server Application Name: SPLService

MPL Admin Port Number: <Mandatory> - Multipurpose Listener

Port

MPL Automatic startup: false

3. Web Application Server Configuration

Web Server Host: <Mandatory>

WebLogic SSL Number: <Mandatory>

WebLogic Console Port Number: <Mandatory>

WebLogic Additional Stop Arguments:

Web Context Root: ouaf

WebLogic JNDI User ID: <Mandatory>

WebLogic JNDI Password: <Mandatory>

WebLogic Admin System User ID: <Mandatory>

WebLogic Admin System Password: <Mandatory>

WebLogic Server Name: myserver

Web Server Application Name: SPLWeb

Deploy Using Archive Files: true

Deploy Application Viewer Module: true

Enable The Unsecured Health Check Service: false

MDB RunAs User ID:

Super User Ids: SYSUSER

4. Database Configuration

Application Server Database User ID: <Mandatory>

Application Server Database Password: <Mandatory>

MPL Database User ID: <Mandatory>

MPL 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: <Mandatory>

JDBC Database User ID: <Mandatory>

JDBC Database Password: <Mandatory>

Database Name: <Mandatory>

Database Server: <Mandatory>

Database Port: <Mandatory>

ONS Server Configuration: <Mandatory>

Database Override Connection String: <Mandatory>

Character Based Database: <Mandatory>

Oracle Client Character Set NLS_LANG: AMERICAN_AMERICA.AL32UTF8

5. General Configuration Options

Batch RMI Port: <Mandatory> - RMI port

for batch

RMI Port number for JMX Business:

RMI Port number for JMX Web:

JMX Enablement System User ID:

JMX Enablement System Password:

Coherence Cluster Name: <Mandatory> - Unique

name for batch

Coherence Cluster Address: <Mandatory> - Unique

Multicast address

Coherence Cluster Port: <Mandatory> - Unique

port for batch cluster

Coherence Cluster Mode: <Mandatory> - prod

6. SSL Certificate Keystore

Certificate Keystore Type: CUSTOM

Identify Keystore File:

Identify Keystore File Type: jks

Identify Keystore Password:

Identity Private Key Alias:

Trust Keystore File:

Trust Keystore File Type: jks

Trust Keystore Password:

Trust Private Key Alias:

7. OUAF TrustStore Options

Import TrustStore Directory:

Store Type: JCEKS

Alias: ouaf.system

Alias Key Algorithm: AES

Alias Key Size: 128

HMAC Alias: ouaf.system.hmac

Padding: PKCS5Padding

Mode: CBC

Each item in the above list should be configured for a successful install.

Choose option (1,2,3,4,5,6,7, <P> Process, <X> Exit):

12.

When you are done with the parameter setup, proceed with the option P. The utility writes the configured parameters and their values into the configuration file.

Once the install has finished, the installation log location appears 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. You can now install Oracle Utilities Service and Measurement Data Foundation as described in the following section.

Installing Oracle Utilities Application Framework V4.3.0.4.0 Single Fix Prerequisite Rollup for SMDF V2.2.0.1.0

1.

Navigate to ../App/FW43040_Rollup.

2.

Refer to the Readme.txt inside 'Application-Server-Multiplatform' file for instructions on installing the Oracle Utilities Application Framework 4.3.0 Service Pack 4 Prerequisite Single Fixes.

These patches are also available for download separately from My Oracle Support.

See Appendix E for a list of the patches contained in the rollup.

Upgrading the Oracle Utilities Service and Measurement Data Foundation Application Component to V2.2.0.1.0

This section describes how to upgrade the application component of Oracle Utilities Service and Measurement Data Foundation, including:

•

Copying and Decompressing Install Media

•

Upgrading the Application Component

Copying and Decompressing Install Media

The Oracle Utilities Service and Measurement Data Foundation file is delivered in jar format for both 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 userid.

1.

Log in to the application server as the Oracle Utilities Application Framework administrator user ID (default cissys). This is the same user ID that was used to install the Oracle Utilities Application Framework.

2.

Navigate to the ../App/SMDF.V2.2.0.1.0 directory.

Upgrading the Application Component

Follow the steps below to install the application component of Oracle Utilities Service and Measurement Data Foundation:

1.

Log on as Oracle Utilities Service and Measurement Data Foundation 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 it is running.

UNIX:

$SPLEBASE/bin/spl.sh stop

Windows:

%SPLEBASE%\bin\spl.cmd stop

Installing the Application

1.

Execute the script:

UNIX:

ksh ./install.sh

Windows :

install.cmd

Note : On UNIX, ensure that you have the proper execute permission on install.sh

The configuration menu for the Oracle Utilities Service and Measurement Data Foundation Application appears.

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 (MDF) worksheet to assist you in this step. See the Appendix B : Installation and Configuration Worksheets .

When you are done with the parameter setup, choose option P to proceed with the installation.

Installation of Oracle Utilities Service and Measurement Data Foundation Application Server is complete if no errors occurred during installation.

Upgrading the Oracle Utilities Meter Data Management Application Component to V2.2.0.1.0

This section describes how to install the application component of Oracle Utilities Meter Data Management, including:

•

Copying and Decompressing Install Media

•

Upgrading the Application Component

Copying and Decompressing 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, follow these steps:

1.

Log in to the application server host as the Oracle Utilities Application Framework administrator user ID (default cissys). This is the same user ID that was used to install the Oracle Utilities Application Framework.

2.

Navigate to ../App/MDM.V2.2.0.1.0 directory.

Upgrading the Application Component

Follow the steps below to install Oracle Utilities Meter Data Management application component:

1.

Log in to the application server host as Oracle Utilities Meter Data Management Administrator (default cissys).

2.

Change directory:

cd <install_dir>/bin

where <install_dir> is the location where the Oracle Utilities Service and Measurement Data Foundation 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.

If the environment is running, stop it by running the appropriate command:

UNIX

./spl.sh stop

Windows

spl.cmd stop

5.

Execute the install script:

Note: On UNIX, ensure that you have the proper execute permission on install.sh.

UNIX

ksh ./install.sh

Windows

install.cmd

Choose option P to proceed with the installation.

Installation of Oracle Utilities Oracle Utilities Meter Data Management Server is complete if no errors occurred during the installation.

6.

Start up the environment. Run the following command:

UNIX

spl.sh start

Windows

spl.cmd start

Follow the message on the screen and review the logs in $SPLSYSTEMLOGS directory to ensure that the environment was started successfully.

If the startup failed, identify the problem by reviewing the logs. Resolve any issues before attempting to restart the environment.

Note : The first time you start Oracle Utilities Meter Data Management, you need to log into the WebLogic console and give system access to cisusers role. The WebLogic console application can be accessed through the following URL: http://<hostname>:<portname>/console.

After the Upgrade

After you complete the upgrade installation, verify the following:

1.

Verify installation logs created under decompressed installer location for any errors.

2.

Confirm installation logs do not contain any errors.

3.

Confirm all the configurations are correct. Refer to Appendix B : Installation and Configuration Worksheets for details.

4.

Confirm that the database is ready.

5.

Start the application server. For instructions, refer to Appendix C : Common Maintenance Activities .

6.

To operate the application, refer to the Operating the Application section.

Operating the Application

At this point your installation and custom integration process is complete. Be sure to read the Oracle Utilities Meter Data Management Server Administration Guide for more information on further configuring and operating the system.

Additional Tasks

This section describes tasks that should be completed after installing Oracle Utilities Meter Data Management, including:

•

Importing Self-Signed Certificates

•

Customizing Configuration Files

•

Integrating Existing Customer Modifications

•

Generating the Application Viewer

•

Building Javadocs Indexes

•

Configuring the Environment for Batch Processing

•

Customizing the Logo

•

Configuring Secure Sockets Layer (SSL)

•

Setting Up an Application Keystore

•

Deploying Inbound WebServices (IWS)

•

Domain Templates (Linux WebLogic 12.1.3.0+, WebLogic 12.2.1.1+ only)

•

Database Patching

•

BI Publisher Report Configuration

I mporting Self-Signed Certificates

If you are using self-signed certificates and the Inbound Web Services (IWS) feature, then it is necessary to import these certificates into the OUAF truststore file.

Perform the following commands:

1.

Start WebLogic.

2.

Initialize a command shell and setup the environment by running the following:

UNIX

$SPLEBASE/bin/splenviron.sh -e $SPLENVIRON

For example:

/ouaf/TEST_ENVIRON1/bin/splenviron.sh -e TEST_ENVIRON1

Windows

%SPLEBASE%\bin\splenviron.cmd -e %SPLENVIRON%

For example:

D:\ouaf\TEST_ENVIRON1\bin\splenviron.cmd -e TEST_ENVIRON1

3.

Execute the following script to generate all information:

UNIX

$SPLEBASE/bin/initialSetup.sh -i

Windows

%SPLEBASE%\bin\ initialSetup.cmd -i

Note : This needs to be performed before deploying the IWS application.

Customizing Configuration Files

If you wish to make customer modifications to various configuration files, create a ‘CM copy’ of the template file or a user exit. This preserves your changes whenever initialSetup is executed; otherwise, your changes to the delivered template files will be lost if it is patched in the future:

For example, to customize hibernate properties of the SPLWeb web application, perform the following:

1.

Locate the hibernate.properties.template in the $SPLEBASE/templates directory

2.

Copy the file to cm.hibernate.properties.template.

3.

Apply your changes to cm.hibernate.properties.template.

4.

Update application war file with the latest changes by executing the following command:

UNIX

$SPLEBASE/bin/initialSetup.sh

Windows

%SPLEBASE%\bin\initialSetup.cmd

Refer to the Oracle Utilities Application Framework SDK documentation for more details.

Integrating Existing Customer Modifications

Existing Customer Modifications (CM) applied to an application server on an earlier release cannot be applied directly to a later version. CM code needs to be applied from an SDK version compatible with this release.

Refer to SDK documentation for more information about migrating CM code.

Generating the Application Viewer

You may extend application viewer capabilities within an environment by generating additional items. These include information about algorithm types, algorithms, maintenance objects and data dictionary information. The Javadoc indexes are also re-built.

To generate the additional items in the application viewer, perform the following:

1.

Shut down the environment.

2.

Initialize a command shell and setup the environment by running the following:

UNIX

$SPLEBASE/bin/splenviron.sh -e $SPLENVIRON

For example:

/ouaf/TEST_ENVIRON1/bin/splenviron.sh -e TEST_ENVIRON1

Windows

%SPLEBASE%\bin\splenviron.cmd -e %SPLENVIRON%

For example:

D:\ouaf\TEST_ENVIRON1\bin\splenviron.cmd -e TEST_ENVIRON1

3.

Execute the following script to generate all information.

UNIX

ksh $SPLEBASE/bin/genappvieweritems.sh

Windows:

%SPLEBASE%\bin\genappvieweritems.cmd

4.

Restart your application.

Building Javadocs Indexes

Rebuilding Javadoc indexes is already part of generating application viewer above. However, there are times when you need to run it separately. For example, this is required after customer modifications (CM) have been applied to an environment when it includes Java code.

Perform the following to rebuild the Javadoc indexes.

Windows

%SPLEBASE%\bin\buildJavadocsIndex.cmd

UNIX

ksh $SPLEBASE/bin/buildJavadocsIndex.sh

Configuring the Environment for Batch Processing

See the Server Administration Guide for information on configuring the environment for batch processing.

Customizing the Logo

To replace the Oracle Utilities logo on the main menu with another image, put the new image <customer_logo_file>.png file into the directory $SPLEBASE/etc/conf/root/cm and create a new "External" Navigation Key called CM_logoImage. To do that, run the Oracle Utilities application from the browser with the parameters: http://<hostname>:<port>/cis.jsp?utilities=true&tools=true.

From the Admin menu, select Navigation Key.

Add the above Navigation Key with its corresponding URL Override path.

The syntax for the URL path is:

Windows:

http://<host name>:<port>/<Web Context>/cm/<customer_logo_file>.png

UNIX:

http://<host name>:<port>/<Web Context>/cm/<customer_logo_file>.png

The root directory may be deployed in war file format for runtime environment (SPLApp.war). Use provided utilities to incorporate your cm directory into SPLApp.war file.

Configuring Secure Sockets Layer (SSL)

Secure Sockets Layer (SSL) provides secure connections by allowing two applications connecting over a network to authenticate each other's identity and by encrypting the data exchanged between the applications. Authentication allows a server, and optionally a client, to verify the identity of the application on the other end of a network connection. Encryption makes data transmitted over the network intelligible only to the intended recipient

Follow these steps to configure Secure Sockets Layer:

1.

Obtain an identity (private key and digital certificates) and trust (certificates of trusted certificate authorities) for WebLogic Server.

Use the digital certificates, private keys, and trusted CA certificates provided by the WebLogic Server, the CertGen utility, the keytool utility, or a reputable vendor such as Entrust or Verisign to perform this step.

2.

Store the identity and trust.

Private keys and trusted CA certificates which specify identity and trust are stored in keystores.

3.

Configure the identity and trust keystores for WebLogic Server in the WebLogic Server Administration Console.

See "Configure keystores" in the Oracle WebLogic Server Administration Console Online Help.

For additional information on configuring keystores, refer to http://docs.oracle.com/middleware/1213/wls/WLACH/taskhelp/security/ConfigureKeystoresAndSSL.html

4.

Set SSL configuration options for the private key alias and password in the WebLogic Server Administration Console.

Optionally, set configuration options that require the presentation of client certificates (for two-way SSL).

For additional information, refer to the following topics:

•

Servers: Configuration: SSL ( http://docs.oracle.com/middleware/1213/wls/WLACH/pagehelp/Corecoreserverserverconfigssltitle.html )

•

Configure two-way SSL ( http://docs.oracle.com/middleware/1213/wls/WLACH/taskhelp/security/ConfigureTwowaySSL.html)

•

Obtaining and Storing Certificates for Production Environments ( http://docs.oracle.com/middleware/1213/wls/SECMG/identity_trust.htm#SECMG798)

•

Configuring Keystores with WebLogic Server ( http://docs.oracle.com/middleware/1213/wls/SECMG/identity_trust.htm#SECMG383)

Note : Depending on your choice of implementation you may need to change some configuration files. These files are managed by templates and will be overwritten if the procedures documented in "Customizing Configuration Files" are not followed.

The identity and trust keystore files and other SSL certificate related options are configured using the configureEnv.sh|cmd utility.

Setting Up an Application Keystore

This section describes how to set up a keystore in your system. The keystore is used for functionality such as digital signatures for document numbers, and encryption for credit card security.

Note that this different from the Oracle Utilities Application Framework (also called the system) keystore and the WebLogic SSL keystores.

For additional information about document numbers, digital signatures, and encryption, see the online help.

For additional information about using the Java keytool utility, see the following section of the Oracle Java SE documentation:

http://docs.oracle.com/javase/7/docs/technotes/tools/solaris/keytool.html

Follow this procedure to set up the keystore in your environment:

1.

Generate the keystore. The following command creates the file ".mykeystore" in directory ${SPLEBASE}:

keytool -genkeypair -alias <keyalias> -keyalg RSA -sigalgSHA256withRSA -keystore ${SPLEBASE}/<filename> -keysize 1024 -storetype JCEKS -dname "CN=<name>, OU=<unit>, O=<organization>, C=<country>" -validity 365

For example:

keytool -genkeypair -alias ouaf.application -keyalg RSA -sigalg SHA256withRSA -keystore ${SPLEBASE}/.mykeystore -keysize 1024 -storetype JCEKS -dname "CN=Mark Jones, OU=TUGBU, O=Oracle, C=US" -validity 365

The utility will prompt you for the keystore and key passwords. Make sure that they are the same.

2.

Configure the following template files by adding the following entries:

For WebLogic Server:

•

To enable in WebLogic, edit the following in ${SPLEBASE}/templates/startWeblogic.sh.template:

JAVA_OPTIONS="$JAVA_OPTIONS -Dcom.oracle.ouaf.keystore.file=$SPLEBASE/<filename>"

JAVA_OPTIONS="$JAVA_OPTIONS -Dcom.oracle.ouaf.keystore.password=<keystore_password>"

For <keystore_password>, use the same password entered in the keytool utility.

•

To enable this in batch, edit the threadpoolworker.properties.template:

com.oracle.ouaf.keystore.file=@force_forward_slash(SPLEBASE)@/.mykeystore

com.oracle.ouaf.keystore.password=<keystore_password>

Note: Because the path needs to be passed with forward slashes even on Windows platforms, the force_forward_slash function will convert any "\" to "/".

For <keystore_password>, use the same password entered in the keytool utility.

List of spl.properties templates (located in ${SPLEBASE}/templates/ folder):

•

spl.properties.iws.template

•

spl.properties.template

•

spl.properties.service.template

•

spl.properties.XAIApp.template

•

spl.properties.standalone.template

3.

Re-initialize the environment to propagate these changes by executing the initialSetup.sh/cmd.

4.

Restart the environment.

Deploying Inbound WebServices (IWS)

All existing XAI Inbound Services have been duplicated as Inbound Web Services as the application moves toward deprecation of XAI and full transition to IWS in the next release. The duplicated services are designed to work seamlessly in this release, and customers providing custom services are encouraged to migrate to IWS to take full advantage of the new, more efficient Web service technology.

For more information on migrating from XAI to IWS, please refer to Migrating from XAI to IWS Oracle Utilities Application Framework (Doc ID 1644914.1) on My Oracle Support.

Note : This is an optional step for customers using IWS instead of XAI services.

For deploying IWS, please follow the steps below:

For UNIX

1.

Enable the Web Services Functionality as shown below:

a.

cd $SPLEBASE/bin

b.

Execute configureEnv.sh -a

Select option 50 and set the option "Enable Web Services Functionality" to true. Enter "P" to process.

2.

Execute initialSetup.sh as shown below:

cd $SPLEBASE/bin

ksh ./initialSetup.sh

3.

Set the classpath as shown below:

$ CLASSPATH=$WL_HOME/server/lib/weblogic.jar:$CLASSPATH

$ export CLASSPATH

$ cd $SPLEBASE/bin

4.

Execute the following command:

$ java weblogic.Admin -username <username> -password <password> STOREUSERCONFIG -userconfigfile $SPLEBASE/etc/.wlsuserconfig - userkeyfile $SPLEBASE/etc/.wlsuserkey

Select y

5.

Execute the below step in $SPLEBASE/bin. Please note that the application server should be up before running the below command.

ksh ./iwsdeploy.sh

For WINDOWS

1.

Enable the Web Services Functionality as shown below:

cd %SPLEBASE%\bin

2.

Execute configureEnv.cmd -a

Select option 50 and set the option "Enable Web Services Functionality" to true. Enter "P" to process.

3.

Execute initialSetup.cmd as shown below:

cd %SPLEBASE%\bin initialSetup.cmd

4.

Set the classpath as shown below:

set CLASSPATH=%WL_HOME%\server\lib\weblogic.jar;%CLASSPATH%

5.

Execute the following command:

java weblogic.Admin -username system -password ouafadmin STOREUSERCONFIG -userconfigfile %SPLEBASE%\etc\.wlsuserconfig - userkeyfile %SPLEBASE%\etc\.wlsuserkey

Select y

6.

Execute the below step in %SPLEBASE%\bin. Please note that the application server should be up before running the below command.

iwsdeploy.cmd

Domain Templates (Linux WebLogic 12.1.3.0+, WebLogic 12.2.1.1+ only)

The intended use of the domain templates is for native/clustered installation of the Oracle Utilities Application Framework (OUAF) environment into a WebLogic domain. The domain template(s) defines the core set of resources within a WebLogic domain, including an Administration Server along with the basic configuration information for a Oracle Utilities Application Framework based application. The domain template is a "snapshot" of the delivered embedded "splapp" domain. When working with domain templates you will need to manage the application (stopping, starting, deployment, undeployment) utilizing the WebLogic delivered utilities.

•

Install and configure application stack (OUAF and Edge Product)

Note: Environment will need to be configuring to deploy in ear format.

•

Review domain templates (Simple /Complex)

•

Execute config.sh and enter the path of the domain template file

•

Configure domain

•

Complete domain configuration

Note: Configure nodemanager.properties and setDomainEnv.sh

•

Update SPLEBASE (ENVIRON.INI)

Detailed Description

The product installation includes a two predefined WebLogic Server Domain templates. The delivered domain templates are located under the SPLEBASE:

$SPLEBASE/tools/domaintemplates

•

Oracle-Utilities-Simple-Linux-12.1.3.0.0.jar

•

Oracle-Utilities-Complex-Linux-12.1.3.0.0.jar

•

Oracle-Utilities-Simple-Unix-12.2.1.1.0.jar

The Simple Domain Template is for use with one machine and does not include a WebLogic cluster, this domain configuration is similar to current delivered embedded splapp domain, with the exception that there will be two WebLogic servers (utilities_server1 and a "Admin Server").

The Complex Domain Template is configured for use with a pre-configured WebLogic cluster, with one machine configured, node manager settings, and one managed server configured.

The delivered domain templates defines the full set of resources within an Oracle Utilities Application Framework domain including:

•

Demo certificates (the demo certificates will need to be updated for production use)

•

Setting of XML Registry Settings

•

Setting of Default users and groups

•

Machine configuration

•

Default Users and Groups

Note : The Users and Groups match the delivered values delivered with the embedded domain.

•

JTA Settings

•

Node Manager Settings

•

WebLogic Server

Configure Node Manager Properties to allow SSL

Follow the steps below to update the nodemanager.properties with the correct Private Key Passphrase.

Under the following location: DOMAIN_HOME/nodemanager update the following properties in the nodemanager.properties file:

•

CustomIdentityKeyStorePassPhrase=

•

CustomIdentityPrivateKeyPassPhrase=

Set these to the value "0uaf_demo_c3rt"

Note : At first when the node manager is started, the values in the file will be encrypted. These values will need to updated in production configuration with the proper values based on your configuration.

Configure setDomainEnv.sh Script

You will need to set the value of SPLEBASE with the proper value for your implementation. Under the following location, DOMAIN_HOME/bin, update the setDomainEnv.sh file and add the following

SPLEBASE="${SPLEBASE}"

Note : You will need to update ${SPLEBASE} with appropriate value based on your configuration.

Update SPLEBASE

The following update in the configuration indicates if the embedded configuration is being utilized or if the environment is a native installation to Weblogic. When this item is populated in the environment, the delivered base tools will be able to identify that the starting and stopping of the environment are being done under the domain home.

1.

Initialize the Environment: splenviron.sh -e <Environment_Name>

2.

Execute: configureEnv.sh -a

3.

Select Menu Item: 52. Advanced Web Application Configuration

=================================================

4.

02. Configuration Option: Domain Home Location

Current Value <ENTER>:

The WebLogic Domain Home location, when this parameter is populated you will need to use the native WebLogic tools for maintenance (starting, stopping, deployment, and undeployment).

Enter Value: <Enter your domain home location>

5.

Once the Domain Home location has been completed, Enter <P> Process

Update setDomainEnv.sh

Edit setDomainEnv.sh and change antlr, serializer and xalan jar versions to the following:

•

antlr-2.7.7.jar

•

serializer-2.7.2.jar

•

xalan-2.7.2.jar

Update setUserOverrides.sh

Edit setUserOverrides.sh and add the below to JAVA_OPTIONS. For AIX, the below parameters also need to be added to JAVA_OPTIONS.

-Djavax.xml.transform.TransformerFactory=org.apache.xalan.processor.TransformerFactoryImpl -Djavax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema=org.apache.xerces.jaxp.validation.XMLSchemaFactory

Database Patching

The database patching utility is delivered under SPLEBASE and is Java-based so you are able to create a standalone package to be able to install database patches on a separate server that has Java 7 installed. You can also install database patches using the components that are delivered under SPLEBASE without the need to move the database patching utility to a different server.

The following is an overview of the process to install database patches on a separate server. You will need to create a jar file containing the utilities and supporting files to allow you to run the database patch installer on another server.

To generate the jar file:

1.

Initialize a command shell:

The scripts that are provided with the system need to be run from a shell prompt on the machine where you installed the application server. Before such scripts can be run the shell must be "initialized" by running the splenviron script provided with the system.

UNIX

Log on to your UNIX box as the Oracle Utilities Administrator (default cissys) and open a shell prompt.

In the following example, replace the variables

•

$SPLEBASE with the Full directory name that you installed the application into

•

$SPLENVIRON with the name you gave to the environment at installation time

To initialize the environment enter:

$SPLEBASE/bin/splenviron.sh -e $SPLENVIRON

For example:

/ouaf/DEMO/bin/splenviron.sh -e DEMO

Windows

The command window should be opened on the Windows server that you installed the application on.

In the below example you should replace the following variables:

•

%SPLEBASE%: The Full directory name that you installed the application into

•

%SPLENVIRON%: The name you gave to the environment at installation time

To initialize the environment, type the following in your command prompt:

%SPLEBASE%\bin\splenviron.cmd -e %SPLENVIRON%

For example:

D:\ouaf\DEMO\bin\splenviron.cmd -e DEMO

2.

Execute the following script to generate the jar file.

UNIX

ksh $SPLEBASE/bin/createDBStandlone.sh

Windows

%SPLEBASE%\bin\createDBStandlone.cmd

Note : By default, the output jar db_patch_standalone.jar is created in SPLEBASE/tools/dbstandalone. You can use the -l option to change the default directory.

3.

Transfer the generated jar (db_patch_standalone.jar) to the Windows/Unix machine where you want to run the database patching utility.

4.

Extract the contents of the archive file:

jar xvf db_patch_standalone.jar

Note : You must have Java 7 JDK installed on the machine to use the jar command. Be sure to install the JDK that is supported for your platform.

Overview of Database Patching Application

The database patching utility requires you have Java 7 JDK installed on the machine to execute the database patch application process.

The patch application process will perform following items to account for executing patch application under SPLEBASE or on a standalone server.

The database patch application utility will look do the following when it is executed:

•

Checks to see if the environment variable $SPLEBASE is set.

If the $SPLEBASE variable is set, the utility uses the libraries under $SPLEBASE to apply the patch.

•

When the $SPLEBASE is not set, the utility checks to see if the TOOLSBIN environment variable is set.

If the TOOLSBIN is set, the utility uses the libraries under the TOOLSBIN location.

•

When both SPLEBASE and TOOLSBIN environment are not set, the utility prompts for the location of the TOOLSBIN.

The TOOLSBIN is the location of the of the application scripts ouafDatabasePatch.sh[cmd].

Unix Example:

The TOOLSBIN location would be set to /ouaf/dbpatch/bin

export TOOLSBIN=/ouaf/dbpatch/bin

Unix Sample - Database Patch Application (ouafDatabasePatch.sh)

Note : The default permissions (ouafDatabasePatch.sh), may need to be adjusted to be executed by your user and group, when applying database fixes.

•

Sample Execution - Passing a Password

./ouafDatabasePatch.sh -x ouafadm -p "-t O -d CISADM_Z1_12C_43020_BLD001,slc04lds:1522:Z143Q12C"

•

Sample Execution - Prompting for a Password

./ouafDatabasePatch.sh -p "-t O -d CISADM_Z1_12C_43020_BLD001,slc04lds:1522:Z143Q12C"

•

Sample Execution - passing in the tools bin location

/ouafDatabasePatch.sh -u

ouafDatabasePatch.sh [-h] [-u] [-v] [-x] [-t tools dir] [-p ouafparms]

-h displays help of ouafpatch

-u displays usage of ouafDatabasePatch.sh

-v displays version of ouafpatch

-x password to be passed to ouafpatch

-b location of the tools bin directory

-p parameters directly passed to ouafpatch

must be the last parameter passed and

be enclosed with quotes

WINDOWS Example:

The TOOLSBIN location would be set to c:\ouaf\dbpatch\bin

SET TOOLSBIN=c:\ouaf\dbpatch\bin

Windows Sample - Database Patch Application (ouafDatabasePatch.cmd)

•

Sample Execution - Passing a Password

ouafDatabasePatch.cmd -x password -p "-t O -d SCHEMA_NAME,DBSERVER:DBPORT:DBSID"

•

Sample Execution - Prompting for a Password

ouafDatabasePatch.cmd -p "-t O -d SCHEMA_NAME,DBSERVER:DBPORT:DBSID C"

•

Sample Execution - passing in the tools bin location

ouafDatabasePatch.cmd -b "C:\temp\db_patch_standalone\bin" -p "-t O -d SCHEMA_NAME,DBSERVER:DBPORT:DBSID -c C:\temp\dbrollup\CDXPatch2\CDXPatch.ini"

Windows Sample Usage

ouafDatabasePatch.cmd -u

USAGE:

USAGE:ouafDatabasePatch.cmd[-h] [-u] [-v] [-x] [-b tools dir] [-p ouafparms]

USAGE: -h displays help of ouafpatch

USAGE: -u displays usage of ouafDatabasePatch.cmd

USAGE: -v displays version of ouafpatch

USAGE: -x password to be passed to ouafpatch

USAGE: -b location of the tools bin directory

USAGE: -p parameters directly passed to ouafpatch

USAGE: must be enclosed with quotes: " "

USAGE:

USAGE:

USAGE:

BI Publisher Report Configuration

This section describes the steps required to configure Oracle Utilities Meter Data Management and Oracle BI Publisher to support a reporting solution that uses Oracle BI Publisher.

This release of Oracle Utilities Meter Data Management has a separate bundle with a sample BI Publisher 11g report.

Unzip Oracle Utilities Meter Data Management Report Files

1.

Unzip the MDM-V2.2.0.1.0-Reports.zip file from the installation media into an <TEMPDIR> directory. We'll refer to this directory as the reports extract folder.

2.

For both UNIX and Windows platforms, a sub-directory named BIPublisher11g is created. The contents of the installation directory are identical for both platforms.

Note: By default, the reports provided are read only. You will need to reset the permissions on the files before making any changes, for example, to configure the default data source.

Publish the Sample Reports in Oracle BI Publisher Enterprise

The installation media contains sample reports provided with the system. The report files are in the reports extract folder under < TEMPDIR >\BIPublisher11g\reportFiles

Install Oracle BI Publisher Enterprise. This section assumes that you have already installed Oracle BI Publisher Enterprise.

To configure the BI Publisher reports, follow these steps:

1.

Create a folder named D2_VEEEME in the <BI_Repository_Path>\Reports folder

2.

Copy D2_VEEEME.xdo and D2_VEEEME.xdm folders to <BI_Repository_Path>\Reports\D2_VEEEME folder

Note: To check for the location of your <BI_Repository_Path>, log in to the BI console as an Administrator and go to Administration, Server Configuration. If the repository type is File System, the path will be seen in Catalog region. If the repository type is not File System you cannot load the sample reports.

3.

Login as Administrator to BI Publisher server.

4.

Go to the Administration tab.

a.

In the JDBC Connection section under Data Sources, add a new data source using Add Data Source.

b.

Create a new Data Source named D2 201 Dev with connection details pointing to the D2 201 Dev database.

c.

Test Connection to make sure the Database connection is successful and save changes using Apply.

Note : Make sure the Data Source Name (D2 201 Dev) is created with the same name else the reports won't show up.

5.

Go to the Catalog Tab

a.

Click New->Report from dropdown list and select "Use Existing Data Model" option to create new reports using existing data model and then select Data Model from the Shared folders Catalog.For example: ./Shared Folders/D2_VEEEME/D2_VEEEME.xdm).

b.

Click Next and select "Use Report Editor" option. Click Finish.

c.

Select My Folder and save report name as D2_VEEEME.

6.

Go to the Catalog tab, select D2_VEEEME Report under My folders and click Open. Once the report is open, click Actions and Export Data as XML. Save it.

7.

Go to the Catalog tab, select My Folders and click on Edit Report (D2_VEEEME) and then click on Data Model D2_VEEEME. Under Attachment click on "Upload Sample data" and browse the xml file saved from above and then upload it. Click on Save and return.

8.

Click Add New Layout. Under Upload or Generate Layout, click Upload and give Layout Name as D2_VEEEME.rtf.

Browse Template File to <BI_Repository_Path>\Reports\D2_VEEEME\D2_VEEEME.xdo folder and select D2_VEEEME.rtf file. Select type as RTF template and Locale as English and click on Upload.

9.

Click View Report to see reports.

Note : Please follow the same steps for configuring other reports except for step 4.

Installation Menu Functionality Overview

This chapter provides an overview of the Installation Menu Functionality and also the respective menu details.

The main configuration menu is structured so that related variables and/or options are grouped together and are associated by a menu item number. To access a particular group of variables and options, enter the menu item number associated with that group. Each option is displayed in turn on the screen, along with a prompt so that you can type the desired value for the option, if it is not the same as the default or current value.

When performing the initial installation you need to go through all menu options. The menu options may have a default value, a list of valid values and a validation check.

On each option prompt you can keep the current value by simply leaving the input line empty. In order to erase a variable value you need to enter one dot ("."). The leading spaces will be trimmed out on each values entered. The menu includes the following:

•

Valid Values: [ALFANUM]. This indicates you will need to enter an alphanumeric value in the prompt.

•

Valid Values: [NUM]. This indicates you will need to enter an numeric value in the prompt.

Please also note the following:

•

When all options are set, type <P> at the main menu prompt option. This will save the option values selected throughout the configuration.

•

During this processing the global variables are validated and the configuration file <SPLEBASE>/etc/ENVIRON.INI is created or updated. This file contains all the variables inputted and calculated. These are needed by the next part of the installation process.

•

To exit the configuration utility without saving any of the values entered, type <X> and press 'Enter'.

Installation Menu Functionality Details

The Environment Installation Utility requires that Oracle Client Home is set in the path for the user performing the installation.

Prior to running the installation utility you will need to review the supported platforms document to ensure you have all of the Third Party software installed.

In this menu if the variables are set prior to execution, that value will be defaulted by the installation utility when performing the installation.

When the installation has been completed successfully, the values will be written to an ENVIRON.INI file. When splenviron.sh / cmd is executed, it will read from the ENVIRON.INI file to set the environment variables. Refer to the Oracle Utilities Application Framework Server Administration Guide for details about configuring these values.

Install the Oracle Client software specified in the Supported Platforms section prior to running any of the installation utilities.

The following prompt will appear when executing the installation utility:

Enter Oracle Client Home Directory (<ENTER> quit):

Note: If the environmental variable ORACLE_CLIENT_HOME is set, the install script will validate the variable. If it passes the validation you will not be prompted for it. This is needed in order to run Perl installation utilities.

Encryption Methods

When the application server choice is Oracle WebLogic, the Oracle Utilities Application Framework installation uses the WebLogic API to encrypt the User ID and password that perform admin functions for the WebLogic application servers. Please refer to the WebLogic documentation for further information about the encryption.

The Oracle Utilities Application Framework installation also uses industry standard cryptography to encrypt passwords that are prompted within the installation.

When these passwords are entered in the command line, the input values are not reflected on the screen when performing the installation.

Installation and Configuration Worksheets

Application Framework Installation and Configuration Worksheets

During the installation and configuration of the application you will need to provide a variety of system values. These worksheets will assist you in providing that information. They should be completed before installing the application framework. No Customer Install Value fields should be left blank.

Note: Some web application server information will not be available until the software installation steps have been completed as described in the Installing Prerequisite Software section in the Chapter 3 : Planning the Installation for prerequisite third-party software installation instructions.

Refer to the Oracle Utilities Server Administration Guide for additional details (default, valid values, usage, etc.), as applicable.

Menu Block 1: Environment ID, Roles, Third Party Software Configuration

The Environment ID, Roles, Third Party Software Configuration options include:

Menu Option

Name Used in Documentation

Customer

Install Value

Environment ID

ENVIRONMENT_ID

Server Roles

SERVER_ROLES

Oracle Client Home Directory

ORACLE_CLIENT_HOME

Web Java Home Directory

JAVA_HOME

Hibernate JAR Directory

HIBERNATE_JAR_DIR

**ONS JAR Directory

ONS_JAR_DIR

Web Application Server Home Directory

WEB_SERVER_HOME

WebLogic Server Thin-Client JAR Directory

WLTHINT3CLIENT_JAR_DIR

* ADF Home Directory

ADF_HOME

OIM OAM Enabled Environment

OPEN_SPML_ENABLED_ENV

* Denotes optional menu items that may be required for the product installation and variables.

** In order to activate the RAC FCF, the application needs the external ons.jar file, from the ORACLE_HOME path:

$ORACLE_HOME/opmn/lib/ons.jar

During the installation the relevant option should be populated with the folder location of the ons.jar.

Menu Block 2: Keystore Options

The keystore is a set of files used for encryption, decryption and hash generation. The files reside in the following location:

<SPLEBASE>/ks/.ouaf_keystore

<SPLEBASE>/ks/.ouaf_storepass

In order to run the application correctly, data encryption, decryption and hash generation of data in the database and on the application server must be performed using the same keystore; otherwise, the application will fail.

Please review the section on configuring the OUAF Keystore in the Oracle Utilities Security Guide for information on setting up the keystore properly.

Keystore options include:

Menu Option

Name Used in Documentation

Customer

Install

Value

Import Keystore Directory

KS_IMPORT_KEYSTORE_FOLDER

Store Type

KS_STORETYPE

Alias

KS_ALIAS

Alias Key Algorithm

KS_ALIAS_KEYALG

Alias Key Size

KS_ALIAS_KEYSIZE

HMAC Alias

KS_HMAC_ALIAS

Padding

KS_PADDING

Mode

KS_MODE

Menu Block 50: Environment Installation Options

Environment installation options include:

Menu Option

Name Used in Documentation

Customer

Install

Value

Environment Mount Point

SPLDIR

Log File Mount Point

SPLDIROUT

Environment Name

SPLENVIRON

Web Application Server Type

SPLWAS

Installation Application Viewer Module

WEB_ISAPPVIEWER

Install Demo Generation Cert Script

CERT_INSTALL_SCRIPT

Install Sample CM Source Code

CM_INSTALL_SAMPLE

Menu Block 1: Environment Description

The environment description menu option includes:

Menu Option

Name Used in Documentation

Customer

Install

Value

Environment Description

DESC

Menu Block 2: [WebLogic] Business Application Server Configuration

WebLogic Business Application Server configuration options include:

Menu Option

Name Used in Documentation

Customer

Install

Value

Business Server Host

BSN_WLHOST

WebLogic Server Name

BSN_WLS_SVRNAME

Business Server Application Name

BSN_APP

MPL Admin Port number

MPLADMINPORT

MPL Automatic Startup

MPLSTART

Menu Block 3: [WebLogic] Web Application Server Configuration

WebLogic Web Application Server configuration options include:

Menu Option

Name Used in Documentation

Customer

Install

Value

Web Server Host

WEB_WLHOST

Weblogic SSL Port Number

WEB_WLSSLPORT

Weblogic Console Port Number

WLS_ADMIN_PORT

Weblogic Additional Stop Arguments

ADDITIONAL_STOP_WEBLOGIC

Web Context Root

WEB_CONTEXT_ROOT

WebLogic JNDI User ID

WEB_WLSYSUSER

WebLogic JNDI Password

WEB_WLSYSPASS

WebLogic Admin System User ID

WLS_WEB_WLSYSUSER

WebLogic Admin System Password

WLS_WEB_WLSYSPASS

WebLogic Server Name

WEB_WLS_SVRNAME

Web Server Application Name

WEB_APP

Deploy Using Archive Files

WEB_DEPLOY_EAR

Deploy Application Viewer Module

WEB_DEPLOY_APPVIEWER

Enable The Unsecured Health Check Service

WEB_ENABLE_HEALTHCHECK

MDB RunAs User ID

WEB_IWS_MDB_RUNAS_USER

Super User Ids

WEB_IWS_SUPER_USERS

Menu Block 4 - Database Configuration

The parameters below and in the worksheet are for the database configuration. Note that if changes are made to any of the database menu option items below, thus potentially connecting to a different schema, a warning will be displayed in the screen next to the actual option that has been changed.

Menu Option

Name Used in Documentation

Customer

Install

Value

Application Server Database User ID

DBUSER

Application Server Database Password

DBPASS

MPL Database User ID

MPL_DBUSER

MPL Database Password

MPL_DBPASS

XAI Database User ID

XAI_DBUSER

XAI Database Password

XAI_DBPASS

Batch Database User ID

BATCH_DBUSER

Batch Database Password

BATCH_DBPASS

Web JDBC DataSource Name

JDBC_NAME

JDBC Database User ID

DBUSER_WLS

JDBC Database Password

DBPASS_WLS

Database Name

DBNAME

Database Server

DBSERVER

Database Port

DBPORT

ONS Server Configuration

ONSCONFIG

Database Override Connection String

DB_OVERRIDE_CONNECTION

Character Based Database

CHAR_BASED_DB

Oracle Client Character Set NLS_LANG

NLS_LANG

Menu Block 5 - General Configuration Options

The general configuration options include:

Menu Option

Name Used in Documentation

Customer

Install

Value

Batch RMI Port

BATCH_RMI_PORT

RMI Port number for JMX Business

BSN_JMX_RMI_PORT_PERFORMANCE

RMI Port number for JMX Web

WEB_JMX_RMI_PORT_PERFORMANCE

JMX Enablement System User ID

BSN_JMX_SYSUSER

JMX Enablement System Password

BSN_JMX_SYSPASS

Coherence Cluster Name

COHERENCE_CLUSTER_NAME

Coherence Cluster Address

COHERENCE_CLUSTER_ADDRESS

Coherence Cluster Port

COHERENCE_CLUSTER_PORT

Coherence Cluster Mode

COHERENCE_CLUSTER_MODE

Menu Block 6 - SSL Certificate Keystore (WebLogic Only)

By default, SSL (Secure Sockets Layer) certificates are required for authentication. The product provides demo certificates generated with 1024 byte keys. For production environments, please use your own custom certificates.

Menu Option

Name Used in Documentation

Customer

Install

Value

Certificate Keystore Type

CERT_KS

Identify Keystore Type

CERT_IDENT_KS_FILE

Identify Keystore File Type

CERT_IDENT_KS_TYPE

Identify Keystore Password

CERT_IDENT_KS_PWD

Identity Private Key Alias

CERT_IDENT_KS_ALIAS

Trust Keystore File

CERT_TRUST_KS_FILE

Trust Keystore File Type

CERT_TRUST_KS_TYPE

Trust Keystore Password

CERT_TRUST_KS_PWD

Trust Private Key Alias

CERT_TRUST_KS_ALIAS

Menu Block 7 - OUAF TrustStore Options

The OUAF truststore configuration is required for IWS.

Menu Option

Name Used in Documentation

Customer

Install Value

Import TrustStore Directory

TS_IMPORT_KEYSTORE_FOLDER

Store Type

TS_STORETYPE

Alias

TS_ALIAS

Alias Key Algorithm

TS_ALIAS_KEYALG

Alias Key Size

TS_ALIAS_KEYSIZE

HMAC Alias

TS_HMAC_ALIAS

Padding

TS_PADDING

Mode

TS_MODE

Advanced Menu Options

The advanced menu options are not available during installation. These options can be accessed after installation using the following commands:

Unix:

$SPLEBASE/bin/configureEnv.sh -a

Windows

%SPLEBASE%\bin\configureEnv.cmd -a

Menu Block 50 - WebLogic Advanced Environment Miscellaneous Configuration

WebLogic advanced environment miscellaneous configurations include:

Menu Option

Name Used in Documentation

Customer

Value

Install

OUAF DBMS Scheduler User

OUAF_DBMS_SCHEDULER_USER

Online JVM Batch Server Enabled

BATCHENABLED

Online JVM Batch Server Enabled

BATCHENABLED

Online JVM Batch Number of Threads

BATCHTHREADS

Online JVM Batch Scheduler Daemon Enabled

BATCHDAEMON

Enable Batch Edit Funtionality

BATCHEDIT_ENABLED

Batch Online Log Directory

BATCH_ONLINE_LOG_DIR

Enable Web Services Functionality

WEBSERVICES_ENABLED

IWS deployment target

WLS_CLUSTER_NAME

Web Admin Server Host

WEB_ADMIN_SERVER

GIS Service Running on the same Web Server

GIS

GIS Service URL

GIS_URL

GIS WebLogic System User ID

GIS_WLSYSUSER

GIS WebLogic System Password

GIS_WLSYSPASS

Online Display Software Home

ONLINE_DISPLAY_HOME

Max Queries To Hold In Cache Across All Threads

XQUERIES_TO_CACHE

Seconds Timeout Flush Cache Completely

XQUERY_CACHE_FLUSH_TIMEOUT

Cloud Restriction URLs Enable

CLOUD_RESTRICTION_URLS_ENABLE

Cloud White List Full Path

CLOUD_WHITE_LIST_PATH

Cloud Custom White List Full Path

CLOUD_CUSTOM_WHITE_LIST_PATH

Menu Block 51 - WebLogic Advanced Environment Memory Configuration

WebLogic advanced environment memory configurations include:

Menu Option

Name Used in Documentation

Customer

Install

Value

Web Application Java Initial Heap Size

WEB_MEMORY_OPT_MIN

Web Application Java Max Heap Size

WEB_MEMORY_OPT_MAX

Web Application Java Max Perm Size

WEB_MEMORY_OPT_MAXPERMSIZE

Web Application Additional Options

WEB_ADDITIONAL_OPT

Global JVM Arguments

GLOBAL_JVMARGS

Ant Min Heap Size

ANT_OPT_MIN

Ant Max Heap Size

ANT_OPT_MAX

Ant Additional Options

ANT_ADDITIONAL_OPT

Thread Pool Worker Java Min Heap Size

BATCH_MEMORY_OPT_MIN

Thread Pool Worker Java Max Heap Size

BATCH_MEMORY_OPT_MAX

Thread Pool Worker Java Max Perm Size

BATCH_MEMORY_OPT_MAXPERMSIZE

Thread Pool Worker Additional Options

BATCH_MEMORY_ADDITIONAL_OPT

Additional Runtime Classpath

ADDITIONAL_RUNTIME_CLASSPATH

Menu Block 51 - Advanced Web Application Configuration

Advanced web application configurations include:

Menu Option

Name Used in Documentation

Customer

Install

Value

Web Application Cache Settings

WEB_L2_CACHE_MODE

Web Server Port Number

WEB_WLPORT

WebLogic Overload Protection

WLS_OVERRIDE_PROTECT

Domain Home Location

WLS_DOMAIN_HOME

Batch Cluster URL

WEB_BATCH_CLUSTER_URL

Strip HTML Comments

STRIP_HTML_COMMENTS

Authentication Login Page Type

WEB_WLAUTHMETHOD

Web Form Login Page

WEB_FORM_LOGIN_PAGE

Web Form Login Error Page

WEB_FORM_LOGIN_ERROR_PAGE

Application Viewer Form Login Page

WEB_APPVIEWER_FORM_LOGIN_PAGE

Application Viewer Form Login Error Page

WEB_APPVIEWER_FORM_LOGIN_ERROR_PAGE

Help Form Login Page

WEB_HELP_FORM_LOGIN_PAGE

Help Form Login Error Page

WEB_HELP_FORM_LOGIN_ERROR_PAGE

Web Security Role

WEB_SECURITY_NAME

Web Principal Name

WEB_PRINCIPAL_NAME

Application Viewer Security Role

WEB_APPVIEWER_ROLE_NAME

Application Viewer Principal Name

WEB_APPVIEWER_PRINCIPAL_

NAME

This is a development environment

WEB_ISDEVELOPMENT

Preload All Pages on Startup

WEB_PRELOADALL

Maximum Age of a Cache Entry for Text

WEB_MAXAGE

Maximum Age of a Cache Entry for Images

WEB_MAXAGEI

JSP Recompile Interval (s)

WEB_wlpageCheckSeconds

Menu Block 53 - Advanced Web Application Configuration

Advanced web application configurations include:

Menu Option

Name Used in Documentation

Customer

Install

Value

SPML SOAP Trace Setting

OIM_SPML_SOAP_D EBUG_SETTING

SPML IDM Schema Name

OIM_SPML_UBER_S CHEMA_NAME

SPML OIM Name Space

OIM_SPML_NAME_S PACE

SPML OIM Enclosing Element

OIM_SPML_SOAP_EL EMENT

Menu Block 54 - WebLogic Diagnostics

WebLogic diagnostic options include:

Menu Option

Name Used in Documentation

Customer

Install

Value

Diagnostic Context Enabled

WLS_DIAGNOSTIC_CONTEXT_ENABLED

Diagnostic Volume

WLS_DIAGNOSTIC_VOLUME

Built-in Module

WLS_DIAGNOSTIC_BUILT_IN_MODULE

Menu Block 53 - OIM Configuration Settings

OIM Configuration Settings include:

Menu Option

Name Used in Documentation

Customer

Install

Value

SPML SOAP Trace Setting

OIM_SPML_SOAP_DEBUG_SETTING

SPML IDM Schema Name

OIM_SPML_UBER_SCHEMA_NAME

SPML OIM Name Space

OIM_SPML_NAME_SPACE

SPML OIM Enclosing Element

OIM_SPML_SOAP_ELEMENT

Menu Block 55 - URI, File and URL Related Options

URI, File and URL Related Options include:

Menu Option

Name Used in Documentation

Customer

Install

Value

Restriction URLs Enable

CLOUD_RESTRICTION_URLS_ENABLE

Custom SQL Security

CUSTOM_SQL_SECURITY

White List Full Path

CLOUD_WHITE_LIST_PATH

Custom White List Full Path

CLOUD_CUSTOM_WHITE_LIST_PATH

Substitution Variable List File Location

CLOUD_SUBSTITUTION_VARIABLE_LIST_FILE_LOCATION

Directory For Variable F1_CMA_FILES

CLOUD_LOCATION_F1_MIGR_ASSISTANT_FILES

The following list identifies entries that are visible on the menu but will be deprecated in a future release so they should not be used:

Directory For Variable F1_BI_EXTRACTS

CLOUD_LOCATION_F1_BI_EXTRACT

Directory For Variable F1_INTERNAL_FILES

CLOUD_LOCATION_F1_PROD_INTER_FILES

Directory For Variable F1_CUST_APP_BASE

CLOUD_LOCATION_F1_CUST_APP_BASE

Directory For Variable F1_PROCESS_DIR

CLOUD_LOCATION_F1_PROCESS_DIR

Directory For Variable F1_SVC_CATALOG_WSDL_DIR

CLOUD_LOCATION_F1_SVC_CATALOG_WSDL_DIR

Directory For Variable F1_PDB_EXTRACTS

CLOUD_LOCATION_F1_PDB_EXTRACTS

Service and Measurement Data Foundation Installation and Configuration Worksheets

During the installation and configuration of the application you will need to provide a variety of system values. These worksheets will assist you in providing that information. They should be completed before installing the application framework. No Customer Install Value fields should be left blank.

Note: The OSB configuration and SOA configuration menus are optional for Oracle Utilities Meter Data Management and Oracle Utilities Customer To Meter and can be skipped. These configurations are required in case another product such as Oracle Utilities Smart Grid Gateway will also be installed on top of Oracle Utilities Service and Measurement Data Foundation.

WebLogic OSB Configuration

The WebLogic OSB configuration includes:

Menu Option

Name Used In Documentation

Customer Install Value

OSB Home

OSB_HOME

OSB Host Server

OSB_HOST

OSB Port Number:

OSB_PORT_NUMBER

OSB SSL Port Number

OSB_SSL_PORT

JDBC URL for database

DBURL_OSB

OSB Service Table Schema Name

RCUSTBSCHEMA_OSB

OSB Service Table Schema Password

RCUSTBSCHEMAPWD_OSB

OSB WebLogic User Name

WEBLOGIC_USERNAME_OSB

OSB WebLogic UserPassword

WEBLOGIC_PASSWORD_OSB

OSB WebLogic UserPassword

OSB_PASS_WLS

Mount point for OSB files

OSB_LOG_DIR

WebLogic SOA Configuration

The WebLogic SOA Configuration includes:

Menu Option

Name Used in this Documentation

Customer Install Value

SOA Home

SOA_HOME

SOA Host Server

SOA_HOST

SOA Port Number:

SOA_PORT_NUMBER

SOA SSL Port Number

SOA_SSL_PORT_NUMBER

SOA Internal URL

SOA_INTERNAL_URL

SOA External URL

SOA_EXTERNAL_URL

JDBC URL for database

DBURL_SOA

SOA Service table schema Name

RCUSTBSCHEMA_SOA

SOA Service table schema Password

RCUSTBSCHEMAPWD_SOA

SOA WebLogic User Name

WEBLOGIC_USERNAME_SOA

SOA WebLogic User Password

WEBLOGIC_PASSWORD_SOA

Specify the path for XAI/IWS Service

WEB_SERVICE_PATH

WebLogic SOA Configuration Plan

The WebLogic SOA Configuration Plan includes:

Menu Option

Name Used In Documentation

Customer Install Value

MDF Bulk Request Callback URL

D1_BULK_REQUEST_CALLBACK_URL

MDF Headend http connection timeout

D1_HEADEND_HTTP_CONN_TIMEOUT

MDF Headend http read timeout

D1_HEADEND_HTTP_READ_TIMEOUT

MDF SOA Request Queue JNDI Name

SOA_REQUEST_QUEUE_D1

MDF SOA Notify Queue JNDI Name

SOA_NOTIFY_QUEUE_D1

MDF SOA Commnad Queue JNDI Name

SOA_COMMAND_QUEUE_D1

SGG-NMS TestHarness Partition Name

SOA_PARTITION_D1

Configuration for DataRaker Integration

The Configuration for DataRaker Integration includes:

Menu Option

Name Used In Documentation

Customer Install Value

Destination Queue to publish SGG payloads for DataRaker Integration Tool

SGG_DR_INT_QUEUE

Number of records (SGG Payloads) to accumulate

SOA_DR_PUBLISH_SIZE

Max file size for the accumulated (SGG Payloads) file in Kilobytes

SOA_DR_FILE_SIZE

Specify a time which, when exceeded, causes a new outgoing file to be created in seconds

SOA_DR_ELAPSED_TIME

Polling frquency of Staging directory for new files in seconds

SOA_DR_POLLING_FREQ

Mount point/directory for the accumulated SGG payload file

SOA_DR_STAGING_DIR

Mount Point/directory for the converted XML file to place for DataRaker

SOA_DR_INTEGRATION_DIR

Advanced Menu Options

The advanced menu options are not available during installation. These options can be accessed after installation using the following commands:

Unix

$SPLEBASE/bin/configureEnv.sh -a

Windows

%SPLEBASE%\bin\configureEnv.cmd -a

Advanced Menu Option for OSB SSL Deployment

The Advanced Menu Option for OSB SSL deployment includes:

Menu Option

Name Used In Documentation

Customer Install Value

Enable OSB SSL Port

OSB_SSL

OSB Trust Keystore Type

OSB_TRUST_KS

OSB Trust Keystore File Type

OSB_TRUST_KS_TYPE

OSB Trust Keystore File

OSB_TRUST_KS_FILE

Advanced Environment Memory Configurations

The Advanced Environment Memory configurations include:

Menu Option

Name Used In Documentation

Customer Install Value

SOA Initial Heap Size

SOA_MEMORY_OPT_MIN

SOA Maximum Heap Size

SOA_MEMORY_OPT_MAX

SOA Minimum Perm Size

SOA_MEMORY_OPT_MINPERMSIZE

SOA Maximum Perm Size

SOA_JVM_ADDITIONAL_OPT

The name of the OWSM policy to use when SOA calls another SOA service

SOA_SOA_CLIENT_POLICY

The name of the OWSM policy to use when SOA is called by another SOA service

SOA_SOA_SERVICE_POLICY

The name of the OWSM policy to use when SOA calls an OUAF service

SOA_SOA_SERVICE_POLICY

The Advanced Memory Configurations for OSB includes:

Menu Option

Name Used In Documentation

Customer Install Value

OSB Initial Heap Size

OSB_MEMORY_OPT_MIN

OSB Maximum Heap Size

OSB_MEMORY_OPT_MAX

OSB Minimum Perm Size

OSB_MEMORY_OPT_MINPERMSIZE

OSB Maximum Perm Size

OSB_MEMORY_OPT_MAXPERMSIZE

OSB Application Additional Options

OSB_JVM_ADDITIONAL_OPT

The Data Migration options include:

Menu Option

Name Used In Documentation

Customer Install Value

Enable Data Migration

DATA_MIGRATION

Data Migration Database User

DATA_MIGRATION_DB_USER

Data Migration Database Password

DATA_MIGRATION_DB_PASS

The Advanced Configurations for SOA include:

Menu Option

Name Used In Documentation

Customer Install Value

Enable SOA SSL Port

SOA_SSL

SOA Trust Keystore Type

SOA_TRUST_KS

SOA Trust Keystore File Type

SOA_TRUST_KS_TYPE

SOA Trust Keystore File

SOA_TRUST_KS_FILE

Common Maintenance Activities

This appendix lists frequently-used commands that you use to perform common maintenance activities, such as starting and stopping the environment and thread pool worker, modifying the configuration items.

Run the following commands to perform these common tasks:

To Initialize the Environment

1.

Go the directory <install_dir>/bin.

2.

Run the following command:

UNIX

./splenviron.sh -e <Env_Name>

Windows

splenviron.cmd -e <Env_Name>

To Start the WebLogic Server

1.

Initialize the environment.

2.

Run the following command:

UNIX

./spl.sh start

Windows

spl.cmd start

To Stop the WebLogic Server

1.

Initialize the environment.

2.

Run the following command:

UNIX

./spl.sh stop

Windows

spl.cmd stop

To Start the Thread Pool Worker

1.

Initialize the environment.

2.

Run the following command:

UNIX

./spl.sh -b start

Windows

spl.cmd -b start

To Stop the Thread Pool Worker

1.

Initialize the environment.

2.

Run the following command:

UNIX

./spl.sh -b stop

Windows

spl.cmd -b stop

To Modify the Configuration Values

1.

Initialize the environment.

2.

Run the following command:

UNIX

configureEnv.sh

Windows

configureEnv.cmd

The configuration utility launches menu items. Select any Menu option.

3.

Change the menu values.

4.

After you change the menu values, press P to write the changes to the configuration file.

5.

To apply the changes to the environment, run the initial setup script:

initialSetup.sh

To Modify the Advanced Menu Option Values

1.

Initialize the environment.

The configuration utility launches menu items.

2.

Run the following command:

UNIX

configureEnv.sh -a

Windows

configureEnv.cmd -a

3.

Select any menu option.

4.

Change the menu values.

5.

To apply the changes to the environment, run initial setup script:

initialSetup.sh

Installing User Documentation as a Standalone Application

Installing User Documentation

This section provides instructions for installing the Oracle Utilities Meter Data Management user documentation that is supplied with the system. The Oracle Utilities Meter Data Management user documentation is provided in PDF format for printing.

The documentation is also provided in HTML format located inside the Oracle Utilities Meter Data Management application server installation package. It is automatically installed and can be launched from the user interface. The files are under the applications directory packaged in the file named help.war. User documentation is provided in English (ENG).

The documentation material is divided into the following subdirectories underneath the language directory:

•

D1: Oracle Utilities Service and Measurement Data Foundation User Guide

•

D2: Oracle Utilities Meter Data Management User Guide

•

F1: Oracle Utilities Application Framework Administration and Business Process Guides

Installing Stand-Alone Online Help

You can also use the Oracle Utilities Meter Data Management online help in stand-alone mode (that is, you do not have to launch it from the Oracle Utilities Meter Data Management application or access it on the application server).

To install the Oracle Utilities Meter Data Management help for stand-alone operation, copy the help.war from the Oracle Utilities Meter Data Management server (environment) or from the Oracle Utilities Meter Data Management installation package to the server or machine on which you want to access the help. If you want to copy the file from any installed Oracle Utilities Meter Data Management environment, you can locate the file in the $SPLEBASE/splapp/applications directory on the server.

Unzip the help.war file to any directory on your machine. To launch the Oracle Utilities Meter Data Management help in stand-alone mode, open the SPLHelp.html file (located inside the language directory that you wish to use).

Note: Do not change the subdirectory names. The documents use relative path names to link to other documents. Changing the subdirectory names will result in broken links.

Customizing Help for Stand-Alone Operation

You can customize the SPLHelp.html file to open to the file and topic that you most frequently use. To do so, edit the SPLHelp.html file and change the DEFAULT_BOOKMARK to the desired location. The default DEFAULT_BOOKMARK is 'helpHome.html'.

Installing Stand-Alone Help Under Web Server

You can also install Oracle Utilities Meter Data Management online help as a stand-alone web application. You can use any Web Application server like WebLogic. Configure the configuration file for your web application server to use web application help.

For example:

For WebLogic, configure config.xml file for deployed application Name="help" with URI="help.war" and set WebServer DefaultWebApp="help"

Access the documentation from the browser by the following URL:

http://<host name>:<port name>/<WebContext>/<Lang>/SPLHelp.html, where

<hostname>:<portname> is the URL of the web server, <Web Context> is the root web context name specified during Web application server configuration, <Lang> is the name of the language directory, for example, ENG.

Note: Stand-alone online help files are not automatically updated when changes are made to the help files on the application server. You will have to re-install the stand-alone online help files.

Oracle Utilities Application Framework 4.3.0 Service Pack 4 (4.3.0.4.0) Fixes

The following table lists the Oracle Utilities Application Framework 4.3.0 Service Pack 4 (4.3.0.4.0) fixes included in this release.

Fix

Description

23128950

RESTRICTING URIS FOR THE CLOUD IS ACCEPTING ONLY TWO PROTOCOLS (HTTP & HTTPS)

24589020

COPY OF BUG 24583489 - GENAPPVIEWERITEMS FAILS IN WINDOWS IF ONLY ONLINE ROLE IS

25119728

ABILITY TO ADD SOAP HEADER PARAMETERS TO OUTBOUND MESSAGE

25300770

PROGRAM TO LIST CLASSES ALLOWABLE IN SOURCE FOR JAVADOCS

25343308

SUPPORT FOR HTTP REST CALL WITH JSON PAYLOAD&TRANSFORMATION FOR GIS INTEGRATION

25458441

INFO STRING WITH SPACE AND HYPHEN IN MONEY AND DATES WRAPS IN SERVICE ZONES

25459906

COPY OF 24495181 - COPY OF 24487407 - COPY OF 23742898 - COPY OF 22544303 - ISSU

25468195

INFO STRING HAVING DATE IN DESCRIPTION GETS WRAPPED IN BO SEARCH RESULTS

25471512

ISSUE FOUND WHEN CHECKBOX ELEMENT IS WITHIN A LIST

25478719

ADA: OUTSTANDING CCB KEYBOARD ISSUES 2.1.1, 2.4.3 AND 3.2.3

25479526

COPY OF 25210796 - SLA: PERFORMANCE TARGET ZONE NOT DISPLAYING TIME TARGET CORRE

25498483

USING F1-GETDBMSJOBS WITH JOBSTATUS SET TO COMP RETURNS A NULL AND OTHER ISSUES

25506815

COPY OF 25485728 - COPY OF 25164929 - COPY OF 24965749 - SEARCH BY IS RESET AFTER

25509633

CMA - NPE APPLYING FIELD ACTIVITY MIGRATION OBJECT IN CCB

25513156

00239 - PLUG-IN DRIVEN BATCH DOES NOT SUPPORT ADDING ADDITIONAL SORT KEYS

25592230

COPY OF 25545108 - COPY OF 25419076 - OUTBOUND MESSAGE HAS THE MRID FIELD MISSIN

25610076

SUCCEEDING WARNINGS NO LONGER DISPLAYED AFTER ACCEPTING WARNING

25616513

MISSING INDEXES FOUND IN DB HEALTHCHECK ON INITIAL INSTALL

25616857

COPY OF 25201396 - WAM V2: ENHANCE OUTBOUND MESSAGE JSON SENDER TO SUPPORT DYNAM

25636490

COPY OF 24473095 - TEMPLATE PROPERTIES MISSING FORCE_FORWARD_SLASH

25636518

COPY OF 24749849 - CLD: BATCH ON WLS IS NOT ABLE TO START AFTER SECURITY HARDENI

25642648

TPW NOT WORKING IN WEBLOGIC DOMAIN FW 4.3.0.4.0

25645976

00239 - PLUG-IN DRIVEN BATCH RESULTS TO NPE ERROR WHEN VALIDATING TO DO TYPE

25704043

ONLY SHOW BATCH, ALGORITHM, ETC. SOURCE IN JAVADOCS

25712815

ADD SUPPORT FOR OWSM TO HTTP AND SOAP REALTIME SENDERS

25714240

MAKE REST SECURITY FILTER OPTIONAL FOR OWSM

25720956

COPY OF 25697855 - OUTBOUND WSDL AND IWS FROM WEB CATALOG HAS MISSING RESPONSE M

25754126

PHONE FORMAT ISSUE

25762422

NEW ISSUE BEING INTRODUCED BY FW BUG 25468195

25808038

CALENDAR POPUP THROWS JAVASCRIPT ERRORS IF YOU TRY TO USE ANY OF THE WIDGETS

25831771

HTTP HEADERS WRAPPED IN [ ]

Preface

This guide provides an overview of installing Oracle Utilities Meter Data Management and is intended for anyone interested in the installation process. This section includes:

•

Related Documents

•

Updates to Documentation

•

Acronyms

•

Additional Resources

To complete installation you should have:

•

Administrative privileges on the host where you are installing the software.

•

Experience installing and configuring application servers and other software.

Related Documents

The following documentation is included with this release.

Installation, Configuration, and Release Notes

•

Oracle Utilities Meter Data Management Release Notes

•

Oracle Utilities Meter Data Management Quick Install Guide

•

Oracle Utilities Meter Data Management Installation Guide

•

Oracle Utilities Meter Data Management Database Administrator Guide

•

Oracle Utilities Meter Data Management Licensing Information User Manual

User Guides

•

Oracle Utilities Meter Data Management Business User Guide

•

Oracle Utilities Meter Data Management Administrative User Guide

Supplemental Documents

•

Oracle Utilities Meter Data Management Security Guide

•

Oracle Utilities Meter Data Management Server Administration Guide

Updates to Documentation

Additional and updated information about the product is available from the Knowledge Base section of My Oracle Support (http://support.oracle.com). Please refer to My Oracle Support for more information. Documentation updates are also posted on the Oracle Technology Network documentation page as they become available (http://docs.oracle.com/cd/E72219_01/documentation.html).

Conventions

The following text conventions are used in this document:

Convention

Meaning

boldface

Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.

italic

Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.

monospace

Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

Acronyms

The following acronyms and terms are used in this document:

Acronym

Definition

ADF

Oracle Application Development Framework

EAR

Enterprise Archive

EJB

Enterprise JavaBeans

HTML

HyperText Markup Language

JAR

Java Archive

JDBC

Java database connectivity

JMX

Java Management Extensions

JNDI

Java Naming and Directory Interface

JSP

JavaServer Pages

JVM

Java Virtual Machine.

MPL

Multi Purpose Listener

OUAF

Oracle Utilities Application Framework

OAM

Oracle Access Manager

OIM

Oracle Identity Management

ONS

Oracle Notification Service

Oracle RAC FCF

Oracle Real Application Clusters Fast Connection Failover

RMI

Remote Method Invocation

SOAP

Simple Object Access Protocol

SOA

Service-oriented architecture

SPLEBASE

The location where the application will be installed.

SPLOUTPUT

This location is used for storing batch log files and output from batch jobs

WAR

Web application Archive

WLS

WebLogic

XAIApp

XML Application Integration

Additional Resources

For more information and support, visit the Oracle Support Web site at: http://www.oracle.com/support/index.html