Post Install for a Federated Server in Network Deployment Mode

After you have completed the creation of a JD Edwards EnterpriseOne HTML Web Server as a Managed Instance in Server Manager the Management Console displays this warning:

Do not click the Synchronize Configuration button yet. Follow the steps in this section.

To install a HTML Web Server HTML Web Server to a WebSphere Federated Server in Network Deployment Mode:

Note:

Steps 1 and 3 below are only applicable if the J2EE server you selected to create the HTML Web Server managed instance resides on a machine different that the deployment manager. The remainder of the steps are applicable to all federated deployments. You may ignore steps 2 and 4 if the federated server you selected resides on the same machine as the deployment manager.

1. If you are using an Oracle database, configure the tnsnames.ora setting using these steps:

   1. Use this navigation path for the Managed Instance you just created in Server Manager:

      Configuration > JDBJ Database Configuration > Oracle Database Settings > TNSNAMES.ORA Location

   2. Configure the setting to tnsnames.ora without the full file path.

      For example:

      

2. If you have not already done so, install the JDBC driver to the J2EE container. Refer to Install JDBC Drivers to J2EE Servers in this guide.

3. After installing the JDBC driver, you must modify the WebSphere JDBC provider as described in these steps:

   1. Copy the JDBC driver file(s) appropriate to your database to a location on the physical machine on which the federated server resides. For example:

      /u01/JDBCDriver

   2. Use these steps to modify the JDBC provider for the remote J2EE container in WebSphere to point to the driver file in this new location.

      i. In the WebSphere Administrative Console (for the deployment manager), navigate to the section called JDBC Providers as shown in this screen:

      

      ii. Complete the filter fields with the appropriate Cell, Node and Server information for the J2EE Container to which the HTML Web Server was deployed.

      For example:

      

      iii. Click the Apply button.

      iv. On JDBC Providers, click on the appropriate JDBC provider for the database which you are using with HTML Web Server.

      Note:

      The preceding example screen assumes an Oracle database.

      v. Replace the path to the JDBC driver files as configured by Server Manager to the machine-specific path where you previously placed the drivers. Refer to the preceding Step 3 where you copied the JDBC driver file(s) appropriate to your database to a location on the physical machine on which the federated server resides.

      This example screen assumes Oracle JDBC driver files were placed in the location /u01/JDBCDriver:

      

      vi. Click the OK button to save the configuration change and initiate node synchronization through the deployment manager.

   3. This completes the modification of the WebSphere JDBC provider.

4. Configure the HTTP Server by copying the appropriate text:

   from this file:

   JDE_HOME/targets/e1_html_server_instance_name/Readme.txt

   to this file:

   The httpd.conf file of the HTTP server you wish to use for this Managed Instance.

   where e1_html_server_instance_name is the name you defined in Server Manager.

   You must modify the path to the Readme.txt file to reflect the JDE_HOME location and the Managed Instance name in your environment. This is an example of a properly configured Readme.txt file:

   

5. Make any other configuration changes required to define this Managed Instance.

   

6. In Server Manager, navigate to the page for the Managed Instance and click on the Synchronize Configuration button.

   The synchronization process may take a few minutes to complete. The JD Edwards EnterpriseOne Managed Instance is configured and ready to use after the preceding steps have been completed.

For any subsequent configuration changes made to this Managed Instance, Management Console re-displays the Synchronize Configuration button with the corresponding warning message. You must click the button to apply the configuration changes to the remote server. After the changes are applied, the Management Console no longer displays the button and warning message.