Solved: Architecture

Former Member · ‎09-08-2006

Hi,

What is your Answer in brief to the question,

Explain XI Architecture?

Thanks

Seshu

Former Member · ‎09-08-2006

Hi Seshu,

From SAP Help the information i could gather regarding the

XI Architecture, is as follows....

The principle architecture of an SAP Exchange Infrastructure (XI) landscape is described in the Master Guide – SAP NetWeaver ’04 and in the SAP Exchange Infrastructure: Technical Infrastructure guide.

An XI landscape consists of either a full-fledged XI used for communication between various types of back-end application systems (business systems), or of a light-weight Partner Connectivity Kit (PCK) that serves as an endpoint for B2B communication.

XI landscape has the following groups of components:

- Messaging components responsible for message processing and protocol handling. These components include the Integration Server (IS) with the central Integration Engine and the central Adapter Engine (AE), optional decentral Adapter Engines, and optional J2SE-based Adapter Engines.

- Tools for design, configuration, administration, and monitoring purposes (Integration Builder, Exchange Profile, System Landscape Directory, Runtime Workbench, Search and Classification Engine TREX) that require user interaction and are not directly involved in messaging.

- Backend systems and business partner systems that act as the sender or receiver of messages.

Concerning security, the following XI components have to be considered in more detail:

1. Integration Server

The XI 3.0 Integration Server is based on SAP Web Application Server (Web AS) 6.40. The Integration Server acts as a hub for a set of senders and receivers of messages. Technically, an Integration Server consists of three engines:

- Integration Engine

This engine processes XI messages according to the configuration defined with the Integration Builder.

- Central Adapter Engine

This engine connects senders and receivers that do not speak the XI message protocol by handing over messages to the Integration Engine and the other way round. Additional non-central Adapter Engines can be installed on the J2EE part of SAP Web AS 6.40 without Integration Engines.

- Business Process Engine

This engine is part of the Integration Server, but it is not relevant for security and therefore not depicted in the figure above.

2. Non-central Adapter Engines

Technically, there are two different types of Adapter Engines:

- J2EE-based Adapter Engine

This type of Adapter Engine runs on the SAP J2EE Engine. There may be any number of non-central Adapter Engines, each associated with exactly one Integration Server with which the Adapter Engine communicates using the XI protocol.

- Plain J2SE Adapter Engine

This type of Adapter Engine was already available with XI 2.0. It merely requires a Java Virtual Machine to run.

3. Integration Builder

Comprises a set of tools for designing, configuring, administrating and monitoring an Exchange Infrastructure. The major parts are:

- Integration Repository

Contains interfaces and mappings available across several landscapes. The Integration Repository runs on the SAP J2EE Engine.

- Integration Directory

Contains meta data for a given landscape, such as routing relations, communication channels, and security settings. The Integration Directory runs on the SAP J2EE Engine.

4. Runtime Workbench

Provides tools for monitoring an Exchange Infrastructure.

5. TREX (optional)

Standalone engine required for payload-based message search in XI.

6. Exchange Profile

Contains the most basic technical configuration data of an XI landscape

7. System Landscape Directory

Describes the components that make up the given landscape.

8. Sender and receiver business systems

Depending on the message protocol, there are several types of systems:

- SAP business systems residing on SAP Web AS 6.40

These communicate with the Integration Server by using XI proxies (ABAP or Java).

- SAP business systems residing on SAP Web AS 6.20

These incorporate XI 2.0 proxies which enable them to send and receive XML messages in the XI 2.0 message format. The XI 3.0 Integration Server maps between XI 2.0 and XI 3.0 message formats.

- SAP business systems residing on SAP Web AS 6.10 or lower

These do not contain XI proxies, thus have to communicate with the Integration Server by using RFC and IDoc adapters.

- Non-SAP business systems

Any systems that exchange XML messages or other protocols by using the Integration Server. They are connected to XI by using adapters.

I guess this information gives you a very clear picture of the XI Architecture.

Regards,

Abhy

Former Member · ‎09-08-2006

Sorry I reposted it by mistake.

Message was edited by: Abhy Thomas

Former Member · ‎09-08-2006

Hi Seshu,

Beginning with the components of SAP Exchange Infrastructure (XI),

Main component of SAP XI is Integration Server,Integration Engine, System Landscape Directory (SLD), Integration Builder.

The Integration Server is a central communication and 'distribution engine’ that processes XML messages. This includes services for determining receivers (logical and technical routing) and for the transformation of message contents between sender and receiver systems (mapping). The Integration Engine can also receive messages from, or send messages to (by using HTTP) other runtime components of SAP Exchange Infrastructure by using communication services. Without these components you would not be able to exchange messages using the Exchange Infrastructure.

Adapters enable you to connect interfaces from external systems or from SAP systems with SAP Basis Release 4.6 or earlier, to the Integration Engine. Interfaces involved in the integration scenario can be imported into a central Integration Repository.

You can use the Integration Builder to create and edit objects in both the design and configuration phases. Two different tools are available to you in the design and configuration phase. You can call both tools from the start page of the Integration Builder.

SAP’s Exchange Infrastructure is a new program model for new developments. This model enables you to define platform-independent interface descriptions in the central Integration Repository. You can then use the descriptions to generate interface proxies for Java applications and for SAP systems. In this case, XML messages are exchanged with the Proxy Runtime using the Integration Engine.

former_member91687 · ‎09-08-2006

Hi,

The architecture of XI would include components to be used at design time, configuration time and those used at runtime.

The components being:

1. SLD- Which is the central repository of information.

2. Integration builder- Comprises the ID and IR.

3. Integration Server- Central processing engine of XI.

4. Central Monitoring- Gives a comprehensive view off all components and processes at runtime.

5. The Adapter engine- A JCA compliant adapter engine through which backend systems can be connected to XI.

You could look for more info on each of these, but this should be the architecture in brief

Regards,

Chandra

bhavesh_kantilal · ‎09-08-2006

Seshu,

Answer in brief to this is difficult

XI in terms of architecture has the following components,

1.SLD

2. Integration Builder comprising Intergration Repository and Integration Directory

3. Integration Server -- Consists of Integration Engine , Business Process Engine and the Adapter / J2ee ENgine.

4. Supports Synch as well as Asynch Processing

5. Uses SOAP protocol to exhange XML messages.

Regards,

Bhavesh

Architecture

Accepted Solutions (1)

Accepted Solutions (1)

Answers (4)

Answers (4)

Re: HTTP Receiver adapter with Dynamic value in UR...

How to create a rolling forecast in SAC? I have an...

In SAP Hana Cloud, do packages exist as database o...

Re: Mass Update a Zfield in Std Table with Split &...

Re: Change BW Query Initial Variable Input at runt...