4 JD Edwards EnterpriseOne HTML Server

This chapter contains these topics:

4.1 Understanding JD Edwards EnterpriseOne HTML Server

The JD Edwards EnterpriseOne HTML server is a WebLogic server. This server works with the OAM to ensure that SSO credentials are valid. When valid SSO credentials are entered, the user is granted access to JD Edwards EnterpriseOne.

When you download the software from Oracle Technology Network (OTN) note the directories to which you downloaded the software and replace the directory location specified in this chapter with your directory locations. This chapter also specifies executable files for a Windows platform. Be sure to install the executable files for your platform.

Note: The JD Edwards EnterpriseOne HTML server is installed on a different server than the OAM/OID server.

4.2 Installing SOA Suite 11g

You install SOA Suite 11g, version 11.1.1.5. You use the installer to download the Oracle Fusion Middleware 11g SOA Suite.

Prerequisites

Use these steps to install Oracle SOA Suite 11.1.1.5.0

  1. Launch the installer:

    • On Windows: setup.exe with Run as administrator option.

    • On Unix: ./runInstaller as a non-root user.

  2. On the Welcome page, click Next.

    This image is described in surrounding text
    Description of the illustration image107.gif

  3. Select the appropriate update option for your company.

    This image is described in surrounding text
    Description of the illustration image108.gif

  4. The installer performs prerequisite checks.

    This image is described in surrounding text
    Description of the illustration image109.gif

  5. Enter the Middleware Home and a SOA Home Directory.

    This image is described in surrounding text
    Description of the illustration image110.gif

  6. Select WebLogic as the application server.

    EnterpriseOne does not support the configuration with WebSphere Application Server.

    This image is described in surrounding text
    Description of the illustration image111.gif

  7. Review the Installation Summary.

    This image is described in surrounding text
    Description of the illustration image112.gif

  8. Click Next when the installation process is completed.

    This image is described in surrounding text
    Description of the illustration image113.gif

  9. Click Finish to exit the installer.

    This image is described in surrounding text
    Description of the illustration image114.gif

  10. Launch the Domain Configuration Wizard (config.cmd or config.sh) from <MW_Home>/Oracle_SOA/common/bin/.

    This image is described in surrounding text
    Description of the illustration image115.gif

  11. Select Oracle WSM Policy Manager-11.1.1.0 and Oracle JRF-11.1.1.0 options.

    This image is described in surrounding text
    Description of the illustration image116.gif

  12. Enter a domain name.

    This image is described in surrounding text
    Description of the illustration image117.gif

  13. Enter the Administrator User and Password.

    This image is described in surrounding text
    Description of the illustration image118.gif

  14. Select Production Mode and verify the JDK location.

    This image is described in surrounding text
    Description of the illustration image119.gif

  15. Enter the JDBC Schema information.

    This image is described in surrounding text
    Description of the illustration image120.gif

  16. Verify the schema connections.

    This image is described in surrounding text
    Description of the illustration image121.gif

  17. Select Administration Server and Managed Servers, Clusters and Machines options.

    This image is described in surrounding text
    Description of the illustration image122.gif

  18. Enter the Administration Server Name and Port.

    This image is described in surrounding text
    Description of the illustration image123.gif

  19. Click Next on the Configure Managed Servers page.

  20. Click Next on the Configure Clusters page.

  21. Add a logic machine name.

    This image is described in surrounding text
    Description of the illustration image124.gif

  22. Assign a server to the machines.

    This image is described in surrounding text
    Description of the illustration image125.gif

  23. Review the Configuration Summary and Click Create.

    This image is described in surrounding text
    Description of the illustration image126.gif

  24. Click Done and start the Administration Server.

    Refer to Appendix B on how to start and stop the Administration Server.

4.2.1 Verify the Installation

You must have the Administration Server running.

  1. Open an internet browser, and enter the following URL:

    http://server:port:/wsm-pm/validator

  2. Enter the Admin user and password.

  3. The Policy Manager Status screen appears.

    This image is described in surrounding text
    Description of the illustration image127.gif

  4. If the following error message occurs, use the steps in the next task to resolve the error.

    This image is described in surrounding text
    Description of the illustration image128.gif

