Troubleshooting
Problem
This technote explains why EJB projects migrated from IBM WebSphere Application Studio Developer v5.1.2 into IBM Rational Application Developer for WebSphere Software v7 results in the error "The mapping for backend Default is not valid" and provides instructions to resolve the issue. Similar problem also when migrating from Rational Application Developer v6.0
Symptom
Attempts to migrate EJB projects from WebSphere Studio Application Developer v5.1.2 into Rational Application Developer v7 results in the following error:
The mapping for backend Default is not valid. The database vendor may not be supported. See the META-INF/Schema/SQLModelMigration.log file for details {WSADProjectSomeEjb} Unknown 1211985005718 347506
Another similar looking example from Rational Application Developer v6.0 of a specific iSeries migrated database backend version not supported in Rational Application Developer v7, as shown by errors in the Problems view:
The mapping for backend DB2UDBAS400_V5_1 is not valid. The database
vendor may not be supported. See the
META-INF/backends/DB2UDBAS400_V5_1/SQLModelMigration.log file for
details {SomeEJB2xCMPProject}
and in the corresponding SQLModelMigration.log file:
Migration of: DB2UDBAS400_V5 is not supported.
Cause
There is a missing target server in the EJB project.
Resolving The Problem
You need to specify a target server in WebSphere Studio Application Developer v5.1.2 or Rational Application Developer v6.0 that is supported in Rational Application Developer v7.0 (same for any other new RAD version), for example WebSphere Application Server (WAS v5.1) in the case of WebSphere Studio Application Developer v5.1.2, for the EJB project before the migration. Once migrated cleanly to v7.0 under that server target, it can be changed to another targeted runtime such as WAS v6.x.
Note: Migrating from a version of WebSphere Studio Application Developer prior to v5.1.2 is not an officially supported migration path. It will usually work with WebSphere Studio Application Developer v5.1.1+ which introduced the Server Target feature.
Here are the steps:
- Be sure the Server Targeting feature of WebSphere Studio Application Developer v5.1.2 was enabled.
Select Window -> Preferences -> J2EE ,then select: Enable server targeting support , on the right panel.
- Right-click on the EJB project select : Server Target -> Modify -> select one of the available servers supported on Rational Application Developer v7.0.
Note: Typically this would be done on the EAR project and selecting the checkbox to apply it to all members or the EAR.
If the target server is/was valid and the same error is present, the vendor database version for the CMP ejb backend folder may no longer be supported in Rational Application Developer v7.0, as per the DB2UDBAS400_V5_1 example under Cause (above).
- If not done so yet, migrate the original database to a version of the vendor database supported in Rational Application Developer v7.0
- Do a meet-in-the middle mapping to a new backend folder with a connection to that supported database. Make sure the mapping to the existing CMP ejb(s) matches the previous backend in Rational Application Developer v6.0.
Under the Related Information section, its important to read over technote: Backwards compatibility restrictions with the Software Development Platform and the Rational Application Developer v7.0 Help/Info Center items it references on migration from WebSphere Studio Application Developer v5.1.2 and Rational Application Developer v6.0.
Related Information
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21306466