Pre-Installation Tasks
Hardware and Software Version Prerequisites
Supported Platforms and Hardware Requirements contains all of the available platforms that are required with this release of the product.
Database Installation
Verify that the database has been installed and is operational. See Oracle Utilities Digital Asset Management Database Administrator’s Guide for more information.
Installation Prerequisites
Installing Application Server Prerequisite Software describes all preparations that need to be done on the server prior to installing the application server. Please read carefully the server setup requirements and make sure that all prerequisite software is installed and that all required environment variables are set. Correct server setup and proper environment variable settings are an essential prerequisite for successful environment installation.
System Architecture Overview
Oracle Utilities Application Framework V4.5.0.1.0 is a decoupled system architecture involving a business service application tier and a web application tier. Typically both will run on the same server, but the design does allow each tier to be installed on separate servers.
The design implements a stateless session bean (EJB technology, under Java EE 7), to provide remote access to service invocations. The root web app and XAI web apps can be configured to access service processing locally (as in previous versions), or to make a remote EJB call to perform the service request. In the latter case, the served containers, effectively, run as very thin servlet wrappers around the remote call.
For all supported application servers except for WebLogic expanded configuration (SDK environment), the deployment is in the form of two Enterprise Archive (ear) Files: SPLService.ear and SPLWeb.ear. Web Archive (war) files are created during the installation process but are not deployed.
Copying and Decompressing Install Media
To copy and decompress the Oracle Utilities Digital Asset Management installation media:
1. Download Oracle Utilities Digital Asset Management V2.0.0.0.0 from Oracle Software Delivery Cloud (eDelivery) and extract the following:
Oracle Utilities Application Framework V4.5.0.1.0 Application Installation Media
Oracle Utilities Application Framework V4.5.0.1.0 Single Fix Prerequisite Rollup for Oracle Utilities Digital Asset Management V2.0.0.0.0 (if there is any)
Oracle Utilities Customer Care and Billing V2.9.0.1.0 for Multiplatform
Oracle Utilities Customer Care and Billing V2.9.0.1.0 Single Fix Prerequisite Rollup for Oracle Utilities Digital Asset Management V2.0.0.0.0 (if there is any)
Oracle Utilities Meter Data Management V2.5.0.1.0 Multiplatform
Oracle Utilities Work and Asset Management V2.4.0.1.0 Multiplatform
Oracle Utilities Digital Asset Management V2.0.0.0.0 for Multiplatform
Oracle Utilities Digital Asset Management V2.0.0.0.0 Single Fix Prerequisite Rollup for Oracle Utilities Digital Asset Management V2.0.0.0.0 (if there is any)
2. Copy the following Oracle Utilities Digital Asset Management files to your local machine:
FW-V4.5.0.1.0-Multiplatform
C2M-V2.9.0.1.0-FW-PREREQ-MultiPlatform (if there is any)
CCB-V2.9.0.1.0-Multiplatform
CCB-V2.9.0.1.0-Rollup-MultiPlatform (if there is any)
MDM-V2.5.0.1.0-Multiplatform
Oracle Utilities Work and Asset Management V2.4.0.1.0 Multiplatform
C2M-V2.9.0.1.0-Multiplatform
C2M-V2.9.0.1.0-Rollup-MultiPlatform (if there is any)
The Oracle Utilities Application Framework V4.5.0.1.0 installation file is delivered in jar format for both UNIX and Windows platforms.
If you are planning to install multiple Oracle Utilities Application Framework V4.5.0.1.0 environments operated by different Oracle Utilities administrator user IDs, you must complete each of the following installation steps for each administrator user ID.
To copy and decompress the install media:
1. Login to the application server host with the Oracle Utilities Application Framework administrator user ID.
2. Download the Oracle Utilities Application Framework V4.5.0.1.0 Multiplatform from Oracle Software Delivery Cloud.
3. Create a temporary directory such as c:\ouaf\temp or /ouaf/temp. (Referred to below as <TEMPDIR>.)
Note: This directory must be located outside any current or other working Oracle Utilities application environment. All files that are placed in this directory as a part of the installation can be deleted after completing a successful installation.
4. Copy the file FW-V4.5.0.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.5.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:
A sub-directory named “FW-V4.5.0.1.0” is created. It contains the installation software for the Oracle Utilities framework application server.
Set 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.5.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 Application 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 Application 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.