How to Build an EnterpriseService using SAPNetWeaver ProcessIntegrationPrasad IllapaniSAP NetWeaver RIGSAP Labs LLC., Bellevue, WA

Service Enablement Overview

Publish Enterprise Service to a UDDI Registry

Demo

Enterprise Services – Creation & Delivery

Developing Enterprise Services using PI

Service Enablement Overview

Publish Enterprise Service to a UDDI Registry

Enterprise Services- Creation & Delivery

Developing Enterprise Services using PI

Demo

SAP 2007, PI - KNHC Call

Enterprise Service Oriented Architecture

SAP NetWeaverBusiness Process Platform

Portal Devices Office RFID

xAppsComposites Powered by SAP NetWeaver

Rendering

ProcessComponents

EnterpriseServices

Repository

Sub-sidiary

BusPartner

HomeGrown /

ISVSAP

SAP NetWeaver and the Business Process Platform

Service Enablement refersto the process of providingenterprise functionality inthe form of well-definedservices.

ServiceEnablement

SAP 2007, PI - KNHC Call

Business Process Platform

Portal Devices Office RFID

xAppsComposites Powered by SAP NetWeaver

Rendering

ProcessComponents

EnterpriseServices

Repository

Sub-sidiary

BusPartner

HomeGrown /

ISVSAP

Enterprise Services in Business Process Platform

Structure ofEnterprise Services

Service Implementation//create with external keypublic java.lang.String ejbCr

throws BOCreateEeif (! throw new BOPermion

Service Interface

Glue Code//create with external keypublic java.lang.String ejbCr

throws BOCreateEeif (! throw new BOPermion

SAP 2007, PI - KNHC Call

Enterprise Service Repository– Design Time

Enterprise ServicesRepository (ESR)

Integration Repository as thefoundation for the ESREnhancements:

Process (ARIS) ModelsService InterfacesService Registry…

SAP interfaces/data types/…are naturally part of ESR

Leverage existing investmentLegacy/3rd PartyLegacy/3rd Party SAPSAP

Analytics

EnterpriseServices

Repository

ServiceEnablement

PlatformProcess Components

PlatformProcess Components

Composite ApplicationsComposite Applications

PartnerPartner

People Productivity

SAP 2007, PI - KNHC Call

Enterprise Registry - Publish

CONSUMERAPPLICATIONCONSUMER

APPLICATIONSERVICE

IMPLEMENTATIONSERVICE

IMPLEMENTATIONSERVICEENDPOINT

INVOCATION

PROVIDERCONSUMER

CONSUMERTOOLS ENTERPRISE

REGISTRY

SERVICE MODELPUBLICATIONS

SERVICE MODELPUBLICATIONS

SERVICE DEFINITIONPUBLICATIONS

SERVICE DEFINITIONPUBLICATIONS

SERVICE ENDPOINTPUBLICATIONS

SERVICE ENDPOINTPUBLICATIONS

PUBLISHDISCOVER

Refer

ence

ReferenceReference

SOA

ESR

SERVICE DEFINITIONS

SAP 2007, PI - KNHC Call

Business Process Platform

Portal Devices Office RFID

xAppsComposites Powered by SAP NetWeaver

Rendering

ProcessComponents

EnterpriseServices

Repository

Sub-sidiary

BusPartner

HomeGrown /

ISVSAP

Key Differentiator in Business Process Platform

The Enterprise ServicesRegistry and Repository are

key differentiators

EnterpriseRegistry

ES Repository

Service Enablement Overview

Publish Enterprise Service to a UDDI Registry

Demo

Enterprise Services – Creation & Delivery

Developing Enterprise Services using PI

SAP 2007, PI - KNHC Call

Enterprise Services – Definition

Enterprise Services are Web Services that provideenterprise level business value.

Only one version --- reused throughout various applications

S&P

APP1 APP2 APP3

D&BS&PD&B

APP1 APP2 APP3 APP1 APP2 APP3

S&PD&B

Traditional Web Services Enterprise Services

Proprietary protocolsHard coded logic

Standard protocolsVarious semantics

Web Services Tech.Standardize semanticsBusiness rules

SAP 2007, PI - KNHC Call

Enterprise Services – Criteria

An Enterprise Service has to fulfill the following criteria:Technically a Web Service– WSDL, XML, SOAP, HTTP, …

Business Semantics and rules.– Enterprise Services delivered by SAP follow SAP methodology.

Published in a central repository– UDDI Registry– ESR = Integration Repository + SOA Requirements

SAP 2007, PI - KNHC Call

Enterprise Services – ESR and Registry

Duet

RepositoryDefinition of Processes and Services.Service Enabling in SAP Apps.

Non-SAP

22

1. Define2. Generate3. Implement4. Register

ServiceRegistry

(UDDI)

Bac

kend

ImplementationsImplementations

33

SAP Dev Tools

SAP

44

Discover

55

5. Discover6. Compose7. Deploy & Configure8. Run

66

77

Name

Title

Check

Composites

88

11

WSDL

WSDL++

RegistryYellow pages of ServicesAdd deployment information (i.e. endpoint)Ease of consumption: Discovery and Binding.

EnterpriseServices

Repository

Run time

SAP 2007, PI - KNHC Call

Enterprise Services – Creation

ERPERPESA Definition &ProvisioningESA Definition &Provisioning

ISVs25

75

500

TierTier1&21&2

Tier 3

ES DefinitionGroupsES DefinitionGroups

ESCLeadership

Council

ESCLeadership

Council

Reconci-liation

Reconci-liation PIC 0PIC 0

PIC1-3

PIC1-3

Requestors Roll-In-Channel

Proforma 1:1Definition Group

Strategic SAPPrograms(Duet, Analytics FT,CFT, iCOD,ESA BusinessPackages)

Strategic SAPPrograms(Duet, Analytics FT,CFT, iCOD,ESA BusinessPackages)

PTU ISISV ProgramPTU ISISV Program

Customers(in ESC)

ESA Definition& Provisioning

Development(Provider)

Portfolio Mgmt & Governance

Use CaseServiceRequest

Impl.Impl.

CRM/…CRM/…

PIC1-3

PIC1-3 Impl.Impl.

Ind.Dev.Ind.Dev.

PIC1-3

PIC1-3 Impl.Impl.

SAP 2007, PI - KNHC Call

Enterprise Services – Delivery

Service Interface

Service Implementation

//create with external keypublic java.lang.String ejbCr

throws BOCreateEeif (! throw new BOPermion

//create with external keypublic java.lang.String ejbCr

throws BOCreateEeif (! throw new BOPermion

Glue Code

Enterprise Services are delivered as Add OnsService Interfaces

– Also known as “PI Content”– Blueprints or interfaces created with the

Integration Repository– They reside in the Integration repository

Glue Code– Also known as “XI Proxies” ( ABAP or Java ),

“implementation code”– Services structure and code needed to service

enable backend functionality– Resides in Backend systems

Documentation– Publish and discover enterprise services

Service Implementation– Also known as “Application code”– Resides in SAP backend systems– In some scenarios may be part of the Add On

SAP 2007, PI - KNHC Call

Enterprise Services – Delivery

Enhancement PackagesDelivering new capabilities along with criticalupdates business scenarios and processes.They include new functionality, ES Packages,composite applications.

Enterprise Service WorkplaceExplore, test and use Enterprise Serviceswww.sdn.sap.com Enterprise SOA

Discovery System for Enterprise SOAFully configured SAP LandscapeDelivered on a physical serverReady to run Enterprise Services and compositeapplications.

Service Enablement Overview

Publish Enterprise Service to a UDDI Registry

Demo

Enterprise Services – Creation & Delivery

Developing Enterprise Services using PI

SAP 2007, PI - KNHC Call

SAP NetWeaver

Com

posi

te A

pplic

atio

n Fr

amew

ork

PEOPLE INTEGRATION

Multi channel access

Portal Collaboration

INFORMATION INTEGRATION

Bus. Intelligence

Master Data Mgmt

Knowledge Mgmt

APPLICATION PLATFORM

J2EE

DB and OS Abstraction

ABAPLife C

ycle Mgm

t

PROCESS INTEGRATION

IntegrationBroker

BusinessProcess Mgmt

From Process Integration to Enterprise SOA

Analytics

Composite Applications

Legacy/3rd PartyLegacy/3rd Party PartnerPartner SAPSAP Platform

Process ComponentsPlatform

Process Components

Composite Application

Process Integration with SAP NetWeaver… the Corner Stone of an Enterprise SOA

Service EnablementESR

SAP 2007, PI - KNHC Call

Creating Enterprise Services in SAP Netweaver 2004s

1

2

3 Activate /Deploy the Service

GenerateWeb Service

Implement Code InBusiness App

Inside-Out Approach Outside-In Approach

Implement CodeIn Business App

Generate a ProxyInterface in the App

Define MessageInterface In SAP PI

Create/ Publish theService

1

2

3

4

SAP 2007, PI - KNHC Call

Outside In Approach: Create Service (SAP App)

1. Design the Message Interface Objects in the Integration Repository of SAPExchange Infrastructure.

2. In the SAP Application System Go Tr: SPROXY. Generate a Proxy Interface.Add your Application Logic to the Proxy Class Interface

3. Go to Tr: SE80, under the user Local Objects, right click on: EnterpriseServices Select Create-> WebService

SAP 2007, PI - KNHC Call

Outside In Approach: Create Service

4. Enter Service Definition name and Short text. Select endpoint type asMessage Interface.

5. Select the Message Interface which is same as the Proxy Interface name inStep2. Select the Profile and check the box to release the service for runtime.

SAP 2007, PI - KNHC Call

Outside In Approach: Admin Service

6. Go to Tr: WSADMIN, to display and administer the Enterprise Service.

7. Double Click on the Enterprise Service to display the properties.

SAP 2007, PI - KNHC Call

Outside In Approach: Admin Service

8. In Tr: WSADMIN Click on the button to display the WSDL file in a browserpage as shown below.

SAP 2007, PI - KNHC Call

Outside In Approach: Test Service

9. In Tr: WSADMIN Click on the button to display the web service homepage.

10. Here you check the WSDL location details, and also test the service usingthe Test link by providing the input parameters for the service.

SAP 2007, PI - KNHC Call

Outside In Approach: Release Service

11. Tr: WSCONFIG to release the Web Service for SOAP Runtime.

Double click on the Web Service and click on the ICF Details buttonto display the service location details.

Service Enablement Overview

Developing Enterprise Services using PI

Demo

Enterprise Services – Creation & Delivery

Publish Enterprise Service to a UDDI Registry

SAP 2007, PI - KNHC Call

Publish Service: Configuration

1. To use the old publish service in SAP NW-04s-SPS09 release, set the userparameter: OLD_UDDI to ‘X’ in the user profile. Tr: SU01

2. In Tr: SM59 Create HTTP destinations to an External Server (Type: G) for UDDIInquiry and UDDI Publish.

SAP 2007, PI - KNHC Call

Publish Service: Configuration

3. Register the Corresponding UDDI Registry in Tr: SUDDIREG and Save theentries. The example below is for a Local UDDI registry.

Inquire and Publish API Destination Values must be the same one created inStep2.

SAP 2007, PI - KNHC Call

Publish Service: UDDI Registry

1. Tr: SE80, Expand the enterprise service and select Variants tab, Right click onUDDI node, Choose Publish. Select the Registry and click the continue button topublish the service.

2. After Publishing the service to the corresponding registry, check the t-modelentry created for the service.

SAP 2007, PI - KNHC Call

Publish Service: Checking the Service in UDDI Client

1. Log in to the UDDI Client link from the J2ee Home Page: http://<HostName>:<J2ee Port#>/index.html. Select the Search Registry radio button tosearch the published service

Search Results:

SAP 2007, PI - KNHC Call

DEMO

SAP 2007, PI - KNHC Call

Q&A

Questions?

SAP 2007, PI - KNHC Call

Copyright 2007 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 bechanged without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, 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, System i, System i5, System p,System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC aretrademarks or registered trademarks of IBM Corporation.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated 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 registeredtrademarks 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.

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 purpose without the express priorwritten 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 intended strategies, developments,and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that thisdocument 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 itemscontained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to 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. Thislimitation 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 that you may access through the use of hot links contained inthese materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.