bit450 en col53 fv part ltr

BIT450BIT450 SAP Exchange Infrastructure

DevelopmentSAP NetWeaver

Date

Training Center

Instructors

Education Website

Participant HandbookCourse Version: 2005 Q3Course Duration: 2 Day(s)Material Number: 50072895

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

Copyright

Copyright 2005 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose withoutthe express permission of SAP AG. Additionally this publication and its contents are provided solelyfor your use, this publication and its contents may not be rented, transferred or sold without the expresspermission 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 softwarecomponents of other software vendors.

Trademarks

Microsoft, WINDOWS, NT, EXCEL, Word, PowerPoint and SQL Server areregistered 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 ofCitrix Systems, Inc.

HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C, World WideWeb 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 aretrademarks or registered trademarks of SAP AG in Germany and in several other countries allover the world. All other products mentioned are trademarks or registered trademarks of theirrespective companies.

Disclaimer

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

About This HandbookThis handbook is intended to complement the instructor-led presentation of thiscourse, 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 typographicconventions are also used.

Type Style Description

Example text Words or characters that appear on the screen. Theseinclude field names, screen titles, pushbuttons as well asmenu names, paths, and options.

Also used for cross-references to other documentationboth internal (in this documentation) and external (inother locations, such as SAPNet).

Example text Emphasized words or phrases in body text, titles ofgraphics, and tables

EXAMPLE TEXT Names of elements in the system. These include reportnames, program names, transaction codes, table names,and individual key words of a programming language,when surrounded by body text, for example SELECTand INCLUDE.

Example text Screen output. This includes file and directory namesand their paths, messages, names of variables andparameters, and passages of the source text of a program.

Example text Exact user entry. These are words and characters thatyou enter in the system exactly as they appear in thedocumentation.

Variable user entry. Pointed brackets indicate that youreplace these words and characters with appropriateentries.

25-08-2005 2005 SAP AG. All rights reserved. iii

About This Handbook BIT450

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 instructorspresentation.

iv 2005 SAP AG. All rights reserved. 25-08-2005

ContentsCourse Overview ...... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Course Goals.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .viiCourse Objectives .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Unit 1: Development Objects in SAP XI ..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1XI Components and Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3Development in SAP XI ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Introduction to Proxies .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Proxy Runtime Configuration... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Integration Scenarios in the Integration Repository .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Unit 2: Generating Proxy Objects .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Introduction to the Proxy Program Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68ABAP Proxy Generation .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Java Proxy Generation.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Enhancing Interfaces .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Unit 3: Using Generated Proxy Objects ..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109ABAP Server Proxy Implementation .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110Using Java Client Proxies ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124Configuration in the Integration Directory .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .141Java Server Proxy Implementation.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .151Using ABAP Client Proxies.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .155Server Proxies, Web Services, and WSDL... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .167

25-08-2005 2005 SAP AG. All rights reserved. v

Contents BIT450

vi 2005 SAP AG. All rights reserved. 25-08-2005

Course OverviewThis course provides an introduction to the program model for proxy objects. Togetherwith SAP Exchange Infrastructure, this program model presents a new approach toimplementing integration scenarios. In this approach, message formats are savedcentrally in a repository. In this repository, the actual functions are then created inthe back end by generating proxy objects. The course structure takes the participantsthrough this procedure. Unit 1 introduces the concept and looks at the definitionof message formats, unit 2 addresses the subsequent generation of proxy objectsfor ABAP and Java environments, and unit 3 explains how to use these objects toexchange messages using SAP Exchange Infrastructure.

Target AudienceThis course is intended for the following audiences:

ABAP and Java developers who want to implement functions in SAP systems asserver proxies as part of the implementation of an SAP Exchange Infrastructurescenario

ABAP and Java developers who want to develop function calls in an SAPsystem by using client proxy objects as part of the implementation of an SAPExchange Infrastructure scenario.

Course PrerequisitesRequired Knowledge

BIT400 BC400 JA100

Recommended Knowledge

BC401 JA300 Basic knowledge of Web services and WSDL

25-08-2005 2005 SAP AG. All rights reserved. vii

Course Overview BIT450

Course GoalsThis course will prepare you to:

Understand how proxy objects are used in SAP Exchange Infrastructure (XI) Generate proxies for connecting SAP systems to XI Implement generated proxies and use them in your own programs

Course ObjectivesAfter completing this course, you will be able to:

Assess when to use proxy objects Execute the necessary proxy generation Use the generated client proxy objects Implement the generated server proxy objects

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

XI 3.0

viii 2005 SAP AG. All rights reserved. 25-08-2005

Unit 1Development Objects in SAP XI

Unit OverviewIntroduction to the topic of XI development and revision of the basic principles ofXI with reference to proxy technology.

Unit ObjectivesAfter completing this unit, you will be able to:

Understand the components of SAP Exchange Infrastructure List the options available for connecting application systems to SAP Exchange

Infrastructure Understand the concepts of products, software components, and namespaces Create your own namespaces in the Integration Repository Describe the procedures for using proxies Understand the scenario used in the course Configure an SAP system based on the SAP WebAS ABAP for proxy

communication, or check the configuration Configure an SAP system based on the SAP WebAS Java for proxy

communication, or check the configuration Create integration scenarios in the Integration Repository Create objects for message interfaces in the Integration Repository

Unit ContentsLesson: XI Components and Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

Exercise 1: Checking the Entries in the System Landscape Directory ... . .9Lesson: Development in SAP XI.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Exercise 2: Checking Namespaces.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Exercise 3: Creating and Using Software Components ... . . . . . . . . . . . . . . . . . 25

Lesson: Introduction to Proxies ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Exercise 4: Checking Existing Interface Objects ... . . . . . . . . . . . . . . . . . . . . . . . . . 35

25-08-2005 2005 SAP AG. All rights reserved. 1

Unit 1: Development Objects in SAP XI BIT450

Lesson: Proxy Runtime Configuration .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Exercise 5: Checking the Local Integration Engine of a BusinessSystem .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Lesson: Integration Scenarios in the Integration Repository.. . . . . . . . . . . . . . . . . . 47Exercise 6: Creating an Integration Scenario and Repository Objects inthe Integration Repository .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

2 2005 SAP AG. All rights reserved. 25-08-2005

BIT450 Lesson: XI Components and Connectivity

Lesson: XI Components and Connectivity

Lesson OverviewThis lesson provides a recap of the architecture of the SAP Exchange Infrastructure.

Lesson ObjectivesAfter completing this lesson, you will be able to:

Understand the components of SAP Exchange Infrastructure List the options available for connecting application systems to SAP Exchange

Infrastructure

Business ExampleYou are responsible for development in SAP Exchange Infrastructure and need anoverview of the architecture and components of SAP Exchange Infrastructure.

Components of SAP Exchange InfrastructureThe aim of SAP Exchange Infrastructure is to provide a platform that allows differentinterfaces to connect using a uniform technology. This improves the overview andalso reduces maintenance costs.

Figure 1: System Landscape with SAP Exchange Infrastructure

Components of SAP Exchange InfrastructureSAP Exchange Infrastructure comprises various components:



Figure 2: Architecture of SAP Exchange Infrastructure

You can enter your system landscape in the System Landscape Directory(SLD).

You enter all the necessary interfaces of the various software components, aswell as mapping programs, in the Integration Repository.

You configure the scenarios in the Integration Directory. The Integration Builder is the user interface (GUI) for working with the

Integration Repository and Integration Directory. The Business Process Engine controls the correlation of messages and the

processing of messages within Business Process Management (BPM). The Integration Engine of the Integration Server ensures that messages are

