Generic Web Integration Layer - Missing?

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

talbeno

We need to integrate the Activiti engine with our products. We went over the REST APIs and the custom java classes.

We think that what could be a "clean" integration architecture is a way to inject into the process XML file / process definition generator, a reference to the following:
1. From a process step definition, a WS*/REST call to an outside program/URL. Without the need to bind with code (e.g. Java class).
2. Define a process event that can be triggered from an outside program over WS*/REST. Since you already have a REST API all that is needed is a mechanism to register to the external REST call, and then activating the step in the process that this event was attached to in RT.

Going over your documentation I assume that this integration layer is missing in the current product.
Is this true - or any alternatives that are still in this "clean" direction (rather than bind a Java code)? Is this on the roadmap? Any advice for us how to implement it on our own?

Thanks,
Tal

trademak

Hi,

You can already do this using the Camel or Mule integration modules.
But the difficult thing is always, how do you create the request messages and how do you process the response messages.
So creating a Java delegate class to create a request message and do the REST or WS call would still be a clean approach to my opinion.

Best regards,