Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Ebpm/Service Manager
< Ebpm
Introduction
At a first glance eBPM could seems to be a Complex Platform to use. This is mainly because:
- The Overall Solution is composed by a set of pieces working together instead of distributing a whole package.
- A wide range of capabilities and configuration options is offered. The goal of this document is to introcuce users to the eBPM architecture, and concepts and then to examine the configuration detail offered.
Understanding the Pieces
As you can see from the picture eBPM is made by the following parts:
-
eBPM Service Manager
The service manager is the rutime part of eBPM, basically it’s the software that act as server for eBPM Processes/ Services and Connector -
eBPM Studio Tools
The eBPM studio is not available yet, but we are going to contribute it soon.
It’s the set of “Eclipse Based” development tools for developing/creating/configuring services/processes/connectors that will be deployed on service manage. However, you can use the studio tools of the original Project, Spagic3 Studio , that is compatible with eBPM -
Monitoring and Web Tools
eBPM doesn't provide a tool for monitoring, at presente we are evaluating if contribute also for this part, but you can use the Spagic Console that is compatible with eBPM runtime
For more infomation go to Spagic Service Manager Concepts and Guide