Oracle Utilities Work and Asset

Management

Installation Guide

Release 2.1.1

E69057-02

December 2015

(Updated February 2016)

Oracle Utilities Work and Asset Management Installation Guide, Release 2.1.1

Copyright © 2000, 2015 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.

Contents

Preface................................................................................................................................................................................. i-i

Related Documents . . . . ..................................................................................................................................................................... i-i

Conventions.. . . . . . . . . . ............................................................................................... . . . . . . ......................................................... i-i

Acronyms. . . . . . . . . . . . ..................................................................................................................................................................... i-ii

Chapter 1

Overview ............................................................................................................................................................................ 1-1

Product Overview. . . . . .................................................................................................................................................................... 1-2

Installation Overview. . ...................................................................................................... . . . ....................................................... 1-3

Installation Types. . . . . . ................................................................................................. . . . . . ....................................................... 1-4

Initial Installation. . . . . . . . . . . ......................................................................................................................................... 1-4

Demo Installation.. ............................................................................................................................. . ............................ 1-4

Package Contents............................................................................................................... . . . . ....................................................... 1-4

Documentation. . . . . . . . . . . . . ........................................................................................................................................ 1-5

Installation Packages. . . . . . . . .......................................................................................... . . . . . . . . . ............................ 1-5

Readiness Checklist . . . . ................................................................................................................................................................... 1-6

Chapter 2

Supported Platforms and Hardware Requirements .......................................................................................................... 2-1

Operating Systems and Application Servers.................................................................................................................................. 2-2

Hardware Requirements ................................................................................................................................................................... 2-2

Application Server Memory Requirements . . . . . . . . . . . ............................................................................................................. 2-3

Additional Notes on Supported Platforms.................................................................................................................................... 2-3

Support for Software Patches and Upgrades ................................................................................................................................ 2-4

Chapter 3

Planning the Installation ................................................................................................................................................... 3-1

Before You Install . . . . . ................................................................................................... . . . . ....................................................... 3-2

Prerequisite Software List. . . . . . . . . . . . ............................................................................. . . ....................................................... 3-2

Prerequisite Software for Application Server ............................................................................................................... 3-2

Web Browser Requirements. . ................................................................................................... . . . . ............................ 3-2

Installing PreRequisite Software...................................................................................................................................................... 3-2

AIX 7.1 TL01 Application Server . . . . . . . . . . .............................................................................................................. 3-2

Oracle Linux 6.x or 7.x or Red Hat Linux 6.x or 7.x Application Server.............................................. 3-5

Oracle Solaris 11 Application Server....................................................................................................... 3-8

Windows Server 2012 Application Server ............................................................................................. 3-10

Chapter 4

Installing Oracle Utilities Work and Asset Management - Initial Installation................................................................. 4-1

Before You Install . . . . . ................................................................................................... . . . . ....................................................... 4-2

Contents - i

Oracle Utilities Work and Asset Management Installation Guide

Contents

Initial Installation Procedure. . . . . . . . . . ........................................................................................................................................ 4-2

Database Component Installation .................................................................................................................................. 4-2

Application Components Installation ............................................................................................................................ 4-2

After the Installation ......................................................................................................... ............................................................... 4-9

Operating the Application...................................................................................................... ......................................................... 4-9

Chapter 5

Installing Oracle Utilities Work and Asset Management - Demo Installation................................................................. 5-1

Before You Install ............................................................................................................. ............................................................... 5-2

Demo Installation Procedure........................................................................................................................................................... 5-2

Database Component Installation .................................................................................................................................. 5-2

Application Components Installation ............................................................................................................................ 5-2

After the Installation ......................................................................................................... ............................................................... 5-9

Operating the Application...................................................................................................... ......................................................... 5-9

Chapter 6

Additional Tasks ................................................................................................................................................................ 6-1

WebLogic Production Server Considerations...................................................................................... ........................................ 6-2

Configuring Identity and Trust ....................................................................................................................................... 6-2

Building Javadoc Indexes ....................................................................................................... ......................................................... 6-2

Configuring the Environment for Batch Processing ................................................................................................................... 6-3

Customizing the Logo........................................................................................................... ........................................................... 6-3

Deploying Inbound WebServices (IWS)........................................................................................................................................ 6-3

Installing Service Packs and Patches............................................................................................................................................... 6-4

Chapter 7

Installing Optional Products ............................................................................................................................................. 7-1

Oracle BI Publisher........................................................................................................................................................................... 7-1

Supported BI Publisher Versions ................................................................................................................................... 7-1

About Oracle BI Publisher Enterprise ........................................................................................... .............................. 7-1

Configuring the System to Enable Reports................................................................................................................... 7-2

Sample Reports Supplied with the Product .................................................................................................................. 7-3

Appendix A

Installation Menu Functionality Overview....................................................................................................................... A-1

Installation Menu Functionality Details........................................................................................ ............................... A-1

Appendix B

Installation and Configuration Worksheets...................................................................................................................... B-1

Application Framework Installation and Configuration Worksheets....................................................................................... B-1

Environment ID, Roles, Third Party Software Configuration.................................................................................. B-1

Keystore Options ............................................................................................................... ............................................. B-3

Environment Installation Options ................................................................................................................................ B-4

Environment Description............................................................................................................................................... B-6

WebLogic Business Application Server Configuration .............................................................................................. B-7

WebLogic Web Application Server Configuration . . . . . . . . . . ................................................................................. B-8

Database Configuration ................................................................................................................................................ B-10

General Configuration Options. . . . . . . . . . . . ........................................................................................................... B-13

SSL Certificate Keystore (Weblogic Only)....................................................................................... ......................... B-14

Advanced Menu Options.......................................................................................................... ................................... B-16

Contents - ii

Oracle Utilities Work and Asset Management Installation Guide

Contents

Advanced Environment Memory Configuration...................................................................................................... B-19

Advanced Web Application Configuration. . . .......................................................................................................... B-21

OIM Configuration Settings..................................................................................................... . . . . . ......................... B-24

Appendix C

Application Framework Prerequisite Patches .................................................................................................................. C-1

Appendix D

Common Maintenance Activities .................................................................................................................................... D-1

Contents - iii

Oracle Utilities Work and Asset Management Installation Guide

Preface

This guide describes how to install Oracle Utilities Work and Asset Management v2.1.1 and is

intended for anyone interested in the process of installing Oracle Utilities Work and Asset

Management.

To use this document you should have:

•

Administrative privileges on the host where you are installing the software

•

Experience installing and configuring application servers and other software (preferable)

Related Documents

For more information, refer to the following documents for this release:

Installation Guides

•

Oracle Utilities Work and Asset Management Release Notes

•

Oracle Utilities Work and Asset Management Quick Install Guide

•

Oracle Utilities Work and Asset Management Installation Guide

•

Oracle Utilities Work and Asset Management DBA Guide

•

Oracle Utilities Work and Asset Management License Information User Guide

User Guides

•

Oracle Utilities Work and Asset Management and Oracle Utilities Operational Device

Management Business User’s Guide

•

Oracle Utilities Work and Asset Management and Oracle Utilities Operational Device

Management Administrative Guide

Supplemental Documents

•

Oracle Utilities Work and Asset Management Server Administration Guide

•

Oracle Utilities Work and Asset Management Security Guide

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.

Preface - i

Oracle Utilities Work and Asset Management Installation Guide

Preface

Convention

Meaning

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 are used in this document:

•

WAM – Work and Asset Management (also known as Oracle Utilities Work and Asset

Management)

•

OUAF – Oracle Utilities Application Framework

Preface - ii

Oracle Utilities Work and Asset Management Installation Guide

Chapter 1

Overview

This chapter provides an overview of the Oracle Utilities Work and Asset Management (WAM)

product and installation process.

This section includes the following:

•

Product Overview

•

Installation Overview

•

Installation Types

•

Package Contents

•

Readiness Checklist

Overview 1-1

Oracle Utilities Work and Asset Management Installation Guide

Product Overview

Product Overview

Oracle Utilities Work and Asset Management is housed in the Oracle WebLogic J2EE Web

Application Server. The system is comprised of two layers: web and service. The application is

accessed by using a browser to connect to the web layer.

Oracle Utilities Work and Asset Management data is stored in the Oracle Database. For processing

large amounts of data, the system provides a thread pool worker (batch server) which interacts

with the same database.

The following figure provides an overview of the Oracle Utilities Work and Asset Management

product:

Refer to the Business User’s Guide for information about the features and functionality in this release.

Overview 1-2

Oracle Utilities Work and Asset Management Installation Guide

Installation Overview

Installation Overview

Oracle Utilities Work and Asset Management consists of several components, all of which need to

be installed for a successful installation. Certain prerequisite software may need to be installed

before installing each of these components.

The following figure details the workflow for the initial and demo installation process.

Refer to the Installation Types section for the list of components comprising the product.

Refer to the Prerequisite Software List for the list of prerequisite software.

Overview 1-3

Oracle Utilities Work and Asset Management Installation Guide

Package Contents

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 or Installing Oracle Utilities Work and Asset Management from scratch - 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

The following sections describe these installation types in detail.

Initial Installation

This installation type is applicable when installing Oracle Utilities Work and Asset Management

for the first time or from scratch. Each of the following components should be installed during an

initial installation:

•

Database components:

Refer to the “Initial Install” section of the Oracle Utilities Work and Asset Management Database

Administrator’s Guide for more information.

•

Application components:

•

Oracle Utilities Application Framework application

•

Oracle Utilities Application Framework single fix pre-requisite rollup

•

Oracle Utilities Work and Asset Management application

For detailed steps on installing each of the above components, refer to the chapter Installing

Oracle Utilities Work and Asset Management - Initial Installation.

Demo Installation

This installation type is applicable when installing a demo application of Oracle Utilities Work and

Asset 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 Work and Asset Management Database

Administrator’s Guide for more information.

•

Application components:

•

Oracle Utilities Application Framework application

•

Oracle Utilities Application Framework single fix pre-requisite rollup

•

Oracle Utilities Work and Asset Management application

Refer to chapter Installing Oracle Utilities Work and Asset Management - Demo Installation for

the steps involved in installing each of the above components.

Package Contents

The following documentation and installation packages are part of the product package.

This section includes information about:

•

Documentation

•

Installation Packages

Overview 1-4

Oracle Utilities Work and Asset Management Installation Guide

Package Contents

Documentation

Installation Guides

•

Oracle Utilities Work and Asset Management Release Notes

•

Oracle Utilities Work and Asset Management Quick Install Guide

•

Oracle Utilities Work and Asset Management Installation Guide

•

Oracle Utilities Work and Asset Management DBA Guide

•

Oracle Utilities Work and Asset Management License Information User Guide

User Guides

•

Oracle Utilities Work and Asset Management and Oracle Utilities Operational Device

Management Business User’s Guide

•

Oracle Utilities Work and Asset Management and Oracle Utilities Operational Device

Management Administrative Guide

Supplemental Documents

•

Oracle Utilities Work and Asset Management Server Administration Guide

•

Oracle Utilities Work and Asset Management Security Guide

Installation Packages

•

Oracle Utilities Work and Asset Management v2.1.1.0.0 Release Notes.zip

•

Oracle Utilities Work and Asset Management v2.1.1.0.0 Install Documentation.zip

•

Oracle Utilities Work and Asset Management v2.1.1.0.0 Quick Install Guide.zip

•

Oracle Utilities Work and Asset Management v2.1.1.0.0 User Documentation.zip

•

Oracle Utilities Work and Asset Management v2.1.1.0.0 Supplemental

Documentation.zip

•

Oracle Utilities Work and Asset Management v2.1.1.0.0 Multiplatform.zip

•

Oracle Utilities Work and Asset Management v2.1.1.0.0 Oracle Database

Multiplatform.zip

•

Oracle Utilities Application Framework v4.3.0.1.0 Multiplatform.zip

•

Oracle Utilities Application Framework v4.3.0.1.0 Single Fix Prerequisite Rollup for

Oracle Utilities Work and Asset Management v2.1.1.0.0.zip

•

Oracle Utilities Work and Asset Management v2.1.1.0.0 Reports.zip

Overview 1-5

Oracle Utilities Work and Asset Management Installation Guide

Readiness Checklist

Readiness Checklist

The following checklist will guide you through the installation process of Oracle Utilities Work

and Asset 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 chapter Planning the Installation for more details.

3. Ensure that you have downloaded the Oracle Utilities Work and Asset Management v2.1.1

components from Oracle Software Delivery Cloud.

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 Installing

Oracle Utilities Work and Asset Management - Initial Installation

•

Demo Installation - For demo installation follow the instructions mentioned in

Installing Oracle Utilities Work and Asset Management - Demo Installation

6. Perform post-installation tasks.

7. Install optional products as described in chapter Installing Optional Products.

Overview 1-6

Oracle Utilities Work and Asset Management Installation Guide

Chapter 2

Supported Platforms and Hardware

Requirements

This installation is certified to operate on many operating system, application server and database

server combinations. The following sections provide information on the supported platforms and

requirements, including information on:

•

Operating Systems and Application Servers

•

Hardware Requirements

•

Application Server Memory Requirements

•

Additional Notes on Supported Platforms

•

Support for Software Patches and Upgrades

Supported Platforms and Hardware Requirements 2-1

Oracle Utilities Work and Asset Management Installation Guide

Hardware Requirements

Operating Systems and Application Servers

The following table details the operating system and application server combinations on which

this version of Oracle Utilities Work and Asset Management is supported.

Operating

Operating

System and Web

Application 

System

Chipset

Database

Browser

Server

(Server)

(Client)

AIX 7.1

Power 

WebLogic