processed according to the configuration in the Integration Directory. Thisinvolves determining who the receiver is and mapping the inbound message tothe receiver interface structure.

The Adapter Engine forms the basis of many adapters for connecting systemsto the Integration Server.

The Runtime Workbench is the main tool for central monitoring of componentsand messages.

Connecting the Application Systems to XIA local Integration Engine can be used on any application system that runs on SAPWeb AS release 6.20 or higher. This means you can implement application scenariosfrom XI. You define the interface structure in the Integration Repository. You can then



generate and call an outbound proxy in the application system; this proxy creates amessage in XI format from the interface parameters and sends it to the IntegrationServer. You can generate an inbound proxy in the target system; this proxy receivesa message in XI format from the Integration Server and processes the data. ABAPand Java proxy generation is supported.

Figure 3: Runtime Procedure: Conversion to XI Message Format

At present, all other application systems are connected to XI using adapters. Thesender system provides data in a document format and sends it to the adapter by usinga particular protocol. The adapter converts the document to XI format and sends it tothe Integration Server in http(s) format. The adapter that is to receive the message isspecified 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.

Proxy Technology and SAP AdaptersSAP adapters (RFC adapters, IDoc adapters) are designed for connecting SAP systemsthat run on a technical basis predating SAP Web AS 6.20 (for example, R/3 4.6), andwhich therefore do not directly support the XI protocol. Since SAP adapters (basedon the RFC protocol) can also be used to connect SAP systems based on SAP WebAS >= 6.20, when you develop a new interface, you must decide which of the twooptions to use.



Figure 4: Overview of Proxies and Adapters

This requires an understanding of the SAP Exchange Infrastructure concept, which isbased on message formats (message interfaces). These message formats are savedcentrally in the Integration Repository using Internet standards (WSDL, XMLschema), independently of the programming languages actually used (ABAP, Java,.NET). However, if you use SAP adapters, the interfaces are developed locally inthe business system and only imported to the Integration Repository later. Thisdoes not comply with the SAP Exchange Infrastructure concept of central interfacedevelopment in the Integration Repository.

This central interface development simplifies the realization of integration scenariosand supports the integration of external interfaces by importing the correspondingWSDL files.

There is another significant difference of a more technical nature, namely the protocolused. It is not always possible to communicate with the back-end system using theRFC protocol. However, this is necessary when using an SAP adapter, because theAdapter Engine communicates with the SAP system using RFC. The HTTP protocol,which is used in proxy technology, is less problematic, particularly if firewalls areused between the Integration Server and the business system.



Figure 5: Outbound vs. Inbound

It is important to understand the definition of outbound and inbound. In theapplication, an outbound message interface is used for a message sent from theapplication to the Integration Server. In the context of adapters, messages that are sentto the Integration Server require a sender adapter; this adapter sends messages fromthe sender to the Integration Server. In the case of proxies, client proxies correspondto an outbound interface and server proxies represent an inbound interface.

Furthermore, when using adapters, the exchanged data format is adapter-specific anddiffers from the proxy XML data format.



Exercise 1: Checking the Entries in theSystem Landscape Directory

Exercise ObjectivesAfter completing this exercise, you will be able to: Check the settings for your business systems in the System Landscape Directory

(SLD)

Business ExampleYou want to implement business processes in an existing system landscape. SAPExchange Infrastructure is installed and the existing system landscape is configuredin the SLD. You want to check these settings to ensure that they are complete and tomake alterations where applicable.

Task: SLD Configuration in the Integration ServerCheck the configuration in the System Landscape Directory (SLD).

1. Log on to the System Landscape Directory.

2. Check whether the software component SC_BIT450_CIS is configured in theSLD.

3. Check whether the business system Training is configured in the SLD.

4. Which technical system is assigned to the business system Training in the SLD?



Solution 1: Checking the Entries in theSystem Landscape DirectoryTask: SLD Configuration in the Integration ServerCheck the configuration in the System Landscape Directory (SLD).

1. Log on to the System Landscape Directory.

a) Call transaction SXMB_IFR to display a menu for the SAP ExchangeInfrastructure J2EE Engine in the Web browser. It is also possible tocall the System Landscape Directory from this page. The user name andpassword are the same as those required to log on to the Integration Server.

2. Check whether the software component SC_BIT450_CIS is configured in theSLD.

a) To display the products and software components, choose SoftwareSoftware Catalog from the SLD initial screen. In the Software Typefield, select Software Components. To view only the relevant softwarecomponents, enter the prefix SC_ in the Display Filter filter field andchoose Enter (or select the filter icon).

3. Check whether the business system Training is configured in the SLD.

a) To navigate back to the initial screen of the SLD, choose Home. To displaythe business systems, choose Business Landscape on the SLD initial screen.

b) The business system Training is maintained as an SAP system; itcorresponds to client 821 of the Integration Server.

4. Which technical system is assigned to the business system Training in the SLD?

Answer: This information is displayed in the overview or the detailed view ofthe business systems:The business system Training is assigned to client 821 of the XI system. Atechnical system is also assigned to the business system, which has the samesystem ID as the XI system.



Lesson Summary

You should now be able to: Understand the components of SAP Exchange Infrastructure List the options available for connecting application systems to SAP Exchange

Infrastructure



Lesson: Development in SAP XI

Lesson OverviewThis lesson gives an overview of development objects and development environments.


Understand the concepts of products, software components, and namespaces Create your own namespaces in the Integration Repository

Business ExampleYou are a new member of an XI development team and need an overview of thecomponents involved and the procedure in a development project.

Development Objects and Programming LanguagesSince SAP Exchange Infrastructure is based on the SAP Web Application Server,which as of release 6.20 enables ABAP development as well as Java development, itmay seem a good idea to separate development according to the various programminglanguages, but this is not necessarily the case.

Figure 6: SAP Web AS and SAP XI


BIT450 Lesson: Development in SAP XI

Although many SAP XI tools are based on Java, it actually makes more sense toorganize development according to development objects. All development objectsare located in the Integration Repository (the Integration Directory essentiallycontains scenario configurations). Development objects are created in the IntegrationRepository independently of the development environment used later.

In addition, some development objects, in particular proxy objects, are located in theapplication system and are dependent on the respective development environment.These are the proxy objects generated for a message interface in the IntegrationRepository and the objects that are used by the generated proxy objects, for exampleprograms.

Products, Software Components, and NamespacesIn an SAP environment, a product corresponds to a technical SAP component. Aproduct consists of one or more software components and customers can see it, installit, and renew it. A product is delivered by way of a product version, which in turncontains software component versions.

Figure 7: Product and Software Component Versions (SWCV) in the SLD

A software component is a reusable product module that can be individuallyupgraded or have patches installed. Software components are versioned to enabledevelopment to continue alongside the productive use of a software component.Development therefore always takes place in a software component version (SWCV).The development manager creates a separate namespace in the Integration Repositoryfor objects that belong together semantically. This is similar to ABAP packages



(previously called development classes) or Java packages. In this way, the objectsare identified uniquely by their name and namespace. The objects of a namespaceare always delivered together with the relevant SWCV.

A namespace in XML is a user-defined constant that follows two conventions: theprefix http:// and the prefix urn:. The prefix http:// does not necessarily mean thatthe namespace is a website. It is more important that namespaces must be globallyunique, not just within the SWCV. Therefore, the use of a company name in thenamespace is a valid option.

