PIDX Message Exchange Using SAP NetWeaver’s RNIF Adapter – Webinar Powerpoint

7/14/2019 PIDX Message Exchange Using SAP NetWeaver’s RNIF Adapter – Webinar Powerpoint

http://slidepdf.com/reader/full/pidx-message-exchange-using-sap-netweavers-rnif-adapter-webinar-powerpoint 1/39

Sam Raju

SAP Netweaver RIG Americas

SAP Labs, LLC

PIDX message exchangeusing SAP Netweaver’sRNIF Adapter



Introduction

SAP Netweaver – Providing infrastructure of B2B

PIDX Overview

PIDX Content

Configur ing RNIF Adapter

Summary

Message Monitoring and Security



SAP AG 2006, KHNC/ Sam Raju/ 091907/ 3

Why Enabling Business-to-Business Processes?

Complex Integration Requirements

Non-homogeneous infrastructures

Integration via open networks (Internet)

Diverse options for technical connectivity

Adapt to changing processes / business partners

Changing ability to dictate communication standards

Connect to all sizes of business partners

Time to connect new business partners is business cr itical

B2B Integration Challenges

your

business

partners

your

company

Partner

Market-place




Capabilities that can be used for B2B Integration

Supporting Standards to Improve Processes

Predefined Integration Content

Adapter Partner Ecosystem

Central Interface Repository

Trading Partner Collaboration

Secure Messaging and Routing

Capabilities



Introduction


PIDX

PIDX Content


Summary





B2B: Standards-based integration of inter-company processes

B2B Integration with SAP NetWeaver

your

businesspartners

your

company

Partner

Market-place

SAP NetWeaver Process Integration acts as B2B Gateway




One Integration Platform:B2B with SAP NetWeaver Process Integration

Industry StandardProtocols

B2BMessaging

S e c u r i t y

Enterprise Services

Repository

Service Interfaces

Integration Processes

Mappings

Integration Scenarios

Integration Directory

Collaboration Agreements

Small Trading

Partners

SAP

Partner

Connectivity Kit

Business

Partners

Business

Partners

Integration Server

BPE

Integration

Engine

Advanced Adapter Engine

Collaboration Profiles

Adapter FrameworkMessagingQueuing

Security Handling

SAPApplication

Routing Rules

Any

Appl ication




Supporting Standards to Improve Processes

Industries involved in

Industry Standards Support

High Tech

Chemical

Agrichemical

Oil and Gas

Automotive

Aerospace and Defense

Consumer Products

Mill Products

Financial

Others…

UN/CEFACT

GS1

http://www.uc-council.org/ean_ucc_system/index.html

http://www.spec2000.com/index.html

http://www.papinet.org/PubRelations/papiNet_Powered.asp

http://www.rapidnet.org/default.htm

http://www.rapidnet.org/default.htm

http://www.cidx.org/default.asp

http://www.rosettanet.org/RosettaNet/Rooms/DisplayPages/LayoutInitial




Chemical Companies CIDXTM Customer

Shipment Notice

PO

Order Response /Confirmation

Payment

Invoice

Enterprise B

Appl icat ion

Enterprise B

Appl icat ionEnterprise A

Appl icat ion

Enterprise A

Appl icat ion

Order Change

Supplier PIDXTM Oil&Gas Companies

SAP Business Packages – Example




Ready-to-run Integration Scenarios

Content from SAP Partners

SAP Application Content SAP Business Packages

Partner Content A2A/B2B

Enhance PackageA d d n ew P c k g.

E n h a n c e

P a c k g .

Add n ew Pckage

Content from SAP



Introduction


PIDX Overview

PIDX Content


Summary





What is PIDX?

Petroleum Indust ry Data Exchange (PIDX)

API’s commit tee on Business Standards and Processes

A group of petroleum industry representat ives and technology

service providers collaborated to define a set of industry specific

XML standards

PIDX mission is to influence the archi tecture and facili tates the

implementation of effective standards and processes for electronic

business communications within the Petroleum Industry

PIDX Standard contains the XML Schema files which are core of

the PIDX XML specif ication

These XML Schema files define the data structures that PIDXimplementers share via XML files

PIDX




PIDX XML Standards

PIP Number

P11

P12

P21

P22

P31

P32

P33

P41

P42

P43

P51

XML Schema

FieldTicket

FieldTicketResponse

Invoice

InvoiceResponse

OrderCreate

OrderChange

OrderResponse

QuoteRequest

Quote

QuoteNotification

RequestRequisitionReturn

Each Transaction implemented by PIDX is assigned with a PIP

Below given are some of the PIPs corresponding to their Schema




PIDX TRP Standards

PIDX TRP Standards are used to securely and reliably package,transport and route PIDX messages across the internet

PIDX TRP Protocol requirements include:

Message Identification

Authent ication

Authorization Non-Repudiation

Confidentiality, Data Integrity

Reliable Messaging

Error Handling

RNIF 2.0 support for TRP Standards

RNIF 2.0 is based on needs for reliable messaging and non-repudiationand supports many of the TRP requirements

It provides a consistent envelope format for use across all types of PIDXtransactions

Transport, Routing, and Packaging Standards




PIDX Message