Oracle

TL1

64-bit

12.1.3.0+*

Database

WebSphere

12.1.0.1+

(Basic)/

WebSphere

(ND) 8.5.5

Oracle Enterprise Linux x86_64

WebLogic

Oracle

Windows 7, 8.1

6.x or 7.x

12.1.3.0+*

Database

(Internet Explorer 

(64-bit)

12.1.0.1+

11, Firefox ESR 38)

Red Hat Enterprise

Linux 6.x or 7.x

(64-bit)

Oracle Solaris 11 

SPARC 

WebLogic

Oracle

(64-bit)

64-bit

12.1.3.0+*

Database

12.1.0.1+

Windows Server 2012

x86_64

WebLogic

Oracle

R2

12.1.3.0+*

Database

(64-bit)

12.1.0.1+

* A plus sign (+) after the fourth digit in the version number indicates that this and all

higher versions of WebLogic are supported. For example, 12.1.3.0+ means that

12.1.3.0 and any higher 12.1.3.x.x versions are supported.

** Oracle Utilities Work and Asset Management is tested and supported on the versions

of Oracle Linux specified. Because Oracle Linux is 100% userspace-compatible with

Red Hat Enterprise Linux, Oracle Utilities Work and Asset Management also is sup-

ported on Red Hat Enterprise Linux for this release.

•

The platforms listed above are current at the time of release. For the most current supported

platforms, please refer to Oracle Utilities Product Matrix on My Oracle Support (MOS)

Knowledge Article (Doc ID 1454143.1).

Hardware Requirements

Client Side Hardware Requirements

Configuration

Processor

Memory (RAM)

Monitor (Display)

Minimum

1 GHz or faster 64-bit

2 GB

1280x1024

(x64) processor

Recommended*

3 GHz or faster 64-bit

4 GB

1280X1024

(x64) processor

Supported Platforms and Hardware Requirements 2-2

Oracle Utilities Work and Asset Management Installation Guide

Additional Notes on Supported Platforms

* The Recommended configuration supports better performance of the client.

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.

Disk Space Requirements

The approximate disk space requirements in a standard installation are as follows:

Location

Size

Usage

Install_dir Location

10 GB

This location is where the application and

minimum

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.

Log Location

5 GB

This location is used for storing batch log

minimum

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

5 GB

This location is used by various web server

web work files on the web

minimum

vendors to expand the application. It should

servers

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

uncompress the files and install the

application.

Oracle data area

4 GB

This location is where the Oracle database

minimum

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.

Additional Notes on Supported Platforms

Oracle Database Server

This version of Oracle Utilities Work and Asset Management is certified on Oracle Database

Server 12.1.0.1+ on the operating systems listed in the section above. The following versions of

the database are supported:

•

Oracle Database Enterprise Edition

•

Oracle Database Standard Edition

Supported Platforms and Hardware Requirements 2-3

Oracle Utilities Work and Asset Management Installation Guide

Support for Software Patches and Upgrades

Oracle VM Support

This version of Oracle Utilities Work and Asset Management is supported on Oracle VM 3.2.0

and 3.3.1 for supported releases of Oracle Linux and Microsoft Windows operating systems.

Oracle Support Policy on VMWare

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

VMWare.

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 from this rule 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.

Supported Platforms and Hardware Requirements 2-4

Oracle Utilities Work and Asset Management Installation Guide

Chapter 3

Planning the Installation

This chapter provides information for planning an Oracle Utilities Work and Asset Management

installation, including:

•

Prerequisite Software List

•

Installing PreRequisite Software

Planning the Installation 3-1

Oracle Utilities Work and Asset Management Installation Guide

Installing PreRequisite Software

Before You Install

Refer to My Oracle Support for up-to-date additional information about installing Oracle Utilities

Work and Asset Management.

Prerequisite Software List

Before you install Oracle Utilities Work and Asset Management, you must install prerequisite

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

downloading and installing.

This section includes information on the following:

•

Prerequisite Software for Application Server

•

Web Browser Requirements

Prerequisite Software for Application Server

The prerequisite software for the application component of Oracle Utilities Work and Asset

Management is as follows:

•

Oracle Database 12c Release 1 Client

•

Java 8 Update 51+ (64-bit)

•

Oracle Web Logic 12c (12.1.3.0+)

•

Hibernate 4.1.0 FINAL

Web Browser Requirements

The following operating system / web browser software are supported:

•

Windows 7, 8.1 with Internet Explorer 11, Firefox ESR 38

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 Application Server

•

Oracle Linux 6.x or 7.x or Red Hat Linux 6.x or 7.x Application Server

•

Oracle Solaris 11 Application Server

•

Windows Server 2012 Application Server

AIX 7.1 TL01 Application Server

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

application server.

Planning the Installation 3-2

Oracle Utilities Work and Asset Management Installation Guide

Installing PreRequisite Software

Supported Application Servers

Operating System

Chipset

Application Server

AIX 7.1 (64-bit) TL01

POWER 64-bit

Oracle WebLogic 12.1.3.0+ (64-bit) version

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

Customer Defined

Description

Default Value

Value

Oracle Utilities Work and Asset Management

cissys

Administrator User ID

Oracle Utilities Work and Asset Management User

cisusr

Group

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. Primary group cisusr. Set the primary shell for the cissys user to

Korn Shell.

3. Set the desired hard/soft limit of the file handler to 4096 or higher.

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.

Planning the Installation 3-3

Oracle Utilities Work and Asset Management Installation Guide

Installing PreRequisite Software

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 12.1.0.1 Client

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 7.0 SR64 64-bit

Installation of Java is a prerequisite for using Oracle WebLogic as a web 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 Work and Asset Management.

To install Hibernate:

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/

Click the “4.1.0.Final” link to download the zip file.

3. 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.

Planning the Installation 3-4

Oracle Utilities Work and Asset Management Installation Guide

Installing PreRequisite Software

4. 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-logging-3.1.0.CR2.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

Oracle WebLogic Server 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 12.1.3.0+.

Oracle Linux 6.x or 7.x or Red Hat Linux 6.x or 7.x Application Server

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 Linux 6.x or 7.x 

x86_64

Oracle WebLogic 12.1.3.0+ 

(64-bit)

(64-bit) version

Red Hat Enterprise Linux 6.x or 7.x (64-bit)

Oracle Linux 6.x or 7.x or Red Hat Enterprise Linux 6.x or 7.x 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:

Customer Defined

Description

Default Value

Value

Oracle Utilities Work and Asset Management

cissys

Administrator User ID

Oracle Utilities Work and Asset Management User

cisusr

Group

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

reasons.

Planning the Installation 3-5

Oracle Utilities Work and Asset Management Installation Guide

Installing PreRequisite Software

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.

3. Set the desired hard/soft limit of the file handler to 4096 or higher.

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 Database 12.1.0.1+

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.

Planning the Installation 3-6

Oracle Utilities Work and Asset Management Installation Guide

Installing PreRequisite Software

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 Update 51+, 64-bit

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

https://support.oracle.com

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.

Hibernate 4.1.0 FINAL

You must install Hibernate before installing Oracle Utilities Work and Asset Management.

To install Hibernate:

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/

Click the “4.1.0.Final” link to download the zip file.

3. 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.

4. 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-logging-3.1.0.CR2.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

Oracle WebLogic 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 12.1.3.0+.

Planning the Installation 3-7

Oracle Utilities Work and Asset Management Installation Guide

