Network Deployment (Distributed operating systems), v8.0 > Reference > Administrator best practices

Migration to the Thin Client for JMS with WAS

There are a number of differences to consider when migrating to the Thin Client for JMS with WAS from an earlier version of the client.

Migration from WAS v6.0.2 to WAS v7.0 or later. The first column of the table lists the areas where the differences are found between WAS v6.0.2 and WAS v7.0 or later. The second column lists the availability, applicability, file path, JRE level or the property names of the specific area of WAS v6.0.2 (Client for JMS on Java 2 Platform, Standard Edition with WAS). The third column provides the file path, file names, JRE level or property names of the specific area of WAS v7.0 or later (Thin Client for JMS with WAS).

Area	WAS v6.0.2 (Client for JMS on Java 2 Platform, Standard Edition with WAS)	WAS v7.0 or later (Thin Client for JMS with WAS)
Installation	Available for separate download and installation	Installed in the WAS or Application Client /runtimes directory
JMS jar file name	sibc.jms.jar file	com.ibm.ws.sib.client.thin. jms_version_number.jar
Performing JNDI lookups of JMS resources	Requires optional sibc.jndi.jar file (and ORB sibc.orb.jar file for non-IBM JREs)	Requires Thin Client for EJB with WAS jar file com.ibm.ws.ejb. thinclient_version_number.jar or com.ibm.ws.ejb. thinclient.z_version_number.jar (and ORB com.ibm.ws.orb_version_number.jar for non-IBM JREs)
SSL configuration	Secure connections are configured by using JRE global properties: -Djavax.net.ssl.keyStore -Djavax.net.ssl.keyStorePassword -Djavax.net.ssl.trustStore -Djavax.net.ssl.trustStorePassword	Two approaches to configuring secure connections. The first approach uses JRE global properties: -Djavax.net.ssl.keyStore -Djavax.net.ssl.keyStorePassword -Djavax.net.ssl.trustStore -Djavax.net.ssl.trustStorePassword The second approach is to specify security settings that are specific to Thin Client for JMS with WAS connections: -Dcom.ibm.ssl.keyStoreType -Dcom.ibm.ssl.keyStore -Dcom.ibm.ssl.keyManager -Dcom.ibm.ssl.trustManager -Dcom.ibm.ssl.keyStorePassword -Dcom.ibm.ssl.protocol -Dcom.ibm.ssl.contextProvider -Dcom.ibm.ws.sib.jsseProvider
Minimum JRE level	1.4.2	1.5
Enable trace (set trace specification)	-Dcom.ibm.ws.sib.client.traceSetting	-Dcom.ibm.ejs.ras.lite.traceSpecification
Set trace file name	-Dcom.ibm.ws.sib.client.traceFile	-Dcom.ibm.ejs.ras.lite.traceFileName
Set max trace file size	Not applicable	-Dcom.ibm.ejs.ras.lite.maxFileSize
Set max number of trace files	Not applicable	-Dcom.ibm.ejs.ras.lite.maxFiles
Set trace format	Not applicable	-Dcom.ibm.ejs.ras.lite.traceFormat
Use alternative trace properties file	-DtraceSettingsFile	-DtraceSettingsFile Thin Client for JMS with WAS supports new options described in Trace user interface for stand-alone clients
Enable and specify FFDC file name	-DffdcLogFile	-Dcom.ibm.ejs.ras.lite.ffdcLogFile
NLS support	Installation option for NLS support	Non-English versions are available in the sibc.nls.jar file

+

Search Tips   |   Advanced Search