Call another WebLogic's EJBs from resource adapter?

          Is it possible to call another WebLogic's EJBs from a resource adapter?
          A call to the javax.naming.InitialContext(Hashtable environment) results in a
          VersioningError:
          weblogic.common.internal.VersioningError: Incompatible service packs in CLASSPATH:
          (BEA Systems, WebLogic Server 6.1 SP4 11/08/2002 21:50:43 #221641 , 6.1.4.0)
          not compatible with
          (BEA Systems, WebLogic Server 6.1 SP3 06/19/2002 22:25:39 #190835 , 6.1.3.0)
          at weblogic.common.internal.VersionInfo.verifyPackages(VersionInfo.java:128)
          at weblogic.common.internal.VersionInfo.<init>(VersionInfo.java:60)
          at weblogic.common.internal.VersionInfo.initialize(VersionInfo.java:79)
          at weblogic.kernel.Kernel.initialize(Kernel.java:122)
          at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:101)
          at weblogic.jndi.WLInitialContextFactoryDelegate.<init>(WLInitialContextFactoryDelegate.java:166)
          at java.lang.Class.newInstance0(Native Method)
          at java.lang.Class.newInstance(Class.java:232)
          at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:147)
          at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241)
          at javax.naming.InitialContext.init(InitialContext.java:217)
          at javax.naming.InitialContext.<init>(InitialContext.java:193)
          at java.lang.reflect.Constructor.newInstance(Native Method)
          I'm not sure it will always be possible to match the version, although here upgrading
          the SP3 to SP4 will probably be done soon.
          Does anyone have experience with this?
          Or better: is there any documentation on this issue?

          Hi Hans,
          Here is the link for Weblogic SP3 / SP4 vulnerability and comparison for
          http://216.239.53.104/search?q=cache:RqqaQ3HZdwoJ:www.nipc.gov/cybernotes/2003/cyberissue2003-06.pdf+Versioning+Error+in+BEA+weblogic+6.1+SP3+and+SP4&hl=en&ie=UTF-8
          Hope this will help you.
          Let me know if u have any further problems.
          rgds
          KSK
          "Hans Bausewein" <[email protected]> wrote:
          >
          >
          >Is it possible to call another WebLogic's EJBs from a resource adapter?
          >
          >A call to the javax.naming.InitialContext(Hashtable environment) results
          >in a
          >VersioningError:
          >
          >weblogic.common.internal.VersioningError: Incompatible service packs
          >in CLASSPATH:
          >(BEA Systems, WebLogic Server 6.1 SP4 11/08/2002 21:50:43 #221641 ,
          >6.1.4.0)
          >not compatible with
          >(BEA Systems, WebLogic Server 6.1 SP3 06/19/2002 22:25:39 #190835 , 6.1.3.0)
          > at weblogic.common.internal.VersionInfo.verifyPackages(VersionInfo.java:128)
          > at weblogic.common.internal.VersionInfo.<init>(VersionInfo.java:60)
          > at weblogic.common.internal.VersionInfo.initialize(VersionInfo.java:79)
          > at weblogic.kernel.Kernel.initialize(Kernel.java:122)
          > at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:101)
          > at weblogic.jndi.WLInitialContextFactoryDelegate.<init>(WLInitialContextFactoryDelegate.java:166)
          > at java.lang.Class.newInstance0(Native Method)
          > at java.lang.Class.newInstance(Class.java:232)
          > at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:147)
          > at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241)
          > at javax.naming.InitialContext.init(InitialContext.java:217)
          > at javax.naming.InitialContext.<init>(InitialContext.java:193)
          > at java.lang.reflect.Constructor.newInstance(Native Method)
          >
          >
          >
          >I'm not sure it will always be possible to match the version, although
          >here upgrading
          >the SP3 to SP4 will probably be done soon.
          >
          >Does anyone have experience with this?
          >
          >Or better: is there any documentation on this issue?
          >

Similar Messages

Calling a WebLogic web service from a WebLogic web application

We would like to call a WebLogic web service from WebLogic web application. The current architecture looks like:
LoadBalancer--->iPlanet-1/iPlanet-2--->Firewall--->WebLogic-AppServer-1/WebLogic-AppServer-2
The web application and web service are in the same WebLogic cluster. We would prefer that the web services do not get published externally.
Does the WebLogic web application need to make a call back outside the firewall to the load balancer?
Is there a way the web services can be called locally with load balancing?
Can web service calls be made over the t3 protocol?
Thanks,
Mike