Installing PreRequisite Software

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 12.1.3.0+ (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:

Customer Defined

Description

Default Value

Value

Oracle Utilities Work and Asset Management

cissys

Administrator User ID

Oracle Utilities Work and Asset Management User

cisusr

Group

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.

3. Set the desired hard/soft limit of the file handler to 4096 or higher.

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.

Planning the Installation 3-8

Oracle Utilities Work and Asset Management Installation Guide

Installing PreRequisite Software

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 Database 12.1.0.1+ Client

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 Update 51+, 64-bit

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:

https://support.oracle.com

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.

Hibernate 4.1.0 FINAL

You must install Hibernate before installing Oracle Utilities Work and Asset Management.

To install Hibernate:

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/

Click the “4.1.0.Final” link to download the zip file.

3. Extract the contents of the archive file:

jar xvf hibernate-release-4.1.0.Final.zip

Planning the Installation 3-9

Oracle Utilities Work and Asset Management Installation Guide

Installing PreRequisite Software

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.

4. 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-logging-3.1.0.CR2.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

Oracle WebLogic 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 12.1.3.0+.

Windows Server 2012 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

x86_64

Oracle WebLogic 12.1.3.0+

(64-bit)

Oracle Database 12.1.0.1+ Client

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 Update 51+, 64-bit

This software is required for the Oracle WebLogic Installation. At time of release, Oracle Java

packages could be obtained from:

https://support.oracle.com

The Oracle WebLogic Server requires the 64-bit version. The main prerequisite for the web server

is the version of Java mentioned above.

Planning the Installation 3-10

Oracle Utilities Work and Asset Management Installation Guide

Installing PreRequisite Software

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.

Hibernate 4.1.0 FINAL

You must install Hibernate before installing Oracle Utilities Work and Asset Management.

To install Hibernate:

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/

Click the “4.1.0.Final” link to download the zip file.

3. 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.

4. Copy the jar files to your Hibernate jar directory ($HIBERNATE_JAR_DIR) using the

following commands:

copy hibernate-release-4.1.0.Final/lib/optional/

ehcache/ehcache-core-2.4.3.jar $HIBERNATE_JAR_DIR

copy hibernate-release-4.1.0.Final/lib/optional/

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

copy hibernate-release-4.1.0.Final/lib/required/

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

copy hibernate-release-4.1.0.Final/lib/required/

hibernate-core-4.1.0.Final.jar $HIBERNATE_JAR_DIR

copy hibernate-release-4.1.0.Final/lib/required/

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

copy hibernate-release-4.1.0.Final/lib/required/

javassist-3.15.0-GA.jar $HIBERNATE_JAR_DIR

copy hibernate-release-4.1.0.Final/lib/required/

jboss-logging-3.1.0.CR2.jar $HIBERNATE_JAR_DIR

copy hibernate-release-4.1.0.Final/lib/required/

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

Oracle WebLogic 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 12.1.3.0+.

Planning the Installation 3-11

Oracle Utilities Work and Asset Management Installation Guide

Chapter 4

Installing Oracle Utilities Work and Asset

Management - Initial Installation

This chapter provides instructions for installing Oracle Utilities Work and Asset Management

from scratch.

Note: The software components that are required for an initial installation are

available for download from the Oracle Software Delivery Cloud.

This chapter includes information on the following:

•

Initial Installation Procedure

•

After the Installation

•

Operating the Application

Installing Oracle Utilities Work and Asset Management - Initial Installation 4-1

Oracle Utilities Work and Asset Management Installation Guide

Initial Installation Procedure

Before You Install

Refer to My Oracle Support for up-to-date additional information on Oracle Utilities Work and

Asset 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 Work and Asset Management must be

complete before you can proceed with the following sections. Refer to the section “Initial

Install” of the Oracle Utilities Work and Asset 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 Application Component v4.3.0.1.0

•

Installing Oracle Utilities Application Framework v4.3.0.1.0 Single Fix PreRequisite

Rollup

•

Installing the Oracle Utilities Work and Asset Management Application Component

Installing the Oracle Utilities Application Framework Application Component

v4.3.0.1.0

This section describes how to install the application component of Oracle Utilities Application

Framework, 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 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 administrator user ID.

2. Download the Oracle Utilities Application Framework V4.3.0.1.0 Multiplatform from Oracle

Software Delivery Cloud.

3. Create a temporary directory such as c:\ouaf\temp or /ouaf/temp. (Referred to below as

<TEMPDIR>.)

Note: This directory must be located outside any current or other working

Oracle Utilities application environment. All files that are placed in this

directory as a part of the installation can be deleted after completing a

successful installation.

Installing Oracle Utilities Work and Asset Management - Initial Installation 4-2

Oracle Utilities Work and Asset Management Installation Guide

Initial Installation Procedure

4. Copy the file FW-V4.3.0.1.0-MultiPlatform.jar from the delivered package to the

<TEMPDIR>. If you are using FTP to transfer this file, remember to use the BINARY

option for the FTP transfer.

5. Decompress the file:

cd <TEMPDIR>

jar -xvf FW-V4.3.0.1.0-MultiPlatform.jar

Note: You will need to have Java JDK installed on the machine used to (un)jar

the application server installation package. Please install the JDK that is

supported for the install on your platform to be able to use the jar command.

This is the location of Java packages: http://www.oracle.com/technetwork/

java/archive-139210.html

A sub-directory named "FW.V4.3.0.1.0" is created. It contains the installation software for the Oracle Utilities framework application server.

Setting Permissions for the cistab file in UNIX

Every Oracle Utilities Application Framework environment installed on a server must be

registered in the /etc/cistab file located on that server. On UNIX servers, generally only the root

user ID has write permissions to the /etc directory. Since the installation process is run by the

Oracle administrator user ID (cissys), this user ID may not be able to write to /etc/cistab table.

The install utility checks permissions and if it identifies a lack of the necessary permissions, it

generates a script in the <TEMPDIR>/FW.V4.3.0.1.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.

1. Login to the Application Server host as administrator user ID (the default is cissys on UNIX)

or as a user with administrator privileges (on Windows).

2. Change directory to the <TEMPDIR>/FW.V4.3.0.1.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

Installing Oracle Utilities Work and Asset Management - Initial Installation 4-3

Oracle Utilities Work and Asset Management Installation Guide

Initial Installation Procedure

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 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. Environment ID, Roles, Third Party Software Configuration

Environment ID:

Server Roles: batch, online

Oracle Client Home Directory:

Web Java Home Directory:

Hibernate JAR Directory:

ONS JAR Directory:

Web Application Server Home Directory:

WebLogic Server Thin-Client JAR Directory:

ADF Home Directory:

OIM OAM Enabled Environment:

2. Keystore Options

Import Keystore Directory:

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:

Log Files Mount Point:

Environment Name:

Web Application Server Type:

Install Application Viewer Module: true

Install Demo Generation Cert Script: true

Install Sample CM Source Code: true

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

install.

Installing Oracle Utilities Work and Asset Management - Initial Installation 4-4

Oracle Utilities Work and Asset Management Installation Guide

Initial Installation Procedure

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>

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 Port 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:

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>

Database Name: <Mandatory>

Database Server: <Mandatory>

Database Port: <Mandatory>

ONS Server Configuration:

Database Override Connection String:

Oracle Client Character Set NLS_LANG:

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:

Installing Oracle Utilities Work and Asset Management - Initial Installation 4-5

Oracle Utilities Work and Asset Management Installation Guide

Initial Installation Procedure

Batch Mode: <Mandatory> - CLUSTERED

or DISTRIBUTED

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: DEMO

Identify Keystore File:

Identify Keystore File Type: jks

Identify Keystore Password:

Identity Private Key Alias: ouaf_demo_cert

Trust Keystore File:

Trust Keystore File Type: jks

Trust Keystore Password:

Trust Private Key Alias: ouaf_demo_cert

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

install.

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

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.

Installing Oracle Utilities Application Framework v4.3.0.1.0 Single Fix PreReq-

uisite Rollup

Oracle Utilities Application Framework patches must be installed prior to installing Oracle

Utilities Work and Asset Management. The patches are available as a convenience rollup inside the

zip file ‘Oracle Utilities Application Framework v4.3.0.1.0 Single Fix Prerequisite Rollup for

Oracle Utilities Work and Asset Management v2.1.1.0.0.zip’ which is part of the downloaded

Media Pack.

For a list of the patches that are included in this rollup, refer to Appendix Application Framework

Prerequisite Patches.

Follow these steps for installing the application patches on top of Oracle Utilities Application

Framework 4.3.0.1.0:

1. Copy the file WAM-V21100-FW-PREREQ-MultiPlatform.jar in the delivered package to a

<TEMPDIR>. Unjar using below command:

jar -xvf WAM-V21100-FW-PREREQ-MultiPlatform.jar

2. Initialize the Framework environment that you want to install the Framework patch rollup

into:

UNIX:

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

Windows:

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

3. Install application patches:

Installing Oracle Utilities Work and Asset Management - Initial Installation 4-6

Oracle Utilities Work and Asset Management Installation Guide

Initial Installation Procedure

a.

Navigate to the <temp location>/ FW-V4.3.0.1.0-Rollup/Application folder

b. Execute the group installation script:

Unix /Linux:

chmod a+x installSFgroup.sh

chmod a+x FW*/*.sh

./installSFgroup.sh

Windows:

installSFgroup.cmd

Installing the Oracle Utilities Work and Asset Management Application Com-

ponent

This section describes how to install the application component of Oracle Utilities Work and

Asset Management, including:

•

Copying and Decompressing Install Media

•

Installing the Application Component

•

Performing Post-Installation Tasks

Copying and Decompressing Install Media

The Oracle Utilities Work and Asset 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 administrator user ID (default cissys). This is the

same user ID that was used to install the Oracle Utilities Application Framework.

2. Download the Oracle Utilities Work and Asset Management V2.1.1.0.0 Multiplatform from

Oracle Software Delivery Cloud.

3. Create a <TEMPDIR> directory on the host server, which is independent of any current or

other working Oracle Utilities Work and Asset Management application environment. This

can be the same <TEMPDIR> used during the installation of the Oracle Utilities Application

Framework.

4. Copy the file WAM-V2.1.1.0.0-MultiPlatform.jar in the delivered package to a <TEMPDIR>

on your host server. If you are using FTP to transfer this file, remember to use the BINARY

option for the FTP transfer.

5. Decompress the file:

cd <TEMPDIR>

jar -xvf WAM-V2.1.1.0.0-MultiPlatform.jar

For Windows installations, include the location of the JDK in your path before you execute

the jar command.

For both Unix and Windows platforms, a sub-directory named W1.V2.1.1.0.0 is created. The

contents of the installation directory are identical for both platforms. The directory contains the

install software for the application product.

Installing the Application Component

Follow the steps below to install Oracle Utilities Work and Asset Management application

component:

1. Log in to the application server host as the administrator user ID (default cissys).

2. Change directory:

cd <install_dir>/bin

Installing Oracle Utilities Work and Asset Management - Initial Installation 4-7

Oracle Utilities Work and Asset Management Installation Guide

Initial Installation Procedure

where <install_dir> is the location where the Oracle Utilities Asset Management 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. If the environment is running, stop it by running the appropriate command:

UNIX:

./spl.sh stop

Windows:

spl.cmd stop

5. Change to the <TEMPDIR>/W1.V2.1.1.0.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

Note: •If you are using demo certificates, please execute the below

command before starting the environment:

UNIX:

cd $SPLEBASE/bin

perl demo_gen_cert.plx

Windows:

cd %SPLEBASE%/bin

perl demo_gen_cert.plx

Once the install has finished successfully, generate the app viewer as described below.

Performing Post-Installation Tasks

1. Generate the appviewer by following the steps below:

a.

Change the directory.

cd <install_dir>/bin ,

where <install_dir> is Oracle Utilities Work and Asset Management Application

Component installation directory

b. Run the script to generate the appviewer.

UNIX:

ksh ./genappvieweritems.sh

Installing Oracle Utilities Work and Asset Management - Initial Installation 4-8

Oracle Utilities Work and Asset Management Installation Guide

Operating the Application

Windows:

genappvieweritems.cmd

3. Create a default WAM user by following the steps below:

a.

For HTTP (Non-SSL) Connections:

ant -f $SPLEBASE/splapp/userAdmin.xml -

Dadmin.server.url=t3:<weblogic-host>:<weblogic-port> -

Dadmin.user=<weblogic-admin-username> -Dadmin.password=<weblogic-

admin-password> -Duser.name=WAMUSER -Duser.password=<password>

b. For HTTPS (SSL) Connections:

ant -f $SPLEBASE/splapp/userAdmin.xml -

Dadmin.server.url=t3s:<weblogic-host>:<weblogic-port> -

Dadmin.user=<weblogic-admin-username> -Dadmin.password=<weblogic-

admin-password> -Duser.name=WAMUSER -Duser.password=<password>

After the Installation

After you complete 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 Installation and Configuration

Worksheets for details.

4. Confirm that the database is ready.

5. Generate appviewer.

6. Start the application server. For instructions, refer to Appendix Common Maintenance

Activities.

7. 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 Work and Asset Management Server Administration Guide for more information on further configuring and operating the system.

Installing Oracle Utilities Work and Asset Management - Initial Installation 4-9

Oracle Utilities Work and Asset Management Installation Guide

Chapter 5

Installing Oracle Utilities Work and Asset

Management - Demo Installation

This chapter provides instructions for setting up a demo application of Oracle Utilities Work and

Asset Management useful for demonstration or training purposes. This chapter includes:

•

Demo Installation Procedure

•

After the Installation

•

Operating the Application

Installing Oracle Utilities Work and Asset Management - Demo Installation 5-1

Oracle Utilities Work and Asset Management Installation Guide

Demo Installation Procedure

Before You Install

Oracle recommends that you do not clone the demonstration environment as a basis for a new

production environment. The demonstration environment typically includes transactional data

that will be irrelevant to your production environment and can cause unexpected issues if it is not

purged correctly. The recommended process is to start a new production environment from a new

installation and migrate "clean" system data (such as business objects and algorithms) and

administrative data (such as sample activity types or other administrative entities) from the

demonstration and/or test or development environments as applicable.

Please refer to the Administrative Guide for more information or contact Oracle Support.

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 Work and Asset Management must be

complete before you can proceed with the following sections. Refer to the Oracle Utilities Work and Asset 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 Application Component v4.3.0.1.0

•

Installing Oracle Utilities Application Framework v4.3.0.1.0 Single Fix PreRequisite

Rollup

•

Installing the Oracle Utilities Work and Asset Management Application Component

Installing the Oracle Utilities Application Framework Application Component

v4.3.0.1.0

This section describes how to install the application component of Oracle Utilities Application

Framework, 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 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 administrator user ID.

2. Download the Oracle Utilities Application Framework V4.3.0.1.0 Multiplatform from Oracle

Software Delivery Cloud.

Installing Oracle Utilities Work and Asset Management - Demo Installation 5-2

Oracle Utilities Work and Asset Management Installation Guide

Demo Installation Procedure

3. Create a temporary directory such as c:\ouaf\temp or /ouaf/temp. (Referred to below as

<TEMPDIR>.)

Note: This directory must be located outside any current or other working

Oracle Utilities application environment. All files that are placed in this

directory as a part of the installation can be deleted after completing a

successful installation.

4. Copy the file FW-V4.3.0.1.0-MultiPlatform.jar from the delivered package to the

<TEMPDIR>. If you are using FTP to transfer this file, remember to use the BINARY

option for the FTP transfer.

5. Decompress the file:

cd <TEMPDIR>

jar -xvf FW-V4.3.0.1.0-MultiPlatform.jar

Note: You will need to have Java JDK installed on the machine used to (un)jar

the application server installation package. Please install the JDK that is

supported for the install on your platform to be able to use the jar command.

This is the location of Java packages: http://www.oracle.com/technetwork/

java/archive-139210.html

A sub-directory named "FW.V4.3.0.1.0" is created. It contains the installation software for the Oracle Utilities framework application server.

Setting Permissions for the cistab file in UNIX

Every Oracle Utilities Application Framework environment installed on a server must be

registered in the /etc/cistab file located on that server. On UNIX servers, generally only the root

user ID has write permissions to the /etc directory. Since the installation process is run by the

Oracle administrator user ID (cissys), this user ID may not be able to write to /etc/cistab table.

The install utility checks permissions and if it identifies a lack of the necessary permissions, it

generates a script in the <TEMPDIR>/FW.V4.3.0.1.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.

1. Login to the Application Server host as administrator user ID (the default is cissys on UNIX)

or as a user with administrator privileges (on Windows).

2. Change directory to the <TEMPDIR>/FW.V4.3.0.1.0 directory.

3. Set the ORACLE_CLIENT_HOME and PATH variables as Oracle Client Perl is required to

run the installer.

Installing Oracle Utilities Work and Asset Management - Demo Installation 5-3

Oracle Utilities Work and Asset Management Installation Guide

Demo Installation Procedure

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 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. Environment ID, Roles, Third Party Software Configuration

Environment ID:

Server Roles: batch, online

Oracle Client Home Directory:

Web Java Home Directory:

Hibernate JAR Directory:

ONS JAR Directory:

Web Application Server Home Directory:

WebLogic Server Thin-Client JAR Directory:

ADF Home Directory:

OIM OAM Enabled Environment:

2. Keystore Options

Import Keystore Directory:

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:

Log Files Mount Point:

Environment Name:

Installing Oracle Utilities Work and Asset Management - Demo Installation 5-4

Oracle Utilities Work and Asset Management Installation Guide

Demo Installation Procedure

Web Application Server Type:

Install Application Viewer Module: true

Install Demo Generation Cert Script: true

Install Sample CM Source Code: true

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

install.

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

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>

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 Port 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:

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>

Database Name: <Mandatory>

Database Server: <Mandatory>

Database Port: <Mandatory>

ONS Server Configuration:

Database Override Connection String:

Oracle Client Character Set NLS_LANG:

Installing Oracle Utilities Work and Asset Management - Demo Installation 5-5

Oracle Utilities Work and Asset Management Installation Guide

Demo Installation Procedure

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:

Batch Mode: <Mandatory> - CLUSTERED

or DISTRIBUTED

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: DEMO

Identify Keystore File:

Identify Keystore File Type: jks

Identify Keystore Password:

Identity Private Key Alias: ouaf_demo_cert

Trust Keystore File:

Trust Keystore File Type: jks

Trust Keystore Password:

Trust Private Key Alias: ouaf_demo_cert

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

install.

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

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.

Installing Oracle Utilities Application Framework v4.3.0.1.0 Single Fix

PreRequisite Rollup

Oracle Utilities Application Framework patches must be installed prior to installing Oracle

Utilities Work and Asset Management. The patches are available as a convenience rollup inside the

zip file ‘Oracle Utilities Application Framework v4.3.0.1.0 Single Fix Prerequisite Rollup for

Oracle Utilities Work and Asset Management v2.1.1.0.0.zip’ which is part of the downloaded

Media Pack.

For a list of the patches that are included in this rollup, refer to Appendix Application Framework

Prerequisite Patches.

Follow these steps for installing the application patches on top of Oracle Utilities Application

Framework 4.3.0.1.0:

1. Copy the file WAM-V21100-FW-PREREQ-MultiPlatform.jar in the delivered package to a

<TEMPDIR>. Unjar using below command:

jar -xvf WAM-V21100-FW-PREREQ-MultiPlatform.jar

2. Initialize the Framework environment that you want to install the Framework patch rollup

into:

Installing Oracle Utilities Work and Asset Management - Demo Installation 5-6

Oracle Utilities Work and Asset Management Installation Guide

Demo Installation Procedure

UNIX:

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

Windows:

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

3. Install application patches:

a.

Navigate to the <temp location>/ FW-V4.3.0.1.0-Rollup/Application folder

b. Execute the group installation script:

Unix /Linux:

chmod a+x installSFgroup.sh

chmod a+x FW*/*.sh

./installSFgroup.sh

Windows:

installSFgroup.cmd

Installing the Oracle Utilities Work and Asset Management Application

Component

This section describes how to install the application component of Oracle Utilities Work and

Asset Management, including:

•

Copying and Decompressing Install Media

•

Installing the Application Component

•

Performing Post-Installation Tasks

Copying and Decompressing Install Media

The Oracle Utilities Work and Asset 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 administrator user ID (default cissys). This is the

same user ID that was used to install the Oracle Utilities Application Framework.

2. Download the Oracle Utilities Work and Asset Management V2.1.1.0.0 Multiplatform from

Oracle Software Delivery Cloud.

3. Create a <TEMPDIR> directory on the host server, which is independent of any current or

other working Oracle Utilities Work and Asset Management application environment. This

can be the same <TEMPDIR> used during the installation of the Oracle Utilities Application

Framework.

4. Copy the file WAM-V2.1.1.0.0-MultiPlatform.jar in the delivered package to a <TEMPDIR>

on your host server. If you are using FTP to transfer this file, remember to use the BINARY

option for the FTP transfer.

5. Decompress the file:

cd <TEMPDIR>

jar -xvf WAM-V2.1.1.0.0-MultiPlatform.jar

For Windows installations, include the location of the JDK in your path before you execute

the jar command.

For both Unix and Windows platforms, a sub-directory named W1.V2.1.1.0.0 is created. The

contents of the installation directory are identical for both platforms. The directory contains the

install software for the application product.

Installing Oracle Utilities Work and Asset Management - Demo Installation 5-7

Oracle Utilities Work and Asset Management Installation Guide

Demo Installation Procedure

Installing the Application Component

Follow the steps below to install Oracle Utilities Work and Asset Management application

component:

1. Log in to the application server host as the administrator user ID (default cissys).

2. Change directory:

cd <install_dir>/bin

where <install_dir> is the location where the Oracle Utilities Asset Management 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. If the environment is running, stop it by running the appropriate command:

UNIX:

./spl.sh stop

Windows:

spl.cmd stop

5. Change to the <TEMPDIR>/W1.V2.1.1.0.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

Note: •If you are using demo certificates, please execute the below

command before starting the environment:

UNIX:

cd $SPLEBASE/bin

perl demo_gen_cert.plx

Windows:

cd %SPLEBASE%/bin

perl demo_gen_cert.plx

Once the install has finished successfully, generate the app viewer as described below.

Performing Post-Installation Tasks

1. Generate the appviewer by following the steps below:

a.

Change the directory.

Installing Oracle Utilities Work and Asset Management - Demo Installation 5-8

Oracle Utilities Work and Asset Management Installation Guide

Operating the Application

cd <install_dir>/bin ,

where <install_dir> is Oracle Utilities Work and Asset Management Application

Component installation directory

b. Run the script to generate the appviewer.

UNIX:

ksh ./genappvieweritems.sh

Windows:

genappvieweritems.cmd

2. Create a default WAM user by following the steps below:

a.

For HTTP (Non-SSL) Connections:

ant -f $SPLEBASE/splapp/userAdmin.xml -

Dadmin.server.url=t3:<weblogic-host>:<weblogic-port> -

Dadmin.user=<weblogic-admin-username> -

Dadmin.password=<weblogic-admin-password> -Duser.name=WAMUSER -

Duser.password=<password>

b. For HTTPS (SSL) Connections:

ant -f $SPLEBASE/splapp/userAdmin.xml -

Dadmin.server.url=t3s:<weblogic-host>:<weblogic-port> -

Dadmin.user=<weblogic-admin-username> -

Dadmin.password=<weblogic-admin-password> -Duser.name=WAMUSER -

Duser.password=<password>

After the Installation

After you complete 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 Installation and Configuration

Worksheets for details.

4. Confirm that the database is ready.

5. Generate appviewer.

6. Start the application server. For instructions, refer to Appendix Common Maintenance

Activities.

7. 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 Work and Asset Management Server Administration Guide for more information on further configuring and operating the system.

Installing Oracle Utilities Work and Asset Management - Demo Installation 5-9

Oracle Utilities Work and Asset Management Installation Guide

Chapter 6

Additional Tasks

This section describes tasks that should be completed after installing Oracle Utilities Work and

Asset Management, including:

•

WebLogic Production Server Considerations

•

Building Javadoc Indexes

•

Configuring the Environment for Batch Processing

•

Customizing the Logo

•

Deploying Inbound WebServices (IWS)

•

Installing Service Packs and Patches

Additional Tasks 6-1

Oracle Utilities Work and Asset Management Installation Guide

Building Javadoc Indexes

WebLogic Production Server Considerations

By default, WebLogic Server is configured with two keystores, to be used for development only.

These keystores should not be used in a production environment.

Configuring Identity and Trust

Private keys, digital certificates, and trusted certificate authority certificates establish and verify identity and trust in the WebLogic Server environment. WebLogic Server is configured with a

default identity keystore DemoIdentity.jks and a default trust keystore DemoTrust.jks. In addition,

WebLogic Server trusts the certificate authorities in the cacerts file in the JDK. This default

keystore configuration is appropriate for testing and development purposes. However, these

keystores should not be used in a production environment.

To configure identity and trust for a server:

1. Obtain digital certificates, private keys, and trusted CA certificates from the CertGen utility,

Sun Microsystem's keytool utility, or a reputable vendor such as Entrust or Verisign. You can

also use the digital certificates, private keys, and trusted CA certificates provided by the

WebLogic Server kit. The demonstration digital certificates, private keys, and trusted CA

certificates should be used in a development environment only.

2. Store the private keys, digital certificates, and trusted CA certificates. Private keys and trusted CA certificates are stored in a keystore.

3. Configure the identity and trust keystores for a WebLogic Server instance on the

Configuration: Keystores page.

By default, WebLogic Server is configured with two keystores, to be used for development only.

•

DemoIdentity.jks: Contains a demonstration private key for WebLogic Server. This keystore

establishes an identity for WebLogic Server.

•

DemoTrust.jks: Contains a list of certificate authorities trusted by WebLogic Server. This

keystore establishes trust for WebLogic Server.

These keystores are located in the WL_HOME\server\lib directory and the

JAVA_HOME\jre\lib\security directory. For testing and development purposes, the keystore

configuration is complete. Use the steps in this section to configure identity and trust keystores for production use.

Refer to the WebLogic documentation to configure identity and trust keystores for production use

(Secure servers and resources > Configure identity and trust/Set up SSL)

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.

Building Javadoc Indexes

The following script rebuilds the Javadocs indexes in the application viewer java module. This is

necessary after customer modifications (CM) have been applied to an environment. You need to

run this script only if the customer modification includes Java code.)

