ORB initialization problem

Question

I have an application hosted on WLS 7.0.2. From an EJB in this application, I am
trying to use resources hosted on another web application server (non-BEA). I
have the orb.properties, the jndi.properties and the jar files needed for connecting
to the other app server in the JRE\lib folder under the JDK that WLS is using,
so that the extension classloader will load them up. This works perfectly with
a command line client for my other app server. However, I am running into a problem
when I try to initialize the ORB for the other app server from my EJB. The exact
stack dump is as follows:
java.lang.reflect.InvocationTargetException: org.omg.CORBA.INITIALIZE: can't instantiate
default ORB implementation xxx.yyy.ORB minor code:0 completed: No
at org.omg.CORBA.create_impl(ORB.java:281)
at org.omg.CORBA.init(ORB.java:323)
What do I need to change in my WLS setting to get the classloader to initialize
the ORB? Please help.
Thanks
Sriram

Answer 1

My foreign app server is not j2ee 1.3 compliant. It fails to resolve the iiop URL
in the JNDI lookup. I am not certain it has support for CSIv2.
I use the common library by placing the jar files required for the foreign app
server's clients on the classpath in my startWebLogic.cmd file and override the
WLS corba properties by placing the foreign app server's properties as arguments
on the java startup command in my startWebLogic.cmd file. This is resulting in
the following exception:
org.omg.CORBA.BAD_PARAM: minor code: 0 completed: No
at org.omg.SecurityLevel2.PrincipalAuthenticatorHelper.narrow(PrincipalA
uthenticatorHelper.java:60)
Any suggestions as to why this might be occurring?
Thanks,
Sriram
Andy Piper <[email protected]> wrote:
"sriram" <[email protected]> writes:
Thank you the information. I have some further questions:
Can I use the weblogic initialcontext factory or do I need to use theother app
server's factory class for the lookup? What Context.SECURITY_AUTHENTICATIONwould
I need to use?You need to use WLInitialContextFactory (or none if you are inside the
server). For security you need to use CSIv2. Setting this up is
somewhat appserver dependant but support is required by J2EE 1.3 so if
your foreign appserver is J2EE 1.3 compliant it should work.
Do I necessarily need to use to RMI-IIOP to get to the other app server?The server
application that I am connecting to on the other app server has a libraryof objects
for performing the basic connectivity (includes initializing an ORB),authentication
operations and maintaining a user's session. My concern is that ifI decide to
go the RMI-IIOP way, I might not be able to use the common librarythat other
clients for the application use. What advantages does RMI-IIOP buyme over initializing
and using an ORB directly.I'm not sure I understand. RMI-IIOP happens over IIOP. If you
initialize and ORB you are using IIOP. So the level of support should
be equivalent, its just easier to use RMI-IIOP. How do you "use" the
common library? Are you saying its a jar you want to put in WLS?
andy