XI Java Proxy deploy on JBoss

Hello,
Can I deploy XI java Proxy inside JBoss application server
Appreciate you response.
Thanks

Hi,
<b>Yes</b>
You can deploy your Java Proxy inside JBoss Server (in any Application server). But this will be possible only for Client Java Proxy and not for Server Java Proxy.
I have succesfully completed those scenarios.
After generating Client Java proxy, create EJB application with generated Java classes for proxies and deploy it in JBoss.
Then you can access that EJB to pass inputs either in standalone application or some JSP.
Regards,
Uma

Similar Messages

Getting Inbound Java Proxy Exception in method "onMessage"

I have built an Inbound Java proxy, deployed the EJB, viewed it in the J2EE admin tool, registered the JPR settings (also listAll, reviewed results, looks OK), configure the XI scenario. When I run the XI scenario using the Runtime workbench I get the following error in the BPM Synchronous Send step (calling the Java Proxy)
"com.sap.aii.af.ra.ms.api.DeliveryException: Exception in method onMessage".
Does anyone have any suggestions?
What causes an "onMessage" Exception?

Thanks Sudhir Here is the process I am following to deploy my Proxy, would you please validate it. Created EJB Project in NWDS, unziped XI gened proxies into ejbModule folder, renamed *PortTypeImpl.template to *PortTypeImpl.java (will add real code later), compiled all code (no errors), edited ejb_jar.xml to match your suggested format, can view EJB Candidates (and see my Proxy Bean), built EJB.JAR file (via Wizard), created new Enterprise Application Project and pointed build path to my EJB Project, within the Enterprise Application Project I built an EAR file (which includes the "EJB Project JAR File", Deployed Enterprise Application Project to the XI J2EE Engine. I can log into XI J2EE Admin and see my EJB Project and the Proxy Bean I am trying to execute. Is this the process you used to deploy the proxy bean?
Also you you turn on JPR Tracing to see what parameters are passed into the JPR engine?

Deploy XI java Proxy inside JBoss application server

Hello,
Can I deploy XI java Proxy inside JBoss application server
Appreciate you response.
Thanks

Hi,
<b>Yes</b>
You can deploy your Java Proxy inside JBoss Server (in any Application server). But this will be possible only for Client Java Proxy and not for Server Java Proxy.
I have succesfully completed those scenarios.
After generating Client Java proxy, create EJB application with generated Java classes for proxies and deploy it in JBoss.
Then you can access that EJB to pass inputs either in standalone application or some JSP.
Regards,
Uma

Where to deploy EAR file(Client java proxy) in SAP J2EE engine (XI)?

hi i m novice in J2ee technology of XI,
I m trying a blog to create client Java proxy,
can u tell me after making the EAR file .... where should i deploy it,
means it instructs me to deploy the EAR file in the SAP J2EE engine.... what is that .... whats the URL and port ?

Hi sudeep
check these
http://help.sap.com/saphelp_nw04/helpdata/en/01/a70e408230c442e10000000a1550b0/frameset.htm
http://help.sap.com/saphelp_nw70/helpdata/en/9c/8a9383a2aeda4a962446d3c29b9e19/frameset.htm
http://help.sap.com/saphelp_nw70/helpdata/en/05/4fac3e00c8b014e10000000a114084/frameset.htm
also this
/message/3943924#3943924 [original link is broken]
thanks

Facing Problem in Deploying EAR for Client Java Proxy.

Hi All,
            I am facing problems in deploying EAR in PI/XI server.
The scenario is Client Java Proxy to SAP
. I have followed the the pdf-how to create java proxies in 3.0. Using that I have created the EJB module and it archive.
Finally created the EAR without errors. But while deploying the same in PI server, it throws the following error. Please do help me out in providing any inputs on the same.
Deploy trace is seen below:-
Deploy of the ear has errors :
java.rmi.RemoteException: Cannot deploy application sap.com/BusPartnerEAR..
Reason: Errors while compiling:
D:/usr/sap/ECD/DVEBMGS03/j2ee/cluster/server0/apps/sap.com/BusPartnerEAR/EJBContainer/temp/temp1175887267437/com/mud/sAPFICA/businessPartner/_MIOSBusinessPartner_PortTypeRemoteObjectImpl0_0_Tie.java:91: illegal escape character
      if (method.equals("U0024descriptor")) {
                          ^
D:/usr/sap/ECD/DVEBMGS03/j2ee/cluster/server0/apps/sap.com/BusPartnerEAR/EJBContainer/temp/temp1175887267437/com/mud/sAPFICA/businessPartner/_MIOSBusinessPartner_PortTypeRemoteObjectImpl0_0_Tie.java:98: illegal escape character
      if (method.equals("U0024jcoRuntimeMetaData")) {
                          ^
D:/usr/sap/ECD/DVEBMGS03/j2ee/cluster/server0/apps/sap.com/BusPartnerEAR/EJBContainer/temp/temp1175887267437/com/mud/sAPFICA/businessPartner/_MIOSBusinessPartner_PortTypeRemoteObjectImpl0_0_Tie.java:112: illegal escape character
      if (method.equals("U0024generationInfo")) {
                          ^
D:/usr/sap/ECD/DVEBMGS03/j2ee/cluster/server0/apps/sap.com/BusPartnerEAR/EJBContainer/temp/temp1175887267437/com/mud/sAPFICA/businessPartner/_MIOSBusinessPartner_PortTypeRemoteObjectImpl0_0_Tie.java:119: illegal escape character
      if (method.equals("U0024messageSpecifier")) {
                          ^
D:/usr/sap/ECD/DVEBMGS03/j2ee/cluster/server0/apps/sap.com/BusPartnerEAR/EJBContainer/temp/temp1175887267437/com/mud/sAPFICA/businessPartner/_MIOSBusinessPartner_PortTypeRemoteObjectImpl0_0_Tie.java:152: illegal escape character
      if (method.equals("U0024runtime")) {
                          ^
D:/usr/sap/ECD/DVEBMGS03/j2ee/cluster/server0/apps/sap.com/BusPartnerEAR/EJBContainer/temp/temp1175887267437/com/mud/sAPFICA/businessPartner/_MIOSBusinessPartner_PortTypeRemoteObjectImpl0_0_Tie.java:195: illegal escape character
      if (method.equals("U0024messageSpecifierRead")) {
                          ^
D:/usr/sap/ECD/DVEBMGS03/j2ee/cluster/server0/apps/sap.com/BusPartnerEAR/EJBContainer/temp/temp1175887267437/com/mud/sAPFICA/businessPartner/_MIOSBusinessPartner_PortTypeRemoteObjectImpl0_0_Tie.java:202: illegal escape character
      if (method.equals("U0024messageSpecifier__")) {
                          ^
D:/usr/sap/ECD/DVEBMGS03/j2ee/cluster/server0/apps/sap.com/BusPartnerEAR/EJBContainer/temp/temp1175887267437/com/mud/sAPFICA/businessPartner/_MIOSBusinessPartner_PortTypeRemote_Stub.java:93: illegal escape character
          org.omg.CORBA_2_3.portable.OutputStream out = (org.omg.CORBA_2_3.portable.OutputStream)_request("U0024descriptor", true);
                                                                                ^
D:/usr/sap/ECD/DVEBMGS03/j2ee/cluster/server0/apps/sap.com/BusPartnerEAR/EJBContainer/temp/temp1175887267437/com/mud/sAPFICA/businessPartner/_MIOSBusinessPartner_PortTypeRemote_Stub.java:112: illegal escape character
      ServantObject so = servantpreinvoke("U0024descriptor", MIOSBusinessPartner_PortTypeRemote.class);
                                              ^
D:/usr/sap/ECD/DVEBMGS03/j2ee/cluster/server0/apps/sap.com/BusPartnerEAR/EJBContainer/temp/temp1175887267437/com/mud/sAPFICA/businessPartner/_MIOSBusinessPartner_PortTypeRemote_Stub.java:134: illegal escape character
          org.omg.CORBA_2_3.portable.OutputStream out = (org.omg.CORBA_2_3.portable.OutputStream)_request("U0024jcoRuntimeMetaData", true);
                                                                                ^
D:/usr/sap/ECD/DVEBMGS03/j2ee/cluster/server0/apps/sap.com/BusPartnerEAR/EJBContainer/temp/temp1175887267437/com/mud/sAPFICA/businessPartner/_MIOSBusinessPartner_PortTypeRemote_Stub.java:153: illegal escape character
      ServantObject so = servantpreinvoke("U0024jcoRuntimeMetaData", MIOSBusinessPartner_PortTypeRemote.class);
                                              ^
D:/usr/sap/ECD/DVEBMGS03/j2ee/cluster/server0/apps/sap.com/BusPartnerEAR/EJBContainer/temp/temp1175887267437/com/mud/sAPFICA/businessPartner/_MIOSBusinessPartner_PortTypeRemote_Stub.java:216: illegal escape character
          org.omg.CORBA_2_3.portable.OutputStream out = (org.omg.CORBA_2_3.portable.OutputStream)_request("U0024generationInfo", true);
                                                                                ^
D:/usr/sap/ECD/DVEBMGS03/j2ee/cluster/server0/apps/sap.com/BusPartnerEAR/EJBContainer/temp/temp1175887267437/com/mud/sAPFICA/businessPartner/_MIOSBusinessPartner_PortTypeRemote_Stub.java:235: illegal escape character
      ServantObject so = servantpreinvoke("U0024generationInfo", MIOSBusinessPartner_PortTypeRemote.class);
                                              ^
D:/usr/sap/ECD/DVEBMGS03/j2ee/cluster/server0/apps/sap.com/BusPartnerEAR/EJBContainer/temp/temp1175887267437/com/mud/sAPFICA/businessPartner/_MIOSBusinessPartner_PortTypeRemote_Stub.java:257: illegal escape character
          org.omg.CORBA_2_3.portable.OutputStream out = (org.omg.CORBA_2_3.portable.OutputStream)_request("U0024messageSpecifier", true);
21 errors
Awaiting for your replies...
Regards,
Dhana

Hi,
     Thanks for your input..
   I have also opend the EAR as ZIP file and deleted the existing listing libaries
apart from the actual implementing Jar and META-INF folder.
I have tried deploying the Jar for the second time, it is throwing the same error.
What I did is...Once the EAR is created, I went to Resource perspective in NWDS and copied the EAR from the EAR project and used the same for deployment.
Is there is anything else to be modified or deleted before deployement?
Regards,
Dhana

Porblem with Java Proxy EJB deploy to XI through NWDI

Situation - I have a web app in Server A (WAS7), it needs to call a java proxy in Server B (XI WAS7). I want to deploy the Java Proxy EJB into the landscape using NWDI. To do this I created an external library with public parts that contains the required jars to build the java proxies. These are aii_msg_runtime.jar, aii_proxy_xirt.jar, and aii_utilxi_misc.jar. The EJB module used part is mapped to the library's public parts. Everything builds fine and the deployment was successful into XI.
Problem - When my web application makes a remote call to the java proxy in XI, NoClassDefFoundError occurs. The first jar that it complain about was aii_util_cimaccess.jar. I included this jar into the library and redeployed. Called the java proxy again, and got another NoClassDefFoundError exception. Now it wanted the lrcclient.jar. I included that into the library and redeployed. Now it wanted another jar. The issue is that all these jars are in the XI server and I shouldn't have to add them as part of the library. Is there a SCA out there that contains these jars, or did I just forget to mark a checkbox somewhere when creating the EJB so that it would reference the XI jars without me adding them to the library?
Note - This architecture works fine without having to add the jars above, if I deploy the Java Proxy EJB from my workspace to XI through the SDM process available through NWDS. This only breaks when I deploy through NWDI.
Thank you in advance.

HI,
please see the below link
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/bc7f08e1-0901-0010-b1bd-80966009d8f0
http://help.sap.com/saphelp_nw2004s/helpdata/en/40/00be09879f114aa1ec46c2afa4445b/frameset.htm
To add On-
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/9221b490-0201-0010-0e90-8cc75cde876c
http://help.sap.com/saphelp_webas630/helpdata/en/cb/f4bc3d42f46c33e10000000a11405a/content.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/eaeb475d-0c01-0010-f5a4-d7a8eb185793
Regards
Chilla

Error when deploy Java Proxy Server EAR to PI

We are trying to deploy our Java Proxy Server EAR to PI using Visual Administrator. However, it gives the following error:
Deploy of the ear has errors :
java.rmi.RemoteException: Cannot deploy application sap.com/TestBatch
Reason: Errors while compiling:
.... .java:91 illegal escape character
if (method.equals("U0024descriptor")) { ....
We have tried to deploy the same EAR to another PI system and it works fine. As a result, we think we might have missed something when installing or configuring this PI but don't have a clue where to start. We have also tried deploying using SDM but also didn't succeed.

Hi Pikad !
I understand that it the very same EAR deployed with no hassle in another PI, here it should work ok, but I think you should check the backslash you are using. If you need to use the backslash character, you must use ("
U0024descriptor") or change the U to \u0024 for the dollar sign.
Check:
Regards,
Matias.

Java.io.InvalidClassException: org.jboss.proxy.Interceptor...

Hi there,
I'm working on a JSP running on a Tomcat server 4.0.1. Such JSP calls a Servlet, which tries to recover an EJB:
     public CommunityEJB getCommunityEJB() throws UnexpectedException
          CommunityEJB lRet = null;
          CommunityEJBHome lhome = null;
          Context jndiContext = null;
          try
               lhome = (CommunityEJBHome) ServiceLocator.getInstance().getEJBHome(JNDINames.EJB_COMMUNITY);
               lRet = lhome.create();
          catch (Exception e)
               UnexpectedException ue = new UnexpectedException(e);
               logger.throwing(CLASS_NAME, "getCommunityEJB", ue);
               throw ue;
          return lRet;
The EJB is recovered though JNDI, running on JBoss 3.2.1. Tomcat server and JBoss are running separately (Tomcat I'm using is not the embedded in JBoss).
The code above throws the next exception:
tuamo.core.exception.UnexpectedException: javax.naming.CommunicationException [Root exception is java.io.InvalidClassException: org.jboss.proxy.Interceptor; local class incompatible: stream classdesc serialVersionUID = 4358098404672505200, local class serialVersionUID = 8774269974037850782]
Can anybody help me with this?
Thanks!!

The EJB client jar is out of sync with the EJB server jars. In simple words, you might have recompiled any or all of the following and either only redeployed it on the server or dropped it in the client classpath depending on where did you make the changes.
home interface
remote interface
types being passed over the methods in these interfaces (parameters, return values, etc.)
I'm not quite sure what you mean by recovering an EJB? Typically its called looking it up.

Java Proxy Runtime: failure to locate proxy bean on inbound call

Hello gurus of the SDN,
I have been trying to get an inbound Java Proxy scenario to work in XI 3.0 but have not been able to get the JPR to recognize my generated and deployed java code. My scenario is set up to call the java proxies generated from a message interface based on the MATMAS Idoc. I successfully deployed the generated java proxies on the same host box as is running the XI instance. The objects are named as follows
Message interface on XI = Inbound_MATMAS04
Generated proxy bean = Inbound_MATMAS04_PortTypeBean
Implementing class = InboundMATMAS04_PortTypeImpl
Implementing method = inboundMATMAS04
I used the JPR transport servlet to register the interface and implementing class but am not sure if I did this correctly. I used the following entry in my web browser:
http://nadcp786:50000/ProxyServer/register?
ns=urn:xiTrainingLabs:groupXX:SAP&
interface=InboundMATMAS04&
bean=InboundMATMAS04_PortTypeImpl&
method=inboundMATMAS04
I also tried using the localejb/ prefix for the bean name in the above step since the code is co-located. When I trigger the scenario, the Idoc info is passed into XI and the Java Proxy Runtime is called, but I get the following error response back in the SOAP header:
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="PARSING">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: Cannot locate proxy bean InboundMATMAS04_PortTypeImpl: com.sap.aii.proxy.xiruntime.core.XmlInboundException: Cannot locate proxy bean InboundMATMAS04_PortTypeImpl</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Finally, appended at the end of this post is the audit log of the messaging system showing that the JPR is called but without being able to locate the bean. I think I am missing a configuration step somewhere, but cant figure out what it is!! Can anyone help me?
Many thanks in advance.
Regards,
Nick Simon
Time Stamp     Status     Description
2004-10-25 19:47:32     Success     The message was successfully received by the messaging system. Profile: XI URL: http://nadcp786.bcsdc.lexington.ibm.com:50000/MessagingSystem/receive/JPR/XI
2004-10-25 19:47:32     Success     Using connection JPR. Trying to put the message into the receive queue.
2004-10-25 19:47:32     Success     The message was successfully retrieved from the receive queue.
2004-10-25 19:47:32     Success     The message status set to DLNG.
2004-10-25 19:47:32     Success     Java proxy runtime (JPR) accepted the message
2004-10-25 19:47:34     Error     JPR could not process the message. Reason: Cannot locate proxy bean localejbs/InboundMATMAS04_PortTypeImpl
2004-10-25 19:47:34     Error     Delivery of the message to the application using connection JPR failed, due to: Cannot locate proxy bean localejbs/InboundMATMAS04_PortTypeImpl.
2004-10-25 19:47:34     Error     The message status set to FAIL.
2004-10-25 19:47:34     Error     Asynchronous error detected: Cannot locate proxy bean localejbs/InboundMATMAS04_PortTypeImpl. Trying to report it.
2004-10-25 19:47:34     Error     Asynchronous error reported.
Message was edited by: Nicholas Simon

Hi
How do you determine the JNDI naming of the a EJB?
I have following entry in JNDI directory in the root
Object Name FlightQueryIn
Class Name javax.naming.Reference
Context Name
Object Value Reference Class Name:
Type: clientAppName
Content: sap.com/JavaProxyEAR
Type: interfaceType
Content: remote
Type: home
Content: com.sap.aii.proxy.xiruntime.core.AbstractProxyInboundHome4
Type: ejb-link
Content: FlightSeatAvailabilityQueryIn_PortTypeBean
Type: jndi-name
Content: FlightQueryIn
Type: remote
Content: com.sap.aii.proxy.xiruntime.core.AbstractProxyInboundRemote4
I tried to register the bean with JPR using:
http://ctsapxid01:50100/ProxyServer/register?ns=http://sap.com/xi/XI/Demo/Airline&interface=FlightSeatAvailabilityQuery_In&bean=FlightQueryIn&method=flightSeatAvailabilityQueryIn
I followed the following blog
http://wiki.sdn.sap.com/wiki/display/Java/JavaProxyChangesinPI7.1fromPI7.0
Thanks,
Chris

Error while running java proxy in PI 7.1

Hi All,
I had created a java proxy using nwds 7.1. This java proxy is called by XI channel and its synchronous.
WHen i run my scenario in PI i am getting a error "Error while sending message: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error processing inbound message. Exception: No remote bean found for reference of class $Proxy2919
Kindly help me finding what can be the issue.
Regards,
Rajesh

Go to the JNDI Browser (Nwa -> Problem Management), and check if the proxy was deployed correctly with the exact name "Proxy2919".
Also, check the OSS note below.
#1292633 - JPR: Throwing "No remote bean found for reference of class"

BC4J deploy in JBoss 3.0.3

While trying to deploy a BC4J app in JBoss 3.0.3, the
following Exception was raised:
java.lang.ClassCastException: org.jboss.resource.adapter.jdbc.local.LocalPreparedStatement
All the steps listed in OTN's articles were done:
http://otn.oracle.com/products/jdev/howtos/appservers/deploy_bc4j903_to_jboss303.html
http://otn.oracle.com/products/jdev/howtos/bc4j/ejbstateless_with_bc4j.html
Trying to access AppModule without de Stateless EJB Session as a client, the Exception was:
java.lang.IllegalStateException: No security context set.
Has anyone seen something like that?

What version of BC4J do you use? If it is 9.0.4, you have to add more libraries to Jboss.

EJB 3.0 deployment on JBoss - No ClassLoaders found

I have problem deploying a simple EJB 3.0 jar file , it contains an Interface , its Bean and the jboss.xml
jboss.xml
<?xml version="1.0" encoding="UTF-8"?>
<jboss>
<enterprise-beans>
<session>
<ejb-name>ServerDBConnectionBean</ejb-name>
<management>org.jboss.ejb3.test.service.ServiceSixManagement</management>
<ejb-class>connection.server.ServerDBConnectionBean</ejb-class>
<remote>connection.server.ServerDBConnection</remote>
<jndi-name>ServerDBConnectionBean</jndi-name>
</session>
</enterprise-beans>
</jboss>
The problem is that when i deploy this jar file in JBoss , it says .........
12:10:17,988 WARN [ServiceController] Problem creating service jboss.j2ee:service=EJB3,module=server.jar
java.lang.ClassNotFoundException: No ClassLoaders found for: connection.server.ServerDBConnectionBean
at org.jboss.mx.loading.LoadMgr3.beginLoadTask(LoadMgr3.java:212)
at org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryClassLoader.java:511)
at org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:405)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at org.jboss.ejb3.Ejb3AnnotationHandler.populateBaseInfo(Ejb3AnnotationHandler.java:265)
at org.jboss.ejb3.Ejb3DescriptorHandler.populateBaseInfo(Ejb3DescriptorHandler.java:202)
at org.jboss.ejb3.Ejb3AnnotationHandler.getContainers(Ejb3AnnotationHandler.java:123)
at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:409)
at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:397)
at org.jboss.ejb3.Ejb3Deployment.deployUrl(Ejb3Deployment.java:378)
at org.jboss.ejb3.Ejb3Deployment.deploy(Ejb3Deployment.java:350)
at org.jboss.ejb3.Ejb3Deployment.create(Ejb3Deployment.java:305)
at org.jboss.ejb3.Ejb3Module.createService(Ejb3Module.java:77)
at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:243)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.create(Unknown Source)
at org.jboss.system.ServiceController.create(ServiceController.java:330)
at org.jboss.system.ServiceController.create(ServiceController.java:273)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy28.create(Unknown Source)
at org.jboss.ejb3.EJB3Deployer.create(EJB3Deployer.java:429)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238)
at org.jboss.ws.integration.jboss.DeployerInterceptor.create(DeployerInterceptor.java:74)
at org.jboss.ws.integration.jboss.DeployerInterceptorEJB.create(DeployerInterceptorEJB.java:44)
at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180)
at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy29.create(Unknown Source)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:959)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at sun.reflect.GeneratedMethodAccessor25.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy8.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225)
I suppose the problem is with the package , cause when i deploy with single package hirarechy i.e; server.ServerDBConnectionBean , it works .
Kindly any suggestions

hi
I think you ur jboss.xml is wrong.
Try using like this for EJB3
     <enterprise-beans>
          <session>
               <ejb-name>XXX</ejb-name>
               <jndi-name>XXXX</jndi-name>
               <local-jndi-name>XXXXX</local-jndi-name>
          </session>
     </enterprise-beans>I think <ejb-class> is not supported in jboss.xml..
Regards
Srinivas

Help - how to create java proxy (sender) in NWDS 7.1

Hi,
I am trying to develop a java proxy as sender to send message from WAS to PI.
I am using NWDS 7.1. Let me explain what I have done so far,
1. Received proxy classes from PI
2. Created a EJB Project, imported the proxy classes into EJB project
3. created a EJB bean, local interface in the EJB project and exposed as webservice
4. added the ejb to an ear
5. added reference to the following jar files (external library)
tcaiiproxy_rt_api.jar
com.sap.aii.af.sdk.jar
com.sap.aii.utilxi.server.jar
com.sap.aii.utilxi.core.jar
com.sap.aii.proxy.svc_api.jar
6. able to build and deploy the application
7. able to open the webservice in wsnavigator
Error encountered:
"Server Exception: javax.ejb.EJBException: nested exception is: java.lang.RuntimeException: java.lang.NoClassDefFoundError: com/sap/aii/proxy/xiruntime/core/AbstractType "
Questions:
1. Which method I should execute / call among all the proxy classes from local bean class to send message to PI?
2. Is it mandatory to add refernces to the application.xml, ejb-jar.xml and other xmls ?
3. How can I test / monitor the message being sent to PI interface?
Thanks and best regards,
Arun prabhu S

plz cross chk the references under application-j2eeengine.xml and ejb-jar.xml
http://wiki.sdn.sap.com/wiki/display/Java/JavaProxyChangesinPI7.1fromPI7.0
u can chk tis article also:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/508bb504-87cf-2c10-2aaf-f3a5df75e651?quicklink=index&overridelayout=true

Unable to invoke java proxy in PI 7.1

Hi ,
I am using NWDS 7.2 (Trial ver) and using it to deploy java proxy on PI 7.1.
I also registered the interface using http://<pi>:<port>/ProxyServer url
But when I invoke the proxy I get the error as
"Cannot locate proxy bean"
Please tell me what to do...
regards,
Piyush

Hi,
This sort of error usually comes when JPR cannot find the deployed java server proxy bean.
1) Register ur server proxy using this :
http://host:port/ProxyServer/register?ns=xxx&interface=SI_Proxy_IA&bean=localejbs/Jndi-name&method=method name
refer this: http://help.sap.com/saphelp_nw04/helpdata/en/a4/d5b3b0b16843b3867c0245d9847ae5/content.htm
2)Chk whether u have mentioned the corrcet JNDI name while registering the URL.
3) Chk ur JNDI name under NWA.
4) Chk ur references under application-j2ee-engine.xml.
<?xml version="1.0" encoding="UTF-8"?>
<application-j2ee-engine xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="application-j2ee-engine.xsd">
<reference reference-type="weak">
<reference-target provider-name="sap.com" target-type="library">com.sap.aii.af.sdk.lib</reference-target>
</reference>
<reference reference-type="weak">
<reference-target provider-name="sap.com" target-type="service"> com.sap.aii.proxy.svc</reference-target>
</reference>
<reference reference-type="weak">
<reference-target provider-name="sap.com" target-type="library">com.sap.xi.util.misc</reference-target>
</reference>
<reference reference-type="weak">
<reference-target provider-name="sap.com" target-type="library">com.sap.guid</reference-target>
</reference>
</application-j2ee-engine>
Thanks
Amit

Java Proxy error

Hi,
I have generated and deployed Java server proxy successfully in PI 7.1.
The problem is I am getting a error as follows
com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error processing inbound message. Exception: Cannot locate proxy bean sap.com/HTTPEAR/DeliveryInImp
I have regiered the bean using the URL already.
Should i add any jar references to my EAR explicitly and redeploy.
Regards,
Sudharshan N A

Hello,
You need to add the references of the proxy libraries (jars) in application-j2ee-engine.xml. Once you build the .ear file, you need to delete the libraries by unziping the .ear. Because, the proxy libraries (jar) should not be deployed as there are already existed in J2EE engine. Refer the following blog
/people/thorsten.nordholmsbirk/blog/2006/08/06/use-a-java-proxy-instead-of-a-jca-adapter
Regards,
Prasanna

XI Java Proxy deploy on JBoss

Similar Messages

Maybe you are looking for