I think one solution is to use a Java proxy to call the Web services.
In the Java proxy you can have a method that accepts the user/pass and sets them correctly for the Web service.
Then you expose that Java proxy as a data control (right click, create data control) - and then create a page that invokes that method.
(For the basics of working with a POJO data control see: http://blogs.oracle.com/shay/2009/07/java_class_data_control_and_ad.html )

Connectivity from ejb to Resource Adapter at run time

          I am facing a problem regarding the look-up of the Resource Adapter from the Ejb.
          To explain :
          1.I have The <resource-ref> tag in ejb-jar.xml set at follows :
          <resource-ref>
          <description>The Resource Adapter</description>
          <res-ref-name>eis/RitResourceAdapter</res-ref-name>
          <res-type>javax.sql.DataSource</res-type>
          <res-auth>Container</res-auth>
          </resource-ref>
          and the <resource-description> tag in weblogic-ejb-jar.xml as follows:
          <resource-description>
          <res-ref-name>eis/RitResourceAdapter</res-ref-name>
          <jndi-name>eis/RitResourceAdapterConnectorJNDINAME</jndi-name>
          </resource-description>
          2.Even though I have mentioned the res-ref-type as javax.sql.Datasource , in my
          code I have done :
          rcf = (RitConnectionFactory) c.lookup ("java:comp/env/eis/RitResourceAdpapter");
          Where rcf is the my Resource Adapter specific Connection Factory (one which
          I have prepared and not
          the javax.resource.cci.ConnectionFactory). So this means the connection
          object which I get is casted to
          get my own application specific connection object.
          3.When I run my servlet (which looks up the Ejb and which in turn looks-up the
          Resource Adapter) it works fine to the point that it looks-up the bean successfully
          but fails when it tries to do so for Resource Adapter. The Server exception is
          as follows :
                    javax.ejb.EJBException
                    - with nested exception:
          [javax.naming.NameNotFoundException: Unable to resolve comp/env/eis/RitResourceAdpapter/
          Resolved: 'comp/env/eis' Unresolved:'RitResourceAdpapter' ; remaining name '']
          It will be great to hear about any solution from you people.
          For your information :
          I am using Weblogic 6.1, both the ejb jar and the RitResourceAdapter.rar has been
          deployed and the relevant portion of the weblogic-ra. xml is :
          <connection-factory-name>LogicalNameOfRitResourceAdapter</connection-factory-name>
          <jndi-name>eis/RitResourceAdapterConnectorJNDINAME</jndi-name>
          Regards,
          Ritwik


> My question here is that is there any way where I do not put the queue name in the sender adapter at design time and based on the data availability in the queue let the sender adapter know the queue name to be processed at run time.
Unfortunately for JMS Sender CC it is not possible, but other way around is possible. I.e. you can dynamically choose the receving queue names by using ASMA "JMSReplyTo" in JMS Sender CC.
Regards,
Sarvesh

RFC calls with SAP JCO and IBM resource adapter for SAP - basic tuning

Hi experts,
we are working on a java portal connected to a backend system SAP by calling RFCs.
On our first integration tests, it appears to be quite slow fetching data from SAP by calling the remote functions from the custom portal. We are using SAP JCo 3.0.6 and IBM resource adapter for SAP 7.0.0.3 to integrate SAP with our portal.
Is there any basic tuning to achieve to improve performances or any hint of where to tune in SAP ?
Any help would be greatly appreciated.
Thanks a lot,
Jamal

Hi Jamal,
I understand you have already checked performance issues in the SAP Server. We had some problems with certain RFC calls and it turned out to be a badly developed ABAP sentence.
I'd recommend you to use httpwatch or another tool to check the response times from the browser, so you can point accurately where the is.
Regards
Francisco

Weblogic-ra.xml for resource adapter

Hi
We are trying to deploy Oracle Centraloffice on weblogic 10.3
But after configuring resource adapter which resides inside Central office application's EAR file, are application stops working.
It give us No classdef found error, basically it stops finding the JAR files which resides inside the application.
Resource adapter is configured to read file system for incoming JAR files and then process them, but if it starts working then are application stops working.
We are configuring the resource adapter's weblogic-ra.xml with the weblogic 9.10 schema in which everything is bundled inside <outbound-resource-adapter> tag

What is the correct way of looking up a resource adapter from another resource adpater? The JNDI name of my resource adapter is "StorageFactory" and I am doing a lookup like:
          Context ctx = new InitialContext();
          ctx.lookup("StorageFactory")
          Is this a correct way to lookup?

Code to call another Page Flow URL from one page flow URL

Can anyone send me the code to call another pageflow url from one page flow URL.

thanks...
In my appication there is no Form page. Only based on Canvas in that ,
i implemented Text box, Text Field And Drop down list etc..by own coding without using any abstract methods.
I did every thing with in single Midlet file.While developng goes on i got the problem ,
Like "your application exceeds the memorylimit you cant
use more than 32Kb of byte code in Canvas"...
So the application is not opened.
I tried to call the next file in same package to proceed, i got it. codition goes to next file, but its not return back to the Main(MIDlet) file, throws the excepton as "Security exception".
How to solve this problem,is any other way? please...

Calling a newly deployed EJB from an EJB gives a NoSuchMethod Exception if the jar of the newly deployed ejb is not in the classpath

Hi ,
I have an EJB A which is already deployed when the server starts. A second ejb
B is deployed at a later time.
EJB A calls methods in EJB B. I use reflection in EJB A to call methods in EJB
B.
I get a NoSuchMethodException when I call the create method in the Home object
of EJB B. If I add the ejb jar file to the classpath before the server starts
then it is able to resolve the method.
The problem is the EJBs which are called from EJB A is not known before the server
is started. New EJBs can be deployed at runtime and EJB A should be able call
the methods in newly deployed EJB's.
I also use the URLClassLoader to load all the classes in the jar file of the newly
deployed EJB in EJB A and it still gives a NoSuchMethodException because it cannot
resolve the stub class.
My error log is shown below.
This is an urgent issue.
Thanks
SampleConnector::testEJBService called
In Key : P1 Value : Input2
In Key : P3 Value : Input1
In Key : P2 Value : SomeConst
Loaded Class = com.bizwave.samples.rejb.SampleRemote
Loaded Class = com.bizwave.samples.rejb.SampleRemoteEJB
Loaded Class = com.bizwave.samples.rejb.SampleRemoteEJB_svq1df_EOImpl
Loaded Class = com.bizwave.samples.rejb.SampleRemoteEJB_svq1df_HomeImpl
Loaded Class = com.bizwave.samples.rejb.SampleRemoteEJB_svq1df_Impl
Loaded Class = com.bizwave.samples.rejb.SampleRemoteHome
java.lang.NoSuchMethodException
at java.lang.Class.getMethod0(Native Method)
at java.lang.Class.getDeclaredMethod(Class.java:1151)
at com.bizwave.samples.ejb.SampleConnectorEJB.testEJBService(SampleCon
ctorEJB.java:181)
at com.bizwave.samples.ejb.SampleConnectorEJB_be5y1v_EOImpl.testEJBSer
ce(SampleConnectorEJB_be5y1v_EOImpl.java:98)
at java.lang.reflect.Method.invoke(Native Method)
at com.bizwave.fc.utils.ClassUtils.invokeEJBMethod(ClassUtils.java:109
at com.bizwave.infra.fjet.engine.EJBServiceStepMgr.executeService(EJBS
viceStepMgr.java:91)

Hi,
I am attaching a test case. This test case actually demonstrates a security bug.
Unzip the file and modify the StartWeblogic.cmd in domainA to not refer to the
SampleRemoteEJB.jar in the classpath. If u run the test client under the client
dir u will see a NoSuchMethodException.
The reason is it is not able to load the dynamically generated stub file.
Initially I had the getMethod and it didn't work. You might have to modify the
files to suit ur env. The easier way is to run th edomain wizard and create 2
domains. Run the servers in development mode and place the jars under the applications
dir
Thanks
Rajesh Mirchandani <[email protected]> wrote:
Do you have any old EJB classes in your classpath? Did you recompile
your EJBs if you
upgraded from a old release or a Service pack?
Bob Lee wrote:
Hmmmm. That's an interesting problem.
Why is it giving you a NoSuchMethodException instead of a
ClassNotFoundException?
Can you post the code from SampleConctorEJB.java, line 181?
Try changing your call to getDeclaredMethod() to getMethod().
getDeclaredMethod() searches only the class you called it on, whereas
getMethod() traverses to the superclasses and interfaces. You onlyneed
getDeclaredMethod() when you're accessing a nonpublic method.
Not sure if this will help, but it's worth a shot.
Bob
Vasu wrote:
Hi ,
I have an EJB A which is already deployed when the server starts.
A second ejb
B is deployed at a later time.
EJB A calls methods in EJB B. I use reflection in EJB A to call methodsin EJB
B.
I get a NoSuchMethodException when I call the create method in theHome object
of EJB B. If I add the ejb jar file to the classpath before the serverstarts
then it is able to resolve the method.
The problem is the EJBs which are called from EJB A is not knownbefore the server
is started. New EJBs can be deployed at runtime and EJB A shouldbe able call
the methods in newly deployed EJB's.
I also use the URLClassLoader to load all the classes in the jarfile of the newly
deployed EJB in EJB A and it still gives a NoSuchMethodExceptionbecause it cannot
resolve the stub class.
My error log is shown below.
This is an urgent issue.
Thanks
SampleConnector::testEJBService called
In Key : P1 Value : Input2
In Key : P3 Value : Input1
In Key : P2 Value : SomeConst
Loaded Class = com.bizwave.samples.rejb.SampleRemote
Loaded Class = com.bizwave.samples.rejb.SampleRemoteEJB
Loaded Class = com.bizwave.samples.rejb.SampleRemoteEJB_svq1df_EOImpl
Loaded Class = com.bizwave.samples.rejb.SampleRemoteEJB_svq1df_HomeImpl
Loaded Class = com.bizwave.samples.rejb.SampleRemoteEJB_svq1df_Impl
Loaded Class = com.bizwave.samples.rejb.SampleRemoteHome
java.lang.NoSuchMethodException
at java.lang.Class.getMethod0(Native Method)
at java.lang.Class.getDeclaredMethod(Class.java:1151)
at com.bizwave.samples.ejb.SampleConnectorEJB.testEJBService(SampleCon
ctorEJB.java:181)
at com.bizwave.samples.ejb.SampleConnectorEJB_be5y1v_EOImpl.testEJBSer
ce(SampleConnectorEJB_be5y1v_EOImpl.java:98)
at java.lang.reflect.Method.invoke(Native Method)
at com.bizwave.fc.utils.ClassUtils.invokeEJBMethod(ClassUtils.java:109
at com.bizwave.infra.fjet.engine.EJBServiceStepMgr.executeService(EJBS
viceStepMgr.java:91)
Rajesh Mirchandani
Developer Relations Engineer
BEA Support
[user_projects.zip]

Deploying J2E CA 1.0 Resource Adapter on 11g

I am currently only supplying an ra.xml file since I have not been able to get the same RAR file that worked with WLS 8 to install correctly on 11g with my weblogic-ra.xml. I receive the following error even though I do not supply a weblogic-ra.xml file as the error message states. Are 1.0 resource adapters supported? I have included a copy of the ra.xml at the bottom of message.
Any ideas?
Eric
<Nov 24, 2010 2:37:04 PM MST> <Error> <Deployer> <BEA-149265> <Failure occurred
in the execution of deployment request with ID '1290634624475' for task '0'. Err
or is: 'weblogic.application.ModuleException: A <jndi-name> is specified for the
resource adapter bean in weblogic-ra.xml, however no <resourceadapter-class> el
ement is specified in ra.xml'
weblogic.application.ModuleException: A <jndi-name> is specified for the resourc
e adapter bean in weblogic-ra.xml, however no <resourceadapter-class> element is
specified in ra.xml
at weblogic.connector.deploy.ConnectorModule.prepare(ConnectorModule.jav
a:229)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(Modu
leListenerInvoker.java:199)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(Depl
oymentCallbackFlow.java:507)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD
river.java:41)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(Dep
loymentCallbackFlow.java:149)
Truncated. see log file for complete stacktrace
>
<Nov 24, 2010 2:37:04 PM MST> <Warning> <Deployer> <BEA-149004> <Failures were d
etected while initiating deploy task for application 'BullHooXG8Line'.>
<Nov 24, 2010 2:37:04 PM MST> <Warning> <Deployer> <BEA-149078> <Stack trace for
message 149004
weblogic.application.ModuleException: A <jndi-name> is specified for the resourc
e adapter bean in weblogic-ra.xml, however no <resourceadapter-class> element is
specified in ra.xml
at weblogic.connector.deploy.ConnectorModule.prepare(ConnectorModule.jav
a:229)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(Modu
leListenerInvoker.java:199)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(Depl
oymentCallbackFlow.java:507)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD
river.java:41)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(Dep
loymentCallbackFlow.java:149)
Truncated. see log file for complete stacktrace
>
<Nov 24, 2010 2:37:04 PM MST> <Error> <Console> <BEA-240003> <Console encountere
d the following error weblogic.application.ModuleException: A <jndi-name> is spe
cified for the resource adapter bean in weblogic-ra.xml, however no <resourceada
pter-class> element is specified in ra.xml
at weblogic.connector.deploy.ConnectorModule.prepare(ConnectorModule.jav
a:229)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(Modu
leListenerInvoker.java:199)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(Depl
oymentCallbackFlow.java:507)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD
river.java:41)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(Dep
loymentCallbackFlow.java:149)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(Dep
loymentCallbackFlow.java:45)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.ja
va:1221)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD
river.java:41)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.j
ava:367)
at weblogic.application.internal.SingleModuleDeployment.prepare(SingleMo
duleDeployment.java:43)
at weblogic.application.internal.DeploymentStateChecker.prepare(Deployme
ntStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(App
ContainerInvoker.java:60)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.cr
eateAndPrepareContainer(ActivateOperation.java:207)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.do
Prepare(ActivateOperation.java:98)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.pr
epare(AbstractOperation.java:217)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploym
entPrepare(DeploymentManager.java:747)
at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploy
mentList(DeploymentManager.java:1216)
at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare
(DeploymentManager.java:250)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.pre
pare(DeploymentServiceDispatcher.java:159)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallb
ackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallb
ackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallb
ackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTunin
gWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE connector PUBLIC '-//Sun Microsystems, Inc.//DTD Connector 1.0//EN' 'http://java.sun.com/dtd/connector_1_0.d
td'>
<connector>
<display-name>HooXG8 Line NoTxn Adapter</display-name>
<vendor-name>Bull</vendor-name>
<spec-version>1.0</spec-version>
<eis-type>GCOS</eis-type>
<version>2.1</version>
<resourceadapter>
<managedconnectionfactory-class>com.bull.HooX.GcosManagedConnectionFactoryImpl</managedconnectionfactory-class
>
<connectionfactory-interface>javax.resource.cci.ConnectionFactory</connectionfactory-interface>
<connectionfactory-impl-class>com.bull.HooX.GcosConnectionFactory</connectionfactory-impl-class>
<connection-interface>javax.resource.cci.Connection</connection-interface>
<connection-impl-class>com.bull.HooX.GcosConnectionImpl</connection-impl-class>
<transaction-support>NoTransaction</transaction-support>
<config-property>
<description>IP name or address</description>
<config-property-name>ipAddress</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>DSA node name</description>
<config-property-name>dsaNode</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>Mailbox name</description>
<config-property-name>mailbox</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>Protocol to use(EGATE, LINE, NONE)</description>
<config-property-name>protocol</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>LINE</config-property-value>
</config-property>

There should be a weblogic-ra.xml file in your deployment plan somewhere. The structure of the deployment plan is as follows:
somewhere/Plan.xml
somewhere/plan/META-INF/weblogic-ra.xml
The resource adapter does not support you specifying a <jndi-name> for the resource adapter. You can however specify <jndi-name> for the connection instances you create after deploying the adapter. If you have a <jndi-name> for the recource adapter, simply delete it from weblogic-ra.xml (also delete empty element such as <jndi-name></jndi-name> or <jndi-name /> ). Then update the adapter from the Deployments page in Admin console.
Here is my weblogic-ra.xml file:
<?xml version='1.0' encoding='UTF-8'?>
<weblogic-connector xmlns="http://xmlns.oracle.com/weblogic/weblogic-connector" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/weblogic-connector http://xmlns.oracle.com/weblogic/weblogic-connector/1.0/weblogic-connector.xsd">
<native-libdir>C:\dev\wls_domains\domain1\lib</native-libdir>
<enable-access-outside-app>false</enable-access-outside-app>
<enable-global-access-to-classes>true</enable-global-access-to-classes>
<security></security>
<outbound-resource-adapter>
<default-connection-properties>
<pool-params></pool-params>
<logging></logging>
</default-connection-properties>
<connection-definition-group>
<connection-factory-interface>javax.resource.cci.ConnectionFactory</connection-factory-interface>
<default-connection-properties>
<pool-params></pool-params>
<logging>
<logging-enabled>false</logging-enabled>
<rotation-type>bySize</rotation-type>
<number-of-files-limited>false</number-of-files-limited>
<file-count>7</file-count>
<file-size-limit>500</file-size-limit>
<rotate-log-on-startup>true</rotate-log-on-startup>
<log-file-rotation-dir></log-file-rotation-dir>
<rotation-time>00:00</rotation-time>
<file-time-span>24</file-time-span>
</logging>
</default-connection-properties>
<connection-instance>
<jndi-name>hoox</jndi-name>
<connection-properties>
<pool-params></pool-params>
<logging>
<log-filename>C:\dev\wls_domains\domain1\servers\AdminServer\logs\hoox.log</log-filename>
<logging-enabled>true</logging-enabled>
<rotation-type>bySize</rotation-type>
<number-of-files-limited>true</number-of-files-limited>
<file-count>7</file-count>
<file-size-limit>10000</file-size-limit>
<rotate-log-on-startup>false</rotate-log-on-startup>
<log-file-rotation-dir>C:\dev\wls_domains\domain1\servers\AdminServer\logs</log-file-rotation-dir>
<rotation-time>00:00</rotation-time>
<file-time-span>24</file-time-span>
</logging>
<properties>
<property>
<name>mailbox</name>
<value>XXXXXXXXXXXXXX</value>
</property>
<property>
<name>dsaNode</name>
<value>XXXXXXXXXXXXX</value>
</property>
<property>
<name>ipAddress</name>
<value>XXXXXXXXXXXXXXX</value>
</property>
<property>
<name>options</name>
<value>-TL FULL -MCMDSIZE 5</value>
</property>
<property>
<name>protocol</name>
<value>EGATE</value>
</property>
<property>
<name>serviceMapPath</name>
<value>C:\dev\wls_domains\domain1\lib\vdirmap.xml</value>
</property>
</properties>
</connection-properties>
</connection-instance>
</connection-definition-group>
</outbound-resource-adapter>
</weblogic-connector>

Calling EJB from another EJB

I need to make a several calls to the methods inside EJB1 from EJB2. I was getting
the remote reference of the EJB2 inside the ejbCreate() of the EJB1, is it a good
practice ?? If not, do I need to get remote reference of the EJB2 every time I
need to call EJB2 method??
Thanks in advance.

To refer a Ejb from another Ejb include <ejb-ref> in ejb-jar.xml
<session>
<ejb-name>Ejb1</ejb-name>
<ejb-ref>
<ejb-ref-name>Ejb2</ejb-ref-name>
<ejb-ref-type>Entity</ejb-ref-type>
<home>com.ejb.Ejb2Home</home>
<remote>com.ejb.Ejb2</remote>
</ejb-ref>
<session>
Include a <reference-discriptor> in weblogic-ejb-jar.xml
<weblogic-enterprise-bean>
<ejb-name>EjbSession</ejb-name>
<reference-descriptor>
<ejb-reference-description>
<ejb-ref-name>Ejb2</ejb-ref-name>
<jndi-name>com.ejb.Ejb2Home</jndi-name>
</ejb-reference-description>
</reference-descriptor>
</weblogic-enterprise-bean>
In Ejb1 bean class refer to Ejb2 method with a remote reference to Ejb2.
InitialContext initialContext = new InitialContext();
Ejb2Home ejb2Home = (Ejb2Home)initialContext.lookup("com.ejb.Ejb2Home");
Ejb2 ejb2 = ejb2Home.findByPrimaryKey();
Alex Pratt wrote:
I need to make a several calls to the methods inside EJB1 from EJB2. I was getting
the remote reference of the EJB2 inside the ejbCreate() of the EJB1, is it a good
practice ?? If not, do I need to get remote reference of the EJB2 every time I
need to call EJB2 method??
Thanks in advance.

Challenge: call local ejb from remote ejb on weblogic 9.2

Hi ALL,
How do I call to local ejb from remote ejb object. The jar file is deployed on weblogic server 9.2, if you want get it http://geocities.yahoo.com.br/lindembe/BEAProject.jar and the source code are http://geocities.yahoo.com.br/lindembe/BEAProject.zip. It is a sample app with two ejb that works so good on JBOSS, JOnAS, but BEA Weblogic.....
The complete problem you watch http://forum.java.sun.com/thread.jspa?threadID=768718&messageID=4387570#4387570
or
http://forums.bea.com/bea/message.jspa?messageID=600043148&tstart=0

Your code in SigemFacadeBean should just do:
InitialContext ctx = new InitialContext();
when you lookup the local EJB. (This will work on all app servers. There's no need to put an app-server specific intial context factory in your code.)
Also, you can remove the jndi-name setting for the local ejb from your weblogic-ejb-jar.xml. jndi-name is only applied to remote ejbs.
-- Rob
WLS Blog http://dev2dev.bea.com/blog/rwoollen/

Calling an ejb from glassfish to weblogic server

I'd like to be able to call a stateless session bean from a glassfishV3 server that is residing on weblogic 9.2.3. (Ejb spec 2.1 NOT 3.0 please)
I've done this successfully from Tomcat to weblogic, but there are a few hiccups when trying this on glassfish.
Basically what I've attempted is this:
1.) I add these jvm properties to the glassfish startup:
-Dorg.omg.CORBA.ORBClass=weblogic.corba.orb.ORB
-Dorg.omg.CORBA.ORBSingletonClass=weblogic.corba.orb.ORB
-Djavax.rmi.CORBA.PortableRemoteObjectClass=weblogic.iiop.PortableRemoteObjectDelegateImpl
-Djavax.rmi.CORBA.UtilClass=weblogic.iiop.UtilDelegateImpl
2.) Copy weblogic.jar, tools.jar, and webservices.jar from the weblogic/server/lib directory to the glassfish lib/ext directory
...glassfish won't start then because of the weblogic.jar...
3.) Move the weblogic.jar to the WEB-INF/lib directory of my war in glassfish.
Now I try it and get:
(I'm skipping some of the stacktrace at the start)
.....java.lang.IllegalAccessError: tried to access method weblogic.kernel.KernelStatus.initialized()V from class weblogic.kernel.Kernel at weblogic.kernel.Kernel.ensureInitialized......
I'm guessing that this has to do with the "weblogic kernel" not being initialized. So now I'm stuck.
Am I going down the wrong path?
I've also tried these other proposed solutions:
1.) Changing the connection properties of the InitialContext to use these properties:
env.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
env.put(Context.PROVIDER_URL, "t3://localhost:7001");
env.put(Context.SECURITY_PRINCIPAL, "weblogic");
env.put(Context.SECURITY_CREDENTIALS, "weblogic");
2.) Using RMI over IIOP instead of T3.
None of these with any luck.
If anyone has done this successfully I'd appreciate some insight.
Regards,
Eric

