You should go to sap sdn. They have loads of information about Xi
https://www.sdn.sap.com/irj/sdn/developerareas/xi?rid=/library/uuid/2205b790-0201-0010-0586-87e7cdc28ceb
Process Integration
The traditional approach towards process integration takes two systems and puts a connection in-between those systems. By doing so companies create IT environments that are integrated at a high price; the complexity of all the 1:1 connections and the costs of setting them up and maintaining them increases rapidly. With the SAP® Exchange Infrastructure each system is connected to a central hub. This Integration Server (hub) allows for new features like central routing, mapping, monitoring and process management.
Over the past ten years, lots of technical solutions have been introduced by various vendors to achieve some relief. Therein lies the problem: application integration is not merely a technical problem, it also has to be addressed from a business process perspective. The need for a common, cohesive, and standards-based infrastructure is obvious. SAP provides this with the SAP Exchange Infrastructure.
Integration Broker
SAP Exchange Infrastructure (SAP XI) is SAP's platform for process integration based on the exchange of XML messages.
SAP Exchange Infrastructure:
*
Provides a technical infrastructure for XML-based message exchange in order to connect SAP components with each other, as well as with non-SAP components.
*
Delivers business- process and integration knowledge to the customer, in the form of SAP's predefined business scenarios.
*
Provides an integrated toolset for building new business scenarios by defining and maintaining all integration-relevant information (shared collaboration knowledge).
SAP Exchange Infrastructure is based on the following principles:
*
Data is exchanged between application systems in the form of XML messages. XML provides a whole new set of standards and technical building blocks that provide a huge step forward in terms of interoperability.
*
Only one integration infrastructure is needed for application-to-application integration (be it SAP or non-SAP) - it is the same one that reaches out to business partners, and is the foundation of private exchanges as well as public marketplaces.
*
The information stored as shared collaboration knowledge is based on XML and open standards (XPath and Java for routing, XSLT and Java for mapping, WSDL for Web services). This makes it easy to share information with customers and partners. It also fosters the ability to provide and reuse this knowledge for partners and customers and for third-party and legacy systems, taking it well beyond pure SAP-to-SAP integration.
*
Although collaboration knowledge will be centralized, the infrastructure will support central and distributed execution. For efficient integration management and administration, it is key that relevant information on integration (collaboration knowledge) is visible in a central place.
*
The SAP Exchange Infrastructure will deliver content on SAP-to-SAP integration, plus the potential for out-of-the-box integration of SAP components with other systems.
Check also the SAP help portal:
http://help.sap.com/saphelp_nw2004s/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm
Component documentation SAP NetWeaver Exchange Infrastructure Locate the document in its SAP Library structure
Purpose
Exchange Infrastructure in SAP NetWeaver (SAP NetWeaver 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 NetWeaver XI supports internal company scenarios and cross-company scenarios.
Note
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
Overview section.
2006-08-31 20:42:39
·
answer #1
·
answered by roy_s_jones 6
·
0⤊
0⤋
you should use the advice elements window in seen Studio to create an information source that contains the relationship string and also you'll use that similar window to substantiate that it extremely works. The C# nook internet website has many functional and relevnat articles; my article "Database table replace in a DataGridView with out Writing Code" i wish is a delightful, usefull creation. also be conscious that an issue-free reason behind the region you're encountering is that typically the sq. Server server isn't all started. flow to the sq. Server Configuration manager to envision it and also you'll commence it from there if mandatory.
2016-12-06 02:09:14
·
answer #2
·
answered by Anonymous
·
0⤊
0⤋