Develop stand-alone thin client applications

Develop the application code, then assemble the code into a client application that we can deploy on a client machine.

 

• Getting server objects and resources.

  A stand-alone client application can get suitable server objects and resources (like connection factories, JMS queues, and data sources) programmatically without using JNDI. Alternatively, a client application can use full JNDI support provided by the Thin Client for EJB.

• Compiling stand-alone thin client applications. To compile the client application, include the JAR files needed in the CLASSPATH setting for the javac command; for example, any extra JAR files for the client application's own classes, JAR files for IBM Thin clients used, and JAR files for JDBC provider classes.

  For the stand-alone thin clients, the following JAR files are provided in the /runtimes/ directory of either an Application Client installation or Application Server installation:

  
  

  Table 1. JAR files for stand-alone thin clients

  JAR file	Description
  com.ibm.jaxws.thinclient_7.0.0.jar	IBM Thin Client for Java API for XML-based Web Services (JAX-WS). This file enables a Java SE client application to use the JAX-WS model to invoke Web services that are hosted by the application server.
  com.ibm.ws.ejb.thinclient_7.0.0.jar	Thin Client for EJBs . This file enables a Java SE client application to access remote Enterprise Java Beans on a server through JNDI look up. If this file is running with a non-IBM product JRE on a non-IBM product platform, the IBM ORB implementation library, com.ibm.ws.orb_7.0.0.jar, is also needed.
  com.ibm.ws.jpa.thinclient_7.0.0.jar	IBM Thin Client for Java Persistence API (JPA). This file allows a Java SE client application to use the Java Persistence API (JPA) to store and retrieve persistent data through the application server.
  com.ibm.ws.messagingClient.jar	With the com.ibm.ws.ejb.thinclient_7.0.0.jar file, this file enables a Java SE client application to use WebSphere MQ messaging provider JMS resources from the WAS JNDI namespace. WebSphere MQ client jar files are also needed, and must be obtained from the WebSphere MQ product.
  com.ibm.ws.orb_7.0.0.jar	The IBM ORB implementation library. This file is needed if the IBM Thin Client for EJB is running with a non-IBM product JRE on a non-IBM product platform.
  com.ibm.ws.sib.client.thin.jms_7.0.0.jar	IBM Thin Client for JMS. This file enables a Java SE client application to use JMS resources of the default messaging provider. For languages other than US English, you also need the additional language files from sibc.nls.zip, which provides language-specific resource bundles.
  com.ibm.ws.sib.client_ExpeditorDRE_7.0.0.jar	The JMS Client packaged for Lotus Expeditor.
  com.ibm.ws.webservices.thinclient_7.0.0.jar	IBM Thin Client for JAX-RPC. This file enable a Java SE client application to use the JAX-RPC model to invoke Web services that are hosted by the appserver.

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

 

Next steps

After developing and compiling a stand-alone thin client application, we can deploy and run the client application.

Stand-alone thin clients

 

Related tasks

connection factories and references to JMS queues or topics may be obtained programmatically without using JNDI. Alternatively, full JNDI support may be obtained from the Thin Client for EJB with WAS.">Use JMS resources with the Thin Client for JMS with WAS
WebSphere MQ queue manager can get administratively-created WebSphere MQ messaging provider JMS resources from the WAS JNDI namespace.">Obtaining WebSphere MQ JMS resources in the stand-alone client environment
Install and configuring the Thin Client for JMS with WAS
Running an unmanaged Web services JAX-RPC client
Use the Administration Thin Client