IBM Support

PK57362: EJBDeploy V6.1 for WebSphere Application Server V5.1/V6.0

Download


Abstract

Enterprise JavaBeans (EJB) Applications built using IBM® Rational® Application Developer v7.0 fail when run using EJBDeploy from IBM WebSphere® Application Server v5.1 or v6.0.

Download Description

PK57362 resolves the following problem:

ERROR DESCRIPTION:
WebSphere Application Server (base) 5.1.1.3
Rational Software Architect 7.0.0.4

Projects are migrated from RSA6 to RSA7 but still use WebSphere Application Server 5.1 as the runtime. Projects that are already migrated to RSA6/7 cannot be built with the ejbcompiler toolkit from the standalone WebSphere Application Server v5.1.

If there is a migrated backend folder(produced by RSA7), it is not possible to do ejbdeploy using ejbdeploy script which is bundled in standalone WebSphere Application Server v5.1.

The error that occurs will be similar to the following:

[wsejbdeploy] framework search path: c:/<Programe files><IBM><WAS-V51>/deploytool/itp/plugins
[wsejbdeploy] java.lang.NullPointerException
[wsejbdeploy] at
com.ibm.etools.ejbrdbmapping.migration.
CompatibilitySAXXMIV6Handler.migrateHref
(CompatibilitySAXXMIV6Handler.java:129)

LOCAL FIX:
N/A

PROBLEM SUMMARY:

USERS AFFECTED:
All users of WebSphere Application Server v5.1 and v6.0 EJBDeploy

PROBLEM DESCRIPTION:
EJB Applications built using Rational Application Developer v7.0 fail when run using EJBDeploy from WebSphere Application Server v5.1 or v6.0.

RECOMMENDATION:
None

APAR PK57362 is being closed FIN with concurrence from the submitting customer. This means that a fix to this APAR is expected to be delivered from IBM in a release which is being developed at the time that the APAR was closed. The latest release of the product to exit development at the time this APAR was closed was: WebSphere Application Server 6.0

PROBLEM CONCLUSION:

In Rational Application Developer V7.0 a new SQL model format was introduced to resolve many design problems with the SQL model format used by WebSphere Studio Application Developer V5.1.x Rational Application Developer V6.0.

The EJBDeploy command tool for WebSphere Application Server v5.1 originated from the EJBDeploy GUI tool for WebSphere Studio Application Developer v5.1 and the EJBDeploy command tool for WebSphere Application Server v6.0 originated from the EJBDeploy GUI tool for Rational Application Developer v6.0. As a result, they will not understand the new SQL model introduced in Rational Application Developer V7.0.

Running the EJBDeploy command tool from WebSphere Application Server V5.1 or V6.0 is going to fail to process your EJB application if you use Rational Application Developer v7.0 to develop an EJB that contains a CMP 1.1 or 2.x back-end targeting either a WebSphere Application Server V5.1 or V6.0

The fix for this problem is an entire replacement of the EJBDeploy command tool for WebSphere Application Server V5.1 and V6.0 with the EJBDeploy provided in WebSphere Application Server V6.1.

The problem introduced in Rational Application Developer V7.0 that causes this scenario to fail has been corrected in Rational Application Developer V7.5. A new action has been added to the EJB Project context menu which will allow generating a CMP backend folder that is compatible with the WebSphere Application Server V6.0 EJBDeploy command tool.

In Rational Application Developer V7.5 this action can be found by selecting Java™ EE > EJB to RDB Mapping (1.x-2.x) > Generate back-end files for WebSphere Application Server 6.0 deployment.

CAUTION

  • This update replaces the entire deploytool directory so you should never apply it to a production environment or to any product other than WebSphere Application Server. This EJBDeploy update cannot be used with Wsadmin or Administrative Console tools. You can only use the updated EJBDeploy through the command-line scripts (ejbdeploy.bat or ejbdeploy.sh) or the WsEjbDeploy Ant task
  • Ensure that the original EJBDeploy deploytool directory and wsanttasks.jar file are backed up (for more details see the Installation Instructions section) before applying this maintenance
  • See the Known side effects section under the Download package section for WebSphere Application Server maintenance information

Prerequisites

WebSphere Application Server V5.1.x or V6.0.x installed on the supported Operating System platforms.

Installation Instructions

  1. Please review the readme.txt for detailed installation instructions.

[{"INLabel":"readme","INLang":"English","INSize":"8722","INURL":"ftp://public.dhe.ibm.com/software/websphere/appserv/support/fixes/PK57362/readme.txt"}]

