Creating a WebSphere Application Server v6.x

You can create a server to identify the WebSphere® Application Server v6.x runtime environment for testing or publishing your project resources.
There are two types of application servers you can create: To create a WebSphere Application Server v6.x:
  1. When creating a server, in the select the server type list, select WebSphere v6.x server.
  2. Click Next to configure additional settings.
  3. If the workbench does not have a reference to the installed server runtime environment, the New Server wizard is going to prompt you for this information in the WebSphere Runtime page. Otherwise, the WebSphere Runtime page does not display in the New Server wizard.
    1. (Optional) In the Name field, type the name assigned to the server.
    2. In the Installation directory field, type or browse to the path where the WebSphere Application Server is installed. This path is the same as the WAS_ROOT path mappings as defined by the WebSphere server configuration. For example, if you have installed WebSphere Application Server in c:/WebSphere/AppServer directory, then use this as the WebSphere installation path.
    3. Click Next to configure WebSphere Application Server settings.
  4. On the WebSphere Server Settings page, specify one or more of the following settings:
    Option Description
    WebSphere profile name In the drop-down list, select the name of the profile of WebSphere Application Server. A profile is the set of files that define the runtime environment. For information on creating a profile, see Creating a profile.

    This option is available only when running a local server and not available when running a remote server.

    Server connection type and admin port Use the radio button to select whether to use the remote method invocation (RMI) or Simple Object Access Protocol (SOAP) port for communication between the development environment and the server. These ports are used for making Java™ Management Extensions (JMX) connections with the server.

    The RMI (ORB bootstrap) port is designed to improve performance and communication with the server. The default setting of the RMI port is port 2809 and selected when working with a local server.

    The SOAP connector port is designed to be more firewall compatible. The default setting of the SOAP port is port 8880 and selected when working with a remote server.

    Tip: If there is a firewall between the development environment and the server, use the SOAP connector port rather than the ORB bootstrap port. For more details on this option, see Setting the connection to the WebSphere Application Server v6.x
    Run server with resources within the workspace This check box enables you to run your application from within the workbench without publishing to the server. As a result, your application will not get copied to the server under the installedApp folder (x:/profiles/profile_name/installedApps, where x is the installation directory where WebSphere Application Server is installed). This option is available only when running a local server and not available when running a remote server. For local servers, this check box is enabled by default.

    If this check box is clear, the workbench runs the server with resource on the server. This publishes your application on the targeted server. As a result, the enterprise application (EAR) file is automatically published to the server by expanding into the installedApps folder (x:/profiles/profile_name/installedApps, where x is the installation directory where WebSphere Application Server is installed).

    Security is enabled on this server Enables the security feature that comes with WebSphere Application Server. When security is not enabled, all other security settings are ignored. For more details about this security option, see Specifying administrative settings to a secured WebSphere Application Server v6.x.
    Server name Specify the name of the server instance of WebSphere Application Server. The server name is the same as the server-level name in the server configuration. The server instance with the given instance name must already be created on the server. If the target server is a Network Deployment (ND) server, use the server name of the deployment manager, for example dmgr.
  5. If the server you are defining is started, click on the Detect button. Otherwise, you will need to manually provide the information under the Server type section.
    1. Use the radio buttons to select the WebSphere Application Server edition:
      • Base, Express or unmanaged Network Deployment server: Specifies you are connecting to an application server that is a stand-alone (unmanaged). Do not use this option with a federated (managed) WebSphere Application Server in a Network Deployment cell; instead select the Network Deployment server radio button.
      • Network Deployment server: Specifies you are connecting to an application server that is federated (managed).

      If you used the Detect button the server tools identifies the WebSphere Application Server edition by selecting the appropriate radio button under the Server type section.

    2. For Base, Express or unmanaged Network Deployment server, in the Server name field, type the name of the server instance. The server name is the same as the server-level name in the server configuration. The server instance with the given instance name must already be created on the server.

      If you used the Detect button the server tools, pre-fills the Server Name field with the server instance of the WebSphere Application Server.

    3. For Network Deployment, in the Network Deployment server name field, type the name of the server instance. The server name is the same as the Network Deployment server name. The server instance with the given instance name must already be created on the server. The server name is in the form of <cell name>/<node name>/<server name>.

      If you used the Detect button and the server tools cannot pre-fill this field, you will need to provide this information.

  6. (Optional) Click Next to add the projects of your application to the server. On the Add and Remove Projects page, under the Available projects list, select the project that you want to test and click Add. The project appears in the configured projects list.

    Depending on what type of projects you are adding to the server, the Next button might be enabled. If the Next button is available and selected, the Select Task page opens. In the Select Task page, use the check boxes to select tasks to be performed on the server, such as create tables and data source, and deploy EJB beans.

  7. Click Finish. The server tools automatically completes the following tasks for you:
    • Creates the server.
    • Adds your project to the server.
    • The Servers view displays the status of the server, for example if the server is Started or Stopped.
Related concepts
Servers view
Working with a WebSphere Application Server Network Deployment environment
Related tasks
Publishing settings for a WebSphere Application Server v6.x
Defining the installed server runtime environments preferences

Feedback