BIT400 - 2005-Q2 - Ltr - SAP Exchange Infrastructure

BIT400SAP Exchange InfrastructureSAP NetWeaver

Date Training Center Instructors Education Website

Participant HandbookCourse Version: 2005 Q2 Course Duration: 5 Day(s) Material Number: 50070510

An SAP course - use it to learn, reference it for work

CopyrightCopyright 2005 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. Additionally this publication and its contents are provided solely for your use, this publication and its contents may not be rented, transferred or sold without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Trademarks Microsoft, WINDOWS, NT, EXCEL, Word, PowerPoint and SQL Server are registered trademarks of Microsoft Corporation. IBM, DB2, OS/2, DB2/6000, Parallel Sysplex, MVS/ESA, RS/6000, AIX, S/390, AS/400, OS/390, and OS/400 are registered trademarks of IBM Corporation. ORACLE is a registered trademark of ORACLE Corporation. INFORMIX-OnLine for SAP and INFORMIX Dynamic ServerTM are registered trademarks of Informix Software Incorporated. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, the Citrix logo, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, MultiWin and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc. HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. JAVA is a registered trademark of Sun Microsystems, Inc. JAVASCRIPT is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.com are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other products mentioned are trademarks or registered trademarks of their respective companies.

DisclaimerTHESE MATERIALS ARE PROVIDED BY SAP ON AN "AS IS" BASIS, AND SAP EXPRESSLY DISCLAIMS ANY AND ALL WARRANTIES, EXPRESS OR APPLIED, INCLUDING WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THESE MATERIALS AND THE SERVICE, INFORMATION, TEXT, GRAPHICS, LINKS, OR ANY OTHER MATERIALS AND PRODUCTS CONTAINED HEREIN. IN NO EVENT SHALL SAP BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES OF ANY KIND WHATSOEVER, INCLUDING WITHOUT LIMITATION LOST REVENUES OR LOST PROFITS, WHICH MAY RESULT FROM THE USE OF THESE MATERIALS OR INCLUDED SOFTWARE COMPONENTS.

About This HandbookThis handbook is intended to complement the instructor-led presentation of this course, and serve as a source of reference. It is not suitable for self-study.

Typographic ConventionsAmerican English is the standard used in this handbook. The following typographic conventions are also used. Type Style Example text Description Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths, and options. Also used for cross-references to other documentation both internal (in this documentation) and external (in other locations, such as SAPNet). Example text EXAMPLE TEXT Emphasized words or phrases in body text, titles of graphics, and tables Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example SELECT and INCLUDE. Screen output. This includes file and directory names and their paths, messages, names of variables and parameters, and passages of the source text of a program. Exact user entry. These are words and characters that you enter in the system exactly as they appear in the documentation. Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

Example text

Example text

2005/Q2

2005 SAP AG. All rights reserved.

iii

About This Handbook

BIT400

Icons in Body TextThe following icons are used in this handbook. Icon Meaning For more information, tips, or background Note or further explanation of previous point Exception or caution Procedures

Indicates that the item is displayed in the instructors presentation.

iv


2005/Q2

ContentsCourse Overview ............................................................................. viiCourse Goals.................................................................................vii Course Objectives ...........................................................................vii

Unit 1: Introduction to SAP Exchange Infrastructure ..................................1Work Method of SAP Exchange Infrastructure ........................................... 2

Unit 2: The System Landscape............................................................ 17Software Components and Products..................................................... 19 Implementing Technical Systems......................................................... 35 Business Systems and the Integration Directory ....................................... 46

Unit 3: SAP XI Pipeline Example for an Asynchronous Scenario ................. 59Introducing the Scenario ................................................................... 61 XI Messages: Structure and Transfer to the Pipeline .................................. 79 Logical Routing ............................................................................. 88 Mapping and Technical Routing ......................................................... 102 Message Mapping ......................................................................... 115

Unit 4: Runtime Workbench...............................................................133Runtime Workbench Overview........................................................... 134

Unit 5: XI Connectivity .....................................................................145XI Connectivity ............................................................................. 147 HTTP Adapter .............................................................................. 158 XI Proxy Overview ......................................................................... 169 IDoc Adapter ............................................................................... 190 Receiver IDoc Adapter .................................................................... 204 Sender IDoc Adapter ...................................................................... 221 Receiver File/FTP Adapter ............................................................... 237 Sender File/FTP Adapter ................................................................. 254 RFC Adapter Overview ................................................................... 274 Receiver RFC Adapter .................................................................... 288 Sender RFC Adapter ...................................................................... 302 B2B: Business-to-Business .............................................................. 316

2005/Q2


v

Contents

BIT400

Unit 6: Business Process Management ................................................323BPM Overview ............................................................................. 324 ccBPM: Designing and Configuring Integration Processes .......................... 331 BPM Runtime .............................................................................. 345

Appendix 1: Appendix: SAP XI 3.0 Roadmap

......................................357

Appendix 2: Authorizations and Support Packages for Importing IDoc Types and RFC Signatures ......................................................................367

vi


2005/Q2

Course OverviewThis course demonstrates how to implement scenarios in a distributed system landscape by using SAP Exchange Infrastructure (SAP XI). It introduces the architecture and features of SAP XI. It gives a detailed introduction to scenario configuration and the connection of back-end systems by using adapters.

Target AudienceThis course is intended for the following audiences: Developers and consultants who want to configure scenarios using SAP Exchange Infrastructure

Course PrerequisitesRequired Knowledge Basic knowledge of business processes in distributed system landscapes Basic knowledge of integration technologies

Recommended Knowledge Basic knowledge of IDoc processing (for IDoc adapters)

Course GoalsThis course will prepare you to: Configure scenarios in SAP Exchange Infrastructure Connect systems to SAP Exchange Infrastructure by using adapters

Course ObjectivesAfter completing this course, you will be able to: Configure an asynchronous scenario with different outbound and inbound interfaces Connect sender or receiver SAP systems using the IDoc adapter or the RFC adapter

2005/Q2


vii

Course Overview

BIT400

Transfer files as a data source to SAP Exchange Infrastructure by using the file adapter, and write messages from SAP Exchange Infrastructure to a file using the file adapter

SAP Software Component InformationThe information in this course pertains to the following SAP Software Components and releases:

viii


2005/Q2

Unit 1Introduction to SAP Exchange InfrastructureUnit OverviewThis unit introduces the functions and architecture of SAP Exchange Infrastructure (SAP XI).

Unit ObjectivesAfter completing this unit, you will be able to: Describe how SAP Exchange Infrastructure processes messages List the options available for connecting application systems to SAP Exchange Infrastructure

Unit ContentsLesson: Work Method of SAP Exchange Infrastructure .......................... 2

2005/Q2


1

Unit 1: Introduction to SAP Exchange Infrastructure

BIT400

Lesson: Work Method of SAP Exchange InfrastructureLesson OverviewThis lesson explains how SAP Exchange Infrastructure (XI) processes messages and how to connect application systems.

Lesson ObjectivesAfter completing this lesson, you will be able to: Describe how SAP Exchange Infrastructure processes messages List the options available for connecting application systems to SAP Exchange Infrastructure

Business ExampleYou want to implement business processes in a distributed system landscape. You want messages to be sent as uniformly as possible when data is transferred between systems. You want to use SAP Exchange Infrastructure to do this.

Complex System LandscapesIn the past, you integrated different applications in an SAP system by saving all the data in a database, but system landscapes have since become much more complex.

2


2005/Q2

BIT400

Lesson: Work Method of SAP Exchange Infrastructure

Figure 1: Historical Development of System Landscapes