Windows:

%SPLEBASE%\bin\buildJavadocsIndex.cmd

UNIX:

ksh $SPLEBASE/bin/buildJavadocsIndex.sh

Additional Tasks 6-2

Oracle Utilities Work and Asset Management Installation Guide

Deploying Inbound WebServices (IWS)

Configuring the Environment for Batch Processing

See the Batch 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>.gif 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>.gif

UNIX:

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

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.

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:

UNIX:

1. Enable the Web Services Functionality as shown below:

a.

cd $SPLEBASE/bin

b. Execute configureEnv.sh –a

c.

Select option 50 and set the option “Enable Web Services Functionality” to true.

d. Set the option Web Application Additional Options to “ -

Djavax.xml.soap.MessageFactory=com.sun.xml.interna

l.messaging.saaj.soap.ver1_1.SOAPMessageFactory1_1I mpl”

e.

Set the option Additional Runtime Classpath to “$WL_HOME/../oracle_common/

modules/ com.sun.xml.messaging.saaj.saaj-impl_1.3.jar”

f.

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

Additional Tasks 6-3

Oracle Utilities Work and Asset Management Installation Guide

Installing Service Packs and Patches

$ 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

WINDOWS:

1. Enable the Web Services Functionality as shown below:

cd %SPLEBASE%\bin

2. Execute configureEnv.cmd –a

a.

Select option 50 and set the option “Enable Web Services Functionality” to true.

b. Set the option Web Application Additional Options to “ -

Djavax.xml.soap.MessageFactory=com.sun.xml.interna

l.messaging.saaj.soap.ver1_1.SOAPMessageFactory1_1I mpl”

c.

Set the option Additional Runtime Classpath to “$WL_HOME/../oracle_common/

modules/ com.sun.xml.messaging.saaj.saaj-impl_1.3.jar”

d. 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

Installing Service Packs and Patches

Periodically, Oracle Utilities releases a service pack of single fixes for its products. A service pack is an update to an existing release that includes solutions to known problems and other product

enhancements. A service pack is not a replacement for an installation, but a pack consisting of a

collection of changes and additions for it. The service pack may include changes to be applied to

the application server, the database, or both. The service pack includes all files necessary for

installing the collection of changes, including installation instructions.

Between services packs, Oracle Utilities releases patches to fix individual bugs. For information on

installing patches, refer to knowledge base article ID 974985.1 on My Oracle Support.

Service packs and patches can be downloaded from My Oracle Support (https://

support.oracle.com/).

Additional Tasks 6-4

Oracle Utilities Work and Asset Management Installation Guide

Chapter 7

Installing Optional Products

This chapter describes the optional products that can be installed. These should be completed

after installing Oracle Utilities Work and Asset Management. These products include:

•

Oracle BI Publisher

Oracle BI Publisher

This section describes the steps required to configure Oracle Utilities Work and Asset

Management and Oracle BI Publisher to support an Oracle BI Publisher reporting solution. This

section includes:

•

Supported BI Publisher Versions

•

About Oracle BI Publisher Enterprise

•

Configuring the System to Enable Reports

•

Sample Reports Supplied with the Product

•

Sample Reports Supplied with the Product

Supported BI Publisher Versions

At the time of release, supported Oracle BI Publisher versions for include:

•

Windows: BI Publisher 11g (11.1.1.7.0)

•

Unix: BI Publisher 11g (11.1.1.7.0)

About Oracle BI Publisher Enterprise

Oracle BI Publisher Enterprise provides the tools for:

•

Making reports available over the web (establishing the required report server processes)

•

Integrating reports with the Oracle Utilities Work and Asset Management system

•

Scheduling reports to run on a regular basis

•

Managing instances of the reports that have been created by a previous run

•

Managing user access to the report instances

Installing Optional Products 7-1

Oracle Utilities Work and Asset Management Installation Guide

Oracle BI Publisher

Installing Oracle BI Publisher Enterprise

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

requests can be pointed to the Oracle BI Publisher Enterprise running on Windows or Unix.

Note: If you are running the BI Publisher server on a Linux or Unix machine

that does not have an X Server installed, reports that contain images may not

be properly generated. 



To fix this, specify the following property at the java command line:

-Djava.awt.headless=true

Configuring the System to Enable Reports

This section describes the steps needed to configure your system to enable reports, including:

•

Configuring the System to Invoke Oracle BI Publisher Enterprise Real-time

•

Interfacing with Oracle BI Publisher Enterprise Batch Scheduler

Configuring the System to Invoke Oracle BI Publisher Enterprise Real-time

In order to invoke Oracle BI Publisher Enterprise from within Oracle Utilities Work and Asset

Management, the system must be configured accordingly.

Specifying Reporting Tool Options

The following information should be defined on Reporting Tool Options table:

•

Reporting Server is the web server URL where the reporting tool is installed.

•

Reporting Folder defines the name of the directory on the Oracle BI Publisher server where

reports are located. The Oracle Utilities Work and Asset Management reporting tool

algorithm constructs the URL needed to open Oracle BI Publisher Enterprise based on the

information provided on Reporting Options. 



The same folder name should be used as a report folder in Oracle BI Publisher Enterprise

where reports are published.

Reporting Tool Algorithm

The base product provides an Installation Options system event called Reporting Tool which

should contain an algorithm which invokes the reporting tool in real-time. Oracle Utilities Work

and Asset Management provides an algorithm type called F1-BIPR-INV, which invokes Oracle BI

Publisher Enterprise.

This algorithm relies on information defined in the Reporting Options table: the reporting server

and folder names for accessing the reporting tool. The algorithm constructs several strings, for

example, the URL of the BI Publisher, information about the report being requested and user info

in the format expected by Oracle BI Publisher Enterprise. The Java program returns the correct

URL to the browser. The browser then opens a BI Publisher Enterprise window with the

appropriate URL.

To use the F1-BIPR-INV algorithm type to invoke Oracle BI Publisher Enterprise, perform the

following steps:

1. Create an algorithm for this algorithm type.

2. On the installation options, add an entry to the algorithm collection with an algorithm entity

of Reporting Tool and indicate the algorithm created in the previous step.

Installing Optional Products 7-2

Oracle Utilities Work and Asset Management Installation Guide

Oracle BI Publisher

Interfacing with Oracle BI Publisher Enterprise Batch Scheduler

Presently Oracle Utilities Work and Asset Management does not provide support for batch jobs

with Oracle BI Publisher. Please use Oracle BI Publisher directly in order to schedule reports to

run in batch.

Sample Reports Supplied with the Product

The system provides several sample reports that may be used by your organization as a starting

point for creating a new report. The following sections provide instructions on how to set up your

implementation environment to use the sample reports.

If you would like to use any of the sample reports, you need to perform some steps to be able to

execute them in an implementation environment. This section walks you through the steps

needed, including:

•

Unzipping Oracle Utilities Work and Asset Management Report Files

