Migration tips for application clients

Tips for migrating thin application client code:

The Java invocation used to run non-J2EE application clients has changed in Version 5.0. You must specify -Xbootclasspath/p:%WAS_BOOTCLASSPATH% on Windows systems or -Xbootclasspath/p:$WAS_BOOTCLASSPATH on UNIX systems when you invoke the Java command.

Set the WAS_BOOTCLASSPATH environment variable in one of the following ways:

For more information about using -Xbootclasspath, view sample code at the following path after you preform the application client installation:
install_root\samples\bin\ActiveXBridgeClients\VB\XJBExamples\modXJBHelpers.bas

Tips for migrating J2EE application client code:

If your J2EE application client uses resource references and you configured those resources using the Application Client Resource Configuration Tool (ACRCT), you must run the ClientUpgrade command to migrate the resource configuration information in WebSphere Application Server Version 5.


Related reference
The clientUpgrade command



Searchable topic ID:   rcli_migratetips
Last updated: Jun 21, 2007 8:07:48 PM CDT    WebSphere Business Integration Server Foundation, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.wasee.doc/info/ee/ae/rcli_migratetips.html

Library | Support | Terms of Use | Feedback