Update: thanks to the huge interest, access to registration and recordings has been extended until 30 April 2014. Go grab your recording and slides! |
|---|
If you have missed the
Process Orchestration webcast series you still have the chance to grab the recordings and slides. Recordings will be available until the end of 2013 to all registrants. More details about each particular sessions and how to get the recording can be found in the session follow-up blogs:
We are very happy with the high interest and that so many participants have joined us and asked so many questions. We have received a lot of positive feedback that these sessions were useful to many in revealing different aspect of the SAP Middleware platform and all new and continuous investments that make it best in class.
In this blog we would like to share some of the most common and also the most interesting questions that have been raised. We hope you will find these useful. Thanks to katrin.ahsen, stephan.schluchter, eduardo.chiocconi, christian.loos and alexander.bundschuh for the input.
SAP Operational Process Intelligence Session:
Q: If my organization already has SAP NetWeaver Process Orchestration, why we would need to also license SAP Operational Process Intelligence powered by SAP HANA?
A: SAP Operational Process Intelligence is an SAP HANA technology solution - it can consume events from SAP Business Suite, SAP Business Workflow, and SAP NetWeaver Process Orchestration – as they act as the content provider systems. SAP HANA is needed to deploy the solution and then it’s configured to receive events from some or all these different provider systems. Using the native analytical intelligence capabilities of
sapopint your organization is gaining end-to-end visibility into its business processes.
Q: Should SAP Operational Process Intelligence be applied to all my business processes?
A: In general this is possible. Based on our customer engagements so far, the mission critical processes (the most important ones for your business) are a good starting point to create the most value of the usage of this solution. But yes, you can apply this to all your processes.
Q: How is the technical link made between SAP Operational Process Intelligence powered by SAP HANA and SAP NetWeaver Process Orchestration?
A: It uses SLT at runtime to replicate the events. SLT is included with HANA.
Q: So is this brand new product? What do I have to buy?
A: Yes, SAP Operational Process Intelligence is a new solution and it is priced separately. You can test drive it today – find out more details
here. For further details on pricing please contact your local SAP representative.
Q: Sounds like SAP Operational Process Intelligence is something very complex.
A: In fact the solution itself shields the complexity from you. It collects, correlates and contextualizes the events and processes from the content provider systems and displays all crucial information to the business users. Yes, it’s a complex topic, as end-to-end processes are, but SAP Operational Process Intelligence let you focus on the business aspects of the processes. It tracks business processes in real-time and provides very comprehensive, focused visualization and intuitive user interface for the line of business users so they can make timely and informed decisions.
Q: If I want to get more information – where will I find this?
SAP NetWeaver Process Orchestration Overview Session:
Q: Does the use of SAP NetWeaver DS indicate that SAP NetWeaver DI is mandatory to deploy BPM development to QAS and PRD?
A: Technically, BPM processes can also be deployed without SAP NetWeaver DI (NWDI) using the Deployment perspective of SAP NetWeaver DS. However, for productive usage, NWDI is highly recommended as the central repository, build and transport system.
Q: Does SAP NetWeaver DS inSAP NetWeaver Process Orchestration allow designing Process Integration service interfaces like we do in IR and ID?
A: Starting with SAP NetWeaver Process Orchestration 7.31 you can implement your integration scenarios in SAP NetWeaver DS, using the SAP NetWeaver Process Integration Designer perspective.
Q: From which version of SAP NetWeaver CE we could upgrade seamlessly to SAP NetWeaver Process Orchestration?
A: It is possible to upgrade SAP NetWeaver CE to SAP NetWeaver Process Orchestration since version 7.1. First, you need to upgrade your CE system to SAP NetWeaver 7.31 or 7.4, and then deploy AEX as an additional usage type. See SAP note 1868764 for more information.
Q: Will SAP NetWeaver Process Orchestration require additional license if we already have SAP NetWeaver PI 7.3?
A: Yes. SAP NetWeaver Process Orchestration is different from SAP NetWeaver Process Integration and includes 2 additional components: SAP NetWeaver BPM and BRM. To find out which is the best option for your organization to migrate licenses, please contact your local SAP Account Executive.
Q: How to use SAP NetWeaver Process Orchestration / BPM along with MDG - Master Data Governance which is ABAP and workflow based?
A: SAP NetWeaver Process Orchestration via its Business Process Management capabilities (BPM) allows the creation of standard based governance and master data management business processes that can connect to MDG and other backend systems of records where information needs to be syndicated. Processes created with SAP NetWeaver Process Orchestration can be exposed as SOAP Web Services to start the master data management process and also reach out these backend systems via any available APIs.
Q: Approximately how many customers have the SAP B2B / EDI modules in production at this time?
A: Official references are made available on SAP.com. SAP does not disclose information other than official references. It is worth pointing out that SAP NetWeaver PI has been used for many years as a B2B hub leveraging B2B Adapters from partners and exchanging EDI documents in different formats. The B2B Add-on brings SAP native B2B capabilities providing a more unified middleware footprint and streamlined access to SAP Ariba Business Network.
Q: Are developments reusable with SAP NetWeaver Process Orchestration - can I reuse development components for different project?
A: Yes. SAP NetWeaver Process Orchestration is a bundle solution that allows creating different types of projects for BPM, BRM and Integration scenarios. These projects can interoperate with one another and also establish dependencies for tracking project relationships. All assets created within these projects can also be exposed as reusable services enabling a loosely coupled way of connecting one with another.
Q: Does using SAP NetWeaver BPM along with PI have any negative effect on the performance of the message processing?
A: As with any system it is necessary to size the footprint for the peak processing time, taking into consideration all usage types (both PI messages and BPM processes). There is also the option to move individual business-critical integration scenarios to a dedicated, de-central adapter engine (DAE).
Q: Does SAP NetWeaver Process Orchestration support federated deployment options?
A: Yes. SAP NetWeaver Process Orchestration introduced the co-deployment option for SAP NetWeaver PI, BPM and BRM as a new deployment topology. Although for initial rollouts, it is also possible to deploy all these components separately and distributed creating a federation of services that can still connect with each other to accomplish the broader goals of a unified middleware stack supporting multiple and diverse use cases and scenarios.
Q: Is it recommended to use SAP NetWeaver Process Orchestration on one SID with extensive UI WD Java developments from SAP NetWeaver CE environment?
A: It depends. System sizing needs to account for all deployed scenarios. But generally speaking the co-deployment scenario on one SID has its advantages as highlighted during the webcast.
SAP NetWeaver Process Orchestration Roadmap Session:
Q: Will SAP be coming up with option to split SAP NetWeaver PI dual-stack and upgrade to SAP NetWeaver Process Orchestration (assuming all interfaces are moved to AEX)?
A: At this point, there is no direct upgrade path from SAP NetWeaver PI dual-stack to Process Orchestration Java-only option. However SAP has offered a migration tool for SAP NetWeaver PI to help and aid in migrating most assets to the single Java AEX runtime. Some assets cannot be migrated directly / automatically, like ABAP proxies and ccBPM.
Q: SAP NetWeaver 7.4 is in General Availability now and PI is part of it. Does it make sense for me to upgrade?
A: Changes in SAP NetWeaver 7.4 are mainly on the ABAP side and in the support for SAP HANA. Feature-wise, SAP NetWeaver 7.31 SP8 is equivalent to 7.4 SP3.
Q: Do I have to do DB/OS migration for our SAP NetWeaver PI system if I want to use SAP HANA?
A: If you want to use SAP HANA as a backend DB, then you will need to migrate. If you want to send SAP NetWeaver PI and BPM events to SAP Operational Process Intelligence, you do not need to change the underlying DB.
Q: Is the pre-packaged integration with SAP Ariba or CrossGate included in the SAP NetWeaver Process Orchestration license?
A: These pre-packaged integrations are offered as part of Rapid Deployment Solution (RDS) packages that are priced separately. For more information please contact your local SAP Account Executive.
Q: With what service pack is available the Rapid Deployment Solution for integration with SAP Ariba Network?
A: This RDS requires SAP NetWeaver PI release version 7.3 SP07 or PI 7.31 SP04 and your SAP ERP backend needs to be on release level 6.0 SP12, EHP 5 SP08 or EHP6 SP04.
Q: What is current recommendation for the monitoring of SAP NetWeaver PI 7.31 SP7? Is it Component Based Monitoring or should we implement Integration Visibility. Should we still use CCMS for end-to-end monitoring?
A:
Currently the monitoring of the following runtimes is supported: SAP NetWeaver PI (AEX, ABAP Integration Server, Central AE, De-central AEs) and SAP backend system layers ABAP Proxy and ALE. However full Integration Visibility capabilities will be available with the next service packs. For more details see this blog:
What is new in SP7 of SAP NetWeaver Process Orchestration 7.31. Please follow the space on SCN to stay up to date with information about next service packs.
Q: How does SAP NetWeaver Gateway fit in the SAP NetWeaver Process Orchestration roadmap?
Q: We are looking at migrating from SAP NetWeaver PI dual-stack to AEX – Java-only or Process Orchestration. Does SAP provide a tool and support for that?
A: There is already a migration tool available allowing you to migrate Integration Directory objects from SAP NetWeaver PI dual-stack towards PI Java-only or Process Orchestration in an semi-automated fashion.
Q: Are there any plans to provide an automated tool for ccBPM (dual-stack) to SAP NetWeaver BPM (single stack). If no, what kind of support SAP can provide for customers who want to migrate from ccBPM to SAP NetWeaver BPM.
A: Integration Directory can be migrated using the migration tool, see the answer of the previous question. SAP does not deliver a tool for migrating ccBPM towards SAP NetWeaver BPM, because they are fundamentally different. ccBPM will continue to be supported, however the use of SAP NetWeaver BPM is strongly recommended. SAP has announced back in 2011 that SAP NetWeaver BPM is the standardized process engine going forward for whatever orchestration you may need, be it for system-centric, human-centric processes or a combination of both. Please refer to this article:
SAP NetWeaver BPM for System-to-System Message Orchestration (Including Migration of ccBPM to SAP Ne.... It describes how to develop a stateful system-centric message orchestration business process using the BPM component of SAP NetWeaver Process Orchestration 7.31, instead of using ccBPM. It will show you the basics of stateful system-to-system message orchestration using SAP NetWeaver BPM. It also showcases a simple use-case scenario of the design and configuration requirement of integrating SAP NetWeaver PI and SAP NetWeaver BPM to cover similar use cases as for ccBPM.
Considerations for customers migrating from SAP NetWeaver PI dual-stack to Process Orchestration single-stack configuration and as part of this transition will be using BPM capabilities for user centric scenarios:
Q: If the scenarios involve too many BPM projects deployed, how to make sure the performance of the existing A2A scenarios is not affected. Shall we look into distributed deployment where we have a single java SID for A2A scenarios and another one for BPM scenarios.
A: Instead of having separate Process Integration/ Orchestration domains it is recommended to have one Process Orchestration and adding additional non-central Adapter Engines to the Process Orchestration domain. That way you will be able to run BPM scenarios on the central Adapter Engine of Process Orchestration and stateless A2A scenarios on the non-central AEs. This approach allows to configure centrally all scenarios. This is also more convenient from monitoring point of view.
Q: What features we will be missing if we chose a separate deployment of SAP NetWeaver PI from SAP NetWeaver BPM for A2A and BPM scenarios. Would there be important features compromised because of a separate deployment configuration?
A: Separation of A2A/BPM scenarios is a reasonable approach, however Process Orchestration Java SID is recommended for both systems for the following reasons:
- For A2A, BPM might be required for stateful integration processes or business rules management for receiver determination etc.
- For BPM, PI adapters and mapping may still be required to connect to backend systems.
- Reliable connectivity between PI and BPM via XI3.0 protocol (WS-RM is not available for PI Java!)
- Reuse of mappings from PI in BPM
- End-to-end monitoring between PI and BPM
Please also have in mind that the footprint of a pure AEX or BPM system is not that different from a Process Orchestration system.
We will continue sharing information about future service packs and future innovation plans in the .
We will add more information as we go, so feel free to join the discussion by adding your questions and comments.
