on 04-29-2014 8:50 AM
Hi,
I just encountered a concept of POL(Process Object Layer).
It seems that POL has a particular layer in ABAP stack to help process management.
How does POL work?
I would like to know how PO is used in interface and BPM technically.
Also, my another question is about SOA approach in technical.
If there are unit function modules/web services that can present an enterprise service,
then should we expose single enterprise service putting together all the relevant unit services?
Or should we build process object or business processes to orchestrate single processes?
Looking forward to hear from you, expert.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi colleagues,
to be precise. What was is likely meant as POL (Process Object Layer) is available as a product called Process Object Builder, see SAP Process Object Builder (CA-FS-POL) - SAP Library. It is a tool that helps orchestrating processes. Contact here is .
The relationship between Process Object Builder and Process Observer is that Process Object Builder uses/is integrated into Process Observer for monitoring the orchestrated processes. So this means that you can easily generated process logs using Process Observer for processes orchestrated with Process Object Builder for monitoring and further evaluation.
Regards,
Bernd
Process Object Layer:
The Process Object Layer has been introduced as an additional software layer in the architecture model:
Communication between the software layers and the Process Object Layer is based on Web services. Back-end applications are therefore integrated across all systems.
To communicate with back-end systems, the layer consumes the synchronous and asynchronous services provided by the back-end systems.
The layer can also consume services from non-SAP systems.
The layer provides new object-specific services (POT/PROT services) for the business processes to be implemented. These can in turn be consumed by front-end applications or tools for process orchestration (such as SAP Business Process Management).
This layer therefore acts as a mediator between back-end system and front-end channels. It enables transparent status and event management for all business objects that are involved in a business process.
Data required for the business process is persisted.
Business Process Management (BPM) Process: POT is integrated with BPM. The BPM orchestrates the POT services sequence.
Using BPM is optional for orchestrating a POT. We can also use other tools for handling errors.
Thanks & Best Regards,
Deependra
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Deepandra already explained it very well. I would just like to add some information.
I would like to emphasize that orchestration is not the major target of process objects although like in BPM and any other implementation it is necessary to call the services in a sequence.
Process Objects (POTs) provide a transactional behaviour
Persistent Retrieval Objects (PROTs) are a spin-off which focus on data provisioning across multiple components:
Best regards,
Werner
Hi Hyeyoung Han,
I have same doubt: how POL & BPM are different ? .
Kindly let me know if you found the answer . it will be very helpful.
Best Regards,
Deependra
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
10 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.