Why we r not Creating Sender Agreement For HTTP & IDOc Adapter at Sender .

[Former Member]

Hi Buddy's,

Why we r not Creating Sender Agreement For HTTP & IDOc Adapter at Sender .And why we create receiver agreements at receiver side bt not sender agreement at sender side.

Wat Is GLOBAL Container ?, where it will Occur & wat is the functionality of that.

[Former Member]

Hi

IDoc Adapter resides on ABAP stack and hence can communicate directly with Integration Server, for the conversion from IDoc to IDoc XML.Communication Channel is used for communication with the Integration Server which is obtained directly in case of IDoc .Hence Sender idoc adapter is not required and therefore no Sender Agreement.

Adapter resides on the ABAP stack ie on the Integration Engine. This makes them both part of the IS pipeline and the processing is done automatically.So Integration engine takes care of the conversion format from IDOC to XML, hence there is no need for sender Adapter .Also since its residing on Integration server you can directly post the message in the Integration engine.

Thanks

[Former Member]

Hi,

An adapter engine is required to get the message from the source and send it to IE. You need a sender agreement to set off these adapters.

HTTP and IDOC are NOT part of AE, they are part of IE. so a http message (for eg:sent from a http client with the mandatory agruments) can reach the IE directly. thats why you dont need a sender agreement for these adapters.

Regards,

Balaji.M

[Former Member]

Kumar,

1) XI integrattion server - IS expects the messages in XML format. If you see the HTTP request you will see that we pass all the info contained in the Sender areement in the the HTTP request itself , namely - Message interface, message type and the namespace (along with login parameters). For IDOCs the the IDOC- XML are are sent to the IS (through IDOC port configuration at the source system.

2) When send a message to XI the sender knows that XI system parameters, but when at the reciver end there could be any any system that is reciving the IDOc/HTTTp message. you specify those message through a commumication channel and this channel is associated to a receiver agreement.

3) A Global container is like a place holder for variables. You can set a variable here and access it throughout your mapping and hence the name.

A good example for a gloabal container is a counter to countthe number of records in te target side.

Regards,

Arvind ravindran

[agasthuri_doss]

Hi,

Global Container helps to cache the values that you want to read again when you next call any user-defined function in the same message mapping.

/people/michal.krawczyk2/blog/2005/03/04/globalcontainer--in-graphical-mapping-xi

http://help.sap.com/saphelp_nw04/helpdata/en/e0/7d8e40496f6f1de10000000a1550b0/frameset.htm

Regards

Agasthuri Doss

[agasthuri_doss]

Hi,

IDOC & HTTP are in ABAP stach..They contact Integration Engine directly..Hence no Sender Agreement

Regards

Agasthuri Doss