3 Install Oracle WebLogic Server

This section contains the following topics:

Section 3.1, "Install Oracle Java Development Kit"
Section 3.2, "Install and Patch Oracle WebLogic Server"
Section 3.3, "Install and Upgrade Oracle Application Developer Framework"
Section 3.4, "Create the Metadata Services Repository Schema in the Database"
Section 3.5, "Create a WebLogic Server Domain for Oracle DMW"
Section 3.6, "Upgrade ADF in the Oracle DMW Domain"
Section 3.7, "Copy runtime12.jar into the Domain's lib Directory"
Section 3.8, "Edit setDomainEnv.sh"
Section 3.10, "Change the Default Timeout Period (Optional)"
Section 3.12, "Restart WebLogic Server and Check Settings"
Section 3.13, "Change WebLogic Server to Production"
Section 3.14, "Enable E-Business Suite User Authentication"
Section 3.15, "Configure the DMWServer Managed Server"
Section 3.16, "Restart the WebLogic Server"

The complete documentation set for Oracle WebLogic Server 10.3.6 is available at: http://docs.oracle.com/cd/E23943_01/wls.htm.

Note:

You must install Oracle WebLogic Server on a different application server from Oracle Life Sciences Data Hub (Oracle LSH).

Note:

Perform all installation tasks as the same OS user.

3.1 Install Oracle Java Development Kit

Oracle Java Development Kit (JDK) 1.7 is also known as JDK 7. Oracle DMW 2.4 uses JDK 1.7.0_51 or higher.

To download and install JDK 1.7.0_51:

Go to My Oracle Support at https://support.oracle.com and sign in.
In the Search Knowledge Base field in the upper right, enter: All Java SE Download on MOS [ID 1439822.1].
Click the link to the document All Java SE Downloads on MOS (ID 1439822.1).
Scroll down to the list of JDK versions to Oracle JDK 7 Update 51 (or higher).
Click the patch number link.
Select the appropriate platform and click ReadMe to read the release notes and Download to download the patch.
Follow instructions in the release notes to apply the patch.

3.2 Install and Patch Oracle WebLogic Server

3.2.1 Install Oracle WebLogic 10.3.6

Install WebLogic 10.3.6 following instructions in OracleÂ® Fusion Middleware Installation Guide for Oracle WebLogic Server 11g Release 1 (10.3.6), which you can find on the media pack or at http://docs.oracle.com/cd/E23943_01/doc.1111/e14142.pdf, or download the PDF from here: http://docs.oracle.com/cd/E23943_01/wls.htm.

Point to Installed JDK 7

The WebLogic Server installation process includes specifying a JDK installation. At this point, specify the Oracle Java Development Kit (JDK) that you installed in Section 3.1.

3.2.2 Apply Patch 10.3.6.0.8

Install Oracle WebLogic Server Patch Set Update (PSU) 10.3.6.0.8, which is patch 18040640, following instructions in the readme file. See "Finding Patches on My Oracle Support."

3.3 Install and Upgrade Oracle Application Developer Framework

Install Oracle Developer Framework (ADF, which is also known as Oracle Application Developer) and apply required patches.

3.3.1 Install Oracle Application Developer Framework

Install Oracle Application Developer Framework (ADF) 11g R1 (11.1.1.6), which is included in the media pack as Application Development Runtime.

Follow instructions in OracleÂ® Fusion Middleware Installation Guide for Application Developer 11g Release 1 (11.1.1.6.0), which you can find on the media pack or at http://docs.oracle.com/cd/E23943_01/doc.1111/e14827/toc.htm.

3.3.2 Upgrade ADF to 11.1.2.4

Additional information is in the patch readme files. However, because there are no WebCenter components explicitly installed, you cannot follow the patch readme instructions completely.

Note:

Oracle supports only English OS language settings for the application tier.

Copy the following patches from the staging area you created when you downloaded the media pack to a temporary directory:
- 16546129âJDeveloper patch
- 16546157âWebCenter Composer patch

Set environment variables to run the OPatch utility.

export MW_HOME=MIDDLEWARE_HOME
export ORACLE_HOME=MIDDLEWARE_HOME/oracle_common
export PATH=$PATH:MIDDLEWARE_HOME/oracle_common/OPatch