•

Oracle Functions and Packages

•

Publishing the Sample Reports in Oracle BI Publisher Enterprise

•

Preparing Oracle BI Publisher Enterprise Server For integration

•

Copying a Report Definition From the Demonstration Database

•

Copying a Report Definition From the Demonstration Database

Unzipping Oracle Utilities Work and Asset Management Report Files

Unzip the ‘Oracle Utilities Work and Asset Management v2.1.1.0.0 Reports.zip’ file from the

installation media into an empty directory. We'll refer to this directory as the reports extract folder.

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.

Oracle Functions and Packages

Each report has one or more corresponding database functions and packages that store the

business logic to fetch the data from the database. This data is then presented in the report.

The installation media contains the required database functions and packages. These files are in

the reports extract folder under . \WAM-V21100-Reports\BIPublisher\functions\oracle.

The prerequisite for Oracle Utilities Work and Asset Management reports to work against the

target database is setting up of a RPTUSER database user. This user should have read access to all

Oracle Utilities Work and Asset Management database objects and execution privilege on the

stored procedures that the reports access.

The steps involved in setting up the RPTUSER are:

1. Create or refresh the Oracle functions and packages.

•

Using SQLPLUS, log in to the target database as the user CISADM.

This user owns Oracle Utilities Work and Asset Management schema objects.

•

Execu te t he scr ipt CDX_rptfn.sql by entering the following command at the SQL

prompt:

SQL> @CDX_rptfn.sql

