InfoCenter Home >
4: Developing applications >
4.7: Java Clients

4.7: Java Clients

In a traditional client server environment, the client requests a service and the server fulfills the request. A single server is used by multiple clients. Clients can also access several different servers. This model persists for Java clients except now these requests make use of a client's runtime environment.

Prior to J2EE (Java TM 2 Platform Enterprise Edition), a typical Web-based client application consisted of the following model:

    browser (HTML file) -> servlet -> EJB
In this model, the client application requires a servlet to communicate with the Enterprise Java Bean (EJB), and the servlet must reside on the same machine as WebSphere Application Server.

With version 4.0, Java application clients can now consist of the following models:

In the Applet client model, a Java applet is embedded in a HyperText Markup Language (HTML) document residing on a client machine that is remote from WebSphere Application Server. With this type of client, the user accesses an EJB in WebSphere Application Server through the java applet in the HTML document.

The J2EE application client is a Java application program that accesses EJBs, JDBC databases, and Java Message Service message queues. The J2EE application client program runs on client machines. This program follows the same Java programming model as other Java programs; however, the J2EE application client depends on the application client runtime to configure its execution environment, and it uses the JNDI name space to access resources.

The Java thin application client provides a light-weight Java client programming model. This client is best suited for use in situations where a Java client application exists but the application must be enhanced to make use of EJBs, or where the client application requires a thinner, more light-weight environment than the one offered by the J2EE application client.

Go to previous article: Support for the use of MQSeries Java Message Service resources Go to next article: Applet client programming model

 

 
Go to previous article: Support for the use of MQSeries Java Message Service resources Go to next article: Applet client programming model