EJB Interoperability of JBoss Portal and IBM WAS

This posting outlined how we configured the servers to have a Portlet which runs in JBoss Portal making EJB calls to WAS. This involves couple of challenges:

- Interoperability between IBM and Non IBM components on JNDI binding and EJB calls.
- Compatibility of different JDK versions among Portal and Middle tier.
- The situation of having JDK 1.5 running JBossPortal and JDK 1.4 running WAS.

1. Preparing JBoss Portal for WAS EJB interoperability

- Install IBM JDK 5, run JBossPortal using IBM JDK. IBM packaged their low level CORBA//IIOP classes in their JDK runtime, using standard Sun's JDK5 results to a lot of Class Not Found Exception.

- Copy jacorb.jar from $JBOSS_HOME\client to $JBOSS_HOME\server\default\lib
- Copy jboss-iiop-client.jar from $JBOSS_HOME\client to $JBOSS_HOME\server\default\lib


2. Packing Portlet application for WAS EJB Client

The following IBM jars are required to package into the WEB-INF\lib directory of the Portlet's WAR.

- naming.jar
- naminglcient.jar
- wsexception.jar
- iwsorb.jar
- ras.jar
- bootstrap.jar
- emf.jar
- ecutils.jar
- ffdc.jar
- idl.jar

Testing

First Blog posting - testing.