sap's orchestration overview

28
SAP Solutions SAP’s Orchestration Overview October 2013 © 2013 SAP AG or an SAP affiliate company. All rights reserved.

Upload: trinhdieu

Post on 01-Jan-2017

229 views

Category:

Documents


1 download

TRANSCRIPT

SAP Solutions

SAP’s Orchestration Overview October 2013

© 2

013

SAP

AG o

r an

SAP

affilia

te c

ompa

ny. A

ll rig

hts

rese

rved

.

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Table of Contents

4 Executive Summary Single Sign-On and Identity Management

Application and Business Partner Integration

Master-Data Management

Business Process Management

6 Introduction and Scope Business Processes

9 Single Sign-On and Identity ManagementEmployee Scenario

Consumer Scenario

Business Networks

13 Application and Business Partner IntegrationTypes of Application Integration

Application Integration Architecture

SAP Solutions for Application Integration

Business Partner Integration

17 Master-Data ManagementMaster-Data Technology

19 Business Process ManagementBusiness Rules

Collaboration

Process Optimization

24 Outlook and Conclusion

25 Find Out MoreContact Information

About the AuthorsDr. Bernhard Drittler and Dr. Ralf Dentzer are members of the products and innovation area at SAP.

3Orchestration Overview© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Disclaimer

This document provides an overview of SAP’s orchestration approach and concept. It contains current and intended strate-gies, developments, and functionalities of SAP® solutions, applications, and technologies and is not intended to be bind-ing upon SAP to any particular course of business, product strategy, or development; its content is subject to change with-out notice.

This document is not subject to your license agreement or any other service or subscription agreement with SAP.

SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or complete-ness of the information, text, graphics, links, or other items contained within this material. This document is provided with-out a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fit-ness for a particular purpose, or noninfringement.

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 prod-ucts is not affected. SAP has no control over the information that you may access through the use of 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 Web pages or their content.

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 the publication date, and they should not be relied upon in making purchasing decisions.

4 Orchestration Overview© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Executive Summary

Today CIOs and IT managers are challenged with new business trends that can be tackled with software innovations that enhance customer collaboration, shorten response times, improve decision making, identify upcoming exceptions, or make operations in general more efficient. While the IT department has to integrate these innovations, it also has to keep business-critical processes running smoothly. On top of that, IT must provide access to applications via multiple channels, secure user access from all kinds of devices, integrate processes and data, keep master data consistent, and ensure optimal process execution. Why emphasis is shifting to orchestration is clear. Orchestration – the ability to manage and optimize business processes end to end, throughout the enterprise and across enterprises – has become a key IT capability.

Orchestration at SAP addresses these requirements. It helps IT staff create, manage, enhance, and secure new and existing business solutions while they keep business-critical processes running smoothly. This paper provides a comprehensive view of this orchestration approach. It shows interconnections between key scenarios, reference architectures, and SAP®

software and service products. It covers the key concepts of single sign-on and identity management, integration of applica-tions within an enterprise and with a business partner, master-data management, and business process management (see Figure 1). Application lifecycle management, although a part of orchestration, is not covered.

Figure 1: Orchestration of End-to-End Processes

Identity management and single sign-on

Business process management

Application integration

Master-data management

5Orchestration Overview© 2013 SAP AG or an SAP affiliate company. All rights reserved.

SInglE SIgn-On AnD IDEntIty MAnAgEMEnt

In a world of interconnected on-premise, cloud-based, and mobile solutions, end users access a number of applications, even when performing work within a single business process. User efficiency would be severely impaired if they had to con-tinually enter different IDs and passwords to access all this software. The solution is to allow users to access all software and systems with a single logon. This requires a single sign-on infrastructure in combination with identity management. For some time now, SAP has been supporting both in its on-prem-ise software. SAP extends these features to the cloud and sup-ports open standards like Security Assertion Markup Language (SAML) and OAuth, an open standard for authorization.

APPlICAtIOn AnD BuSInESS PArtnEr IntEgrAtIOn

The classical and essential area of orchestration is the integra-tion of applications and business partners in order to compose end-to-end software support for business processes. The growing number of distributed applications both on premise and in the cloud greatly increases the need for integration. Inte-gration covers a wide spectrum of IT tasks, from providing high-speed, high-volume message-based communication to ensuring maximum throughput for the transfer of large data quantities. SAP provides a well-established on-premise integra-tion technology to integrate on-premise and cloud applications from SAP and other vendors.

For those businesses that do not want to operate their own integration technology on premise, SAP has a cloud-based integration platform that offers integration technology as a ser-vice and leverages well-established concepts of on-premise integration technology. Combined, cloud and on-premise tech-nologies form a powerful hybrid integration approach. SAP’s strategy is complemented with prebuilt integration content for standard processes composed of SAP applications.

MAStEr-DAtA MAnAgEMEnt

Master data is used in multiple steps of a process, and high-quality master data that is consistent along the process chain is important for successful process execution. In simple sce-narios, master-data distribution based on standard integration technology is sufficient. In the case of more complex scenarios, additional support may be required, for example, for rule-based validation, enrichment, and duplicate checks. Furthermore, it may be necessary to consolidate master data from multiple sources or introduce a process for creating and changing mas-

ter data centrally, including approval workflows, to comply with a company-specific governance policy. SAP offerings cover all these requirements.

BuSInESS PrOCESS MAnAgEMEnt

While business process management in general addresses the whole enterprise and IT landscape, this document focuses on keeping processes across business applications executing smoothly. Important innovations specific to this topic are tak-ing place in the areas of collaboration and optimization.

Human collaboration during business process execution has always been an important consideration. Tool-based collabora-tion increases the efficiency with which business can be con-cluded, but collaboration should not end at the enterprise boundaries. For example, the preparation of a quote or resolu-tion of a delivery issue should be conducted by internal experts together with customer representatives. SAP helps strengthen collaboration within the enterprise by continually adding more collaboration features to its applications. SAP also enables col-laboration with parties beyond the enterprise with solutions that utilize cloud infrastructures.

Process optimization has been a topic in business process management for more than 20 years. Recognizing this, SAP offers services to optimize processes as part of its support offering. In addition, visibility into core processes in SAP soft-ware has been enabled through process-logging functions now included in SAP software.

With the SAP HANA® platform, the in-memory computing tech-nology from SAP, it became possible to realize process optimi-zation in ways never possible before. Detailed visibility of run-ning processes in applications, combined with application data, provides new insight in real time. Operational analytics and decision management help business users focus on exceptions and resolve them promptly. In the future, this insight may be complemented with knowledge gained from process mining, which could lead to an enhanced understanding of why some processes perform better than others and what is necessary to improve process execution.

