Page History

...

1. In the Java EE perspective, open the Servers view.
2. On the Server panel, right click on the server to be started.
3. On the resulting context menu, click Debug.

Local deployment

Use this procedure to deploy Java EE assets to a local server.

1. In the Java EE perspective, select the Project view and right click the Java EE project you want to deploy. Select Run As, Run on server
2. On the Run on server panel, if you have an existing server, keep the Choose an existing server option and select the server. If you don't have a WASCE server defined, select the Manually define a new server option and select the WASCE server.
3. Click Finish. The WTP server adapter will deploy the Java EE assets shortly. If the server is not started, the WTP server adapter will start the server and deploy the Java EE asset when the server has initialized.

Removing an asset that has been published to the server

Once an asset has been published to the server, you must use the tool's Add/Remove project option if you want to remove it from the server. If you simply remove the asset without removing its project, the asset will remain deployed on the server.

1. In the Java EE perspective, the select the Server view.
2. On the Server panel, right click on the server where the asset was deployed.
3. On the resulting context menu, click Add/Remove Projects.
4. On the selection panel, click on the asset to undeploy and click the <Remove button to move it from the right to the left list. Click Finish.

Remote deployment

You can use the same steps discussed above to deploy a Java EE asset to a remote server, but there are additional considerations.

• To define a remote server, you must first define a local server and then change the value of its hostname attribute to the name of the remote server's host. This is required because the Eclipse framework must use the class libraries from the local server.
• You cannot use Eclipse to start, stop, or restart the remote server. You cannot use Eclipse to start the remote server in debug mode. Often, this limitation makes it more convenient to develop and debug your Java EE assets using a local server and then switch to a remote server when you need a common server to integrate your assets with assets from other developers.
• If there is a firewall between your system and the target server, it must be configured to permit both HTTP and RMI requests to flow between your system and the server's host. When the server is installed, the initial HTTP port is 8080 and the initial RMI port is 1099. If the target server has been configured to use different ports, the firewall must be configured to use those ports instead.
• Make sure the target system can be contacted by ping command.
• The remote server must be running when you invoke the deploy command. When you deploy or refresh your Java EE asset, the files will be copied across the network, saved as temporary files, and then deployed.

Debugging a remote application on an already running server

...