Business processes in a heterogeneous system landscape generally span several systems. Until now, you had to develop the external interfaces separately for each interface exchanging data between systems. The method you chose depended on the options available at the time of development.

External Interfaces Using Point-To-Point ConnectionsIf interfaces are developed between two systems in such a way that the sender system sends a document to the receiver system, this is what is called a point-to-point connection. If you look at the whole system landscape with all its interfaces, you will see that this often results in a complicated network of connections.

2005/Q2


3


BIT400

Figure 2: System Landscape with Point-To-Point Connections

Technical Implementation of a Point-To-Point ConnectionSender and receiver software components are usually made by different vendors and function using different technologies. The software components often provide external outbound and inbound interfaces. However, they differ in their document structure and in the protocol that the systems support.

Figure 3: Technical View of a Point-To-Point Connection

To establish the connection, you use a connector that supports both protocols and can convert a message from one protocol to another. If the document structures are different, you map the source document fields to the target document fields by using a mapping program. Some connectors provide graphical mapping tools for this purpose.

4


2005/Q2

BIT400


Implementing Business ProcessesBefore you develop the interfaces you have to analyze the business process that you want to implement in a distributed system landscape. In this analysis, you have to determine which process steps you are going to implement in which system and in which software component.

Figure 4: Business Process in a Distributed System Landscape

Every time data is transferred between systems, you have to check whether an external interface exists and how the sender outbound interface fits together with the receiver inbound interface.

2005/Q2


5


BIT400

Figure 5: External Interfaces in a Distributed System Landscape

Next, you evaluate the various methods of developing the interface and then implement it. The relationship between the interface and the business process as a whole is often considered to be unimportant for the technical implementation. Usually, the documentation of the business process and the corresponding interfaces is not given high enough priority. Usually, the main priority is that the interface works. However, if the business process is changed at a later date or a software component is exchanged or updated, this can have an effect on communication between the interfaces. In this case it is important to know how the integration process and the interface are related.

External Interfaces Using SAP Exchange InfrastructureThe aim of SAP Exchange Infrastructure is to provide a platform that allows different interfaces to communicate using a uniform technology. This promotes overall clarity and reduces maintenance effort.

6


2005/Q2

BIT400


Figure 6: System Landscape with SAP Exchange Infrastructure

Architecture of SAP Exchange InfrastructureSAP Exchange Infrastructure comprises various components:

2005/Q2


7


BIT400

Figure 7: Architecture of SAP Exchange Infrastructure

You enter your system landscape details in the System Landscape Directory (SLD). You enter all the necessary interfaces of the various software components and store mapping programs in the Integration Repository. You configure the scenarios in the Integration Directory. The Integration Builder is the user interface (GUI) you use when working in the Integration Repository and the Integration Directory. The Business Process Engine controls the message correlations and how messages are processed as part of Business Process Management (BPM). The Integration Engine of the Integration Server ensures that the messages are processed in the Integration Directory according to the configuration. This involves determining who the receiver is and mapping the inbound message to the receiver interface structure. The Adapter Engine is the basis for multiple adapters used to connect systems to the Integration Server. The Runtime Workbench is the main tool used to centrally monitor components and messages.

8


2005/Q2

BIT400


The System Landscape in the SLDYou enter all the technical systems of the system landscape in the SLD. This includes host names and other technical attributes as well as information on the software component installed on a server. Assign a business system name to each technical system. This business system name is required for scenario configuration as the name for the sender and receiver systems.

Figure 8: The System Landscape in the SLD

Interfaces and Mapping Programs in the Integration RepositoryThe Integration Repository stores the interfaces of the software components you use.

2005/Q2


9


BIT400

Figure 9: Implementing Software Component Versions and Corresponding Interfaces

In some cases you can import the interfaces into the Integration Repository, in some cases you have to create them manually. You can save mapping rules for structure mapping and value mapping for each external interface. There is a graphical mapping tool for this purpose. Alternatively, you can create mapping programs in Java or XSLT.

10


2005/Q2

BIT400


Figure 10: Mapping Interfaces and Defining Mappings

You can create integration scenarios to provide a clear overview of the relationship between the interfaces and business processes.

Figure 11: Implementing Scenarios and Assigning the Interfaces and Mappings Used

You can create process steps for a system with a particular role; these steps are referred to as actions. You can assign outbound and inbound interfaces to each of these actions. Connect the actions by using connection lines. You can represent synchronous and asynchronous connections. Select an outbound interface for the sender system action

2005/Q2


11


BIT400

and an inbound interface for the receiver system action for each connection. You can specify a mapping program, if necessary, which maps the outbound interface to the inbound interface.

Configuring Scenarios in the Integration DirectoryThe Integration Repository only stores information relating to the development objects of a software component. For these objects it is not important whether, or on which server, the software component is actually installed.

Figure 12: Configuring Scenarios in the System Landscape in the Integration Directory

To implement business processes in a distributed system landscape, you configure configuration scenarios containing exact information on the business systems you want to send a message between. You create this configuration in the Integration Directory. The rules define which business system and which inbound interface a document is sent to once it has been sent from a business system with a particular outbound interface to the Integration Server.

Connecting Application Systems to SAP Exchange InfrastructureYou can install a local Integration Engine on any application system that runs on SAP Web AS (Release 6.20 or higher). This means you can implement application scenarios from XI. You define the interface structure in the Integration Repository. An outbound proxy can then be generated and called in the application system; this proxy creates a message in XI format from the interface parameters and sends it to

12


2005/Q2

BIT400


the Integration Server. An inbound proxy, on the other hand, can be generated in the target system; this proxy receives a message in XI format from the Integration Server and processes the data. Both ABAP and Java proxy generation is supported.

Figure 13: Runtime Procedure: Conversion to XI Message Format

For all other application systems, you have to use adapters to connect to XI. The sender system provides data in a document format and sends it to the adapter by using a protocol. The adapter converts the document to XI format and sends it to the Integration Server by HTTP(S). The adapter that is to receive the message is specified in the configuration. The Integration Server sends the message to the adapter. The adapter converts the message to the receiver protocol and sends it to the receiver.

2005/Q2


13


BIT400

Runtime Procedure of SAP Exchange Infrastructure

Figure 14: Runtime Procedure: Pipeline

The processing procedure begins in the Integration Server pipeline as soon as the message reaches the Integration Server in XI format. First of all, the receiver and the receiver inbound interface are determined from the configuration data. This step is called logical routing. If there are multiple receivers, the message is duplicated. For each receiver, the message with the structure of the sender outbound interface is mapped to the structure of the receiver inbound interface. The pipeline then determines the technical method for contacting the receiver. This is called technical routing. Finally, the message is sent to the target system or corresponding adapter.

14


2005/Q2

BIT400


Lesson SummaryYou should now be able to: Describe how SAP Exchange Infrastructure processes messages List the options available for connecting application systems to SAP Exchange Infrastructure

2005/Q2


15

Unit Summary

BIT400

Unit SummaryYou should now be able to: Describe how SAP Exchange Infrastructure processes messages List the options available for connecting application systems to SAP Exchange Infrastructure

16


2005/Q2

Unit 2The System LandscapeUnit OverviewThe technical system landscape determines the basic technical conditions for an integration solution. To achieve a successful integration, it is therefore important that you analyze your system landscape first. Which servers are available? Which basis software is installed on which server? (SAP Web AS ABAP, SAP Web AS Java, and so on.) Which transport protocols does this basis software support? Which application software is installed on which server? Which external interfaces and services are provided by the application software?

This unit explains how you represent your system landscape in the System Landscape Directory (SLD). It also covers how you define information for software components that are installed on the systems. You will be shown how to transfer software components from the SLD into the Integration Repository, and which information needs to be added in the Integration Repository. You will also be shown how to transfer systems entered in the SLD into the Integration Directory and how to enhance them by using communication channels.

