Test and deployment tools - release notes


1.0 Limitations
   1.1 IWAA1350E error when adding J2C resource adapter to WebSphere Application Server v5.x*
   1.2 For a successful run of embedded messaging applications in Linux (SLES9.0 & RHEL3)
   1.3 How to start the WebSphere Application Server v6.0 in non-root Linux IDs
   1.4 Unable to add host aliases for WebSphere Application Server v6.0*
   1.5 Terminate button in the console view should be disabled for a WebSphere Application Server V6.0*
   1.6 Universal Test Client Issues with WebSphere Application Server v6.0*
2.0 Known problems
   2.1 Launch Universal Test Client does not load Java resource in the first run of WebSphere Application Server v6.0 server
   2.2 AutomatedDeploy example expected to have updates
   2.3 Ant tasks for J2EE Export fail to produce the output file
   2.4 Headless Ant fails while building non-migrated v5.1.x Web project
   2.5 Problems using the Run on Server task when a project defines a default server*
   2.6 WebSphere Application Server v6.0 secure console output**

1.0 Limitations

1.1 IWAA1350E error when adding J2C resource adapter to WebSphere Application Server v5.x*

When trying to add a J2C resource adapter to WebSphere Application Server v5.x using the server editor, the IWAA1350E error might appear:

IWAA1350E Could not read RAR deployment descriptor. Choose another RAR or cancel this operation. (IWAE0099E An Exception occurred while parsing xml: Line #: 2 :Column #:241)

This error can indicate that a RAR file in the workspace has a bad deployment descriptor, but it can also appear incorrectly if there is a JCA v1.5 project in the workspace. WebSphere Application Server v5.x only supports JCA v1.0. If you are trying to add a JCA v1.0 project and a JCA v1.5 project exists on your workspace, complete the following to workaround the problem:

  1. Close all JCA v1.5 projects in the workspace and leave only the JCA v1.0 projects:
    1. In the Project Explorer view, right-click the JCA 1.5 projects.
    2. Select Close Project.
  2. In the Servers view, double-click the WebSphere Application Server v5.x to open the server editor.
  3. Select the J2C tab at the bottom of the server editor to add the resource adapter.
  4. Reopen all JCA v1.5 projects:
    1. In the Project Explorer view, right-click the JCA v1.5 projects.
    2. Select Open Project.

Note: This has been fixed in V6.0.0.1.

1.2 For a successful run of embedded messaging applications in Linux (SLES9.0 & RHEL3)

For a successful run of embedded messaging applications using WebSphere v5.1.x test environment under SuSE Linux Enterprise Server (SLES)9.0 and Red Hat Enterprise Linux (RHEL) 3, the following steps must be completed:

  1. For SLES9.0 and RHEL3, make sure the following environment variables are set in your user profile.
    1. export LD_ASSUME_KERNEL=2.4.19
    2. export LC_CTYPE='C'
    3. export LANG=$LC_CYPE
  2. For SLES9.0, under Java VM arguments, a system property can be set:
    -Djava.net.preferIPv4Stack=true
    This causes the JVM to resolve "localhost" to 127.0.0.1 instead of ::1.

1.3 How to start the WebSphere Application Server v6.0 in non-root Linux IDs

In SuSE Linux Enterprise Server (SLES)9.0 and Red Hat Enterprise Linux (RHEL) 3, WebSphere Application Server v6.0 can not start in IDs other than root by default. In order to start WebSphere Application Server v6.0 in non-root IDs, there is a workaround mentioned in the WebSphere Application Server v6.0 InfoCenter. For details, refer to the topic subject, "Running application servers from a non-root user" in the WebSphere Application Server v6.0 InfoCenter.

1.4 Unable to add host aliases for WebSphere Application Server v6.0*

The Add button to add host aliases for WebSphere Application Server v6.0 is always disabled. This Add button is located on the Deployment page of the Application Deployment Descriptor editor, under the Virtual Hosts section, and beside the Host aliases table.

If you are adding or selecting an entry in the Virtual host name list table, the Add button in the Host aliases table does not enable.

A workaround to the problem is to use WebSphere Application Server V6.0 administration console to add the host name and its aliases.

Note: This has been fixed in V6.0.0.1.

1.5 Terminate button in the console view should be disabled for a WebSphere Application Server V6.0*

If you start a WebSphere Application Server v6.0, go to the console view, and then select the Terminate button, the WebSphere Application Server v6.0 will not terminate; even though the terminate button in the Console view appears enabled.

To terminate the WebSphere Application Server v6.0, use the Stop button in the Servers view to stop the server.

Note: This has been fixed in V6.0.0.1.

1.6 Universal Test Client Issues with WebSphere Application Server v6.0*

When using the Universal Test Client (UTC) with WebSphere Application Server v6.0, you should be aware of the following two issues:

  1. If the server is using a non-default admin (SOAP) port, the UTC will not pick up the server's classpath correctly when launching the UTC directly or restarting it. There are two ways around this problem:
    1. Launch the test client from an EJB bean. For instance, right-click on an EJB and select Run on Server.
    2. Open up a Web browser, and use the following URL to launch the test client, filling in your admin (SOAP) port as specified:
      http://<hostname>:<HTTP port>/UTC/initialize?wasAdminPort=<SOAP port>
  2. When your bean classes change, the UTC will not automatically restart. If you are having problems in the UTC or it cannot resolve recent changes, restart the UTC and lookup your EJB beans or classes again.

Note: This has been fixed in V6.0.0.1.

2.0 Known problems

2.1 Launch Universal Test Client does not load Java resource in the first run of WebSphere Application Server v6.0 server

In the Project Explorer, if you select a Java resource and right-click to select the Launch Universal Test Client from the pop-up menu, the browser might show the bean is not loaded in the UTC. This occurs if the project of your selected Java resource is not published on the server. This problem only happens when using a WebSphere Application Server v6.0.

To workaround the problem, first publish the project on the server and then run the Launch Universal Test Client command.

2.2 AutomatedDeploy example expected to have updates

There is an Automated Deployment example program. To view instructions on how to access and run this example, open the online help and expand Developing Java applications > Developing enterprise applications > J2EE applications > Working with Ant > Example: Automated deploy. It is expected that there will be updates to this example. Any such updates will be available from the sample scripts Web page in the Developer Domain WebSphere Library Samples (www.ibm.com/developerworks/websphere/library/samples/SampleScripts.html). Any such updates may fix problems in the example, or may add new features to the example.

2.3 Ant tasks for J2EE Export fail to produce the output file

You can run Ant tasks for J2EE Export (EJBExport, WARExport, AppClientExport, and EARExport) without any error messages, however the output file will not be created. This problem has been identified and the fix is target to be available in an upcoming interim fix.

To workaround this problem, you can manually export your J2EE projects using the export operation from the workbench.

2.4 Headless Ant fails while building non-migrated v5.1.x Web project

Headless (command-line interface) Ant builds of non-migrated v5.1.x Web projects fail with a java.lang.ClassNotFoundException: com.ibm.etools.siteedit.builder.SiteUpdateBuilder. To avoid this problem, you need to complete one of the following:

2.5 Problems using the Run on Server task when a project defines a default server*

If you set a default server for a project and you use the Run on Server task to run your application on the default server, you might notice the following problems occur:

To run your application on a preferred server, you can choose one of the following two options:

  1. Remove the default servers settings for a project:
    1. Set the default server to none. You can complete this by right-click your project in the Project Explorer view > Properties > Servers
    2. In the Project Explorer, right-click the project and select Run > Run on Server. The Server Selection wizard opens and you can now specify the additional server tasks.
  2. Manually add the project to the server:
    1. In the Servers view, right-click your preferred server and select Add and remove projects.
    2. The Add and Remove Projects wizard opens and you can now specify the additional server tasks.

Note: This has been fixed in V6.0.0.1.

2.6 WebSphere Application Server v6.0 secure console output**

If you run WebSphere Application Server v6.0 in secure mode, the server's console output might not appear in the Console view. In addition, every few seconds an error message appears in the SystemOut.log files of your server, for example:

[11/3/04 16:58:18:412 CST] 0000003b RoleBasedAuth A SECJ0305I: The role-based authorization check failed for admin-authz operation ConfigService:queryConfigObjects:com.ibm.websphere.management.Session:javax.management.ObjectName:javax.management.ObjectName:javax.management.QueryExp. The user <null> (unique ID: null_access_id) was not granted any of the following required roles: administrator, operator, monitor, configurator.
[11/3/04 16:58:18:431 CST] 0000003b FileTransferS A ADFS0107E: The file to download "/usr/IBM/WebSphere/AppServer/profiles/default/config/temp/logs/sysout" does not exist.

To fix this problem, complete the following:

  1. Start the secured WebSphere Application Server v6.0.
  2. On the secured server, run the redeployFileTransfer.jacl script.
    1. On a command prompt, navigate to the WAS_home/bin directory, where WAS_home is the installation directory where the WebSphere Application Server is installed. The redeployFileTransfer.jacl file  is located in the WAS_home/bin directory.
    2. Run the following command:
    3. ./wsadmin.sh -profile redeployFileTransfer.jacl -lang jacl -c "fileTransferAuthenticationOn cell_name node_name server_name" -user username -password password

      Tip: To determine the cell name, node name, and server name of your WebSphere Application Server profile, complete the following:
      1. Open the WebSphere Application Server administrative console.
      2. On the left pane, expand the Servers section, click on the Application Servers link.
      3. On the right pane, under the Name column select your server.  The default server profile is called server1.
      4. In the Configuration tab you can find the server name located in its General properties section and  in  the Runtime tab you can find the cell name and node name under its General properties section.

  3. Restart the server to switch from the default file transfer application to the secure file transfer application.
**Note:  This has been updated on May 4, 2005.

Return to the main readme file