Skip to Content

NW Process Orchestration is a bundled product of BPM, BRM and PI. This combination can easily extend your existing and new applications into the mobile environment, beyond the existing system-to-system integrations. In this blog, I will discuss the different options and benefits.

Overview

Process Orchestration, introduced in 2011, provides business process management and integration between SAP and non-SAP applications/systems, and provides user-interactions capabilities between users and applications/systems. It provides a centralized design and configuration environment for business processes, workflows and integration. Many of us are already using these capabilities. Now, we can easily extend these benefits and capabilities to the mobile environment, to allow your mobile users to participate in business processes, workflows and access to SAP and non-SAP systems.

For more information on Process Orchestration, please reference the following links:

With Process Orchestration, not only will the mobile users be able to participate in business processes, to access the company’s SAP and non-SAP applications, but also provide capabilities for the backend application to send notifications and messages to mobile users, e.g. for workflow purposes, status, and acknowledgement for special tasks.

Implementation Options of Using Process Orchestration for Mobile Applications:

  • Using standard protocols and framework directly with mobile applications
    • Provision SOAP, REST and HTTP services for the mobile applications to access business processes, backend SAP and non-SAP applications/systems.
    • Consume SOAP, REST or HTTP services. (HTTP service is sometimes used for notification purposes.)
  • NW Process Orchestration provides three of the primary protocol for mobile applications, SOAP, REST and HTTP. (REST adapter can be licensed from SAP’s business partner.)
    NW Process Orchestration will be able to:

  • Using Sybase Unwire Platform (SUP)
  • SUP is a platform to manage and administer a company’s mobile application environment. It not only provides a development environment to develop generic user interfaces that can be deployed to multiple end-user devices, e.g. iPhone, iPad, Android, Blackberry, it also manages security and accesses to the company’s backend systems.

    SUP is a platform that sits between NW Process Orchestration and end-user mobile devices. Messages between NW Process Orchestration and end-user devices must go through SUP. With this architecture, security and accesses can be managed easily and centrally. For example, when an employee leaves the company, his mobile access to company’s applications and systems can be revoked immediately and easily.

This blog is only an initial discussion of how NW Process Orchestration is ideally suited to meet company’s needs in system-to-system and user-to-system business processes, and how easily it can be extended to the mobile environment. In future blogs, we will go into more details in architecture and implementation guides.

To report this post you need to login first.

3 Comments

You must be Logged on to comment or reply to a post.

  1. Prateek Raj Srivastava
    Hi Bill,
    Thanks for the blog!
    I was wondering what would SAP recommend for the mobile solution even if a customer already has PI in the landscape. Will it be NetWeaver Gateway or PI?
    I understand that this blog shows capability of PI to connect to mobile devices. However, when it comes to consulting, what will be the best practice? Are their some additional new capabilities with Process Orchestration which will make it competitive against Gateway in terms of light weight access?
    Kind regards,
    Prateek Raj Srivastava
    (0) 
    1. William Li Post author
      Hi Prateek,
      As with most SAP’s response:  It depends 🙂

      REST is usually recommended for light weight access for mobile devices.

      If the customer already has PI, it might be prudent to evaluate a REST adapter from a 3rd party partner (right now Advantco provides a generic PI REST adapter and MuleSoft will have a Salesforce.com adatper which is based on REST.)

      Having this option in PI will allow the customer to examine their business cases between PI and Gateway.  (A paper on Gateway and PI is in the works, soon to be published, that will help customer during the evaluation of Gateway and PI.)

      Regards,
      Bill

      (0) 
  2. Shabarish Vijayakumar
    Li,

    Why is SAP not provisioning the REST adapter as an out of box feature? When SAP PO is being provisioned as the next big thing, without the REST adapter as a standard functionality it doesnt help connect the dots.

    Just my opinion.

    Also will be great to see SAP’s view on Gateway vs SAP PO 🙂

    Regards,
    Shabarish

    (0) 

Leave a Reply