Unit ObjectivesAfter completing this unit, you will be able to: Display SAP products and software components in the SLD Display software components and check for any interfaces in the Integration Repository Manually create products and software components in the SLD Display technical systems in the SLD and check their attributes Describe how SAP systems register with the SLD Manually create a technical system in the SLD and assign products and software components Create a business system in the SLD and assign it a technical system

2005/Q2


17

Unit 2: The System Landscape

BIT400

Import a business system into the Integration Directory

Unit ContentsLesson: Software Components and Products ................................... 19 Exercise 1: Software Components and Products ........................... 29 Lesson: Implementing Technical Systems........................................ 35 Exercise 2: Implementing Technical Systems ............................... 43 Lesson: Business Systems and the Integration Directory ...................... 46 Exercise 3: Business System .................................................. 51

18


2005/Q2

BIT400

Lesson: Software Components and Products

Lesson: Software Components and ProductsLesson OverviewThis lesson describes how you can represent software components in the System Landscape Directory.

Lesson ObjectivesAfter completing this lesson, you will be able to: Display SAP products and software components in the SLD Display software components and check for any interfaces in the Integration Repository Manually create products and software components in the SLD

Business ExampleYour integration scenario is based on a system landscape that consists of multiple servers and on which software is installed. Essential information relating to these software components is required by the SAP Exchange Infrastructure and needs to be centrally stored in a System Landscape Directory. This lesson explains how to represent software components.

Term DefinitionFrom a software vendor's point of view, a software component is a modular entity that you can also implement in multiple products. It comprises a standalone software component as well as an add-on. Software components are subject to further development, which results in various software component versions. A product is a grouping of software components that is shipped to customers. A product is also subject to further development. This might be due to new changes made to the software components that it contains, or due to the addition of further software components if the product has had functional enhancements made to it. Thus, each product usually has multiple product versions. For example, the product SAP Advanced Planning & Optimization (SAP APO) has the product versions APO 1.1, 2.0A, 3.0A, 3.1.

2005/Q2


19


BIT400

Figure 15: Products and Software Components

In the SLD, the relationship between the product version and the software component versions is represented by an independent object known as a software feature. This enables you to represent very complex products.

Displaying Products and Software Components in the SLDTo display the products and software components along with their versions in the System Landscape Directory, choose Software Catalog from the SLD initial screen.

Figure 16: Example of a Product and a Software Component

20


2005/Q2

BIT400


You can import SAP products and SAP software components into the SLD. You generally import them when you initially install an XI system; if you need to import them at a later date, you can find updates on SAP Service Marketplace, which you can then import into the SLD. If you use non-SAP software components and products, you need to manually create these in the SLD.

External Interfaces of Software ComponentsEach software component provides programs for particular functions. Generally, software components have external interfaces to enable them to communicate with other software components. These can be both inbound and outbound interfaces.

Figure 17: Software Component with External Interfaces

2005/Q2


21


BIT400

Examples of SAP inbound interfaces are: BAPIs and remote-enabled function modules File interfaces Inbound IDoc interfaces XML interfaces (Web AS 6.20 or higher) Java or ABAP inbound proxies (Web AS 6.20 or higher and integration scenarios that were implemented for SAP Exchange Infrastructure) Web service

Outbound interfaces cannot all be described by one object; they often exist implicitly. Examples of SAP outbound interfaces are: File interfaces in the form of a program that creates a file IDoc outbound interfaces in the form of a program that creates an IDoc RFC outbound interfaces in the form of a program that calls a remote function call by using CALL FUNCTION...DESTINATION XML interfaces in the form of a program that sends an XML message by using HTTP Java or ABAP outbound proxies (Web AS 6.20 or higher and integration scenarios that were implemented for SAP Exchange Infrastructure)

Software Components and Interfaces in the Integration RepositoryDetailed information about the external interfaces of a software component are stored in the Integration Repository. As a rule, the software components are first imported from the SLD into the Integration Repository, and namespaces are then created for the interfaces. A namespace semantically groups objects, in a similar way to ABAP packages (previously called development classes) or to Java packages. Namespaces must be globally unique, and not just for software components; they are unique identifiers for an interface.

22


2005/Q2

BIT400


You can create external interfaces by using one of the following methods: Message Interface: You create the interfaces in the Integration Repository. External Definitions: You can import interfaces, whose structures have been defined using an XML schema or DTD, into the Integration Repository. Imported (SAP) Objects: You can import RFC signatures or IDoc types from a SAP system by using an RFC. In doing so, you generate an XML schema. This type of import can be permitted for every software component. In this case, connection data to a SAP system that contains the current RFC signatures or IDoc types, is defined for the software component.

Figure 18: SLD Interface for the Integration Repository

Message InterfacesThe following objects are created for message interfaces in the Integration Repository. Using attributes, the message interface describes whether the interface is an inbound or outbound interface, and whether it is synchronous or asynchronous. A message type is referenced for the exact message structure. The message type describes the message structure. It references a complex data type. A message type can be used for both outbound and inbound message interfaces.

2005/Q2


23


BIT400

Data types define simple or complex XML data structures. There are elementary data types that define properties for elementary fields. Multiple fields can be grouped together in a structured data type and describe the structure of an XML document node. Elements belonging to a complex data type can be typed with an elementary XML type, an elementary data type, or with a complex data type. This allows you to create nested data types. An occurrence is specified for each element. Normally, a complex data type is created for the structure of the entire document. The fields of this structure reference complex data types, which correspond to line types. The number of occurrences of the node permitted at runtime (cardinality) is also determined.

Figure 19: Repository: Message Interface, Message Type and Data Types

Example: Interface with Nested StructureIn the example scenario, the sender outbound interface is nested.

24


2005/Q2

BIT400


Figure 20: Data Type and Message Type

The following objects have been created in the Integration Repository for the software component SC_BIT400_A: A message interface of type outbound and asynchronous that references the message type MT_Material A message type MT_Material that references the nested data type DT_Material An elementary data type DT_Material. A simply-structured data type DT_MaterialDescription that contains the two string-like fields Language and Description A nested data type that contains required entry fields as well as an optional field and a structured element defined using the data type DT_MaterialDescription. This structured element is optional since the attribute MinOccurs = 0; the number of occurrences is not restricted since the attribute MaxOccurs = unbounded. At runtime, the corresponding message might look as follows as an XML document:

2005/Q2


25


BIT400

Figure 21: XML Structure of the Source Document

Example: Message with Multiple NodesThe receiver inbound interface in the example scenario consists of a message with two independent node types. Each node is optional and can have an unlimited number of occurrences at runtime.

26


2005/Q2

BIT400


Figure 22: Message Type with Multiple Nodes

Figure 23: XML Structure of the Target Document

2005/Q2


27


BIT400

28


2005/Q2

BIT400


Exercise 1: Software Components and ProductsExercise ObjectivesAfter completing this exercise, you will be able to: Check component information in the SLD Display software components and their interfaces in the Integration Repository

Business ExampleYou want to use standard interfaces from software components for an integrated scenario. A representation of the most important software component characteristics and their corresponding interfaces is a prerequisite for this.

Task 1: Component Information in the System Landscape DirectoryCheck the component information in the System Landscape Directory (SLD). 1. 2. Log on to the SLD. Use your user BIT400-## from the Integration Server and your password. Is the product SAP APO in the SLD? How many product versions are there? Which software components belong to product version 3.1? Choose Software Catalog from the SLD initial screen.

Continued on next page

2005/Q2


29


BIT400

3.

For the purposes of this course, we have created products and software components that are not delivered. What software component versions does the product Product_BIT400 have?