(“SQL>” denotes the SQL prompt and doesn't need to be typed).

2. Create the RPTUSER.

•

Navigate to the Database\Oracle folder.

Installing Optional Products 7-3

Oracle Utilities Work and Asset Management Installation Guide

Oracle BI Publisher

•

Edit the file CDX_rptuser.sql to match your requirements. 

Ensure that you review the user password and the default and temporary tablespace

names for the user.

•

Log in to the target database as a DBA user using SQLPLUS.

•

Execute the script by entering following command at SQL prompt:

SQL> @CDX_rptuser.sql

3. Compile the report function.

SQL> @CDX_compfn.sql

4. Configure security.

This involves generating synonyms in RPTUSER and granting it privileges to execute the

stored procedures and read the Oracle Utilities Work and Asset Management tables. The

utility prompts you to answer for the following questions:

•

Enter the Oracle user that owns the schema (e.g. CISADM): CISADM

•

Enter the password for the CISADM user: CISADM

•

Enter the name of the Oracle Database: Your_db

•

Enter a comma-separated list of Oracle users in which synonyms need to be created (e.g.

cisuser,cisread): RPTUSER

•

Select the following options:

•

(A/a): Generate security for All objects in the Database?

•

(O/o): Generate security for specific Objects inputted in this terminal?

•

(F/f): Generate security for specific objects generated from an input File?

<<<< select A to generate security to all objects >>>>

The utility runs and configures security for the Oracle Utilities Work and Asset Management

objects.

Publishing 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 ..\WAM-V21100-Reports\BIPublisher\reportFiles.

Configuring Oracle BI Publisher Enterprise

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

Note: If you install Oracle BI Publisher Enterprise in a location other than the

default installation directory, adjust the path descriptions to match your actual

install directories.

The first step you need to take in order to use any of the samples is to publish the report in Oracle

BI Publisher Enterprise. You need to create a folder in Oracle BI Publisher Enterprise named as

defined on Reporting Options table in Oracle Utilities Work and Asset Management and publish

the report extracted to the reports extract folder.

Create a folder named WAM in the BI_Repository_Path\Reports folder. Copy all Oracle BI

Publisher sample reports into the WAM 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.

Please refer to the Oracle BI Publisher Enterprise documentation for more information.

Installing Optional Products 7-4

Oracle Utilities Work and Asset Management Installation Guide

Oracle BI Publisher

Preparing Oracle BI Publisher Enterprise Server For integration

The WAM Reporting Options Table should include the following information about Reporting

Server and Folder:

•

Reporting Folder: WAM

•

Reporting Server: URL of reporting server. For example: http://sf-

ugbu.splwg.com:9704

If you want to have a different name for your reporting folder, you can rename the WAM folder

on the server and put the corresponding value on the Reporting options table.

Accessing the BI Publisher Enterprise Server

1. Access the BI Publisher Enterprise Server as Administrator.

2. On the Admin tab define a JDBC Connection section under Data Sources, and add a new

data source using Add Data Source.

Create a new Data Source named WAM with connection details pointing to the WAM

database using the RPTUSER credentials set up in the prior section.

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

Apply.

Configuring a new group in WebLogic

1. Configure a group within WebLogic for Authentication called “BIConsumer”.

2. Create an Application Role called “WAM Reports” to access the BI Publisher reports.

3. Associate the member “BIConsumer” with the “WAM Reports” Application Role.

The role will now be visible from within the BI Publisher Enterprise. Within BI Publisher

Enterprise, for the Role Name WAM Reports you just created, click on Add Folders to add

the WAM sample reports to the Allowed Folders.



Do the same for Role Name WAM Reports. Click on Add Data Sources to add the WAM

data source to the Allowed Data Sources.

4. To include appropriate Roles for Role Name WAM Reports, click on Add Role.

Uploading Reports to BI Publisher

From BI publisher server console, upload reports to BI Publisher. To do so:

1. Select Administration, System Maintenance, and then click Server Configuration.

2. Scroll down to the Catalog section and verify that the path to the repository folder is correct in the BI Publisher repository field and is pointing to the WAM folder to which reports were

copied.

3. Click Upload to BI Presentation Catalog to upload the reports to BI Publisher.

Verifying the Data Model Details

From BI publisher server console, verify that the data model details are correct. To do so:

1. From the Reports folder, select the data model of the report.

2. Click Edit to edit the data model.

3. Select Data Model from the tree on the left.

4. Verify that the following are correct:

•

Default Data Source: Set the data source name created in Step 2 of section Accessing the

BI Publisher Enterprise Server.

•

Oracle DB Default Package: Set this to W1_BI_RPT.

Installing Optional Products 7-5

Oracle Utilities Work and Asset Management Installation Guide

Oracle BI Publisher

•

XML Output Options: Ensure that the option Include Parameters Tag is checked.

5. Verify that the data model is pointing to the correct report. Select a report from the Reports

folder and click Edit. Hover on the Data Model link to check it is pointing to the correct data model.

To modify the data model, click the magnifying glass icon and select the correct data model.

Verifying Sample BI Publisher Reports on the Server:

1. Log in to Oracle BI Publisher Server as a user belonging to BIConsumers.

2. Verify that all sample reports provided appear in the WAM folder.

Single-sign-on and more sophisticated security must be tailored to the specific implementation.

Copying a Report Definition From the Demonstration Database

In order to use one of the sample reports in your Oracle Utilities Work and Asset Management

region, you must define the meta-data for the report. The demonstration database contains the

report definition and all its related data for each sample report.

The data present in the demonstration application should be manually created in the database that

is being used by the current WAM application.

1. To copy the data, access the data in WAM demonstration application using the following

menu navigation:

Admin -> R -> Report Definition

2. Click on Search. In the report code field, enter % and click search.

For each report visible in the search results, follow the steps below to copy the report definitions:

1. Click on the report to see the report definition details.

2. In the current WAM application, access the same menu navigation to manually create the

records.

Admin -> R -> Report Definition

3. Click Add.

4. Enter the same values for the report definition that are present in the report definition details

of the demonstration WAM application.

5. Click Save.

Installing Optional Products 7-6

Oracle Utilities Work and Asset Management Installation Guide

Appendix A

Installation Menu Functionality Overview

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 within that group 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.

Note: When working with the menu you will see 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.

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 '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.

In the worksheets there are three different types of values given:

•

Default Values are the values that will be defaulted when running the installation utility.

Installation Menu Functionality Overview A-1

Oracle Utilities Work and Asset Management Installation Guide

Installation Menu Functionality Overview

•

Security Values denote values that should be changed when in production.

•

Example Values are values that can be used for a default installation.

Note: The production environment should not be run with default values. See

the Server Administration Guide specific to this product, for additional

information about configuring these values.

When you enter passwords you will not see the password characters on the screen because they are

entered in silent mode. Passwords are encrypted when the values are entered.

Install the Oracle Client software specified in the section Supported Platforms 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.

In each case these password are entered in the command line but the inputted values are not

reflected on the screen when performing the installation.

Installation Menu Functionality Overview A-2

Oracle Utilities Work and Asset Management Installation Guide

Appendix B

Installation and Configuration Worksheets

Application Framework Installation and Configuration Worksheets

Environment ID, Roles, Third Party Software Configuration

************************************

* Environment Installation Options *

************************************

1. Environment ID, Roles, Third Party Software Configuration

Environment ID:

Server Roles:

Oracle Client Home Directory:

Web Java Home Directory:

Hibernate JAR Directory:

ONS JAR Directory:

Web Application Server Home Directory:

WebLogic Server Thin-Client JAR Directory:

ADF Home Directory:

OIM OAM Enabled Environment: false

Customer

Name Used in

Menu Option

Usage

Install

Documentation

Value

Environment ID

ENVIRONMENT_

Identifier to associate different application server as part of the

ID

same environment.

On a new installation, the default is a random 8 digit number.

Server Roles

SERVER_ROLES

The type of role the server performs whether for batch or online.

A server may be configured to have an online and/or batch role.

Only the menu items appropriate to the role will appear on the

menus, and only the appropriate scripts will be executable in the

application server.

Oracle Client Home

ORACLE_CLIENT_H

The home directory of the Oracle Client. The application will use

Directory

OME

the Perl included under this Oracle Client.

Example Location:

/oracle/client/product/12.1.0.2.0

Installation and Configuration Worksheets B-1

Oracle Utilities Work and Asset Management Installation Guide

Application Framework Installation and Configuration Worksheets

Customer

Name Used in

Menu Option

Usage

Install

Documentation

Value

Web Java Home

JAVA_HOME

Java home that will be used by the web application server.

Directory

Example Location:

/ouaf/java/jdk1.8.0_31

Hibernate JAR

HIBERNATE_JAR_

Location on the disk where the hibernate410.jar is installed.

Directory

DIR

*ONS JAR Directory

ONS_JAR_DIR

Location on the disk where the ons-12.1.0.1.jar file is installed.

**Required for Oracle RAC installation. See the Server

Administration Guide for more information.

Web Application Server

WEB_SERVER_

Location on the disk where the application server is installed.

Home Directory

HOME

Example Location:

WebLogic: /ouaf/middleware/wlserver_12.1.3

To validate the home directory, check if the following jar files exist

in the appropriate path:

$WEB_SERVER_HOME/server/lib/weblogic.jar

%WEB_SERVER_HOME%\server\lib\weblogic.jar

WebSphere:

/ouaf/IBM/WebSphere/AppServer

WebSphere ND:

/ouaf/IBM/WebSphereND/

WebLogic Server Thin-

WLTHINT3CLIENT_J

Location where wlthint3client.jar is located. Populate only if

Client JAR Directory

AR_DIR

WEB_SERVER_HOME is empty and if the application needs to

access JMS from a batch job.

* ADF Home Directory

ADF_HOME

Location on the disk where ADF is installed.

Example Location:

/ouaf/jdev11_1_1_8

Note: This is an optional value.

OIM OAM Enabled

OPEN_SPML_

Denotes if an environment will be integrating with Oracle Identity

Environment

ENABLED_ENV

Manager for user propagation.

Valid values: true

false

Defaulted value: false

* Denotes optional Menu Options 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, version

12.1.0.1+. This ons.jar is located under the Oracle Database Software 12.1.0.1, at the

following path:

Installation and Configuration Worksheets B-2

Oracle Utilities Work and Asset Management Installation Guide

Application Framework Installation and Configuration Worksheets

$ORACLE_HOME/opmn/lib/ons.jar

The ons.jar should be copied to the Application Server. During the OUAF installation the

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

Keystore Options

Note: Please review the Security Guide for more information on setting up keystores.

2. Keystore Options

Import Keystore Directory:

Store Type: JCEKS

Alias: ouaf.system

Alias Key Algorithm: AES

Alias Key Size: 128

HMAC Alias: ouaf.system.hmac

Padding: PKCS5Padding

Mode: CBC

Customer

Name Used in

Menu Option

Usage

Install

Documentation

Value

Import Keystore 

KS_IMPORT_

Specify this option if you want to import the keystore files

Directory

KEYSTORE_

from an external location or directory, during the installation

FOLDER

process. This is needed when the customer has an existing

environment that has a keystore and the database your new

application server.

After installation is complete, to configure keystore options,

perform the following sequence:

configureEnv.sh|cmd –i (enter keystore options)

initialSetup.sh|cmd –s (loads keystore)

configureEnv.sh|cmd (reenter ouaf encrypted security

information such as passwords)

initialSetup.sh|cmd (distribute the encrypted data)

If this option is left empty, the install process creates a new

keystore from scratch.

Store Type

KS_STORETYPE

Value used for keytool option –storetype

Default value: JCEKS

Alias

KS_ALIAS

Value used for keytool option –alias

Default value: ouaf.system

Alias Key Algorithm

KS_ALIAS_KEYALG

Value used for keytool option -keyalg

Alias Key Size

KS_ALIAS_KEYSIZE

Value used for keytool option -keysize

HMAC Alias

KS_HMAC_ALIAS

Value used for keytool option -alias

The following values are fixed:

- HMAC Alias Key Algorithm: HmacSHA256

- HMAC Alias Key Size: 256

Default value: ouaf.system.hmac

Padding

KS_PADDING

Value used for encryption/decryption

Default value: PKCS5Padding

Installation and Configuration Worksheets B-3

Oracle Utilities Work and Asset Management Installation Guide

Application Framework Installation and Configuration Worksheets

Customer

Name Used in

Menu Option

Usage

Install

Documentation

Value

Mode

KS_MODE

Value used for encryption/decryption

Default Vaule: CBC

Environment Installation Options

50. Environment Installation Options

Environment Mount Point:

Log Files Mount Point:

Environment Name:

Web Application Server Type: WLS

Install Application Viewer Module: true

Install Demo Generation Cert Script: true

Install Sample CM Source Code: true

Customer

Name Used in

Menu Option

Usage

Install

Documentation

Value

Environment Mount Point

<SPLDIR>

The mount point into which the application is installed.

For example:

/ouaf for UNIX and C:\ouaf for Windows.

This mount point MUST exist and the administrator user ID

MUST be able to write to this directory. (This is the user ID

that is created specifically to administer the product

environments; the default is cissys). The installation sets

permissions on all subdirectories installed under this

directory.

See <SPLENVIRON> below for more information on how

this mount point is used.

Log File Mount Point

<SPLDIROUT>

A mount point that will contain any application output or

application logs. Example value is /ouaf/sploutput for UNIX

installation or C:\ouaf\sploutput for Windows.

This mount point MUST exist and the administrator user ID

MUST be able to write to this directory. (This is the user ID

that is created specifically to administer the product

environments; the default is cissys).

For each environment initialized, the application logs will be

written to the directory <SPLDIROUT>/

<SPLENVIRON>

Note: Later in the installation the splenviron.sh

(splenviron.cmd) script will set the $SPLOUTPUT

(%SPLOUTPUT%) environment variable to point

to:<SPLDIROUT>/<SPLENVIRON>

Installation and Configuration Worksheets B-4

Oracle Utilities Work and Asset Management Installation Guide

Application Framework Installation and Configuration Worksheets

Customer

Name Used in

Menu Option

Usage

Install

Documentation

Value

Environment Name

<SPLENVIRON>

A descriptive name to be used as both a directory name under

the mount point <SPLDIR> and an environment descriptor.

This value typically identifies the purpose of the

environment. For example, DEV01 or CONV.

On installation a directory <SPLDIR>/<SPLENVIRON>

is created, under which the Oracle Utilities Application

Framework and Oracle Utilities Work and Asset Management

software resides.

When multiple environments are set up on the machine you

will typically have directories such as:

/ouaf/DEV01/....

/ouaf/CONV/....

Each of these contains a complete version of the Oracle

Utilities Application Framework and Oracle Utilities Work

and Asset Management.

Note: Later in the installation process, the splenviron.sh

(splenviron.cmd) script will set $SPLEBASE (

%SPLEBASE%) environment variable to point to

<SPLDIR>/<SPLENVIRON>

Web Application Server

<SPLWAS>

A web application server for the environment to be used. The

Type

following value must be selected:

Valid values:

WLS: WebLogic

WAS: WebSphere

WASND: WebSphere ND

Note: Not all web application servers are supported on all

platforms; refer to Supported Platforms section for details.

Installation Application

<WEB_

Denotes if the Application Viewer Web Module will be

Viewer Module

ISAPPVIEWER>

installed in the environment. When this value is set to false

the application viewer will not be accessible in the

environment.

Valid values:

true: Application Viewer module will be installed.

false: Application Viewer module will not be installed.

Default value: true

Note: When the value of false is selected, the Application

Viewer will only be installed at a later date by a complete

reinstall of the application.

Installation and Configuration Worksheets B-5

Oracle Utilities Work and Asset Management Installation Guide

Application Framework Installation and Configuration Worksheets

Customer

Name Used in

Menu Option

Usage

Install

Documentation

Value

Install Demo Generation

CERT_INSTALL_

You can install/uninstall later by executing the following

Cert Script

SCRIPT

script:

perl [INSTALL_PACKAGE_FOLDER]/installAR.plx

Valid values:

true: Demo Generation Cert Script will be installed.

false: Demo Generation Cert Script will not be installed.

Default value: true

Install Sample CM Source

CM_INSTALL_

You can install/uninstall later by executing the following

Code

SAMPLE

script:

perl [INSTALL_PACKAGE_FOLDER]/installAR.plx

Valid values:

true: Sample CM Source Code will be installed.

false: Sample CM Source Code will not be installed.

Default value: true

Environment Description

1. Environment Description

Environment Description:

Customer

Name Used in

Menu Option

Usage

Install

Documentation

Value

Environment Description

DESC

This is a free form text field to describe the purpose

of the environment.

Installation and Configuration Worksheets B-6

Oracle Utilities Work and Asset Management Installation Guide

Application Framework Installation and Configuration Worksheets

WebLogic Business Application Server Configuration

The WebLogic parameters below and in the worksheet are for a WebLogic installation.

2. Business Application Server Configuration

Business Server Host: <machine_name>

WebLogic Server Name: myserver

Business Server Application Name: SPLService

MPL Admin Port Number:

MPL Automatic startup: false

Customer

Name Used in

Menu Option

Usage

Install

Documentation

Value

Business Server Host

BSN_WLHOST

The host name on which the business application server resides.

Default value: <current server name>

WebLogic Server Name

BSN_WLS_

The name of the WebLogic server where the business application

SVRNAME

resides.

Default value: myserver

Note: If there is not a previously created WebLogic server, take

the default value of “myserver”.

Business Server

BSN_APP

The name of the business application server.

Application Name

Default value: SPLService

MPL Admin Port number

MPLADMINPORT

The port number for the Multi Purpose Listener (MPL) Admin

Server.

Example value: 6502

MPL Automatic Startup

MPLSTART

Automatically starts the MPL Listener whenever environment

starts.

Default value: false

Installation and Configuration Worksheets B-7

Oracle Utilities Work and Asset Management Installation Guide

Application Framework Installation and Configuration Worksheets

WebLogic Web Application Server Configuration

The WebLogic parameters below and in the worksheet are for a WebLogic installation.

3. Web Application Server Configuration

Web Server Host: <machine_name>

Weblogic SSL Port Number:

Weblogic Console Port Number:

WebLogic Additional Stop Arguments:

Web Context Root:

WebLogic JNDI User ID:

WebLogic JNDI Password:

WebLogic Admin System User ID:

WebLogic Admin System Password:

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

Customer

Name Used in

Menu Option

Usage

Install

Documentation

Value

Web Server Host

WEB_WLHOST

The host name on which the web application server resides.

Default value: <current server name>

Weblogic SSL Port

WEB_WLSSLPORT

The port number assigned to WebLogic Secure Sockets

Number

connection. This is the port number that is used for Secure

Sockets connecting to the WebLogic server.

For Production, additional actions are required. Do NOT run

Production with Demo certificates

Example value: 6501

Weblogic Console Port

WLS_ADMIN_PORT

The port number to access the WebLogic Console using https

Number

You will use this port when accessing the WebLogic Console

Example value: 6500

Weblogic Additional Stop

ADDITIONAL_STOP_

This value will be needed when running the WebLogic

Arguments

WEBLOGIC

Console using a different port number (e.g.)

-Dweblogic.security.TrustKeyStore=DemoTrust

-Dweblogic.security.TrustKeystoreType=CustomTrust

Web Context Root

WEB_CONTEXT_

A context root name that allows customers to run multiple

ROOT

instances of web application on the same server.

Default value: ouaf

WebLogic JNDI User ID

WEB_WLSYSUSER

The user ID the application uses to connect to the EJB

component through JNDI. This is the EJB container user ID.

Note: The required value for an initial installation is “system”.

This is a security value.

Installation and Configuration Worksheets B-8

Oracle Utilities Work and Asset Management Installation Guide

Application Framework Installation and Configuration Worksheets

Customer

Name Used in

Menu Option

Usage

Install

Documentation

Value

WebLogic JNDI Password

WEB_WLSYSPASS

The password the application uses to connect to the EJB

component through JNDI.

Note: The required value for an initial installation is

“ouafadmin”. This value will be saved in encrypted format.

This is a security value; it will be encrypted with the Oracle

Application Framework Encryption Algorithm.

WebLogic Admin System

WLS_WEB_

The user ID to log in to the Oracle WebLogic console and to

User ID

WLSYSUSER

administer Oracle WebLogic. The Oracle WebLogic startup

and stop script also utilizes this user ID

Note: The installation utility will prompt you to enter “Y” to

encrypt. For an initial installation, enter Y/y and specify the

required value “system”.

This is a security value; it will be encrypted with the Weblogic

Encryption Algorithm.

WebLogic Admin System

WLS_WEB_

The password to login to Oracle WebLogic console and to

Password

WLSYSPASS

administer Oracle WebLogic. The Oracle WebLogic startup

and stop script also utilize this password.

This is a security value; it will be encrypted with the Weblogic

Encryption Algorithm.

WebLogic Server Name

WEB_WLS_

The name of the WebLogic server where the web application

SVRNAME

resides.

Default value: myserver

Web Server Application

WEB_APP

The name of the web application server.

Name

Default value: SPLWeb

Note: For an initial installation, use the default value of

“SPLWeb”.

Deploy Using Archive Files

WEB_DEPLOY_EAR

When the value is “false” the web application will be deployed

in exploded directory format (no WAR/EAR files).

When the value is “true”, the web application will be deployed

in ear file format.

Note: The expanded application folders will always exist

under the application folder (<SPLEBASE>/splapp/

applications), regardless of the setting of this option.

Valid values:

true (Deploy EAR files)

false (Deploy expanded application folders

Default value: true

Installation and Configuration Worksheets B-9

Oracle Utilities Work and Asset Management Installation Guide

Application Framework Installation and Configuration Worksheets

Customer

Name Used in

Menu Option

Usage

Install

Documentation

Value

Deploy Application Viewer

WEB_DEPLOY_

When the value is “true” the application viewer will be

Module

APPVIEWER

deployed to the web server. When the value is “false”, the

application viewer will not be deployed to the web Server.

Note: With either value the application viewer module will still

be managed by the upgrade process.

Note: When the ‘Install Application Viewer module’ value is

set to false from the installation menu, you will not be able to

change this value to true to deploy the application viewer.

Valid values:

true: The application viewer module will be deployed to the

web server

false: The application viewer module will not be deployed to

the web server

Default value: true

Enable The Unsecured

WEB_ENABLE_

Enables the health check feature of the application

Health Check Service

HEALTHCHECK

MDB RunAs User ID

WEB_IWS_MDB_

The message drive Java Bean RunAs user.

RUNAS_USER

Super User Ids

WEB_IWS_SUPER_

The application super users.

USERS

Enter the super users separating them by commas.

Database Configuration

Note: If any of the database menu option items below are changed, the system displays the

following warning next to the actual option that has been changed:

This database option have been changed. Since the keystore and

encrypted data in the database must be compatible, you have two

options:

- load the compatible keystore into the environment;

Installation and Configuration Worksheets B-10

Oracle Utilities Work and Asset Management Installation Guide

Application Framework Installation and Configuration Worksheets

- keep the current keystore, re-enter any encrypted information

online through the application, and re-generate the database hashes.

Refer to the security guide for more information.

4. Database Configuration

Application Database User ID:

Application Database Password:

MPL Database User ID:

MPL Database Password:

XAI Database User ID:

XAI Database Password:

Batch Database User ID:

Batch Database Password:

Database Name

Database Server:

Database Port:

ONS Server Configuration:

Database Override Connection String:

Oracle Client Character Set NLS_LANG: AMERICAN_AMERICA.AL32UTF8

Customer

Name Used in

Menu Option

Usage

Install

Documentation

Value

Application Database User

DBUSER

The database user ID that has been configured on the

ID

database for the application server connection.

This is a security value.

Application Database

DBPASS

The database password that has been configured on the

Password

database for the application connection.

Note: This value will be saved in encrypted format.

This is a security value; it will be encrypted with the Oracle

Utilities Framework Encryption Algorithm.

MPL Database User ID

MPL_DBUSER

The database user ID that has been configured on the

database for the MPL server connection.

This is a security value.

MPL Database Password

MPL_DBPASS

The database password that has been configured on the

database for the MPL server connection.

Note: This value will be saved in encrypted format.

This is a security value; it will be encrypted with the Oracle

Utilities Application Framework Encryption Algorithm.

XAI Database User ID

XAI_DBUSER

The database user ID that has been configured on the

database for the XAI server connection.

This is a security value.

Installation and Configuration Worksheets B-11

Oracle Utilities Work and Asset Management Installation Guide

Application Framework Installation and Configuration Worksheets

Customer

Name Used in

Menu Option

Usage

Install

Documentation

Value

XAI Database Password

XAI_DBPASS

The database password that has been configured on the

database for the XAI server connection.

Note: This value will be saved in encrypted format.

This is a security value; it will be encrypted with the Oracle

Utilities Application Framework Encryption Algorithm.

Batch Database User ID

BATCH_DBUSER

The database user ID that has been configured on the

database for the batch connection.

This is a security value.

Batch Database Password

BATCH_DBPASS

The database password that has been configured on the

database for the batch connection.

Note: This value will be saved in encrypted format.

This is a security value; it will be encrypted with the Oracle

Utilities Application Framework Encryption Algorithm.

Database Name

DBNAME

The name of the database instance that the application will be

connecting to.

Database Server

DBSERVER

Host name of the server where database resides.

Database Port

DBPORT

Database port number on the database server used for

connecting to the database

ONS Server Configuration

ONSCONFIG

ONS Server Configuration is required for Oracle RAC FCF.

See the Server Administration Guide for more information.

This is an optional value.

Database Override

DB_OVERRIDE_

This connection string can be used to override the database

Connection String

CONNECTION

information entered above for RAC installation.

Set this string to override the standard database connection

string, as entered above.

See the Server Administration Guide for more information.

This is an optional value.

Oracle Client Character Set

NLS_LANG

The Oracle Database Character Set.

NLS_LANG

Select the Language and Territory that are in use in your

country.

Default value: AMERICAN_AMERICA.AL32UTF8

Installation and Configuration Worksheets B-12

Oracle Utilities Work and Asset Management Installation Guide

Application Framework Installation and Configuration Worksheets

General Configuration Options

Note: See the Oracle Utilities Work and Asset Management Server Administration Guide for additional details on this configuration.

5. General Configuration Options

Batch RMI Port:

RMI Port number for JMX Business:

RMI Port number for JMX Web:

JMX Enablement System User ID:

JMX Enablement System Password:

Batch Mode: CLUSTERED

Coherence Cluster Name:

Coherence Cluster Address:

Coherence Cluster Port:

Coherence Cluster Mode: dev

Customer

Name Used in

Menu Option

Usage

Install

Documentation

Value

Batch RMI Port

BATCH_RMI_PORT

Unique port used by the Batch RMI

Example value: 6540

RMI Port number for JMX

BSN_JMX_RMI_PORT_

Example value: 6550

Business

PERFORMANCE

Note: This is an optional value.

RMI Port number for JMX

WEB_JMX_RMI_PORT_PE

Example value: 6570

Web

RFORMANCE

Note: This is an optional value.

JMX Enablement System

BSN_JMX_SYSUSER

This is used to authenticate incoming JMX requests.

User ID

Populate if RMI Port numbers are set.

Note: This is an optional value.

JMX Enablement System

BSN_JMX_SYSPASS

This is used to authenticate incoming JMX requests.

Password

Populate if RMI Port numbers are set.

This is a security value; it will be encrypted with the

Oracle Utilities Application Framework Encryption

Algorithm.

Note: This is an optional value.

Batch Mode

BATCH_MODE

Valid values: CLUSTERED or DISTRIBUTED

Default value: CLUSTERED

Note: CLUSTERED is currently the only supported

mode for production environments.

Coherence Cluster Name

COHERENCE_

Unique name for the batch CLUSTER

CLUSTER_NAME

Note: Value is required when batch mode is

CLUSTERED.

Coherence Cluster Address

COHERENCE_

Unique multicast address.

CLUSTER_ADDRESS

Note: Value is required when batch mode is

CLUSTERED.

Installation and Configuration Worksheets B-13

Oracle Utilities Work and Asset Management Installation Guide

Application Framework Installation and Configuration Worksheets

Customer

Name Used in

Menu Option

Usage

Install

Documentation

Value

Coherence Cluster Port

COHERENCE_

Unique port for the batch CLUSTER

CLUSTER_PORT

Note: Value is required when batch mode is

CLUSTERED.

Coherence Cluster Mode

COHERENCE_

Valid values:

CLUSTER_MODE

dev (Development)

prod (Production)

Default value: dev

SSL Certificate Keystore (Weblogic Only)

Note: See the Oracle Utilities Work and Asset Management Security Guide for additional details on this configuration. 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.

5. SSL Certificate Keystore

Certificate Keystore Type: CUSTOM

Identify Keystore File:

Identify Keystore File Type: jks

Identify Keystore Password:

Identity Private Key Alias: ouaf_demo_cert

Trust Keystore File:

Trust Keystore File Type: jks

Trust Keystore Password:

Trust Private Key Alias: ouaf_demo_cert

Customer

Name Used in

Menu Option

Usage

Install

Documentation

Value

Certificate Keystore Type

CERT_KS

If you choose DEMO you need to execute the following

script at least once

perl [SPLEBASE]/bin/demo_gen_cert.plx

If you change DEFAULT/CUSTOM to DEMO you need

to have installed the demo_gen_cert.plx script, it is part of

the demo source in the installation package.

Default value: CUSTOM

Valid values: DEFAULT,DEMO,CUSTOM

The demo_gen_cert.plx script is available if you select the

‘Install Demo Generation Cert Script’ option during

installation. It automates the creation of the Weblogic

provided demo certificate using 1024 byte keys.

Installation and Configuration Worksheets B-14

Oracle Utilities Work and Asset Management Installation Guide

Application Framework Installation and Configuration Worksheets

Customer

Name Used in

Menu Option

Usage

Install

Documentation

Value

Identify Keystore Type

CERT_IDENT_KS_

Mandatory if the type is CUSTOM.

FILE

No need to populate if type is DEMO, it will use:

[SPLEBASE]/splapp/certs/ouaf_demo_ident.jks

Identify Keystore File Type

CERT_IDENT_KS_

Default value: jks

TYPE

Identify Keystore Password

CERT_IDENT_KS_

This is a security value; it will be encrypted with the

PWD

WebLogic Encryption Algorithm.

Identity Private Key Alias

CERT_IDENT_KS_

Default value: ouaf_demo_cert

ALIAS

Trust Keystore File

CERT_TRUST_KS_

Mandatory if the type is CUSTOM.

FILE

No need to populate if type is DEMO, it will use:

[SPLEBASE]/splapp/certs/ouaf_demo_trust.jks

Trust Keystore File Type

CERT_TRUST_KS_

Default value: jks

TYPE

Trust Keystore Password

CERT_TRUST_KS_

This is a security value; it will be encrypted with the

PWD

WebLogic Encryption Algorithm.

Trust Private Key Alias

CERT_TRUST_KS_

Default value: ouaf_demo_cert

ALIAS

Installation and Configuration Worksheets B-15

Oracle Utilities Work and Asset Management Installation Guide

Application Framework Installation and Configuration Worksheets

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 Environment Miscellaneous Configuration

50. Advanced Environment Miscellaneous Configuration

WebSphere Web Server SOAP Port Number:

WebSphere Business Server SOAP Port Number:

WebSphere Profile Name Home Directory:

Online JVM Batch Server Enabled: false

Online JVM Batch Number of Threads: 5

Online JVM Batch Scheduler Daemon Enabled: false

Enable Batch Edit Functionality: false

Enable Web Services Functionality: false

Web Services WAR file name: Webservices

GIS Service Running on the same Web Server: true

GIS Service URL:

GIS WebLogic System User ID:

GIS WebLogic System Password:

Online Display Software Home:

Customer

Name Used in

Menu Option

Usage

Value

Documentation

Install

WebSphere Web Server

WAS_WEB_SOAP_

WebSphere Web Server SOAP Port Number

SOAP Port Number

PORT

This is the SOAP port used for WebSphere Basic when

executing wsadmin.sh commands.

Note: This value will only appear for WebSphere Basic and

WebSphere ND

WebSphere Business

WAS_BSN_SOAP_

WebSphere Business Server SOAP Port Number. This is

Server SOAP Port Number

PORT

the SOAP port used for WebSphere Basic when executing

wsadmin.sh commands.

Note: This value will only appear for WebSphere Basic and

WebSphere ND

WebSphere Profile Name

WAS_PROFILE_

The profile home will be used when tracking log files, under

Home Directory

NAME_HOME

Websphere home.

Note: This value will only appear for

WebSphere Basic and WebSphere ND

WebSphere Deployment

WASND_DMGR_

WebSphere Deployment Manager Host name, this value is

Manager Host Name

HOS T

used for WebSphere ND, when connecting to the

WebSphere Deployment Manager.

Note: This value will only appear for WebSphere ND.

Installation and Configuration Worksheets B-16

Oracle Utilities Work and Asset Management Installation Guide

Application Framework Installation and Configuration Worksheets

Customer

Name Used in

Menu Option

Usage

Value

Documentation

Install

Online JVM Batch Server

BATCHENABLED

When starting a web application server JVM, this property

Enabled

can be set to “true” to allow the on-line application server

to also act as a batch worker in the grid.

Default value: false

Note: This functionality should only be used in low volume

environments.

Online JVM Batch

BATCHTHREADS

The maximum number of batch processing threads to be

Number of Threads

executed within a worker JVM when no explicit Distributed

Thread Pool is specified. The “DEFAULT” distributed

thread pool is used by the batch-scheduling daemon when it

initiates processing on batch jobs (typically added via the

online system) where no thread pool is specified).

Default value: 5

Note: This will be only used and activated when

BATCHENABLED is set to true.

Online JVM Batch

BATCHDAEMON

In a distributed batch environment, this property can be set

Scheduler Daemon

to “true” to allow a worker JVM to host the batch

Enabled

scheduling daemon. The daemon accepts online batch

submissions requests and automatically submits the work

for them.

Valid values: true, false

Default value: false

Note: This will be only used and activated when

BATCHENABLED is set to true.

Enable Batch Edit

BATCHEDIT_

Enable Batch Edit Funtionality

Funtionality

ENABLED

If enabled, use the bedit.sh|cmd script in order to configure

the batch

Valid values: true, false

Default value: false

Enable Web Services

WEBSERVICES_

If enabled, execute the following commands in oder to

Functionality

ENABLED

allow the application to re-deploy the Webservices without

prompting for the user and password:

- Add weblogic.jar to the CLASSPATH

- Execute: java weblogic.Admin -username [USER NAME]

-password [PASSWORD] STOREUSERCONFIG -

userconfigfile [SPLEBASE]/etc/.wlsuserconfig -userkeyfile

[SPLEBASE]/etc/.wlsuserkey

Valid values: true, false

Default value: false

Installation and Configuration Worksheets B-17

Oracle Utilities Work and Asset Management Installation Guide

Application Framework Installation and Configuration Worksheets

Customer

Name Used in

Menu Option

Usage

Value

Documentation

Install

Web Services WAR File

IWSWAR

Web Services WAR File Name

Name

Do not include the .war suffix

Default Value: Webservices

GIS Service Running on

GIS

Geographical information (GEOCODING) - GIS Service

the same Web Server

running on the same web application server

Valid values: true, false

This value is optional. This value will only appear for

WebLogic.

GIS Service URL

GIS_URL

This is the URL of the external web server.

Note: This value will be only be used when GIS is set to

true.

This value is optional. This value will only appear for

WebLogic.

GIS WebLogic System

GIS_WLSYSUSER

GIS WebLogic System User ID

User ID

Note: This value will be only be used when GIS is set to

true.

This value is optional. This value will only appear for

WebLogic.

GIS WebLogic System

GIS_WLSYSPASS

GIS WebLogic System Password.

Password

Note: This value will be only be used when GIS is set to

true.

This is a security value; it will be encrypted with the Oracle

Utilities Application Framework Encryption Algorithm.

This value will only appear for WebLogic.

Online Display Software

ONLINE_DISPLAY_HO

The location of the Online Display Software installation

Home

ME

directory.

This value is optional.

Installation and Configuration Worksheets B-18

Oracle Utilities Work and Asset Management Installation Guide

Application Framework Installation and Configuration Worksheets

Advanced Environment Memory Configuration

51. Advanced Environment Memory Configuration

Web Application Java Initial Heap Size: 2048

Web Application Java Max Heap Size: 2048

Web Application Java Max Perm Size: 1024

Web Application Additional Options:

Global JVM Arguments:

Ant Min Heap Size: 200

Ant Max Heap Size: 800

Ant Additional Options:

Thread Pool Worker Java Min Heap Size: 512

Thread Pool Worker Java Max Heap Size: 1024

Thread Pool Worker Java Max Perm Size: 512

Thread Pool Worker Additional Options: Additional Runtime

Classpath:

Customer

Name Used in

Menu Option

Usage

Install

Documentation

Value

Web Application Java

WEB_MEMORY_

Initial heap size for the application server.

Initial Heap Size

OPT_MIN

Default value: 1024

Note: For WebLogic installation only.

Web Application Java Max

WEB_MEMORY_

Maximum heap size for the application server.

Heap Size

OPT_MAX

Default value: 1024

Note: For WebLogic installation only.

Web Application Java Max

WEB_MEMORY_OPT_

Maximum Perm Size for the application server.

Perm Size

MAXPERMSIZE

Default value: MB (Linux, Solaris)

MB (Windows)

Note: For WebLogic installation only.

Web Application

WEB_ADDITIONAL_O

Additional options that will be passed in to the web

Additional Options

PT

application server JVM.

-

Djavax.xml.soap.MessageFactory=com.sun.xml.internal.mess

aging.saaj.soap.ver1_1.SOAPMessageFactory1_1Impl

Note: This parameter is required if Enable Webservices is set

to true.

Global JVM Arguments

GLOBAL_JVMARGS

JVM arguments that are passed to all Java server processes

such as Weblogic Server, Threadpoolworkers and jobs.

Installation and Configuration Worksheets B-19

Oracle Utilities Work and Asset Management Installation Guide

Application Framework Installation and Configuration Worksheets

Customer

Name Used in

Menu Option

Usage

Install

Documentation

Value

Ant Min Heap Size

ANT_OPT_MIN

Minimum Heap Size passed to ANT JVM.

Default value: 200

Ant Max Heap Size

ANT_OPT_MAX

Maximum Heap Size passed to ANT JVM.

Default value: 800

Ant Additional Options

ANT_ADDITIONAL_O

Additional options that are passed into the ANT JVM.

PT

Thread Pool Worker Java

BATCH_MEMORY_

Minimum heap size passed to the Thread Pool Worker.

Min Heap Size

OPT_MIN

Default value: 512

Thread Pool Worker Java

BATCH_MEMORY_

Maximum heap size passed to the Thread Pool Worker.

Max Heap Size

OPT_MAX

Default value: 1024

Thread Pool Worker Java

BATCH_MEMORY_

Maximum perm size passed to the Thread Pool Worker

Max Perm Size

OPT_MAXPERMSIZE

Default value: 768

Thread Pool Worker

BATCH_MEMORY_

Additional Memory Options passed into the Thread Pool

Additional Options

ADDITIONAL_OPT

Worker. This is an optional free form field.

For non-AIX only.

Additional Runtime

ADDITIONAL_

Additional Classpath Options passed in when starting the

Classpath

RUNTIME_

WebLogic JVM

CLASSPATH

Note: For WebLogic installation only.

$WL_HOME/../oracle_common/modules/

com.sun.xml.messaging.saaj.saaj-impl_1.3.jar

Note: This parameter is required if Enable Webservices is set

to true.

Installation and Configuration Worksheets B-20

Oracle Utilities Work and Asset Management Installation Guide

Application Framework Installation and Configuration Worksheets

Advanced Web Application Configuration

52. Advanced Web Application Configuration

Web Application Cache Settings: off

Web Server Port Number:

WebLogic Overload Protection: system-exit

Domain Home Location:

Batch Cluster URL:

Strip HTML Comments: false

Authentication Login Page Type: FORM

Web Form Login Page: /loginPage.jsp

Web Form Login Error Page: /formLoginError.jsp

Application Viewer Form Login Page: /loginPage.jsp

Application Viewer Form Login Error Page: /formLoginError.jsp

Help Form Login Page: /loginPage.jsp

Help Form Login Error Page: /formLoginError.jsp

Web Security Role: cisusers

Web Principal Name: cisusers

Application Viewer Security Role: cisusers

Application Viewer Principal Name: cisusers

This is a development environment: false

Preload All Pages on Startup: false

Maximum Age of a Cache Entry for Text: 28800

Maximum Age of a Cache Entry for Images: 28800

JSP Recompile Interval (s): 43200

Customer

Name Used in 

Menu Option

Usage

Install

Documentation

Value

Web Application Cache

WEB_L2_CACHE_

Default value: off

Settings

MODE

Valid values: off

read_write

read_only

Web Server Port Number

WEB_WLPORT

The port number assigned to WebLogic connection. Set this

port if the environment is not configured as SSL.

Note: For WebLogic installation only. This value is optional.

Example Value: 6500

WebLogic Overload

WLS_OVERRIDE_

The overload protection allows for a Weblogic server to be

Protection

PROTECT

“stopped / exited” when there is an out of memory

exception

Valid values:

system-exit (Exit the server process)

no-action (Ignore take no action)

Default value: system-exit

Note: For WebLogic installation only.

Installation and Configuration Worksheets B-21

Oracle Utilities Work and Asset Management Installation Guide

Application Framework Installation and Configuration Worksheets

Customer

Name Used in 

Menu Option

Usage

Install

Documentation

Value

Domain Home Location

WLS_DOMAIN_

The Weblogic Domain Home location, when this parameter

HOME

is populated you will need to use the native Weblogic tools

for maintenance (starting, stopping, deployment, and

undeployment).

Note: For WebLogic installation only

This value is optional

Batch Cluster URL

WEB_BATCH_

Example: service:jmx:rmi:///jndi/rmi://[host]:[TPW JMX

CLUSTER_URL

port]/oracle/ouaf/batchConnector