I'd like to be able to call a stateless session bean from a glassfishV3 server that is residing on weblogic 9.2.3. (Ejb spec 2.1 NOT 3.0 please)
I've done this successfully from Tomcat to weblogic, but there are a few hiccups when trying this on glassfish.
Basically what I've attempted is this:
1.) I add these jvm properties to the glassfish startup:
-Dorg.omg.CORBA.ORBClass=weblogic.corba.orb.ORB
-Dorg.omg.CORBA.ORBSingletonClass=weblogic.corba.orb.ORB
-Djavax.rmi.CORBA.PortableRemoteObjectClass=weblogic.iiop.PortableRemoteObjectDelegateImpl
-Djavax.rmi.CORBA.UtilClass=weblogic.iiop.UtilDelegateImpl
2.) Copy weblogic.jar, tools.jar, and webservices.jar from the weblogic/server/lib directory to the glassfish lib/ext directory
...glassfish won't start then because of the weblogic.jar...
3.) Move the weblogic.jar to the WEB-INF/lib directory of my war in glassfish.
Now I try it and get:
(I'm skipping some of the stacktrace at the start)
.....java.lang.IllegalAccessError: tried to access method weblogic.kernel.KernelStatus.initialized()V from class weblogic.kernel.Kernel at weblogic.kernel.Kernel.ensureInitialized......
I'm guessing that this has to do with the "weblogic kernel" not being initialized. So now I'm stuck.
Am I going down the wrong path?
I've also tried these other proposed solutions:
1.) Changing the connection properties of the InitialContext to use these properties:
env.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
env.put(Context.PROVIDER_URL, "t3://localhost:7001");
env.put(Context.SECURITY_PRINCIPAL, "weblogic");
env.put(Context.SECURITY_CREDENTIALS, "weblogic");
2.) Using RMI over IIOP instead of T3.
None of these with any luck.
If anyone has done this successfully I'd appreciate some insight.
Regards,
Eric

