Basic Dought.. In Integration Repository

Question

Hi All,
Any body Explain me the below topics
<b>Integration Scenario & Integration Process</b>
      -  Integration Scenarios,
      -  Action,
      -  Integration Processes,
<b>Interface object</b>
1.      message Interfaces
2.      message type
3.      fault message types
4.      data types
-     exchangefaultdata
-     exchangeLogData
5.      Datatype Enhancements
6.      Context Objects
7.      External Definitions
<b>Mapping Objects</b>
-     Interface Mapping
-     Message Mapping
-     Mapping Templates
-     Imported Archives
<b>Adapter Objects</b>-     Adapter Metadata
-     Communication Channel Template
This information very use full to me
Thanks & Regards

Answer 1

Hi,
I have taken some time off for you and have given the best possible explanation for the doubts you have.
<b>Integration Scenarios:</b>
An integration scenario completely models the exchange of
messages for a collaborative process and provides an overview of the process flow.
Please go through this link for further reference:
http://help.sap.com/saphelp_nw04/helpdata/en/ec/21ee117a909f44a8b69794b9ed6221/frameset.htm
<b>Integration Processes</b>
An integration process is an executable, cross-system process for processing messages. In an integration process you define all the process steps that are to be executed and the parameters relevant for controlling the process.
You implement integration processes when you want to define, control, and monitor complex integration processes that extend across enterprise and application boundaries. The design and processing of integration processes is also known as cross-component Business Process Management (cross-component BPM, ccBPM).
Please go through this link for further reference:
http://help.sap.com/saphelp_nw04/helpdata/en/3c/831620a4f1044dba38b370f77835cc/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/f7/d4653fd1d3b81ae10000000a114084/frameset.htm
<b>
<u>Interface object</u></b>
<b>1. message Interfaces</b>
ou use a message interface to describe a platform-independent or programming-language-independent interface, which you want to use to exchange messages between application components using SAP Exchange Infrastructure.
Please go through this link for further reference:
http://help.sap.com/saphelp_nw04/helpdata/en/55/c5633c3a892251e10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/06/1522417c22f323e10000000a155106/frameset.htm
<b>
2. message type</b>
A message type comprises a data type that describes the structure of a message. At the following points in SAP Exchange Infrastructure you can refer to the message to be exchanged at runtime by using the message type
Please go through this link for further reference:
http://help.sap.com/saphelp_nw04/helpdata/en/2d/c0633c3a892251e10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/e7/7356405aff1e24e10000000a1550b0/frameset.htm
<b>
3. fault message types</b>
Fault message types are designed for application-specific errors that occur on the inbound side and that are reported back to the sender or persisted in monitoring.
Please go through this link for further reference:
http://help.sap.com/saphelp_nw04/helpdata/en/dd/b7623c6369f454e10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/5d/a45c3cff8ca92be10000000a114084/frameset.htm
<b>4. data types</b>
A data type is a basic unit for defining the structure of the data for a message type and, as a result, for the message to be exchanged.
Please go through this link for further reference:
http://help.sap.com/saphelp_nw04/helpdata/en/a5/04623c4f69b712e10000000a114084/frameset.htm
exchangefaultdata and exchangeLogData
All fault message types reference the data type ExchangeFaultData for this part and, indirectly, the data type ExchangeLogData. These data types are automatically created in a namespace when you create the first fault message type there.
<b>
5. Datatype Enhancements</b>
SAP applications enable customers to enhance application source code without making modifications and thus to meet customer-specific requirements that are not provided for in the standard shipment.  The applications can use Business Add-Ins (BAdIs) for this purpose. Furthermore, if customers use applications that exchange messages by using XI, they can define data type enhancements for Integration Repository data types.
Please go through this link for further reference:
http://help.sap.com/saphelp_nw04/helpdata/en/a8/bfc6373c8fea43bdb3541535bcbd43/frameset.htm
<b>6. Context Objects</b>
Context objects are a simple alternative to XPath expressions for accessing the contents of a message.
Please go through this link for further reference:
http://help.sap.com/saphelp_nw04/helpdata/en/d6/e44fcf98baa24a9686a7643a33f26f/frameset.htm
<b>
7. External Definitions</b>
External definitions enable you to import WSDL, XSD, and DTD documents to the Integration Repository so that you can access the message definitions they contain as external messages.
Please go through this link for further reference:
http://help.sap.com/saphelp_nw04/helpdata/en/43/ce49ef1019087ae10000000a1553f6/frameset.htm
<b><u>Mapping Objects</u>
</b>
<b>Interface Mapping</b>
Interface mappings register your mapping program for an interface pair in the Integration Repository.
Please go through this link for further reference:
http://help.sap.com/saphelp_nw04/helpdata/en/4f/ef761a5ecfb1418b79896e10fe4c57/frameset.htm
<b>
Message Mapping</b>
Please go through this link for further reference:
http://help.sap.com/saphelp_nw04/helpdata/en/d9/cea942ad920c31e10000000a1550b0/frameset.htm
<b>
Mapping Templates</b>
Just like you can reuse data types in different message types, you can also save parts of message mappings as Mapping Templates and reuse them elsewhere. Once you have saved a mapping template it serves as a copy template that you can then load into other message mappings and modify to fit your requirements.
Please go through this link for further reference:
http://help.sap.com/saphelp_nw04/helpdata/en/79/2835b7848c458bb42cf8de0bcc1ace/frameset.htm
<b><u>Adapter Objects</u></b>
<b>Adapter Metadata</b>
With adapter metadata you can define configuration data needed for a certain type of adapter at design time. Adapter metadata define the part of a communication channel that is specific to the adapter type.
Please go through this link for further reference:
http://help.sap.com/saphelp_nw04/helpdata/en/12/f9bb2fe604a94cbcb4c50dc510b799/frameset.htm
<b>Communication Channel Template</b>
You can preconfigure a communication channel with a communication channel template. You can use the communication channel template as a template to define a communication channel at configuration time.
Please go through this link for further reference:
http://help.sap.com/saphelp_nw04/helpdata/en/bd/6af766076e384ebdce621d25161184/frameset.htm
I am sure i have clearly explained your doubts.
Regards,
Abhy
PS: AWARD POINTS FOR HELPFUL ANSWERS.