H Troubleshooting

This appendix contains the following topics:

H.1 Enable Debugging on the AIS Server

Turn on debugging on the AIS Server to generate an AIS Server log file. The log file includes information for all orchestrations unless you activate user level logging. User level logging generates logs based on the EnterpriseOne user ID. See "Available Log Files" in the JD Edwards EnterpriseOne Tools Server Manager Guide for more information about generating and managing log files.

The details in the log file can help you troubleshoot and resolve orchestration issues and EnterpriseOne connection issues.

H.2 Troubleshooting Orchestration Runtime Issues

Interruption of EnterpriseOne Web Client When Running the JD Edwards EnterpriseOne Orchestrator Client

If a user is signed in to the EnterpriseOne Web client and then opens the Orchestrator Client in a new tab in the same browser, the user can no longer perform any actions in the EnterpriseOne Web client. The EnterpriseOne Web client session is interrupted and prompts the user to sign in again.

This issue is caused by an Orchestrator Client JSESSIONID cookie conflict with WebSphere and occurs when both the EnterpriseOne AIS Server and EnterpriseOne HTML Server are deployed on WebSphere on the same host. Both servers use the JSESSIONID cookies for session management, which causes a conflict because both JSESSIONID cookies are configured with a generic path.

To fix this issue, set up the cookie path of the AIS Server:

  1. In the WebSphere administration console, navigate to the server: Application servers, ais_server_name.

  2. Under Container Settings, select Session Management.

  3. Click Enable Cookies link.

  4. Under Cookie path, make sure the "Set cookie path" option is selected and set the cookie path to:

    /jderest

  5. Restart the server.