The namespaces in the Integration Repository also have implications for proxy objectsthat are generated later, since they determine the package names for the Java proxyobjects. For further information on namespaces, see the documentation in the SAPLibrary: SAP Exchange Infrastructure Design and Configuration Time SoftwareLogistics Organization of Shipment Contents Namespaces.

Caution: When creating your own namespaces, the name components mustnever start with a number. If this is nevertheless the case, an underscore (_) isplaced before the number when the Java proxy objects are generated.

The decisive and visible factors for the developer responsible for editing the objects inthe Integration Repository are the SWCV and the namespace (the products are onlyvisible in the Integration Repository in the integration scenarios).

Figure 8: Importing an SWCV to the Integration Repository



In the same way that software components are versioned, there are also productversions. The relationship between a product version and a software componentversion is saved in the SLD as a software feature.

The following preparations need to be made before development starts:

Create a product version in the SLD Create a software component version (SWCV) for the product version Import the SWCV to the Integration Repository Create namespaces for the SWCV in the Integration Repository

Before you start development, you need to create the product and software componentversions in the SLD. If you are creating a new product and new software components,you must first create the product, then the software components, and finally thecorresponding versions. If a product and software components already exist, youneed to create a new version.

Hint: There is also a based-on relationship for software components. IfSAP component functions are used in a customer software component, itmakes sense to save these in the SLD using the based-on relationship. Thisis saved as a software feature for the software component version as acomponent-component requisite association. For example, SAP ABA 6.20 isbased on SAP Basis 6.20.

The software component versions are then imported to the Integration Repository.You create namespaces for the individual developers in the Integration Repository inthe SWCV. If the SWCV is a new version of an existing SWCV, you can copy theobjects from the old SWCV to the new version by using a release transfer.

For an SWCV you can also save logon data for an SAP back end, which enables youto import RFC signatures and IDoc types. You can flag SWCVs as original objects oras modifiable objects by using the relevant object attributes. You set both attributes inthe system in which a SWCV is to be developed.

User-specific change lists are used in the Integration Repository during development,which must be closed by activating the objects. Once development is finished, theSWCV is flagged as not modifiable and the objects are released. As of XI 2.0, thismeans that the objects are exported from the Integration Repository, for example, forimport to a test system.



If an SWCV is to be used in other systems (for example, imported to a test system),neither of the attributes Objects Are Original Objects or Objects Are Modifiable areset. This prevents changes being made. If an attempt is made to reset the attributesat a later date, warning messages will appear to prevent changes from being madeunintentionally.

Development Landscape

As in R/3, a development landscape typically comprises a development system (DEV),a TEST system and a productive XI system (PROD).

The System Landscape Directory (SLD) is typically used for all three XI systems.

Hint: It is also technically possible to create a separate SLD for each XIsystem. In this case, data from the development SLD system can be exportedto the subsequent SLD system.

Similarly, the development objects of the Integration Repository are also transportedto the subsequent systems by export/import (or using the CMS: Change ManagementService, see below). It is possible to transport complete software component versions,individual namespaces of a software component version, or just single objects. For theIntegration Directory configuration data, the receiver and interface determinationscan also be transported by export or import (including mapping). However, you haveto recreate the communication channels and logon data for each subsequent system,because each system has different technical systems and logon data.

Once the data has been exported from the Integration Repository, you have to movethe export file to the target system import directory, and do the same for the exportfrom the Integration Directory. The corresponding directories are as follows:

Integration RepositoryExport /xi/repository_server/exportImport /xi/repository_server/import

Integration DirectoryExport /xi/directory_server/exportImport /xi/directory_server/import



Figure 9: XI Development Landscape

Business System Groups: In the standard scenario, whereby one SLD is used for allXI systems in a development landscape, you can create business system groups in theSLD (each group is assigned to an Integration Server). For example, you can creategroup G1 as a group of business systems in a development landscape and group G2 asa group of business systems in a test landscape. The business systems are assignedto the groups automatically because each business system is already assigned to anIntegration Server.

Next, you maintain the transport targets, that is, assign a business system from groupG1 to a business system from group G2. You do this directly in the business systemsettings. Since the business system is already assigned to a business system group,you just need to assign a business system from another group by choosing TransportTargets in the detail view of the business system.



Figure 10: Business System Groups and Transport Targets in the SLD

Maintaining these transport targets means that when you import configuration data(for example, from the development system) to the Integration Directory of asubsequent system, the business system names are converted using the transport targetinformation in the SLD. The business system names are converted in the receiverdeterminations, the interface determinations, and the routing conditions.

The Change Management Service (CMS) is used for central administration of theJava development environment and the transports to the Web AS 6.40 across thewhole software lifecycle. You can use it to configure development landscapes andtransport software changes. The functions of the CMS are closely related to the SystemLandscape Directory (SLD). As an administrator tool, the CMS joins all involvedcomponents together into one unit, which can also be used to realize distributeddevelopment projects.

Hint: For more information on how to use the CMS and its restrictions, seeSAP Note 754143 CMS notes / restrictions, and related notes.



Figure 11: Change Management Server (CMS) for SAP XI

If the CMS is set up on the Java side of the XI Integration Server, on the homepage ofthe Exchange Infrastructure tools, you can use Administration to set for which objectsthe CMS should be used (menu path Repository / CMS Adjustment CMS transportsettings). This is independent of the SWCV.

AuthorizationsA series of composite roles are supplied for the various development activities in XI,which contain the roles for the ABAP and J2EE parts. The following table showsthe most important composite roles together with information on whether they havebeen assigned for the course for the users BIT450-## in one of the clients used (OK),whether they have only been assigned to one component (J for J2EE and A forABAP), or whether they have not been assigned at all (-).

Composite Roles in SAP XI and in the CourseComposite Role 800 821SAP_XI_DISPLAY_USER OK OKSAP_XI_DEVELOPER (J2EE) OKSAP_XI_CONFIGURATOR OK -SAP_XI_MONITOR - -SAP_XI_CONTENT_ORGANIZER - -SAP_XI_ADMINISTRATOR - -



The users BIT450-## in client 821 have also been assigned authorization for the ABAPWorkbench (SE80). The individual roles are described below, with an explanation ofhow to look them up in role maintenance (PFCG).

SAP_XI_DISPLAY_USER A user with this role can view all content from theIntegration Repository, the Integration Directory, the System Landscape Directory,the Integration Engine/Server, and so on, within SAP Exchange Infrastructure.

SAP_XI_DEVELOPER The XI developer is responsible for all activities in SAPExchange Infrastructure that involve the design and development of businessprocesses. In particular, this includes the design of integration scenarios, interfaces,and mappings in the Integration Repository using the Integration Builder, as well asthe import of existing interfaces from business systems. The XI developer is alsoresponsible for generating proxies (ABAP and Java) and implementing them inbusiness systems.

SAP_XI_CONFIGURATOR The XI configurator is responsible for all activities inSAP Exchange Infrastructure that involve the configuration of business processes(integration content). In particular, this includes the logical routing settings, mapping,physical routing in the Integration Builder and maintenance of business systemsand the System Landscape Directory. The XI configurator is also responsible formaintaining configuration data for the IDoc adapter (metadata).

SAP_XI_MONITOR The XI monitor is responsible for all activities in SAP ExchangeInfrastructure that involve monitoring. In particular, this includes monitoring XMLmessage processing and message throughput, as well as error handling and statustracking. It also includes the monitoring of processed IDocs, RFCs, and othermessages in adapters. The XI monitor can also check the contents of the runtimecache in the Integration Server and trigger cache updates, for example.

