Embedded Cloud Workflow Engine

Embedded Cloud Workflow Engine (ECW) is a self contained J2EE complaint application. You can download and install on any J2EE compliant container and get started in no time.

Steps to Get Started with ECW

• Download and configure the Web Application on your J2EE compliant container. The application comes with a pre-configured Tomcat instance.
• Create a database instance which will store user configuration data
• Create a database which will store all the data flow logs. I can be the same as the configuration database or separate. Since we expect the log database to grow rapidly we recommend that the log database be separate to that of configuration database.
• Setup Web application config files to the configuration database and log database
• Setup Web application with the default Processes to run when an application is invoked
• Setup Web application with the default configuration template to use.

Download & Install

The following distributions are available for use:

docker pull dbsync/dbsync-ecw

Database Script 

ECW comes with a default setup where the Partner app needs to provide a storage for the User Configurations. These configurations are "connections" that end users will setup to connect to their end application. For example, if the Partner App relies on a database to run its platform, then the one end is likely to be static, while the connecting application for example an Accounting application like QuickBooks, will vary from customer to customer. 'sys_partner_app_config' is the table where the engine will store and fetch these connector access / login details to perform the integration. Note that DBSync Cloud Platform will not ever store the customer specific connection information.

CREATE TABLE `sys_partner_app_config` (
`id` bigint(20) NOT NULL AUTO_INCREMENT,
`username` varchar(50) NOT NULL,
`profile` longtext,
`created_date` timestamp NULL DEFAULT NULL,
`modified_date` timestamp NULL DEFAULT NULL,
KEY `id` (`id`)
) ;

When integrations run, it will produce data flow logs. Each log will be saved in 'sys_dataflow_log' table. Partner app developer should design and administer these tables and manage storage. ECW will "NOT" be truncating or managing this table. It is recommended to add a cron script to delete logs every so many days.

CREATE TABLE `sys_dataflow_log` (
  `id` bigint(20) NOT NULL AUTO_INCREMENT,
  `username` varchar(50) NOT NULL,
  `name` varchar(50) DEFAULT NULL,
  `records_processed` varchar(20) DEFAULT NULL,
  `message` text,
  `log_messages` longtext COMMENT 'Log messages for processed data for c2c',
  `created_time` datetime DEFAULT NULL,
  PRIMARY KEY (`id`,`username`),
  UNIQUE KEY `id` (`id`)
)