SAP R/3 (IDoc) - XI- SAP R/3 (Http)

[Former Member]

Hi

I am doing a IDoc to http scenario. Both the sender and receiver systems are SAP Systems. IDoc side configuration is done and i am getting the idoc into xi system. For Http i have created a http receiver channel with RFC destination type H on xi system. It does not work and says message processing not allowed.

Target: host of receiver

Service no: Http ABAP port of receiver SAP i.e. 8000

path prefix: /sap/xi/engine?type=entry

Logon details:

User and pwd of a user on receiver.Client no of the receiver.

Regards

Monika

[former_member181985 · Accepted solution]

>I have to use http adapter only. Actually the actual target application is not available at the moment (which is going to be another XI system) and the XI box is new, hence testing with a SAP System to rectify the things on my side.

So, if you are posting it to another XI system (which is target system), using HTTP receiver adapter with a RFC destination which points to XI PIPELINE, then logically the message will get processed if you have such configuration in Target XI system.

However, when you test with a SAP R/3 system (which will have a Local XI engine with PIPELINE URL), obviously the configuration will not be there at the SAP R/3 system as it expects an ABAP Proxy kind of messages.

So Your assumption is wrong to use SAP R/3 instead of SAP XI as target system.

Regds,

Gujjeti.

[Former Member · Accepted solution]

Hi

Actually sone sdn threads talk abt it so i think thats possible like

and some more.

Regards

Monika

[former_member181985 · Accepted solution]

>

> Hi
> 
> Actually sone sdn threads talk abt it so i think thats possible like
> 
> and some more.
> 
> Regards
> Monika

This topic explains about posting a message to a servlet which basically runs in a J2EE engine. J2EE engine can be part of SAP Web AS Java or some third party J2EE application server such Weblogic etc.

[Former Member · Accepted solution]

Hi

We could post xml data to the adapter_plain service of a SAP System.

Regards

Monika

[former_member181985 · Accepted solution]

Yes we can. But Adapter Plain is part of ABAP stack.

In XI this sits just before the XI PIPELINE and forwards to PIPELINE.

In SAP R/3 too we will have this plain adapter but not sure what happens next. You can give a try.

[Former Member · Accepted solution]

Hi

no i dont want any processing to happen only it should send it to the receiving system through http/

In R/3 also we have these services..adapter_plain,sap/xi/engine so they can act as the receiver of data..

[former_member181985 · Accepted solution]

>

> Hi
> 
> no i dont want any processing to happen only it should send it to the receiving system through http/
> In R/3 also we have these services..adapter_plain,sap/xi/engine so they can act as the receiver of data..

That's what you are getting the message saying "message processing not allowed", though the message is being posted to SAP R/3 since there is no configuration or Service which can does some job.

Edited by: Praveen Gujjeti on Apr 21, 2009 5:45 PM

[Former Member · Accepted solution]

No this was a previous error when i was not using the right user. Actually i have written user not authorised for message processing.

Regards

Monika

[Former Member · Accepted solution]

Hi Monika,

