ActiveVOS
ActiveVOS is a new kind of Business Process Management System (BPMS). ActiveVOS is different from other BPMSs because it is focused on the needs and requirements of development teams.
BPMS development teams love
Because enterprise middleware hasn't been known for ease of use, end users have been encouraged by some BPMS vendors to "go around" development teams to meet their BPM requirements. ){kind=spacer}
Click on image to enlarge
This leads to unavoidable cost, complexity and integration issues when the end-user-generated process is deployed and must inevitably be supported by traditional development teams.
As the graphic above illustrates, ActiveVOS solves this problem by focusing on the needs of professional development teams -- teams that wish to collaborate with business end users -- to deliver integrated, end-to-end applications.
With its integration, ease-of-use, standards-compliance and affordability, ActiveVOS rapidly makes development teams successful.
Say goodbye to consultants
If you think that on the day your organization acquires a new BPMS, it will have to write two checks: one for the software and another for consultants to implement the BPMS, ActiveVOS will change your mind.
Because ActiveVOS BPMS is "shrink-wrap" middleware -- a product instead of a set of technologies you must integrate -- everyone on the development team has everything they need to collaborate with end users to deliver compelling BPM applications.
With a wealth of learning information available both online and in ActiveVOS itself, ActiveVOS enables development teams to achieve two important objectives while saving money. First, it allows development teams to be self-reliant in creating their proofs-of-concept and, second, ActiveVOS allows development teams to reliably deliver BPM applications on time.
True investment protection
Everyone believes standards are necessary when developing a BPM application. But simply "conforming" to a standard in a BPMS may not really deliver the investment protection standards are designed to offer.
For example, if a process is modeled in the Business Process Modeling Notation (BPMN), but is executed on a proprietary execution engine and/or requires custom Java code to execute, the organization loses visibility into the process. Worse, a fundamental advantage of BPMS -- model based-execution -- is lost.
In ActiveVOS, standards like the Business Process Execution Language (BPEL), BPMN modeling, SOAP and REST interfaces, WS-* conformance and more all serve to ensure that portability and visibility are never lost.
Because ActiveVOS is both lightweight -- or lean -- and platform independent, development teams are more effective in creating BPM applications. At deployment time, BPM applications written in ActiveVOS are compatible with the broadest range of existing infrastructure to ensure rapid deployment.
The following sections on this page and the links in the linkbox to the left expand on ActiveVOS BPMS and its unique capabilities.
ActiveVOS Designer is a rich productivity tool that incorporates the BPMN, BPEL and BPEL4People open standards and a set of advanced wizards that make easy it to create business process models and orchestrations quickly. Some of ActiveVOS Designer's important capabilities include:
- Create BPMN models: import common model formats and transform them to BPMN. Export BPMN model to BPEL
- Visually orchestrate human activities and services using intuitive drag and drop diagramming of BPEL processes and BPEL Extensions for People (BPEL4People)
- Export BPEL processes to BPMN for documentation purposes
- Any-order development permits developers to develop a BPM application by starting at the beginning, middle or end of the business process
- A developer's tool, called the Participants View, creates orchestrations naturally, eliminating the need for developers to manually code complex programming constructs like BPEL partner links and BPEL partner link types that are needed to define how services are to be used in a BPM application
- Orchestrate services defined using WSDL interfaces. Or, start with XML schema or XML fragments if this is all that is available to you
- Incorporate non-Web services through flexible bindings to JMS and REST and invoke EJB and Java classes (POJO's), creating a SOA environment with web services that do not necessarily expose a Web Services Definition Language (WSDL) interface
- Simulate service and human BPEL and BPEL4People orchestrations locally or using remote debugging
- Save simulation and test data, and generate unit tests and test suites to perform scenario testing
- Use wizard-based, push-button deployment to deploy new orchestrations and updates to the server
ActiveVOS Server
ActiveVOS Server easily scales to meet the needs of enterprises of any size and can be rapidly incorporated into a production J2EE execution environment to meet rigorous scalability, performance and availability requirements. With ActiveVOS Server, teams can leverage existing skills and collaborate to develop, deploy and run production business process management applications. With ActiveVOS Server you can:
- View dashboards and reports
- Create custom dashboards and reports and add them to the ActiveVOS console
- Perform problem determination using graphical views of the process
- Use exception management such as the "time machine" feature to inspect and investigate running, faulted or completed processes
- Rewind a process to a specific activity and redo the work without having to invoke any of the built-in compensation logic, giving organizations unprecedented flexibility in managing running, in-flight processes
- Configure and enforce runtime behavior of an orchestration using standard policies
- Perform server-based runtime message correlation and handle service communication retries to free the developer from runtime concerns
- Perform endpoint management to make it easy to deploy an orchestration from one environment to another, or deal with a change in topology
- Suspend a running process using process exception management capabilities to handle bad data which would otherwise have unnecessarily failed a transaction, and correct the problem via remote debugging
- Use a universal console to monitor server activity and set performance thresholds for notification
- Deploy a new version of a process and control when it is activated and if running processes need to be automatically migrated to the new version
- Use ActiveVOS Multi Site clustering to deploy and execute orchestrations across geographically distributed data centers, ensuring enterprise-class salability, high availability and fail-over
- Crucial, long-running work – including human tasks – that might represent weeks or even months of work can be started at one site and, in the event of a failure at that site, continued or completed at a another site
- Deploy to Oracle® Web Logic Server®, IBM® Web Sphere® Application Server and Boss® Application Server J2EE platforms