Calling EJB deployed on Weblogic 10.3 from WebSphere Application Server 6

Hi,
We are trying to call an EJB(2.1) deployed in Weblogic 10.3 from WebSphere Application Server 6.
The problem is that the jars containing Weblogic's initial context factory are compiled with JDK5. (Client jar was built as per [http://download.oracle.com/docs/cd/E15051_01/wls/docs103/client/jarbuilder.html] .)
WebSphere is still running on JDK1.4.
Therefore when trying to get the InitialContext to lookup up the bean we get major/minor version errors because of the compiler level mismatch.
Has anyone faced a scenario like this and come up with a solution?
Are there 1.4 jars for Weblogic 10.3 out there?
Any help?
Thanks

Hi Dan,
Yes I am using EJB 3. I saw this thread earlier also but :
1. In my case I am not calling the EJB 3.0 methods directly. I am using a java client (Cataloged as a Java Class Library) which does the lookup and calls the EJB methods. (I am not cataloging and calling the EJB 3.0 methods directly).
2. It is working perfectly fine when the EJB is deployed in Weblogic 10.0 or 10.2.
I am very much new to this so please bear with my small and silly questions! Thanks a lot for you help !
Cheers !
Rajat

Error in calling an EJB from another EJB

Hello All,
I have a scenario where i need to call a method of an ejb from another ejb.
Both the EJB's are in different DC's.
EG: DC1 using DC2
I have added the public part of DC2 in DC1.
The following code is written in DC1 to access the EJB of DC2
      MyRemote l_remote;
       MyHome l_home;
       InitialContext l_ctx = new InitialContext();
