uCosminexus Application Server, Application Development Guide
![[Contents]](FIGURE/CONTENT.GIF)
![[Glossary]](FIGURE/GLOSS.GIF)
![[Index]](FIGURE/INDEX.GIF)
![[Back]](FIGURE/FRONT.GIF)
![[Next]](FIGURE/AFTER.GIF)
(1) Debugging from a shortcut
- In the Project Explorer view, open the Java source file of the project to be debugged, and set up the breakpoint.
- In the Project Explorer view, either choose the project to be debugged or open the Java file using an editor.
- From the Eclipse menu bar, choose Run - Debug As - Cosminexus Batch Application.
The debugging process is started. If the batch server is not running, the batch server will start.
If the management user authentication in the Management Server Management User settings is specified as Authenticate, and if the connection to the Management Server remote management is not established, the Log in - Remote Management dialog box appears. Enter the management user ID and the password, and then click the OK button.
If the breakpoint is reached, the processing is interrupted, and a message appears for confirming whether to open the Debug perspective. If you click the Yes button, the Debug perspective appears.
Note that if you want to restart the processing interrupted at breakpoint, choose Run - Resume from the Eclipse menu bar.
(2) Debugging by displaying the Debug Configurations dialog box
- In the Project Explorer view, open the Java source file of the project to be debugged, and then set up the breakpoint.
- From the Eclipse menu bar, choose Run - Debug Configurations.
The Debug Configurations dialog box appears.
- Select the created start configuration, and then click the Debug button.
The debugging process is started. If the batch server is not running, the batch server will start.
If the management user authentication in the Management Server Management User settings is specified as Authenticate, and if the connection to the Management Server remote management is not established, the Log in - Remote Management dialog box appears. Enter the management user ID and password, and then click the OK button. If the breakpoint is reached, the processing is interrupted, and a message appears asking the user whether to open the Debug perspective. If you click the Yes button, the Debug perspective appears.
Note that if you want to restart the processing interrupted at breakpoint, choose Run - Resume from the Eclipse menu bar.
(3) Precautions for debugging
- If no batch servers are set up, an error occurs.
- When debugging starts, if there are multiple main classes to be debugged or batch servers that execute debug, the Select Batch Application dialog box appears. Specify the main classes to be debugged or batch servers that execute debug.
- If same start configurations are to be debugged multiple times, the Select Batch Application dialog box appears. Select the start configuration for debugging.
- If you change the settings of a running batch server using the management portal or the Smart Composer functionality, restart the batch server.
- Since the batch server starts during the initial debugging of the batch applications, the debugging of the batch applications takes time.
- If the automatic restart of the batch server is enabled in the Management Server settings, the batch server restarts automatically, when an attempt to forcefully terminate the batch applications fails. While the batch server is restarting, you cannot operate the batch server. Also, when the restarting of the batch server started in the debug mode is complete, the debug connection (reconnect) to the batch server is automatically established.
- If a batch application is interrupted at a break point, and you forcefully terminate the batch application, stop the batch server, or end Eclipse, the batch application might stop after executing the number of steps on and after the break point, instead of stopping at the break point.
All Rights Reserved. Copyright (C) 2012, 2013, Hitachi, Ltd.