In the following sections we describe how SAP’s approach addresses the needs involved in orchestrating business pro-cesses for today’s complex enterprise. As already mentioned, emphasis is on a holistic overview of SAP’s orchestration approach, rather than on describing SAP products in detail.

6 Orchestration Overview© 2013 SAP AG or an SAP affiliate company. All rights reserved.

BuSInESS PrOCESSES

Business applications typically need a database to store their business data and an application server to run on. By sharing the same database and application servers – in other words, the same “system” – multiple applications can benefit from common operations, configuration settings, and user manage-ment. Moreover, synergies are possible when supporting differ-ent steps of the same business process by sharing business data on the database and using local application programming interfaces (API) for the integration of the applications. Master data can be shared and subsequent process steps can be started in real time, and all process data is available locally for inspection and analysis.

This paper introduces the orchestration areas and their major challenges, common approaches, and infrastructure require-ments with a focus on emerging types of applications and their integration with existing business software. It describes SAP’s current approach to solutions, reference architectures, and rel-evant products, together with SAP’s underlying strategy and future plans.

This information supports the CIO and IT department in their strategic decisions. It is meant to be used to help them improve the orchestration of their business processes, in particular when new, innovative applications are introduced that must be integrated into software supporting existing business processes.

Introduction and Scope

The business software of an enterprise isn’t just a collection of individual applications. Business software is composed of inte-grated applications that provide end-to-end support for busi-ness processes. The business processes drive the operational business of an enterprise and are essential for business suc-cess. Integration between the applications that support these business processes is critical to that success. In some indus-tries, an integration disruption may lead to production down-time within minutes.

New types of business applications are emerging. They may run on an in-memory database like the SAP HANA database, in the cloud, or on mobile devices; they may handle Big Data or

facilitate collaboration between business partners. To be used effectively, these innovative applications must be included in business processes and integrated with each other and exist-ing on-premise business software, such as SAP Business Suite software. This increases the number, scope, and complexity of integrations, introduces new aspects like users logging in to cloud applications from anywhere, and requires an appropriate infrastructure to manage the complete solution.

Orchestration is the term SAP uses to refer to the ability to manage and optimize entire business processes across one or more enterprises. It comprises the areas shown in the following table.

BuSInESS PrOCESSES ACrOSS APPlICAtIOnS

Orchestration Area Key FeaturesSingle sign-on and identity management

• Users can access all applications after a single logon. • Identities are provisioned throughout a heterogeneous software landscape.

Integration of applications and business partners

• Processes are continued reliably in other applications. • Necessary data is transferred between applications.

Master-data management • Master data that was created in various applications can be cleansed and consolidated. • Excellent-quality master data can be created and distributed to ensure consistency

across applications.

Business process management • Business process execution can be analyzed, forecast, and optimized. • Human collaboration in the context of business processes can be supported.

7Orchestration Overview© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Alternatively, applications can be deployed separately, with their own database and application servers. They can be dis-tributed on separate systems. This is done for various reasons, for example:

• Mergers and acquisitions bring with them separate IT landscapes.

• Innovative applications are based on innovative technology and require their own systems, which may have an in-mem-ory database or run in the cloud.

• Introducing new applications would require an expensive upgrade of existing software.

• Security policies require isolation of critical applications. • High availability of vital applications must be ensured. • Scalability and load balancing must be preserved.

To connect business processes that are supported by distrib-uted applications across application boundaries and enable the exchange of common data, the applications must be linked by an application integration infrastructure (see Figure 2).

Business processes supported by distributed applications are typically connected by messages sent to start the next process step in the receiving application. Standard tasks of the applica-tion integration infrastructure include:

• Determining who the receiver is • Converting the messages to certain formats and protocols • Mapping the structure and value of the message content • Transporting the messages to another system • Delivering the messages reliably

Besides connecting process steps with messages, many kinds of data must be transferred between applications for other purposes. This could be new data from an external source, application data for a data warehouse, or master data that is

needed for the execution of process steps. The same master data is typically used in multiple applications along the process chain and has to be consistent across applications to ensure proper execution of process steps (see Figure 3). Application integration or dedicated master-data management technology is applied for that purpose.

Distributed applications in separate systems have separate user management and require separate logons initially. Identity management can transfer users to distributed applications and simplify administration, while a single sign-on feature greatly improves the user experience (see Figure 4). Ideally, it is com-bined with the logon to end-user equipment – including mobile devices – and the corporate network.

Figure 2: Distributed Applications Connected by Application Integration

Figure 3: Consistent Master Data in Distributed Applications

Figure 4: Identity Management and Single Sign-On

Integration

Master data

8 Orchestration Overview© 2013 SAP AG or an SAP affiliate company. All rights reserved.

When distributed applications support the same business pro-cess, related process steps can be executed in applications running on different systems. Business process management provides visibility of process execution even across separate systems, shows an integrated view of processes end to end (see Figure 5), and helps businesses optimize their processes.

Innovative applications, for example, those running in the cloud or using in-memory databases, often offer sharply delineated business benefits. Cloud applications often attract individual lines of business in enterprises – and, as a result, the total number of applications in the enterprise quickly grows. Initially, running a cloud application is easy. But after some time people realize they are working in silos, without efficient and reliable integration to corporate data and processes and with many manual steps. From a corporate perspective, this is a very undesirable situation, bringing with it high operational efforts and security risks. Instead, cloud applications should be com-bined with existing on-premise applications to compose hybrid solutions that are well integrated to effectively support the business processes end to end.

An orchestration technology (see Figure 6) enables existing on-premise business software and core applications – the cur-rent business backbone – to extend processes through inte-gration with innovative applications, collaboration platforms, or even business partners.

Business people often focus on the advantages innovative applications provide and don’t pay attention to integration needs. They expect the IT department and orchestration tech-nology to meet the integration challenges. The main objective of SAP’s orchestration strategy is to ease IT’s task, so IT can deliver superior, integrated business solutions based on exist-ing and innovative applications.

Figure 5: Business Process Visibility

Figure 6: Orchestration of Business Processes End to End

Identity management and single sign-on

Business process management

Application integration

Master-data management

Visibility

9Orchestration Overview© 2013 SAP AG or an SAP affiliate company. All rights reserved.

EnABlIng uSEr ACCESS

Single Sign-On and Identity Management

In the emerging world of interconnected on-premise, cloud, and mobile solutions, the users of SAP software and services are everywhere, come from everywhere, and access those solu-tions and services from everywhere. To run business processes efficiently and securely and provide useful services, SAP soft-ware must determine the user’s identity and role at the time of access.

