Performing Post Installation for the Standalone Deployment Server with Oracle Database

This section shows you how to perform the post installation tasks for the standalone Deployment Server with Oracle database.

Important: This section is only applicable if you have deployed a standalone Deployment Server with Oracle database using One-Click Provisioning.

You can use One-Click Provisioning to install a standalone Deployment Server. A standalone Deployment Server is deployed when you first use One-Click Provisioning to provision a Deployment Server only, and then use One-Click Provisioning to provision other servers such as the Database Server, Enterprise Server, and HTML Server. This section describes how to complete the postinstallation steps for such a standalone Deployment Server.

If you have used One-Click Provisioning to deploy a standalone Deployment Server (that is, you did not use One-Click to initially deploy a complete system), you must perform the following procedure on your Deployment Server to enable access by JD Edwards EnterpriseOne.

Enable DEP920 Login for an Oracle Database

Important: This section is only applicable if your deployment of JD Edwards EnterpriseOne includes an Oracle Database Server.

After you have used One-Click Provisioning to deploy the complete suite of JD Edwards EnterpriseOne servers, you need to enable EnterpriseOne access to the Oracle database from the Deployment Server.

1. Access the Deployment Server as described in the preceding section "Accessing the Deployment Server".
2. Edit the jde.ini file, which is typically located in this directory:

   c:\Windows

3. Edit the jde.ini file to provide a valid value for the SecurityServer= setting. This is the machine name for your Enterprise Server. For example:

   [SECURITY]

   SecurityServer=oraes

4. Save and close the jde.ini file.

5. Navigate to the location of the Oracle Client that is installed on your Deployment Server. For example:

   C:\JDE\oracle1212\product\client_1\network\admin

6. In the above directory, edit the tnsnames.ora file to add the listener details. You can copy these details from the tnsnames.ora file on your Server Manager machine or your Enterprise Server machine. This tnsnames.ora file is located in the same location on each machine. From the Server Manager, use this navigation to find this tnsnames.ora file on either the Server Manager machine or the Enterprise Server:

   From the HTML Server, select DATABASE, and then select Tnsnames.

   For example, this is the listener section you should copy:

   JDEORCL =
     (DESCRIPTION =
       (ADDRESS = (PROTOCOL = TCP)(HOST = oradb.subnet.vcn.com)(PORT = 1521))
       (CONNECT_DATA =
         (SERVER = DEDICATED)
         (SERVICE_NAME = jdeorcl.subnet.vcn.com)
     )
   )

7. Save and close the tnsnames.ora file.
8. Navigate to the location of the E1Local Network, which is typically:

   C:\JDE\DEP\Oracle\E1Local\NETWORK\ADMIN

9. In the above directory, edit the tnsnames.ora file to add the same listener details that you obtained and copied in a previous step in this procedure.

10. Save and close the tnsnames.ora file.
11. Validate the configuration of the tnsnames.ora file by running ActiveConsole.exe and logging in to the DEP920 environment.