Servers view

Use the Servers view to manage servers. This view lists of all your servers and projects that are associated with each server. A project appears under a server when a project from the workbench is added to the server. You can use this view to start, start in debug mode, restart, or stop the servers. You can also use the Servers view to determine the status and state of a server or the projects added to the server from the workbench.

Graphic depicting a screen capture of the Servers view.

Use the Servers view for the following tasks:

Create a server
Edit a server
Delete a server
Start a server in debug mode
Start a server
Start a server in profiling mode
Restart a server in debug mode
Restart a server
Restart a server in profiling mode
Stop a server
Publish your application
Restart your application
Tip: The difference between restarting versus publishing an application on the server is that restarting an application stops and starts the application on the server; whereas, publishing an application runs the code generation tools on the application.
Deactivate server
Activate server
Switch configuration
Monitor server ports
Add and remove projects from a server
Run WebSphere® administration command assist, which is used for generating WebSphere administrative commands, to help develop Jython scripts.
Run administrative console
Create tables and data sources
Server Configuration Restore
Server Configuration Backup
Run administrative script
Run Universal Test Client
Restart Universal Test Client
Reconnect debug process

Server State

The Servers view shows the current state of all the servers.

The following table lists the possible states of the server:

Table 1. Server states. Description of the server states.
Server state	Description of state
Starting	The workbench is connecting to the server and is beginning the server process. Tip: Verify that the actual server is started.
Started	The workbench is successfully connected to the server. Both the workbench and server are ready to run applications on the server.
Debugging	The workbench is successfully connected to the server. Both the workbench and server are ready to diagnose applications on the server.
Profiling	The workbench is successfully connected to the server. Both the workbench and server are ready to issue a performance analysis on applications that are running on the server.
Stopping	The workbench is connecting to the server and is ending the process on the server.
Stopped	The server process is complete. Or the workbench is unable to connect to the server. Tip: If you are connecting to the server and the state of the server is stopped, verify that the server is started and the port information is correctly provided in the workbench. For a WebSphere Application Server, a Test Connection link is available in the server editor to verify that you have a successful connection between the workbench and the server. Before you can use the Test Connection link, you must start the server.
Inactive	Server is not active

Server Status

The Servers view also displays the current status of all the servers. Depending on the state of the server and the preference options that are selected for that particular server, the workbench determines the server actions that may be taken. Use the status as an indicator for possible actions that you may want to take.

The following table lists the possible server status:

Table 2. Description of the server status
Server status	Description of status
Synchronized	Both the server and the applications are in synch.
Publishing	Files (projects and resource files) are copied to the correct location for the server to find and use them.
Restart	The server needs to be restarted in order for the changes to take place.
Republish	Either the server or the applications or both have changed. The changed files need to be updated on the server.
Restart and republish	Either the server or the applications or both have changed. When the server is restarted, the changed files are also republished.

Project State

The Servers view might show the current state of the application. When the Servers view does not display a current state for the project, the workbench cannot retrieve the state of the project from the server or the server does not support this function.

If a project name appears in italic font style, then the project is not uploaded to the server. After the project is published into the server, the project name switches to the typical font style used in the Servers view.

The following table lists the possible states of the project:

Table 3. Project states. Description of project states.
Project states	Description of states
Installing	The workbench is publishing a new application onto the server.
Starting	The application is changing from a Stopped state to a Started state. Application is starting to run but is not fully running yet. Or, it cannot fully start because one or more application modules are stopped.
Started	The application on the server is ready to run on the server.
Updating	The application is already installed on the server. File changes to the applications are being published onto the server.
Stopping	The application is changing from a Started state to a Stopped state. The application is running.
Stopped	The application on the server is ended and is not taking server requests to run.

Project Status

The Servers view might display the current status of the application is either synchronized or republished. When the Servers view does not display a current status for the project, the workbench cannot retrieve the status of the project from the server, the server is stopped or the server does not support this function.

The following table lists the possible project status:

Table 4. Description of project status
Project status	Description of status
Synchronized	Both copies of the application files on the server and in the workbench are matching.
Republished	The copy of the application files on the workbench has changed and does not match the copy on the server. The server needs to be updated.

Feedback