Configuration Objects (ID Objects) Question

Question

I am trying to understand each ID object better way,
What is the definition of each objects,
What the use of each objects......
Configuration scenario examples using each object.
1. Party
2. Service Without Party
            a. Business System
                1. Communication Channel
            b. Business Service
            c. Integration Process
3. Receiver Determination
4. Interface Determination
5. Sender Agreement
6. Receiver Agreement

Answer 1

Ash:
for a better understanding below i have maade a kinda comparision...hope this shud help you.
<b>1. Party and 2. Service Without Party</b>
Service without Party :
This has to be configured when we are doing A2A integration ie integration with in the same landscape ie in the same corporate boundary.
Party:
This has to be configured when we are doing B2B integration ie outside the corporate boundary...The use of party is mainly for B2B communication, such as Rosettanet. The definition of a party actually identifies the partner system
<b>a. Business System &1. Communication Channel & b. Business Service</b>
Business system is a logical system, and there is an importance on physical existence of the system.Also SLD entry is required.
It is generally used for SAP applications, this is just a general prinicple followed but not mandatory.
You use a Business Service, when you do not have the System details of the the partner system to which you want to communicate. i.e. you have not configured the partner system in SLD. Business Service is an Absract Unit with Sender and Receiver Interfaces,In this case you need to explicitly add the message interfaces while doing configuration in ID. It is generally used for NON-SAP applications, this is just a general prinicple followed but not mandatory
communication channel is the physical connection for adapters to communicate to the systems (within or outside your landscape)
<b>c. Integration Process</b>
Integration Process is a sequence of steps to attain a business process sequence. It gets executed in Business process engine. The Repository, directory etc are not part of Integration Process.They help in creation and execution of the integration process.
<b>3. Receiver Determination and  4. Interface Determination</b>
In receiver determination we never specify interface mapping. We specify interface mapping only in interface determination. Receiver Determination helps to specify which receivers a message is to be sent to. Interface determination helps you to specify which interface a message is to be sent to.
A receiver can have more than one interface, that is why you have to do interface determination. The split between Receiver Determination and Interfacedetermiantion is so that you can add send the same message to Multiple Receivers and then fior each of the receivers , if needed you can add multiple Inbound Interafces / mappings
<b>5. Sender Agreement and 6. Receiver Agreement</b>
Sender agreement binds the sender interface with the communication channel. In a sender agreement, you define how the message of a sender is to be transformed so that it can be processed by the Integration Engine .
When you create a sender agreement, you must specify at least the sender interface and the party or service for the sender and receiver. You can use a wildcard character (*) for the receiver party, receiver service, and the sender interface . One sender agreement can be associated in only one RECEIVER DETERMINATION
If u have any queries keep us posted