inbound proxy issue

[Former Member]

Hi Gurus,

my interface is file to proxy scenario.

Im placing the file in the source directory of PI server and the file is picked up.I used message split and mapping is successfull but the data is not being sent to the SAP system using inbound proxy.

I created the inbound proxy in SAP system in sproxy.

Im not seeing any messages in sxmb_moni in GRD system.

I feel there is something wrong with the HTTP destination created in the PI server which is pointing to the SAP system.

Can you please send the HTTP destination details that has to be created in SM59 transaction.

Thanks,

Jay.

[PriyankaAnagani · Accepted solution]

Hi,

What is the status of message in SXMB_MONI of PI sytem...?while creating an RFC destination of type H in PI pointing to backend, you need to specify the targethostname,serviceNo ie ABAPhttp port number, and pathprefix..that is like /sap/xi/engine?type=entry..&logon details....Please check it and let me know on furrther queries....

Regards

Priyanka

[Former Member · Accepted solution]

Hi Priyanka,

Thanks for the reply.

my RFC destination of type H is pointing to the SAP backend and the path prefix given is /sap/xi/engine?type=receiver.

The service no given is ABAP HTTP port. and logon details are PIAPPLUSER.

case 2:

on sender side i used file adapter and on receiver side I used file dapter the input is split into multiple files and placed in the target directory.The interface is successfull.

case 1:

on sender side i used file adapter and on rceiver side I used inbound proxy in the sxmb_moni it is throwing error in the below

way

"Messages in multi-message format can only be sent to one Adapter Engine"

I used receiver XI adapter to send the message to SAP ECC system wherein i gave HTTP destination.

I dont know why the error is being thrown in PI.

Any help appreciated.

Thanks,

Jay.

[PriyankaAnagani · Accepted solution]

Hi,

Messages that result from the split in a mapping-based message split are sent using one AE. So only adapters running on the AE are supported. In particular, this means that Inbound proxy message splits are not supported i think. You have to use BPM for this because ABAP proxy uses the abap stack and multimapping without BPM requires java stack.

Thanks

Priyanka

[abhay_rajhans2 · Accepted solution]

Hi Jay,

Multimessaging is supported in the case of only adapters running on AE (Adapter engine). XI adapter used for proxy runs on IE (Integration engine) so it does not support the multimessaging. Due to that you are getting error .

The work around can be crate following type of message type at received end or use BPM

mt_proxy 1..1

..records 1..unbounded.. (Pass the multiple records to this record. and under Record define all the fields which you want. Depending on condiition populate the fields Write logic in ABAP proxy for data validation and further processsing)

Edited by: Rajhans Abhay on Jul 7, 2011 2:19 PM

[Former Member · Accepted solution]

Hi,

Try replacing your XI adapter with SOAP adapter and Message Protocol as XI.

Provide Target URL as: HTTP://HostName:Portnumber/sap/xi/engine?type=entry. Where Host Name and Port Number belongs to your ECC system.

Regards

Praveen K

[Former Member · Accepted solution]

can you please tell me what port i need to give to the receiver soap adapter.

Thanks,

Jay.

[Former Member · Accepted solution]

Hi ,

I used SOAP receiver adapter with target URL http://hneccdci01s.glasgow.gov.uk:8080/sap/xi/engine?type=entry,the message is going to SAP ECC system using the channel but Im getting error in the runtime workbench stating that

SOAP: request message entering the adapter with user J2EE_GUEST

SOAP: call failed: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 401 Unauthorized

MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: invalid content type for SOAP: TEXT/HTML; HTTP 401 Unauthorized: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 401 Unauthorized

Can you please help me

in the SOAP receiver channel i gave the transport protocol as HTTP and mesage protocol as SOAP 1.1

Thanks,

Jay.

[Former Member · Accepted solution]

Hi Gurus,

I have used receiver SOAP communication channel to send messages resulted from multimapping to SAP ECC sytem.

The message is failing to go to SAP ECC system.

In the channel I gave the target URL

http://SAP Host:port/sap/xi/engine?type=entry

the user id ,pwd i gave the logon user pwd.

I checked the configure proxy box

where i gave the host as SAP HOST,port SAP port.

user ---PIAPPLUSER

pwd--pwd

The log which i can see in the Runtime Workbench is below:

MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault

Any help appreciated.

Thanks,

JAy

[Former Member · Accepted solution]

Hi Jay,

I hope you have configured ICO-Integrated Configuration Object for your scenario, instead of classical Interface objects.

Message Split - you can manipulate in AAE using SOAP at Receiver end, and providing Message Protocol as XI 3.0. Which will send Messages to your Integration Engine of your ERP but Message Split happens in Advance Adapter Engine.

Note this is available in PI 7.1 EHP 1.

Regards

Praveen K

[Former Member · Accepted solution]

Hi Praveen,

Im not using PI 7.1 ..Im currently using PI 7.0

Im using receiver SOAP adapter to send message to inbound proxy in SAP ECC system.

I followed the blog

/people/praveen.gujjeti/blog/2010/01/14/calling-abap-proxies-using-soap-and-http-adapters-in-sap-xi30pi70

and I gave the target URL in the soap adapter in this way

http://hneccdci01s.glasgow.gov.uk:8000/sap/xi/adapter_plain?namespace=http://access/prototypes/PECOS...

and I checked the "Do not use Enevelope" and "Keep Headers" as per the log.

my soap channel is still throwing the error.

Delivering to channel: CC_SOAP_RECEIVER

MP: Entering module processor

MP: Processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean

SOAP: request message entering the adapter with user J2EE_GUEST

SOAP: completed the processing

SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 403 Forbidden

SOAP: sending a delivery error ack ...

Thanks,

Jay.

[Former Member · Accepted solution]

can anyone pls tell me whether im giving the proper URL or is there any issue with URL.

Thanks,

Jay.

[naveen_chichili · Accepted solution]

Jay,

Check if your Integration Engine configuration is correctly maintained in SXMB_ADM.

Regards,

Naveen

[Former Member · Accepted solution]

Hi Jay,

XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 403 Forbidden

This should be some User Authorization issue. Check the roles assigned for your communication user. Whether he is allowed to process the request XML in your target system.

Regards

Praveen K

[Former Member · Accepted solution]

Hi Jay,

"http://hneccdci01s.glasgow.gov.uk:8000/sap/xi/adapter_plain?namespace=http://access/prototypes/PECOSCXML&interface=mi_test_cxml&service=GRD&party=&agency=&schema=&client=110&sap-language=EN"

mi_test_cxml

I understood that your are processing CXML, check whether your target system is able to process this request instead of XML in proxy.

Let me know if my understand is correct.

Regards

Praveen K

[former_member472138]

Hello jay,

Check the basic stuff like SLDCHECK.

Also see that in target system - sproxy Tcode Connection to ESR should be fine and all reports are fine. If yes, check the messages in target system using SXMB_MONI and analyse.

If not then take the help of basis and finish it out.

Regards

Pothana

[Former Member]

I would suggest , search for the proxy baseline steps ..

Plus try executing sldcheck from your R3 system

and from SLDAPICUST , check if password is correct maintained..

[Former Member]

Hi,

Check this doc by Vikas

[Internal Communication: ABAP Proxy and Process Integration|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/50d69314-1be0-2b10-11ab-8045021f0c3a?quicklink=index&overridelayout=true]

Regards

Praveen K