Run OPatch to verify that the current Oracle Application Developer 11g version installed is: 11.1.1.6.0.
```
opatch lsinventory
```
Change to the temporary directory where you put the patches.

Unzip the patches and confirm that they are extracted.

unzip p16546129_111160_Generic.zip
unzip p16546157_111160_Generic.zip
ls

should return

16546129 16546157 p16546129_111160_Generic.zip p16546157_111160_Generic.zip

Change to directory 16546129 and run opatch apply. Enter y when prompted.
Change to directory 16546157 and run opatch apply. Enter y when prompted.
Verify that both patches are applied successfully:
```
opatch lsinventory 
```
The system returns the date and time they were applied, lists the bugs they fix, and says OPatch succeeded.

3.4 Create the Metadata Services Repository Schema in the Database

Run the Repository Creation Utility 11.1.1.6 to create the metadata services schema, DEV_MDS, in the database. See http://docs.oracle.com/cd/E23943_01/doc.1111/e14259/rcu_screens.htm.

This step is required for the Web Services Manager (WSM) Policy Manager.

3.5 Create a WebLogic Server Domain for Oracle DMW

Create a WebLogic domain with the suggested name DMWDomain following instructions in Creating Domains Using the Configuration Wizard at http://docs.oracle.com/cd/E23943_01/web.1111/e14140.pdf.

During domain creation, do the following.

3.5.1 Select Oracle Common Options

During domain creation, select Generate a domain configured automatically to support the following products and then select:

Oracle JRF - 11.1.1.0 [oracle_common]
Oracle Enterprise Manager - 11.1.1.0 [oracle_common]
Oracle WSM Policy Manager - 11.1.1.0 [oracle_common]

3.5.2 Select Development Mode

In the Configure Server Start Mode and JDK step, select Development Mode.

You will change to Production mode later; see Section 3.13, "Change WebLogic Server to Production".

3.5.3 Create a WebLogic Server "Machine"

During domain creation, create a Machine with the suggested name DMWMachine. A machine is the logical representation of the computer that hosts one or more WebLogic Server instances. Each Managed Server must be assigned to a machine.

3.5.4 Create a Managed Server and Assign it to the Machine

During domain creation, create a Managed Server with the suggested name DMWServer and assign it to the DMW Machine.

Note:

The following instructions refer to this Managed Server as DMWServer and the Machine as DMWMachine.

3.5.5 Configure the JDBC Schema

Provide the details of the schema you created in Section 3.4, "Create the Metadata Services Repository Schema in the Database" to configure the JDBC component schema.

Specify that the JDBC services mds-owsm and wsm-pm are deployed to the AdminServer or the managed server where you want the WSM service to be running.

3.5.6 Support SSL Wildcards and SSL Web Services

If you are using HTTPS, check the following settings and change them if necessary to support SSL wildcards; for example *.company.com instead of server.company.com.

Log in to the WebLogic Server Console and open the SSL tab.
Set Hostname Verification = Custom Hostname Verifier.
Set Custom Hostname Verifier = weblogic.security.utils.SSLWLSWildcardHostnameVerifier
Select Use JSSE SSL. This is required for HTTPS SSL web services, not specifically for wildcards. If you are using HTTP, do not select this setting.
Save.

3.5.7 Restart the WebLogic Server

See Section 3.16, "Restart the WebLogic Server."

3.6 Upgrade ADF in the Oracle DMW Domain

Navigate to MIDDLEWARE_HOME/oracle_common/common/bin.
Run setWlstEnv.sh to set up the environment.
Run wlst.sh to start the WebLogic Scripting Tool (WLST).
At the WLST prompt enter:
```
upgradeADF(&rsquor;DOMAIN_HOME');
```
For example:
```
 upgradeADF('Middleware_Home/user_projects/domains/DMWDomain')
```
Tip:
In the WebLogic Scripting Tool shell you can type help() to get information on available commands.

3.7 Copy runtime12.jar into the Domain's lib Directory

The Oracle Database file runtime12.jar is included in $ORACLE_HOME/sqlj/lib on the Oracle LSH database server computer.