Task 2:In the Integration Repository, search for the interfaces configured for the software components SAP_APPL Version 4.7, SC_BIT400_A Version 1.0 and SC_BIT400_B Version 1.0. 1. 2. Log on to the Integration Repository. Use your user BIT400-## from the Integration Server and your password. Search for the software components listed above. Check which interfaces have been saved for each of these software components. In doing so, take all types of interfaces into account. Examine the message interface MI_Material_outb of the software component SC_BIT400_A, and navigate to the message type. How many nodes does the message type have? Are there any optional nodes? Are there nodes that can have multiple occurrences in the message? Which data types are referenced? Examine the message interface MI_Material_inb of the software component SC_BIT400_B, and navigate to the message type. How many nodes does the message type have? Are there any optional nodes? Are there nodes that can have multiple occurrences in the message? Which data types are referenced?

3.

4.

30


2005/Q2

BIT400


Solution 1: Software Components and ProductsTask 1: Component Information in the System Landscape DirectoryCheck the component information in the System Landscape Directory (SLD). 1. Log on to the SLD. Use your user BIT400-## from the Integration Server and your password. a) Log on to the Integration Server (ABAP). Choose Exchange Infrastructure Start Integration Builder by double clicking it, or call transaction SXMB_IFR. Choose System Landscape Directory from the Integration Builder initial screen, and log on to the SLD using your user and password.

2.

Is the product SAP APO in the SLD? How many product versions are there? Which software components belong to product version 3.1? Choose Software Catalog from the SLD initial screen. a) Navigate to the initial screen of the System Landscape Directory. Choose Software Catalog. Search for the product SAP APO. It has the product versions 2.0A, 3.0A, and 3.1. Choose 3.1. The system displays a list with the software component versions SAP ABA 4.6D, SAP APO 3.1, SAP BASIS 4.6, SAP BW 2.1C, and SAP GUI FOR WINDOWS 6.10.

3.

For the purposes of this course, we have created products and software components that are not delivered. What software component versions does the product Product_BIT400 have? Answer: In the training system, the product Product_BIT400 has the software components SC_BIT400_A, SC_BIT400_B and SC_BIT400_MAPPING, all of which are version 1.0.


2005/Q2


31


BIT400

Task 2:In the Integration Repository, search for the interfaces configured for the software components SAP_APPL Version 4.7, SC_BIT400_A Version 1.0 and SC_BIT400_B Version 1.0. 1. Log on to the Integration Repository. Use your user BIT400-## from the Integration Server and your password. a) 2. Choose Integration Repository from the Integration Builder initial screen. This starts Java Web Start. Log on using your user and password.

Search for the software components listed above. Check which interfaces have been saved for each of these software components. In doing so, take all types of interfaces into account. a) Search for message interfaces. These are the interfaces that were created in the Integration Repository. This applies to new proxy interfaces, for example. Choose Software Component Version Namespace Interface Objects Message Interfaces. If you can expand the node Message Interfaces, it means that interfaces have been created. Double click on the name of an interface to display the detail view for that interface. Search for imported interfaces (for example, WSDL, XSD or DTD). Choose Software Component Version Namespace Interface Objects External Definitions. If you can expand the node External Definitions, it means that interfaces have been created. Double click on the name of an interface to display the detail view for that interface. Search for imported SAP interfaces (for example, RFC, IDoc). Generally, you restrict the search to ABAP-based software components. Choose Software Component Version Imported Objects RFCs when searching for RFC interfaces. Software Component Version Imported Objects IDoc, for IDoc interfaces. Double click on the name of an interface to display the detail view for that interface.

b)

c)


32


2005/Q2

BIT400


3.

Examine the message interface MI_Material_outb of the software component SC_BIT400_A, and navigate to the message type. How many nodes does the message type have? Are there any optional nodes? Are there nodes that can have multiple occurrences in the message? Which data types are referenced? a) b) c) d) e) Navigate to the detail view of the message interface. Double click on the message type MT_Material to navigate to the detail view. The message type has a main node with one sub-node. There are no optional nodes. The sub-node can have multiple occurrences. This is indicated by the occurrence 1..unbounded. You can determine more about the message structure from the Data Type Used field. Double click on the name of the data type DT_Material to navigate to the detail view. The simple data type DT_MaterialID is used to type the field MaterialID; the structured data type DT_MaterialDescription is used to type the sub-node.

4.

Examine the message interface MI_Material_inb of the software component SC_BIT400_B, and navigate to the message type. How many nodes does the message type have? Are there any optional nodes? Are there nodes that can have multiple occurrences in the message? Which data types are referenced? a) b) c) d) Navigate to the detail view of the message interface. Double click on the message type MT_Materials_B to navigate to the detail view. The message type has a main node with two sub-nodes. Both sub-nodes are optional nodes and can have multiple occurrences. This is indicated by the occurrence 0..unbounded. You can determine more about the message structure from the Data Type Used field. Double click on the name of the data type DT_MessageMaterials_B to navigate to the detail view. The structured data type DT_Material_B is used to type the sub-node Material; the structured data type DT_MaterialDescription_B is used to type the sub-node Description.

2005/Q2


33


BIT400

Lesson SummaryYou should now be able to: Display SAP products and software components in the SLD Display software components and check for any interfaces in the Integration Repository Manually create products and software components in the SLD

34


2005/Q2

BIT400

Lesson: Implementing Technical Systems

Lesson: Implementing Technical SystemsLesson OverviewThis lesson describes how to implement technical systems in the System Landscape Directory.

Lesson ObjectivesAfter completing this lesson, you will be able to: Display technical systems in the SLD and check their attributes Describe how SAP systems register with the SLD Manually create a technical system in the SLD and assign products and software components

Business ExampleYou have a heterogeneous system landscape with multiple servers and various different software components. To implement a business process in this system landscape, you need to analyze the technical properties of the various systems and the application components that are installed.

The System Landscape in the SLDIn addition to information about products and software components, you can also enter technical and business systems in the SLD. There are various different types of technical systems. The type of technical system determines exactly which attributes you must enter. To view or check the technical systems in the SLD, choose Technical Landscape from the SLD initial screen. The system navigates to a screen where you can select a system type. It then displays a list of technical systems for the system type you selected.

2005/Q2


35


BIT400

Figure 24: SLD: Technical Systems

SAP Systems (ABAP)As you do for all technical systems, you need to maintain specific attributes for ABAP-based SAP systems, for example, host name, system ID, and message server. . The technical system is assigned the software components that have been installed on the server. A distinctive feature of ABAP-based SAP systems, is that in addition to the typical attributes, you can also have numerous clients. These clients can be viewed as separate systems, from a business perspective.

36


2005/Q2

BIT400


Figure 25: Example: SAP System (Technical View)

The products and software components are assigned at system level, because development objects in SAP systems are not client-specific.

Registering SAP Systems (ABAP)A prerequisite for registering systems as technical systems in the SLD is that you activate the data supplier bridge in the SLD. When you configure the data supplier bridge, you must specify which RFC gateway it is to be registered on.

2005/Q2


37


BIT400

Figure 26: Data Supplier Bridge

You must activate a data supplier in the back-end system. In ABAP-based SAP systems, you can configure and start this data supplier by calling transaction RZ70. You can use various parameters to control which data you want to gather. Normally, you generate an RFC destination according to a naming convention, in transaction RZ70. Gathered data is transferred across the RFC connection and the gateway to the data supplier bridge, and is then imported into the SLD.

38


2005/Q2

BIT400


Figure 27: Data Supplier for SAP Systems (ABAP)

Alternatively, you can also transfer system data to the SLD by means of a CCMS agent.

