Integration with Drools rule engine

View: New views
3 Messages — Rating Filter:   Alert me  

Integration with Drools rule engine

by Ajai :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi,

We are in the process of evaluating a Workflow engine that can be integrated with Drools rule engine. Can Enhydra shark be integrated with Drools rule engine.

Also please tell us the following features are available:

1. versioning of process definition
2. Can web service act as a input
3. Can  Web service be actor in process
4. Process steps can be assigned to Roles, and User in Roles
5. Authorization mechanism.
6. Creating a sub flow from a main flow.

Please let us know the inputs.

Thanks in advance

Regards
Ajai G

Re: Integration with Drools rule engine

by Sasa Bojanic :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi,

I think the integration with Drools shouldn't be a problem. The question
is for which purpose you want to integrate it?
If it is for evaluating of transition condition expressions, you can
just write your own Scripting interface implementation...

About other questions:

1. the definitions are versioned. E.g., when you update XPDL existing in
the system (which can contain of many process definitions), the new
definition (its representation in the runtime) gets new version. Process
instances running on old definitions continue running with the old one,
and newly created processes run on new definitions.

2. Yes, you can communicate with Shark through Shark's WebServices API

3. Yes, inside the process, there can be tool agent (automatic) activity
which can interact with WebServices, get some information, put it back
into the process and continue with the process

4. Yes

5. Shark is typically embedded into your application (when you use it
through its POJO API), and in that case authorization is something you
do within your application. However, shark has Security interface (we
normally configure shark not to use it, and we have only dummy
implementation of this interface), and if you provide the custom
implementation of this interface, you can do authorization.

6. This is of course supported (we completely support XPDL1.0). You can
call sub-flow from the main flow either synchronously (where main flow
initiates sub flow by passing certain information, waits for sub flow to
finish, gets back the results of the sub flow and then continues) or
asynchronously (where main flow initiates sub flow and passes
information to sub flow, and continues immediately without waiting sub flow)

Regards,
Sasa.

Ajai wrote:

> Hi,
>
> We are in the process of evaluating a Workflow engine that can be integrated
> with Drools rule engine. Can Enhydra shark be integrated with Drools rule
> engine.
>
> Also please tell us the following features are available:
>
> 1. versioning of process definition
> 2. Can web service act as a input
> 3. Can  Web service be actor in process
> 4. Process steps can be assigned to Roles, and User in Roles
> 5. Authorization mechanism.
> 6. Creating a sub flow from a main flow.
>
> Please let us know the inputs.
>
> Thanks in advance
>
> Regards
> Ajai G
>  


--
You receive this message as a subscriber of the shark@... mailing list.
To unsubscribe: mailto:shark-unsubscribe@...
For general help: mailto:sympa@...?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

Re: Integration with Drools rule engine

by Ajai :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi Sasa,

Thanks a lot for the response.

I need some more details regarding Shark to complete our evaluation.

1. Can a process definition be exposed as a service
2. Is there a Process compensation (Process roll back/Exception handling)
3. Can a process instance be stopped and resumed again.
4. Can a process be made wait asynchronously.

Thanks again for the response,

Regards
Ajai G




Sasa Bojanic wrote:
Hi,

I think the integration with Drools shouldn't be a problem. The question
is for which purpose you want to integrate it?
If it is for evaluating of transition condition expressions, you can
just write your own Scripting interface implementation...

About other questions:

1. the definitions are versioned. E.g., when you update XPDL existing in
the system (which can contain of many process definitions), the new
definition (its representation in the runtime) gets new version. Process
instances running on old definitions continue running with the old one,
and newly created processes run on new definitions.

2. Yes, you can communicate with Shark through Shark's WebServices API

3. Yes, inside the process, there can be tool agent (automatic) activity
which can interact with WebServices, get some information, put it back
into the process and continue with the process

4. Yes

5. Shark is typically embedded into your application (when you use it
through its POJO API), and in that case authorization is something you
do within your application. However, shark has Security interface (we
normally configure shark not to use it, and we have only dummy
implementation of this interface), and if you provide the custom
implementation of this interface, you can do authorization.

6. This is of course supported (we completely support XPDL1.0). You can
call sub-flow from the main flow either synchronously (where main flow
initiates sub flow by passing certain information, waits for sub flow to
finish, gets back the results of the sub flow and then continues) or
asynchronously (where main flow initiates sub flow and passes
information to sub flow, and continues immediately without waiting sub flow)

Regards,
Sasa.

Ajai wrote:
> Hi,
>
> We are in the process of evaluating a Workflow engine that can be integrated
> with Drools rule engine. Can Enhydra shark be integrated with Drools rule
> engine.
>
> Also please tell us the following features are available:
>
> 1. versioning of process definition
> 2. Can web service act as a input
> 3. Can  Web service be actor in process
> 4. Process steps can be assigned to Roles, and User in Roles
> 5. Authorization mechanism.
> 6. Creating a sub flow from a main flow.
>
> Please let us know the inputs.
>
> Thanks in advance
>
> Regards
> Ajai G
>  



--
You receive this message as a subscriber of the shark@ow2.org mailing list.
To unsubscribe: mailto:shark-unsubscribe@ow2.org
For general help: mailto:sympa@ow2.org?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws