Define a WebSphere server for publishing

The server tools feature simplifies the effort required to test and publish applications on a variety of servers. If your target server is WebSphere Application Server running locally or on a separate machine, provide information about how the server tools should transfer files to the server. You do this when you define the server.

Prerequisites: Before you can test or publish your projects on a separately installed copy of WebSphere Application Server, install the following software on the same machine as the server:

To define a WebSphere server:

  1. On the first page of the New Server wizard ( File > New > Other > Server > Server), select WebSphere v5.0 Server or WebSphere v5.1 Serveras the server type.

  2. In the Host name field, type the fully qualified DNS name or the IP address of the machine that WebSphere Application Server is running on. The field is pre-filled with a default localhost address. For more information about any fields on this and other wizards, select the field and then press F1. Click Next.

  3. To allow multiple users to test concurrently on the same machine, select This server is shared by multiple development clients.

    Note: The server administrator has to perform some steps to enable test environments for multiple users. For instructions on setting up the server for multiple developers, see the list of related tasks at the end of this topic.

  4. Click Next. If security is enabled for Agent Controller on a remote machine, you will be prompted for a user name and password for the remote machine.

  5. The WebSphere Server Settings page of the wizard allows you to provide additional information about the server. Note that all paths on this page are as seen from the machine where WebSphere Application server is installed. In the WebSphere installation directory field, type the path where you installed WebSphere Application Server. This path is the same as the WAS_ROOT path mappings. For example, if you have installed WebSphere Application Server in C:\Program Files\WebSphere\AppServer, then use this as the WebSphere installation path.

  6. If you want to use the default WebSphere deployment directory, select that check box. If you select this option and then you publish to this server, the default WebSphere Application Server server configuration file is replaced with the published version. (If you also select Generate plug-in configuration file, the plugin-cfg.xml file is also replaced at publication time). For more information about the replacement of this file, refer to the related topic about reverting the published server configuration to the original server configuration.

  7. If you do not want to use the default WebSphere deployment directory, clear the Use default WebSphere deployment directory check box and in the WebSphere deployment directory field, type the path and directory where the Web application and server configurations will be published. This directory must be an existing directory that can be seen from the remote server. If you follow WebSphere naming conventions and install WebSphere Application Server in the C:\Program Files\WebSphere\AppServer directory, then the WebSphere deployment directory is C:\Program Files\WebSphere\AppServer. When you publish to WebSphere Application Server, the server configuration and the Web application will be placed in subdirectories called config and installedApps respectively.

  8. If your application requires DB2, in the DB2 driver location field, specify the location where the DB2 classes reside on the machine where WebSphere Application Server is installed, for example C:\SQLLIB\java\db2java.zip. You can set a default value as a preference (Window > Preferences > Server > WebSphere).

  9. Select the platform that the server runs on. If you select iSeries, also specify the WebSphere user install root and the name of the server instance you have created in iSeries.

  10. Click Next to display the Publishing Options page of the wizard.

  11. Defining a Remote File Transfer mechanism. Click next.

  12. Select the Use default port numbers radio button to use the default HTTP port numbers.

  13. Select the Use consecutive port numbers radio button if you want to keep the port numbers within a range. Type the first port number of the range in the First port number field. This field might be pre-filled with a value if this setting has already been defined by a server administrator. Click Next.

  14. The Add and Remove Project wizard opens. In the Available projects list, select the project that you want to publish and click Add. The project appears in the Configured projects list.

  15. Click Finish to create a remote server. The server appears in the Servers view.

 

Parent topic

Publishing projects to a WebSphere Application Server v5.x