SAP_XI_CONTENT_ORGANIZER The XI content organizer is responsible foractivities in SAP Exchange Infrastructure that involve the organization and structuringof the contents of the Integration Repository, the Integration Directory, and the SystemLandscape Directory. These are more important tasks that are not typically performedby an XI developer or an XI configurator (for example, maintenance and import ofsoftware components in the System Landscape Directory).

SAP_XI_ADMINISTRATOR The XI administrator is responsible for all activities inSAP Exchange Infrastructure that involve technical configuration and administration.In particular, this includes the settings for the Integration Engine, the IntegrationServer, the Integration Builder (the Integration Repository and Directory), theSystem Landscape Directory, the Runtime Workbench, and the IDoc adapter. The XIadministrator is also responsible for maintaining the SAP Exchange Infrastructureprofile data (Exchange Profile).



SAP Back-End System Development for SAP AdaptersDevelopment in SAP back-end systems, for example R/3 4.0, corresponds to thetechnologies and procedures from the areas of RFC programming and ALE. There aretherefore no XI-specific development activities to be taken into account for connectingSAP back-end systems. For the SAP back-end system, there is no difference betweenthe RFC or ALE connection to XI and the connection to another SAP back-endsystem. It is only necessary to configure the SAP adapters (RFC adapters and IDocadapters), as described in the course BIT400.



Figure 12: Development in the SAP Back End: Standard

Inbound RFC

To receive inbound RFC calls, you have to create an RFC-enabled functionmodule (RFM: remote-enabled function module) in the back-end system andimport the RFC signature to the Integration Repository.

Inbound ALE

An IDoc type must exist as the structure for the data record, and you have tomake the standard ALE configurations. You have to import the IDoc type intothe Integration Repository.

Outbound RFC

You have to create an RFC destination for the RFC adapter that can be used inan application. The RFC signature for the called function module (RFM) mustbe imported in the Integration Repository.

Outbound ALE

You have to create an RFC destination for the IDoc adapter that can be used inALE customizing, and an IDoc type that must be imported into the IntegrationRepository.

As well as the standard procedures for RFC and ALE technology, you also have toconfigure the SAP adapters and make the XI configuration settings in the IntegrationDirectory.



Exercise 2: Checking Namespaces

Exercise ObjectivesAfter completing this exercise, you will be able to: Check the namespaces for a software component version imported to the

Integration Repository

Business ExampleAs a member of a development project, you have to create your own objects in theIntegration Repository and save them in a separate namespace.

Task:Check the software components SC_BIT450_SALES and SC_BIT450_CIS in theIntegration Repository.

1. Log on to the Integration Server. From the menu, start the Integration Builderand log on to the Integration Repository.

2. Check which namespaces the software component versions SC_BIT450_SALESand SC_BIT450_CIS contain.



Solution 2: Checking NamespacesTask:Check the software components SC_BIT450_SALES and SC_BIT450_CIS in theIntegration Repository.

1. Log on to the Integration Server. From the menu, start the Integration Builderand log on to the Integration Repository.

a) Log on to client 800 in the training system.

b) Choose Exchange Infrastructure: Integration Builder Start IntegrationBuilder or call transaction SXMB_IFR. Choose Repository (Design). Theuser name and password are the same as those required to log on to theIntegration Server.

2. Check which namespaces the software component versions SC_BIT450_SALESand SC_BIT450_CIS contain.

a) To navigate to the individual namespaces, open the software componentsand the software component versions. To see where the namespaces aremaintained, double click the software component version.



Exercise 3: Creating and Using SoftwareComponents

Exercise ObjectivesAfter completing this exercise, you will be able to: Create your own software components in the SLD Import software components into the Integration Repository

Business ExampleTo develop your own interfaces, you need your own software component.

Task 1:Create the software component SC_BIT450_MARKETING_## Version 1.0 in theSystem Landscape Directory for the product P_BIT450_MARKETING.

1. Log on to the System Landscape Directory (SLD).

2. In the SLD, navigate to the list of software components.

3. Create a new software component SC_BIT450_MARKETING_## Version 1.0for the vendor bit450.com.

Task 2:Import the software component SC_BIT450_MARKETING_## Version1.0 from the SLD into the Integration Repository and create the namespacehttp://bit450.com/xi/marketing##.

1. Log on to the Integration Repository.

2. Import your software component SC_BIT450_MARKETING_## Version 1.0.

3. Open your software component version SC_BIT450_MARKETING_##Version 1.0 and enter the namespace http://bit450.com/xi/marketing##



Solution 3: Creating and Using SoftwareComponentsTask 1:Create the software component SC_BIT450_MARKETING_## Version 1.0 in theSystem Landscape Directory for the product P_BIT450_MARKETING.

1. Log on to the System Landscape Directory (SLD).

a) The homepage of the Integration Builder (transaction SXMB_IFR)provides a link for logging on to the System Landscape Directory.

b) Log on with your user BIT450-## and your password from the IntegrationServer client 800.

2. In the SLD, navigate to the list of software components.

a) Choose Software Catalog.

b) In the software catalog, choose the software type Software Components.

3. Create a new software component SC_BIT450_MARKETING_## Version 1.0for the vendor bit450.com.

a) Choose New Component to start the wizard.

b) Maintain the parameters of the software component as follows:

Parameter ValueProduct P_BIT450_MARKETINGVendor bit450.comName SC_BIT450_MARKETING_##Version 1.0

(The product can only be selected from the existing values.)

c) Choose Create to create the software component.

d) Check whether a success message is displayed at the top of the browserwindow (Created SC_BIT450_MARKETING_##, 1.0 of bit450.com ).

Continued on next page



Task 2:Import the software component SC_BIT450_MARKETING_## Version1.0 from the SLD into the Integration Repository and create the namespacehttp://bit450.com/xi/marketing##.


a) The homepage of the Integration Builder (transaction SXMB_IFR)provides a link for logging on to the Integration Repository.

b) Log on with your user BIT450-## and your password from the IntegrationServer client 800.

2. Import your software component SC_BIT450_MARKETING_## Version 1.0.

a) From the menu, choose Tools / Copy from System Landscape Directory /Import Software Component Versions.

b) In the list of software component versions, select the line of your softwarecomponent SC_BIT450_MARKETING_## Version 1.0 and chooseImport.

c) After the message to report successful import has been displayed in theimport log, exit the list of software component versions by choosing Finish.

3. Open your software component version SC_BIT450_MARKETING_##Version 1.0 and enter the namespace http://bit450.com/xi/marketing##

a) On the Objects tab page, the software components are listed in alphabeticalorder. Navigate to your software component and open it so that thesoftware component version SC_BIT450_MARKETING_## Version1.0 is displayed. Double click to open the detail screen for the softwarecomponent version.

b) Switch to change mode and in the Namespaces area, enter the namespacehttp://bit450.com/xi/marketing##.

c) Save your changes.

d) Your namespace is displayed in the left area of the menu under the softwarecomponent version SC_BIT450_MARKETING_## Version 1.0. You canopen the namespace and display the subareas.

e) Activate all your changes.



Lesson Summary

You should now be able to: Understand the concepts of products, software components, and namespaces Create your own namespaces in the Integration Repository


BIT450 Lesson: Introduction to Proxies

Lesson: Introduction to Proxies

Lesson OverviewThis lesson provides an overview of proxy technology.


Describe the procedures for using proxies Understand the scenario used in the course

Business ExampleYour company already uses SAP Exchange Infrastructure. The company isimplementing a new integration scenario using SAP systems, and you need to plan thetechnical conversion and decide whether to use proxies.

Proxy ObjectsA proxy is a server function that enables two remote applications to communicate.Proxy objects act as agents and often perform tasks such as converting transferred data.