Figure 28: Configuring the Data Supplier (ABAP)

2005/Q2


39


BIT400

SAP Web AS Java Systems (J2EE)The Java component SLD data supplier must be deployed and started for the SAP Web AS Java server, (previously called SAP J2EE engine). The parameters for the SLD data provider are passed to this J2EE service (using the Visual Administrator). J2EE server data such as host, installed software components, and so on, is refreshed every time the J2EE machine is restarted, and is imported into the SLD using the data supplier bridge.

Registering SAP Systems (J2EE)

Figure 29: Data Supplier for SAP Web AS Java Systems (J2EE)

The connection parameters for the SLD bridge that are needed to register the SAP Web AS Java system are stored as either RFC data or HTTP connection data in the SLD Data Supplier Service.

Example of a Technical System LandscapeThe system landscape for the examples and exercises is illustrated in the following graphic.

40


2005/Q2

BIT400


Figure 30: Technical System Landscape of the Example Scenario

The system landscape consists of two business systems, which act as application systems, and a client, which is configured as the Integration Server. The systems will exchange data using the SAP Exchange Infrastructure. The network connections and communication channels must therefore be configured at the same time as the system landscape.

2005/Q2


41


BIT400

42


2005/Q2

BIT400


Exercise 2: Implementing Technical SystemsExercise ObjectivesAfter completing this exercise, you will be able to: Manually create and examine technical systems in the SLD Examine the configuration with respect to registering systems

Business ExampleImplementing the server landscape is the basis for integration using a message server.

Task: Creating a Technical System in the System Landscape DirectoryCreate two technical systems ,TS_BIT400_##_A and TS_BIT400_##_B, both of type Third-Party, in the SLD. 1. 2. Log on to the SLD. Use your user BIT400-## from the Integration Server and your password. Create a new technical system of type Third-Party with the name TS_BIT400_##_A. The host name should be bit400host##a. Assign this technical system the software component SC_BIT400_A, version 1.0 of the product Product_BIT400 as an installed software component. Create a new technical system of type Third-Party with the name TS_BIT400_##_B. The host name should be bit400host##b. Assign this technical system the software component SC_BIT400_B, version 1.0 of the product Product_BIT400 as an installed software component.

3.

2005/Q2


43


BIT400

Solution 2: Implementing Technical SystemsTask: Creating a Technical System in the System Landscape DirectoryCreate two technical systems ,TS_BIT400_##_A and TS_BIT400_##_B, both of type Third-Party, in the SLD. 1. Log on to the SLD. Use your user BIT400-## from the Integration Server and your password. a) b) 2. Log on to the System Landscape Directory, for example, by calling transaction SXMB_IFR. In the web browser, choose the link to the SLD.

Create a new technical system of type Third-Party with the name TS_BIT400_##_A. The host name should be bit400host##a. Assign this technical system the software component SC_BIT400_A, version 1.0 of the product Product_BIT400 as an installed software component. a) On the System Landscape Directory initial screen, choose Technical Landscape. Choose New Technical System... to create a new technical system. Choose Third-Party as the system type and then choose Next. Enter the following: System Name TS_BIT400_##_A and Host Name bit400host##a. Select the product Product_BIT400 from the list and then choose Add. Ensure that only the software component SC_BIT400_A is selected. Finally, choose Finish.

b)

c) 3.

Create a new technical system of type Third-Party with the name TS_BIT400_##_B. The host name should be bit400host##b. Assign this technical system the software component SC_BIT400_B, version 1.0 of the product Product_BIT400 as an installed software component. a) On the System Landscape Directory initial screen, choose Technical Landscape. Choose New Technical System... to create a new technical system. Choose Third-Party as the system type and then choose Next. Enter the following: System Name TS_BIT400_##_B and Host Name bit400host##b. Select the product Product_BIT400 from the list and then choose Add. Ensure that only the software component SC_BIT400_B is selected. Finally, choose Finish.

b)

c)

44


2005/Q2

BIT400


Lesson SummaryYou should now be able to: Display technical systems in the SLD and check their attributes Describe how SAP systems register with the SLD Manually create a technical system in the SLD and assign products and software components

2005/Q2


45


BIT400

Lesson: Business Systems and the Integration DirectoryLesson OverviewThis lesson explains why technical systems are assigned a name, the business system, which is used during configuration. You will be shown how to create business systems in the SLD, and how to import them into the Integration Directory. You will also be introduced to important enhancements, for example, changes to communication channels (known as end points in XI 2.0) in the Integration Directory.

Lesson ObjectivesAfter completing this lesson, you will be able to: Create a business system in the SLD and assign it a technical system Import a business system into the Integration Directory

Business ExampleYou have a complex system landscape with multiple servers and complex business processes. You want to be able to configure your business processes in such a way that you can make technical changes to a server without having to make any changes to the configuration of your business processes. Systems should therefore be given logical names, which are used for process configuration.

Assigning Business Systems and Analyzing Business ProcessesTo implement the business processes in a distributed system landscape, you must assign a business system name to each of the technical systems. The business system describes the semantics of a system (or a client in an SAP system). To implement the business processes, you must know which software components are available on which business systems. Each business system must be assigned a technical system, at configuration time at the latest.

46


2005/Q2

BIT400

Lesson: Business Systems and the Integration Directory

Figure 31: Assigning Business Systems

When you implement a business process in a distributed system landscape, you determine the business system in which the particular process steps will run and which software component will execute them. If the business system changes between two consecutive process steps, then the sender software component must provide all the data required for the subsequent process step by means of an outbound interface. This data is sent to the receiver business system, where it is processed using an inbound interface. Therefore, each time data is transferred between two systems you must identify the sender outbound interface and the receiver inbound interface. If the systems are integrated by means of SAP Exchange Infrastructure, the document is converted from the format that it is sent in into an XI-XML document. Within SAP Exchange Infrastructure, the document structure is mapped to the structure of the inbound interface (structure and value mapping) and is converted to the format of the target system. To check the business systems in the SLD, choose Business Landscape from the SLD initial screen. Select a system type. The system displays a list of business systems for the system type you selected.

2005/Q2


47


BIT400

Figure 32: SLD: Business Systems

To create a business system (BS), proceed as follows in the SLD: Navigate to the list of business systems (Business Landscape under System Landscape) Choose New Business System... to create a new system Enter the name of the new BS Select the type of business system (for example, Third-Party) Enter the technical system that the BS is based on Optional: Enter the logical system name if Application Link Enabling (ALE) is to be used Specify which products and SWCV you want to make available to the BS Specify the assigned Integration Server

You then need to assign the business system in the Integration Directory. To do this, go to the Objects tab page and choose Assign Business System... from the context menu of the Service Without Party Business System node. The system then displays a list of the unassigned business systems in the SLD. When you have made your

48


2005/Q2

BIT400


selection, you can specify whether you want the system to generate communication channels for the business systems. Once these are generated, you need to enter exact parameters and customize the information for each of the business systems. Hint: If necessary, clear the SLD cache in the Integration Directory by choosing Environment Clear SLD Data Cache.

Services for Business Systems in the Integration DirectoryIn the configuration in the Integration Builder, business systems are used to define the sender and receiver in a scenario. For this reason, the input help in the Integration Directory has an SLD interface, which lists all the business systems that are maintained in the SLD.

Figure 33: SLD Interface for the Integration Directory

2005/Q2


49


BIT400

Figure 34: Communication Channels

