aspose file tools*
The moose likes Websphere and the fly likes Migratiion from 7 to 8.5.5 - Unable to find ABCManager Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » Websphere
Bookmark "Migratiion from 7 to 8.5.5 - Unable to find ABCManager" Watch "Migratiion from 7 to 8.5.5 - Unable to find ABCManager" New topic
Author

Migratiion from 7 to 8.5.5 - Unable to find ABCManager

Rajesh So
Ranch Hand

Joined: Oct 08, 2002
Posts: 141
Hi,

I have used the Migration toolkit to check if there are any problems. I have solved all the issues of XML File review. I am yet to solve some Java code review issues. The java code issues are not related to the problem I have.

The System.out error message is


However, the ABCManager is available under the jndi name ejb/ABCManager. The same ear file works perfect with WAS 7. The migration tool recommended me to change the version of EJB 1.1 to EJB 2.2 in the schema section of web.xml and ejb-jar.xml. I did not do any other change.

Another error message I receive in the application log file is


I am stuck here for longer. I expected the migration tool to be a magic box. But it is not able to do.
Can you give me a fresh idea?

regards,
Raj
Rajesh So
Ranch Hand

Joined: Oct 08, 2002
Posts: 141
Hi,

The code uses java.rmi.RemoteException in the business methods. I understand RemoteException is deprecated. Could this be the reason ?

During the build, there is an access to ejbdeploy tool. I think that generates some stubs. Can this be the reason for the bean to be missing?

regards,
Raj
Rajesh So
Ranch Hand

Joined: Oct 08, 2002
Posts: 141
Hi,

The EAR file contains two Ejb-jars. The first EJB-Jar has no problem. The problem happens with the second EJB-Jar. The beans of the second EjB-jar is not accessible. The EJB-jar used EJB 1.1 schema. I moved it to EJB 2.1.
Does this ring a bell? Can this be a problem?

I tried to merge, but that resulted in a deployment exception. The reason is there are around 50 beans in each EJB-Jar and there is a binding file ibm-ejb-jar-bnd.xmi I can't make any sense.

Regards,
Raj
Rajesh So
Ranch Hand

Joined: Oct 08, 2002
Posts: 141
Hi,

I have solved the problem. There were two EJB modules. One referred other. There was no problem till WAS 7. In WAS 8, the way to connect is different. I don't know what is different.

The way I got it working is to merge both the ejb modules together. This is a tedious task because the IBM binding file has to be modified too. There is a tool that comes as a plugin in Eclipse. I would not say it was too helpful. I found patterns of the binding file and merged 50+ beans manually. Thankfully, all is well now.

Regards,
Raj
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Migratiion from 7 to 8.5.5 - Unable to find ABCManager