XI - Jump starting

[former_member457420]

Hi guys,

Iam new to XI and while going through all the books & courses,I have some questions in my head which needs to be cleared.

Its quite a few questions.Would appreciate if some one has the patience to go through it all

[1]

How is the plain Http adapter works.I Know that it uses the ICF technology of web AS.what does that mean?.

When I searched in the internet ,people say that it is used for direct communication with the integration server.But it is going through the adapter.Then how can it be called a direct communication.

SAP xI integration knows only the xi-xml language.

Does the sender and reciever http adapter make these conversions to & from the pipleline.

[2]

Is all the functionatlies in sap,web service enabled(Ie from ABAP & java side).If yes,from which version?

If not.Is it possible to make a function, webservice enabled from the perspective of the XI.

[3]

I know that a proxy(client) could be generated from a WSDL file.

Is SAP net weaver system needed(ie: with a local integration server) for creating a proxy & communicationg directly with the XI integration server.

Have also seen that they communicate over http->ICM(Internet communication manager) ->and then to the integration server of XI.

[4]

What is the difference between XI and PI.Is it a marketing trick or is there really a difference.

[5]

If a business system is not part of SLD.Should a business service be created under "party" in the Integration Directory.

Iam not sure how to configure a workflow under XI.That brings to my next question.

[6]

I guess my basics would be clear after the above questions are answered:).

But still Iam not familiar with the XI gui for Designing,configuring things in the integration repository,Integration directory and all.

Would be of great help if there is any document which explains a communication between 2 systems with some adapters,with respect to the XI gui.

Thanks in advance

Pazzuzu

[Former Member · Accepted solution]

Hi Pazzuzu,

Also do some reading up on SAP Web AS Architecture & the different implementation possibilities. You're confusing adapter engine with integration engine. You can have a dual-stack implementation as the Central Integration Engine (i.e. Abap & Java stacks & the 2 stacks can communicate with each other). RFC, IDoc and HTTP are resident on the Abap stack and other adapters are resident on the Java stack. All still on the central integration engine.

Following Link's might be a start: [http://help.sap.com/saphelp_nw2004s/helpdata/en/84/54953fc405330ee10000000a114084/frameset.htm]

[http://help.sap.com/saphelp_nw04/helpdata/en/53/fe48b44c5e4bcab5c71fdcf3ee9bc7/frameset.htm]

Regards, Trevor

[former_member457420]

Thank you Guys...

[former_member457420]

So does that mean that idoc,http,RFC and proxy calls can directly call the integration engine.

In the sap Help they say, RFC and Idoc adapter reside inside the integration engine.(In central adapter engine)

all others are on the J2ee side.(Non-Cental adapter engine)

What is the truth here?

what about java proxies then?How is the direct communication achieved in this case.

[Former Member]

Hi,

In the sap Help they say, RFC and Idoc adapter reside inside the integration engine

Please refer the SAP help again, IDOC, HTTP & XI adapters are reside on ABAP stack and remaining all adapters are on Java Stack. The adapters reside on ABAP not require sender side Adapter and sender agreements.

But for all adapters on Java stack you need to go for adapters.

In case of Java Proxy, you can use XI adapter to send the XMl payload.

Please refer the SAP help carfully, that will help you to calrify the confusion, if any.

Thanks

Swarup

[Former Member]

Hi Pazzuzu,

It like the previous guy said, it's called direct communication because HTTP, Proxy & RFC protocols reside on the Abap Stack of the SAP Web AS. You can send a message straight to the Integration Sever just using a URL.

Use link: http://wiki.sdn.sap.com/wiki/display/XI/Home

In the Tools & Accelerators section, you have some PI/XI Clients to test this theory.

Use the following URL to answer your second question: (The answer is yes, a SAP WEB AS is needed with a local Integration Engine to generate the Proxies)

http://help.sap.com/saphelp_nw04/helpdata/en/ab/585f3c482a7331e10000000a114084/frameset.htm

Regards, Trevor

[former_member457420]

Guys,

I have read sravya's blogs.I have quite a good understanding of how XI works.

The questions I posted are concrete questions from my side

P

[Former Member]

Proxies are interfaces that are generated in application systems to communicate with the Integration Server

SAP systems based on Web AS 6.40 and higher are able to exchange data by using messages and HTTP. These systems can use ABAP proxies to connect to the Integration Server.

for more details refer

http://help.sap.com/saphelp_nw70/helpdata/en/86/58cd3b11571962e10000000a11402f/content.htm

[balaji_pichaimuthu]

Hii,

I belive if u check the following blogs if u will get good knowledge on XI.

Check out this Sravya's blogs

http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3417700)ID0540762450DB11741333447609119856End...