Use these steps to fix errors:

  1. Access Data Sources using this path from the left navigation:

    base_domain -> Services -> JDBC -> Data Sources

    This image is described in surrounding text
    Description of the illustration image129.gif

  2. Click the mds-owsm link.

  3. On the Settings for mds-owsm page, click the Targets tab.

    This image is described in surrounding text
    Description of the illustration image130.gif

  4. On the Targets page, select AdminServer, and then click Save.

    This image is described in surrounding text
    Description of the illustration image131.gif

  5. Activate the change and restart the WLS Admin Server.

  6. Launch the URL again.

4.3 Installing Oracle WebGate

Next, you install Oracle WebGate 11.1.1.5.0.

Oracle HTTP Server WebGate is a Web server plug-in that is shipped out-of-the-box with Oracle Access Manager. The Oracle HTTP Server WebGate intercepts HTTP requests from users for Web resources and forwards them to the Access Server for authentication and authorization. Oracle HTTP Server WebGate installation packages are found on media and virtual media that is separate from the core components.

Prerequisites

  • You must have Oracle HTTP Server installed and configured. See Appendix C, "Installing Oracle HTTP Server."

  • If you are installing Oracle HTTP Server 11g WebGate for Oracle Access Manager on a Linux or Solaris operating system, you must download and install third-party GCC libraries on your machine.

You can download the appropriate GCC library from the following third-party website:

http://gcc.gnu.org/

Operating System Architecture GCC Libraries Required Library Version
Linux 64-bit x64 libgcc_s.so.1

libstdc++.so.6

 3.4.6
Solaris 64-bit SPARC libgcc_s.so.1

libstdc++.so.5

 3.3.2

  • If you are using Windows 2008 64-bit operating systems, you must install Microsoft Visual C++ 2005 libraries on the machine hosting the Oracle HTTP Server 11g WebGate.

The libraries are included in the Microsoft Visual C++ 2005 SP1 Redistributable Package (x64), which can be downloaded from the following website:

http://www.microsoft.com/DownLoads/details.aspx?familyid=EB4EBE2D-33C0-4A47-9DD4-B9A6D7BD44DA&displaylang=en

Use these steps to install Oracle HTTP 11g WebGate.

  1. Download and unzip ofm_oam_webgates_generic_11.1.1.5.0_disk1_1of1.zip.

  2. Launch the installer.

    • On Windows: setup.exe with Run as administrator option

    • On UNIX: ./RunInstaller as a non-root user

  3. Specify JRE/JDK location.

    This image is described in surrounding text
    Description of the illustration image084.gif

  4. Click Next on the Welcome page.

    Oracle HTTP WebGate supports Oracle HTTP version 11.1.1.2 or 11.1.1.3. EnterpriseOne configuration supports version 11.1.1.5. See Appendix A, "Create Database Schemas with Repository Creation Utility" to upgrade to version 11.1.1.5.

  5. The installer performs prerequisite checks.

    This image is described in surrounding text
    Description of the illustration image132.gif

    This image shows the prerequisite checks on Linux operating system.

    This image is described in surrounding text
    Description of the illustration image133.gif

  6. Specify the Middleware Home and WebGate Home Directory.

    This image is described in surrounding text
    Description of the illustration image134.gif

  7. Review the installation Summary.

    This image is described in surrounding text
    Description of the illustration image135.gif

  8. Click Next when the installation is completed.

    This image is described in surrounding text
    Description of the illustration image136.gif

  9. Click Finish to exist the installer.

    This image is described in surrounding text
    Description of the illustration image137.gif

4.3.1 Post-Installation Steps

You must complete the following steps after installing Oracle HTTP Server 11g WebGate for Oracle Access Manager:

  1. Move to the following directory under your Oracle Home for WebGate:

    • On UNIX operating systems:

      <webgate_home>/webgate/ohs/tools/deployWebGate

    • On Windows operating systems:

      <webgate_home>\webgate\ohs\tools\deployWebGate

  2. On the command line, run the following command to copy the required bits of agent from the Webgate_Home directory to the WebGate Instance location:

    • On UNIX operating systems:

      ./deployWebgateInstance.sh -w <Webgate_Instance_Directory> -oh <Webgate_Oracle_Home>

      This image is described in surrounding text
      Description of the illustration image091.gif

    • On Windows operating systems:

      deployWebgateInstance.bat -w <Webgate_Instance_Directory> -oh <Webgate_Oracle_Home>

      This image is described in surrounding text
      Description of the illustration image138.gif

      Where <Webgate_Oracle_Home> is the directory where you have installed Oracle HTTP Server WebGate and created as the Oracle Home for WebGate.

      For example: <MW_Home>/Oracle_OAMWebGate1

      The <Webgate_Instance_Directory> is the location of Webgate Instance Home, which is same as the Instance Home of Oracle HTTP Server.

      For example: <MW_Home>/Oracle_WT1/instances/instance1/config/OHS/ohs1

  3. Run the following command to ensure that the LD_LIBRARY_PATH variable contains <Oracle_Home_for_Oracle_HTTP_Server>/lib

    • On UNIX operating systems:

      Export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:<Oracle_Home_for_Oracle_HTTP_Server>/lib

    • On Windows operating systems:

      Set the <Webgate_Installation_Directory>\webgate\ohs\lib location in the PATH environment variable.

  4. From your present working directory, move up one directory level:

    • On UNIX operating systems:

      <webgate_home>/webgate/ohs/tools/setup/InstallTools

    • On Windows operating systems:

      <webgate_home>\webgate\ohs/tools\editHttpConf

  5. On the command line, run the following command to copy the apache_webgate.template from the Webgate_Home directory to the WebGate Instance location (renamed to webgate.conf) and update the httpd.conf file to add one line to include the name of webgate.conf

  6. Verify the updated httpd.conf.

    The following line is added to the bottom of the file

    include "z:\oracle\Middleware\Oracle_WT1\instances\instance1\config\ohs\ohs1/webgate.conf"

  7. Restart the Oracle HTTP server process.

    Run opmnctl (stopall and startall) from <MW_Home>\Oracle_WT1\instances\instance1\bin

4.4 Configuring the KeyStore Connection

This section discusses configuring the KeyStore connection for WebCenter and EnterpriseOne.

Prerequisites

Verify your Node Manger on your EnterpriseOne machine has the StartScriptEnable set to true:

  • Open the NodeManager.properties file from NMW_HOME>/wlserver_10.3/common/nodemanager folder and enter the following:

    StartScriptEnable=true

  • Restart Node Manager.

4.4.1 Generate the KeyStore from the Oracle WebCenter Server

Use these steps to generate the KeyStore.

  1. Log onto your WebCenter server.

  2. From the <JDK_Home>/bin directory, enter the following:

    ./keytool -genkeypair -v -keyalg RSA -dname "cn+den60208jems,dc+us,dc=oracle,dc=com" -alias webcenter -keypass welcome1 -keystore webcenter.jks -storepass welcome1 -validity 365

    -bash-3,2$ ./keytool -genkeypair -v -keyalg RSA -dname "cn=den60208jems,dc=us, dc=oracle,dc=com" -alias webenter -keypass welcome1 -keystore  webcenter.jks -storepass welcom1 -validity 365 Generating 1,024 bit RSA key pair and self-signed certificate (SHA1withRSA) with a validity of 365 days       for: CN=den60208jems, DC=us, DC=oracle, DC=com [Storing webcenter.jks]

    ./keytool -exportcert -v -alias webcenter -keystore webcenter.jks -storepass welcome1 -rfc -file webcenter.cer

    -bash-3.2$ ./keytool -exportcert -v -alias webventer -keystore webventer.jks -storepass welcome1 -rfc -file webcenter.cer Certificate stored in file <webcenter.cer>

  3. Copy the KeyStore files (keystore.jks and keystore.cer) to this location:

    <MW_HOME>user_projects/domains/<your_domain>/config/fmwconfig

    Note:

    If you launched the keytool from the JRockit/bin directory, then the KeyStore files will be generated in the same location.

  4. Sign on to WebCenter Enterprise Manager console, select WebLogic Domain > Security > Security Provide Configuration.

    Description of keystore001.gif follows
    Description of the illustration keystore001.gif

  5. Click Configure to set up the keystore.

    Description of keystore002.gif follows
    Description of the illustration keystore002.gif

  6. Enter the KeyStore file name and password.

  7. Enter the Key Alias and Crypt Alias, these value are from your key export process.

  8. Enter the passwords for both Signature Key and Encryption Key.

    ./keytool -exportcert -v -alias webcenter -keystore webcenter.jks -storepass welcome1 -rfc -file webcenter.cer

    In this example, we used webcenter as the key alias and the certificate name is webcenter.cer.

    Description of keystore003.gif follows
    Description of the illustration keystore003.gif

  9. Click OK.

  10. Restart WebCenter Admin and WC_Spaces.

