on 10-22-2009 5:35 AM
Hi All,
I have created one async Java Server Proxy Scenario in PI7.1 using NWDS7.1. I have successfully completed the below mentioned steps:
1) Created and deployed my java proxy EAR file on non central adapter engine.
2) Successfully registered my server proxy interface using the followng URL:
where Jndi- name is: JavaProxy2
But when i am seeing the audit log (under RWB->message monitoing) i am getting some exception and my message status turns into the SystemError . The exception is like this:
Delivering the message to the application using connection JPR failed, dueto:com.sap.engine.interfaces.messaging.api.exception
.MessagingException: Error processing inbound message. Exception: Cannot locate proxy bean localejbs/JavaProxy2.
I have looked almost all the post related to this exception but can't able to figure out the problem.
So, request you all to help me.
Thanks
Amit
Hi Amit,
Try this:
Register in
http://yyyy:51000/ProxyServer/register?ns=xxx&interface=SI_Proxy_IA&bean=JavaProxy3&method=sIProxyIA
don't use local ejbs as it is in decentral adapter engine
Check the document
http://help.sap.com/saphelp_nwpi711/helpdata/en/a4/d5b3b0b16843b3867c0245d9847ae5/frameset.htm
There it is specified
http://<Host>:<Port>/ProxyServer/register?ns=<Namespace>&interface=<MessageInterface>&bean=<JNDI_Name>&method=<MethodName>
Regards
Suraj
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Suraj,
I have already tried this and registered my java server proxy interface after removing prefix(localejbs):
But still same exception is coming.
Delivering the message to the application using connection JPR failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error processing inbound message. Exception: Cannot locate proxy bean JavaProxy3.
Thanks
Amit
Hi Amit,
>>Created and deployed my java proxy EAR file on non central adapter engine.
In XI adapter the Adapter Engine should point to de-central adapter engine. Try this
Regards
Suraj
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Amit,
You are calling a java proxy through PI right? So you might have used XI communication channel for this in the agreement. There in the communication channel, there is a option to specify the Adapter Engine, by default this is always Integration Server, but in your case proxy is on a decentral adapter so you need to change this to the FQDN of the decentral adapter (it should come in the drop down)
Regards
suraj
Hi Suraj,
As recommended, i was trying to change the Adapter Eninge from Integration Server to the FQDN of the decentral adapter( af.pae.isvsappisb) but it is not coming under that drop down. The strange thing is that for all other adapter types like SOAP,JDBC, FILE etc the Adapter Engine is haing two entries like:
1) Intergration Server'
2) af.pae.isvsappisb
but when i am trying to select XI as my adapter type then Adapter Engine contains only Integration Server.
Please suggest some solution.
Thanks
Amit
Hi Suraj,
I think that the XI communication channel which i am using for my java server proxy is fine becoz after selecting XI as my adapter type then Adapter Engine contains Integration Server(by default) there i used to write the port number(in this case it is the port number of non central adapter engine where my proxy beans are deployed) as shown below:
Adapter type: XI
Adapter Engine: Integration Server.
Addressing type: URL address
Target Host: YYYY
Service number: 51000( port number pointing towards the non central adapter engine installed)
And also the message log which is coming under MDT is like this after running the scenario:
2009-10-29 11:55:01 Information The message was successfully received by the messaging system. Protocol: XI URL: http://YYYY:51000/MessagingSystem/receive/JPR/XI Credential (User): XXXX
2009-10-29 11:55:01 Information Using connection JPR. Trying to put the message into the receive queue.
2009-10-29 11:55:01 Information Message successfully put into the queue.
2009-10-29 11:55:01 Information The message was successfully retrieved from the receive queue.
2009-10-29 11:55:01 Information The message status was set to DLNG.
2009-10-29 11:55:01 Information Java Proxy Runtime (JPR) accepted the message.
2009-10-29 11:55:24 Error JPR could not process the message. Reason: Cannot locate proxy bean JavaProxy3.
2009-10-29 11:55:24 Error Delivering the message to the application using connection JPR failed, due to:
com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error processing inbound message. Exception: Cannot locate proxy bean JavaProxy3.
2009-10-29 11:55:24 Information The message status was set to WAIT.
Please suggest some solution.
Thanks
Amit
Hi All,
Any idea?? Please help.
Thanks
Amit
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.