Running Java thin client applications
We can run Java thin client applications on machines installed with either a WebSphere Application Client installation or a WAS installation.
Important: Java thin clients are not packaged with JDBC provider classes. For example, the WAS v8.5 Java thin client is not packaged with Apache Derby 10.2 classes. Therefore, to utilize the JDBC provider classes (such as Apache Derby, Oracle, DB2 , Informix , or Sybase) on a Java thin client, you must:
Otherwise, any attempt to load a database class (such as through the JNDI lookup of a datasource) results in a ClassNotFoundException. The Java invocation to run a Java thin client application varies between a client and a server. If the Java thin client application needs to run on both a client installation and a server installation, follow the steps in the Running a Java thin client application on a server machine topic.
- Add the classes to the Java thin client application environment.
- Make the classes visible to the Java thin client application. To do this, add the path to the classes in the client classpath within the script that launched the client program.
- Running a Java thin client application on a client machine
- Running a Java thin client application on a server machine
Example
Your Java thin application client no longer needs additional code to set security providers if we have enabled security for the WAS instance. This code found in IBM i Java thin or pluggable application clients should be removed to prevent migration and compatibility problems. The java.security file from the WebSphere instance in the properties directory is now used to configure the security providers.
Running the thin or pluggable application client with security enabled. The following code examples illustrates how security providers were set programmatically in the main() method and occurred prior to any code that accessed enterprise beans:
import java.security.*; ... if (System.getProperty("os.name").equals("OS/400")) { // Set the default provider list first. Provider jceProv = null; Provider jsseProv = null; Provider sunProv = null; // Allow for when the Provider is not needed, when // it is not in the client application's classpath. try { jceProv = new com.ibm.crypto.provider.IBMJCE(); } catch (Exception ex) { ex.printStackTrace(); throw new Exception("Unable to acquire provider."); } try { jsseProv = new com.ibm.jsse.JSSEProvider(); } catch (Exception ex) { ex.printStackTrace(); throw new Exception("Unable to acquire provider."); } try { sunProv = new sun.security.provider.Sun(); } catch (Exception ex) { ex.printStackTrace(); throw new Exception("Unable to acquire provider."); } // Enable providers early and ahead of other providers // for consistent performance and function. if ( (null != sunProv) && (1 != Security.insertProviderAt(sunProv, 1)) ) { Security.removeProvider(sunProv.getName()); Security.insertProviderAt(sunProv, 1); } if ( (null != jceProv) && (2 != Security.insertProviderAt(jceProv, 2)) ) { Security.removeProvider(jceProv.getName()); Security.insertProviderAt(jceProv, 2); } if ( (null != jsseProv) && (3 != Security.insertProviderAt(jsseProv, 3)) ) { Security.removeProvider(jsseProv.getName()); Security.insertProviderAt(jsseProv, 3); } // Adjust default ordering based on admin/startstd properties file. // Maximum allowed in property file is 20. String provName; Class provClass; Object provObj = null; for (int i = 0; i < 21; i++) { provName = System.getProperty("os400.security.provider."+ i); if (null != provName) { try { provClass = Class.forName(provName); provObj = provClass.newInstance(); } catch (Exception ex) { // provider not found continue; } if (i != Security.insertProviderAt((Provider) provObj, i)) { // index 0 adds to end of existing list if (i != 0) { Security.removeProvider(((Provider) provObj).getName()); Security.insertProviderAt((Provider) provObj, i); } } } // end if (null != provName) } // end for (int i = 0; i < 21; i++) } // end if ("os.name").equals("OS/400")For examples of Java thin client applications, refer to the Samples section of the information center.
Subtopics
- (dist) Run a Java thin client application on a client machine
To run a Java thin client application on a machine with Application Client for WebSphere Application Server installed, use the setup Client command then start the application.
- (dist) Run a Java thin client application on a server machine
To run a Java thin client application on a machine with WAS installed, use the setupClient command then start the application.
Related concepts
Java thin client Access the samples
Related tasks
Develop stand-alone thin client applications Samples documentation