Using SFTP, copy it from there to the WebLogic Server computer, to the lib directory of the domain created when you installed the WebLogic Server.

3.8 Edit setDomainEnv.sh

Modify the setDomainEnv.sh to configure the WebLogic Administration Server and DMWServer. Oracle recommends the following settings for production use. Be careful to insert text as directed before or after the located sections.

Check the available RAM on your machine. In Step 6 Oracle recommends setting it to 8gb, but this may not be possible.
Stop the Administration Server.
Log in to the system, change to the domain\bin directory, and open setDomainEnv.sh in an editing tool.
Add a parameter named DdmwWebService to JAVA_OPTIONS and set its value to:
- SSL if you plan to use HTTPS for InForm adapter web service calls.
- NONSSL if you plan to use HTTP for InForm adapter web service calls.
Search for the following text:
```
JAVA_OPTIONS="${JAVA_OPTIONS}â
```
Add the parameter and value within the quotes. For example:
```
if [ "${WEBLOGIC_EXTENSION_DIRS}" != "" ] ; then
JAVA_OPTIONS="${JAVA_OPTIONS} -Dweblogic.ext.dirs=${WEBLOGIC_EXTENSION_DIRS}"
export JAVA_OPTIONS

fi

JAVA_OPTIONS="${JAVA_OPTIONS} -DdmwWebService=SSL"
export JAVA_OPTIONS

# SET THE CLASSPATH
```
On one and only one application server, add a parameter named -DhandleDiscEvent to JAVA_OPTIONS and set its value to TRUE, following the instructions in the previous step.

This is required to support multiple middle tiers pointing to the same database. Only the server with this parameter set to True will be able to send data from Oracle Thesaurus Management System (TMS) to InForm.
Synchronize the DMW WebLogic server clock with the InFormAdapter server clock by adding a parameter named user.timezone to JAVA_OPTIONS and set its value to the same timezone used by the InForm Adapter server, using a valid format supported by Java 7; for example:
```
-Duser.timezone=GMT
```
or
```
-Duser.timezone=EST
```
Make sure this parameter is contained within the quotes:
```
JAVA_OPTIONS="${JAVA_OPTIONS} -Duser.timezone=VALID_TIMEZONE"
export JAVA_OPTIONS 
```

Locate the following section:

if [ "${USER_MEM_ARGS}" != "" ] ; then
        MEM_ARGS="${USER_MEM_ARGS}"
        export MEM_ARGS
fi

and add the following text (which may continue to the next page) BEFORE the text shown above:

Note:

If you are using names other than "AdminServer" and "DMWServer," change the text accordingly.

# Set 1024MB for AdminServer
if [ "${SERVER_NAME}" == "AdminServer" ] ; then
      USER_MEM_ARGS="-Xms512m -Xmx1024m -XX:PermSize=256m -XX:MaxPermSize=512m "
    export USER_MEM_ARGS
fi
#Set 4G for Managed Server
if [ "${SERVER_NAME}" == "DMWServer" ] ; then
     USER_MEM_ARGS="-Xms8192m -Xmx8192m -XX:PermSize=1024m -XX:MaxPermSize=1024m -XX:NewSize=1024m -XX:MaxNewSize=1024m -XX:SurvivorRatio=8"
    export USER_MEM_ARGS
fi

Locate the following section:

if [ "${POST_CLASSPATH}" != "" ] ; then
        POST_CLASSPATH="${COMMON_COMPONENTS_HOME}/modules/oracle.jrf_11.1.1/jrf.jar${CLASSPATHSEP}${POST_CLASSPATH}"
        export POST_CLASSPATH
else
        POST_CLASSPATH="${COMMON_COMPONENTS_HOME}/modules/oracle.jrf_11.1.1/jrf.jar"
        export POST_CLASSPATH
fi

and add the following AFTER the text shown above:

if [ "${POST_CLASSPATH}" != "" ] ; then
        POST_CLASSPATH="${COMMON_COMPONENTS_HOME}/modules/features/adf.model_11.1.1.jar${CLASSPATHSEP}${POST_CLASSPATH}"
        export POST_CLASSPATH