On the other hand, users do not want to have to register, pro-vide, or maintain their identity information repeatedly when using software or services. Keeping track of numerous pass-words for different logons to multiple services is a nuisance everybody today knows all too well. Ideally, users want to lever-age existing accounts and identity information when starting to use a new application or service. They want to log on only once, independent of where access takes place, and rely on the soft-ware to store their information securely and share it when needed.

To meet these expectations, SAP has defined a strategy for identity management and single sign-on that covers on-prem-ise solutions but extends to cloud services and mobile access. It supports different scenarios.

The “employee scenario” addresses employees of an enter-prise or users working in a comparable capacity, such as busi-ness partners who work closely with the enterprise. This sce-nario includes classical users with dedicated roles based on user tasks or functions. The “consumer scenario” addresses consumers, citizens, and similar users who have only a spo-radic relationship with the enterprise. For these users, self-reg-istration mechanisms or logons through Facebook or Google identities are common.

EMPlOyEE SCEnArIO

The primary source of data describing employee users is the human capital management (HCM) corporate software. The HCM software supplies the identity management functionality with data about new hires and, more importantly, about people leaving the enterprise (see Figure 7). The SAP ERP Human Capital Management (SAP ERP HCM) solution can be inte-grated with identity management software for that purpose, for example, with the SAP NetWeaver® Identity Management (SAP NetWeaver ID Management) component. This integration can automatically deactivate a user account when that employee leaves the organization – a mechanism of great importance to keep applications in the cloud secure. If left unaddressed, a for-mer employee could access a cloud application – and its confi-dential data – from anywhere, even if that user’s access to the corporate network has been blocked.

Figure 7: Creating and locking Employee Identities

Human capital management

Identity management Application

Hire employee Create identity Distribute identity

Release employee Delimit identity Lock identity

10 Orchestration Overview© 2013 SAP AG or an SAP affiliate company. All rights reserved.

SAP plans to extend its established on-premise identity man-agement software to the cloud. For that purpose, SAP plans to introduce a central channel to distribute employee and identity data to cloud-based applications. This central channel would be intended to guarantee the consistency of data in the cloud while making sure that only relevant employee data is trans-ferred to the cloud.

The single-sign-on strategy realized by SAP is based on open standards that have proven security features and offer very good interoperability. On premise, SAP has chosen the proto-cols SAML 2.0 and Kerberos as strategic standards. Options like X.509 and logon tickets used in SAP software will continue to be supported. In the cloud, SAP applications support SAML 2.0 as a strategic standard, which is widely adopted by third-party applications.

The SAP NetWeaver Single Sign-On application – an on-prem-ise product – comprises the necessary infrastructure to sup-port all these options to implement single sign-on for SAP products and the overall customer on-premise software land-scape. Alternatively, the open standard strategy followed by SAP allows customers to use their strategic single-sign-on product as long as it also supports these standards.

When moving to the cloud, single-sign-on functionality both among cloud applications and between on-premise and cloud applications is needed. The SAP ID service supports the first scenario, acting as an SAML 2.0 identity provider, while the cloud platforms from SAP support the SAML 2.0 protocol for authentication. An alternative identity provider could be used in special cases. The SAP ID service handles initial authentica-tion and offers the necessary services in case a user forgets his

or her password or wants to change it. After successful authen-tication, the user is redirected with the created SAML authenti-cation assertion to the respective cloud application and auto-matically logged in.

To extend single sign-on from on-premise applications to cloud applications, an on-premise identity provider is needed for which a trusted relationship with the SAP ID service can be established. SAP offers such an identity provider as part of SAP NetWeaver Single Sign-On or SAP NetWeaver ID Management. An appropriate third-party identity provider can also be used. In this case, an employee’s login request to a cloud application is automatically forwarded via the SAP ID service to the on-premise identity provider, which authenticates and redirects the user appropriately. This approach is called “IDP proxying.” A cloud application could also be configured to connect directly to an on-premise identity provider, but using the SAP ID service is recommended, as it avoids the need to configure multiple trust relationships with the cloud.

11Orchestration Overview© 2013 SAP AG or an SAP affiliate company. All rights reserved.

by leveraging federation features of the SAML 2.0 standard. SAP plans to support a second approach for runtime access with an emerging standard called system for cross-domain identity management (SCIM). Figure 8 shows an overview of identity management and single-sign-on infrastructure compo-nents on premise and in the cloud.

Cloud applications can either replicate their identities from the central employee and identity store or access identity informa-tion at runtime without creating their own copy. Runtime access to identity data can avoid costly replication, in particu-lar when extending single sign-on from on premise to the cloud. Therefore, SAP enabled all applications on SAP HANA Cloud Platform for runtime access through the SAP ID service

Figure 8: Identity Management and Single Sign-On for On-Premise and Cloud Software

SAP® ID Service

Cloud Application

Human Capital Management

Identity Management/

Identity Provider

Business Application

Distribute IdentityEmployee/

Identity Channel

Distribute Identity/Employee

Single Sign-On

Create Identity

Single Sign-On

Distribute Identity

Cloud

On-Premise

Hire Employee

IdP

Prox

ying

Fede

ratio

n

12 Orchestration Overview© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Distributed applications that cooperate within a business pro-cess regularly call each other. Consider a sales representative using a cloud application to prepare a quotation for a customer. To determine the price or availability of the products, the cloud application calls an on-premise service. Conceptually, this call to the on-premise software is done on behalf of the cloud user and should be executed with the permissions of this sales rep-resentative. In practice, however, such calls are often enabled with technical users in the called software. Avoiding technical users improves auditability and segregation of permissions: individual permissions can be assigned to the right user in the called software and audit logs can record the correct user who initiated an action. Single sign-on according to the Web Service Security standard SAML Token Profile or the OAuth 2.0 proto-col for Open Data (OData) protocol services are viable alterna-tives supported by SAP. SAP already offers SAML Token Profile for major on-premise software based on the SAP NetWeaver technology platform and OAuth 2.0 on some platforms. SAP plans further enhancements to support these open standards, in particular for applications providing or consuming OData.

Mobile applications from SAP provide access to business data and applications from anywhere. For that reason, data security and user convenience must be carefully balanced. The SAP Afaria® mobile device management solution can enforce a secure passcode for mobile devices. In addition, mobile appli-cations from SAP can optionally be protected by an application passcode. This passcode is used to encrypt confidential data, for example, authentication data, that the application stores on the device. To authenticate the mobile user’s access to busi-ness software, SAP Mobile Platform supports several mecha-nisms. Usually the credentials of the user are provided when configuring the mobile application for the device. SAP is also investigating alternative approaches based on OAuth 2.0.

