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:

• Oracle Linux Application Server

• Oracle Solaris Application Server

• Windows Server 2012 R2 Application Server

Oracle Linux Application Server

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

• Web/Application Server Tier

• Oracle Java Development Kit v8.0.x.x Update 291, 64-bit

• Oracle Database Client 19c - Runtime Option

• Hibernate 4.1.0

• Oracle WebLogic Server 12c Release 2 (12.2.1.4) 64-bit

Web/Application Server Tier

LINUX Administrator User ID

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

Description	Default Value	Customer Defined Value
Oracle Utilities Work and Asset Management Administrator User ID	cissys
Oracle Utilities Work and Asset Management User Group	cisusr

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

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

By default, the cissys user ID 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 exist to secure a system. In this application all files will be created with the minimum permissions required to ensure that group-readable, group-writable and group-executable files will have the correct user groups and to restrict the permissions available to legitimate users. In this way, a low privileged end user cannot directly edit configuration files and thereby bypass application security controls.

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

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

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.

You must use the same user for starting and stopping a process. For example, if cissys is used to start the application server, the use cissys to stop it as well.

Oracle Java Development Kit v8.0.x.x Update 291, 64-bit

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

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

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

For the user ID 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.

Oracle Database Client 19c - Runtime Option

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

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

Hibernate 4.1.0

You must install Hibernate before installing the product.

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

1. Create a Hibernate jar external depot:

export HIBERNATE_JAR_DIR=<Hibernate 3rd party jars depot>

2. Download the hibernate-release-4.1.0.Final.zip file from https://sourceforge.net/projects/hibernate/files/hibernate4/.

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

4. Extract the contents of the archive file:

unzip -q hibernate-release-4.1.0.Final.zip

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

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

cp hibernate-release-4.1.0.Final/lib/optional/ehcache/hibernate-ehcache-4.1.0.Final.jar $HIBERNATE_JAR_DIR

cp hibernate-release-4.1.0.Final/lib/required/hibernate-commons-annotations-4.0.1.Final.jar $HIBERNATE_JAR_DIR

cp hibernate-release-4.1.0.Final/lib/required/hibernate-core-4.1.0.Final.jar $HIBERNATE_JAR_DIR

cp hibernate-release-4.1.0.Final/lib/required/hibernate-jpa-2.0-api-1.0.1.Final.jar $HIBERNATE_JAR_DIR

cp hibernate-release-4.1.0.Final/lib/required/javassist-3.15.0-GA.jar $HIBERNATE_JAR_DIR

cp hibernate-release-4.1.0.Final/lib/required/jboss-transaction-api_1.1_spec-1.0.0.Final.jar $HIBERNATE_JAR_DIR

cp hibernate-release-4.1.0.Final/lib/required/jboss-logging-3.3.0.Final.jar $HIBERNATE_JAR_DIR

cp hibernate-release-4.1.0.Final/lib/required/ehcache-core-2.5.2.jar $HIBERNATE_JAR_DIR

Oracle WebLogic Server 12c Release 2 (12.2.1.4) 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 SDK 1.8 (as documented above) before installing WebLogic.

• Download and install WebLogic Server ((Fusion Middleware Infrastructure) 12c Release 2 (12.2.1.4) 64-bit.

Oracle Solaris Application Server

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

• Web/Application Server Tier

• Oracle Solaris JDK 1.8.0_281+

• Oracle Database Client 19c - Runtime Option

• Install the /usr/ucb/ps Command

• Hibernate 4.1.0

• Oracle WebLogic Server 12c (Release 12.2.1.4) 64-bit

Web/Application Server Tier

UNIX Administrator User ID

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

Description	Default Value	Customer Defined Value
Oracle Utilities Work and Asset Management Administrator User ID	cissys
Oracle Utilities Work and Asset Management User Group	cisusr

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

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

By default, the cissys user ID 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 make sure 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.

You must use the same user for starting and stopping a process. For example: If cissys is used to start the application server, use cissys to stop it as well.

Oracle Solaris JDK 1.8.0_281+

This software is only required for Oracle WebLogic installations. At the time of release, the Oracle Solaris JDK 1.8.0_281+ used in the test cycle was downloaded from:

http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html

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

For the user ID 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.

Oracle Database Client 19c - Runtime Option

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.

Install the /usr/ucb/ps Command

Installing the /usr/ucp/ps command is a prerequisite for Solaris platforms that are below version 11.4. It is necessary to execute the following command successfully:

spl.sh -b stop (stop the Threadpool Worker)