else
        POST_CLASSPATH="${COMMON_COMPONENTS_HOME}/modules/features/adf.model_11.1.1.jar"
        export POST_CLASSPATH
fi

Locate the first occurrence of POST_CLASSPATH and add the following after it:

if [ "${POST_CLASSPATH}" != "" ] ; then
      POST_CLASSPATH="${DOMAIN_HOME}/lib/fndext.jar${CLASSPATHSEP}${DOMAIN_HOME}/lib/runtime12.jar${CLASSPATHSEP}${POST_CLASSPATH}"
      export POST_CLASSPATH
else
      POST_CLASSPATH="${DOMAIN_HOME}/lib/fndext.jar${CLASSPATHSEP}${DOMAIN_HOME}/lib/runtime12.jar"
      export POST_CLASSPATH
fi

Set PRODUCTION_MODE=true to run in Server mode.
If you want to use a date format other than the default format, dd-MMM-yyyy (01-JAN-2016), in the Listings pages, add the parameter -DlistingDateFormat to JAVA_PROPERTIES and set it to one of the supported values found in http://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html.

If the date format has space character in it, you must replace the space with an underscore ( _) character because WebLogic Server on Linux will not start with spaces in a parameter. For example, the following value:
```
-DlistingDateFormat=yyyy.MM.dd_G_'at'_HH:mm:ss_z"
```
displays dates as:
```
2001.07.04 AD at 12:08:56 PDT
```
Locate the first occurrence of EXTRA_JAVA_PROPERTIES and add the following to enable huge pages after it.
```
EXTRA_JAVA_PROPERTIES="${EXTRA_JAVA_PROPERTIES} -XX:+UseLargePages"
export EXTRA_JAVA_PROPERTIES
```
Set application module properties:

Note:
The setting -Djbo.ampool.maxinactiveage=1200000" creates a session timeout value of 20 minutes. If you prefer a different timeout period, see "Change the Default Timeout Period (Optional)."

EXTRA_JAVA_PROPERTIES="${EXTRA_JAVA_PROPERTIES}
-Djbo.ampool.doampooling=true
-Djbo.ampool.maxavailablesize=expected_maximum_number_of_concurrent_users
-Djbo.ampool.initpoolsize=80%_of_maximum_number_of_concurrent_users
-Djbo.ampool.minavailablesize=80%_of_maximum_number_of_concurrent_users
-Djbo.recyclethreshold=same_as_maximum_number_of_concurrent_users
-Djbo.ampool.timetolive=-1
-Djbo.ampool.maxinactiveage=1200000"
export EXTRA_JAVA_PROPERTIES

3.9 Restart the WLS Server

See Section 3.16, "Restart the WebLogic Server."

3.10 Change the Default Timeout Period (Optional)

The default timeout period is 20 minutes. It is set in both setDomainEnv.sh and plan.xml. The values in each place must be equal.

Note:

If you change these settings after deploying Oracle DMW, you must redeploy it, following instructions in Chapter 4, "Deploy Oracle DMW on the WebLogic Server."

To set a different timeout value:

Edit plan.xml, which is located in the top level of the DMW release .zip file. Open plan.xml in an editor, search for SessionTimeout, then change its value, which is in minutes, from 20 to the number of minutes you want.

<variable>

<name>SessionTimeout</name>

<value>number_of_minutes</value>

</variable>
Edit setDomainEnv.sh, which is located in the domain\bin directory, to add a value in milliseconds equal to the number of minutes you entered in plan.xml. For example, 20 minutes is 1200000 milliseconds. Find:

EXTRA_JAVA_PROPERTIES="${EXTRA_JAVA_PROPERTIES}

and add or edit the line:

-Djbo.ampool.maxinactiveage=number_of_milliseconds

3.11 Start the Node Manager and Check Settings

You can use the Node Manager to start and stop the Administration Server and the Managed Server and to start the server. If the following settings are not correct, change them manually.

Start the node manager; see http://docs.oracle.com/cd/E23943_01/web.1111/e13813/reference.htm#WLSTC516.
In the nodemanager.properties file, located at Middleware_Home/wlserver_10.3/common/nodemanager, set:

