Stand-alone thin clients

Small embeddable Java SE clients we can use either on their own (stand-alone) or, to provide different features, with one or more other stand-alone thin clients.

The stand-alone thin clients are provided as embeddable JAR files in the %WAS_HOME%/runtimes directory of either an Application Client installation or a WebSphere Application Server installation.

IBM Thin Client for Java Messaging Service (JMS)

The Thin Client for JMS is a Java service integration bus JMS client designed to run as an embeddable client in Java SE applications under the IBM, Sun and HP Java run-time environments (JREs). The client supports no transaction and local transaction models.

IBM Thin Client for EJB

The Thin Client for EJB allows Java SE applications to access remote Enterprise Java Beans on a server through JNDI look up. It can be embedded in a Java SE application running under the IBM, Sun, or HP JREs.

IBM Thin Client for Java API for XML-based Web Services (JAX-WS)

The Thin Client for JAX-WS allows Java SE client applications to use JAX-WS to invoke web services that are hosted by an application server. Such unmanaged client applications can use JAX-WS APIs to directly inspect a WSDL file and formulate the calls to web services

IBM Thin Client for JAX-RPC

The Thin Client for JAX-RPC allows Java SE client applications to use JAX-RPC to invoke web services that are hosted by an application server. Such unmanaged client applications can access a web service as if the web service is a local object mapped into the client address space even though the web service provider is located in another part of the world.

IBM Thin Client for Java API for RESTful Web Services (JAX-RS)

The Thin Client for JAX-RS is a stand-alone Java SE 6 client environment that enables running unmanaged JAX-RS RESTful web services client applications in a non-WebSphere environment to invoke JAX-RS RESTful web services that are hosted by the application server.

IBM Thin Client for Java Persistence API (JPA)

The Thin Client for JPA allows Java SE client applications to use the Java Persistence API (JPA) to store and retrieve persistent data without the use of an application server.

If we are running two or more of these stand-alone thin clients together, we must obtain all the clients that we are using from the same installation of Application Client for WAS, the same installation of the WAS product, or the same service refresh.

Although the stand-alone thin clients can coexist with each other, none of them can coexist with the Administration Thin Client for WAS.

WAS and IBM Application Client for WASalso provide a resource adapter for JMS that enables a third-party application server to be a stand-alone JMS client of WAS:

IBM Resource Adapter for JMS with WAS

A Java EE Connector Architecture (JCA) V1.5-compliant resource adapter that runs in a supported Java EE V1.4 compliant application server. The resource adapter provides full two-phase transaction support through an XA interface, supports inbound messages through message-driven beans (MDBs) and supports connection pooling with lazy association.

Running an unmanaged web services JAX-RPC client

Running an unmanaged web services JAX-WS client

Task overview: Store and retrieve persistent data with the JPA API

Use JMS from a third party application server to interoperate with service integration resources