Workload management for stand-alone Java application clients
Enterprise beans provide business logic for all types of J2EE clients. Enterprise bean clients include servlets, JavaServer Pages (JSP) files, stand-alone Java applications, and other enterprise beans. Traditionally two client models are supported in a client server model.
- Web-based clients (servlets, JSPs)
- Stand-alone Java application clients
Web-based clients utilize a browser and access enterprise beans or other server-side resources through a servlet or JSP. Servlets and JSPs run in a Web container and typically in the same Java virtual machine (JVM) as the enterprise bean. Workload management and clustering provide high availability for the Web container. Failover support is provided by the WebSphere Application Server Web server plugin code.
A stand-alone Java client communicates with the enterprise beans that are deployed in an EJB container. This section describes workload management considerations for these types of stand-alone Java clients:
J2EE application client
A J2EE application client program runs its own JVM code and is invoked at its main method. This type of application client runs in a J2EE client container and uses the Java Naming and Directory Interface (JNDI) name space to access resources.Thin client
A thin application client provides a lightweight Java client programming model and does not run in a J2EE client container.
For more information about these application clients, see Application clients in Application Development.
These topics provide additional information about using workload management with application clients:
Workload management considerations for application clients
This topic provides information about the components and processes involved in workload management for application clients.Sample: Look up InitialContext with multiple hosts and ports
This topic provides an example of an application client that uses multiple hosts and ports to obtain the InitialContext for an EJB container.Sample: Use an IIOP URL
This topic provides an example of an application client that uses an IIOP URL to obtain the InitialContext for an EJB container.