Restoring the Full Productive State of the J2EE Engine (SAP Library

Restoring the Full Productive State of the J2EE Engine

Use

After finishing with all debugging tasks, you need to restore the normal operation of the J2EE Engine cluster. Having the debug nodes isolated from the cluster communication and load-balancing mechanism is not efficient for the optimal J2EE Engine performance, so you need to return the state of the J2EE Engine as it was before.

Note

If you created separate Java instances or nodes specially for debugging, you do not have to follow the steps in this procedure. You should only delete the instances or nodes after the debugging instead.

Procedure

1. In the J2EE Engine view, select the server process you debugged, and choose Disable debugging of process from the context menu.

The J2EE Engine is automatically restarted, which may take some time. Use the Refresh button to update the status displayed in the J2EE Engine view.

2. Start the Config tool and connect to the J2EE Engine database.

3. In the left pane, unfold the instance to which the process belongs, and then select the process node.

4. In the right pane, enter the Debug tab.

5. Uncheck the Enabled debug mode and Restricted load balance properties.

6. Choose Apply changes in the toolbar.

7. Restart the server process so that the changes can take effect.

If you have done all steps correctly, you see the following status in the J2EE Engine view:

Property	Value
Productive Use	NO
Restricted Load Balancing	NO
Debug Mode	OFF
State	Running

Result

The nodes you previously used for debugging are now active participants in the J2EE Engine cluster communication and load-balancing mechanism, and are capable of servicing customer requests. This increases the cluster capabilities in comparison with its capabilities during the debugging. Note that after this procedure the nodes are still debuggable, not productive, meaning that you can still perform remote debugging on them if a problem occurs in a deployed application.