cancel
Showing results for 
Search instead for 
Did you mean: 

connecting directly from ECC 6.0 to a 3rd party system with out XI ?

Former Member
0 Kudos

Hi Guys,

we have developed soap-soap scenarios in XI and we are sending the data from ECC 6.0 -> XI ->3rd party webbased system.

Due to some security reasons we are looking for options of doing the same with out XI ie directly from ECC 6.0 to 3rd party system.

can somebody explain or provide the links for doing the direct connection and also suggest the advantages and disadvantages of eliminating XI completly from the design

any hep would be really appreciated

Thanks,

Srini

Accepted Solutions (1)

Accepted Solutions (1)

VijayKonam
Active Contributor
0 Kudos

You can publish your ABAP proxy code as a webservice in R3 system then can generate the wsdl for it. By giving this WSDL to the 3rd party system you can have them call R3 sys directly. You need to provide them a user ID and password on the R3 system like PIAPPLUSER.

There could be security issues in this case because the customers are hitting R3 directly and might have adverse affects on performance if the load is high. SAP prefers to have XI in between and as a hub for communication with R3 system thus taking all the load and by passing direct hits to R3. This way you would also have flexibility that, you can bundle your messages and have single line of communication even fpr processing multiple requests on R3.

If you try let 3rd party systems hit R3 for any variation of the service, you have to do a new development on R3 where as if XI is in the middle you can just do the variations on the outbound interface side and keep the inbound interfaces as they are thus no change on ABAP side..!!

I would not prefer removing XI from the landscape..!!

VJ

Former Member
0 Kudos

Hi VijayaShankar,

Thanks for the quick reply, we are actually sending the request from the R/3 to 3rd party system. This is synchronus and we expect the reponse coming back to R/3 like Proxy - Soap.

Is it possible to send the asynchronus request from R/3 to 3rdparty system or it has to be to always the synchronus call ?

any help would be really appreciated

Thanks,

Srini

Former Member
0 Kudos

Hi,

You can have synchronous as well as asynchronous requests with R/3 to 3rd party.

Normally RFC as webservice exposed as synchronous call, but you have avoided the response parameters then it can treat as async call.

Thanks

swarup

Former Member
0 Kudos

Hi Swarup,

Thanks for the quick reply and the detailed explanation.

we have enterprise services delivered by SAP which needs to be mapped and converted to the format of the 3rrd party webservice. I think all these can be done in the client proxy and the end point we should give it as 3rd party URL.

I think it is also possible to do the HTTPS call and validate the customers based on the client certificates or user id and password authentication.

1. Using the standard Enterprise services from SAP as the input generate a client proxy report which results in the fomat exactly how the 3rd party system webservice is going to accept.

2. HTTPS connection.

any help or suggestions would be appreciated

Can you explain the things what are the disadvant we will have with out XI.

Thanks,

Srini

Former Member
0 Kudos

HI,

Yes, using standard Enterprise services from SAP you can communicate with 3rd party systems also,

Even you can configure the HTTPS communication with R/3 to 3rd Party system. For this you need to install the client Certificates and have to use valid User ID and Passwords.

http://help.sap.com/saphelp_nw04s/helpdata/en/3a/7cddde33ff05cae10000000a128c20/frameset.htm

http://help.sap.com/saphelp_nw04s/helpdata/en/e8/1f1041a0f6f16fe10000000a1550b0/frameset.htm

Disadvantage of communication without XI

1. XI provides the re-usability concept. i.e. if you have just R/3 to 3rd party and tomorrow you may need to add another 3rd party or sap system to communicate, then you just re-use the existing scenario.

But in case of direct communication is leads to point-to-point connection.

2. R/3 can't directly support to the open Standards, either you have to use ABAP proxies or RFCs to convert it to XML format. But XI is an Centralized Integration Platform with Open Standard. In current world, Openness is important.

3. XI has the Ability to communicate with other messaging systems/products may be JMS or any other 3rd party systems also which has the limitations with direct communication

4. Complex processes for communication possible instead of only sending and receiving (business process management) (connect e.g. asynchronous and synchronous steps, define complex communication scenarios)

Mapping etc possible to accomplish in Java. Platform independent Java components.

5. XI has Java & .Net support. which is not possible with directly R/3

Thanks

Swarup

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi,

Without XI , you can connect ECC directly to 3rd party systems with various ways.

1. Direct RFC call using RFC adapter

2. Expose RFC as webservice and use SOAP adapter

3. Use ABAP proxy to call RFC

Such as using RFC as Webservice and communicate directly with third party systems

Using RFC as WebService in WebDynpro

Expose the RFC as a service directly from the R/3(or other SAP app system), you need at least WebAS 6.20 or above. The RFC should be Remote-enabled in the Attributes. Then you can get the WSDL for it by accessing the following link corresponding to your R/3/SAP app host:

http://<hostname>:<port_number>/sap/bc/bsp/sap/WebServiceBrowser/search.html?sap-client=<relevant_cl...;

Be sure to include the client and use a fully-qualified hostname.

With this option, assuming a web service client, you should be able to call the RFC as a web service directly or via XI (sender/receiver SOAP adapter). You can still use the receiver RFC adapter, of course, but then you wouldn't be asking for the WSDL.

2. If the RFC is developed on a SAP basis 46D system or below, it cannot directly be called as a web service from a web service client. XI has to "front" as the web service for the RFC. In this case, it would be a a SOAP->XI->RFC scenario only.

Thanks

Swarup