You can create a server to identify the WebSphere® v6.0 run-time environment for testing or publishing your project resources.
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 run-time 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.0
|
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. This option is available only when running a local server and not available when running a remote server. If this check box is clear, the workbench runs the server with resource on the server. This publishes your application on the targeted server. By default, the Run server with resources within the workspace check box is enabled. |
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 authentication settings to a secured WebSphere Application Server v6.0. |
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. |
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.
If you used the Detect button the server tools, pre-fills the Server Name field with the server instance of the WebSphere Application Server.
If you used the Detect button the server tools can not pre-fill this field, you will need to provide this information.
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.