Strip HTML Comments:

STRIP_HTML_

Stripping HTML (and JavaScript) comments will increase

false

COMMENTS

the security of the system.

Default value: false

Valid values: true, false

Authentication Login Page

WEB_WLAUTHMETHOD

Specifies which authentication mode should be used. To

Type

switch off OUAF Login Page enter: BASIC

Valid values: FORM, BASIC

Default value: FORM

Web Form Login Page

WEB_FORM_

Specify the jsp file used to login into the application.

LOGIN_PAGE

Default value: /loginPage.jsp

Web Form Login Error

WEB_FORM_LOGIN

Specify the jsp file used when there is an error when logging

Page

_ERROR_PAGE

into the application.

Default value: /formLoginError.jsp

Application Viewer Form

WEB_APPVIEWER_

Specify the jsp file used to login into the application viewer

Login Page

FORM_LOGIN_

application.

PAGE

Default value: /loginPage.jsp

Application Viewer Form

WEB_APPVIEWER_

Specify the jsp file used when there is an error when logging

Login Error Page

FORM_LOGIN_

into the application viwer application.

ERROR_PAGE

Help Form Login Page

WEB_HELP_FORM_

Specify the jsp file used to login into the help application.

LOGIN_PAGE

Default value: /loginPage.jsp

Help Form Login Error

