Managing servers

You can use the server tools views to manage servers. The following tasks may be included as part of the development path:

• Adding projects to a server
  Once you have created a server, you need to create a relationship between the projects that contain the files you want to test and your server.

• Removing a project from a server
  To remove a project from a server:

• Starting a server
  When you are ready to test your projects, start a server. In some situations, listed below, the server tools start a server for you automatically. For more information on which test server will start, refer to the list of related topics at the end of this topic.

• Stopping a server
  You can stop the server from the Servers view.

• Clean projects published on the server
  You can use the clean option available in the Servers view to remove any invalid resources from the server before doing a full republish. This helps remove by-products generated as a result of the publishing process. When you find there is old code or an invalid state of code running on the server, try using this clean option to see if this helps remove these invalid states from the server.

• Setting a default server
  A default server is the server that you want to use when a project has more than one server defined.

• Displaying or hiding the metadata of the server
  On the workbench, you have the option to display or hide the metadata of the server.

• Generating WebSphere administrative commands to assist in developing Jython scripts
  Use the WebSphere® Administration Command assist tool to generate WebSphere administrative (wsadmin) commands for Jython scripting language as you interact with the WebSphere Administrative Console.

• Accessing the Administration Console
  The server tools provide access to the WAS Administration Console. You can use the advanced functions provided in the administration console to change settings in your configuration that is defined to use WAS.

• Backing up server configuration from a WAS
  The Server Configuration Backup wizard packages the server's cell configuration files into a configuration archive (.car) file.

• Restoring server configuration to a WAS
  The Server Configuration Restore wizard applies the server configuration that is defined in the configuration archive file (.car) to the server profile associated to the selected server in the Servers view.

• Migrating server configuration files from WAS V6.0.x to V6.1.x
  The Server Configuration Backup and Server Configuration Restore options available in the workbench are not the correct way to migrate an existing WebSphere® Application Server V6.0.x profile into a V6.1.x profile. Instead, the Migration wizard from the WAS V6.1.x should be used.

• Running external administrative scripts
  You can run administrative scripts from within the development environment, without having to switch to the non-graphical command interpreter, WebSphere® administrative scripting tool (wsadmin).

• Keeping a WebSphere server running after exiting the development environment
  Learn how to keep the server running after you shut down the development environment.

---