The main tasks involved in creating a communication channel are: Select the service Specify which service you want to create the communication channel for, for example, the business system. Specify the name Enter the name of the communication channel; choose a name that is self-explanatory, for example, RFC_Sender. Select the adapter type Specify the connection details (for example, file adapter for file access) and whether it is sender or receiver. Select the Adapter Engine and the protocol In addition to the central Adapter Engine, you can also have other non-central Adapter Engines. You also need to enter details for the transport and message protocols (XI 2.0 or XI 3.0, NFS or FTP) Adapter-specific parameters You need to enter further details for each adapter: for file receiver, for example, the target directory.

50


2005/Q2

BIT400


Exercise 3: Business SystemExercise ObjectivesAfter completing this exercise, you will be able to: Create and display business systems in the SLD Import business systems into the Integration Directory

Business ExampleBusiness systems are the basis for configuring scenarios in the SAP Exchange Infrastructure.

Task 1:Create two business systems in the SLD. 1. Create a new business system of type Third-Party with the name BS_BIT400_##_A. Leave the field ALE Name initial. The software component SC_BIT400_A must be configured as an active component. You will configure this business system as a sender in later exercises. Create a new business system of type Third-Party with the name BS_BIT400_##_B. Leave the field ALE Name initial. The software component SC_BIT400_B must be configured as an active component. You will configure this business system as a receiver in later exercises.

2.

Task 2:Import the two business systems you created, BS_BIT400_##_A and BS_BIT400_##_B, into the Integration Directory. System BS_BIT400_##_A is to act as a sender and communicate with the SAP Exchange Infrastructure using the HTTP adapter. A sender communication channel is not required for the HTTP adapter. System BS_BIT400_##_B is to act as a receiver and communicate with the SAP Exchange Infrastructure using the file adapter. You need to create a receiver communication channel for this. 1. Log on to the Integration Directory. Enter the user BIT400-## and your password.


2005/Q2


51


BIT400

2.

Switch from the Scenarios tab page to the Objects tab page. Assign the business system BS_BIT400_##_A to Service Without Party of type Business System. To do this, use the wizard by choosing Service Without Party Business System and calling the context menu. Leave the Party field empty and make sure the Create Communication Channels Automatically checkbox is not selected. Assign the business system BS_BIT400_##_B to Service Without Party of type Business System. To do this, use the wizard by choosing Service Without Party Business System and calling the context menu. Leave the Party field empty and make sure the Create Communication Channels Automatically checkbox is not selected. Create a communication channel File_Receiver_##_B for the business system BS_BIT400_##_B. Use the file adapter for the communication. Use the template BIT400_File_Receiver_Template. In the Target Directory field, replace ## in //localhost/xitrans/group## with your group number. Activate the new objects you created in the Integration Directory.

3.

4.

5.

52


2005/Q2

BIT400


Solution 3: Business SystemTask 1:Create two business systems in the SLD. 1. Create a new business system of type Third-Party with the name BS_BIT400_##_A. Leave the field ALE Name initial. The software component SC_BIT400_A must be configured as an active component. You will configure this business system as a sender in later exercises. a) Choose Business Landscape on the System Landscape Directory initial screen. Choose New Business System... to create a new business system. Enter the name BS_BIT400_##_A for your business system. Select the Third-Party radio button and then choose Next. Select the technical system TS_BIT400_##_A that you just created and choose Next. Select the product Product_BIT400 and choose Next. Select the Integration Server and exit by choosing Finish.

2.

Create a new business system of type Third-Party with the name BS_BIT400_##_B. Leave the field ALE Name initial. The software component SC_BIT400_B must be configured as an active component. You will configure this business system as a receiver in later exercises. a) On the System Landscape Directory initial screen, choose XI Landscape. Choose New Business System... to create a new business system. Enter the name BS_BIT400_##_B for your business system. Select the Third-Party radio button and then choose Next. Select the technical system TS_BIT400_##_B that you just created and choose Next. Select the product Product_BIT400 and choose Next. Select the Integration Server and exit by choosing Finish.


2005/Q2


53


BIT400

Task 2:Import the two business systems you created, BS_BIT400_##_A and BS_BIT400_##_B, into the Integration Directory. System BS_BIT400_##_A is to act as a sender and communicate with the SAP Exchange Infrastructure using the HTTP adapter. A sender communication channel is not required for the HTTP adapter. System BS_BIT400_##_B is to act as a receiver and communicate with the SAP Exchange Infrastructure using the file adapter. You need to create a receiver communication channel for this. 1. Log on to the Integration Directory. Enter the user BIT400-## and your password. a) 2. Choose Integration Directory on the initial screen for tools. Switch from the Scenarios tab page to the Objects tab page. Assign the business system BS_BIT400_##_A to Service Without Party of type Business System. To do this, use the wizard by choosing Service Without Party Business System and calling the context menu. Leave the Party field empty and make sure the Create Communication Channels Automatically checkbox is not selected. a) b) Switch from the Scenarios tab page to the Objects tab page. To start the wizard for assigning business systems, choose Service Without Party Business System and then choose Assign Business System in the context menu. Choose Continue. Leave the Party field empty, and choose Continue. Select the business system BS_BIT400_##_A from the list. If this business system does not appear in the list, ask your instructor to delete the cache for SLD data. Deselect the checkbox Create Communication Channels Automatically and choose Finish.

c) d) e)


54


2005/Q2

BIT400


3.

Assign the business system BS_BIT400_##_B to Service Without Party of type Business System. To do this, use the wizard by choosing Service Without Party Business System and calling the context menu. Leave the Party field empty and make sure the Create Communication Channels Automatically checkbox is not selected. a) b) c) d) Start the wizard for assigning business systems, by choosing Service Without Party Business System and then calling the context menu. Choose Continue. Leave the Party field empty, and choose Continue. Select the business system BS_BIT400_##_A from the list. If this business system does not appear in the list, ask your instructor to delete the cache for SLD data. Deselect the checkbox Create Communication Channels Automatically and choose Finish.

4.

Create a communication channel File_Receiver_##_B for the business system BS_BIT400_##_B. Use the file adapter for the communication. Use the template BIT400_File_Receiver_Template. In the Target Directory field, replace ## in //localhost/xitrans/group## with your group number. a) Create a communication channel by choosing Service Without Party Business System BS_BIT400_##_B Communication Channel and then choosing New from the context menu. Enter your communication channel File_Receiver_##_B in the Communication Channel field and choose Create. Choose Communication Channel Import Template.In the Target Directory field, replace ## in //localhost/xitrans/group## with your group number. Save the communication channel. Switch from the Objects tab page to the Change Lists tab page. Choose Standard Change List and activate all objects by calling the context menu and choosing Activate. Your change list contains three objects, which are selected. Choose Activate to confirm the activation.

b)

c) 5. a) b)

Activate the new objects you created in the Integration Directory.

2005/Q2


55


BIT400

Lesson SummaryYou should now be able to: Create a business system in the SLD and assign it a technical system Import a business system into the Integration Directory

56


2005/Q2

BIT400

Unit Summary

Unit SummaryYou should now be able to: Display SAP products and software components in the SLD Display software components and check for any interfaces in the Integration Repository Manually create products and software components in the SLD Display technical systems in the SLD and check their attributes Describe how SAP systems register with the SLD Manually create a technical system in the SLD and assign products and software components Create a business system in the SLD and assign it a technical system Import a business system into the Integration Directory

2005/Q2


57

Unit Summary

BIT400

58


2005/Q2

Unit 3SAP XI Pipeline Example for an Asynchronous ScenarioUnit OverviewThis unit explains message processing within the Integration Server. It is unimportant at this stage how the back-end systems are connected to SAP Exchange Infrastructure. Message processing within the runtime environment is the same for all messages, regardless of the connection method. This unit explains which configuration settings you must make for the receiver determination, and how you set up a mapping from the sender outbound interface to the receiver inbound interface.

