PK65017: CUSTOMER CANNOT EDIT DEFAULT VALUES FOR RUN LAUNCHER OF WAS APPLICATION CLIENT ON RAD

Rational Software Architect, Version 7.0.0.7
Rational Application Developer for WebSphere Software, Version 7.0.0.7
6.1.1.7: WebSphere Application Server Toolkit Version 6.1.1 Fix Pack 7

APAR status

• Closed as program error.

Error description

• 'WebSphere v6.x Application Client' Run Launcher always defaults
  under the Arguments and ClassPath Tabs
  
  a) Arguments Tab : VM Arguments refer to the default profile for
  the Websphere Ruintime from the Application tab, instead of the
  specific server and its profile selected with :
  [x] Enable application client to connect to server
  
  Editing/changing this manually is not acceptable and error
  prone.
  
  b) ClassPath Tab:
  - Bootstrap Entries are set to the first Websphere
  Application Server V6.x JRE installed
  - User Entries properties folder and lib jars are also set from
  the first WebSphere Application Server V6.x runtime installed.
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of WebSphere Application Server   *
  *                  Toolkit v6.1.1 and Rational Application     *
  *                  Developer v7                                *
  ****************************************************************
  * PROBLEM DESCRIPTION: Cannot change VM arguments and          *
  *                      classpath in the WebSphere v6.x         *
  *                      Application Client Launcher             *
  *                      dialog                                  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The Websphere v6.1 Application Client Launcher can only uses
  the VM arguments and classpath of the default WebSphere runtime
  (usually the pre-existed runtimes of RAD, or the first added
  runtime in AST), even if you change the "WebSphere runtime" in
  the Launcher dialog, or the default runtime isn't valid any
  more (such as the runtime has been uninstalled, or manually
  removed from file system). If the users are not able to change
  the VM arguments and classpath, they can not run the client
  against the desired run-time. Most importantly, if the default
  runtime has been removed, the client will be running against
  invalid VM arguments and classpath. The execution will fail
  over some runtime errors, or ClassnotfoundException. Manually
  edit these value in the Launcher dialog is tedious job and
  error-prone.
  

Problem conclusion

• With the fix to this APAR, the user should be able to change
  the VM arguments and classpath of websphere v6.x Application
  Clients by switch the "WebSphere runtime" in the Launcher
  dialog. The launcher will use the vm arguments and classpath
  of the selected WebSphere runtime.
  
  The fix for this APAR is currently targeted for inclusion in
  the WebSphere Application Server Toolkit fixpack 7.1.1.7 and
  Rational Application Developer fixpack 7.0.0.7.  Please refer
  to the following Recommended Updates page for WebSphere
  Application Server Toolkit delivery information:
  http://www.ibm.com/support/docview.wss?uid=swg27004980
  and the following Recommended Updates page for Rational
  Application Developer delivery information:
  http://www.ibm.com/support/docview.wss?uid=swg27007823
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WEBAPP SERVER A

• Fixed component ID

  5724J0820

Applicable component levels

• R610 PSY

     UP