4.4.2 Configure KeyStore on EnterpriseOne

Use these steps to configure the KeyStore on EnterpriseOne.

  1. Log onto your EnterpriseOne machine.

  2. Change the directory to <MW_HOME>/user_projects/domains/<your_domain>/config/fmwconfig.

  3. Copy these files from your WebCenter machine:

    • cwallet.sso

      This file is different than the OAM configuration; do not copy it from your OAM server.

    • your keystore.jks

      For example, webcenter.jks

    • your keystore.cer

      For example, webcenter.cer

  4. Open jps-config.xml from the same location.

  5. Search for default-keystore.jks.

  6. Replace the KeyStore location with your <keystore>.jks.

    You can adjust the description as illustrated here:

    Description of keystore004.gif follows
    Description of the illustration keystore004.gif

  7. Save the file.

4.5 Installing JD Edwards EnterpriseOne HTML Server

You must install the JD Edwards EnterpriseOne HTML Server.

See the JD Edwards EnterpriseOne HTML Web Server Reference Guide for your platform in the JD Edwards EnterpriseOne Installation and Upgrade for Apps 9.0 & Apps 9.1 using Tools 9.1 Documentation Library http://docs.oracle.com/cd/E24902_01/nav/reference.htm.

Prerequisites

  • For Related Information Application Framework configuration, EnterpriseOne HTML server must be installed within the SOA domain.

  • Install and configure the JD Edwards EnterpriseOne Server Manager

  • Install Server Manger Agent on the EnterpriseOne HTML Server.

  • Start the EnterpriseOne HTML Server.

This image is described in surrounding text
Description of the illustration image141.gif

4.6 Configuring Oracle HTTP Server for EnterpriseOne HTML Server

After you install and configure the Oracle HTTP Server and Oracle HTTP WebGate, use the following example to configure mod_wl_ohs.conf (located at <MW_Home>/OracleWT1/instance/instance1/config/OHS/ohs1.). Verify that WebLogic port numbers match your configuration.

This image is described in surrounding text
Description of the illustration image142.gif

4.7 Registering the WebGate Agent for EnterpriseOne HTML Server

Prerequisites

  • Install Oracle HTTP Server and WebGate.

  • Install and configure OID and OAM Server.

  • Install and configure EnterpriseOne HTML Server.