http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3417700)ID0540762450DB11741333447609119856End...

http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3417700)ID0540762450DB11741333447609119856End...

Michal' blog

http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3417700)ID0540762450DB11741333447609119856End...

Regards,

Balaji

[Former Member]

Hi,

you can search below line in sdn forum. you will get the idea about xi, it is very nice blog with three parts

Aspirant to learn SAP XI...You won the Jackpot if you read this!-Part I

Thanks

Laxmi Bhushan

[Former Member]

Hi,

[1]------> SAP Help "The Internet Communication Framework enables you to use standard protocols (HTTP, HTTPS, and SMTP) to operate communications between systems through the Internet."

Refer http://help.sap.com/saphelp_nw04/helpdata/EN/36/020d3a0154b909e10000000a114084/content.htm

SAP XI message data works on XML payload, and HTTP adapter is used. HTTP adapter is used to send the Paylod in the HTTP Post. It uses native HTTP interface for communciation i.e. avoiding the SOAP envelope.

[2]-----> No, not alll functionalities in SAP are web service enabled. But you may use RFC to expose as web service with the help of ABAP proxies. This is possible from WAS 6.4 and ahaead...

Refer

Exposing webservice through R3.

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/80fa3dff-ce76-2a10-3f94-f3df8f2d...

Exposing BAPI as Web Services through SAP XI

/people/community.user/blog/2006/10/24/exposing-bapi-as-web-services-through-sap-xi

refer this link to know how to create and expose BAPI as a web service:

/people/sridhar.k2/blog/2006/09/12/creating-and-exposing-bapi-as-web-service-and-using-it-in-web-dynpro

[3]----

---

> In XI you define the proxy strcuture, but the related classes/methods are generated in SAP system having WAS 6.4 or more.. Proxies are used to connect to the other systems when the kernel of WEB AS is > 6.40 Proxy communication starts with objects in integration repository and adapter communication starts with application system. Here you need to wirte the Business logice explicitly.

[4]----> You will get this answer on SDN...so many forums about the same discussion

[5]----

---

> Nope....this is wrong meaning ...about usage of Business system. Business Service and use of Party.

If you need to link with external systems and restrict those applications to access the SLD data, you should create Business service. Generally for SAP systems preferred to use Business systems as it may access the same landscape.

For A2A scenario you should go for service without party and for B2B scenario Party will be used.

[6]----

---

> You should refer the SAP Pi architecture to understand the scope of Integration Builder (repository/config.) and usage of ABAP stack.

Refer - SAP Exchange Infrastructure Architecture and Operational Aspects

http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/50fc0e7e-bd11-2a10-85a0-966fb8ec21cc

Thanks

Swarup

Edited by: Swarup Sawant on Sep 23, 2009 10:07 AM

[former_member457420]

Hi swarup,

Thanks a lot.Would be nice if could provide some claricications regarding the points below

>>When I searched in the internet ,people say that it is used for direct communication with the integration server.But it is going >>through the adapter.Then how can it be called a direct communication.

So is the above statement true.

>>know that a proxy(client) could be generated from a WSDL file.

>>Is SAP net weaver system needed(ie: with a local integration server) for creating a proxy & communicationg directly with the >>XI integration server.

>>Have also seen that they communicate over http->ICM(Internet communication manager) ->and then to the integration server >>of XI.

Are the things true which I stated above.

Thanks

P

Edited by: pazzuzu on Sep 23, 2009 11:06 AM

[Former Member]

Hi,

When I searched in the internet ,people say that it is used for direct communication with the integration server.But it is going >>through the adapter.Then how can it be called a direct communication.

This concept interpret that the XML payload can be directly processed to Integration engine. Basically the use of adapters is to convert the messages in XML payload and pass to integration engine.

But in case of HTTP, IDOC, Proxy adapters which are based on ABAP stack; can send the XML payload directly to Integration engine. you may use the Integration engine end-point url in these cases.

(http://<server>:<port>/sap/xi/engine?type=entry)

But you need to use the receiver HTTP adapter as here you need to give Receiver HTTP destination or Receiver Url.

know that a proxy(client) could be generated from a WSDL file.
Is SAP net weaver system needed(ie: with a local integration server) for creating a proxy & communicationg directly with the >>XI integration server.
Have also seen that they communicate over http->ICM(Internet communication manager) ->and then to the integration server >>of XI.

--> As mentioned in above calrification, Proxy i.e. XI adapter is on ABAP stack, and the message format is by default XML, thus you may directly process these payloads to Intergration engine. no need of any XML conversions.

Refer the detail information provided in forum

Thanks

Swarup