Oracle® Solaris Cluster Data Service for Oracle JD Edwards EnterpriseOne Enterprise Server Guide

Exit Print View

Updated: July 2014, E40215–01
 
 

How to Verify the JD Edwards EnterpriseOne Enterprise Server Installation and Configuration in a Multi-Master or Multi-Instance Configuration

This procedures verifies that you installed and configured Oracle Solaris Cluster HA for JD Edwards Enterprise Server correctly for a multi-master or multi-instance configuration.

  1. Ensure that you can successfully connect to the JD Edwards EnterpriseOne Enterprise Servers from a client and that all the servers are running.
  2. On one of the cluster nodes, kill the Enterprise Server process.

    The Fault Monitor must detect the killed process and restart the JD Edwards EnterpriseOne Enterprise Server.

  3. Verify the status of the JD Edwards EnterpriseOne Enterprise Server.
    # su - jde_User -c "/u01/jdedwardsppack/e910/system/bin32/jdejobs"
    # su - jde_User -c "/u01/jdedwardsppack/e910/system/bin32/porttest JDE JDE DV910"
  4. If a JD Edwards HTML Web Server is configured for the corresponding JD Edwards EnterpriseOne Enterprise Server on Oracle WebLogic Server, deploy a sample application that consists of the WebLogic server instances configured for the JD Edwards HTML Web Server.
  5. Use a proxy web server to access the sample application.
  6. Shut down one of the nodes and access the application using the proxy web server address.

    Shut down one of the nodes and try to access the application using the proxy web server address. You should still be able to access the application.

    If the previous steps are successful, you have correctly configured Oracle Solaris Cluster HA for JD Edwards EnterpriseOne Enterprise Server in a multi-master or multi-instance configuration.


    Tip  -  After the JD Edwards EnterpriseOne Enterprise Server are in production under Oracle Solaris Cluster control, do not start or stop the servers manually or through the Server Manager Management Console. If you do need to perform maintenance on the servers, you must first disable their associated resources.