BIT400 - SAP Process Integration

Prévia do material em texto

BIT400
SAP Process Integration
.
.
PARTICIPANT HANDBOOK
INSTRUCTOR-LED TRAINING
.
Course Version: 15
Course Duration: 5 Day(s)
e-book Duration: 37 Hours 50 Minutes
Material Number: 50123977
SAP Copyrights and Trademarks
© 2018 SAP SE or an SAP affiliate company. 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 SE or an SAP affiliate company.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. Please see http://global12.sap.com/
corporate-en/legal/copyright/index.epx for additional trademark information and notices.
Some software products marketed by SAP SE and its distributors contain proprietary software components of other software
vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or
warranty of any kind, and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP SE or SAP affiliate company products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or
any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation,
and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and
functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without
notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or
functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ
materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which
speak only as of their dates, and they should not be relied upon in making purchasing decisions.
http://global12.sap.com/corporate-en/legal/copyright/index.epx
http://global12.sap.com/corporate-en/legal/copyright/index.epx
Typographic Conventions
American English is the standard used in this handbook.
The following typographic conventions are also used.
This information is displayed in the instructor’s presentation
Demonstration
Procedure
Warning or Caution
Hint
Related or Additional Information
Facilitated Discussion
User interface control Example text
Window title Example text
© Copyright. All rights reserved. iii
VLC About This Handbook
About This Handbook
This handbook provides you with basic information for attending your virtual live classroom session.
Adobe Connect Support Information
Web and audio support is available by:
● Pressing *0 from within the audio-conferencing
● Calling the support hotline numbers listed below
● Emailing the PGi support hotline below
Global PGi Support Hotline for SAP Education (24/7)
Tel: +1 800-368-1945
Tel: +1 719-234-7915
Note: After dialing in, press option 2 for technical support. You will then be presented with two options –
press 1 for Audio support, or press 2 for Web support.
Email: sapedsupport@premiereglobal.com
Setting up your Learning Environment
Ideally you want to be in a private room when participating in a synchronous (live) event. In reality, you
may not be able to arrange that. Here are some tips for maximizing your learning environment:
● Create an inspirational office/studio to work in
● Use a comfortable chair
● Use well designed and functional computer peripherals
● Keep a log or journal of notes and ideas you can use for future sessions
Before your online class:
● Tell co-workers you will be in class (send e-mail)
● Post a sign indicating when you will be free again (when class is over)
● Use a headset instead of your computer speakers to minimize disruption of others
● Ignore people who try to get your attention
● Turn off the ringers / alerts on telephone, pager, and cell phone
● Turn off e-mail and instant message alerts
● Remove other distractions lying on your desktop
● Keep a glass of water at your desk
Teleconferencing ground rules:
● Use the mute button or press *6
● Do not place call on hold
© Copyright. All rights reserved. iv
● Use the "Raise hand" icon in the Attendee List: My Status to indicate you want to ask a question
● Identify yourself before speaking, when not called on
● Charge the batteries for your cordless handset
● If possible use a land line instead of your cell phone
Minimum Hardware Requirements
● PC with 1.4 GHz processor or higher (Windows) or 1.83 GHz process or higher (Mac OS). Minimum
processor required for screen sharing. You may be asked to share your screen during hands-on
exercise portions of the class.
● 17 inch or larger monitor is recommended, set at 1024 X 768. Larger monitor and 1024 X 768 setting
will make presentation and system screens easier to read.
● Phone with Headset/Microphone or Speakerphone feature – to maximize student listening and
comfort during presentation and demonstration portions of the course.
Software Requirement
A complete list of supported Operating Systems, browsers and additional requirements for Adobe ®
Acrobat® Connect™ can be found at: www.adobe.com/products/acrobatconnectpro/systemreqs
Sample Email to Notify Others You Are in a Virtual Class
This is a sample of an email you can send to your colleagues and manager when you are taking an online
course.
Dear colleagues,
Today I will be participating in an online class from my desk. I will be online from approximately 9:30 a.m.
to 5:30 a.m. EST. I would appreciate it if you would not disturb me during this time. If you have an
immediate question, please contact Joe Smith at extension 123. If it can wait until after 11:00 a.m.,
please send me an email and I will follow up with you before the end of the business day. I appreciate
your consideration.
Best regards,
Getting the Most Out of Your Session
Session Guidelines
● Turn off email, phones, instant messaging tools, and clear other distractions away from your training
area.
● Participate and prepare to be called on by name.
● Use the “Raise Hand” icon if you have an immediate question or comment.
● Be patient waiting for a response to your chat messages.
● If you leave the program, please use the “Step Away” status icon in the Attendee List pod to let your
instructor know when you leave and remember to clear it when you return.
© Copyright. All rights reserved. v
© Copyright. All rights reserved. vi
Contents
x Course Overview
1 Unit 1: SAP Process Integration Architecture
2 Lesson: Describing SAP Process Integration Architecture
13 Lesson: Explaining the Functionality and Utilization of SAP Process
Integration
21 Unit 2: The System Landscape Directory (SLD)
22 Lesson: Maintaining Products and Software Components in the
System Landscape Directory (SLD)
28 Lesson: Implementing Technical Systems in the System Landscape
Directory
35 Lesson: Maintaining Business Systems for Use in the Integration
Directory
43 Unit 3: Interface Objects in the Enterprise Service Repository (ESR)
44 Lesson: Listing Options for Navigating the Enterprise Services
Repository (ESR)
49 Lesson: Analyzing Interface Objects in the Enterprise Services
Repository (ESR)
58 Lesson: Maintaining Interface Objects
62 Lesson: Defining Message Processing Types and Quality of Services
75 Unit 4: Object Mapping in the Enterprise Service Repository (ESR)
76 Lesson: Creating MessageMapping Objects
85 Lesson: Mapping Between Service Interfaces
91 Lesson: Analyzing Asynchronous Integration Scenarios
101 Unit 5: Configuration of Integration Directory Communication Objects
102 Lesson: Using Configuration Views
106 Lesson: Creating Communication Channels in the Integration
Directory (ID)
112 Unit 6: Configuration of Integration Directory Objects for ABAP
Processing
113 Lesson: Analyzing Objects Used in the Configuration of Integration
Engine (IE) Communication
124 Lesson: Analyzing Routing Objects Used in Integration Engine (IE)
Communication
131 Lesson: Analyzing Multiple Receiver Objects Used in Integration
Engine (IE) Communication
© Copyright. All rights reserved. vii
javascript:parent.gotoPageFromSvg(68);
javascript:parent.gotoPageFromSvg(53);
javascript:parent.gotoPageFromSvg(86);
javascript:parent.gotoPageFromSvg(122);
javascript:parent.gotoPageFromSvg(111);
javascript:parent.gotoPageFromSvg(101);
javascript:parent.gotoPageFromSvg(95);
javascript:parent.gotoPageFromSvg(134);
javascript:parent.gotoPageFromSvg(31);
javascript:parent.gotoPageFromSvg(32);
javascript:parent.gotoPageFromSvg(31);
javascript:parent.gotoPageFromSvg(141);
javascript:parent.gotoPageFromSvg(116);
javascript:parent.gotoPageFromSvg(59);
javascript:parent.gotoPageFromSvg(38);
javascript:parent.gotoPageFromSvg(12);
javascript:parent.gotoPageFromSvg(23);
javascript:parent.gotoPageFromSvg(10);
javascript:parent.gotoPageFromSvg(85);
javascript:parent.gotoPageFromSvg(85);
javascript:parent.gotoPageFromSvg(45);
javascript:parent.gotoPageFromSvg(45);
javascript:parent.gotoPageFromSvg(72);
javascript:parent.gotoPageFromSvg(123);
javascript:parent.gotoPageFromSvg(59);
javascript:parent.gotoPageFromSvg(72);
javascript:parent.gotoPageFromSvg(122);
javascript:parent.gotoPageFromSvg(53);
javascript:parent.gotoPageFromSvg(141);
javascript:parent.gotoPageFromSvg(23);
javascript:parent.gotoPageFromSvg(32);
javascript:parent.gotoPageFromSvg(134);
javascript:parent.gotoPageFromSvg(141);
javascript:parent.gotoPageFromSvg(54);
javascript:parent.gotoPageFromSvg(54);
javascript:parent.gotoPageFromSvg(12);
javascript:parent.gotoPageFromSvg(86);
javascript:parent.gotoPageFromSvg(134);
javascript:parent.gotoPageFromSvg(11);
javascript:parent.gotoPageFromSvg(23);
javascript:parent.gotoPageFromSvg(59);
javascript:parent.gotoPageFromSvg(112);
javascript:parent.gotoPageFromSvg(112);
javascript:parent.gotoPageFromSvg(10);
javascript:parent.gotoPageFromSvg(116);
javascript:parent.gotoPageFromSvg(123);
javascript:parent.gotoPageFromSvg(111);
javascript:parent.gotoPageFromSvg(116);
javascript:parent.gotoPageFromSvg(68);
javascript:parent.gotoPageFromSvg(123);
javascript:parent.gotoPageFromSvg(45);
javascript:parent.gotoPageFromSvg(32);
javascript:parent.gotoPageFromSvg(95);
javascript:parent.gotoPageFromSvg(38);
javascript:parent.gotoPageFromSvg(101);
javascript:parent.gotoPageFromSvg(38);
javascript:parent.gotoPageFromSvg(54);
javascript:parent.gotoPageFromSvg(11);
152 Unit 7: Configuration of Integration Directory Objects for Java
Processing
153 Lesson: Maintaining Objects for Advanced Adapter Engine (AAE)-
Only Processing
157 Lesson: Maintaining Objects for Advanced Adapter Engine Extended
(AEX) Message Processing
164 Lesson: Creating and Deploying Integration Flows to the Advanced
Adapter Engine Extended (AEX)
168 Unit 8: Operations of SAP Process Integration
169 Lesson: Using the Runtime Workbench
175 Lesson: Using the Process Integration Monitoring (PIMon) Home
180 Lesson: Using the SAP NetWeaver Administrator
188 Unit 9: Connectivity Options for SAP Process Integration
189 Lesson: Analyzing Connectivity Options Between Back-End
Systems with SAP Process Integration
198 Unit 10: HTTP Connectivity Options
199 Lesson: Configuring the Simple Object Access Protocol (SOAP)
Adapter
201 Lesson: Using Proxy Technology
206 Lesson: Checking the HTTP ABAP Adapter
211 Lesson: Using the HTTP_AAE (Java) Adapter
220 Unit 11: File Adapter Configuration
221 Lesson: Configuring the Receiver File Adapter
229 Lesson: Configuring a Sender File Adapter
240 Unit 12: Intermediate Document (IDoc) Connectivity Options
242 Lesson: Using the Intermediate Document (IDoc) Adapter with the
Receiver Intermediate Document Adapter for the ABAP Stack
253 Lesson: Using the Sender Intermediate Document (IDoc) Adapter
257 Lesson: Using the Intermediate Document (IDoc) Adapter in the
Advanced Adapter Engine (AAE)
260 Lesson: Configuring a Complete Intermediate Document (IDoc)
Scenario
267 Unit 13: Configuration of SAP Business Application Programming
Interfaces (BAPIs) Connectivity
268 Lesson: Configuring the Receiver Remote Function Call (RFC)
Adapter
275 Lesson: Configuring the Sender Remote Function Call (RFC)
Scenario
© Copyright. All rights reserved. viii
javascript:parent.gotoPageFromSvg(216);
javascript:parent.gotoPageFromSvg(231);
javascript:parent.gotoPageFromSvg(285);
javascript:parent.gotoPageFromSvg(162);
javascript:parent.gotoPageFromSvg(239);
javascript:parent.gotoPageFromSvg(270);
javascript:parent.gotoPageFromSvg(190);
javascript:parent.gotoPageFromSvg(174);
javascript:parent.gotoPageFromSvg(277);
javascript:parent.gotoPageFromSvg(163);
javascript:parent.gotoPageFromSvg(179);
javascript:parent.gotoPageFromSvg(230);
javascript:parent.gotoPageFromSvg(250);
javascript:parent.gotoPageFromSvg(267);
javascript:parent.gotoPageFromSvg(163);
javascript:parent.gotoPageFromSvg(190);
javascript:parent.gotoPageFromSvg(199);
javascript:parent.gotoPageFromSvg(199);
javascript:parent.gotoPageFromSvg(270);
javascript:parent.gotoPageFromSvg(162);
javascript:parent.gotoPageFromSvg(167);
javascript:parent.gotoPageFromSvg(231);
javascript:parent.gotoPageFromSvg(167);
javascript:parent.gotoPageFromSvg(221);
javascript:parent.gotoPageFromSvg(185);
javascript:parent.gotoPageFromSvg(278);
javascript:parent.gotoPageFromSvg(209);
javascript:parent.gotoPageFromSvg(208);
javascript:parent.gotoPageFromSvg(239);
javascript:parent.gotoPageFromSvg(267);
javascript:parent.gotoPageFromSvg(178);
javascript:parent.gotoPageFromSvg(185);
javascript:parent.gotoPageFromSvg(252);
javascript:parent.gotoPageFromSvg(211);
javascript:parent.gotoPageFromSvg(252);
javascript:parent.gotoPageFromSvg(174);
javascript:parent.gotoPageFromSvg(267);
javascript:parent.gotoPageFromSvg(174);
javascript:parent.gotoPageFromSvg(216);
javascript:parent.gotoPageFromSvg(270);
javascript:parent.gotoPageFromSvg(230);
javascript:parent.gotoPageFromSvg(199);
javascript:parent.gotoPageFromSvg(278);
javascript:parent.gotoPageFromSvg(198);
javascript:parent.gotoPageFromSvg(252);
javascript:parent.gotoPageFromSvg(167);
javascript:parent.gotoPageFromSvg(263);
javascript:parent.gotoPageFromSvg(277);
javascript:parent.gotoPageFromSvg(278);
javascript:parent.gotoPageFromSvg(209);
javascript:parent.gotoPageFromSvg(263);
javascript:parent.gotoPageFromSvg(221);
javascript:parent.gotoPageFromSvg(285);
javascript:parent.gotoPageFromSvg(209);
javascript:parent.gotoPageFromSvg(163);
javascript:parent.gotoPageFromSvg(285);
javascript:parent.gotoPageFromSvg(211);
javascript:parent.gotoPageFromSvg(198);
javascript:parent.gotoPageFromSvg(208);
javascript:parent.gotoPageFromSvg(179);
javascript:parent.gotoPageFromSvg(250);
javascript:parent.gotoPageFromSvg(178);
284 Unit 14: Enterprise Services and B2B Connectivity
285 Lesson: Analyzing Enterprise Services
302 Lesson: Configuring Business-to-Business (B2B) Connectivity
312 Unit 15: Cross-Component Business Process Management (ccBPM)
Integration Processes
313 Lesson: Analyzing the Runtime of the Cross-Component Business
Process Management (ccBPM)
318 Lesson: Identifying the Steps to Create and Use an Integration
Process
© Copyright. All rights reserved. ix
javascript:parent.gotoPageFromSvg(312);
javascript:parent.gotoPageFromSvg(323);
javascript:parent.gotoPageFromSvg(322);
javascript:parent.gotoPageFromSvg(294);
javascript:parent.gotoPageFromSvg(328);
javascript:parent.gotoPageFromSvg(294);
javascript:parent.gotoPageFromSvg(322);
javascript:parent.gotoPageFromSvg(295);javascript:parent.gotoPageFromSvg(328);
javascript:parent.gotoPageFromSvg(323);
javascript:parent.gotoPageFromSvg(323);
javascript:parent.gotoPageFromSvg(312);
javascript:parent.gotoPageFromSvg(328);
javascript:parent.gotoPageFromSvg(295);
Course Overview
TARGET AUDIENCE
This course is intended for the following audiences:
● Business Process Architect
● Business Process Owner/Team Lead/Power User
● Developer
● Development Consultant
● Enterprise Architect
● System Administrator
● System Architect
● Technology Consultant
© Copyright. All rights reserved. x
UNIT 1 SAP Process Integration
Architecture
Lesson 1
Describing SAP Process Integration Architecture 2
Lesson 2
Explaining the Functionality and Utilization of SAP Process Integration 13
UNIT OBJECTIVES
● Explain SAP Process Integration architecture
● Navigate to the System Landscape Directory (SLD)
● Navigate to the Enterprise Services Repository (ESR)
● Navigate to the Integration Builder
● Explain the use of SAP Process Integration.
© Copyright. All rights reserved. 1
https://saplearninghub.plateau.com/icontent_e/CUSTOM_eu/sap/self-managed/ebook/BIT400_EN_Col15_R1.3/xml/topic12.svg
https://saplearninghub.plateau.com/icontent_e/CUSTOM_eu/sap/self-managed/ebook/BIT400_EN_Col15_R1.3/xml/topic23.svg
Unit 1
Lesson 1
Describing SAP Process Integration
Architecture
LESSON OVERVIEW
This lesson explains how the SAP Process Integration offering processes messages. The
lesson also explains how you can connect application systems by using SAP Process
Integration.
Business Example
You want to implement business processes in a distributed system landscape. In addition,
you want to send messages as uniformly as possible when data is transferred between
systems. For this reason, you require the following knowledge:
● An understanding of SAP Process Integration architecture
● An understanding of the options available for connecting application systems to SAP
Process Integration
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Explain SAP Process Integration architecture
● Navigate to the System Landscape Directory (SLD)
● Navigate to the Enterprise Services Repository (ESR)
● Navigate to the Integration Builder
© Copyright. All rights reserved. 2
SAP Process Integration Architecture and Tools
Figure 1: Architecture of SAP Process Integration
SAP Process Integration consists of the following components and an additional installation
option:
● System Landscape Directory
This component contains information about the Landscape (Technical Systems and
Business Systems) and the Software Catalog (Product and Software Component
Versions). You can configure an SAP system to register itself in the SLD.
● Enterprise Services Repository
This component contains design objects such as interfaces, mappings, and process
definitions.
● Services Registry
This component is a Universal Description, Discovery, and Integration (UDDI) compliant
registry that lists available web service definitions (based on Web Services Description
Language (WSDL)), and is extended with a classification system.
● Integration Directory
This component enables you to configure scenarios for the message exchange.
● Business Process Engine (BPE)
This component controls message correlations and determines how messages are
processed as part of cross-component business process management (ccBPM).
● Integration Engine
Lesson: Describing SAP Process Integration Architecture
© Copyright. All rights reserved. 3
This component is a part of the Integration Server and it processes messages in the
Integration Directory according to the system configuration. This processing involves
determining the receiver and mapping the inbound message to the receiver interface
structure.
● Advanced Adapter Engine
This component provides the basis for many adapters used to connect systems to the
Integration Server.
● Runtime Workbench
This component is a tool used for central monitoring of components and messages.
SAP Process Integration UI Tools to Access the Components
Figure 2: SAP Process Integration UI Tools to Access the Components
You can use the following tools to access SAP Process Integration components:
● SAP GUI
SAP GUI is a client tool to access the ABAP stack of SAP Process Integration.
● Integration Builder
The Integration Builder tool provides the Java GUI that you use to work in the Integration
Directory. The Integration Builder also regulates versioning and lock management on the
server.
● Enterprise Services Builder
The Enterprise Services Builder tool provides the Java GUI that you use to work in the ESR.
Unit 1: SAP Process Integration Architecture
© Copyright. All rights reserved. 4
● SAP NetWeaver Developer Studio (NWDS)
The NWDS tool is the Eclipse-based Java development tool of SAP. You can use this tool to
view and edit object types in the ESR.
● Browser
In your browser, you can access configuration and monitoring, the integration directory,
and the system landscape directory (SLD).
Installation Options
Figure 3: Installation and Connectivity Options and Configuration Types
The figure, Installation and Connectivity Options and Configuration Types, shows the
installation options available in SAP Process Integration.
Lesson: Describing SAP Process Integration Architecture
© Copyright. All rights reserved. 5
System Landscape Directory
Figure 4: Mapping the System Landscape in the SLD
You enter the information on technical systems of the customer-specific system landscape in
the SLD. This information includes host names and other technical attributes, and
information about the software components installed on a server.
Note:
The structure of the SLD is based on the Common Information Model (CIM)
standard. CIM was developed by the Distributed Management Task Force (DMTF),
which is a consortium that aims to organize the administration of IT systems in
distributed landscapes.
Business systems represent the sender or receiver systems of messages. You assign a
business system name to each technical system in the SLD. For ABAP systems, you assign a
business system to each client that exchanges messages with SAP Process Integration.
Business systems are then imported into the Integration Directory.
Unit 1: SAP Process Integration Architecture
© Copyright. All rights reserved. 6
Enterprise Services Repository
Figure 5: Mapping Software Component Versions and Their Interfaces
The uniqueness of an object in the ESR is determined by the following elements:
● The name of the object
● The name of the software component
● The associated namespace
In addition to the technical and assigned business systems, the products, and their software
components and versions that run on the technical systems are also created in the SLD. The
software components are imported into the ESR. Within the software component version, you
create the namespaces in which you then store the interface objects that you use in your
business processes.
Interface objects include the inbound and outbound interfaces and details for mapping.
You can use interfaces, such as Remote Function Call (RFC), Intermediate Document (IDoc),
eXtensible Markup Language Schema Definition (XSD), or WSDL into the ESR, or you can
create them manually in the ESR.
Lesson: Describing SAP Process Integration Architecture
© Copyright. All rights reserved. 7
Mapping Interfaces and Defining Mappings
Figure 6: Mapping Interfaces and Defining Mappings
You define outbound and inbound interfaces in the ESR. If the outbound and inbound
messages in a scenario do not match, you also define mapping rules for a structure mapping
in the ESR. For this purpose, the system provides you a graphical mapping tool or you can
create mapping programs in Java, ABAP, or eXtensible Stylesheet Language Transformations
(XSLT). In addition to the structure mapping, which maps the source and inbound structures
to each other, you can also define a value mapping that mapsthe values of the structure to
the required values in the inbound structure, for example, value 001 to value abc in the
Material group field.
The ESR allows you to define the relationships between interfaces and business processes in
a transparent way. To define these relationships, you create an integration scenario that
represents the relationships between interfaces in abstract form (without the assignment of
specific systems).
Unit 1: SAP Process Integration Architecture
© Copyright. All rights reserved. 8
Implementation of a Scenario and Assignment of the Interfaces and Mappings Used
Figure 7: Implementing a Scenario and Assigning the Interfaces and Mappings Used
You can create process steps (referred to as actions) for a system with a particular role. You
can assign outbound and inbound interfaces to each of these actions. You can connect the
actions with connecting lines. You can represent synchronous and asynchronous
connections. Select an outbound interface for the sender system action and an inbound
interface for the receiver system action for each connection. You can specify a mapping
program that maps the outbound interface to the inbound interface.
Hint:
Integration scenarios and objects referenced in scenarios, such as interfaces and
mapping, are provided as the ESR or SAP Process Integration content by SAP
and its partners. These scenarios and objects can be used as configuration
templates. In this way, they simplify the implementation of standard scenarios.
Lesson: Describing SAP Process Integration Architecture
© Copyright. All rights reserved. 9
Integration Directory
Figure 8: Configuring Scenarios in the System Landscape in Integration Directory
The ESR only stores information related to the development objects of a software
component. For these objects, it is not important whether, and on which server, the software
component is installed.
To allow business processes to run in a distributed system landscape, you need the
configuration objects that you store in the Integration Directory.
Unit 1: SAP Process Integration Architecture
© Copyright. All rights reserved. 10
Configuration Objects in the Integration Directory
Figure 9: Configuration Objects in the Integration Directory
In addition to the sender and receiver (as services) and the adapters, the following
configuration objects also belong to the configuration in the Integration Directory:
● Sender agreement
● Receiver determination
● Interface determination
● Receiver agreement
Message Processing
Messages can be processed by the Integration Engine (pipeline processing), or by the
Advanced Adapter Engine (AAE), depending on the required adapters and functionality.
For processing messages by the Integration Engine, you configure how the sender technically
links up with SAP Process Integration (sender agreement) and with the receiver that receives
a message (receiver determination). You then configure which inbound interface receives the
message for the receiver (interface determination) and how the Integration Server can
technically link up with the receiver system (receiver agreement).
For processing messages by the AAE, you create an integrated configuration and maintain the
routing information in the AAE.
The Integration Directory provides an object in which you can bundle all the configuration
objects that belong together in the configuration scenario. Configuration scenarios make it
easier to use configuration objects.
Lesson: Describing SAP Process Integration Architecture
© Copyright. All rights reserved. 11
LESSON SUMMARY
You should now be able to:
● Explain SAP Process Integration architecture
● Navigate to the System Landscape Directory (SLD)
● Navigate to the Enterprise Services Repository (ESR)
● Navigate to the Integration Builder
Unit 1: SAP Process Integration Architecture
© Copyright. All rights reserved. 12
Unit 1
Lesson 2
Explaining the Functionality and Utilization of
SAP Process Integration
LESSON OVERVIEW
This lesson explains how to analyze functionality and utilization of SAP Process Integration.
Business Example
You want to implement business processes in a distributed system landscape. You want to
send messages as uniformly as possible when data is transferred between systems. For this
reason, you require the following knowledge:
● An understanding of how to use SAP Process Integration for processing messages
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Explain the use of SAP Process Integration.
Potential Uses of SAP Process Integration
The potential utilizations of SAP Process Integration are as follows:
● The architecture of SAP Process Integration is based on an established architecture for
implementing cross-system business processes and represents an enhancement of the
earlier releases.
● SAP Process Integration plays a key role in supporting service-oriented architecture (SOA)
for business applications. The focus is on a service-based integration of applications.
SOA supports the basic principles of service-oriented architecture (messaging structure,
tools for creating services, tools for consuming services, registry, and repository tools, and so
on), but it does not provide additional business logic. SAP provides the infrastructure and
executable content in the form of enterprise services that encapsulate the relevant functions
of the SAP Business Suite application.
© Copyright. All rights reserved. 13
Connecting of Application Systems to SAP Process Integration
Figure 10: Runtime Procedure – Conversion to SAP Process Integration Message Format
The Integration Engine of SAP Process Integration expects to receive an inbound message in
a specific SAP Process Integration XML format and sends messages in the SAP Process
Integration XML format to the receiver systems.
Before connecting systems, ensure that the sender system can create the message that is
sent in the SAP Process Integration XML format and the receiver system receives the
message in the SAP Process Integration XML format.
A local Integration Engine is part of SAP Basis 6.20 and later. The local Integration Engine can
directly exchange messages with SAP Process Integration based on the SAP Process
Integration XML format. The application system uses SAP Process Integration proxies for the
message exchange.
Using adapters is the other connectivity option for SAP Process Integration. The connected
system provides data in its format and the adapter converts between that format and SAP
Process Integration XML format and transfers it to SAP Process Integration message
processing.
SAP technical adapters are included with SAP Process Integration, but you can also use
adapters from SAP partners.
Unit 1: SAP Process Integration Architecture
© Copyright. All rights reserved. 14
Runtime Procedure of SAP Process Integration Pipeline Processing
Figure 11: Runtime Procedure – Pipeline
Processing begins in the Integration Server pipeline as soon as a message reaches the
Integration Server in the SAP Process Integration message format. First, the configuration
data determines the receiver and the receiver inbound interface. This step is called logical
routing. If there are multiple receivers, the system duplicates the message. 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 to
contact the receiver. This is called technical routing. Finally, the system sends the message to
the target system or corresponding adapter.
Lesson: Explaining the Functionality and Utilization of SAP Process Integration
© Copyright. All rights reserved. 15
Building Blocks of SOA
Figure 12: Building Blocks of SOA
In an application that uses enterprise services, SAP Process Integration acts as an Enterprise
Service Bus at runtime to facilitate the exchange of calls between the various services.
Interfaces are centrally stored inthe Enterprise Services Repository (ESR).
Hint:
SAP Process Integration and SAP Composition Environment use the ESR.
LESSON SUMMARY
You should now be able to:
● Explain the use of SAP Process Integration.
Unit 1: SAP Process Integration Architecture
© Copyright. All rights reserved. 16
Unit 1
Learning Assessment
1. Which of the following tools are used to access the SAP Process Integration components?
Choose the correct answers.
X A SAP NetWeaver Developer Studio
X B Enterprise Services Builder
X C Integration Builder
X D Workflow Builder
2. __________ systems represent the sender and receiver systems of messages.
Choose the correct answer.
X A Business
X B Technical
X C ABAP
3. What are the elements that determine the uniqueness of an object in the Enterprise
Service Repository?
Choose the correct answers.
X A The name of the object
X B The name of the software component with which the object is associated
X C The associated namespace
X D The number of objects
4. You can use _________ to bundle all the configuration objects that belong to a single
interface scenario.
Choose the correct answer.
X A configuration scenario
X B Advanced Adapter Engine
X C Integration Engine
© Copyright. All rights reserved. 17
5. SAP Process Integration acts as an Enterprise Service Bus at runtime to facilitate the
exchange of calls between various services.
Determine whether this statement is true or false.
X True
X False
Unit 1: Learning Assessment
© Copyright. All rights reserved. 18
Unit 1
Learning Assessment - Answers
1. Which of the following tools are used to access the SAP Process Integration components?
Choose the correct answers.
X A SAP NetWeaver Developer Studio
X B Enterprise Services Builder
X C Integration Builder
X D Workflow Builder
2. __________ systems represent the sender and receiver systems of messages.
Choose the correct answer.
X A Business
X B Technical
X C ABAP
3. What are the elements that determine the uniqueness of an object in the Enterprise
Service Repository?
Choose the correct answers.
X A The name of the object
X B The name of the software component with which the object is associated
X C The associated namespace
X D The number of objects
© Copyright. All rights reserved. 19
4. You can use _________ to bundle all the configuration objects that belong to a single
interface scenario.
Choose the correct answer.
X A configuration scenario
X B Advanced Adapter Engine
X C Integration Engine
5. SAP Process Integration acts as an Enterprise Service Bus at runtime to facilitate the
exchange of calls between various services.
Determine whether this statement is true or false.
X True
X False
Unit 1: Learning Assessment - Answers
© Copyright. All rights reserved. 20
UNIT 2 The System Landscape
Directory (SLD)
Lesson 1
Maintaining Products and Software Components in the System Landscape Directory (SLD) 22
Lesson 2
Implementing Technical Systems in the System Landscape Directory 28
Lesson 3
Maintaining Business Systems for Use in the Integration Directory 35
UNIT OBJECTIVES
● Use product and software components terminology
● Create products and software components in the System Landscape Directory (SLD)
● Import software components from the System Landscape Directory (SLD) into the
Enterprise Service Registry (ESR)
● Implement technical systems in the System Landscape Directory (SLD)
● Register SAP NetWeaver Application Server for ABAP in the System Landscape Directory
(SLD)
● Maintain the SAP NetWeaver Application Server for Java in the System Landscape
Directory (SLD)
● Create third-party technical systems in the System Landscape Directory (SLD)
● Maintain a business system in the System Landscape Directory (SLD)
● Import a business system into the System Landscape Directory (SLD)
© Copyright. All rights reserved. 21
https://saplearninghub.plateau.com/icontent_e/CUSTOM_eu/sap/self-managed/ebook/BIT400_EN_Col15_R1.3/xml/topic32.svg
https://saplearninghub.plateau.com/icontent_e/CUSTOM_eu/sap/self-managed/ebook/BIT400_EN_Col15_R1.3/xml/topic45.svg
https://saplearninghub.plateau.com/icontent_e/CUSTOM_eu/sap/self-managed/ebook/BIT400_EN_Col15_R1.3/xml/topic38.svg
Unit 2
Lesson 1
Maintaining Products and Software
Components in the System Landscape
Directory (SLD)
LESSON OVERVIEW
This lesson explains how you can map software components in the System Landscape
Directory (SLD) and integrate these components into the Enterprise Services Repository
(ESR). In addition, this lesson describes which interface objects you can create within the
software component version.
Business Example
Your integration scenario is based on a system landscape that consists of multiple servers
and on which software is installed. SAP Process Integration requires essential information
relating to these software components. The SLD stores this information centrally. For this
reason, you require the following knowledge:
● An understanding of SAP product and software components in the SLD
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Use product and software components terminology
● Create products and software components in the System Landscape Directory (SLD)
● Import software components from the System Landscape Directory (SLD) into the
Enterprise Service Registry (ESR)
Software Components
Technically, a software component is a modular entity that you can implement in multiple
products.
Software components are subject to further development, which results in various software
component versions.
Product and Software Components Definition
A product is a grouping of independent 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 or the addition of further software components if any functional
enhancements are made to the product. In most cases, each product has multiple product
versions. For example, the SAP Customer Relationship Management (SAP CRM) application
has product versions SAP CRM 4.0, 5.0, 7.0 and more.
In an ABAP system, one or more software components are assigned to a product. The
software components may have various versions.
© Copyright. All rights reserved. 22
Product versions are software units that you can install on your system and that run
independently of other software (for example, SAP ERP 6.0).
Product Instance
Figure 13: Products and Software Components
In the SLD, an independent object that is known as software feature represents the
relationship between the product version and the software component versions. This
construct of the software feature enables you to represent complex products. In contrast to
the products and software components versions that are visible in the SLD, the software
features are not based on any visible objects.
Hint:
You can access the SLD in various ways. In an ABAP back end, you may use
transaction SLDHTMLGUI to connect to the SLD.
Lesson: Maintaining Products and Software Components in the System Landscape Directory (SLD)
© Copyright. All rights reserved. 23
Example of a Product and Software Component
Figure 14: Example of a Product and Software Component
To display the products and software components along with their versions in the SLD,
choose Software Catalog from the SLD initial screen.
You can import SAP products and SAP software components into the SLD. Your
administrator does this after installing SAP Process Integration. SAP Service Marketplace
also provides the latest updates and you should import these updates twice a year.
If you use non-SAP software components and products, create them manually in the SLD.
Unit 2: The System Landscape Directory (SLD)
© Copyright. All rights reserved. 24
Software Components with External Interfaces
Figure 15: Software Component with External Interfaces
Each software component provides programs for particular functions. Software components
have external interfacesto enable them to communicate with other software components.
These interfaces can be both inbound and outbound.
Examples of SAP Inbound Interfaces
● The BAPI programming interfaces and remote-function modules (RFMs)
● File interfaces
● Inbound Intermediate Document (IDoc) interfaces
● XML interfaces (SAP Basis 6.20 or higher)
● Java or ABAP inbound proxies (SAP Basis 6.20 or higher)
● Web services
● Enterprise services
Outbound interfaces cannot all be described by one object, they exist implicitly.
Examples of SAP Outbound Interfaces
● File interfaces in the form of a program that creates a file
● IDoc outbound interfaces
● Remote Function Call (RFC) outbound interfaces in the form of a program that starts 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
Lesson: Maintaining Products and Software Components in the System Landscape Directory (SLD)
© Copyright. All rights reserved. 25
● Java or ABAP outbound proxies (SAP Basis 6.20 or higher)
● SAP Process Integration outbound proxies
Software Components and Interface in the ESR
Figure 16: SLD Interface in the ESR
Detailed information about the external interfaces of a software component is stored in the
ESR within the software component version.
In the ESR, you first import the software components from the SLD. Then you create the
namespaces in the software component version and use the namespace for the interfaces.
A namespace semantically groups objects, in a similar way to ABAP packages (previously
called development classes) and Java packages. Namespaces must be globally unique, and
not just for software components; they make interface objects uniquely identifiable.
Conventions for Creating Namespaces
You can use the following conventions for creating namespaces:
● Prefix http://
When you specify an HTTP address as a namespace, the HTTP address used ensures that
the name of the namespace is unique. This specification does not mean that you can
access additional information about the namespace from this address (in some cases an
XML schema definition is hidden behind the address). SAP namespaces follow the
standard http://sap.com/xi/ .
● Prefix urn:
Namespaces with these types of prefix have no value because they are not connected with
a web page on the Internet.
Unit 2: The System Landscape Directory (SLD)
© Copyright. All rights reserved. 26
http://sap.com/xi/
Caution:
It is assumed that conventions ensure that namespaces are unique. For more
information about namespaces, go to www.w3.org/TR/REC-xml-names (Url was
checked in April, 2013) .
Within a namespace, the Enterprise Services Builder allows you to maintain objects in
different areas. These include SAP Process Integration scenario objects, modeling objects in
the Enterprise Services Builder area, interface objects, mapping objects, adapter objects, as
well as objects that identify a work area, in other words, software components, and
namespaces.
The key objects of an interface in the interface objects area are service interfaces, together
with the corresponding service operations, message types, and data types.
LESSON SUMMARY
You should now be able to:
● Use product and software components terminology
● Create products and software components in the System Landscape Directory (SLD)
● Import software components from the System Landscape Directory (SLD) into the
Enterprise Service Registry (ESR)
Lesson: Maintaining Products and Software Components in the System Landscape Directory (SLD)
© Copyright. All rights reserved. 27
Unit 2
Lesson 2
Implementing Technical Systems in the
System Landscape Directory
LESSON OVERVIEW
This lesson describes how to implement technical systems in the System Landscape
Directory (SLD).
Business Example
You have a heterogeneous system landscape with multiple servers and various software
components. To implement a business process in the system landscape, you need to analyze
the technical properties of the various systems and the application components that are
installed. For this reason, you require the following knowledge:
● An understanding of how to display technical systems in the SLD and check their
attributes
● An understanding of how SAP systems can register with the SLD
● An understanding of how to manually create a technical system in the SLD and assign
products and software components
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Implement technical systems in the System Landscape Directory (SLD)
● Register SAP NetWeaver Application Server for ABAP in the System Landscape Directory
(SLD)
● Maintain the SAP NetWeaver Application Server for Java in the System Landscape
Directory (SLD)
● Create third-party technical systems in the System Landscape Directory (SLD)
© Copyright. All rights reserved. 28
System Types
Figure 17: SLD: Technical Systems
In addition to information about products and software components, you can also enter
technical and business systems in the SLD. There are various types of technical systems. The
type of technical system determines the attributes you must enter. From the SLD initial
screen, follow the Technical Systems link to access the definition of the technical systems.
The system navigates to a screen where you can select a system type. The system then
displays a list of technical systems for the selected system type.
Lesson: Implementing Technical Systems in the System Landscape Directory
© Copyright. All rights reserved. 29
SAP System: Technical View
Figure 18: Example – SAP System (Technical View)
You 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 feature that is unique to the ABAP-based SAP
system is that in addition to the typical attributes, you can also have numerous clients. From a
business perspective, you can view these clients as separate systems.
The products and software components are assigned at the system level because
development objects in SAP systems are not client-specific.
Unit 2: The System Landscape Directory (SLD)
© Copyright. All rights reserved. 30
SAP NetWeaver Application Server for ABAP in the System Registraion
Figure 19: Definition of the Data Supplier Bridge in SLD
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, specify the
Remote Function Call (RFC) gateway on which you register.
Data Supplier for SAP Systems (ABAP)
Figure 20: Data Supplier for SAP Systems (ABAP)
Lesson: Implementing Technical Systems in the System Landscape Directory
© Copyright. All rights reserved. 31
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. The selection of data
collection programs allows you to control which data is collected and transferred. An RFC
destination SLD_UC or SLD_NUC is automatically created for transfers. The data collected is
transferred by the RFC connection through the gateway to the data supplier bridge, and is
then imported into the SLD.
Configuring of the Data Supplier (ABAP) – Transaction RZ70
Figure 21: Configuring of the Data Supplier (ABAP) – Transaction RZ70
Hint:
With SAP ERP 6.04 and later, transaction RZ70 also collects information about
the product version of the system.
Unit 2: The System Landscape Directory (SLD)
© Copyright. All rights reserved. 32
SAP NetWeaver Application Server for Java Registration
Figure 22: Data Suppliers for SAP NetWeaver AS for Java Systems
The Java component SLD data supplier is deployed and started for the Data Suppliers for SAP
NetWeaver AS for Java Systems server (formerly known as the SAP Java 2 Platform,
Enterprise Edition SAP J2EE engine). The necessaryparameters are passed to this Java
service using the SAP NetWeaver Administrator (NWA) tool.
Refreshing the data of the Java server (such as host, installed software components, and so
on) is done each time the machine restarts, and the data is imported into the SLD using the
data supplier bridge.
To Register a Java Server in the SLD
Perform the following steps to register a Java server in the SLD:
1. Log on to the Java server with NWA system (http://<server>.<domain>:<port>/nwa).
2. Choose Configuration→ Infrastructure→ Destinations.
3. Choose SLD DATA Supplier Service and maintain the following data on the HTTP Settings
tab page:
a) Set the appropriate URL to http://host:port .
b) Set the authentication to basic.
c) Set the appropriate user name and password.
Note:
The specified user must have the user role SAP_SLD_DATA_SUPPLIER or
higher on the target SLD Server.
d) Save the data.
4. In the menu, choose Go To→ Configuration→ Infrastructure→ SLD Data Supplier
Configuration.
5. Choose the Collect and Send Data pushbutton.
Lesson: Implementing Technical Systems in the System Landscape Directory
© Copyright. All rights reserved. 33
A successful data transfer message is displayed and you see the system in SLD.
Example of a Technical System Landscape
Figure 23: Technical System Landscape of the Example Scenario
The figure, Technical System Landscape of the Example Scenario, shows the system
landscape for the Create Technical Systems in the System Landscape Directory exercise.
The system landscape consists of two third-party type application systems and client 800 of
the SAP Process Integration system, which is configured as the Integration Server. The
system exchanges data using SAP Process Integration. Therefore, the network connections
and communication channels are configured at the same time as the system landscape.
LESSON SUMMARY
You should now be able to:
● Implement technical systems in the System Landscape Directory (SLD)
● Register SAP NetWeaver Application Server for ABAP in the System Landscape Directory
(SLD)
● Maintain the SAP NetWeaver Application Server for Java in the System Landscape
Directory (SLD)
● Create third-party technical systems in the System Landscape Directory (SLD)
Unit 2: The System Landscape Directory (SLD)
© Copyright. All rights reserved. 34
Unit 2
Lesson 3
Maintaining Business Systems for Use in the
Integration Directory
LESSON OVERVIEW
This lesson explains why technical systems are assigned a name (the business system),
which is used for configuration. The lesson shows how to create business systems in the
System Landscape Directory (SLD) and import them into the Integration Directory. It also
explains how you add important information, such as communication channels in the
Integration Directory.
Business Example
You 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 changing the configuration of your business
processes. Systems are therefore given logical names, which are used for process
configuration. For this reason, you require the following knowledge:
● An understanding of how to create a business system in the SLD and assign it to a
technical system
● An understanding of how to import a business system into the Integration Directory
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Maintain a business system in the System Landscape Directory (SLD)
● Import a business system into the System Landscape Directory (SLD)
© Copyright. All rights reserved. 35
Business Systems
Figure 24: Assigning Business Systems
You want to map business processes in a distributed system landscape, and you want the
mapping to be independent of changes to the physical servers of the systems involved. For
this reason, you assign a business system name to the technical systems in the SLD. 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 in which business systems. A business system must be assigned to each technical
system at configuration time at the latest.
When you implement a business process in a distributed system landscape, you determine
the business system in which the particular process step runs and which software component
executes the process steps. If the business system changes between two consecutive
process steps, the sender software component must provide all the data. This data is
required for the subsequent process step with 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 SAP Process Integration
(SAP PI) is used to integrate the systems, the document is converted from the format in
which it is sent into an SAP Process Integration XI-Message Protocol, an XML based message
format. Within SAP Process Integration, 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.
Unit 2: The System Landscape Directory (SLD)
© Copyright. All rights reserved. 36
Business Systems in the SLD
Figure 25: SLD – Business Systems
To define and display the business systems in the SLD, choose the Business systems link on
the initial screen of the SLD, and choose New Business System or select an entry in the list of
existing business systems. Note that you can also apply filters to retrieve a limited list of
defined business systems.
To Create a Business System
Perform the following tasks to create a business system in the SLD:
1. Navigate to the list of business systems ( Landscape/Business Systems ).
2. Choose New Business System .
3. Select the type of the underlying technical system (for example, Third Party).
4. Select the technical system on which the business system is based. You have the option of
entering the logical system name if Application Link Enabling (ALE) is to be used.
5. Enter the name of the new business system.
6. Specify which products and software component version (SWCV) you want to make
available to the business system.
7. Specify the assigned Integration Server.
After creating the business system in the SLD, you can import it into Integration Directory.
Lesson: Maintaining Business Systems for Use in the Integration Directory
© Copyright. All rights reserved. 37
SLD Interface for the Integration Directory
Figure 26: SLD Interface for the Integration Directory
The figure, SLD Interface for the Integration Directory, illustrates the interface between the
SLD and the Integration Directory.
LESSON SUMMARY
You should now be able to:
● Maintain a business system in the System Landscape Directory (SLD)
● Import a business system into the System Landscape Directory (SLD)
Unit 2: The System Landscape Directory (SLD)
© Copyright. All rights reserved. 38
Unit 2
Learning Assessment
1. Product versions are software units that can be installed on your system and do not run
independently of other software.
Determine whether this statement is true or false.
X True
X False
2. You choose _________ on the System Landscape Directory initial screen to display the
products and software components along with their version.
Choose the correct answer.
X A Software Catalog
X B Technical Systems
X C Business Systems
3. The Enterprise Service Repository within the software component version stores detailed
information about the _______ of a software component.
Choose the correct answer.
X A external interfaces
X B internal interface
4. Which of the following technical system types can you enter in the SLD? Select all that
apply.
Choose the correct answers.
X A AS ABAP
X BAS JAVA
X C TREX
X D Third-party systems
© Copyright. All rights reserved. 39
5. The products and software components are assigned at the system level because
__________.
Choose the correct answer.
X A development objects in SAP systems are not client-specific
X B development objects in SAP systems are client-specific
X C training objects in SAP systems are not client-specific
6. The Java component SLD data supplier is deployed and started for the SAP NetWeaver AS
Java server.
Determine whether this statement is true or false.
X True
X False
7. Each time data is transferred between two systems, identify the ________ interface and
the ________ interface.
Choose the correct answer.
X A sender outbound, receiver inbound
X B receiver outbound, sender outbound
X C receiver outbound, sender inbound
X D receiver inbound, sender inbound
8. When using a single System Landscape Directory for your entire system landscape, define
groups of ______________________ so that you can map and manage each part of your
system landscape independently.
Choose the correct answer.
X A technical systems and transport targets
X B business systems and transport targets
X C communication channels and transport targets
Unit 2: Learning Assessment
© Copyright. All rights reserved. 40
Unit 2
Learning Assessment - Answers
1. Product versions are software units that can be installed on your system and do not run
independently of other software.
Determine whether this statement is true or false.
X True
X False
2. You choose _________ on the System Landscape Directory initial screen to display the
products and software components along with their version.
Choose the correct answer.
X A Software Catalog
X B Technical Systems
X C Business Systems
3. The Enterprise Service Repository within the software component version stores detailed
information about the _______ of a software component.
Choose the correct answer.
X A external interfaces
X B internal interface
4. Which of the following technical system types can you enter in the SLD? Select all that
apply.
Choose the correct answers.
X A AS ABAP
X B AS JAVA
X C TREX
X D Third-party systems
© Copyright. All rights reserved. 41
5. The products and software components are assigned at the system level because
__________.
Choose the correct answer.
X A development objects in SAP systems are not client-specific
X B development objects in SAP systems are client-specific
X C training objects in SAP systems are not client-specific
6. The Java component SLD data supplier is deployed and started for the SAP NetWeaver AS
Java server.
Determine whether this statement is true or false.
X True
X False
7. Each time data is transferred between two systems, identify the ________ interface and
the ________ interface.
Choose the correct answer.
X A sender outbound, receiver inbound
X B receiver outbound, sender outbound
X C receiver outbound, sender inbound
X D receiver inbound, sender inbound
8. When using a single System Landscape Directory for your entire system landscape, define
groups of ______________________ so that you can map and manage each part of your
system landscape independently.
Choose the correct answer.
X A technical systems and transport targets
X B business systems and transport targets
X C communication channels and transport targets
Unit 2: Learning Assessment - Answers
© Copyright. All rights reserved. 42
UNIT 3 Interface Objects in the
Enterprise Service
Repository (ESR)
Lesson 1
Listing Options for Navigating the Enterprise Services Repository (ESR) 44
Lesson 2
Analyzing Interface Objects in the Enterprise Services Repository (ESR) 49
Lesson 3
Maintaining Interface Objects 58
Lesson 4
Defining Message Processing Types and Quality of Services 62
UNIT OBJECTIVES
● Use the Enterprise Services Repository (ESR) as part of SAP Composition Environment
and SAP Process Integration
● Access the Enterprise Services Repository (ESR) objects
● Search the Enterprise Services Repository (ESR) objects
● Display data types
● Display message types
● Display the service interfaces
● Display context objects
● Create interface objects
● Import interface objects in the Enterprise Services Repository (ESR)
● Define the quality of service (QoS) and message processing types
© Copyright. All rights reserved. 43
https://saplearninghub.plateau.com/icontent_e/CUSTOM_eu/sap/self-managed/ebook/BIT400_EN_Col15_R1.3/xml/topic68.svg
https://saplearninghub.plateau.com/icontent_e/CUSTOM_eu/sap/self-managed/ebook/BIT400_EN_Col15_R1.3/xml/topic54.svg
https://saplearninghub.plateau.com/icontent_e/CUSTOM_eu/sap/self-managed/ebook/BIT400_EN_Col15_R1.3/xml/topic59.svg
https://saplearninghub.plateau.com/icontent_e/CUSTOM_eu/sap/self-managed/ebook/BIT400_EN_Col15_R1.3/xml/topic72.svg
Unit 3
Lesson 1
Listing Options for Navigating the Enterprise
Services Repository (ESR)
LESSON OVERVIEW
This lesson describes how to list navigation options for the Enterprise Services Repository
(ESR).
Business Example
Your company plans to implement SAP Process Integration. You want to understand the ESR
architecture so that you can design and manage the enterprise service. For this reason, you
require the following knowledge:
● An understanding of the navigation options available in the ESR
● An understanding of the ESR objects
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Use the Enterprise Services Repository (ESR) as part of SAP Composition Environment
and SAP Process Integration
● Access the Enterprise Services Repository (ESR) objects
● Search the Enterprise Services Repository (ESR) objects
ESR for SAP Composition Environment and SAP Process Integration
Figure 27: One Central ESR for Multiple SAP PI Domains
The figure shows one central ESR for multiple SAP PI domains.
© Copyright. All rights reserved. 44
Usage Profile
The ESR is a development environment where many users achieve goals based on their
requirements. The ESR is the central access point for users to develop services and provides
access to the development of cross-component processes based on the exchange of XML
messages. The ESR caters to a variety of users, therefore it contains many models and design
time objects. However, only a small subset of these objects may be of interest to different
user groups.
The ESR provides the functionality to adapt the environment to your needs. Depending on
your requirements, you can have a subset of objects from the ESR, which helps to reduce the
complexity of the tool.
The usage profile defines the set of object types, software component versions, and business
modeling filters that you can use. Usage profiles are personalized filters that enable you to
view and work with only a set of object types, software component versions, and modeling
filters required to achieve your goals. All the other object types are hidden.
In the Enterprise Services Builder, you can choose from a set of predefined usage profiles
delivered by SAP. However, if these profiles do not meet your requirements, you can create
your own usage profile.
Standard Usage Profiles
Based on common usage of various user groups or roles, SAP delivers three predefined usage
profiles.
You can choose any of the following standard usage profiles available in the Enterprise
Services Builder:
● Service Development
This basic selection facilitates modeling and interface development.
● Process Integration
This basic selection facilitates the modeling of cross-component processes and the
development of interfaces, mappings, and adapter objects.
● Unrestricted
This basic selection contains all the object types available in the Service Development and
Process Integration usage profiles.
When you log on to the Enterprise Services Builder for the first time, you can choose a usage
profile based on your requirements. However, you can always change this selection later in
the Enterprise Services Builder.
Context Perspective
The contextperspective in the Enterprise Services Builder provides improved access to
objects and better navigation capabilities, and allows you to work with a subset of objects of
your choice.
In the context perspective view, you can perform the same set of operations as with the
classic view.
You can use the context perspective to perform the following tasks:
● Access recently used objects.
Lesson: Listing Options for Navigating the Enterprise Services Repository (ESR)
© Copyright. All rights reserved. 45
To access objects that you recently created, edited, and viewed, expand the Work Context
node under My Workplace.
● Create folders based on filter criteria.
● Access information from multiple user interfaces on one user interface.
● To view the referenced objects and where-used list for a specific object, select an object
from My Workplace or My Work History and expand the References node.
● To view the properties of an object, select an object from My Workplace or My Work
History and expand the Properties node.
● To switch to the design objects, change list, or conflicts tab page, choose the required
option from the tool bar on the left.
● To locate the opened object in the navigation tree of My Workplace, choose Work Context
with Editor.
● Run applications using widgets.
To run specific applications, choose ES Repository Widgets → Add or Customize Widgets
and select the required widget.
Object Search
To access objects that you recently created, edited, and viewed, expand the Work Context
node under My Workplace.
To define a folder based on specific filter criteria, such as software component version,
namespace, object type, or object name, perform the following steps:
1. Select the Search Folders node under My Workplace.
2. In the context menu, choose New Search Folder .
3. Enter a name for the search folder.
4. If you want to filter objects based on object names, enter the object name in the Object
Filter field.
5. Select the required software component versions and namespaces on which you want to
define search filters.
6. For the software component versions and namespaces selected in step 5, select the
corresponding object types on which you want to define search filters.
7. Choose Create .
To view the referenced objects and where-used list for a specific object, perform the following
steps:
1. Select an object from My Workplace or My Work History.
2. Expand the References node.
To run specific applications, perform the following steps:
1. Choose ES Repository Widgets .
2. Choose Add or Customize Widgets and select the required widget.
Unit 3: Interface Objects in the Enterprise Service Repository (ESR)
© Copyright. All rights reserved. 46
Objects Search by Documentation
Once you have browsed for services in the Enterprise Services Workplace (ES Workplace),
you can search for the required objects in the ES Workplace based on the documentation.
You use this feature to search for objects in the ESR to ensure reuse of objects.
To search for an object by transferring the documentation URL from the ES Workplace,
perform the following steps:
1. Log on to ES Builder.
2. Choose Perspective→ Select Perspective→ Context.
3. Choose ES Repository Widgets .
4. Choose Add or Customize Widgets and select Search by Documentation .
To search for an object in the ESR, move a documentation link from ES Workplace to the
assigned area on the widget.
Subscriptions
In the Enterprise Services Builder, you subscribe to an interface object if you want to receive
e-mails of changes made to the object. You receive notifications when an interface object is
modified or deleted. For service interfaces, you can also choose to receive notifications when
you classify or publish a service interface.
Perform the following steps to subscribe to notifications in the context menu of an interface
object:
1. Choose Manage Subscription.
The New Subscription dialog box appears.
2. In the Notification Event section, select the events for which you want to receive
notifications.
3. To receive an e-mail notification, specify a valid e-mail address.
4. Choose OK.
Perform the following steps to unsubscribe to notifications in the context menu of an
interface object:
1. Choose Perspective → Select Perspective→ Context.
2. Choose ES Repository Widgets .
3. Choose Add or Customize Widgets and select My Subscriptions.
4. Select the subscription you want to unsubscribe and choose Unsubscribe in the context
menu.
5. Confirm the popup.
Note:
Context perspective, Search based on documentation, and Subscribing for
objects are new features for SAP NetWeaver 7.3.
Lesson: Listing Options for Navigating the Enterprise Services Repository (ESR)
© Copyright. All rights reserved. 47
LESSON SUMMARY
You should now be able to:
● Use the Enterprise Services Repository (ESR) as part of SAP Composition Environment
and SAP Process Integration
● Access the Enterprise Services Repository (ESR) objects
● Search the Enterprise Services Repository (ESR) objects
Unit 3: Interface Objects in the Enterprise Service Repository (ESR)
© Copyright. All rights reserved. 48
Unit 3
Lesson 2
Analyzing Interface Objects in the Enterprise
Services Repository (ESR)
LESSON OVERVIEW
This lesson describes how to analyze and understand interface objects in the Enterprise
Services Repository (ESR).
Business Example
You are responsible for developing new ESR objects and understanding the existing ESR
objects for an interface in your organization. For this reason, you require the following
knowledge:
● An understanding of data types, message types, service interface, and context objects
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Display data types
● Display message types
● Display the service interfaces
● Display context objects
Data Types
Data types are the basic components of interfaces. Data types define simple or complex XML
data structures that you create or import in a data type editor.
With SAP Process Integration, you determine the structure of data types based on their
classification.
The various data types are as follows:
● Freely modeled data types
● Core data types (CDTs)
● Aggregated data types
SAP uses CDTs and aggregated data types to create the signature of enterprise services.
The modeling of CDTs and aggregated data types is based on the United Nations Centre for
Trade Facilitation and Electronic Business (UN/CEFACT) Core Component Technical
Specification (CCTS) or CCTS for short (see also ISO 15000-5). The methodology formulated
by the UN/CEFACT committee defines semantic modules (core component types)
independently of syntax, which take account of the current requirements for the generic
description of business data. The implementation of this methodology facilitates the
© Copyright. All rights reserved. 49
realization of cross-company processes. In SAP, a CDT defines a primary component (also
referred to as a content component) and one or more optional supplementary components.
The character of a CDT is defined using a representation term (for example, Amount). Unlike
freely modeled data types, CDTs also contain additional information about the semantics of
data types. SAP currently identifies 25 representation terms for CDT (for example, Amount,
Text, Identifier, Date, Time, Name, and Description).
Caution:
The representation term of a CDT defines semantics for a more accurate
characterization of the data type, but does not yet define business-relevant
semantics with a specific reference to business processes. For example, the
characterization of a data type with the Amount representation term indicates
that the value of this type must also be specified more precisely with a currency.
This type of mandatory characterization does not apply to free modeling of this
category of data type as an XML Schema Definition (XSD) type (for example,
xsd:decimal).
Global Data Type (GDT)
The business semantics are contained in the SAP Global Data Type (GDT). GDTsare based on
CDTs, and are used across SAP as a basis for application-specific data types. However, in
contrast to the former categories of data type, GDTs are not intended for a specific usage. A
GDT is designed to be reused later in many different application scenarios. GDTs are
therefore rather broad, and need to be refined when they come to be used in a specific
application. CDTs are not application-specific, and are therefore also described as context-
free.
SAP creates a GDT as a CDT or aggregated data type in the ESR. This creation depends on
whether the GDT merely enhances a CDT with business semantics, or whether CDTs (and any
aggregated data types that may already exist) are used in a new, aggregated data type.
Message Types
The message type describes the structure of a message that SAP Process Integration sends
or receives and determines the root element of the message. The message type references a
single and complex data type and can be used for both outbound and inbound service
interfaces.
An XSD version of the message type is provided in the ESR for the export of the interface.
Unit 3: Interface Objects in the Enterprise Service Repository (ESR)
© Copyright. All rights reserved. 50
Service Interface
Figure 28: Service Interface and Service Operation
In contrast to the message interfaces in SAP Process Integration 7.0 and lower, you use a
service interface to describe operations that you need for a subsequent implementation in the
application system, independently of a platform or programming language.
Note:
With SAP Process Integration 7.3, you can create some interface objects in the
SAP NetWeaver Developer Studio (NWDS). You can create service interfaces,
data types, and message types using the ESR view in the Enterprise Services
Browser. A new feature for this version is that you can activate or reject changes
of a pending change in SAP NWDS.
A service interface is a structured element and contains one or more service operations. The
service operations reference one or more message types (request or response in the case of
synchronous operations), and thus also the description of the inbound or outbound
messages. A service operation represents the service interface and its interface as a whole,
uses attributes to describe the type of interface used, and distinguishes between inbound and
outbound interfaces.
If you use the interface in an integration process, then it becomes an interface with the
abstract attribute. This attribute has no direction (outgoing or inbound) but represents the
placeholder of the message in the integration process.
Lesson: Analyzing Interface Objects in the Enterprise Services Repository (ESR)
© Copyright. All rights reserved. 51
You can define fault message types for application error messages and reference them in
synchronous interfaces.
Hint:
Asynchronous inbound interfaces can also reference a fault message type, in
which case the application error persists in the target system.
Nested Structure
Figure 29: Enterprise Services Repository – Service Interface, Service Operation, Message Type, and Data Types
The figure shows different interface objects in the ESR.
Unit 3: Interface Objects in the Enterprise Service Repository (ESR)
© Copyright. All rights reserved. 52
Data Type and Message Type
Figure 30: Data Type and Message Type
Interface objects are presented in a specific sample scenario in the figure.
Specific Interface Objects
The following objects are created in the ESR for the SC_BIT400_A software component:
● A service interface and service operation of the outbound and asynchronous type that
references the MT_Material message type
● A message type MT_Material that references the nested data type DT_Material
● An elementary data type DT_MaterialID
● A simply structured data type DT_MaterialDescription that contains the two string-like
fields Language and Description
● A nested data type that contains the required entry field, an optional field, and a structured
element defined by using the data type DT_MaterialDescription
Note:
This structured element is optional because the attribute MinOccurs = 0; the
number of occurrences is not restricted because the attribute MaxOccurs =
unbounded.
Lesson: Analyzing Interface Objects in the Enterprise Services Repository (ESR)
© Copyright. All rights reserved. 53
XML Structure of the Source Document
Figure 31: XML Structure of the Source Document
The figure shows an example XML structure of the source document.
Example of a Message with Multiple Nodes
Figure 32: Message Type with Multiple Nodes
The 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. The term "node" means structure in an XML document.
Unit 3: Interface Objects in the Enterprise Service Repository (ESR)
© Copyright. All rights reserved. 54
XML Structure of the Target Document
Figure 33: XML Structure of the Target Document
The figure shows an example of the XML structure of a target document.
Interface Objects and Web Service Description Language (WSDL)
Figure 34: Interface Objects and WSDL
The interface is available as a WSDL file for exporting interfaces. In the WSDL file, message
types become message elements, data types become type elements, and the interface itself
becomes a port element.
Lesson: Analyzing Interface Objects in the Enterprise Services Repository (ESR)
© Copyright. All rights reserved. 55
Context Objects
Context objects are elements within the interface definitions.
Take an example where a message InvoiceOut contains the address of a customer.
In this scenario, you can use the expression /InvoiceOut/customerData/address/postalCode
in XPath to access the contents of a field such as postalCode, which is stored in the address of
customerData and which belongs to the InvoiceOut message. If you need this expression in
several conditions, then you must type it or copy it every time.
Alternatively, you can assign a context object to the postalCode field, for example with the
name PostalCode. In all conditions where you need the field value, you can use PostalCode
from the context object, so that these conditions are more readable.
Context Objects in the ESR and Their Assignment
Figure 35: Context Objects in the ESR and Their Assignment
Context objects encapsulate the XPath expression with which you access the contents of the
field. Context objects represent a comfortable alternative to XPath expressions for accessing
message contents.
Hint:
The context object is used for typical key fields and has a business-related or
meaningful name. You can reference a context object in several interfaces to
clarify which different interface fields correspond to the same business content.
Unit 3: Interface Objects in the Enterprise Service Repository (ESR)
© Copyright. All rights reserved. 56
After you have created a context object in the ESR and assigned it to the field of a request
message (Context Object tab page in the service interface), you can use this context object in
the following situations:
● To determine the receiver of a message depending on its content
● To process the process steps depending on the content of a message
There is a range of predefined technical context objects to enable you to access the message
header information.
LESSON SUMMARY
You should now be able to:
● Display data types
● Display message types
● Display the service interfaces
● Display context objects
Lesson: Analyzing Interface Objects in the Enterprise Services Repository (ESR)
© Copyright. All rights reserved. 57
Unit 3
Lesson 3
Maintaining Interface Objects
LESSON OVERVIEW
This lesson explains the methods for creating interface objects.
Business Example
As an ABAP developer, you need to maintain interface objects in the Enterprise Services
Repository (ESR). Therefore, you need to create and import interface objects within the