Overview XI/PI

Product Components and Functionalities Overview

Arquitecture

Components• SLD – System Landscape Directory – contains the registry of the systems

evolved in integration interfaces, organized in Product/Software Components, Technical Systems and Business Systems;

• Integration Builder – integration development environment– Integration Repository(Design) – interface objects design: software components,

namespaces, data types, message types, message interfaces, message mappings, interface mappings

– Integration Directory(Configuration) – interface objects configuration: integration scenarios, communication channels, sender agreements, receiver determinations, interface determinations, receiver agreements

• Integration Server – integration runtime environment– Intergrations processing – pipeline;– XML messages monitoring(SXI_MONITOR);– Message processing queues monitoring(SMQR);– Cache monitoring(SXI_CACHE);

Componentes(cont...)

• Adapters – Software pieces to communication with several types of protocols (SOAP, JDBC, RFC, IDoc, File/FTP, etc);

• Central Monitoring – CCMS – Computing Center Management System– Runtime Workbench – Component Monitoring (

communication channel monitoring), Message Monitoring, Alert Configuration, Alert Inbox;

– Alert Framework – E-mail messages sending warning about interface messages with processing errors in PI/XI.;

Integration Builder(Started by transaction SXMB_IFR)

Index

SLD(System Landscape Directory – Started by a link in Integration Builder start

page)

Index

SLD(Products/Software Components)

Index

The Product/Software Component registry, is based in software/systems versioning/release data. In these objects remains data like Product Name, Vendor, Version, Release state(Beta, Testing, Released, etc)

Product

Software Component

SLD(Technical Systems)

Index

A Technical System is a technical registry about a installed Product/Software Component, thus, in the Technical System are registered phisical installation data about the system(host, version installed, software components available). A Product/Software Component can be registered as several Technical Systems(Development, Quality Assurance, Production environments for example)

Technical System

Product Software Components

SLD(Business Systems)

Index

A Business System is a object created on SLD to be used on XI/PI Configuration(Integration Directory) objects. A Business System registry contains the corresponding Technical System, which is the Integration Server(XI/PI) that will integrate it (XI/PI DEV,QAS,PRD). Usually, there is a Business System for each Technical System.

Business System

Related Technical System

Integration Builder – Integration Repository(Design)

Index


• Software Component and Software Component Version

– Namespace

• Interface Objects

– Data types

– Message Types

– Message Interface

• Mapping Objects– Message Mapping

– Interface Mapping

• Integration Scenarios & Integration Processes

– Integration Scenario

– Imported Objects

Index


Software Component/Software Component Version

This design object is imported from SLD, from the Product/Software Component registry.

Index


Namespace

Namespaces are components under which the interface design objects are grouped/constructed. Basicly it´s function is act as a grouping component, its naming can help to identify objects belonging to a specific interface.

Index


Interface Objects

Definition of objects for data structures and operation mode(synchronous/asynchronous)/direction(inbound/outbound) of interfaces

Index


Data Type

Data types are definitions of data structures that will be processed by interfaces. A data type can be composed by another data types(in the picture above, the DT_FuncLocCreate uses in its composition, two another data types: DT_BAPI_ITOB and

DT_BAPI_ITOB_FL_ONLY, as can be seen in the column “Type”);

Index


Message Type

Message Types are definitions of messages that will be processed in interfaces, and its structure is defined by a given data type(so, we can conclude that data types are created/composed to be used in Message Types creation). In the example above, the message type MT_FuncLocCreate, is created using the data type DT_FuncLocCreate; Index


Message Interface

Message Interfaces are used to define the interface mode(sync/async) and direction(Inbound/Outbound), and the message(s) evolved, in respect to the System that it belongs. In the example above, we have the message interface MI_FuncLocCreate, that uses the message type MT_FuncLocCreate, is Asynchronous and Outbound(the data is sent OUT from external system – GISConneX - to XI – for

an Inbound interface, the data is sent from XI and arrives IN external system);Index


Mapping Objects

The node Mapping Objects contains objects related to structures/data mapping/conversions

Index


Message Mapping

A Message Mapping is used to make structure and/or data conversions (for example: from a WebService call to a RFC Function call). In the example above, the data received in the message type MT_FuncLocCreate, is mapped to a call for the BAPI_FUNCLOC_CREATE, and in detail is a conversion of field EQINSTALL(if EQINSTALL of MT_FuncLocCreate is equals to “Y” or “X”, the value “X” is mapped to EQINSTALL in

BAPI_FUNCLOC_CREATE, else the value “ “ is mapped); Index


Interface Mapping

