Accessing Ejb On Websphereasv6 Using Wsif From Flow In Bpelpm 10.1.2 On Oc4j (Doc ID 392403.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle(R) BPEL Process Manager - Version: 10.1.2.0
This problem can occur on any platform.

Symptoms

On 10.1.2.0.2 in Production:
When attempting to access a EJB hosted on WebSphere Application Server V6, using WSIF from a flow hosted in the BPEL Process Manager 10.1.2.0.2 , the following error occurs.

Since the EJB is currently hosted on WebSphere App Server V6 now, the following configuration
tasks have been done.

1. added the following jars in the classpath of BPEL Server
ETAService.jar(EJB classes),emaETAClient.jar(EJB stubs),bootstrap.jar ,emf.jar
,ffdc.jar ,ffdcSupport.jar ,naming.jar ,ras.jar ,wsexception.jar
,namingclient.jar

2. changed the Service def in WSDL to
<service name="ETAEJBService">
<port name="EJBPort" binding="emaeta:TASEJBBinding">
<ejb:address
className="com.ema.eta.ejb.ETAServiceEJBHome"
jndiName="ETAServiceEJB"
initialContextFactory="com.ibm.websphere.naming.WsnInitialContextFactory"
jndiProviderURL="iiop://emahost:2809"/>
</port>
</service>

ERROR
06/08/28 15:59:55 Building Application TagLibrary Persistent Cache for
console_war
Failed to create "invoker" bean; exception reported is:
"javax.naming.ConfigurationException: Name space accessor for the java: name
space has not been set. Possible cause is that the user is specifying a java:
URL name in a JNDI Context method call but is not running in a J2EE client or
server environment.
at
com.ibm.ws.naming.java.javaURLContextFactory.isNameSpaceAccessable(javaURLContex
tFactory.java:98)
at
com.ibm.ws.naming.urlbase.UrlContextFactory.getObjectInstance(UrlContextFactory.
java:73)
at javax.naming.spi.NamingManager.getURLObject(NamingManager.java:579)
...

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms