SAP Exchange

Infrastructure

B2B and Industry Standards

1
 Agenda

Topics
Introduction to SAP XI 3.0

System Landscape Directory

Integration Repository

Integration Directory

Monitoring

Adapter Framework

Business Process Management

Server Administration

Security

B2B and Industry Standards

© SAP AG 2004, B2B Industry Standards / 2

2
 B2B and Industry Standards : Objectives

After completing this lesson, you will be able to:

z Explain the XI Infrastructure for supporting B2B
scenarios and Industry Standards.
z Describe the configuration objects to use for
implementing B2B scenarios.
z Describe SAP Business Packages for Industry.

© SAP AG 2004, B2B Industry Standards / 3

3
 B2B And Industry Standards Support – Challenges
Business Partners
3rd Party
Application Industry Standard SAP
Protocols
Workflow Hard-coded Application
Tool Integration Other
Integration
Solution
Mainframe Marketplaces
Application SAP
Application B2B Tool

Security
B2B Tool Business
Industry
EAI standard
Partner
Tool Adapter Application

• Different solutions for A2A and B2B scenarios

• Custom solutions to connect to Industry Standards compliant business partners
• Substantial effort to develop and support mappings to standard interfaces
• Small business partners have to invest heavily to be industry standards compliant
• Different solutions used to connect to Marketplaces
• Use of proprietary technologies for security handling in B2B scenarios

© SAP AG 2004, B2B Industry Standards / 4

4
 B2B In XI 3.0 Overview

Industry Standard
Protocols
Business
Partners
Any SAPApplication
Application
B2B
Messaging Business
Partners

Partner
SAP XI Connectivity Kit
Small Trading
Partners

Security
Market
places

© SAP AG 2004, B2B Industry Standards / 5

z Same infrastructure as for A2A

z Extended by Technical partner directory for technical info of message exchange
z Applications provide content for Industry standards - supported by import functionality of
XI
z Additionally an XI Partner Connectivity Kit, based on the Adapter Engine running on
J2EE, is provided for business partners of our customers.

5
 B2B In XI 3.0

SAPApplication
Any
Application

Industry Standard
Protocols
Integration Server Business
Integration Directory Partners
BPE

Collaboration Agreements
Integration B2B
Collaboration Profiles Messaging
Engine
Business
Partners
Integration Repository
Adapter Engine
Business Scenarios
Adapter Framework Partner
Business Processes Messaging Connectivity Kit

Security
Mappings Queuing
Security Handling Small Trading
Message Interfaces Partners

© SAP AG 2004, B2B Industry Standards / 6

z Same infrastructure as for A2A

z Extended by Technical partner directory for technical info of message exchange
z Applications provide content for Industry standards - supported by import functionality of
XI
z Additionally an XI Partner Connectivity Kit, based on the Adapter Engine running on
J2EE, is provided for business partners of our customers.

6
 B2B Related Configuration In The Directory

Creation of Party
„The new object party facilitates the B2B functions of SAP Exchange
Infrastructure and contains the following information:
„Name, description, and additional identifiers (DUNS, GLN or SCAC) of
the party

© SAP AG 2004, B2B Industry Standards / 7

z A communication party represents a larger unit, which is involved in a cross-system

process, for example a company.
z Across the world, many different identifiers are used to identify companies involved in
cross-company processes (for example, D&B D-U-N-S-Number). In the Integration
Directory, you can specify multiple alternative identifiers for a communication party, which
you can then use to identify this party (for example, when specifying receiver
determinations).
z Internally, a communication party is identified uniquely by its name (in the Integration
Directory).
z In a particular collaboration step, two parties must agree on a particular identifier. You
define this in the collaboration agreement (in the assigned communication channel).

7
 B2B Related Configuration In The Directory
Creation of Service

„ The new object service generalizes business systems.

„ A service can represent:
A business system (in A2A scenarios)
Semantical units (grouping of interfaces), which are used mainly for
routing purposes in the communication between multiple B2B
parties. An example would be a specific PIP® (RosettaNet).
A business process

© SAP AG 2004, B2B Industry Standards / 8

z A business service represents an abstract unit for addressing the senders and receivers
of messages. You can use a business service to group interfaces.
z It is useful to use business services when configuring cross-company processes. Usually,
the interface descriptions of the business partners involved are made publicly available.
However, the system landscape of those involved is normally unknown, or only partly
known, and cannot therefore be entered in the SLD. As a result, you cannot address
business systems as the senders or receivers of messages in logical routing.

8
 B2B Related Configuration In The Directory

Creation of a Channel
Communication channels can be used in two
directions
Sender communication channel
-Receiver communication channel

For configuring specific adapters you can use the

predelivered communication channels called
channel templates
Channel templates also contain the security policies
Contains specific information for the message
protocol, transport protocol, URL, logon data and
adapter specific configuration
This also helps in the central configuration of
adapters in the Integration directory
© SAP AG 2004, B2B Industry Standards / 9

9
 B2B Related Configuration In The Directory

Creation of Sender and Receiver Agreements

The new objects sender agreement and receiver agreement

describe which channel to use and specify the party related
security settings like certificates

The sender agreement is used on the Integration Server for

inbound processing, the receiver agreement for outbound
processing.

Sender agreement and receiver agreement can be subsumed

under the term „collaboration agreement“.

© SAP AG 2004, B2B Industry Standards / 10

z In a collaboration agreement you define which communication channel to use to process

messages for particular combination of senders and receivers.
z In a collaboration agreement, senders and receivers can also agree on additional security
settings, which refer to the content of the messages.
z In outbound processing (see: Receiver Agreement), you can use security settings to do
the following:
z Sign a message
z Guarantee the integrity of the data
z In inbound processing (see: Sender Agreement), you can use security settings to do the
following:
z Check the signature of an inbound message
z In a collaboration agreement you define which communication channel to use to process
messages for particular combination of senders and receivers.
z In a collaboration agreement, senders and receivers can also agree on additional security
settings, which refer to the content of the messages.

10
z In outbound processing You use a receiver agreement. In the receiver agreement, you
define how the message is to be transformed so that it can be processed by a receiver.
In receiver agreements, you can change elements of the message header. In the receiver
agreement, you can use security settings to do the following:
y Sign a message
y Guarantee the integrity of the data
z In inbound processing You use a sender agreement. In the sender agreement, you define
how the message is to be transformed so that it can be processed by the Integration
Engine. In sender agreements you can use security settings to do the following:
y Check the signature of an inbound message
y Check the integrity of the data
y Authorize the sender of a message

11
 B2B Security Details

Availability XI 1.0 / XI 3.0 XI 3.0

Levels of Security XI 2.0 XI protocol RNIF

Connection Level Security

3 3 3
(HTTPS)

Message Level Security (for B2B)

Signature 3 3
Data Integrity 3 3
Non-Repudiation of origin 3 3
Non-Repudiation of receipt 3
Encryption 3
Technology WS-Security S/MIME
(XML-Signature)

© SAP AG 2004, B2B Industry Standards / 12

z Levels of encryption -> content and service content encryption

z Trust models - > direct and hierarchy
z Certificates have to be issued by the root CA
z There is no need for any of the revocation lists

12
 B2B In XI 3.0

„Collaboration Partner Data in the Integration Directory

Manages technical characteristics of partners to facilitate document
exchange such as
¾Party identification
¾Message formats and versions supported
¾Security requirements
¾Collaboration Agreements

„ Partner Connectivity Kit

¾For small business partners
¾Enable business partners of XI customers to conduct XML
document exchange with XI
¾Small scale easy to use client

„ B2B security (Signature/Encryption)

„ XI as marketplace messaging infrastructure

© SAP AG 2004, B2B Industry Standards / 13

z The XI messaging protocol has been enhanced. The message header contains the
information that is relevant for B2B support in order to identify the parties of the message
exchange, as well as the service e.g. procurement etc.

13
 SAP XI Provides Industry Standards Technology

Any
Application
SAPApplication

Industry Standard
Protocols
Integration Server Business
Partners
Integration Repository BPE
& Integration Directory

Integration B2B
Engine Messaging
Business
Partners

Adapter Engine

Partner
Connectivity Kit

Security
Small Trading
Partners

© SAP AG 2004, B2B Industry Standards / 14

14
 Industry Standards Support

SAP Industry Solution

IDOC/Proxy

SAP CRM
Integration Server

BPE

Integration Directory
Business Partner Integration
Engine
Collaboration Agreements

Collaboration Profiles
Adapter Engine

Integration Repository
Adapter Framework Industry Standard
Business Scenarios Protocol
Business Processes
Application↔Standard Mappings

Business Doc Schema Message Interfaces

© SAP AG 2004, B2B Industry Standards / 15

z Same infrastructure as for A2A

z Extended by Technical partner directory for technical info of message exchange
z Applications provide content for Industry standards - supported by import functionality of
XI
z Additionally an XI Partner Connectivity Kit, based on the Adapter Engine running on
J2EE, is provided for business partners of our customers.

15
 SAP Business Packages For Industry Standards

Provides Solution Kits for specific industries and delivers mappings

for RosettaNet and CIDX

Application adoption
„Enhance business applications like mySAP CRM or mySAP SCM to
support SAP Business Packages for high priority processes

Mapping
„Including message sets for the industries according their priority
„Support mappings: versions, upgrade, maintenance

Process Integration
„SAP Business Packages’ message protocol implementation (such as
RNIF 2.0 and RNIF 1.1 for CIDX)
„Provision of Collaboration Agreements
„Business Process Management support

© SAP AG 2004, B2B Industry Standards / 16

z SAP provides solution kits for specific industries, and delivers mappings for RosettaNet
and CIDX.
z In the future, SAP will offer more Solution Kits to broaden the range of supported
standards.

16
 B2B and Industry Standards : Summary

You should now be able to:

z Explain the XI Infrastructure for supporting B2B
scenarios and Industry Standards.
z Describe the configuration objects to use for
implementing B2B scenarios.
z Describe SAP Business Packages for Industry.

© SAP AG 2004, B2B Industry Standards / 17

17
 Copyright 2004 SAP AG. All Rights Reserved
„ No part of this publication may be reproduced or transmitted in any form or for any purpose without the express
permission of SAP AG. The information contained herein may be changed without prior notice.
„ Some software products marketed by SAP AG and its distributors contain proprietary software components of other
software vendors.
„ Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
„ IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries,
pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or
registered trademarks of IBM Corporation in the United States and/or other countries.
„ Oracle is a registered trademark of Oracle Corporation.
„ UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
„ Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered
trademarks of Citrix Systems, Inc.
„ HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium,
Massachusetts Institute of Technology.
„ Java is a registered trademark of Sun Microsystems, Inc.
„ JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and
implemented by Netscape.
„ MaxDB is a trademark of MySQL AB, Sweden.
„ SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver and other SAP products and services mentioned herein
as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other
countries all over the world. All other product and service names mentioned are the trademarks of their respective
companies. Data contained in this document serves informational purposes only. National product specifications may vary.
„ These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated
companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group
shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group 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.

© SAP AG 2004, B2B Industry Standards / 18

18