StartScriptEnabled = TRUE
The Managed Server listener address must be correct for your environment. It defaults to localhost, which causes problems when restarting the Node Manager.
1. Log in to the WebLogic Server Console, then click Environment, then Machines. Select DMWMachine, then Node Manager.
2. Change the value for Listen Address to the correct hostname for your environment.

3.12 Restart WebLogic Server and Check Settings

For the new setEnvDomain.sh settings take effect:

Restart the WebLogic Server. For instructions, see Section 3.16, "Restart the WebLogic Server".
Open the log file at domain_home/servers/DMWServer/logs/DMWServer.log.
Check that the new user memory settings -Xms512m and -Xmx1024m appear in the log file.

3.13 Change WebLogic Server to Production

You installed WebLogic Server in Development mode. Change WebLogic Server to Production mode, following instructions at http://docs.oracle.com/cd/E23943_01/apirefs.1111/e13952/taskhelp/domainconfig/ChangeRuntimeModes.html

3.14 Enable E-Business Suite User Authentication

Oracle DMW uses the user authentication feature of Oracle E-Business Suite, not the Oracle WebLogic Server. To enable Oracle DMW and Oracle WebLogic Server to communicate with the E-Business Suite, you must build a desktop database connection file and fndext.jar using the Oracle E-Business Suite Software Development Kit (SDK) for Java, a library of lightweight E-Business Suite APIs. SDK is not required after this initial setup.

3.14.1 Prepare the Oracle Applications Server to Receive Messages from Oracle DMW

Instructions in this section are in the guide OracleÂ® E-Business Suite Software Development Kit for Java, which you can find on the media pack and on My Oracle Support, ID 974949.1 at https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=455292524919907&id=974949.1&_adf.ctrl-state=1a8dpgv5nt_57.

3.14.1.1 Copy the Database Connection File

Create a directory on the WebLogic Server.
On the Oracle Applications Server that you installed for Oracle Life Sciences Data Hub, from $FND_SECURE copy the .dbc Oracle Applications database connection file to the directory.

3.14.1.2 Download and Install the Software Development Kit for Java

The E-Business Suite Software Development Kit for Java ships as patch 17269917 (p17269917_R12_GENERIC.zip) on the Oracle Health Sciences Life Sciences Warehouse media pack.

The .zip file contains:

The Oracle E-Business Suite SDK for Java file, fndext.jar
README.txt
Javadoc for Oracle E-Business Suite SDK for Java
An Apache Ant XML file named txkEbsSdkConfig.xml

Extract fndext.jar.
Copy the extracted fndext.jar file and the txkEbsSdkConfig.xml file to a directory such as/home/user1/ebssdk on the WebLogic server.
Copy the Javadoc to any appropriate location for convenient reference.

3.14.1.3 Register the External Node and Generate the Desktop DBC File

Follow instructions in Section 2.1.2, "Register the External Node and Generate the Desktop DBC File," in the OracleÂ® E-Business Suite Software Development Kit for Java.

3.14.1.4 Create the Required User dmwebs@oracle.com

Follow instructions in Section 2.1.3, "Set Up Necessary Oracle E-Business Suite Users" in OracleÂ® E-Business Suite Software Development Kit for Java to create a user named dmwebs@oracle.com user with the role UMX|APPS_SCHEMA_CONNECT.

This is the proxy user required to pass authentication messages.

3.14.2 Configure AppDataSource on the WebLogic Server

See Section 2.1.5, "Configuring AppsDataSource on Oracle WebLogic server (WLS)" in OracleÂ® E-Business Suite Software Development Kit for Java for detailed instructions for only the following steps.

3.14.2.1 Rebuild the fndext.jar file file for Oracle WebLogic Server on UNIX/LINUX

Follow instructions for Step 2.1.5.1 in OracleÂ® E-Business Suite Software Development Kit for Java. Use the new .dbc file created in Section 3.14.1.3, "Register the External Node and Generate the Desktop DBC File".

3.14.2.2 Deploy AppsDataSource Code on the Oracle WebLogic Server

Follow instructions for Step 2.1.5.3 in OracleÂ® E-Business Suite Software Development Kit for Java.

