Use application clients
We can write client applications that run separately from the application server and use the framework provided by an underlying client to access the resources provided by WebSphere Application Server.
The high-level procedure for creating and using client application is generally the same for all types of client.
Tasks
- Choose the type of client application to use. Your choice of client application depends on the objects and functions we want to exploit, and the programming model to use.
- Develop the client application. On the development machine, we install the software development resources needed to develop client applications for use with WAS. During code development, we do not need access to the WAS. However, to assemble some types of client applications we need to install the client that provides the framework for the client application.
Development ends with you assembling the client application. This creates the JAR or EAR file that we can deploy to make the client application available for use.
- Deploy and run the client application. Deploying a client application depends on installing appropriate supporting files on the client machine, usually some configuring actions, and adding the program files for the client application. When the client application has been deployed, the application can be run. The steps required to deploy and run a client application depend on the type of client and the programming model used.
Example
(AIX) (Linux) (HPUX) (Solaris) (Windows) For samples of developing and using client applications, see the Application Client samples.
Related:
Application Client for WAS Developing client applications Deploy client applications Samples, v8.5