An Interface Mapping is used to define Sender and Receiver interface, messages and mapping(s) evolved. In the example above, the Sender is the Message Interface MI_FuncLocCreate and the Receiver is the BAPI_FUNCLOC_CREATE, the messages are MT_FuncLocCreate and BAPI_FUNCLOC_CREATE, and the mapping is MM_FuncLocCreate; Index


Integration Scenarios & Integration Processes

Index

The Integration Scenarios & Integration Processes node, contains Integration Scenarios(a graphical view of the interfaces that compose a scenario, used to provide the Configuration Template of these interfaces, for the Integration Directory – Configuration), Actions(objects used to compose Integration Scenarios) and Integration Processes(that is orchestration of XI/PI interface messagesto manage processes);


Integration Scenario

Index

The Integration Scenario is a graphical view of the interfaces that compose a scenario, used to provide the Configuration Template of these interfaces, for the Integration Directory(Configuration). In the picture above, each pair of boxes with a line connecting them, corresponds to an interface. When the boxes are aligned, this means that is a sync interface, and when the one box is below the other(see the second pair in the picture), this means that is an async interface. Each box pair connected contains pre-configuration data, that will be used in Integration Directory(Configuration) to configure these interfaces, using a wizard;


Imported Objects

Index

The Imported Objects node, is used to import objects from SAP environments: RFCs – ABAP functions configured as Remote Enabled Module(BAPIs and customized RFC functions) IDocs;

Integration Builder – Integration Directory(Configuration)

Index


• Integration Scenarios

– Business System• Communication Channel

– Sender Agreement

– Receiver Determination

– Interface Determination

– Receiver Agreement

Index


Integration Scenarios

Integration Scenarios in XI/PI Configuration are containers usually used to group configuration objects that belongs to a same interface, or group of interfaces.

Index


Objetos Integr. Scenario

The Integration Scenario contain the following configuration objects: Business Systems integrated, Communication Channels, Sender Agreement, Receiver Determination, Interface Determination and Receiver Agreement

Index


Business System

The Business Systems related on an Integration Scenario, are the Business Systems designed in SLD(System Landscape Directory), that need to be assigned in XI/PI Configuration before to be used. They represents the systems that are being integrated(that participate in interfaces) by the objects inside the Integration Scenario. Usually, in a Integration Scenario exists at least two Business Systems.

Index

Business SystemBusiness System


Communication Channels

Communication Channels are objects where are configured Adapters, to promote communication with external world(from the XI/PI point of view). There are a lot of Adapter types that can be used, like JDBC, SOAP, RFC... Above, two sample Comm. Channels, one using SOAP, another using RFC adapter;

Index


Sender Agreement

The Sender Agreement specify, for a Sender System and an outbound interface, which is the Sender Communication Channel that will process the data sent by the Sender System and starts the interface. Index

Sender Business System

Outbound Interface(in this case, a Message Interface, and the

Namespace where it was defined on XI Design)

Sender Communication Channel


Receiver Determination

The Receiver Determination specify, for a Sender System and outbound Interface, which is/are the Receiver System(s) registered to receive data from this outbound interface, and shows which is/are the inbound interfaces related, defined in the next object, the Interface Determination. Index




Receiver Business System


Interface Determination

The Interface Determination specify, for a Sender System and outbound interface, which is the registered Receiver System, which inbound interface(s) of the given Receiver System will receive data, and the interface mapping(s) related;

Index




Receiver Business System

Interface MappingInbound Interface(in this case, a BAPI – a remote enabled module –

Imported in XI Design)


Receiver Agreement

The Receiver Agreement specify, for a given Sender System, a Receiver System and an outbound interface, which is the Communication Channel that will be used to deliver data to the Receiver System.

Index


Receiver Communication Channel

Inbound Interface(in this case, a BAPI – a remote enabled module –

Imported in XI Design)

Integration Server(Runtime)

Index

Integration Server(Runtime)

Index

The Integration Server run in the ABAP stack of XI, and is the XI/PI component responsible to processing the interfaces defined in Integration Repository(Design) and configured in Integration Directory(Configuration). Here is processed the XI Pipeline(the sequence of steps needed to process an interface message), that better shows for what are the objects created on Design and Configuration. Also, the Integration Server make available some tools for interfaces and environment monitoring, discussed in next steps.

Integration Server – XI Pipeline(Where are all Design and Configuration objects used ?)

When a message is sent by a Sender System to XI/PI, the following occurs:1.- Sender Communication Channel receives the message, the Integration Engine so identify what is the Sender Agreement related to the Communication Channel activated;2.- According to Sender Agreement, identify the receiver system(s) looking at Receiver Determination;3.- According to Receiver Determination, identify the interface(s) that must be activated;4.- If there are more than one interface to receive data, message is splitted;5.- Message(s) is sent to Interface Mapping(defined on XI Design), that activate the corresponding Message Mapping(s);6.- Integration Engine makes the technical routing, sending the output messages(from the mapping(s)) to the corresponding Receiver Agreement(s);7.- The corresponding Receiver Communication Channel(s) is/are activated, to send the data to the Receiver System(s).