3.14.2.3 Configure the AppsDataSource in the Administration Console

Follow instructions for Step 2.1.5.4 in OracleÂ® E-Business Suite Software Development Kit for Java with the following requirements specific to Oracle DMW:

Note:

The .dbc file referred to here is the file that was copied in step Section 3.14.1.1, "Copy the Database Connection File."

In Step 5, enter values exactly as follows:

Name for the datasource: lswdbDS
JNDI Name: jdbc/lswdbDS
Database Type: Oracle
Database Driver: Oracle's Driver (Thin) for Instance connections; Versions:9.0.1,9.2.0,10,11

(This is for a non-XA data source, since Oracle DMW has only one database.)

In Step 10, enter values exactly as follows:

Driver Class Name:

oracle.apps.fnd.ext.jdbc.datasource.AppsDataSource
Database User Name:

dmwebs@oracle.com

3.14.2.4 Enable CLOB Support

You must enable CLOB Support for Oracle DMW in the WebLogic Server:

Navigate to Home, then Data Sources, then lswdbDS.
Click the Connection Pool tab.
Click Advanced.
Uncheck the property Wrap Data Types.
Restart the WebLogic server; see Section 3.16, "Restart the WebLogic Server."

3.14.3 Prepare a Security Realm on the WebLogic Server

Follow instructions for Step 3.3, "JAAS Configuration for Oracle WebLogic Server," up to substep 3.3.5, in OracleÂ® E-Business Suite Software Development Kit for Java.

For the Realm Name, enter EbsRealm (Step 6, Section 3.3.2, "Set Up Security Realm."

3.15 Configure the DMWServer Managed Server

Make the following changes on the DMWServer Managed Server.

3.15.1 Apply the JRF Template to DMWServer

Log in to Enterprise Manager.
Select the managed server DMWServer from the left pane.
Click the Apply JRF Template button at the top of the right pane.

3.15.2 Apply the JSF Library to the Oracle DMW Domain

In the WebLogic Server Console:

Click Deployments.
Under Name, select jsf(2.0,1.0.0.0_2-0-2).
Select the Targets tab.
Select the DMWServer and AdminServer check boxes if they are not already selected.
Save.

3.15.3 Change the Connection Pool Maximum Capacity on DMWServer

In the WebLogic Server Console:

Navigate to Services, then Data Sources, then lswdbDS, then the Connection Pool tab.
Change the Maximum Capacity setting from 15 to the number you entered (Section 3.8, "Edit setDomainEnv.sh", Step 9) for the maximum number of concurrent users during peak time plus 15%.

3.15.4 Clear the Listen Address

In the WebLogic Server Console:

Under Settings for DMWServer, select Configuration, then General.
Clear the value in the Listen Address field.
Save.

3.15.5 Set Up HTTPS

By default Oracle DMW supports and requires HTTPS. The following setup is required to use HTTPS.

Note:

If you want to use HTTP instead, skip this section. And when you get to Chapter 4, "Deploy Oracle DMW on the WebLogic Server", follow instructions in Section 4.2, "Alternative Oracle DMW Deployment Disabling HTTPS Support".

In the WebLogic Server Console:

Navigate to Servers, then Summary of Servers, then DMWServer.
Click DMWServer.
In the General tab, enable SSL by verifying that the following check boxes are selected:
- SSL Listen Port Enabled
- Client Cert Proxy Enabled
Verify that a port number is displayed for the SSL Listen Port.

3.16 Restart the WebLogic Server

For information on starting and stopping the WebLogic Server, see the OracleÂ® Fusion Middleware Managing Server Startup and Shutdown for Oracle WebLogic Server 11g Release 1 (10.3.6) at:

HTML: http://docs.oracle.com/cd/E23943_01/web.1111/e13708/toc.htm
PDF: You can download a PDF version of the same document in the same location by right-clicking the PDF link and selecting Save Target As.

Log Files Log files for the AdminServer and the DMWServer are located in:

middleware_home/user_projects/domains/DMWDomain/servers/AdminServer/logs

and

middleware_home/user_projects/domains/DMWDomain/servers/DMWServer/logs