Unit ObjectivesAfter completing this unit, you will be able to: Describe the asynchronous example scenario Describe the design view of the scenario and check it in the Integration Repository by using an integration scenario Describe the configuration view of the scenario and generate it using a wizard Describe how an XI XML message is structured Make the relevant settings for logical routing in the Integration Directory Check the runtime procedure by using the monitor for processed XML messages and understand the logical routing steps in the XML document Create an interface mapping in the Integration Repository Create a message mapping by using the graphical mapping editor Describe the concept of target-field mappings Describe the challenges created by structure mappings

Unit ContentsLesson: Introducing the Scenario.................................................. 61

2005/Q2


59

Unit 3: SAP XI Pipeline Example for an Asynchronous Scenario

BIT400

Exercise 4: Checking an Integration Scenario at Design Time, Configuration Time, and Runtime ............................................. 71 Lesson: XI Messages: Structure and Transfer to the Pipeline................. 79 Exercise 5: Checking the Message Monitor ................................. 85 Lesson: Logical Routing ............................................................ 88 Exercise 6: Logical Routing .................................................... 95 Lesson: Mapping and Technical Routing ........................................ 102 Exercise 7: Interface Mapping ................................................ 111 Lesson: Message Mapping ........................................................ 115 Exercise 8: Creating Message Mappings ................................... 125

60


2005/Q2

BIT400

Lesson: Introducing the Scenario

Lesson: Introducing the ScenarioLesson OverviewThis lesson introduces the example scenario.

Lesson ObjectivesAfter completing this lesson, you will be able to: Describe the asynchronous example scenario Describe the design view of the scenario and check it in the Integration Repository by using an integration scenario Describe the configuration view of the scenario and generate it using a wizard

Business ExampleA third-party system is responsible for maintaining material master data. It has an outbound interface that is used to distribute material master data. In this training course, this is simulated by an HTTP client that is used to manually create a message for a particular material. The chosen procedure for distributing the master data will not be tied to a specific technology and the material master data will be sent to all dependent systems. In the first step, an XML file is created for another third-party system. The structure of the message that is sent differs from the structure of the file expected by the target system. To solve this problem, the structure will be mapped in SAP Exchange Infrastructure (SAP XI). A further receiver will be added to the scenario later on.

Asynchronous ScenarioThe work method of SAP XI is first explained by means of an asynchronous scenario. To begin with, the lesson focuses on the processing and configuration steps within SAP XI. SAP XI receives a document in a special XML format, identifies the receiver or receivers, and sends each receiver system one document in a special XML format. The data format that the sender system uses to transfer the document to SAP XI is irrelevant. There are various adapters available that can convert the document to the XML format that SAP XI expects. The same applies to the receiver system. If necessary, adapters can also convert the document to a format that the receiver supports. A document is always processed in the same way within SAP XI.

2005/Q2


61


BIT400

Figure 35: Asynchronous Scenario

This will be illustrated by means of a simplified material-master-data-distribution example with demonstrations and exercises. The sender system is simulated by an HTTP client. A file is created for a virtual receiver system.

Design ViewThe term design view is often used in the context of SAP XI. Each process that is to be implemented in a system landscape must have particular functions in the form of programs. Various programs that include functions that belong together are grouped together either in an application component or in a software component. In the design phase, the inbound and outbound interfaces of the software components used are analyzed and saved in the Integration Repository. If applicable, you can create mapping rules for mapping an outbound interface to an inbound interface. If, as part of a business process in a distributed system landscape, a software component of one business system is to communicate with a software component of another business system, then the following prerequisites must be met: The sender software component must have an outbound interface The receiver software component must have an inbound interface

62


2005/Q2

BIT400


Figure 36: Design View

The following objects must be created in the Integration Repository during the design phase: All the software components used are entered in the SLD and then imported into the Integration Repository. The inbound and outbound interfaces used for each software component are available in the Integration Repository. A mapping rule from an outbound interface to an inbound interface is defined for each required interface. If the structure of the outbound interface is different to that of the inbound interface, you need to create a mapping program. To get a better overview of which outbound interface from which business process is assigned to which inbound interface, you have the option of creating an integration scenario in the Integration Repository.

2005/Q2


63


BIT400

Figure 37: Integration Scenario

In an integration scenario in the Integration Repository, you create application components; for example, you maintain master data in one system and then want this data to be distributed from there to all dependent systems. You create an application component 'Distribute Master Data'. At configuration time, the application component is assigned a system. A different application component receives and posts the master data. At configuration time, this can cover multiple systems. For this reason, you can assign multiple systems to an application component at configuration time. Therefore, you do not have to know the exact number of systems in a system landscape when you design a scenario in the Integration Repository at design time. This information is more important for the software components and interfaces, in other words, the development objects. You can create actions for each application component. You can assign inbound and outbound interfaces to the actions. In an integration scenario you can then show which outbound interface is to be assigned to which inbound interface and which mapping program is to be used to do so. All objects in the design view can be shipped by the vendor of a software component. You can create any missing objects in your Integration Repository. To avoid naming conflicts for object names in later shipments, you save your objects in a separate namespace. At runtime, it is the task of SAP XI to receive the data from the outbound interface, to then convert it to the data format that the inbound interface expects, and finally to transfer it to the inbound interface of the target system. Besides the information about the software components and their interfaces, you also require information about the actual system landscape for SAP XI to complete its task.

64


2005/Q2

BIT400


Configuration ViewThe emphasis of the configuration view is on the implementation of the scenario in a real system landscape. The configuration view determines which system and outbound interface is to be used to send a message to a different system and inbound interface. You specify the sender and receiver as business systems. In the System Landscape Directory (SLD), each business system is assigned a technical system.

Figure 38: Configuration View

For this reason, the configuration view slides not only contain the inbound or outbound interfaces, but also the systems from which a message is to be sent or in which a message is to be received. You make the settings for the configuration view in the Integration Directory. These settings cannot be shipped by SAP since they are specific to customers' system landscapes.

RuntimeOnce a document has been transferred to the Integration Server in a special XML format, it is processed in the pipeline. The business system and the receiver inbound interface are determined during logical routing. If more than one receiver is determined during logical routing, the inbound message is duplicated in a message split. The structure of the sender document is converted to the structure of the receiver document by a mapping. Technical routing, on the other hand, determines how the receiver can be reached. If applicable, the relevant adapter is then called.

2005/Q2


65


BIT400

Figure 39: Runtime Procedure: Pipeline

The Integration Engine is the runtime environment of SAP XI and is used to exchange messages according to the business processes that you have configured. You create your configurations by using the Integration Builder: Directory (Configuration). The receiver of an XML message is determined in logical and technical routing, which takes place during inbound processing. This receiver determination determines how processing will continue.

Figure 40: Runtime Procedure: The Integration Server Pipeline

66


2005/Q2

BIT400


If no receiver is found, an error is displayed and processing is terminated. If only one receiver is found, the message is placed in the corresponding outbound queue for outbound processing. If more than one receiver is found, in the case of asynchronous quality of service, processing of the message is branched. A new message with a new message ID is created from the original message for each interface or receiver pair in the receiver list that was determined during logical routing. To ensure that this message branch remains clear, the message ID of the original message is saved with each new message. If the quality of service is synchronous, then an error occurs if multiple receivers are determined. During the mapping phase, you also have the option of modifying the content of the message by using an interface mapping/message mapping, which you previously saved in the Integration Repository.

MonitoringTo start the XI monitor, choose Exchange Infrastructure Monitoring Integration Engine - Monitoring. On the subsequent screen, choose Integration Engine Monitoring Monitor for Processed XML Messages.

Figure 41: Transaction SXI_MONITOR

