Installing Prerequisite Software
This section describes the software that needs to be installed for each of the supported operating system and application server combinations. The sections for this chapter are:
AIX 7.2 TL5+ Application Server
This section describes the software requirements for operating the application using the AIX application server.
Supported Application Servers
AIX 7.2 TL5 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:
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 user ID is the only one given access to the installed files.
1. Create a group ‘cisusr’ (user group).
2. Create a user ‘cissys’. Primary group cisusr. Set the primary shell for the cissys user to Korn Shell.
The shell scripts use the “>” to overwrite shell functionality. Your operating system may be configured to not allow this functionality by default in the users shell.
To avoid file access permission problems when executing scripts, consider placing the following command into cissys profile script:
set +o noclobber
Security Configuration
Various options exist to secure a system. In this application all files will be created with the minimum permissions required to ensure that group-readable, group-writable, and group-executable files will have the correct user groups and to restrict the permissions available to legitimate users. In this way, a low privileged end user cannot directly edit configuration files and thereby bypass application security controls.
The following users and group categories must be defined to implement this security. For demonstration purposes the following users and groups will be used. These users must be created according to industry standards (including password policies). All users should be created with a default umask of 022 to ensure files created during normal operation have the correct permissions.
Please replace these users and groups for your installation defaults:
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 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.
IBM Java Software Development Kit v8.0 SR15 64-bit, IBM SDK, Java Technology Edition v8.0.x.x
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:
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 user ID (cissys), make sure 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 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>
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 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 (as documented above) before installing WebLogic.
• Download and install WebLogic Server 12.2.1.4.
Note: With Oracle Utilities Application Framework V4.5.0.1.0 a WebLogic native installation is required. Refer to the
Oracle WebLogic 12.2.1.x Configuration Guide for Oracle Utilities Application Framework (Doc ID 2413918.1) document on
My Oracle Support.
Oracle Service Bus 12.2.1.4
Oracle Service Bus is required for implementations that plan to use middleware implementations of adapters or the generic adapter to process meter reading or device event data.
Oracle Service Bus is NOT required with native implementations of Smart Grid Gateway adapters. See Smart Grid Gateway Implementations in the Oracle Utilities Meter Solution Administrative User Guide for more information.
Note: Oracle Service Bus 12.2.1.4 requires Oracle WebLogic Server 12.2.1.4.
Oracle Service Bus must be installed prior to the installation of Oracle Utilities Smart Grid Gateway. Oracle Service Bus can be downloaded from the
Oracle Fusion Middleware Software Downloads portal.
Oracle SOA Suite 12.2.1.4
Oracle SOA Suite, specifically BPEL Process Manager, is required for implementations that plan to use middleware implementations of adapters or the generic adapter to implement two-way communications for processing meter commands.
SOA Suite is NOT required with native implementations of Smart Grid Gateway adapters. See Smart Grid Gateway Implementations in the Oracle Utilities Meter Solution Administrative User Guide for more information.
Note: Oracle SOA Suite 12.2.1.4 requires Oracle WebLogic Server 12.2.1.4.
Oracle SOA Suite must be installed prior to the installation of Oracle Utilities Smart Grid Gateway. Oracle SOA Suite can be downloaded from the
Oracle Fusion Middleware Software Downloads portal.
Oracle Linux 8.x or Red Hat Linux 8.x Operating System
This section describes the software requirements for operating the application using the Oracle Linux or Red Hat Linux application server.
Supported Application Servers
Oracle Linux or Red Hat Enterprise Linux Operating System Running on x86_64 64-bit Architecture
UNIX Administrator User ID
The following user groups and accounts have to be created to install and administer the application:
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 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.
The shell scripts use the “>” to overwrite shell functionality. Your operating system may be configured to not allow this functionality by default in the users shell.
To avoid file access permission problems when executing scripts, consider placing the following command into cissys profile script:
set +o noclobber
Security Configuration
Various options exist to secure a system. In this application all files will be created with the minimum permissions required to ensure that group-readable, group-writable, and group-executable files will have the correct user groups and to restrict the permissions available to legitimate users. In this way, a low privileged end user cannot directly edit configuration files and thereby bypass application security controls.
The following users and group categories must be defined to implement this security. For demonstration purposes the following users and groups will be used. These users must be created according to industry standards (including password policies). All users should be created with a default umask of 022 to ensure files created during normal operation have the correct permissions.
Please replace these users and groups for your installation defaults:
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 an install user, these components must belong to cissys.
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.
Oracle Java Development Kit v8.0.x.x Update 291, 64-bit
At time of release, Oracle Java packages could be obtained from:
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.
Hibernate 4.1.0 FINAL
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>
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 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 (as documented above) before installing WebLogic.
• Download and install WebLogic Server 12.2.1.4.
Note: With Oracle Utilities Application Framework V4.5.0.1.0 a WebLogic native installation is required. Refer to the
Oracle WebLogic 12.2.1.x Configuration Guide for Oracle Utilities Application Framework (Doc ID 2413918.1) document on
My Oracle Support.
Oracle Service Bus 12.2.1.4
Oracle Service Bus is required for implementations that plan to use middleware implementations of adapters or the generic adapter to process meter reading or device event data.
Oracle Service Bus is NOT required with native implementations of Smart Grid Gateway adapters. See Smart Grid Gateway Implementations in the Oracle Utilities Meter Solution Administrative User Guide for more information.
Note: Oracle Service Bus 12.2.1.4 requires Oracle WebLogic Server 12.2.1.4.
Oracle Service Bus must be installed prior to the installation of Oracle Utilities Smart Grid Gateway. Oracle Service Bus can be downloaded from the
Oracle Fusion Middleware Software Downloads portal.
Oracle SOA Suite 12.2.1.4
Oracle SOA Suite, specifically BPEL Process Manager, is required for implementations that plan to use middleware implementations of adapters or the generic adapter to implement two-way communications for processing meter commands.
SOA Suite is NOT required with native implementations of Smart Grid Gateway adapters. See Smart Grid Gateway Implementations in the Oracle Utilities Meter Solution Administrative User Guide for more information.
Note: Oracle SOA Suite 12.2.1.4 requires Oracle WebLogic Server 12.2.1.4.
Oracle SOA Suite must be installed prior to the installation of Oracle Utilities Smart Grid Gateway. Oracle SOA Suite can be downloaded from the
Oracle Fusion Middleware Software Downloads portal.
Oracle Solaris 11 Application Server
This section describes the software requirements for operating the application using the Oracle Solaris application server.
Supported Application Servers
Solaris 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:
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 user ID is the only one given access to the files installed.
1. Create a group with name “cisusr” (user group).
2. Create a user with name “cissys” and primary group “cisusr”. Set the primary shell for the cissys user to Korn Shell.
The shell scripts use the “>” to overwrite shell functionality. Your operating system may be configured to not allow this functionality by default in the users shell.
To avoid file access permission problems when executing scripts, consider placing the following command into cissys profile script:
set +o noclobber
Security Configuration
Various options exist to secure a system. In this application all files will be created with the minimum permissions required to ensure that group-readable, group-writable, and group-executable files will have the correct user groups and to restrict the permissions available to legitimate users. In this way, a low privileged end user cannot directly edit configuration files and thereby bypass application security controls.
The following users and group categories must be defined to implement this security. For demonstration purposes the following users and groups will be used. These users must be created according to industry standards (including password policies). All users should be created with a default umask of 022 to ensure files created during normal operation have the correct permissions.
Please replace these users and groups for your installation defaults:
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 an install user, these components must belong to cissys.
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.
Oracle Java Development Kit v8.0.x.x Update 291, 64-bit
At time of release, Oracle Java packages could be obtained from:
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.
Hibernate 4.1.0 FINAL
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>
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 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 (as documented above) before installing WebLogic.
• Download and install WebLogic Server 12.2.1.4.
Note: With Oracle Utilities Application Framework V4.5.0.1.0 a WebLogic native installation is required. Refer to the
Oracle WebLogic 12.2.1.x Configuration Guide for Oracle Utilities Application Framework (Doc ID 2413918.1) document on
My Oracle Support.
Oracle Service Bus 12.2.1.4
Oracle Service Bus is required for implementations that plan to use middleware implementations of adapters or the generic adapter to process meter reading or device event data.
Oracle Service Bus is NOT required with native implementations of Smart Grid Gateway adapters. See Smart Grid Gateway Implementations in the Oracle Utilities Meter Solution Administrative User Guide for more information.
Note: Oracle Service Bus 12.2.1.4 requires Oracle WebLogic Server 12.2.1.4.
Oracle Service Bus must be installed prior to the installation of Oracle Utilities Smart Grid Gateway. Oracle Service Bus can be downloaded from the
Oracle Fusion Middleware Software Downloads portal.
Oracle SOA Suite 12.2.1.4
Oracle SOA Suite, specifically BPEL Process Manager, is required for implementations that plan to use middleware implementations of adapters or the generic adapter to implement two-way communications for processing meter commands.
SOA Suite is NOT required with native implementations of Smart Grid Gateway adapters. See Smart Grid Gateway Implementations in the Oracle Utilities Meter Solution Administrative User Guide for more information.
Note: Oracle SOA Suite 12.2.1.4 requires Oracle WebLogic Server 12.2.1.4.
Oracle SOA Suite must be installed prior to the installation of Oracle Utilities Smart Grid Gateway. Oracle SOA Suite can be downloaded from the
Oracle Fusion Middleware Software Downloads portal.
Windows Server 2012 R2 Application Server
This section describes the software requirements for operating the application using the Windows application server.
Supported Application Servers
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.
Oracle Java Development Kit v8.0.x.x Update 291, 64-bit
At time of release, Oracle Java packages could be obtained from:
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.
Hibernate 4.1.0 FINAL
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>
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 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 (as documented above) before installing WebLogic.
• Download and install WebLogic Server 12.2.1.4.
Note: With Oracle Utilities Application Framework V4.5.0.1.0 a WebLogic native installation is required. Refer to the
Oracle WebLogic 12.2.1.x Configuration Guide for Oracle Utilities Application Framework (Doc ID 2413918.1) document on
My Oracle Support.
Oracle Service Bus 12.2.1.4
Oracle Service Bus is required for implementations that plan to use middleware implementations of adapters or the generic adapter to process meter reading or device event data.
Oracle Service Bus is NOT required with native implementations of Smart Grid Gateway adapters. See Smart Grid Gateway Implementations in the Oracle Utilities Meter Solution Administrative User Guide for more information.
Note: Oracle Service Bus 12.2.1.4 requires Oracle WebLogic Server 12.2.1.4.
Oracle Service Bus must be installed prior to the installation of Oracle Utilities Smart Grid Gateway. Oracle Service Bus can be downloaded from the
Oracle Fusion Middleware Software Downloads portal.
Oracle SOA Suite 12.2.1.4
Oracle SOA Suite, specifically BPEL Process Manager, is required for implementations that plan to use middleware implementations of adapters or the generic adapter to implement two-way communications for processing meter commands.
SOA Suite is NOT required with native implementations of Smart Grid Gateway adapters. See Smart Grid Gateway Implementations in the Oracle Utilities Meter Solution Administrative User Guide for more information.
Note: Oracle SOA Suite 12.2.1.4 requires Oracle WebLogic Server 12.2.1.4.
Oracle SOA Suite must be installed prior to the installation of Oracle Utilities Smart Grid Gateway. Oracle SOA Suite can be downloaded from the
Oracle Fusion Middleware Software Downloads portal.
Additional Prerequisite Software Information
This section outlines additional information related to installing the prerequisite software, including:
Setting Up and Using the Additional JAR Directory
The additional JAR directory must be populated if the Web Application Server Home directory is not set.
For example: The environment is for batch only and the server has no WebLogic installed. In this scenario, the Additional JAR Directory must be created prior to the installation and the following list of WebLogic JARs should be copied to that directory (full path from the actual WebLogic location which must be installed in the web server).
<Web Application Server Home Directory>/server/lib/wlthint3client.jar
<Web Application Server Home Directory>/../oracle_common/modules/org.codehaus.woodstox.stax2-api.jar
<Web Application Server Home Directory>/../oracle_common/modules/org.glassfish.jersey.core.jersey-client.jar
<Web Application Server Home Directory>/../oracle_common/modules/org.glassfish.jersey.core.jersey-common.jar
<Web Application Server Home Directory>/../oracle_common/modules/org.glassfish.jersey.bundles.repackaged.jersey-guava.jar
<Web Application Server Home Directory>/../oracle_common/modules/org.glassfish.jersey.core.jersey-server.jar
<Web Application Server Home Directory>/../oracle_common/modules/org.glassfish.jersey.media.jersey-media-jaxb.jar
<Web Application Server Home Directory>/../oracle_common/modules/org.glassfish.jersey.media.jersey-media-multipart.jar
if WebLocic 12.2.1.[0-2].0:
<Web Application Server Home Directory>/../oracle_common/modules/org.codehaus.woodstox.woodstox-core-asl.jar
if WebLocic is not 12.2.1.[0-2].0:
<Web Application Server Home Directory>/../oracle_common/modules/com.fasterxml.woodstox.woodstox-core.jar
If the Additional JAR directory is configured, the initialSetup process will pull those JARs from that directory. If it is not configured, the initialSetup process will pull those JARs from the Web Application Server Home directory.
Special Note to Upgrade from a WebLogic 12.1.3.x Environment
If you are upgrading from an environment which is using WebLogic 12.1.3.x, make sure to follow the steps below prior to the installation:
1. Install Oracle WebLogic Server (Fusion Middleware Infrastructure) 12.2.1.4.
2. Install Oracle Java SE Development Kit 1.8.0_261 (if not installed yet).
3. Shutdown the application server environment.
4. Take a full backup of the application:
$SPLEBASE
5. Set the environment as follows:
splenviron.sh -e <ENV NAME>
6. Reconfigure the environment to point to the new WebLogic and Java (if upgraded Java as well):
Execute:
configureEnv.sh -i
Update:
“Web Java Home Directory” and “Web Application Server Home Directory”
Type <P> to process (no need to rerun initialSetup.sh).
7. Set the environment again.
splenviron.sh -e <ENV NAME>
8. Upgrade the Oracle Utilities Application Framework to V4.5.0.1.0.
install.sh -u