uCosminexus Application Server, Application Development Guide
![[Contents]](FIGURE/CONTENT.GIF)
![[Glossary]](FIGURE/GLOSS.GIF)
![[Index]](FIGURE/INDEX.GIF)
![[Back]](FIGURE/FRONT.GIF)
6.4 Changing the server configuration
You can use a server editor to change the server configuration. To change the Cosminexus J2EE server configuration:
- In the Server view, double-click Cosminexus J2EE server to change the configuration.
The Server Overview page appears.
![[Figure]](FIGURE/ZU131030.GIF)
- Change the following items to any value:
Item name |
Explanation |
General Information |
You can change the server name displayed in the Server view. Do not change the runtime environment. |
J2EE Server Information |
You can check the display name of the J2EE server, the logical server name, and the host name of the J2EE server. |
J2EE Server Deployment |
You can change the directory for allocating the J2EE applications. Specify an absolute path for the directory. |
J2EE Server Ports |
You can change the HTTP access port and debug port used when a J2EE application is debugged from the Debug On Sever dialog box, or when a J2EE application is executed from the Execute On Server dialog box.
You can change the debug port only when the remote J2EE server is used.
The default value of the HTTP access port is 80. You can specify an integer in the range from 1 to 65535.
The default value for the debug port is 3999. You can specify an integer in the range from 1 to 65535. |
- Click the Management Portal tab if you are using the management portal.
The Management Portal window appears.
![[Figure]](FIGURE/ZU131040.GIF)
- Organization of this section
- (1) Notes on changing the configuration of a J2EE server
(1) Notes on changing the configuration of a J2EE server
Note the following points when you change a J2EE server configuration:
- The J2EE application to be published is created in the deploy directory. You can specify a short path for the directory as and when required, if the deploy directory and J2EE application has a deeply nested hierarchy.
- Do not specify the same deploy directory for multiple servers when publishing a project. If you specify the same deploy directory, an error might occur.
- If an attempt to obtain the J2EE server information fails when the Server Overview page is displayed, check and, if necessary, revise the settings of Remote Management. After you revise the settings, open the server editor again.
- In the Preferences dialog box, click Server, Remote Management, and then Connection page, to set a timeout value for the J2EE server operations. To implement timeout correctly, specify a value greater than the setting on the Connection page, in the Timeout section of the Server Overview page.
- The created deploy directory will not be deleted even if you delete the server. Delete the deploy directory manually as and when required.
- Do not specify a path consisting of only backslashes (\) or only slashes (/) for the deploy directory.
- If you want to debug the J2EE applications to be operated on local J2EE server by using Eclipse, use the port number allocated according to the OS as debug port. To avoid conflict with the port number used in other programs, start the other programs that use the port number before starting the J2EE server as and when required.
All Rights Reserved. Copyright (C) 2012, 2013, Hitachi, Ltd.