Business networksCloud-based business network applications facilitate collabo-ration within and between enterprises, for example, for buying and selling goods and services or exchanging information. Enterprises can use these business network applications like other cloud applications. Therefore, the single-sign-on and identity management approaches for cloud applications in the employee scenario are also suitable for users of an enterprise working in the business network account of that enterprise.

Business networks can often enable restricted access of one enterprise to relevant business information in the account of another enterprise. This allows external people to access sys-tems and data of another enterprise on premise with no com-plex identity management procedures required. COnSuMEr SCEnArIO

SAP not only wants to offer first-class applications to the employees of its customers. SAP also wants to help its custom-ers offer first-class applications to their customers, whether they are consumers or citizens. Such applications are prefera-bly deployed in the cloud to be accessed anytime from anywhere.Consumer applications require heterogeneous access con-straints. Some applications can be used anonymously. Some ask for self-registration. Others are restricted to a certain set of users, for example, registered customers. Therefore, SAP plans to provide an infrastructure to define user options according to concrete scenario requirements, such as:

• Anonymous use of cloud applications that provide public information

• Self-registration and central login functionality via the SAP ID service

• Use of Facebook, Google, or similar identities for logon via the SAP ID service in the cloud

If enterprises or organizations have their own registered user base on premise, an application in the cloud can use these identities at runtime via SAML 2.0 federation features or SCIM. It is similar to how it is performed in the employee scenario.

Single sign-on for consumers is possible with the SAML 2.0 protocol, which fits nicely with established consumer services or consumer applications offered in the cloud, for example, from Google or Twitter. For scenarios with consumer applica-tions calling services in other applications, SAP plans to provide support for the OAuth 2.0 protocol.

13Orchestration Overview© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Application and Business Partner Integration

The integration of distributed applications, called application integration, is a classic task and primary objective of orchestra-tion. It is indispensable in supporting processes end to end across applications running in separate systems. Often, the applications and software of business partners, customers, or suppliers must be integrated as well.

After an introduction to the most important types of applica-tion integration, this section explains typical components of an application integration infrastructure. It also discusses SAP’s product and solution offerings for on-premise and cloud solu-tions. Finally, several approaches to business partner integra-tion are reviewed.

tyPES OF APPlICAtIOn IntEgrAtIOn

Application integration covers two basic archetypes: the invo-cation of a remote process step and the transfer of data, called process and data integration (see Figure 9). A wide spectrum of mixed cases is based on these two archetypes.

Examples of process integration are posting a logistics transac-tion to financials for payment and accounting purposes and placing a purchase order with a supplier in an automated sup-ply chain. Data integration examples include transferring the master data needed in processes and feeding analytic applica-tions or data warehouses with data.

Real application scenarios are often a mixture of both types. Master-data integration, for example, frequently uses data inte-gration for the initial load and uses process integration to dis-tribute subsequent changes. Process integration semantics can be implemented with data integration by transferring the data needed by a subsequent process step to that step so it can start.

Data integration can be realized in various ways: • It can be initiated by the source or target application or by a

central integration hub. • Data can be extracted or loaded via APIs or directly via data-

base tables. • Data can be extracted, stored in a file or other container, and

loaded from there or streamed directly between the applica-tion systems.

Typically, data integration must be able to process large data quantities with maximum throughput.

The standard approach for process integration is message-based communication triggered by the completion of a single process step. This trigger should start the subsequent process step without delay. As many process instances can run simul-taneously, process integration technology must be able to pro-cess high volumes of messages with minimal latency.

Some applications don’t support this standard approach. They might lack a trigger at the end of a process step or appropriate messages. Then a combination of data integration and specific logic to determine the end of a process step from changed data sets can help.

APPlICAtIOn IntEgrAtIOn ArCHItECturE

Several components contribute to application integration (see Figure 10). The applications themselves have to provide APIs as access points to their data and processes or to call other appli-cations. The APIs are usually based on a local integration infra-structure that enables remote connections based on certain communication protocols. Central integration hubs can medi-ate between different partners or monitor communication centrally.

IntEgrAtIng DIStrIButED APPlICAtIOnS

Figure 9: Process and Data Integration

Process invocation

Data transfer

14 Orchestration Overview© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Besides providing APIs, applications should trigger messages for process integration at the end of a process step and provide information on data updates to improve data integration effi-ciency by transferring changed data only.

The local integration infrastructure provides the configuration and administration environment for application APIs. It enables the configuration of network communication end points and partners, security settings, and communication protocols. The local integration infrastructure also enables the adaptation and extension of APIs.

Communication protocols define the technical structure of the communication and of data sent through the communication channel. Conversion between different protocols is usually pos-sible without knowledge of the business semantics of the data.

Application integration is possible without a central integration hub if the APIs and communication protocols of two applica-tions are well aligned. Otherwise, or for central control and monitoring of integration traffic for multiple systems, an inte-gration hub is recommended in order to avoid disruption. Cen-tral integration hubs can translate communication protocols and enable integration between diverse applications. They can transform data from one API and adapt it to another API, or implement integration choreographies involving multiple appli-cations that have to communicate in certain sequences. Or

they can operate centrally, monitor the integration, and improve security and error handling.

Applications usually include APIs for standard integration sce-narios. These APIs are typically aligned between applications of the same vendor. When different vendors are mixed or applica-tions are combined in new integration scenarios, adaptations in the local infrastructure, on integration hubs, or even in the application APIs may be necessary.

SAP SOlutIOnS FOr APPlICAtIOn IntEgrAtIOn

SAP provides standard integration solutions for core processes and important analytic scenarios. These consist of necessary application interfaces as well as scenario configuration and logic for the local infrastructure or central integration hubs. Customers can adapt and extend these solutions to their needs, for example, to integrate third-party applications or realize their own distinct business processes.

SAP has chosen open Web service protocols as the strategic standard for communication. On premise, SAP will continue to support classic protocols like Remote Function Call (RFC) and Intermediate Document (IDoc) interfaces. OData is emerging as a standard for the consumption of applications in user inter-faces. SAP is keeping an eye on the evolution of OData and other emerging standards, and it rates their relevance for the integration strategy.

Figure 10: Elements of Application Integration

local integration infrastructure

API

Communication protocol

Central integration hub

15Orchestration Overview© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Customers not willing to buy and operate on-premise hubs can use integration technology in the cloud to connect cloud appli-cations with on-premise software. SAP offers SAP HANA Cloud Integration technology for that purpose in a subscription model. The technology leverages concepts from SAP NetWeaver PI and SAP Data Services for an implementation optimized for the cloud. It covers data and process integration, as a combination of both types is often needed. For example, an initial load of high data volumes can be a pure data transfer, while continuous updates should be distributed quickly via pro-cess integration messages triggered by data changes.

Figure 11 shows a typical hybrid landscape with business appli-cations on premise, in a cloud operated by SAP, and in a cloud operated by a third party. SAP HANA Cloud Integration con-nects cloud applications. Integration to the on-premise IT land-scape is performed via on-premise integration technology for which several options are possible: a standard on-premise inte-gration hub like SAP NetWeaver PI, an on-premise agent avail-able with SAP HANA Cloud Integration, or the local integration infrastructure of the on-premise application. Alternatively, third-party integration technology could be used.

In cases where SAP does not provide an API required for a spe-cific customer scenario, the API can be implemented in the local development or extension infrastructure. When needed for new standard integration scenarios, SAP delivers additional APIs as small, modification-free add-on products to existing SAP Business Suite applications. This eliminates the need to perform a system upgrade.

SAP offers established integration hubs that are operated on premise. For process integration, SAP NetWeaver Process Orchestration software is available. It bundles SAP NetWeaver Process Integration (SAP NetWeaver PI) technology, available now as a pure Java version with improved performance and reduced operation costs, and the SAP NetWeaver Business Process Management (SAP NetWeaver BPM) component. That way, the software supports complex integration flows and choreographies across multiple distributed applications. SAP NetWeaver PI can translate between the classical protocols used by SAP software and the Web service standards, and it can embed further adapters to handle other protocols. In par-ticular, third-party adapters can be applied to enable proprie-tary protocols of other vendors that do not yet support open standards.

For data integration, SAP offers multiple options. SAP Data Services software handles complex extract, transform, and load (ETL) scenarios, supports numerous communication pro-tocols, and can adapt deviating data models. SAP Landscape Transformation software and SAP Sybase® Replication Server® provide real-time data replication on the database table level. This is beneficial, for example, to transfer huge amounts of data quickly from an SAP Business Suite application to an SAP HANA database.

In some cases, it may not be clear whether process integration or data integration technology will best support your objec-tives. A document on SAP Community Network can help you determine whether SAP NetWeaver Process Orchestration or SAP Data Services is best suited to help you.

Integration between on-premise and cloud applications, referred to as hybrid integration, crosses the public Internet. Therefore, special security policies and protocol restrictions may apply. The on-premise integration technology and hubs available from SAP can perform the necessary protocol con-versions, support several security policies, and integrate an on-premise landscape with the cloud.

Figure 11: Integration Hubs on Premise and in the Cloud

SAP® Cloud portfolio

On premise

SAP HANA® Cloud Integration technology

On-premise integration

Third-party cloud

Third-party integration

16 Orchestration Overview© 2013 SAP AG or an SAP affiliate company. All rights reserved.

By combining on-premise and cloud technology, SAP strategi-cally addresses hybrid processes end to end with a hybrid inte-gration infrastructure that also supports existing protocols and applications and connects them with emerging applications and innovations.

BuSInESS PArtnEr IntEgrAtIOn

In the classical form of business partner integration, an appli-cation of one enterprise communicates with an application of a second enterprise, while the applications are operated in the respective on-premise software landscapes of the enterprises. Current integration technology like SAP NetWeaver Process Orchestration provides the necessary business-to-business integration functionality. A variation of this classical form has one of the applications operating in a public cloud, which can also be addressed by existing on-premise or emerging cloud integration technology.

A more recent form of business partner integration is used in business networks. These are application software systems – for example, marketplaces – operated by a provider in the cloud. Each business partner participates with his or her own account in the business network application. Business pro-cesses between business partners may start in one on-premise software landscape, cross both accounts in the business net-work, and then reach the business partner’s on-premise appli-cation (see Figure 12).

The integration technology from SAP is able to connect the on-premise software landscapes with the corresponding accounts in the business network. The business network provider typi-cally connects the accounts, and the end-to-end connection is established. For the Ariba Network – from Ariba, an SAP com-pany – for example, SAP will provide standard integration solu-tions that realize a smooth integration between SAP business applications and the accounts on the Ariba Network.

In summary, the on-premise integration infrastructure pro-vided by SAP allows you to integrate existing business software with new applications on premise, in the cloud, at business partner sites, or in business networks. The infrastructure sup-ports existing protocols and open standards and is comple-mented by an integration infrastructure in the cloud that offers fast time to value.

Figure 12: Integration through a Business network

Business network

17Orchestration Overview© 2013 SAP AG or an SAP affiliate company. All rights reserved.

A FOunDAtIOn FOr BuSInESS PrOCESSES

Master-Data Management

Master data is the foundation for business processes (see Fig-ure 13). The processing of other data relies on master data, and consistent master data in distributed applications is a prereq-uisite for proper process execution across applications. The main task of master-data management is to maintain the con-sistency and the quality of master data according to corporate requirements and policies. Application integration technology can be applied for this purpose as well as a dedicated master-data management infrastructure to address two basic scenar-ios: master-data governance and master-data consolidation. Both scenarios will be explained in this section.

There are many types of master data representing customers, products, organizational units, and cost centers, to name a few. In simple cases, one application, for example, an HCM applica-tion, is the natural owner of the master-data entity, employees. All master data is created, changed, and terminated in this leading application. It is the single source of truth for the entity, implements an appropriate business practice for maintenance, and can provide the master data for other applications (see Figure 14).

Application integration technology facilitates the replication of master data to other applications. It supports both an initial load of master data to a new application and the continuous transfer of changes. For the integration of master data in het-erogeneous software landscapes, the following aspects are important:

• Receiver determination and outbound filtering to define which applications receive which master-data types and which master-data instances

• Key and value mapping to handle: – Deviating identifiers (keys) of master-data instances in

separate systems – Deviating code values with the same semantics, like devi-

ating title codes in separate applicationsThese aspects could be handled with pure application integra-tion technology, yet a dedicated master-data infrastructure helps address them more effectively.

MAStEr-DAtA gOVErnAnCE

Often, a central governance practice should be established to ensure well-defined and consistent master data, enforce com-pliance to company policies and legal regulations, and enable approval processes before master data is used productively. Sometimes, this task can be fulfilled by an application that is the natural owner for a master-data entity. In other cases, such an application is missing or doesn’t provide support for all required governance features. If this is the case, a dedicated master-data governance application (see Figure 15) can be set up as a leading application for the entity. Central maintenance combined with strict validations and monitoring of change pro-cesses can help ensure consistent data of high quality across all applications.

