Business Function Processing Problems

The Oracle JD Edwards EnterpriseOne configurable network computing (CNC) solution enables developers and administrators to map business functions to one or more application servers for logic processing. When a problem occurs on the server, the software attempts to reconnect to the application server so that the business function can run. If the software can reconnect to the server and run the business function, work proceeds uninterrupted.

However, these circumstances can complicate business function processing:

• The client workstation cannot reconnect to the application server because a server process has died.

• Business function processing creates cache, or state information, on the application server whose process has died.

• The business function causes one or more processes to die on the server.

• The client workstation cannot reconnect to the application server because the server machine has gone down and the server machine is part of a server cluster.

When the client workstation cannot communicate with the server, the software redirects business function processing to a secondary server. A list in the CallObject code designates the name of the original server and the name of the secondary server to which future calls should be rerouted.

Note: The default configuration is that no secondary server is defined during the JD Edwards EnterpriseOne installation process. Defining a server will require changes to the OCM mappings. If you do not define a secondary server and failover occurs, the software remaps business function processing from the failed server to the client workstation.

When business function processing creates cache on the application server where a process has died, the client workstation reconnects to the application server, but the user must exit the application and restart it.

When a business function causes one or more processes to die on the server, the client workstation reconnects to the server. Because the business function is causing the jdenet_k process to die, JD Edwards EnterpriseOne fails the business function call.

When the client workstation cannot communicate with a server in a server cluster, the software recognizes that the server is part of a cluster and continues to try to reconnect. The transfer of control from one server in a cluster to another server in a cluster can take several minutes.

The JD Edwards EnterpriseOne Configurable Network Computing solution provides a methodology that handles business function failure and enables you to continue working, even when a server has failed or a kernel process has died, ending the processing of logic on an application server. In addition, the software writes a message to the jde.log whenever a failover occurs, enabling you to troubleshoot the problem.