This topic helps you examine typical topologies and uses for WebSphere Application Server Clients.
Before you begin
This topic is one in a series of topics described in Planning the installation. Consider all of the planning scenarios that are mentioned in the parent article to determine the best approach to installing your e-business network. This topic describes installing and using the WebSphere Application Server Clients.Why and when to perform this task
In a traditional client server environment, the client requests a service and the server fulfills the request. Multiple clients use a single server. Clients can also access several different servers. This model persists for Java clients except that now these requests use a client run-time environment.
In this model, the client application requires a servlet to communicate with the enterprise bean, and the servlet must reside on the same machine as the WebSphere Application Server.
The following graphic shows a topology for installing the Application
Client and using client applications:
Use the following procedure as a example of installing the Application Client.
Steps for this task
The wizard automatically configures the HTTP Server to communicate with the first application server.
The diagram shows two different types of application clients on two different operating systems. Although this example shows two application clients, you do not have to install two application clients to have a working system. Each application client is fully functional and works independently of the other.
Optionally install the Application Client from your product CD on Machine B.
Optionally install the Application Client from your product CD on Machine C.
Result
This topic can help you plan run-time environments for client applications.
What to do next
See Application Client for WebSphere Application Server for information about creating client applications.