We accept

Dot Online Sap Integration With Exchange Infrastructure Computer Research Essay

The SAP Connectors allow the integration of different applications which consists of technology with SAP Systems using the requirements. The connectors are opportinity for complex interoperability of SAP Components (written in ABAP or ABAP Objects) and other components (e. g. written in Java, C++, Aesthetic Basic, . NET, etc. ). You will discover many types of SAP Connectors such as SAP. NET Connection, SAP JAVA Connector, SAP DCOM Connector, SAP BUSINESS Connector. SAP Exchange Infrastructure is middleware which may be used by various applications and solutions to incorporate with SAP using an available protocol and standards.

SAP Exchange Infrastructure (SAP XI) is SAP's venture application integration (EAI) software, a component of the web Weaver product group used to help in the exchange of information among a company's interior software and systems and those of external parties. Like other World wide web Weaver components, SAP XI is compatible with software products of other companies.

SAP message or calls XI an integration broker since it mediates between entities with differing requirements in terms of connectivity, format, and protocols. Relating to SAP, XI reduces integration costs by giving a common repository for interfaces. The central element of SAP XI is the SAP Integration Server, which facilitates conversation between diverse os's and applications across interior and external networked computer systems.

Exchange Infrastructure

SAP Xi- Architecture

XI is well suited for joining SAP systems with one another and with non-SAP. When the focus is not on SAP systems, other alternatives might be an improved choice today. SAP XI provides an integrated workflow engine motor which allows to identify adapters to non-XML-protocols and mappings to convert data content from source to focus on.

Central XI monitoring supplies the following options:

Component monitoring

Message monitoring

Performance monitoring

Alert configuration

Cache monitoring

Business Process Management

A business process can be an executable, cross-system process. Inside a business process we can establish all the procedure steps that are to be carried out and the parameters relevant for managing the process.

Implement cross-component Business Process Management (BPM) when necessary to explain, control, and monitor complex business procedures that lengthen across organization and application limitations.

Integration Engine

The Integration Engine is the runtime environment of the SAP Exchange Infrastructure.

It allows to process XML emails exchanged between applications in heterogeneous system scenery. Both applications of SAP components and exterior applications can communicate with the Integration Engine motor.

Using adapters, the Integration Engine motor can also process IDocs (Intermediate Documents) and RFCs (Remote Function Calls). This option is available for applications that have already identified IDocs or RFCs, as well for applications of SAP components that do not yet have access to the proxy era functions.

The pursuing are types of other important elements of this infrastructure:

Proxy Generation

Integration Repository

Integration Directory

The integration operations involved can take place between heterogeneous system components within a company, as well as between business lovers outside company restrictions.

Adapter Runtime

A central element of the adapter runtime is the Adapter Framework, with services for messaging, queuing, and security handling. The adapter platform helps the JCA standard (JCA: J2EE Connection Structures) and communicates with Source Adapters, which can be either a component of SAP XI or are provided by SAP lovers. All adapters transported by SAP are source of information adapters, in addition to the IDoc adapter.

The pursuing adapter components derive from the adapter construction:

Adapter Engine unit (J2EE): For adapter communication within a system network.

Partner Connectivity Set (J2EE): Enables business companions who do not have SAP XI installed to get and send messages

System landscape Directory

Business companions who use SAP Exchange Infrastructure (XI) can exchange messages between their system landscapes.

If both business associates use SAP XI 3. 0, then we can connect the two Integration Servers to exchange data.

An SAP XI 3. 0 Integration Server can also send and receive SAP XI 2. 0 information. Therefore, it is also possible to combine business partners who use SAP XI 2. 0.

Small business lovers who do not use SAP XI may use the Partner Connectivity

Kit (PCK) to exchange messages with the machine landscape of any business partner

who uses SAP XI 3. 0.

Partner Connectivity Kit

The PCK of the smaller business partner will get a note from its system scenery and converts the format of the message to XI concept protocol. The meaning is forwarded to the Integration Server for further processing.

To onward XML communications from the Integration Server to a recipient business system in the machine landscape of small business partner, the PCK of the business enterprise partner obtains the message, changes into the format required by the device system, and then forwards the communication. The PCK contains the following adapters:

RFC Adapter

File Adapter

JMS Adapter

JDBC Adapter

SOAP Adapter

XI Adapter

How SAP XI works with. Net?

If the. NET program is exposing any API in the form of Web servics, SAP XI can make a call to the web service.

If. Net app is on the sending then it can call SAP XI utilizing a HTTP call or utilizing a Web service.

WSDL (Web Services Information Language) is produced using SAP XI and then it's used to create your client proxies in VB. The ASP. NET web program interacts with SAP XI using generated VB school and SAP XI's SOAP adapter.







Generate Client proxies using WSDL in VB/C#

Reference. cs

Form. aspx

Form. aspx. cs

Webapp. dll

ASP. NET Web Appln

Steps for connecting. Net with SAP:

Configurations from SAP Xi side

Create request note mapping.

Create response communication mapping.

Create program mapping between source & focus on.

Create sender communication route of type Cleaning soap adapter using the outbound synchronous software and its own namespace.

Create device communication channel of type RFC adapter.

Create receiver willpower using sender service, outbound synchronous software, device R/3 business system and then create user interface determination using RFC and lastly create receiver agreement using receiver RFC channel.

Create a WSDL for the outbound synchronous software. Use this Link http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel while determining web service. Save the WSDL (Web Services Explanation Dialect) in the neighborhood system.

Configurations in. Online side

Open the development environment of Microsoft Visual Studio. NET and create a new job of type Aesthetic Basic using the template ASP. NET Web Software.

Copy the WSDL made using SAP XI in the root folder of web request.

Go To solution explorer --> Referrals --> Add Web Reference point.

Browse To: Web services on local machines.

Select the service and select Add reference point.

When the net research is added for the WSDL the. VB source (proxy) is made in the net Personal references folder of the net software. This proxy must be compiled into Dynamic Linked Collection. DLL. Because of this, build the web software using Build-->Build Web request. The DLL is produced in webapp/bin/ folder


Monitoring is better than other middleware product. It offers exhaustive monitoring features like message, performance, part monitoring etc, all of which can be used to monitor and rectify the mistakes. It comes after a hub and spoke model.

When we need to incorporate with an SAP system XI comes with an advantage in helping various SAP components and so forth.

Process functionalities inside XI to change content in the communication channel on own defined guidelines for business purposes.

Mappings and adapters are good as comparable with any other middleware product.

Synchronous & Asynchronous communication can be done.


Web methods are specifically good if u have B2B kind of communication with their Trading Companions product.

XI is lacking full-fledged Message Queue compared to other set up Middleware products.

It lacks in potential to process huge messages but SAP is focusing on that.

It does not have a messaging coating uncovered by APIs like IBM MQ-Series.

It is not comparable to Tibco in conditions of quickness.

SAP depends on other vendors aside from a few adapters.


Currently applications in Honeywell are employing the various SAP connectors. Migrating the applications integration to SAP Exchange Infrastructure are certain to get cost benefits by staying away from SAP connection licenses. SAP PI Bottom part Engine is charged based on the entire processed message quantity expressed in Gigabytes (GB) per month. The applications will also benefit from modern integration functionalities like "delivery assurance", "once-only", "ordered-delivery", "prioritization", "overview of information and resubmitting after correction". SAP Xi is one of the key blocks of enterprise SOA structures provided by SAP.

We can continue to leverage towards Honeywell SOA established IT surroundings with SAP Xi.

More than 7 000 students trust us to do their work
90% of customers place more than 5 orders with us
Special price $5 /page
Check the price
for your assignment