Welcome to XI / PI world, but learning XI basic is too broad in the forum thread, the links Swarup posted include some articles for beginners, you should go over some of documents like that.
If you have particular questions, you can search on the forum to see if there is any similar questions answered before, otherwise, you can open a thread to get answers from other XIers and PIers, make sure you make your question specific.
As Liang had said..the basic information is available in all the above links..and you need to take some efforts to search in it...
I have added some of the information that might be helpful for you.
Below given the best possible explanation for all the basic components from development peceptive related to XI.
SAP NetWeaver is gaining traction in the marketplace as customers realize what a powerful application and integration platform it offers. This has resulted in tremendous interest in the Process Integration layer of the NetWeaver stack, implemented by the SAP Exchange Infrastructure, also known as SAP XI.
A good place to start is to consider the integration landscape that exists in most data centers today. Interfaces that connect different systems are generally peer-to-peer, custom-coded, and expensive to maintain. Furthermore, if one were to ask, "where is the information about a particular interface to be found," the answer would be generally hazy at best: it would be a few lines of comment at the front of a custom program, some document in some dusty binder on some forgotten shelf, or somewhere in the mind of the developer.
The XI straightens out the integration landscape using interface-based, SOAP-XML messaging. It offers transparency into the integration landscape via central repositories of shared collaboration knowledge. It provides unified message handling for both A2A and B2B scenarios. The XI allows SAP applications to communicate natively in the XI message format via proxies. It incorporates adapters for communication with RFC, IDOC, and non-SAP systems (which may be, for example, flat files, JMS queues, plain HTTP, applications from other vendors, or industry standards). It defines all integration objects using web standards such as WSDL, XSD, BPEL4WS, etc. And it is built on the robust, scalable, reliable, and powerful architecture of the SAP Web Application Server.
Here the SLD configuration for technical and business systems...monitoring tools ets also invlove..
Integration Scenarios:
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:
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:
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:
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:
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:
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.
5. Datatype Enhancements
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:
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:
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:
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:
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:
Swarup has already answered ehe quetions for you, I just add a few pionts particular to your questions:
Integration Build is the tool used for the development. It includes integration repository and integration directory.
Integration repository is for design time (check Swarup's answer), from PI 7.1, the name changed to ERS (Enterprise Service Repository )
Integraion directory is used for configuratin time, it answer question like who is the receiver, what interface is used for receiving messages, which commnication channel is used for sender and receiver etc...
Runtime Workbench is used for runtime monitoring purpose:
it can be used for components monitoring, Message Monitoring, End to End monitoring, performance monitoring etc...
System Landscape Directory (SLD) is data center to store information needed for design time, configuration time and runtime.
Adapter Engine is based on Adapter framework, it used to connect different systems, it can be central, local.
Integration server is run time components, it include Integration engine, business process engine and adapter engine.
Integation engine to process messages, mostly for 1:1 mappings or 1:N mapping
Business Process Engine can have m:n mapping
The reason to use XI as middleware, mostly the company has already have other SAP system in their infrastructure,
Xi can provide better integration to SAP Systems (RFC, IDOC and ABAP proxies), the other reason is that XI has provided Pre delivered content.
Compare with other middle ware:
Check this weblog for some differences between XI and Web Methods:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.