aspose file tools*
The moose likes Websphere and the fly likes Migrating from RAD 7.0/WAS 6.0 to RAD 7.5/WAS 7.0 Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » Websphere
Bookmark "Migrating from RAD 7.0/WAS 6.0 to RAD 7.5/WAS 7.0" Watch "Migrating from RAD 7.0/WAS 6.0 to RAD 7.5/WAS 7.0" New topic
Author

Migrating from RAD 7.0/WAS 6.0 to RAD 7.5/WAS 7.0

John Maempa
Greenhorn

Joined: Mar 08, 2012
Posts: 2
Our application exists as a Java application in Subversion, but it is built as a Dynamic Web Project on our local machines by overwriting .metadata, .settings, and .project with web project information from a standard template. We will soon be migrating to RAD 7.5 and WAS 7.0.

I am trying to set up the application on my local machine in this new configuration, but nothing I've tried to date has worked. My first approach was to create a Java 1.6/WAS 7.0 Dynamic Web Project template, using the existing paradigm. I was able to successfully build the application in Java 1.6 after some remediation changes.

However, I was unable to deploy the application to a WAS 7.0 server. The EAR folder generated with the template could not be started with the server.

Next, I've tried using the Migration Wizard by taking a RAD 7.0 workspace and opening it in RAD 7.5. However, the Project Facet remained set to Java 1.4 with a WAS 6.0 Runtime, and I was not given a prompt option to change these.

Any help would be greatly appreciated!
John Maempa
Greenhorn

Joined: Mar 08, 2012
Posts: 2
After a few days' hiatus, I resumed research into this problem. The actual error was missing Resource Reference bindings, WebSphere error "CWNEN0044E". I'd abandoned "magic bullet" conversion recipes, so I dug into the actual problem.

Research on this error led me to examine the default "ibm-web-bnd.xml" file, which had no entries. For reasons yet unknown to me, RAD 7.5 generated a default "ibm-web-bnd.xmi" (XMI) file as well, though not the corresponding "ibm-web-ext.xmi" file.

Our existing application in WAS 6.0 used the XMI files. Some other research suggested that the XMI files were obsolete for WAS 7.0, and that the settings needed to be migrated to the corresponding XML file. I also noted that the XMI file in the example had JNDI names, whereas our existing application's Web Binding XMI file did not have JNDI name entries.

Therefore, I first deleted the default XMI file. I then edited the Web Deployment Descriptor (web.xml) file (DD) with the default editor:
1. I clicked on the References Tab, which showed the three Resource References of concern.
2. The JNDI name was blank for all three, as expected.
3. I added a JNDI name equal to the Resource Name for all three.
4. Saved my changes to the DD.

I expected this would add entries to the "ibm-web-bnd.xml" file. Instead, it created a new XMI file ("ibm-web-bnd.xmi"), containing the new binding entries, complete with new JNDI names.

I started the WAS 7.0 server, and this time, it deployed successfully. I was able to bring the application up in my local environment as well.

This solution generates more questions than it solved. I'm particularly interested in the relationship between the XMI and XML files, whether the XMI files are indeed obsolete or are still required for Dynamic Web Applications, as opposed to EJB Applications.

But for now, my most important takeaway is being grateful that neither the "old approach" nor the Workspace Migration approach worked. I wouldn't have learned anything.
Raj Kesavan
Greenhorn

Joined: Oct 08, 2010
Posts: 4
Our project is upgrading from RAD 7.0/WAS 6.1 to RAD 7.5/WAS 7.0. For the resolution you finally discovered with the ibm-web-bnd.xml file, did you start with the Migration Wizard workspace or with the template one?
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Migrating from RAD 7.0/WAS 6.0 to RAD 7.5/WAS 7.0