The SAP Master Data Governance application is well suited for that purpose. It includes several master-data entities based on the data models and types provided by SAP Business Suite. Examples include master data for customers, suppliers, mate-rials, and financials. Furthermore, SAP Master Data Gover-nance can be extended with new types of master data. It pro-vides workflows, approvals, rule-based business validations, real-world checks like address validation, and duplicate checks, as well as monitoring and optimization functions for change processes. Distribution of master data is supported by the infrastructure for receiver determination, filtering, and key and value mapping.

Figure 13: Master Data Along a Business Process

Figure 14: replication of Master Data from a leading Application

Master data

Master data

Master data

Master data

Replicate Replicate

18 Orchestration Overview© 2013 SAP AG or an SAP affiliate company. All rights reserved.

To support master-data consolidation, SAP Data Services software offers various data quality and cleansing functions. SAP plans to provide a dedicated master data consolidation solution based on SAP HANA. Data services within the SAP HANA platform shall be used to extend master-data gover-nance processes in SAP Master Data Governance, enterprise edition. This integrated governance and consolidation solution shall let you start the governance process immediately for a consolidated record originating from decentralized mainte-nance. The first focus here is planned for customer master data but the solution is also meant to address additional master-data types later on.

The application integration technology employed by SAP covers applications on premise, in the cloud, and in business networks. It serves as a comprehensive basis for the exchange of master data and the use of master-data related services. This enables master-data management software from SAP to run on premise and also to serve applications in the cloud, representing a stable foundation for handling master data across distributed applications.

MAStEr-DAtA COnSOlIDAtIOn

Often master data from different sources must be consolidated (see Figure 16). The multiple sources could be the result of hav-ing multiple applications in which master data is maintained locally, the merging of legacy systems, or data imported from external sources. Consolidation can be executed on a large set of master data to prepare the data for use in analytic process-ing or as an initial load for a new application. It can also serve as a starting point for master-data governance. This consolida-tion typically starts with data cleansing based on validation rules and real-world checks like address validations. Records are then matched to identify duplicates, and a “best record” with the most complete, accurate information is determined. Consolidation services could be called from an application when users enter or change master-data instances to validate or enrich them or to prevent the creation of duplicate records.

Figure 15: Master-Data governance Figure 16: Consolidation of Master Data

Master data

Master data

Master data

Master data

Master data

Master data

Central Governance Central Consolidation

19Orchestration Overview© 2013 SAP AG or an SAP affiliate company. All rights reserved.

OPtIMIzED PrOCESS ExECutIOn

Business Process Management

The field of business process management comprises all aspects of business processes in an enterprise, including their implementation and execution on an IT infrastructure. It can be defined as the discipline that aligns an enterprise and its tech-nology infrastructure to its business needs and targets.

Business process management is closely related to the disci-pline of enterprise architecture. It captures the main entities of an enterprise and their dependencies, such as processes, orga-nizations, and IT applications. Based on this information, busi-ness software realizing the required business processes can be defined, implemented, refined, and optimized. SAP supports these areas of business process management with SAP Sybase PowerDesigner® software as well as with the SAP Solution Manager application management solution, which covers mod-eling, IT management, and application lifecycle management.

In this document, we focus on process execution, business rules, collaboration, and the continuous optimization of busi-ness processes. It is worthwhile here to emphasize an elemen-tary difference in the implementation of business processes. There are built-in processes (see Figure 17) and engine-driven processes (see Figure 18). Most business processes realized within packaged business

applications are implicitly defined through their application logic and configuration, independent of whether they are pro-vided on premise or in the cloud. The processes are executed by transactional activities triggered by a user interaction or a service call. These are called built-in processes. They allow a great flexibility in execution, which is typically needed in core business processes like “sales execution.”

Engine-driven processes are based on an explicit process defi-nition that is executed by a process or workflow engine (like the SAP Business Workflow® tool or SAP NetWeaver BPM) that calls and combines separate modules. They are better suited for more strict processes like approvals. Business processes are often composed of both types of processes.

Engine-driven processes are particularly advantageous for real-izing customer-specific practices without developing program code. Existing applications can be combined and executed according to a customer-defined process model. SAP NetWeaver BPM is well suited for that purpose. It is a state-of-the-art, robust, highly scalable, cross-system process manage-ment tool with enhanced supportability and improved usability for its cross-system in-box functionality.

Figure 17: Built-In Process

Figure 18: Engine-Driven Process

Process engine

Process step in application

20 Orchestration Overview© 2013 SAP AG or an SAP affiliate company. All rights reserved.

COllABOrAtIOn

One way to improve process execution is to support collabora-tion within or along a business process better.

Business processes often include steps of collaborative human activity without a predefined structure, for example, negotia-tions within an enterprise and with business partners, or the resolution of an unforeseen issue. These steps of collaborative and often creative work play an important role in the successful execution of processes, but they are difficult to capture in a for-mal process model. Nevertheless, activities undertaken during collaborative steps, the participants, their contributions, and the overall results should be facilitated in a structured way to preserve them for later reference when similar situations occur.

Social networks are becoming popular places to store and exchange information about human cooperation. Collaboration employs much greater dynamism than traditional applications allow. On request, internal experts or external business part-ners can be involved, even if they have no permission to access the business applications. Therefore, enterprise social net-works should run in the cloud to be accessible from anywhere by anyone who is invited to join.

BuSInESS rulES

Both built-in and engine-driven processes can leverage busi-ness rules management software to increase flexibility. This is software used to define, deploy, execute, monitor, and maintain a variety and complexity of decision logic. This logic, also referred to as business rules, includes policies, requirements, and conditional statements to determine the tactical actions in processes. A core element of the business rules approach is the execution transparency for functional experts and the ability to implement changes to the rules without technical support.

Typical components of business rules management software are:

• A repository allowing decision logic to be externalized from core application code

• Tools enabling technical developers and business experts to define and manage decision logic

• A runtime environment allowing applications to invoke deci-sion logic managed within the business rules management software and execute it using a business rules engine

Business rules management software increases control over implemented decision logic for greater compliance and better business management. Decision logic can be expressed with increased precision using a business vocabulary syntax and graphical rule representations (so-called rule flows), including decision tables, trees, and scorecards.

SAP offers the following comprehensive business rules man-agement software:

