DIFFERENCE BETWEEN ALE WITH XI

[Former Member]

helo experts,

DIFFERENCE BETWEEN ALE WITH XI

thanx in advance,

[Former Member]

thanq

[former_member192295]

HI,

Through ALE we can communicate with some few systems, but using xi we can communcate with any system using adapters, proxies and webservices

find below link for more information

[Former Member]

Hi,

XI is a middleware which connects 'n' number of systems within or across the company.It connect all the application systems by staying at the middle.So, since a large scale company contain many application systems in their respective departments, such company need a middleware to connect them.

But, ALE comes into picture only when SAP System is involved(SAP-SAP, SAP-NON SAP communication).

Thanks,

Bharath.

[former_member182455]

Hi aravind

Application Link Enabling (ALE) is a mechanism for the exchange of business data between loosely-coupled R/3 applications built by customers of SAP, the enterprise resource management program. ALE provides SAP customers with a program distribution model and technology that enables them to interconnect programs across various platforms and systems.

The idea behind ALE is to provide a more rigid integration service while allowing a high degree of independence to the individual SAP com

check this tutorial:

http://www.thespot4sap.com/Articles/SAP_ALE_Introduction.asp

The use of ALE offers a number of advantages:

Distribution of application data between R/3 Systems with different releases

Data exchange can continues after an upgrade without any further adjustment

Customer-specific enhancements

The integration of non-SAP systems through communication interfaces

Coupling R/3 and R/2 Systems

What is XI

SAP Exchange Infrastructure is SAP’s platform for process integration based on the exchange of XML messages.

1. It 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.

2. It delivers business process integration knowledge to the customer in the form of SAP pre-defined business scenarios.

3. It provides an integrated tool set for building new business scenarios by defining and maintaining all integration relevant information. (“Shared collaboration knowledge”).

Before we take a closer look at how the Exchange Infrastructure will enter into the IT landscape of every SAP customer, let’s take a closer look at the capabilities as well as the strategic direction of XI. This particular module of Net Weaver is one of the most powerful and is undeniably the most critical. Its purpose is really three-fold:

Connect:

XI has the ability to connect all applications regardless of whether it is an application

From a 3rd party or from SAP. The solution has pre-built connectivity to all SAP modules

Such as SAP CRM and utilizes the Adapter Framework to integrate 3rd Party solutions

such as Siebel, People Soft, Legacy systems, or AS/400s and Mainframes.

Coordinate:

XI has the ability to define a path/workflow for each business transaction that is

Integrated. The system actively routes each message to ensure that it is properly

Delivered from the source to the target destination. Active monitoring allows

Administrators to manage document exchange on an exception basis.

Communicate:

XI has the ability to translate files into any format whether an internal file format or any

Business to Business integration standard including but not limited to an XML format, an

EDI format, a marketplace, or a Web Service. Finally, there are multiple communication

Protocols included which allow the routing of a file over protocols such as s/FTP, http/s,

SOAP, ebMS, Value-Added Networks, or EDI INT (AS1, AS2).

Understanding The SAP Exchange Infrastructure_

Now, you might be saying to yourself, we already have solutions that provide all of this

Functionality. True, most organizations have invested previously in an integration strategy, but what we see in over 90% of organizations is that they have multiple translators and communication brokers, which they are supporting on a daily basis. This is both a resource drain as well as a monetary drain. For example, it is not uncommon to see the following even in smaller organizations:

• Multiple Point to Point connectivity: For example, R/3 connected to a 3rd party

Warehouse Management Solution via an internally developed adapter or with the SAP

Business Connector

• A 3rd party EAI Integration Broker to connect legacy mainframe systems to SAP and

WMS

• A 3rd party EDI translator to communicate messages

• A 3rd party XML broker to communicate XML messages to marketplaces and non-EDI

Trading partners

• A communication server that focuses on sending messages via FTP, Value-Added

Networks and Internet protocols such as AS2 solution of choice for SAP end users

Interface-

regards

srinivas

[prateek]

Regards,

Prateek