EasyVIPER is a generic workflow engine. VIPER stands for VIrtual Process Engine with Reconfiguration.
Indeed its architecture is based on [Frascati|http://frascati.ow2.org/], a component-based framework following the [SCA|http://en.wikipedia.org/wiki/Service_component_architecture] standard allowing to reconfigure the engine and workflows at runtime.

It is mainly used in relationship with EasyBPEL but is able to accept any upper model managing processes execution.

The following SCA schema represents the main components and services provided by EasyVIPER.

{center}
!EasyVIPER_SCA_MODEL.png|align=center,width=800!
EasyVIPER main components SCA model.
{center}




The EasyVIPER main component is the [Workflow engine core|easyviper:Architecture#core] that receives and sends messages coming from and going to an external environment. The [external environment component|easyviper:Architecture#environment] is an abstract component dedicated to external / internal messages conversion. The [abstract model component|easyviper:Architecture#model] is an abstract component dedicated to workflow model management (when there is one), that is to say, a model registry and a model compilation module.

Moreover, these libraries are used in the Frascati BPEL engine implementation.
!logo_adam_team.jpg|border=1!
{info}

If you want know how to use {report-info:page:space > space:name} library, please consult the list of [How-tos|How-tos].
If you have any questions, please use the \[{report-info:page:space > space:name} contact form\|Contact\].