interesting scenario of yours but sorry you are making a slight error in its configuration :(........

the HTTP destination of r/3 is okay but the point is to make your scenario work, you will have to use XI reciver adapter and not HTTP receiver adapter because HTTP receiver adapter will send a plain HTTP msg to integration engine of r/3 but R/3 cannot process it as the integration engine expects a msg in SOAP format and not plain HTTP format..........so when you will use XI reciver adapter, then R/3 integration engine will get a SOAP msg and then it will be able to process it...........

Moreover you said later you have to use another XI system instead of target R/3 system, so later also you can use XI adpater for communication between your XI systems..............

Regards,

Rajeev Gupta

[Former Member · Accepted solution]

k,let me give it a try with xi adapter but with the actual target i will have to use http only

[Former Member · Accepted solution]

Hi Rajeev

I have converted to XI Receiver Adpater and also configured sxmb_adm on receiver r/3 by assigning the role as application system and giving the details of PI in Related integration server like: pidev:50000/sap/xi/engine?type=entry.

Now i guess i need to do SLDAPICust and other similar configs as required for proxies..

Regards

Monika

[Former Member · Accepted solution]

Hi Monika,

Yes, now you have to do all the configuration required for proxy communication like SXMB_ADM, SLDAPICUST.....

configured sxmb_adm on receiver r/3 by assigning the role as application system and giving the details of PI in Related integration server like: pidev:50000/sap/xi/engine?type=entry - See here in related IS you have to mention dest://XYZ where XYZ will be a SM59 connection of type H pointing to your XI server by giving your XI hostname and XI HTTP port and path prefix as /sap/xi/engine?type=entry and in specific configuration add entries for category RUNTIME for ENGINE_TYPE as LOC and IS_URL as dest://XYZ

Then in reciver R/3 system by transaction SPROXY you will have to generate the proxy for your receiver inbound msg interface and then implement the method EXECUTE_ASYNCHRONOUS for processing of your msg in reciver R/3 system........

then your msg will be processed in receiver R/3 system.

Regards,

Rajeev Gupta

Edited by: RAJEEV GUPTA on Apr 22, 2009 9:15 AM

[Former Member · Accepted solution]

Hi Rajeev

Yes i am doing that only. But i guess for communicating with PI instead of R/3 i will not have to maintain these settings like SLDAPICust and LCRSAPRFC and SAPSLDAPI RFC destinations or will we have to?

Also in that case i feel plain_http adapter will also suffice?

Regard

Monika

[Former Member · Accepted solution]

Hi,

But i guess for communicating with PI instead of R/3 i will not have to maintain these settings like SLDAPICust and LCRSAPRFC and SAPSLDAPI RFC destinations or will we have to? - For XI - XI communication, these settings are not required because each XI system will have its own settings for these things for their SLDs............

Also in that case i feel plain_http adapter will also suffice? - No, plain HTTP adapter will not be able to send msgs between IS of two XI systems because IS communicate with eachother through XI protocol....

i think your second XI system will not be in your current SLD........so to communicate with it you will need to create a Business Service for your second XI system and configure receiver XI comm channel to communicate with your second XI system........

Regards,

Rajeev Gupta

[Former Member · Accepted solution]

Hi

Thanks for your inputs. The scenario works with both HTTP_PLAIN as well as XI Adapter.

The path with HTTP is /sap/xi/adapter_plain.

The path with XI is /sap/xi/engine?type=entry.

However XI Adapter required all the setting similar to a proxy SLSAPICUST, 2 RFC destions on ECC etc.

For the actual scenario however XI Adapter should be used since no conversion is required between the two IS. However we plan to go with HttPs for the security reasons. Moreover http can be used to send data from one IS to another (partner's IS) as our idea is to just put the data into the pipeline from where it would be picked again for sending out a IDoc to a partner ECC. Since the actual system is available, i would start work on that.Thanks everybody for the inputs, it really helped for this RnD.

Regards

Monika

[Former Member]

Hope ur problem should have been solved by now, if not,

RFC destination, in Logon & Security Tab, which user you have provided? Try to use "PIAPPLUSER",

for the password get it from BASIS team.

[Former Member]

Hi Prabu

that is solved and i get 500 response, empty request received.

But in moni when i trigger the idoc, it gives 500 internal error.

Regards

Monika

[Shabarish_Nair]

>

SAP R/3 (IDoc) - XI- SAP R/3 (Http)

why do you need a HTTP receiver to SAP?

If you are communicating to SAP ideal scenarios are the use of Idocs, RFC or Proxies. Is there any specific reason to use HTTP in your case?

As mentioned in above replies, i suggest the use of Proxy else a similar IDoc in the receiver R3.

ref:

Server Proxy (Receiver Proxy)-

/people/siva.maranani/blog/2005/04/03/abap-server-proxies

[Former Member]

Hi

Now while testing the RFC detsination i get 500 code, Empty http request received.

And in moni i get the error as

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!-- Call Adapter

-->

- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">

<SAP:Category>XIAdapter</SAP:Category>

<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_SERVER</SAP:Code>

<SAP:P1>500</SAP:P1>

<SAP:P2>Internal Server Error</SAP:P2>

<SAP:P3>Error during parsing of SOAP header</SAP:P3>

<SAP:P4 />

<SAP:AdditionalText />

<SAP:Stack>HTTP server code 500 reason Internal Server Error explanation Error during parsing of SOAP header</SAP:Stack>

<SAP:Retry>M</SAP:Retry>

</SAP:Error>

[former_member183908]

Hi

Please check your Receiver service,Receiver Interface.

Thanks

[Former Member]

Hi

Receiver is a service and sender and receiver interface are same with one to one mapping and test configuration is successful.

Regards

Monika

[former_member183908]

Hi Monika

I am not saying about the Interface mapping in the IR.

-->In ID while creating the Receiver Communication Channel we nedd to configure the Receiver Business system(we can use service also) and Receiver Interface and Receiver namespace.

Once pls chekc these details also..

thanks

[prateek]

Instead of using http adatper, use XI adapter using proxy communication.

Regards,

Prateek

[Former Member]

Hi Prateek

I have to use http adapter only. Actually the actual target application is not available at the moment (which is going to be another XI system) and the XI box is new, hence testing with a SAP System to rectify the things on my side.

Regards

Monika

[Former Member]

Hello,

U are creating this on sm59.....just check it can be zsm59...

[Former Member]

Hi

I wonder whether the parameters given by me are correct. In the mean time i am checking for a relevant user as i also get user not unauthorized for message processing.

Regards

Monika

[Former Member]

Hi

Sorry i dint get you.

[prateek]

For connecting to another XI system, you may also use soap adapter by just getting the wsdl from second XI system and importing it and sending soap message using first XI system.

Regards,

Prateek

[prasannakrishna_mynam]

Hello Monika,

While you are giving the path prefix you need to include the query string along with it, the follwing is the syntax of it.

http://<hostname:port>/<path>?<query-string>;

Specify the target host, service number, and path prefix including query string.

Specify the RFC destination as you have done already.

Refer the below link for more details on how to go deal with the query string.

http://help.sap.com/saphelp_nw04/helpdata/en/0d/5ab43b274a960de10000000a114084/frameset.htm

Regards.

Prasanna..

[prasannakrishna_mynam]

Hi,

I would like to add some thing, when you are creating RFC Destination, make sure you have configure your RFC Destination in R/# as below.

Configuration Business system as local Integration Engine.

1. Go to Transaction SXMB_ADM

2. Choose Edit --> Change Global Configuration Data.

3. Select Role of Business System: Application system

4. Corresponding Integration server: dest://RFCDESTINATION

and try to execute the scenario.

Regards..

Prasanna..

[former_member732072]

Hi Monika,

Please have a look at the following link and see if it helps you.

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a8424011-0d01-0010-e19d-e5bd8ca5...

Best regards.