cancel
Showing results for 
Search instead for 
Did you mean: 

Integration Engine URL encoding issue

Former Member
0 Kudos

I searched the forum and saw several similar questions, but no answer or solution posted.

We have developed a SOAP -> XI -> RFC integration. It works just fine when the URL created is not encoded. As an example:

http://server:port/sap/xi/engine?type=entry&version=3.0&Sender.Service=myservice&Interface=http://do...

Another intermediary we are using will not allow entry of the target url without encoding, such as:

http://server:port/sap/xi/engine?type=entry&version=3.0&Sender.Service=myservice&Interface=http%3A%2...

When SAP XI receives the encoded query string. It cannot resolve the receiver determination, as we receive the error, RCVR_DETERMINATION.MESSAGE_INCOMPLETE. with text "Message is incomplete. No Sender". It can't decode the sender service.

It all works except, when the integration engine receives an encoded query string. Any ideas on how to resolve this issue?

Thanks,

Jay

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

check the option use encoded headers in the communication channel. that should solve your problem.

Award if helpful,

Sarath.

Former Member
0 Kudos

Sarath,

I believe I tried this last week, but to no avail.

Intuitively this makes sense as the integration engine couldn't figure out which communication channel to use, so settings in the communication channel wouldn't impact the integration engine processing in this case.

Thanks for the suggestion!

Jay

Answers (1)

Answers (1)

Former Member
0 Kudos

Forgot to post I had resolved this.

The way I goit this to work was to go through the SOAP adapter, rather than directly to the integration engine. This results in a URL that does not need to be encoded.

http://server:port/XISOAPAdapter/MessageServlet?channel=:MyService:MyChannel

It appears that the integration engine cannot handle the encoded URL, so it can not determine the receiver to process the message.

Using the SOAP adapter does add latency, but that isn't citical for this transaction.

Jay