• SAP NetWeaver Decision Service Management software and Business Rule Framework software for applications based on the ABAP® programming language

• The SAP NetWeaver Business Rules Management (SAP NetWeaver BRM) component for Java-based applications, which is part of SAP NetWeaver BPM

21Orchestration Overview© 2013 SAP AG or an SAP affiliate company. All rights reserved.

By assigning a collaboration group to a process instance or step, a clear connection is established (see Figure 19). This pro-vides direct navigation to the collaboration information from a later process step or from a different process instance with a similar situation. That makes it possible, for example, to quickly navigate from accounting to the collaboration that documents customer negotiations, to research some contract detail, or to find the people who were involved in that collaboration. If a pro-cess issue is detected that was solved in a previous process instance, the related collaborative activity can give valuable hints about the solution. Collaboration can be supported by direct access to business data from collaboration groups and the use of feeds to push process information or activities to users.

SAP leverages the SAP Jam social software platform to sup-port collaborative aspects of processes better. Processes are closely connected to collaboration through business objects and processes. Users can be informed via feeds triggered from process events. SAP extends typical functions of a social net-work with access to business data to provide the context of the business process to users of SAP Jam.

PrOCESS OPtIMIzAtIOn

Over the last 10 to 15 years, enterprises used dedicated soft-ware to optimize their business processes. They evaluated their process-related business data with analytic methods, cal-culated and compared key performance indicators (KPIs) for processes based on business data, and adjusted and improved their processes accordingly.

Current solutions fully exploit the potential of this approach. Further improvements need to go beyond classical approaches by:

• Including a greater level of detail on the execution of individ-ual process instances and their context, and improving process visibility

• Including real-time information on running processes • Supporting users with automated rule-based evaluation of

these huge amounts of data in real time • Supporting the adjustment and optimization of running

processes • Supporting collaboration in the context of a process,

especially in cases of process issues, and capturing it for later reference

Process optimization has two flavors: • It can address a process in general by changing the process

definition or model, for example, by omitting an approval step, which results in executing all future process instances in a new way.

• It can focus on running process instances, detect execution issues of an individual instance as soon as possible, and adjust the process if necessary while it is still running.

Optimization of the process definitions is traditionally based on business data, the business outcome, carefully defined KPIs, and statistical analysis of historical data. The constant need for systematic optimization of business processes to increase pro-cess efficiency is referred to as business process improvement. Its aim is to achieve more efficient results of overall process execution by measuring, analyzing, and improving existing pro-cesses and adopting new process requirements.

As established functionality, business process analytic soft-ware, an offering of SAP Enterprise Support services in SAP Solution Manager, supports a large set of predefined through-put and backlog indicators for built-in processes of SAP

Figure 19: Collaboration Assigned to a Process Step

Collaboration

22 Orchestration Overview© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Business Suite. Focus is on business process improvement of traditional best-practice processes that support backlog and bottleneck analysis and benchmarking. These analytic func-tions work on business data retrieved from back-end software. Further functions are trend, age, and detail analysis for root cause analysis.

Further insight can be gained using process logs that provide an additional level of information on the process instance level. For engine-driven processes, detailed process logs of the exe-cution engine are usually available. Comparable information is often missing for built-in processes. Only limited information can be derived from business data in the applications. To sup-port advanced process optimization, applications must provide more detailed logs of all executed steps of built-in processes, including information on their business context.

The process observer functionality provides detailed logs of the execution of built-in processes in SAP Business Suite appli-cations, thus making the backbone of many business pro-cesses visible. It can also deliver business data related to a pro-cess step.

Business processes often span multiple distributed applica-tions. The logs of processes running in individual applications on separate systems have to be combined for end-to-end visi-bility, taking connection information from the application inte-gration infrastructure into account (see Figure 20).

In the past, numerous approaches for process analytics and optimization were available, but generally they did not prove to be effective, which was in part due to technical limitations. A vast amount of detailed information available in process logs about the process flow and execution of each individual pro-cess instance should be processed in real time. This can only be fully utilized with in-memory computing technology, some-thing recognized by the overall market, where a trend toward in-memory computing can be seen. Besides real-time analytics on large amounts of data, in-memory analysis closes the loop between real-time analytics and transactional data by bringing the analytics into the transactional system. In-memory com-puting is the key approach to achieving the next level of pro-cess excellence. It can provide deeper insight that enables improvement and optimization of business processes on new levels.

SAP Operational Process Intelligence software powered by SAP HANA combines process logs from distributed applications and process engines as well as data from the business context to create federated end-to-end visibility. With these features, many important processes are made visible with a level of detail that was not possible before.

Figure 20: Visibility of Processes End to End

Visibility

23Orchestration Overview© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Instance optimization requires detailed, timely information on all processes in execution to quickly detect indicators for pro-cess issues or delays. While the process logs provide deep insight and a high level of detail, it is not possible for human beings to consume the vast amounts of data in real time. Therefore, powerful real-time evaluation of process logs based on in-memory computing is needed. In combination with rule-based decision logic, it makes possible the continuous moni-toring of running processes and can detect evolving issues, forecast delays, and alert responsible users.

Process logs support the optimization of processes in various ways. They can be used to:

• Show an overview and drill down to details of a single pro-cess instance spanning multiple distributed applications to investigate the root cause of an issue

• Define KPIs and analyze processes with varying process defi-nitions or parameters to test optimization options

• Identify process instances on a critical path, monitor them, and adjust them in time

• Simulate next steps of running processes, predict their com-pletion, compare alternatives, and suggest optimizations

• Analyze running processes, compare their progress to histor-ical averages, predict how long it will take for them to com-plete, and use this information in business planning

• Automate decisions in processes based on rules, process variants, and historical data

SAP HANA enables in-memory computing for analysis as described in the different solutions above. SAP Operational Process Intelligence gives insight into processes end to end in SAP and non-SAP software. These products, together with the process observer functionality, allow customers to monitor and optimize their critical processes according to their specific rules and KPIs.

24 Orchestration Overview© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Outlook and Conclusion

The orchestration approach advanced by SAP addresses tradi-tional on-premise systems and current trends in cloud com-puting, collaboration with business partners, use of mobile devices, and specialized applications that can process huge amounts of data. Orchestration enables the integration of these innovations with existing applications from a user, busi-ness process, and data perspective.

In addition to connecting today’s innovative applications, SAP has started to leverage innovations for improved orchestration infrastructure and features. Examples include SAP Master Data Governance, enterprise edition, powered by SAP HANA; and SAP HANA Cloud Integration. SAP harnesses synergies with existing products and technologies, for example, for applica-tion integration, which leads to hybrid infrastructures. These combine proven technology and innovative approaches to offer a broader range of options and improved functionality in emerging hybrid IT landscapes.