1.-Sender Communication Channel receives a call,The corresponding Sender Agreement is identified

2.-According to Sender Agreement specifications, Integration Server identify Receiver(s) by the

Receiver Determination

3.- According to Receiver Determination, Integration Server identify the interface(s) that must receive data

4.- If more than one interface is to receive data, message is splitted

5.- Integration Server send the message(s) to the Corresponding Interface Mapping(s), that activate the

corresponding Message Mapping(s)

6.- The message(s) mapped are routed to the corresponding Receiver Agreement(s)

7.- The corresponding Receiver Communication Channel(s) are

activated to send data to Receiver System(s)

Index

Integration Server(XML Messages Monitoring – SXI_MONITOR)

Index

The SXI_MONITOR transaction make available the XML messages process monitoring, being one of main resources for identification of message processing errors in XI/PI. It´s possible to filter the messages by several parameters, like date/time, system(sender/receiver), etc.

After execute the SXI_MONITOR transaction, it returns something like the above screenshot, a list of processed messages, according with the parameters filled in the previous screen. In this example, all messages was processed successfully(the “square-lined flag” icon indicates that the message was processed successfully by the integration server). Note that, a message with success status here, can yet be in error status in the Runtime Workbench Message Monitoring(because here basicly is validated the route of the interface - from where the message arrives, and to where need to be delivered - and the message mapping. In the Runtime Workbench you will find errors received by the Communication Channels,

when trying to deliver a message to a receiver system).

Integration Server(XML Messages Monitoring – SXI_MONITOR)-cont.

Index

Integration Server(XML Messages Monitoring – SXI_MONITOR)-cont.

Index

When double-click on a line in the previous screen, a screen with message details is showed, and here is possible to see the XML content processed, and in case of processing error, check the error message, request reprocessing or cancelling of the message(for async interface messages).

Integration Server(Cache Monitoring – SXI_CACHE)

Index

The SXI_CACHE transaction make possible to check the XI Cache status. This screen is related to cache of objects developed in XI Design and Configuration. If there are problems with cache update, the XI/PI will not be able to process interface messages correctly.

Integration Server(Queue Monitoring – SMQR)

Index

The SMQR transaction allows the monitoring of async messages processing queues. After select all queue prefix names, like picture above, and click on button “qRFC Monitor”, the system navigates to the screen in the next slide.

Integration Server(Queue Monitoring – SMQR) – cont.

Index

In this screen, in a production environment with several messages being processed, is possible to see the async messages processing queues, being filled and emptied, and check details for each one.

Runtime Workbench

Index

The Runtime Workbench contain the most used monitoring tools to identify and solve message processing problems.

Runtime Workbench(Component Monitoring)

Index

The Component Monitoring allow to check the state of several XI/PI components, and the most used is to check the Adapter Engine and the Communication Channel Monitoring, that can be seen in the next slide.

Runtime Workbench(Component Monitoring – Comm. Channel Monit.)

Index

Runtime Workbench(Component Monitoring – Comm. Channel Monit.)-cont.

Index

The Communication Channel Monitoring allows to check state of the several communication channels existing in the environment, and in case of processing error, allows to check error messages from the adapters log.

Runtime Workbench(Component Monitoring – Comm. Channel Monit.)-cont.

Index

When a Communication Channel is selected, the screen show message processing details of it.

Runtime Workbench(Message Monitoring)

Index

The Message Monitoring, checking messages processed by the Adapter Engine, is one of the most used tools to identify and solve problems in message processing. Sometimes, a message processed successfully in Integration Engine, can stop with error here, for example, in the case of a adapter that could not connect with the receiver system(for example, in an interface with database, if the database is not working, the message will stop with error in the adapter message monitoring).

Runtime Workbench(Message Monitoring) – cont.

Index

In the same way as SXI_MONITOR transaction, it´s possible to configure several parameters for message selection in Runtime Workbench Message Monitoring. It´s possible to see details of each processed message, as is showed in the next slide.

Runtime Workbench(Message Monitoring) – cont.

Index

Alert Framework(e-Mail with error advice)

Index

Another tool extremely useful, is the Alert Framework, that correctly configured, allows that XI/PI sent e-mails to pre-defined destinations, communicating errors ocurred in interface messages processing. These messages can inclusive carry links to XI monitoring screens, allowing monitoring, check, identification and solving problems to be more easy.

Overview XI/PI

Documents

Transcript of Overview XI/PI