Download Package

Download package

Download RELEASE DATE LANGUAGE SIZE(Bytes) Download Options
ejbdeploy61019_for_WAS51_Solaris11-24-2008US English218,771,239FTP
ejbdeploy61019_for_WAS51_Windows11-24-2008US English192,357,267FTP
ejbdeploy61019_for_WAS60_Solaris11-24-2008US English218,782,076FTP
ejbdeploy61019_for_WAS60_Windows11-24-2008US English192,374,637FTP

Known Side Effects

If, after applying this solution, any additional WebSphere Application Server fixpack maintenance is needed using the Update Installer then you must restore the original deploytool directory and wsanttasks.jar file for a successful update. After the new maintenance is applied you can apply the EJBDeploy V6.1 for WebSphere Application Server V5.1 or V6.0 maintenance by following these instructions in this download again.

Change History

EJBDeploy Version

Change
6.1.0.19 EJBDeployEJBDeploy packaged in WebSphere Application Server V6.1.0.19

Off
[{"DNLabel":"Windows-6.1.0.19 EJBDeploy for 5.1","DNDate":"20/10/2008","DNLang":"English","DNSize":"192357267","DNPlat":{"label":"Windows","code":"PF033"},"DNURL":null,"DNURL_FTP":null,"DDURL":"http://public.dhe.ibm.com:7618;sw_websphere;appserv/support/fixes/PK57362/ejbdeploy61019_for_was51_windows.zip"},{"DNLabel":"Windows-6.1.0.19 EJBDeploy for 6.0","DNDate":"20/10/2008","DNLang":"English","DNSize":"192374637","DNPlat":{"label":"Windows","code":"PF033"},"DNURL":null,"DNURL_FTP":null,"DDURL":"http://public.dhe.ibm.com:7618;sw_websphere;appserv/support/fixes/PK57362/ejbdeploy61019_for_was60_windows.zip"},{"DNLabel":"Solaris-6.1.0.19 EJBDeploy for 5.1","DNDate":"20/10/2008","DNLang":"English","DNSize":"218771239","DNPlat":{"label":"Solaris","code":"PF027"},"DNURL":null,"DNURL_FTP":null,"DDURL":"http://public.dhe.ibm.com:7618;sw_websphere;appserv/support/fixes/PK57362/ejbdeploy61019_for_was51_solaris.zip"},{"DNLabel":"Solaris-6.1.0.19 EJBDeploy for 6.0","DNDate":"20/10/2008","DNLang":"English","DNSize":"218782076","DNPlat":{"label":"Solaris","code":"PF027"},"DNURL":null,"DNURL_FTP":null,"DDURL":"http://public.dhe.ibm.com:7618;sw_websphere;appserv/support/fixes/PK57362/ejbdeploy61019_for_was60_solaris.zip"}]
[{"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"EJBDeploy (WSAD)","Platform":[{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"6.0.2.9;6.0.2.8;6.0.2.7;6.0.2.6;6.0.2.5;6.0.2.4;6.0.2.31;6.0.2.3;6.0.2.29;6.0.2.27;6.0.2.25;6.0.2.23;6.0.2.21;6.0.2.2;6.0.2.19;6.0.2.17;6.0.2.15;6.0.2.13;6.0.2.11;6.0.2.1;6.0.2;6.0.0.3;6.0.0.2;6.0;5.1.1.9;5.1.1.8;5.1.1.7;5.1.1.6;5.1.1.5;5.1.1.4;5.1.1.3;5.1.1.2;5.1.1.19;5.1.1.18;5.1.1.17;5.1.1.16;5.1.1.15;5.1.1.14;5.1.1.13;5.1.1.12;5.1.1.11;5.1.1.10;5.1.1.1;5.1.1;5.1.0.6;5.1.0.5;5.1.0.4;5.1.0.3;5.1.0.2;5.1.0.1;5.1","Edition":"Base","Line of Business":{"code":"LOB36","label":"IBM Automation"}},{"Product":{"code":"SSRTLW","label":"Rational Application Developer for WebSphere Software"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"EJB Development","Platform":[{"code":"PF033","label":"Windows"},{"code":"PF016","label":"Linux"}],"Version":"7.0;7.0.0.1;7.0.0.2;7.0.0.3;7.0.0.4;7.0.0.5;7.0.0.6;7.0.0.7;7.0.0.8","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
04 February 2020

UID

swg24020898