| Oracle® Health Sciences Data Management Workbench Installation Guide Release 2.3 E35223-01 |
|
 Previous |
 Next |
| Oracle® Health Sciences Data Management Workbench Installation Guide Release 2.3 E35223-01 |
|
Previous |
Next |
This section contains the following topics:
Section 3.3, "Install Oracle Application Developer and Apply Patches"
Section 3.4, "Create a WebLogic Server Domain for Oracle DMW"
Section 3.5, "Apply the JSF Library to the Oracle DMW Domain"
Section 3.6, "Copy runtime12.jar into the Domain's lib Directory"
Additional setup is required on the WebLogic Server to support the integration with Oracle Health Sciences InForm if you are using HTTPS; see Section 5.4, "Configure the WebLogic Server for Sending Discrepancies to InForm Supporting HTTPS."
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). |
Oracle Java Development Kit (JDK) 1.7 is also known as JDK 7. Oracle DMW 2.3 uses JDK 1.7.0_17. Use this version instead of the older version that is included in the media pack with Oracle Application Developer.
To download and install JDK 1.7.0_17:
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 17 (only).
|
Note: Do not install a higher version of Oracle JDK unless explicitly instructed to do so by an Oracle DMW-specific note on My Oracle Support. |
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.
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/overview.htm, or download the PDF from here: http://docs.oracle.com/cd/E23943_01/wls.htm.
Oracle recommends installing Web Logic Server in Development mode and changing to Production mode after you have finished. The system prompts you for Development or Production mode during installation. To change to Production mode, see http://docs.oracle.com/cd/E23943_01/apirefs.1111/e13952/taskhelp/domainconfig/ChangeRuntimeModes.html
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) 1.7.0_17 (JDK 7) that you installed in Section 3.1.
Install Oracle Application Developer and apply required patches.
Install Oracle Application Developer 11g R1 (11.1.1.6), which is included in the media pack.
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.
Follow instructions in the readme files to apply the following JDeveloper patches to upgrade Oracle Application Developer Framework to 11.1.2.2.0. The patches are included in the media pack.
13656274
13656372
Create a WebLogic domain called DMWDomain 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/overview.htm.
During domain creation, do the following.
During domain creation, create a Machine named 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.
During domain creation, create a Managed Server called DMWServer and assign it to DMWMachine.
Log in to the WebLogic console and run upgradeADF to apply the JSF library to the domain. For example:
upgradeADF('/app/oracle/product/middleware/user_projects/domains/DMWDomain')
For further information, see My Oracle Support document ID 1328698.1.
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.
Modify the setDomainEnv.sh to configure the WebLogic AdminServer and DMWServer. Oracle recommends the following settings for production use.
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:
NONSSL if you plan to use HTTP for InForm adapter web service calls
SSL if you plan to use HTTPS for InForm adapter web service calls
Search for the following text:
JAVA_OPTIONS="${JAVA_OPTIONS}”
Append -DdmwWebService=SSL or NONSSL to the end . Make sure this parameter is contained within the quotes:
if [ "${WEBLOGIC_EXTENSION_DIRS}" != "" ] ; then
JAVA_OPTIONS="${JAVA_OPTIONS} -Dweblogic.ext.dirs=${WEBLOGIC_EXTENSION_DIRS}"
export JAVA_OPTIONS
fi
JAVA_OPTIONS="${JAVA_OPTIONS} -DdmwWebService=NONSSL"
export JAVA_OPTIONS
# SET THE CLASSPATH
|
Note: If this parameter is not explicitly added to the setDomainEnv.sh file, the Oracle DMW application will use SSL by default. For more information on HTTP and HTTPS support, see Chapter 4, "Deploy Oracle DMW on the WebLogic Server". |
Locate the following section:
if [ "${USER_MEM_ARGS}" != "" ] ; then
MEM_ARGS="${USER_MEM_ARGS}"
export MEM_ARGS
fi
and add the following text (which continues to next page) BEFORE the text shown above :
# 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
Add the following text at the end of the file:
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.
Add the following text to enable huge pages:
EXTRA_JAVA_PROPERTIES="${EXTRA_JAVA_PROPERTIES} -XX:+UseLargePages"
export EXTRA_JAVA_PROPERTIES
Set application module properties (replace NN below with expected number of concurrent users):
EXTRA_JAVA_PROPERTIES="${EXTRA_JAVA_PROPERTIES}
-Djbo.doconnectionpooling=true
-Djbo.txn.disconnect_level=1
-Djbo.ampool.doampooling=true
-Djbo.ampool.minavailablesize=1
-Djbo.ampool.maxavailablesize=NN
-Djbo.recyclethreshold=NN
export EXTRA_JAVA_PROPERTIES
After editing setDomainEnv.sh, restart the computer.
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.
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 at https://support.us.oracle.com/oip/faces/secure/km/DownloadAttachment.jspx?attachid=974949.1:EBSSDK_DOC_PDF .
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.
The E-Business Suite Software Development Kit for Java ships as patch 16487062 (p16487062_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.
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.
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 the authentication messages.
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.
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.9.1.3, "Register the External Node and Generate the Desktop DBC File".
Follow instructions for Step 2.1.5.3 in Oracle® E-Business Suite Software Development Kit for Java.
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.9.1.1, "Copy the Database Connection File." |
In Step 5, enter values exactly as follows:
Name for the datasource: lswdbDS
JNDI Name: jbdc/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
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.11, "Stopping and Starting the WebLogic Servers."
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."
Make the following changes on the DMWServer Managed Server.
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.
In the WebLogic Server Console:
Click the Lock and Edit button.
Click on Deployments, then click jsf(2.0,1.0.0.0_2-0-2)
Click the Targets tab and select the DMWServer checkbox. Also leave AdminServer selected.
Save.
Click the Activate Changes button to activate the changes in the WebLogic Server.
In the WebLogic Server Console:
Navigate to to Services, then Data Sources, then lswdbDS, then the Connection Pool tab.
Change the Maximum Capacity setting from 15 to 30.
In the WebLogic Server Console:
Under Settings for DMWServer, select Configuration, then General.
Clear the value in the Listen Address field.
Save.
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.
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:
/app/oracle/product/middleware/user_projects/domains/DMWDomain/servers/AdminServer/logs
and
/app/oracle/product/middleware/user_projects/domains/DMWDomain/servers/DMWServer/logs
|
 Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|