Configuring a WAS

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 machine or on another machine. The following topics describe how to set up a WAS v6.0 or later, such as setting up ports or data sources.

For WAS v6.0 or later, the development environment no longer has the server configuration in the workspace.

Attention: Server-specific configurations for WAS v6.0 and later are now set in the WebSphere Administrative Console. The configuration settings that are specific to an enterprise application can be set using the WAS Deployment editor. Use the WAS Deployment editor to configure the following configurations that are specific to an enterprise application:

• Data Sources

• Resource adapters and connection factories

• Substitution Variables

• Authentications

• Shared Libraries

• Virtual Hosts

• Class loader policies

• Creating a profile
  A profile is the set of files that define the runtime environment of a WAS.

• Setting server status updates
  You can specify how long the development environment is going to wait to update the status of the server running in real-time.

• Setting the connection to the server
  The administrative ports are used to communicate requests between the workbench and the server.

• Enabling hot method replace
  If you want to make changes to your Java™ classes while you are debugging, you can set this preference by editing the server before you start it. When hot method replace is enabled most application changes is picked up automatically without requiring an application or server restart.

• Testing enterprise beans in the universal test client
  The server tools provide you with a Web-based Universal Test Client where you can test your enterprise beans and Java™ classes.

• Reducing the startup time
  Enabling the Optimize server for testing and developing check box, may reduce the startup time of an application server.

• Keeping the WAS running after exiting the development environment
  You can specify that the server will continue running after you shut down the development environment.

• Setting publishing options
  Publishing involves copying files (application, resource files, and deployment descriptor files) to the correct location for the server to find and use them. You have the option whether you want to 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 WAS
  If your WAS runtime environment has global security 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 username and password to the secured server. If you are working with a secured WAS V6.1 or later (including WAS V7.0), you need to establish a trust between the development workbench of this product and the server.

• Switching the hypertext transfer protocol security
  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 on top of HTTP, which is used by Web servers and Web browsers to transfer and display hypermedia documents securely across the Internet.

Related information

WAS maintenance releases

---