Mule migration

Import mule workflows into quickintegrate by uploading mule XML configuration file.

note

• Atleast one project should be created
• Mule workflow name should not be present in the project, otherwise it will fail to create the workflow
• Connection properties configuration will not be created automatically
• Nodes which are not mapped completely, node data will be available in flow json tab in functional key

Steps

1. Select the project from drop down to which mule workflow to be imported
2. Click on mule button on the top right to upload the mule configuration file
3. Select the mule configuration file and click upload

If the uploaded file is successfully processed then a new service will be created within the project selected

Mapped components

Mule node	Quickintegrate node	Fields mapped
flow	flow	name type (only for rest trigger)
http:listner-config	REST_CONFIG	ds_name ds_host ds_port
http:request-config	REST_CONFIG	ds_name ds_host ds_port
http:request	REST	alias basepath method
db:config	DB_CONFIG	ds_name ds_host ds_port ds_username ds_password ds_database
db:select	DB	name query queryparams datasource-name
db:insert	DB	name query queryparams datasource-name
db:update	DB	name query queryparams datasource-name
db:delete	DB	name query queryparams datasource-name
db:query-single	DB	name query queryparams datasource-name
db:bulk-update	DB	name query queryparams datasource-name
db:bulk-delete	DB	name query queryparams datasource-name
set-variable	UTILITY	name pipeline varName
remove-variable	UTILITY	-
logger	UTILITY	name logType
error-handler	CUSTOMSERVICE	name
try	CUSTOMSERVICE	name
scatter-gather	PARALLEL	name timeframe
error-handler	CUSTOMSERVICE	name
choice	DECISIONBOX	name
foreach	DECISIONBOX	-
choice	SCHEDULER	name intialDelay startDelay
s3:create-bucket	CUSTOM	-
s3:put-object	FILE	name filename datasource-name
s3:get-object	FILE	name filename datasource-name
s3:delete-object	CUSTOM	-
s3:delete-bucket	CUSTOM	-