A promising new innovation area in orchestration is the com-bined use of technologies to achieve business process excel-lence. It addresses scenarios like process intelligence powered by SAP HANA, which monitors running business processes and matches their progress against historic data and customer-specific rules. This computationally intensive task becomes feasible with in-memory computing technology. When an issue is detected, the people responsible are informed and collabora-

tion along the process chain is initiated. SAP Jam for collabora-tion in the cloud lets external business partners be included as well. Process insight, additional data, and decision-support rules help those involved reach a well-informed decision quickly and make necessary adaptations in real time (see Fig-ure 21). Closing the loop from issue detection to resolution in limited time is vital for business success.

In the future, SAP expects a continuation of the overall trend toward smaller, more-focused applications. These will deliver specific business benefits with superior user experience, mobile access, special collaboration or data processing func-tions, and varying deployment options. They will need a context to run in, get their data from this context, and connect to this context in processes. SAP addresses this trend with suitable platforms on premise and in the cloud – and with orchestration technology, as described in this document. Orchestration remains SAP’s method of choice for the integration of innova-tive applications with existing business software.

The future will surely bring surprises – new trends and innova-tions that drive information technology in the coming years. For that reason, SAP closely monitors research and market trends to keep its products and services competitive and to evolve its orchestration strategy. By adapting this strategy to accommo-date upcoming innovations for close integration with existing applications, SAP helps IT departments benefit from innova-tions while leveraging past investments.

IntEgrAtIng InnOVAtIOn wItH ExIStIng SOFtwArE

Figure 21: Continuous Process Improvement

Rules and tools

Collaboration

Process insight

Decision

25Orchestration Overview© 2013 SAP AG or an SAP affiliate company. All rights reserved.

nEtwOrK lOCAtIOnS

Find Out More

For more information, visit the following network locations.

generalProduct and solution road maps

• SAP® technology portfolio • SAP NetWeaver® technology platform • SAP NetWeaver Identity Management • SAP NetWeaver Single Sign-On • SAP NetWeaver Process Integration • Enterprise information management • SAP Data Services Enterprise • Enterprise master-data management • SAP NetWeaver Process Orchestration • SAP Solution Manager • SAP NetWeaver Business Process Management

Available at SAP Service Marketplace at http://service.sap.com/roadmap

SAP HANA® http://scn.sap.com/community/hana-in-memory

SAP Business Suite http://scn.sap.com/community/business-suite

Single Sign-On and Identity ManagementSAP NetWeaver Identity Management http://scn.sap.com/community/netweaver-idm

SAML 2.0 http://en.wikipedia.org/wiki/Security_Assertion_Markup_ Language

Kerberos http://en.wikipedia.org/wiki/Kerberos_(protocol)

X.509 http://en.wikipedia.org/wiki/X.509

Logon tickets for SAP software http://wiki.sdn.sap.com/wiki/display/BBA/Single+Sign-On

SAP NetWeaver Single Sign-On http://scn.sap.com/community/netweaver-sso http://help.sap.com/nwsso

SAP ID service Available at SAP HANA Cloud Platform Documentation at https://help.hana.ondemand.com/help

SAP HANA Cloud Platform https://help.hana.ondemand.com/help

System for cross-domain identity management (SCIM) www.simplecloud.info

SAML Token Profile http://docs.oasis-open.org/wss-m/wss/v1.1.1/os/wss-SAML-TokenProfile-v1.1.1-os.html

OAuth 2.0 http://en.wikipedia.org/wiki/OAuth

SAP Afaria® www.sybase.com/products/mobileenterprise/afaria

SAP Mobile Platform http://help.sap.com/mobile-platform

26 Orchestration Overview© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Application and Business Partner IntegrationWeb service protocols http://en.wikipedia.org/wiki/Web_service

Remote Function Call (RFC) http://help.sap.com/saphelp_nw73ehp1/helpdata/en/48/88068ad9134076e10000000a42189d/content.htm

Intermediate Documents (IDoc) http://help.sap.com/saphelp_nw73ehp1/helpdata/en/4a/b074b6aa3a1997e10000000a421937/content.htm

Open Data (OData) www.odata.org

SAP NetWeaver Process Orchestration http://scn.sap.com/community/process-orchestration

SAP NetWeaver Process Integration http://scn.sap.com/community/pi-and-soa-middleware

SAP NetWeaver Business Process Management http://scn.sap.com/community/bpm

SAP Data Services http://scn.sap.com/community/data-services

SAP Landscape Transformation http://scn.sap.com/community/saplt

SAP Sybase® Replication Server® http://scn.sap.com/community/sybase-replication-server

Positioning of SAP NetWeaver Process Orchestration and SAP Data Services

http://scn.sap.com/docs/DOC-3856

Business-to-business integration http://scn.sap.com/community/b2b-integration

SAP HANA Cloud Integration http://scn.sap.com/docs/DOC-40396

Ariba Network www.ariba.com

Master-Data ManagementSAP Master Data Governance http://scn.sap.com/community/mdm/master-data-gover-

nance

Enterprise information management http://scn.sap.com/community/enterprise-information-man-agement

Several references shown for application integration above are also relevant for master-data management

27Orchestration Overview© 2013 SAP AG or an SAP affiliate company. All rights reserved.

COntACt InFOrMAtIOn

To learn more about the orchestration approach used at SAP, or to discuss this approach with SAP experts, please contact us at [email protected].

Business Process ManagementEnterprise architecture https://en.wikipedia.org/wiki/Enterprise_architecture

SAP Sybase PowerDesigner® http://scn.sap.com/community/sybase-powerdesigner

SAP Solution Manager http://scn.sap.com/community/it-management/alm/solu-tion-manager

SAP Business Workflow® http://scn.sap.com/community/bpm/business-workflow

SAP NetWeaver Business Process Management http://scn.sap.com/community/bpm

SAP NetWeaver Decision Service Management http://scn.sap.com/docs/DOC-29158

Business Rule Framework plus http://scn.sap.com/docs/DOC-8824

SAP NetWeaver Business Rules Management http://scn.sap.com/community/brm

SAP Jam www.sap.com/jam

Process observer http://scn.sap.com/docs/DOC-24983

SAP Operational Process Intelligence http://scn.sap.com/docs/DOC-35420

www.sap.com/contactsap

CMP26084 (13/10) © 2013 SAP AG 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 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. National product specifications may vary.

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 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 other countries.

Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.