WEB_HELP_FORM_

Specify the jsp file used when there is an error when logging

Page

LOGIN_ERROR_

into the help application.

PAGE

Default value: /formLoginError.jsp

Web Security Role

WEB_PRINCIPAL_

Specify the name of the security role.

NAME

Default value: cisusers

Installation and Configuration Worksheets B-22

Oracle Utilities Work and Asset Management Installation Guide

Application Framework Installation and Configuration Worksheets

Customer

Name Used in 

Menu Option

Usage

Install

Documentation

Value

Web Principal Name

WEB_PRINCIPAL_

Specify the name of a principal that is defined in the security

NAME

realm.

Default value: cisusers

Application Viewer Security

WEB_APPVIEWER_

Specify the name of the security role.

Role

ROLE_NAME

Default value: cisusers

Application Viewer

WEB_APPVIEWER_

Specify the name of a principal that is defined in the security

Principal Name

PRINCIPAL_NAME

realm.

Default value: cisusers

This is a development

WEB_ISDEVELOPMENT

If the value is “true”, the web application may be used for

environment

application development, which will trigger certain

generation processes. If the value is “false” the environment

will be used as a runtime environment.

When you choose “true” (development environment) the

startup preload pages will be disabled, and the application

security will be less strict. This value also controls the

amount of logging information written to the application

log files.

Valid values: true, false

Default value: false

Preload All Pages on

WEB_PRELOADALL

This controls if the pages should be pre-loaded during the

Startup

startup of the application or not.

Valid values: true, false

Default value: false

Maximum Age of a Cache

WEB_MAXAGE

Default value: 28800

Entry for Text

Maximum Age of a Cache

WEB_MAXAGEI

Default value: 28800

Entry for Images

JSP Recompile Interval (s)

WEB_wlpageCheckSeconds

Default value: 43200

Note: For Weblogic Installation only.

Installation and Configuration Worksheets B-23

Oracle Utilities Work and Asset Management Installation Guide

Application Framework Installation and Configuration Worksheets

OIM Configuration Settings

53. OIM Configuration Settings

SPML SOAP Trace Setting: false

SPML IDM Schema Name: F1-IDMUser

SPML OIM Name Space: http://xmlns.oracle.com/OIM/provisioning

SPML OIM Enclosing Element: sOAPElement

Customer

Name Used in

Menu Option

Usage

Install

Documentation

Value

SPML SOAP Trace Setting

OIM_SPML_SOAP_

Name of Oracle Identity Manager library for debug

DEBUG_SETTING

Default value: false

Valid values: true, false

SPML IDM Schema Name

OIM_SPML_UBER_

Name of Oracle Identity Manager library for schema

SCHEMA_NAME

Defautlt value: F1-IDMUser

SPML OIM Name Space

OIM_SPML_NAME_

Default Namespace for Oracle Identity Manager

SPACE

integration

Default value: http://xmlns.oracle.com/OIM/

provisioning

SPML OIM Enclosing

OIM_SPML_SOAP_

Default top level SOAP Element name for Oracle Identity

Element

ELEMENT

Manager integration

Default value: sOAPElement

Installation and Configuration Worksheets B-24

Oracle Utilities Work and Asset Management Installation Guide

Appendix C

Application Framework Prerequisite Patches

Oracle Utilities Application Framework patches must be installed prior to installing Oracle

Utilities Work and Asset Management. The patches listed below are available as a convenience

rollup inside the ‘Oracle Utilities Application Framework v4.3.0.1.0 Single Fix Prerequisite Rollup

for Oracle Utilities Work and Asset Management v2.1.1.0.0.zip’ folders.

21836388

20119867

21196697

21647369

21675510

21772779

21793546

21792146

21781526

21793436

21808140

21820764

21834912

21908287

21629815

21647035

21779770

21373651

22013062

21914615

21748264

22172424

21798182

22103984

22104158

22103136

22102884

22260744

22262755

Application Framework Prerequisite Patches C-1

Oracle Utilities Work and Asset Management Installation Guide

Appendix D

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:

Common Maintenance Activities D-1

Oracle Utilities Work and Asset Management Installation Guide

Common Maintenance Activities

$SPLEBASE/bin/threadpoolworker.sh -d Y -p DEFAULT=20 L2OFF=1 -l2

OFF

Windows:

%SPLEBASE%\bin\threadpoolworker.cmd -d Y -p DEFAULT=20 L2OFF=1 -l2

OFF

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

Common Maintenance Activities D-2

Oracle Utilities Work and Asset Management Installation Guide

Document Outline

- Installation Guide

- Contents

- Preface

- Related Documents

- Conventions

- Acronyms

- Overview

- Product Overview

- Installation Overview

- Installation Types

- Initial Installation

- Demo Installation

- Package Contents

- Documentation

- Installation Packages

- Readiness Checklist

- Supported Platforms and Hardware Requirements

- Operating Systems and Application Servers

- Hardware Requirements

- Application Server Memory Requirements

- Additional Notes on Supported Platforms

- Support for Software Patches and Upgrades

- Planning the Installation

- Before You Install

- Prerequisite Software List

- Prerequisite Software for Application Server

- Web Browser Requirements

- Installing PreRequisite Software

- AIX 7.1 TL01 Application Server

- Oracle Linux 6.x or 7.x or Red Hat Linux 6.x or 7.x Application Server

- Oracle Solaris 11 Application Server

- Windows Server 2012 Application Server

- Installing Oracle Utilities Work and Asset Management - Initial Installation

- Before You Install

- Initial Installation Procedure

- Database Component Installation

- Application Components Installation

- After the Installation

- Operating the Application

- Installing Oracle Utilities Work and Asset Management - Demo Installation

- Before You Install

- Demo Installation Procedure

- Database Component Installation

- Application Components Installation

- After the Installation

- Operating the Application

- Additional Tasks

- WebLogic Production Server Considerations

- Configuring Identity and Trust

- Building Javadoc Indexes

- Configuring the Environment for Batch Processing

- Customizing the Logo

- Deploying Inbound WebServices (IWS)

- Installing Service Packs and Patches

- Installing Optional Products

- Oracle BI Publisher

- Supported BI Publisher Versions

- About Oracle BI Publisher Enterprise

- Configuring the System to Enable Reports

- Sample Reports Supplied with the Product

- Esri ArcGIS Server

- Installing the Esri ArcGIS Server

- Verifying Pre-Requisites

- Importing Feature Classes to Database

- Deploying Map Packages

- Installation Menu Functionality Overview

- Installation Menu Functionality Details

- Installation and Configuration Worksheets

- Application Framework Installation and Configuration Worksheets

- Environment ID, Roles, Third Party Software Configuration

- Keystore Options

- Environment Installation Options

- Environment Description

- WebLogic Business Application Server Configuration

- WebLogic Web Application Server Configuration

- Database Configuration

- General Configuration Options

- SSL Certificate Keystore (Weblogic Only)

- Advanced Menu Options

- Advanced Environment Memory Configuration

- Advanced Web Application Configuration

- OIM Configuration Settings

- Application Framework Prerequisite Patches

- Common Maintenance Activities

Table of Contents

Preface.............................................................................................

Acronyms. . . . . . . . . . . . ....................................................................

Chapter 1

Product Overview. . . . . ..........................................................................

Installation Overview. . ...........................................................................

Installation Types. . . . . . ......................................................................

Documentation. . . . . . . . . . . . . .............................................................

Readiness Checklist . . . . ........................................................................

Chapter 2

Operating Systems and Application Servers...........................................................

Application Server Memory Requirements . . . . . . . . . . . .......................................

Support for Software Patches and Upgrades ..........................................................

Chapter 3

Before You Install . . . . . .......................................................................

Oracle Linux 6.x or 7.x or Red Hat Linux 6.x or 7.x Application Server..............................

Oracle

Windows Server 2012 Application Server .............................................................

Chapter 4

Initial Installation Procedure. . . . . . . . . . ..................................................

After the Installation .............................................................................

Chapter 5

Before You Install .................................................................................

Operating the Application...........................................................................

Chapter 6

WebLogic Production Server Considerations...........................................................

Configuring the Environment for Batch Processing ...................................................

Installing Service Packs and Patches................................................................

Chapter 7

Configuring the System to Enable Reports............................................................

Sample Reports Supplied with the Product ...........................................................

Appendix A

Appendix B

Keystore Options ...................................................................................

Environment Installation Options ...................................................................

Environment Description.............................................................................

WebLogic Business Application Server Configuration .................................................

WebLogic Web Application Server Configuration . . . . . . . . . . ..................................

Database Configuration .............................................................................

General Configuration Options. . . . . . . . . . . . ...............................................

SSL Certificate Keystore (Weblogic Only)............................................................

Advanced Menu Options...............................................................................

Advanced Environment Memory Configuration...........................................................

Advanced Web Application Configuration. . . ........................................................

OIM Configuration Settings..........................................................................

Appendix C

Appendix D

Installing Oracle Utilities Application Framework v4.3.0.1.0 Single Fix PreRequisite

Installing the Oracle Utilities Work and Asset Management Application Component

Setting Permissions for the cistab file in UNIX

Performing Post-Installation Tasks