6.1.0.1: WebSphere Application Server Toolkit V6.1.0 Fix Pack 1

Download Description

IBM WebSphere Application Server Toolkit Version 6.1.0.1 provides improvements for the following components:

• Eclipse
  
  • APAR PK27580: Projects are corrupted when using double-byte character set systems
  
  


• Server Tools
  
  • A publishing error will occur when publishing an Enterprise Application project that contains a directory that ends with '.jar'
  
  
  • Variables, such as -Dmy.argument={env_var:MY_ENV_VARIABLE}, defined in the 'Program Arguments' tab of the Application Client Launch Configuration dialog are not passed as program arguments to the JVM during launch
  
  
  • Variables defined in the 'Environment Arguments' tab of the Application Client Launch Configuration dialog are not passed to the JVM as environment variables during launch
  
  
  • When restarting a WebSphere Application Server v6.1 there is an anonymous* directory left behind in the <WAS_HOME>/profiles/<profile name>/wstemp directory
  
  
  • When running WebSphere Application Server Toolkit (AST) on Linux, the server status cannot be determined when using RMI to connect to a local WebSphere Application Server v6.1 that has security enabled
  
  
  • When running WebSphere Application Server Toolkit (AST) on Linux as a non-root user and WebSphere Application Server v6.1 is installed using a root user then the server state will not be detected
  
  
  • When switching from a secure to unsecure WebSphere Application Server v6.1, publishing errors will occur and the server state will not be detected
  
  
  • A check box has been added to allow automatic trust server certificate during a SSL handshake.
  • Connecting to multiple servers with security enable requires the same username and password on all servers
  • Modifications on the Deployment tab of the Enterprise Application deployment descriptor are not being updated when republished
  • WebSphere Application Server Toolkit publish will fail to publish an imported Enterprise Application project if the Enterprise Application project contains J2EE modules that have same name. For example, if test.ear contains test.jar (EJB module) and test.war (Web module) modules then this application will fail to publish
• Documentation
  • This fix includes updates to the translated versions of the product documentation in French, German, Italian, Brazilian Portuguese, Spanish, Japanese, Korean, Simplified Chinese, and Traditional Chinese