On the selection screen that is then displayed you can restrict the selection of messages to be displayed. Note that there is also a second tab page that contains additional selection criteria.

2005/Q2


67


BIT400

Figure 42: Message List

Choose Execute to display a list of messages that satisfy your selection criteria. To display more details about a particular message, select the relevant line and choose Display.

Figure 43: Detail View of a Message

68


2005/Q2

BIT400


The screen is divided into three areas: The pipeline steps that have been executed are displayed in a tree-format on the left-hand side. The right-hand side shows two windows that contain detailed information about the message. You can switch between these windows by choosing Display Window 1 or Display Window 2, as applicable.

2005/Q2


69


BIT400

70


2005/Q2

BIT400


Exercise 4: Checking an Integration Scenario at Design Time, Configuration Time, and RuntimeExercise ObjectivesAfter completing this exercise, you will be able to: Describe the design view of the scenario and use an integration scenario in the Integration Repository to check it

Business ExampleYou want to simulate the distribution of material master data. Material master data is created as an XML document in system A and then sent to SAP XI by using HTTP and the HTTP adapter. In SAP XI, the document is mapped to the structure of the inbound interface of target system B. This system expects to receive an XML file, and it is therefore connected to the file adapter.

Task 1:In the Integration Repository, analyze integration scenario BIT400_Scenario1, which distributes material master data. Find out which software components and interfaces are involved, and which mapping is used. 1. 2. Log on to the Integration Server. From the menu, start the Integration Builder and log on to the Integration Repository. Look at integration scenarioBIT400_Scenario1 for software component SC_BIT400_MAPPING in namespace urn:education.sap.com:BIT400:Mapping. What actions does this scenario have? How many application components are involved? What is the name of the outbound interface of the sender application component? What is the name of the inbound interface of the receiver application component? Which mapping program is used?


2005/Q2


71


BIT400

Task 2:In the Integration Directory, configure the configuration scenario BIT400_## for integration scenario BIT400_Scenario1, which you analyzed in task 1. Assign business system BS_BIT400_##_A as the sender and BS_BIT400_##_B as the receiver. Use the communication channel for the receiver that was created on the basis of the template BIT400_File_Receiver_Template. 1. 2. Log on to the Integration Directory and navigate to the view for configuration scenarios. Start the wizard for generating a configuration scenario from an integration scenario. Select integration scenario BIT400_Scenario1 and use it as a template to create a configuration scenario BIT400_##. Check the entries in all four configuration steps in the wizard, and correct any details, if applicable.

3.

Task 3:Test the scenario and display the corresponding message in the XI monitor. Which pipeline steps were executed? 1. On the Integration Builder start page, choose Additional Information and then Tools for BIT400. Start the HTTP client. This simulates an application that generates an XML document for a material master and sends it to the XI pipeline using the HTTP adapter. If necessary, correct the details for the sender service so that they match your scenario configuration. Change the material number in your document to BIT400_## and send the XML document. Analyze the message in the XI monitor (transaction SXMB_MONI). Which pipeline steps has the message passed through?

2. 3.

72


2005/Q2

BIT400


Solution 4: Checking an Integration Scenario at Design Time, Configuration Time, and RuntimeTask 1:In the Integration Repository, analyze integration scenario BIT400_Scenario1, which distributes material master data. Find out which software components and interfaces are involved, and which mapping is used. 1. Log on to the Integration Server. From the menu, start the Integration Builder and log on to the Integration Repository. a) b) Log on to client 800 in the training system. Choose Exchange Infrastructure: Integration Builder Start Integration Builder or call transaction SXMB_IFR. Choose Repository (Design). The user name and password are the same as those required to log on to the Integration Server.

2.

Look at integration scenarioBIT400_Scenario1 for software component SC_BIT400_MAPPING in namespace urn:education.sap.com:BIT400:Mapping. What actions does this scenario have? How many application components are involved? What


2005/Q2


73


BIT400

is the name of the outbound interface of the sender application component? What is the name of the inbound interface of the receiver application component? Which mapping program is used? a) Integration scenario BIT400_Scenario1 is located under node SC_BIT400_MAPPING SC_BIT400_MAPPING, 1.0 of sap.education urn:education.sap.com:BIT400:Mapping Integration Scenarios & Integration Processes Integration Scenarios. Double click to navigate to the graphical view. The scenario has the actions 'Replicate Material Master Data' and 'Create or Change Material'. Two application components are involved. Double click the action before you send the message to display the possible outbound interfaces of the sender system. Two message interfaces are saved there as outbound interfaces: MI_Material_outb and MI_Materials_outb. Double click the action 'Create or Change Material' to display the possible inbound interfaces of the receiver system. One message interface is saved there as an inbound interface: MI_Materials_inb. To display the outbound and inbound interfaces used in this scenario, double click the connection line that symbolizes the sending of a message. The Assign Interfaces tab page contains a list of the interfaces used in this scenario. The interface mapping IM_MaterialA_MaterialsB is entered on tab page Assign Mapping.

b) c) d)

e)

f)

Task 2:In the Integration Directory, configure the configuration scenario BIT400_## for integration scenario BIT400_Scenario1, which you analyzed in task 1. Assign business system BS_BIT400_##_A as the sender and BS_BIT400_##_B as the receiver. Use the communication channel for the receiver that was created on the basis of the template BIT400_File_Receiver_Template. 1. Log on to the Integration Directory and navigate to the view for configuration scenarios. a) b) Log on to the Integration Directory with your user BIT400-## and your password. Navigate to the Scenarios tab page. Continued on next page

74


2005/Q2

BIT400


2.

Start the wizard for generating a configuration scenario from an integration scenario. Select integration scenario BIT400_Scenario1 and use it as a template to create a configuration scenario BIT400_##. a) b) c) d) Choose Tools Transfer Integration Scenario from Integration Repository... In Step 1: Select Integration Scenario, use the search help to select BIT400_Scenario1. Choose Continue. In Step 2: Create Configuration Scenario, change the name of the configuration scenario to BIT400_##. Choose Finish. Choose Close to access the wizard for assigning business systems.


2005/Q2


75


BIT400

3.

Check the entries in all four configuration steps in the wizard, and correct any details, if applicable. a) b) Step 1: Select Component View: Integration scenario BIT400_Scenario1 should be displayed. Step 2: Assign Services (for the sender): First, select the application component with the action Replicate Material Master Data. Next, choose Step 2: Assign Services. Assign a new service by using the icon with the green cross ( ). Select your business system BS_BIT400_##_A by using the search help and then choose Assign. Step 2: Assign Services (for the receiver): Now, select the application component with the action Create or Change Material. Next, choose Step 2: Assign Services. Assign a new service by using the icon with the green cross ( ). Select your business system BS_BIT400_##_B by using the search help and then choose Assign. Step 3: Configure Connections: On the Connections from the Service Assignment tab page, use the search help to select the communication channel File_Receiver_##_B for your business system BS_BIT400_##_B. Step 4: Generate: In the dialog box, choose Generation to generate the missing configuration objects. Choose Start and check the log. You can close the log without saving. Save your configuration in the integration scenario configurator (menu Settings Apply Settings and Save Configuration Scenario) and then close it. Scenario BIT400_## is now displayed and the objects it contains are highlighted. Activate your objects.

c)

d)

e) f) g)

h)

Task 3:Test the scenario and display the corresponding message in the XI monitor. Which pipeline steps were executed? 1. On the Integration Builder start page, choose Additional Information and then Tools for BIT400. Start the HTTP client. This simulates an application that generates an XML document for a material master and sends it to the XI pipeline


Documents

BIT400 - 2005-Q2 - Ltr - SAP Exchange Infrastructure