May I use Application Lifecycle Conductor to integrate with another application via web services?
If not. What can I use?
Anybody from your team can help me with this question?
Regards and hugs!
ALC 3.0 IR1 has introduced a REST API, to remotely trigger rules execution. It is described in the Manage Rule Scripts part of the Administration Guide, Rest API for Executing Rules sub-chapter.
Hope it answers your question.
We are proposed to do a POC with SOAP?
Does it works?
Christian's answer nails it - we have a REST API to trigger rule execution via web services in 3.0. Since the back end is essentially a workflow, taking any number of parameters which become variables in the workflow, it can be used as a front end for other product automation (e.g. triggering package creation, execution, promotion, notifications, etc.). More APIs are coming in the next release as well.
The ALC web services API is REST only, however it should be easier to use than SOAP. Is there a reason SOAP is proposed?
The external provider propose to make the integration via SOAP Web Services.
The other idea for integration is using scritps directly from Harvest. They want programs to compile, check in executables and get objects to deploy. They have their own deploying tool.
OK - thanks for the info. Scripts would be possible but will require a Harvest client (command line) on the machine the scripts work from. The operations you propose are probably best suited to the CLI API from what I see though as you'd be transferring fairly large amounts of data over HTTP for check in / check out.