on 02-16-2011 6:16 AM
Hi Experts,
I have a scenario where the data is triggered from a Portal and data gets updated into the SAP R3. This is a Soap --> Proxy.
When the data is triggered the SAP is not updated with the data. The moni is not showing any messages.
The Portal team says that they get the follwing message.
(ProjectResourceBundle.java:264) - getBundle(org.apache.axis,org.apache.axis.i18n,resource,null,...)
=[Feb 16 10:51:03] DEBUG (ProjectResourceBundle.java:423) - loadBundle: Ignoring MissingResourceException: Can't find bundle for base name org.apache.axis.resource, locale en_US
=[Feb 16 10:51:03] DEBUG (ProjectResourceBundle.java:318) - Created org.apache.axis.i18n.resource, linked to parent null
=[Feb 16 10:51:03] DEBUG (ProjectResourceBundle.java:264) - getBundle(org.apache.axis,org.apache.axis.utils,resource,null,...)
Have anyone faced this. Could you please tell me what should be done.
Edited by: Lavanya Ravi on Feb 16, 2011 7:18 AM
Thank you everyone for your replies.
The issue is resolved. The technical setting was not maintained in the sxmb_adm in R3 system.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you everyone for your reply.
I have generated the WSDL again and the portal team is using it now. When they execute it, the portal team is getting an error log "No service HTTP found".
Also in PI SOAP sender communication channel, i am getting the following error:
com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIServer:DESTINATION_NOT_FOUND:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Since it's a soap sender, there won't be any destination maintained for this right?
Also, now i gave the portal team the WSDL again. The portal team replied that they are not able to consume the WSDL and that it's showing "class methods missing" error. Is this error coming becasue of PI or is this error coming at their end?
Edited by: Lavanya Ravi on Feb 24, 2011 7:28 AM
Hi ,
check if the wsdl contains URL in below format.
http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel
Also check your wsdl having operation attached proper parameters
Regards
Pradeep P N
Yes Adish . ECC will be giving back a response. But in this case, data itself is not coming from the portal. The SOAP CC is showing Destination not found error. This same error is received in the Portal end when they are sendind the data.
Does it mean that the error that the SOAP CC is showing, is the error that the Portal team is receiving? Is the CC receiving that error message from the Portal team? or is it an PI error message.
Please clarrify this as i am now not able to find out if the problem is in the PI end or the portal end.
Edited by: Lavanya Ravi on Feb 24, 2011 7:47 AM
Hi,
Did you tested the WSDL provided to the portal team using any soap tool like SOAPUI or XMLSPY..
if not test the same and if you are getting the error still then check the configuration of PI whehter any other scenarios are working or not...also do SLDCHEK to know the status of PI system configuraiton..
HTH
Rajesh
This was previously running fine. But was not used for a long time.
Now when they ran it it started to show the error that i had mentioned above.
In the RWB, it's now showing an error:
com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIServer:DESTINATION_NOT_FOUND:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
Check the port they are using. Is it correct? Basis team can provide you more information, about the request entering from Portal is reaching in PI or not.
Also have you checked in SXMB_ADM -> Integration Engine Configuration->Corresponding Integ.
Server RFC destination type HTTP? Does connection test work fine in SM59?
-Rahul
hi Nayan,
The web service is created. The portal team was maintaining a WSDL previously and that had a ip in it. This ip is not the XI production ip. Hence the portal team replaced the old ip with the XI production ip. Now when the portal team triggers, moni is showing internal error. Error message is HTTP Destination not maintained.
Should this be maintained anywhere or should the WSDL be replaced fully?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
1. Try to check the WSDL again using XML spy and test it from it.
2. Generate the WSDL again in PI and use that for sending.
3. What is the link of URL r u using,to send it from Portal.
4. Check the SOAP comm channel configuration
5. Did u check the soap comm channel from RWB component monitoring.
chirag
Hi Ravi,
Have you created web service defination in XI?
If no, then create web service definition for the soap comm channel and provide that WSDL to portal team to create client proxy at portal end.
If yes, then try to open comm channel URL (SOAP URL in the WSDL) from the portal server. check whether it is sowing any error or not?
Rgards,
Nayan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi ,
I am not sure how much this is gonna help you ,but please go through the forum :
http://wso2.org/forum/thread/5249
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
83 | |
24 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.