Proxy objects therefore provide server services in programming, so that (server)application functions can be used from a (client) application. These functions usestandard protocols and formats, for example http and XML, independently of thedevelopment language used to implement the server or the client. Each functionhas a description, which is used to generate the proxy objects in the appropriatedevelopment environment for the client. The use of proxy objects therefore enablesyou to use server application functions in the client application.



Figure 13: Proxy Principle: Server Functions

The server functions are described in a representation independent of the developmentenvironments (and languages), typically in the form of special machine-readableXML files, so that proxy objects can be generated automatically. The format of theXML files is WSDL (Web Service Description Language. For further information, seehttp://www.w3.org/2002/ws).

In XI, the functions are saved as message interfaces in the Integration Repositoryand these interfaces are used to generate the proxy objects for the respectivedevelopment environment (currently ABAP or Java). Functions are called usingHTTP protocol and special XML data formats.

Proxy Objects in XIProxy objects are classes and methods in a programming language that generate orprocess messages for a message format defined in the Integration Repository (messageinterface). A distinction is made between client proxy for outbound interfaces andserver proxy for inbound interfaces:

Client Proxy Objectsenable you to create messages (which correspond to an outbound messageinterface for which the proxy objects were generated) and send these messagesto the Integration Server.



Server Proxy Objectsrepresent a back-end function that can be called using an XI message (thatcorresponds to an inbound message interface).

Hint: In XI 2.0, client proxies were called outbound proxies, as theybelong to an outbound message interface, and server proxies were referred toas inbound proxies.

To use proxy objects, the following steps are necessary:

1. Define the message interfaces in the Integration Repository.2. Generate the proxy objects.3. Use proxy runtime.

Define the message interfaces in the Integration Repository.The repository objects to be used for a scenario are saved in the IntegrationRepository at design time. This includes the message interface, message types,and data types. Flagging the message interface as inbound or outbound alsodetermines whether server or client proxy objects will be generated for thismessage interface.

Generate the proxy objects.The system can then generate the proxy objects for a development environment(ABAP or Java) from a defined message interface. These objects are classes,methods, and in some cases structure definitions, that are used in an inboundscenario to implement server functions, that is, to process an inbound messagethat corresponds to the message interface. In an outbound scenario, the clientproxy objects can be used to create and send an outbound message correspondingto the message interface.

Using the proxy runtime.To be able to use proxy objects, the business system in question must havea proxy runtime that enables messages to be sent and received independentlyof the scenario and the message format. Proxy runtime includes, among otherthings, a local Integration Engine. ABAP proxy runtime belongs to the ABAPpart of the Web AS (in the XI Add-On) and Java proxy runtime is part of XIConnectivity, which can also be installed separately.

The development process in this case is different from the programming of anRFC-enabled function module (RFM: Remote-enabled FunctionModule). RFMfunctions are developed (as an inbound interface) in the target system together withthe signature (import and export parameters). The functions can then be called. When



using proxy objects, the interface definition is separated from the implementation ofthe actual functions. First, the message format for the inbound message is saved in theIntegration Repository in the form of an inbound message interface. This definition isused to create a shell (a method) representing the corresponding interface, into whichthe functions must be incorporated (for inbound messages). This is similar to thecreation of a function module source text with a set signature.

Figure 14: Proxy Generation and Use

At design time, you create the repository objects, which are then used for proxygeneration to generate proxy objects for a programming language such as ABAP orJava. At runtime, a method can be accessed to send a message to SAP ExchangeInfrastructure, for example. Proxy runtime is used to send a message from an SAPsystem.

Scenario for ExercisesIn the exercises, participants will connect a Java standalone application to a client of anSAP ABAP system in a synchronous scenario by using proxy technology. Customerinformation is saved in the target system (business system SAP_BACKEND).This customer information is required for sales orders in the business systemWEB_AS_JAVA.

Design Time: First, create the message interfaces CustomerInformation_Requestand CustomerInformation_Provide in the Integration Repository for the softwarecomponents SC_BIT450_SALES and SC_BIT450_CIS.



Figure 15: Design View: Creating Interfaces

The next step is to generate the proxy objects for both sides. You have to generatea CustomerInformation_Request in the caller system by using the generatedproxy method; this request is sent to the central Integration Server. You also haveto implement the generated proxy method in the target system, that is, you mustdevelop the ABAP instructions for compiling the answer for the message formatCustomerInformation_Provide.

Figure 16: Synchronous Scenario



Exercise 4: Checking Existing InterfaceObjects

Exercise ObjectivesAfter completing this exercise, you will be able to: Find existing interface objects in the Integration Repository.

Business ExampleYou want to gain an overview of the existing interface objects.

Task:Check which interface objects are available in the SWCV SC_BIT450_CIS in yournamespace http://bit450.com/xi/abap##.


2. Naviagte to the SWCV SC_BIT450_CIS and the namespacehttp://bit450.com/xi/abap##, and search for existing message interfaces.



Solution 4: Checking Existing InterfaceObjectsTask:Check which interface objects are available in the SWCV SC_BIT450_CIS in yournamespace http://bit450.com/xi/abap##.



b) Choose Exchange Infrastructure: Integration Builder Start IntegrationBuilder or call transaction SXMB_IFR. Choose Integration Repository.The user name and password are the same as those required to log onto the Integration Server.

2. Naviagte to the SWCV SC_BIT450_CIS and the namespacehttp://bit450.com/xi/abap##, and search for existing message interfaces.

a) Open the SWCV SC_BIT450_CIS, then choose version 1.0 and thenamespace http://bit450.com/xi/abap##.

b) Open the Interface Objects / Message Interface node, and double click toopen the existing message interface CustomerInformation_Provide.

c) In the message interface CustomerInformation_Provide, the messagetypes MtName and MtCustomerInfo, and the fault message typeMissingInformation are referenced. You can double click on these namesto navigate to the message type definitions. The data types referenced inthe message types are also directly displayed here.



Lesson Summary

You should now be able to: Describe the procedures for using proxies Understand the scenario used in the course



Lesson: Proxy Runtime Configuration

Lesson OverviewThis lesson explains the required configuration for the ABAP and Java runtimeenvironments.


Configure an SAP system based on the SAP WebAS ABAP for proxycommunication, or check the configuration

Configure an SAP system based on the SAP WebAS Java for proxycommunication, or check the configuration

Business ExampleIn your company, interfaces of an SAP system are connected to SAP XI using proxytechnology, and you are responsible for checking the configuration.

ABAP Proxy Runtime ConfigurationYou have to configure the proxy runtime in the business system so that the localIntegration Engine is not the Integration Server itself, but an application system. Youalso need to determine to which Integration Server the messages will be sent.

In ABAP, you have to make client-specific configuration settings using transactionSXMB_ADM. You have to specify that each client is an application system, whichmeans that proxy runtime belongs to a local Integration Engine. You also have toset the corresponding Integration Server. You can do this directly using a URL, orby using an existing SM59 destination.


BIT450 Lesson: Proxy Runtime Configuration

Figure 17: ABAP Proxy Runtime Configuration

As with the application systems, you also have to configure the central IntegrationServer as the Integration Server. Of course, in this case you do not need to set furtherparameters for the corresponding Integration Server.

For connecting an SAP ABAP back-end system, additional general configurationsteps are required. These are listed briefly below:

RZ0: Register the technical system in the SLD Define the business system in the SLD and import into the directory Define a communication channel XI recipient for back end SXMB_ADM: Define the Integration Engine as decentral SXMB_ADM: Maintain the destination on the central Integration Engine Enable access to the SLD: SLDAPICUST + SM59 Create user XIAPPLUSER SXMB_ADM: Activate queues