The components of a PIDX message are encased in a multipart/related

envelope

RNIF 2.0 supports following types of messages in PIDX

o Business Action Message

o Business Signal Message

Positive

Negative



Introduction


PIDX Overview

PIDX Content


Summary





PIDX Content in SAP Netweaver PI

* http://service.sap.com/Support Packages and Patches SAP Content XI Conent

PI Content for PIDX*

PI-Content

fr. Partners

PI-Content

for PIDX

http://service.sap.com/Support

http://service.sap.com/Support




PIDX Content in Integration Repository

PIDX software componentcontains the standard content

Al l the Order-to-Invoice PIDX

messages are delivered as

external definitions

External DefinitionsXSDs describing

PIDX PIPs


PIDX PIPs




ExamplePIDX PIPP31 as Integration Scenario

Mappings Application standard

to PIDX PIPstandard

Mappings Application s tandard

to PIDX PIP

standard

External Definit ionsXSDs describing

PIDX PIPs


PIDX PIPs



Introduction


PIDX Overview

PIDX Content


Summary





Collaboration Profiles and Agreements for PIDX Integration

PIDX related configuration provided through:

Defining collaboration profiles centrally Business Party

Business services

Defining collaboration agreements centrally

Sender agreements

Receiver agreements




Pre-configured configuration

ConfigurationTemplates

ConfigurationTemplates

ConfigurationWizard

Configuration

Wizard

Reduce time to hook up with new Business Partners




Configuration using the Scenario Configurator

Generate ConfigurationGenerate Configuration

Transfer scenario

from repository

Transfer scenario

from repository

AssignParty & Service

Assign

Party & Service

Assign

Commun.-Channel

Assign

Commun.-Channel




RNIF adapter – key features

Pack and unpack PIDX messages

Structural verification of the

message headers

Handl ing of message security

Uses the Collaboration Partner

Agreements to manage PIDX PIP

exchanges PIDX defined error handling

procedure

Message monitor ing & auditing

React to failures in the backend

applications

RNIF adapter

Industry Standards Content

Integration

Server

Integration

Repository

Adapter

Engine

Adapter Framework




RNIF Adapter Configuration




RNIF Adapter Configuration Contd..




Configuration

cacheIS

PIDX Message Flow in PI

Adapter

Sender

Adapter

Receiver

Q

Adm inis tratio nSecurity

MonitoringTracing

Logging

Module Processor

Back

end

Channel

Messaging

Configuration

cache

Adapter

Framework

MappingReceiver

Determination

Queue

XI Messages

System Landscape Directory•Holds component description

including address data

Exchange Profile•Holds central connection descriptions

including user, passwords

RWB

IBDir

Adapter Engine in SAP J2EE

Message, Componentmonitoring et.al.

Scenario Configuration

httpIDocBPE



Introduction


PIDX Overview

PIDX Content


Summary





Monitoring PIDX messages in SXMB_MONI




Monitoring PIDX messages in RWB




Encryption

Non-Repudiation of receipt

Non-Repudiation of origin

Data Integrity

Signature

Message Level Security (for B2B)

Connection Level Security

(HTTPS)

RNIFXI protocol

Availabil ity

Levels of Security

Secure Messaging and Routing for B2B Integration

S/MIMEWS-Security(XML-Signature)

Technology




Protect Your Data and SystemsMessage Level Security

Internet

NetWeaver

User Authorization

Message Level Security

Transport Level Security

System Landscape




Protect Your Data and Systems Transport Level Security

Internet

NetWeaver

User Authorization

MessageLevel Security

Transport Level Security

System Landscape




Demo

Demo




Demo

The Order create process is init iated when a Buyer commits to buy

a product f rom Seller.

The Buyer sends an order create PIDX P31 message to the seller.

Upon receipt of the message, the Seller sends a receipt

acknowledgement to the Buyer.



Introduction


PIDX Overview

PIDX Content


Summary





Benefits of B2B with SAP NetWeaver PI

B2B capabil ities of SAP PI

Only one solution for all integration requirements (B2B and A2A)

Centralized design, conf iguration, monitoring, alerting

Pre-configured solutions

Use of RNIF Adapter for PIDX solu tions

Benefits

Low TCO because only one p latform is required for B2B and A2A

Increase business agility

Increase business transparency




Q&A

Questions?




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

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.

J ava is a registered trademark of Sun Microsystems, Inc.

J avaScript 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.

PIDX is the registered trademark of the American Petroleum Institute.

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 mentionedare the trademarks of their respective companies. Data containedin this document serves informational purposes only. National product specifications may vary.

The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purposewithout the express prior written permission of SAP AG.

This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intendedstrategies, developments, and functionalities of the SAP®product and is not intended to be binding upon SAP to any particular course of business, productstrategy, and/or development. P lease note that this document is subject to change and may be changed by SAP at any time without notice.

SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics,links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limitedto the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.

SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence.

The statutory liability for personal injury and defective products is not affected. SAP has no control over the information thatyou may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Webpages.

Copyright 2007 SAP AG. All Rights Reserved

Documents

PIDX Message Exchange Using SAP NetWeaver’s RNIF Adapter – Webinar Powerpoint