Use these steps to register the WebGate Agent.

  1. Open an internet browser and connect to the Oracle Access Manager.

  2. Open the OAM console.

    http://oamserver:oamport/oamconsole

  3. Enter the Admin user and Password.

  4. Select the New OAM 11g Webgate option.

    This image is described in surrounding text
    Description of the illustration image143.gif

  5. Enter a WebGate agent name and select the Open Security option.

  6. Enter the EnterpriseOne HTML URL in Base URL.

    Use the http port number.

  7. Click Apply.

    This image is described in surrounding text
    Description of the illustration image144.gif

  8. Host Identifiers and Application Domains are generated.

    This image is described in surrounding text
    Description of the illustration image145.gif

  9. Select Resources, and then click Create to create the Resource URL.

    This image is described in surrounding text
    Description of the illustration image146.gif

  10. Enter the following information:

    • Type = HTTP

    • Host Identifier = Select your Host Identifier

    • Resource URL = /jde

    • Protection Level = Protected

    • Authentication Policy = Protected Resource Policy

    • Authorization Policy = Protected Resource Policy

    This image is described in surrounding text
    Description of the illustration image147.gif

  11. Repeat the above step and add the resource URL = /…/*

  12. Double-click the Protected Resource Policy to see the newly added resources listed.

    This image is described in surrounding text
    Description of the illustration image148.gif

  13. Click the Responses tab, and then click the Add button

  14. Enter the JDE SSO header field as follows:

    • Response Name = JDE_SSO_UID

    • Type = Header

    • Value = $user.userid

    This image is described in surrounding text
    Description of the illustration image150.gif

  15. Review all registered agents.

  16. Select the System Configuration tab.

  17. Open the Access Manager Settings section and open the SSO Agents option.

  18. Double click OAM Agents, and then click the Search button.

    The system displays a list of registered agents.

    This image is described in surrounding text
    Description of the illustration image151.gif

  19. The registered agent creates a cwallet.sso and ObAccessClient.xml file.

  20. Copy these two file to the EnterpriseOne Server:

    <MW_HOME>/user_projects/domain/OAMDomain/output/<Agent_name> location

    <MW_Home>Oracle_WT1/config/instances/instance1/OHS/ohs1/webgate/config directory.

4.8 Enabling OAM SSO on the EnterpriseOne HTML Server

Use these steps to enable OAM SSO on the JD Edwards EnterpriseOne HTML server through JD Edwards EnterpriseOne Server Manger:

  1. Open Server Manager from a browser.

  2. Select your instance.

  3. Select Network Settings from the Configuration section.

    This image is described in surrounding text
    Description of the illustration image152.gif

  4. Select the Enable Oracle Access Manager option.

  5. Enter the Sign-Off URL

    http://<OAM-Server>:<OAM-Port>/oamsso/logout.html?end_url=http://<JAS-Server:JAS-Port/jde/index.jsp

    For example:

    http://denptw23:14100/oamsso/logout.html?end_url=http://dendell06:7777/jde/index.jsp

  6. Click Apply.

    You are prompted to synchronize the ini changes.

  7. Stop and restart the HTML server.

4.9 Copying JAR File to the HTML Web Server

Copy the following jar files from the WebCenter server to the HTML Web server:

  • spaces-api.jar

  • spaces-webservice-client.jar

  • webcenter-core-api.jar

The spaces-api.jar and webcenter-core-api.jar files are typically located at <WebCenter>\lib\java\internal\oracle.webcenter.spaces\11.1.1.0.0.

For example:

C:\oracle\Middleware\Oracle_WC1\lib\java\internal\oracle.webcenter.spaces\11.1.1.0.0

The spaces-webservice-client.jar file is typically located at <WebCenter>\webcenter\modules\oracle.webcenter.framework_11.1.1.

For example:

C:\oracle\Middleware\Oracle_WC1\webcenter\modules\oracle.webcenter.framework_11.1.1

Copy the jar files to the following location on the HTML Web server:

<Middleware>/user_projects/domains/< domain>/servers/<EnterpriseOne HTML server>/stage/<jas instance>/app/webclient.war/WEB-INF/lib

After you copy the files to the HTML Web server, restart the HTML Web server.

4.10 Granting Permission to the Client Application to Request a Token from OpenSSO

  1. Open the <MW_HOME>/user_projects/domains/<domain>/config/fmwconfig/system-jazn-data.xml file.

  2. Search for the oracle.wsm.security.WSIdentityPermission class.

  3. Add the following permission section:

    <permission>

    <class>oracle.wsm.security.WSIdentityPermission</class>

    <name>resource={your_JAS_server_name}</name>

    <actions>assert</actions>

    </permission>

    This image is described in surrounding text
    Description of the illustration image153.gif

  4. Save the file, and then stop and restart your EnterpriseOne Server using Server Manager.

4.11 Synchronizing the System Clock on all Servers

Important:

After all three of the machines (WebCenter, JD Edwards EnterpriseOne HTML Web Server, and the Oracle Access Manger (SSO Server) are successfully installed and configured, you MUST synchronize the clocks of all three machines. Otherwise you will not able to log in.

See "Synchronizing Clocks" in the JD Edwards EnterpriseOne Tools System Administration Guide

4.12 Testing the SSO Configuration

Use these steps to test the SSO configuration.

  1. Enter the following in the Address line:

    http://<your host:your sso port>/jde/E1Menu.maf

    Note:

    Ensure you provide the HTTP port instead of the actual JAS port. You will not be able to log in with your original JAS port.

  2. The Oracle Access Manager 11g login page appears.

    This image is described in surrounding text
    Description of the illustration image154.gif

  3. After the sign-on is working, create a WebCenter connection and enable an application form.

    See "Creating a WebCenter Connection" in the JD Edwards EnterpriseOne Tools System Administration Guide

    See "Enabling Application Forms" in the JD Edwards EnterpriseOne Tools System Administration Guide

  4. After the configuration is done, log onto EnterpriseOne and test the WebCenter Spaces configuration.

    The WebCenter Spaces appear on your configured application.

  5. You can click the green Plus icon to add new WebCenter Spaces.

    This image is described in surrounding text
    Description of the illustration image155.gif