Hint: These points are covered in more detail in the basic course BIT400.



Java Proxy Runtime ConfigurationThe use of Java proxies requires a SAP J2EE Engine 6.40 SP5 or higher. Togetherwith theMessaging System (MS), the Java proxy runtime (JPR) must be installedon the SAP J2EE Engine. Both the JPR and the MS are components of the XI 3.0Adapter Framework (AF), which is available from the SAP Service Marketplace.

Hint: To install the XI Adapter Framework, you need to install the followingSoftware Delivery Archives (SDA) and Software Component Archives (SCA)using the Software Deployment Manager (SDM):

Two SDAs that contain external libs (for license reasons, these cannot besupplied by SAP):

aii_af_ra_ms_sonic_client.sda aii_adapter_jms_provider_lib.sda

Two SCAs that contain the actual Adapter Framework:

SAPXIAFCnn_x.sca (contains AF core libraries and services) SAPXIAFnn_x.sca (contains AF applications)

(nn stands for the relevant number of the SP, and X is the patch level, forexample SAPXIAF09_0.sca).

Hint: Since the Adapter Framework makes intensive use of the other servicesof the SAP J2EE Engine, SAP recommends that you install the AF at the sameSP level as the J2EE Engine (from SP9, the SP numbers of the componentshave been synchronized).

In contrast to XI 2.0, the Java proxy runtime requires almost no manual configuration.It is more important that the SAP J2EE Engine is correctly integrated into thesystem landscape. The required and optional steps are described in more detail inthe following.

Connection to the SLD:for security reasons, in XI 3.0, the SLD access data is no longer maintained in the filedbconnect.properties. Instead, it is stored in the Secure Store of the J2EEEngine, which gets its date from the Exchange Profile of the Integration Servers.You can configure the corresponding connection to the Integration Server using thelink: http://:/exchangeProfile/connection.jsp.



Figure 18: Configuration of the J2EE Proxy Runtime: Access to theexchangeProfile

To ensure that SLD access is activated, call the service CPACache in the VisualAdministrator and check whether the parameter SLDAccess has the value true.

The J2EE engine accesses the SLD itself using the configuration of the SLD DataSupplier service (with the help of the Visual Administrator).

Business SystemIn XI 2.0, the JPR uses the file technicalID.properties to determine theassociated business system. In XI 3.0, the business system is identified by the SAPJ2EE Server, which automatically logs on to the SLD when the Adapter Frameworkis installed. The business system referenced by the technical system actsas a sender service for outgoing messages.

Logging and Tracing:To change the standard logging and tracing settings, use the Visual Administrator andcall the service Log Configuration. Switch to "Advanced Mode" and select the"Runtime" tab, followed by "Destinations". Here, choose the entries

library_com.sap.aii.proxy.xiruntime_JPRTraceapplication_sap.com/com.sap.xi.proxyserver_ProxyServerTrace

Here you can change the relevant log and trace settings at runtime. However, thesesettings only take effect if the following settings are made in the LogManager (in thekernel tree of the server node):



either ForceSingleTraceFile is set to NOor com.sap.aii.proxy has been added toSingleTraceFile_UnrestrictedLocations.



Exercise 5: Checking the Local IntegrationEngine of a Business System

Exercise ObjectivesAfter completing this exercise, you will be able to: Check which Integration Server your business system SAP_BACKEND is

assigned to.

Business ExampleThe client of an SAP system is a business system which exchanges messages by usingSAP Exchange Infrastructure. Therefore, an Integration Server must be assignedto the client in the SAP system.

Task 1:Check the SLD for the systems SAP_BACKEND andWEBAS_JAVA.

1. Log on to the SLD and check the list of business systems.

Task 2:In the Integration Directory, check whether the systems SAP_BACKEND andWEBAS_JAVA have been imported, and which communication channels areavailable.

1. Navigate to the business systems.

Task 3:Check which Integration Server the business system SAP_BACKEND is assigned to.

1. Log on to the business system SAP_BACKEND and call the transaction forconfiguring the Integration Engine.



Solution 5: Checking the Local IntegrationEngine of a Business SystemTask 1:Check the SLD for the systems SAP_BACKEND andWEBAS_JAVA.

1. Log on to the SLD and check the list of business systems.

a) A list of business systems is displayed under System Landscape / BusinessLandscape.

b) The systems SAP_BACKEND andWEBAS_JAVA are included in thislist.

c) Select the name of the system to view the detailed information.

Task 2:In the Integration Directory, check whether the systems SAP_BACKEND andWEBAS_JAVA have been imported, and which communication channels areavailable.

1. Navigate to the business systems.

a) Log on to the Integration Directory.

b) Choose Objects Service Without Partner Business System SAP_BACKEND Communication Channel. You will see thecommunication channel that the instructor created (SAP_Proxy_In). Thischannel has the type XI recipient and references an SM59 destination.

c) Choose Objects Service Without Partner Business System WEBAS_JAVA Communication Channel. You will see thecommunication channel that the instructor created (J2E_Proxy_In). Thischannel has the type XI recipient and references an SM59 destination.

d) Optional: You can log on to the Integration Server (XI client 800) anduse transaction SM59 to check the SM59 destinations referenced in thecommunication channels.




Task 3:Check which Integration Server the business system SAP_BACKEND is assigned to.

1. Log on to the business system SAP_BACKEND and call the transaction forconfiguring the Integration Engine.

a) Log on to SAP_BACKEND. Use the parameters provided by the instructor.

b) Call transaction SXMB_ADM to configure the Integration Engine.

c) Under the Configuration node, choose the second entry ConfigurationData (Integration Engine).

d) In the Global Configuration Data section, the Role of Business Systemparameter shows that the role LOC Application System is assigned to thecurrent client. The assigned Integration Engine is configured using theCorresponding Integration Server parameter, which contains the URLof the Integration Engine.

Hint: For an explanation of how to configure the URL for callingthe Integration Server, use the F1 help for the CorrespondingIntegration Server field.



Lesson Summary

You should now be able to: Configure an SAP system based on the SAP WebAS ABAP for proxy

communication, or check the configuration Configure an SAP system based on the SAP WebAS Java for proxy

communication, or check the configuration


BIT450 Lesson: Integration Scenarios in the Integration Repository

Lesson: Integration Scenarios in the IntegrationRepository

Lesson OverviewThis lesson introduces the Integration Repository, including integration scenarios andinterface objects.


Create integration scenarios in the Integration Repository Create objects for message interfaces in the Integration Repository

Business ExampleYou want to implement a new integration scenario using SAP Exchange Infrastructure.You are a member of a project team and are responsible for creating the necessaryobjects in the Integration Repository as well as an integration scenario, so that yourcolleagues can later retrace the objects you have created and used.

Introduction to Integration ScenariosBusiness scenarios in the Integration Repository are the graphical representation of anintegration scenario and contain information about the systems involved, as well asthe interfaces and mappings used. They are therefore a type of integration plan andcan be saved, for example, as image files (jpg).

The integration scenarios in the Integration Repository can be copied to the IntegrationDirectory for generating configuration scenarios.

It is not a prerequisite for production operation to save an integration scenario in theIntegration Repository, but it is recommended for documentation and retraceabilitypurposes. It also considerably simplifies the later creation of a configuration scenarioin the Integration Repository.

SAP also supplies integration scenarios for your components that use SAP ExchangeInfrastructure.



