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:
- Close all JCA v1.5 projects in the workspace and leave only the JCA v1.0 projects:
- In the Project Explorer view, right-click the JCA 1.5 projects.
- Select Close Project.
- In the Servers view, double-click the WebSphere Application Server v5.x to open the server editor.
- Select the J2C tab at the bottom of the server editor to add the resource adapter.
- Reopen all JCA v1.5 projects:
- In the Project Explorer view, right-click the JCA v1.5 projects.
- Select Open Project.
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.
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.
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.
When using the Universal Test Client (UTC) with WebSphere Application Server v6.0, you should be aware of the following two issues:
- 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:
- Launch the test client from an EJB bean. For instance, right-click on an EJB and select Run on Server.
- 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>- 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.
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.
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.
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.
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:
- Before the build, migrate the project to a v6 Web project. To migrate the project from v5.1.x to v6 Web project, you need to import your Web project in v6 workspace using the import wizard.
- Add the
<nature>com.ibm.wtp.web.StaticWebNature</nature>
statement to the .project file under the failing Web project root directory as follows:
<natures>
<nature>com.ibm.wtp.web.StaticWebNature</nature>
:
:
</natures>
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:
- the project does not automatically get published (added) to this default server
- the Server Selection wizard is not display. As a result, you are not asked if you would like to complete further server tasks, such as create tables and data sources or generate EJB deploy and RMIC code
To run your application on a preferred server, you can choose one of the following two options:
- Remove the default servers settings for a project:
- Set the default server to none. You can complete this by right-click your project in the Project Explorer view > Properties > Servers
- 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.
- Manually add the project to the server:
- In the Servers view, right-click your preferred server and select Add and remove projects.
- The Add and Remove Projects wizard opens and you can now specify the additional server tasks.
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:
- In the Servers view, start the WebSphere Application Server v6.0.
- After the server is started, right-click WebSphere Application Server v6.0 and select Run external admin script. The Jacl or Jython admin script file to run dialog opens.
- Locate the redeployFileTransfer.jacl from WAS_HOME/bin (where WAS_HOME is the installation directory where WebSphere is installed) and then click Open.
- Restart the server to switch from the default file transfer application to the secure file transfer application.
Return to the main readme file