Configuring a WebSphere Application Server
A server is a definition that identifies where an application is going to be tested or published and points to a specific runtime environment such as a WebSphere® Application Server on a local server or on another server. The following topics describe how to set up a WebSphere Application Server, such as setting up ports or data sources.
- Profile creation for WebSphere Application Server traditional
A profile is the set of files that define the runtime environment of a WebSphere Application Server. - Setting status updates for a WebSphere Application Server
You can specify how long the development environment is going to wait to update the status of the server that is running in real time. - Setting the connection to the WebSphere Application Server
The administrative ports are used to communicate requests between the workbench and the server. - Optimizing starting the WebSphere Application Server for development
There are two options available to help reduce the start time of the WebSphere Application Server: Start server with a generated script and Run -Xquickstart in the JVM settings if applicable. These options are available as check box options in the workbench. - Switching to HPEL mode for logging and tracing on WebSphere Application Server V8.0 or later
There are two modes of logging and tracing for WebSphere Application Server V8.0 or later, which are basic mode and High Performance Extensible Logging (HPEL) mode. HPEL is designed to provide faster log and trace handling capabilities than the basic mode. - Keeping the WebSphere Application Server running after exiting the development environment
To specify that the server will continue running after you shut down the development environment. - Changing the hypertext transfer protocol settings for WebSphere Application Server
Hypertext transfer protocol (HTTP) is an Internet Protocol that is used to transfer and display hypertext and XML documents on the web. Hypertext transfer protocol secure (HTTPS) is an encryption and authentication layer added to HTTP, which is used by web servers and web browsers to transfer and display hypermedia documents securely across the Internet. - Publishing settings for WebSphere Application Server traditional
Publishing involves copying files (application, resource files, and deployment descriptor files) to the correct location for the server to find and use them. You can either publish your application on the server or run your application within the development environment without copying the application into the directories of the server. - Specifying administrative settings to a secured WebSphere Application Server traditional server
If your WebSphere Application Server traditional runtime environment has global security that is enabled, you need to communicate the administrative settings from your development environment to the runtime server. On the workbench, you need to specify that security is enabled on the runtime environment, and provide the user name and password to the secured server. In addition, you need to establish a trust between the development workbench of this product and the server. - Starting a remote WebSphere Application Server
Use the workbench to start a remote WebSphere Application Server running on a Windows or Linux operating system. You can choose to use an operating system or Secure Shell (SSH) authentication method to access the remote host that is running the server. After you provide the workbench with authentication details to the access the remote host, you can start the remote server in start or debug mode. - Configuring a WebSphere Application Server with Federal Information Processing Standard enabled
You can set up the workbench to connect to a WebSphere Application Server with Federal information Processing Standard (FIPS) enabled.
Parent topic: Configuring servers for testing and publishing

