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:
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
31 | |
24 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
5 | |
4 |