>>       l_home = (MyHome)l_ctx.lookup("JNDI Name");
       l_remote = (MyRemote)l_home.create();
There is no error at build time and deploy time, but at run time "MyHome" class is not found.
Even i am not able to access the helper class defined in the DC2 at runtime.
Please help.
Thanks in Advance

First off, wrong forum section.
Check if your JNDI name is correctly placed for the bean you're calling -- check j2ee-engine.xml for that. Check the EJB container if the ear file you deployed is there and updated.
Try placing "localejbs/JNDI name" on your lookup parameter.
Regards,
Jan

Local Session Bean calling another local Session Bean in EJB 3.0

Hi,
In EJB 3.0, I am trying to do JNDI lookup of a local sesion bean from another session bean's helper class.
I am not using @EJB injection mechanism here, as call to the local session bean is made in a helper class. Helper classes do not support resource injection.
Following are the EJB class definitions used in my project. Call to "EJB3Local" made from "EJB1" fails as the "EJB2" helper class is calling "EJB1Local"
@Stateless
@EJBs({@EJB(name="EJB2Local", beanInterface=EJB2Local.class),
@EJB(name="EJB3Local", beanInterface=EJB3Local.class)})
public class EJB1 implements EJB1Remote, EJB1Local{
public void findEJB3Local(){
//1. JNDI lookup for EJB3Local ----
//2. EJB3Local.someFunction()
@Stateless
@EJB(name="EJB1Local", beanInterface=EJB1Local.class)
public class EJB2 implements EJB2Remote, EJB2Local{
public void findEJB1Local(){
//1. JNDI lookup EJB1Local
// 2. Call EJB1Local.findEJB1Local method
@Stateless
public class EJB3 implements EJB3Remote, EJB3Local{
public void someFunction(){}
A remote call to EJB2.findEJB1Local() will invoke EJb1Local.findEJB3Local method and the call fails with "java:comp/env/EJB3Local" not found in EJB1Local.
Has anybody encountered an issue like this issue with local interface calling another local interface?
Thanks,
Mohan

To refer a Ejb from another Ejb include <ejb-ref> element
in ejb-jar.xml
<session>
<ejb-name>SessionBeanA</ejb-name>
<ejb-ref>
<ejb-ref-name>SessionBeanB</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<home>com.ejb.SessionBeanBHome</home>
<remote>com.ejb.SessionBeanB</remote>
</ejb-ref>
</session>
Include a <reference-descriptor> in weblogic-ejb-jar.xml
<weblogic-enterprise-bean>
<ejb-name>SessionBeanA</ejb-name>
<reference-descriptor>
<ejb-reference-description>
<ejb-ref-name>SessionBeanB</ejb-ref-name>
<jndi-name>com.ejb.SessionBeanBHome</jndi-name>
</ejb-reference-description>
</reference-descriptor>
</weblogic-enterprise-bean>
In SessionBeanA Bean class refer to SessionBeanB with
a remote reference to SessionBeanB.
InitialContext initialContext=new InitialContext();
SessionBeanBHome sessionBeanBHome=(SessionBeanBHome)
initialContext.lookup("com.ejb.SessionBeanBHome");
SessionBeanB sessionBeanB=sessionBeanBHome.findByPrimaryKey(primarykey);
sessionBeanB.update();
sessionBeanB.getAll();
thanks,
Deepak

Multiple EARs packaging the same resource adapter -- Weblogic Application S

Hello,
I had a question regarding JNDI and deploying multiple applications (EAR's) which package the same resource adapter running on Webloigc Application Server 9.1. I have an EAR file, ear1, which contains a resource adapter with connection factory with JNDI name say 'xyz' specified in the weblogic-ra.xml file. I have another EAR file, ear2, which again packages the same resource adapter with the same connection factory with JNDI name 'xyz'. Upon activating the 2nd EAR file, I get an exception 'javax.naming.NoPermissionException: A Resource Adapter may only be accessed from within the same application from which it was deployed.', as seen below:
<May 8, 2006 10:29:27 AM PDT> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating distribute task for application 'JMS2JMS_eInsightweblogic2'.>
<May 8, 2006 10:29:27 AM PDT> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException: java.lang.AssertionError: Internal Error occurred, Assertion Failed: No Initial Context for Jndi: javax.naming.NoPermissionException: A Resource Adapter may only be accessed from within the same application from which it was deployed.
at weblogic.connector.deploy.ConnectorModule.prepare(ConnectorModule.java:217)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:90)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:318)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:53)
Truncated. see log file for complete stacktrace
javax.naming.NoPermissionException: A Resource Adapter may only be accessed from within the same application from which it was deployed.
at weblogic.connector.outbound.RAOutboundManager.getConnectionFactory(RAOutboundManager.java:721)
at weblogic.connector.deploy.JNDIHandler.getConnectionFactory(JNDIHandler.java:1017)
at weblogic.connector.deploy.JNDIHandler.lookupObject(JNDIHandler.java:871)
at weblogic.connector.deploy.JNDIHandler.getObjectInstance(JNDIHandler.java:845)
at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304)
Truncated. see log file for complete stacktrace
It seems like the 2nd EAR is trying to go across and lookup the connection factory from the 1st EAR. Does weblogic bind the RA's connection factory jndi name in the global jndi and is not specific to each EAR? Is there some flag or switch I can turn on to make the JNDI specific to each EAR?
My weblogic deployment descriptor for the ra looks like the following:
<weblogic-connector xmlns="http://www.bea.com/ns/weblogic/90"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.bea.com/ns/weblogic/90
http://www.bea.com/ns/weblogic/90/weblogic-ra.xsd">
<jndi-name>JMS2JMS_eInsightDeployment4_stcbpelra</jndi-name>
<enable-access-outside-app>false</enable-access-outside-app>
<enable-global-access-to-classes>false</enable-global-access-to-classes>
<outbound-resource-adapter>
<connection-definition-group>
<connection-factory-interface>javax.resource.cci.ConnectionFactory</connection-factory-interface>
<connection-instance>
          <b><jndi-name>BPELConnectionFactory</jndi-name></b>
          <connection-properties>
          <pool-params>
          <initial-capacity>0</initial-capacity>
          <max-capacity>10000</max-capacity>
          <capacity-increment>1</capacity-increment>
          <shrinking-enabled>true</shrinking-enabled>
          <shrink-frequency-seconds>60</shrink-frequency-seconds>
          <match-connections-supported>false</match-connections-supported>
          </pool-params>
          <properties>
               <property>
                    <name>BPELConnectionFactory</name>
                    <value>BPELConnectionFactory</value>
               </property>
          </properties>
          </connection-properties>
     </connection-instance>
</connection-definition-group>
</outbound-resource-adapter>
</weblogic-connector>

Thanks for the reply... in my case this would be done by the active synch process so no GUI form is required. I will be getting a list of application ID for the user by LDAP AS. One i get it i will have to parse it and get the list of application user id. I am passing those ID;s to a workflow where I am forming the resource name as you mentioned
for example:
If i get user1#user2#user3 from AS i am separating them based on # using split and getting 3 different user id;s
now i am forming a string with the resource name and passing it to the sub process in which i am checking out the user object, setting the user attributes and checking in the new view.
user1#LDAP
user2#LDAP|1
user3#LDAP|2
Problem ; When i run this user1 is getting created in LDAP but user2 and user3 are not. There entry is getting created in IDM.
When I open the IDM object I get a yellow triangle (warning) and if I open the user object and hit save button IDM creates the user account on the LDAP.
any help for further solving this problem would be appreciated.
Regards,

Call another WebLogic's EJBs from resource adapter?

Similar Messages

Maybe you are looking for