Migration to the 搭配 WebSphere Application Server 的 Thin Client for JMS

There are a number of differences to consider when migrating to the 搭配 WebSphere® Application Server 的 Thin Client for JMS from an earlier version of the client.

Table 1. Migration from WebSphere Application Server 6.0.2 版 to WebSphere Application Server 7.0 版或更新版本. The first column of the table lists the areas where the differences are found between WebSphere Application Server 6.0.2 版 and WebSphere Application Server 7.0 版或更新版本. The second column lists the availability, applicability, file path, JRE level or the property names of the specific area of WebSphere Application Server 6.0.2 版 (Client for Java™ Message Service on Java 2 Platform, Standard Edition with WebSphere Application Server). The third column provides the file path, file names, JRE level or property names of the specific area of WebSphere Application Server 7.0 版或更新版本 (搭配 WebSphere Application Server 的 Thin Client for JMS).
Area WebSphere Application Server 6.0.2 版 (Client for Java Message Service on Java 2 Platform, Standard Edition with WebSphere Application Server) WebSphere Application Server 7.0 版或更新版本 (搭配 WebSphere Application Server 的 Thin Client for JMS)
Installation Available for separate download and installation Installed in the WebSphere Application Server 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 WebSphere Application Server 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 搭配 WebSphere Application Server 的 Thin Client for JMS 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

Using alternative trace properties file -DtraceSettingsFile

-DtraceSettingsFile

搭配 WebSphere Application Server 的 Thin Client for JMS 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

指出主題類型的圖示 參照主題



時間戳記圖示 前次更新: July 9, 2016 11:12
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=cord&product=was-nd-mp&topic=rjj_jmsthcli_migrate602
檔名:rjj_jmsthcli_migrate602.html