Skip to content

Code Deployment

Workflow / Delegate Deployment

Workflows, delegates, and associated configurations may be deployed manually using the user interface or automatically as part of the IFS Applications installer. This document explains the automated deployment mechanisms currently available; details for manual configuration and deployment of Workflows can be found here.

Automated deployments follow the Layered Component Architecture philosophy by bundling BPMN and Java Classes within the building home.

BPMN files should be located within the relevant component’s source following the file and folder conventions below. BPMN files will be validated each time the system starts during the deployment phase; as such care should be taken to ensure the BPMN file and system configuration are Valid.

Source Locations

•       \source\\workflow\bpmn*.bpmn

Build Home Locations

•       \server\lob\\bpmn\.bpmn

Java Delegates should be located within the relevant component’s source following the file and folder conventions below. Java code will be compiled as part of the build home bundling phase, so any external references must be included as a library. Base classes, including the Camunda runtime and the oData Workflow API, will be included in each compilation; Java Delegates must extend the TransactionalDelegate class to ensure the safety of the system.

Source Locations

•       \source\\workflow\delegates\\*.java

•       \source\\workflow\lib\\*.jar

Build Home Locations

•       \server\lob\\bpa-impl\-bpa.jar

•       \server\lob\\bpa-lib\.jar

Workflow Configurations can be encoded within database insert files. Lacking elegance, this approach will ensure a consistent base configuration for the system on each installation. Database data files should follow typical conventions and reside within the path below.

Source Locations

•       \\source\\database\Event.ins