on 04-24-2008 1:20 PM
hi sap-xi experts,
i am preparing for xi interview can explain the overall architecture
of xi and how the
message is transfer through it digramtically.
Hi Vijaya
These blogs will help you prepare for ur interview
xi architecture interview questions
XI Architecture questions will be totaly based on the components of xi. u may refer to this doc and have it cleared:
XI/PI FAQ (Frequently Asked Questions)
/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
See also
/people/sap.user72/blog/2005/11/22/xi-faqs-provided-by-sap-updated - XI : FAQ's Provided by SAP
856346 J2EE JMS Adapter: Frequently Asked Questions (FAQ)
615740 CCMS GRMG Availability Monitoring: FAQ
36677 Structure of components for customer messages
To see your message flow , pls follow this link..
/people/siva.maranani/blog/2005/05/25/understanding-message-flow-in-xi
Thnx
Saiyog
(reward points if usefull)
Edited by: Saiyog Gonsalves on Apr 24, 2008 3:26 PM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Vijaya,
Go through this..
http://help.sap.com/saphelp_nw04/helpdata/en/0f/80243b4a66ae0ce10000000a11402f/content.htm
Thanks,
satya Kumar
Reward if it is useful..
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Vijaya,
SAP Exchange Infrastructure
Purpose
SAP Exchange Infrastructure (SAP XI) enables you to implement cross-system processes. It enables you to connect systems from different vendors (non-SAP and SAP) in different versions and implemented in different programming languages (Java, ABAP, and so on) to each other. SAP Exchange Infrastructure is based on an open architecture, uses open standards (in particular those from the XML and Java environments) and offers those services that are essential in a heterogeneous and complex system landscape:
● Modeling and design of messages, transformations, and cross-component integration processes
● Configuration options for managing collaborative processes and message flow
● Runtime for message and process management
● Adapter Engine for integrating heterogeneous system components
● Central monitoring for monitoring message flow and processes
SAP XI supports internal company scenarios and cross-company scenarios.
In this documentation, a collaborative process is a process in the business world that requires cross-system implementation. Note that this term does not describe any concrete objects of this implementation.
Integration
The following graphic is a simple overview showing how SAP XI is positioned within SAP NetWeaver. The important components and concepts of SAP XI are shown on the right-hand side. These are described in more detail in the overview section.
XI Components Within SAP NetWeaver
Features
SAP XI is based on general standards so as to enable external systems to be integrated. At the center of the infrastructure is an XML-based communication that uses HTTP (Hyper Text Transfer Protocol). The application-specific contents are transferred in messages in user-defined XML (eXtensible Markup Language) schema from the sender to the receiver using the Integration Server.
In the above graphic, Integration Broker is an SAP NetWeaver capability (that is, the features for a technological area of SAP NetWeaver) that is supported by SAP XI. The Integration Server, on the other hand, is an XI runtime component.
Senders and receivers that exchange messages using the Integration Server are separated from one another. This separation makes it easier to connect systems that are technologically different. Every system that can exchange messages with the Integration Server can also exchange messages with all other systems that are connected to the Integration Server. SAP XI supports the following methods of communication with the Integration Server:
● Direct communication using proxies, which you generate in the application systems using a description in WSDL (Web Service Description Language).
● Communication using adapters. In this case, you create interfaces for message exchange in the application system, or use existing interfaces.
Simple message processing on the Integration Server is stateless. This means that the Integration Server does not know of any connections between various messages. Cross-component integration processes, on the other hand, describe related processes, which can use the knowledge about messages that have already been processed to further control the process (for example, waiting for the corresponding response for a message in order to start further actions). You can use SAP XI to model, change, and manage these cross-component integration processes centrally. These processes are executed on the Integration Server and are included in message processing by configuration.
As with cross-component integration processes, you save the entire integration knowledge of a collaborative process centrally in SAP XI: Objects at design time in the Integration Repository and objects at configuration time in the Integration Directory. In this way, SAP Exchange Infrastructure follows the principle of shared collaboration knowledge: You no longer need to search for information about a collaborative process in each of the systems involved, but can call this information centrally instead. This procedure considerably reduces the costs for the development and maintenance of the shared applications.
Areas of SAP XI in Detail
Area
Description
Integration Builder
Central tool for the design and configuration of the collaborative process. All the basic functions of the Integration Builder are described in this section. All subareas for design and configuration, and their editors (often graphical) in the Integration Builder, are documented in the subsections for Design and Configuration (see below).
Software Logistics for XI Objects
Organization of objects within SAP XI, versioning and transport of these objects.
Design (Integration Repository)
Designing Integration Scenarios
Design of the collaborative process at the application component level. In the Integration Builder, integration scenarios are used as the central point for understanding the relationships between the objects involved (interfaces, mappings, integration processes). You also use design at configuration time to map the collaborative process to the current system landscape.
Designing Integration Processes (ccBPM)
Design of executable integration processes. Cross-component integration processes support a stateful message processing on the Integration Server.
Designing Interfaces and Proxy Generation
Description and use of messages in interfaces for message exchange. You create interfaces in the Integration Builder and use proxy generation to generate executable proxies in SAP application systems. Furthermore, you can use the Integration Builder to import message schema and SAP interfaces to the Integration Repository for use in the further design process.
Designing Mappings
Design of graphical message mappings and import of Java and XSLT mappings. Description of how to register these mapping programs for the source and target interface.
Configuration (Integration Directory)
Defining Collaboration Profiles
Description of the technical sender and receiver options (and how to identify them) using communication parties, services, and communication channels.
Defining Receiver Determinations
Description at a logical level of which service a message is to be sent to. The service can be a business system, an integration process, or a service for a B2B communication.
Defining Interface Determinations
Assignment of a receiver interface to a sender interface. You also register whether mapping programs are to be executed from the Integration Repository for this interface pair, and if so, which mapping programs.
Defining Collaboration Agreements
In a collaboration agreement you define which communication channel to use to process messages for a particular combination of senders and receivers.
Defining Configuration Scenarios
Grouping of all configuration objects by the scenario in which they are required. You can apply integration scenarios from the Integration Repository for a configuration scenario in the Integration Directory.
Runtime
Integration Engine
Central runtime component of the Integration Server for receiving, processing, and forwarding messages.
Proxy Runtime
Runtime component for proxy communication between the Integration Server and application systems based on SAP Web AS.
Adapter Engine
Runtime components that use adapters to connect external systems and R/3 systems to the Integration Server by means of RFC calls. The IDoc adapter and the plain HTTP adapter run independently of the Adapter Engine.
Central Monitoring
Functions for monitoring the involved XI components, the message processing by one or more components, and the performance of message processing.
Additional Tools (Optional)
Tool
Use
ARIS for SAP NetWeaver
Add functions to SAP NetWeaver for graphically modeling processes at various levels. At the highest level (Process Architecture Model), the process architecture of a company is built from a purely business perspective, that is, without technical details.
You can find ARIS for SAP NetWeaver in the SAP Software Distribution Center on SAP Service Marketplace at service.sap.com/swdc.
SAP Conversion Agent by Itemfield
Adds functions to SAP NetWeaver for converting data to and from XML. It can process unstructured, semi-structured, and structured data. The Conversion Agent can be called using an adapter module in the Adapter Framework of SAP Exchange Infrastructure.
You can find SAP Conversion Agent by Itemfield in the SAP Software Distribution Center on SAP Service Marketplace at service.sap.com/swdc.
Thanks,
Satya Kumar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
SAP-XI architecture involves in details in different stages
Design time and Configuration time and Message processing time.
Please find the follwing link
http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm.
Thanks,
RamuV
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
overall architecture:
http://help.sap.com/saphelp_nw04/helpdata/en/0f/80243b4a66ae0ce10000000a11402f/frameset.htm
message flow in xi:
/people/siva.maranani/blog/2005/05/25/understanding-message-flow-in-xi
Regards
Patrick
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
25 | |
12 | |
9 | |
6 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.