1. Deploying JD Edwards EnterpriseOne Trial Edition on Oracle Cloud Infrastructure Learning Path
  2. Performing Optional Tasks

Performing Optional Tasks

This section shows you how to perform optional tasks after your Trial Edition is deployed.

Optional tasks include:

  • Checking JD Edwards EnterpriseOne Services Status
  • Displaying Trial Edition URLs
  • Configuring Public IP Address/Internal Hostname on Client Machine
  • Working with JD Edwards EnterpriseOne Security

Prerequisite

  • A deployed instance of JD Edwards EnterpriseOne Trial Edition for Oracle Cloud Infrastructure Compute Classic

Checking JD Edwards EnterpriseOne Services Status

Important - Restarting the OCI Instance for Trial Edition:

To restart the Trial Edition instance from Oracle Cloud Infrastructure you should only do a standard reboot or shutdown and avoid selecting the checkbox for Force Reboot. Using Force Reboot could potentially leave Trial Edition in an unstable state. You can also reboot the instance from your Linux session with the command sudo reboot. The EnterpriseOne services should start automatically and in the correct order after the instance is back online. To ensure that the instance has fully recovered after reboot, you can use the jde_status command. In addition, the following manual scripts are available to stop and start the individual JD Edwards EnterpriseOne services.

This section describes how to confirm the services have started, and how to manually stop and start services if required.

  1. From an ssh command line, login to opc and then switch to the root user. For example, you could use these commands:

    ssh opc@<public_ip_address_of_the_instance>

    sudo su - root

  2. As the root user, you can use these commands to check that each of the services are running:

    • jde-status (shows all services and calls all the below status scripts)

    • jde-db status
    • jde-ent status
    • jde-html status
    • jde-bip status

    • jde-sm status

  3. You can manually shutdown services using these commands:
    • jde-bip stop
    • jde-html stop
    • jde-ent stop
    • jde-db stop
    • jde-sm stop
  4. You can manually start services using these commands:
    • jde-db start
    • jde-ent start
    • jde-html start
    • jde-bip start
    • jde-sm start
  5. For log locations, refer to the run time messages of the start and stop scripts.

  6. Verify you can access the HTML Web Server at this URL:

    https://<Public IP:port>/jde

  7. Verify the Orchestrator Studio component URL:

    https://<Public IP>:7077/studio/studio.html

  8. Verify the Server Manager Console at this URL:

    https://<Public IP>:8998/manage

Tip:

You can use a script to display the system-assigned public IP address as described in the next section of this Learning Path entitled: Displaying Trial Edition URLs.

Displaying Trial Edition URLs

As the root user, you can use this command to display the Trial Edition URLs:

jde-url

For example:

URLs Used by Server Manager

Configuring Public IP Address/Internal Hostname on Client Machine

Without this step, the JD Edwards EnterpriseOne application websites can only be accessed using the Public IP Address in a browser. This step allows access using the hostname also as a convenience. The steps given below assume that you have not configured a public web entry point for the JD Edwards EnterpriseOne application tier. In that case you need to manually add the public IP address/Internal DNS hostname of the JD Edwards EnterpriseOne application tier in the hosts file of the client machine.

Alternatively, these steps can be replaced by contacting your site’s network administrator and having the address and hostname setup in DNS.

Access from a UNIX Host

Modify the /etc/hosts file as shown below. For example:

  • public IP: 129.144.000.999
  • public hostname: demojde1.domain.com

Using the above example values, the /etc/hosts file must contain this line:

129.144.000.999 demojde1 demojde1.domain.com

Access from a Microsoft Windows System

Modify the C:\Windows\System32\drivers\etc\hosts file as shown below. For example:

  • public IP: 129.144.000.999
  • public hostname: demojde1.domain.com

Using the above example values, the C:\Windows\System32\drivers\etc\hosts file must contain this line:

129.144.000.999 demojde1 demojde1.domain.com

Working with JD Edwards EnterpriseOne Security

A minimal JD Edwards EnterpriseOne security definition has been shipped with your Database Server. Follow the instructions in the JD Edwards EnterpriseOne Applications Release 9.2 Installation Guide for Oracle on UNIX to change the passwords within EnterpriseOne for JDE and PS920 so they match any changes you make to the passwords for the Oracle Database users.

Important:

It is recommended to change your security list after configuring Trial Edition to only allow traffic from certain IP addresses or a CIDR (range of IP addresses). This can be accomplished by only opening ports to specific Public IP addresses by using the OCI function allowlist (formerly whitelist) to specify a CIDR range or specific IP address that will be allowed to access each port. For example, you can use a source CIDR using the format 123.123.123.0/24, to open an IP port for a range of addresses 123.123.123.0 -123.123.123.255 (256 IP addresses).

The following screen demonstrates the opening of the four Trial Edition web enabled ports to a CIDR value of 123.123.123.0/24.URLs Used by Server Manager

If you do not know the CIDR used by your organization, you should request this information from your network administrator. Alternately, you can specify your exact IP address using the format 123.123.123.123/32 which only allows traffic from a single specific public IP address 123.123.123.123.

After locking down these ports, you will also have to create one additional security rule to allow the Trial Edition instance to make calls from its own public IP address. In this example, the Trial Edition instance public IP is 121.121.121.121 and it is allowed to call any port.

Trial Edition instance public IP