Elements of Integration ScenariosAn integration scenario enables you to save the components involved in the form ofvertical (colored) columns. These application columns are assigned a role in thescenario, which is a purely descriptive name. You do not enter any business systemsin the integration scenarios. At design time, the integration scenario should representthe process independently of the business systems that will be used later.

When you create the application component, you can assign a product from the SLD.If it is not yet clear which product will be used, or the product is not maintained in theSLD, you can use a product template instead.

In the components of the integration scenario, you create actions, which represent theprocess steps in the scenario. An action sends or receives an (ext.) message. Messageinterfaces are saved for the actions, which describe the format of the message.

A connection line between the actions is used to connect the process steps. It indicateswhere messages are exchanged between process steps. The message interfaces usedare entered in the connection line. If different message interfaces are used, you haveto create a relevant message mapping in the connection line.

If the connected actions are on the same level, the process is synchronous. If theaction on the right-hand side is below the action on the left-hand side, this representsan asynchronous scenario step.

Hint: Although an integration scenario is a representation of an integrationscenario that is typically distributed across two or more components, theintegration scenario itself must be assigned as an object to a component andto a namespace in the Integration Repository. This also applies to mappingobjects, which connect the message interfaces of two components. Thecomponent that an integration scenario is assigned to is not important at thisstage. In the scenario used in the following exercises, the integration scenarioand the mapping objects are assigned to the sender system.

The Integration Scenario for the ExercisesIn the exercises, an integration scenario containing the message interfaces to be usedis created in the Integration Repository.

Hint: The software components have already been created and imported tothe Integration Repository. The namespaces for the objects to be created havealso been saved in the software component versions.



Figure 19: The Synchronous Integration Scenario

The integration scenario contains two systems. The first system (role: Sales andDistribution) requires detailed customer information, which is saved in the secondsystem (role: CustomerInfoCenter). This information is to be called synchronously.

The sender system is represented by a Java application that works with a Java clientproxy. The receiver system is the client of an SAP system that works with a serverproxy.

Figure 20: Systems Involved in the Scenario



In this synchronous scenario, a Java application is created that requests information oncustomers from a business system. A client of the R/3 back-end system is used.

The objects required in the Integration Repository are shown below. The objects forthe software component SC_BIT450_CIS have already been created in the IntegrationRepository.

Figure 21: Overview of Message Formats

The Java application sends a query containing a complex data type with two customerfields. However, the application function in the target system only expects a simpledata type with the combined name of the customer. You therefore require a mappingfor this part of the message on the Integration Server.



Figure 22: Mapping Types

You have to create amessage mapping, which maps the outbound message type withtwo source fields to the inbound message type with one target field. An interfacemapping is also necessary. This maps the two message interfaces to each other andcontains the message mapping.

Finally, you have to make the relevant configuration settings in the IntegrationDirectory so that the message sent by the Java application is correctly forwarded tothe target system.



Figure 23: Configuration in the Integration Directory



Exercise 6: Creating an Integration Scenarioand Repository Objects in the IntegrationRepository

Exercise ObjectivesAfter completing this exercise, you will be able to: Create integration scenarios in the Integration Repository

Business ExampleYou are a member of a project team and want to implement an integration scenario.To ensure that the message formats you use and the systems involved can be tracedeven after your project has been completed, create a integration scenario containingthe necessary information in the Integration Repository along with the actual messageinformation (message interfaces).

Task 1:Create an integration scenario called BIT450_CustomerInfoScenario_## in theIntegration Repository.


2. Create a new integration scenario called BIT450_CustomerInfoScenario_##for your software component version SC_BIT450_SALES 1.0 in yournamespace http://bit450.com/xi/java##.

3. Insert the following two application components into your integration scenario:product version P_BIT450_SALES 1.0 with the role Sales and Distributionand product version P_BIT450_CIS 1.0 with the role CustomerInfoCenter.

4. Insert the action RequestCustomerInformation for productversion P_BIT450_SALES 1.0 with the outbound interfaceCustomerInformation_Request into your application component.

Caution: Make sure that you enter the names correctly when creatingthe objects since these names are used in all the following exercises,especially proxy runtime. If you are unsure of the names, use thegraphics from this lesson or ask your instructor.




5. Insert the action you just created and the action ProvideCustomerInformation(from the software component SC_BIT450_CIS) into your integration scenarioand insert a connection line between the actions.

Task 2:In the Integration Repository, create the necessary repository objects for theintegration scenario you just created.

Hint: There are two methods for creating the objects: top-down (by forwardsnavigation from the integration scenario to the message interface down to thedata types) or bottom-up (from the data types to the message types up to themessage interface). The top-down method is described below.


2. Check whether the message interface CustomerInformation_Provide for thesoftware component version (SWCV) SC_BIT450_CIS 1.0 in your namespacehttp://bit450.com/xi/abap## corresponds to the current scenario and that onlyobjects from your namespace are referenced.

3. Create the outbound message interface CustomerInformation_Requestsaved in the action RequestCustomerInformation in your namespacehttp://bit450.com/xi/java##.

It should contain an output message typeMtCustomerName, an input messagetypeMtCustomerInfo, and a fault message typeMissingInformation.

The message typeMtCustomerName should in turn use a complex data typePersonName comprising the elements Surname (XSD:string) and Name(XSD:string).

The message type MtCustomerInfo should use the complex data typeCustomerInfo comprising the integer element ID and the string elementsNAME, CUSTTYPE, POSTCODE, and CITY.

4. Create the message mapping CustomerNameMerge for the softwarecomponent version SC_BIT450_SALES 1.0 in your namespacehttp://bit450.com/xi/java## to map the message typesMtCustomerNameand MtName to each other.

In this message mapping, map both the Surname and Name fields from thesource structure, separated by a blank, to MtName (located in the SWCVSC_BIT450_CIS 1.0 in the namespace http://bit450.com/xi/abap##).




The sequence should be first name, then surname.

Test your message mapping.

5. Create the interface mapping CustomerInfoMap for the softwarecomponent version SC_BIT450_SALES 1.0 in your namespacehttp://bit450.com/xi/java## to map the message interfacesCustomerInformation_Request and CustomerInformation_Provide to eachother (using the message mapping CustomerNameMerge for the request).



Solution 6: Creating an Integration Scenarioand Repository Objects in the IntegrationRepositoryTask 1:Create an integration scenario called BIT450_CustomerInfoScenario_## in theIntegration Repository.




2. Create a new integration scenario called BIT450_CustomerInfoScenario_##for your software component version SC_BIT450_SALES 1.0 in yournamespace http://bit450.com/xi/java##.

a) Navigate to your namespace http://bit450.com/xi/java## in thesoftware component version SC_BIT450_SALES 1.0 and expand theIntegration Scenarios & Processes node. Use the context menu forthe Integration Scenarios node to create a new integration scenarioBIT450_CustomerInfoScenario_##. Enter the name on the initial screen,use the predefined values for namespace and software component version,and choose Create. You can enter a description in the detail view. Save theintegration scenario.




3. Insert the following two application components into your integration scenario:product version P_BIT450_SALES 1.0 with the role Sales and Distributionand product version P_BIT450_CIS 1.0 with the role CustomerInfoCenter.

a) Insert the application components by using the context menu. Create anapplication component in the first vertical column on the left-hand side.Leave Product (Defined in System Landscape Directory) selected anduse the input help to search for the product version P_BIT450_SALES1.0 of bit450.com.

Hint: Since the software components assigned to this product arealso saved for the product in the SLD, these are displayed here asinformation for the actions to be used.

Under Role, save the role name Sales and Distribution and choose Enterto exit the detail view.

