3.4.1 Notes on J2EE Server management
- Organization of this subsection
(1) Notes on the RMI registry
For, Management Server monitors J2EE Server with the RMI registry operating on J2EE server. Thus, if the information of the RMI registry managed by the Management Server does not match with the information of the RMI registry of the actually operating J2EE server, then monitoring might fail. Information of the RMI registry managed by the Management Server is updated at the following timings. Note that the information must not differ from that of the RMI registry operating on J2EE Server.
-
When you perform a recovery of component information with Cosminexus Management Server settings of the management portal
-
When you click the Apply button in the Environment settings of the logical server on the management portal
-
When reading the server settings from the Environment Settings of the logical server on the management portal
-
When cmx_build_model.exe command is executed
-
When cmx_change_model.exe command is executed
For operations of the management portal, see the following points in the uCosminexus Application Server Management Portal User Guide.
-
8. Cosminexus Management Server settings
-
10. Environment settings of the Logical server
For details on each command, see the following points in the uCosminexus Application Server Command Reference Guide.
-
cmx_build_model (Generating information model of Web system)
-
cmx_change_model (Changing information model of Web system)
(2) Notes on starting J2EE applications when you start the J2EE server
The J2EE applications, which are running when the J2EE server stops, auto-start when the J2EE server starts. However, if an error occurs when a J2EE application starts while the J2EE server is being started, the J2EE application might fail to start. In such cases, the J2EE application stops. Even if the J2EE server is restarted in this state, the J2EE application remains in the stopped state and does not start.
For example, in a J2EE application for which servlet error reporting has been set up, if an exception occurs during servlet initialization, the J2EE application fails to start and the application stops. For details on the error report settings, see 9.16 Error notification settings for servlets and JSPs in the uCosminexus Application Server Application Setup Guide.
Use one of the following methods to check whether a J2EE application has started normally and to take action:
-
Check the status of the J2EE application.
-
Detect the failure in starting the J2EE application and then start the J2EE application manually.