Following the same procedure, create another application component asa product in the column to the right of the first application component.Enter the product version P_BIT450_CIS 1.0 of bit450.com and the rolename CustomerInfoCenter.

4. Insert the action RequestCustomerInformation for productversion P_BIT450_SALES 1.0 with the outbound interfaceCustomerInformation_Request into your application component.




Caution: Make sure that you enter the names correctly when creatingthe objects since these names are used in all the following exercises,especially proxy runtime. If you are unsure of the names, use thegraphics from this lesson or ask your instructor.

a) Using the context menu for Actions, create an action calledRequestCustomerInformation for the software component versionSC_BIT450_SALES 1.0 in your namespace http://bit450.com/xi/java##.Enter the name on the initial screen, use the predefined values fornamespace and software component version, and choose Create.

In the detail view under Use, leave Internal selected. UnderOutbound Interfaces use the icon with the green cross toenter CustomerInformation_Request in the Name field andhttp://bit450.com/xi/java## in the Namespace field.

Hint: Since the outbound interface is not created until later, youcan use the F4 input help for the namespace, but not for theoutbound interface.

Save your entries.




5. Insert the action you just created and the action ProvideCustomerInformation(from the software component SC_BIT450_CIS) into your integration scenarioand insert a connection line between the actions.

a) Navigate to your integration scenario (in software componentSC_BIT450_SALES) and insert both actions by choosing Insert Actionfrom the context menu for the respective component. Insert the actionRequestCustomerInformation into the component with the role Salesand Distribution and insert the action ProvideCustomerInformationinto CustomerInfoCenter.

Hint: Since the actions are assigned to the corresponding softwarecomponents (and, in this case, the software components areassigned to different products), make sure that you assign them tothe correct application component.

b) Select both actions (by holding down the Shift key and clicking the leftmouse button). Then call the context menu and choose Create ConnectionBetween Selected Actions to create a connection between the two actions.

c) In the detail view for the connection, select the inbound interfaceCustomerInformation_Provide.

d) In the detail view, choose the Mapping tab and maintain the followingmapping under Assigned Interface Mapping:

Name CustomerInfoMapNamespace http://bit450.com/xi/java##Software component version SC_BIT450_SALES

Hint: Since the interface mapping is not created until later, youcannot use the input help.

e) Choose Enter to exit the detail view.

f) You also have the option of defining the actions as start or end actions. Todo so, in change mode, use the corresponding function in the context menufor the action in the integration scenario.

g) Save and activate all objects.




Task 2:In the Integration Repository, create the necessary repository objects for theintegration scenario you just created.

Hint: There are two methods for creating the objects: top-down (by forwardsnavigation from the integration scenario to the message interface down to thedata types) or bottom-up (from the data types to the message types up to themessage interface). The top-down method is described below.




2. Check whether the message interface CustomerInformation_Provide for thesoftware component version (SWCV) SC_BIT450_CIS 1.0 in your namespacehttp://bit450.com/xi/abap## corresponds to the current scenario and that onlyobjects from your namespace are referenced.

a) Open the SWCV and navigate to the interface objects in yournamespace. Under Message Interfaces, open the message interfaceCustomerInformation_Provide that has already been created by doubleclicking it.

b) Check that the correct message types are referenced by checking thenamespaces and also by navigating to the referenced message types andthen to the data types by double clicking.

c) You can also start a check in the message interface by choosing MessageInterface Check (F7). If a message type has been entered that does notexist, an error message will appear.

3. Create the outbound message interface CustomerInformation_Requestsaved in the action RequestCustomerInformation in your namespacehttp://bit450.com/xi/java##.

It should contain an output message typeMtCustomerName, an input messagetypeMtCustomerInfo, and a fault message typeMissingInformation.




The message typeMtCustomerName should in turn use a complex data typePersonName comprising the elements Surname (XSD:string) and Name(XSD:string).

The message type MtCustomerInfo should use the complex data typeCustomerInfo comprising the integer element ID and the string elementsNAME, CUSTTYPE, POSTCODE, and CITY.

a) In your integration scenario BIT450_CustomerInfoScenario_##, doubleclick to open the action RequestCustomerInformation and switch tochange mode. Call the context menu for the name of the outbound interfaceCustomerInformation_Request to create this (previously only named)object directly.

b) In the attributes, define the message interface as synchronous andoutbound and assign the following names, all in your namespacehttp://bit450.com/xi/java##:

Output Message Type MtCustomerNameInput Message Type MtCustomerInfoFault Message Types MissingInformation

Hint: If you place your cursor in the Namespace field, you canselect your namespace from the input help that appears directly tothe right of the field, instead of typing it in.

Save the message interface.

c) Use forward navigation from the message interface (context menu: New orthe name of the message type) to create the message types named above(incl. fault message type), and then use the output and input messagetypes to create the data types. Create all objects in your namespacehttp://bit450.com/xi/java##.

Message Type MtCustomerName->Data Type PersonName (complex)-> Element Surname (XSD:string)-> Element Name (XSD:string)




When creating the data type CustomerInfo, make sure that the fiveelements are assigned beneath the data element and that they are maintainedas elements and not as attributes.

Message Type MtCustomerInfo->Data Type CustomerInfo (complex)-> Element ID (XSD:integer)-> Element NAME (XSD:string)-> Element CUSTTYPE (XSD:string)-> Element POSTCODE (XSD:string)-> Element CITY (XSD:string)

Hint: Of course, you can also copy the message typeMtCustomerInfo from the ABAP component SC_BIT450_CIS,including all its dependent objects. You then only need to manuallycorrect the XML namespace of the message type.

Save and activate all objects.

Hint: There is an icon under the Object menu option that enablesyou to save all objects at the same time.

4. Create the message mapping CustomerNameMerge for the softwarecomponent version SC_BIT450_SALES 1.0 in your namespacehttp://bit450.com/xi/java## to map the message typesMtCustomerNameand MtName to each other.

In this message mapping, map both the Surname and Name fields from thesource structure, separated by a blank, to MtName (located in the SWCVSC_BIT450_CIS 1.0 in the namespace http://bit450.com/xi/abap##).

The sequence should be first name, then surname.

Test your message mapping.

a) In the objects for your namespace http://bit450.com/xi/java##, navigateto the Message Mappings node by choosing Mapping Objects. Tocreate a new message mapping, call the context menu. Enter the nameCustomerNameMerge and choose Create. Enter a description.




b) In the navigation tree for the software component SC_BIT450_SALES,search for the Message Types node and the message typeMtCustomerName. Use Drag&Drop to drag this type to the hand iconin the source structure (to the field labeled Choose a Source Message).Search for your message type MtName in the software componentSC_BIT450_SALES, in the Message Types node, and use Drag&Drop todrag the message type to the hand icon in the target structure (to the fieldlabeled Choose a Target Message). Alternatively, you can use the inputhelp next to the fields named above.

Hint: Only the message type is listed in the graphical mappingeditor display (for example, MtCustomerName), and not thereferenced data type (for example, PersonName).

c) Select the Text function and use Drag&Drop to drag the concat field tothe data-flow editor.

Double click on the source fields Surname and Name to make themappear in the mapping. Drag one connection line from the Name sourcefield (on the right-hand side) to the concat inbound field on the upperleft-hand side (since the first name should come first) and one from theSurname source field (on the right-hand side) to the concat inbound fieldon the lower left-hand side.

Double click on MtName and this target field will also appear in themapping. This field is automatically assigned the result of the concat stepand all fields which are in the mapping will

bit450 en col53 fv part ltr

Documents