About Generate Project

In IZ Accelerator, you can create a mule application by using two or more patterns in flows and processors.


Pattern represents combination of solution design method and best coding standards to provide a re-usable building block for integrations - whether dynamic or static in nature.

Types of patterns supported by IZ Accelerator are:

  • Source Patterns - Represents ways of triggering a message flow within a mule application like a scheduler or API receiver

  • Processor Patterns - Represents ways of handling the data flowing through the processor like calling an external system like Salesforce or doing data transformation

  • Application Patterns - Represents ways of adding additional application level quality, best practices and reliability requirements across the different processors of the application

Depending on the choice of arrangement of the patterns, same patterns can be re-used to solve a multitude of common enterprise integration problems.


A flow represents a message propagating through the middleware with at least one source pattern, one or more processor patterns and optional application patterns. Each pattern receives an input, carries out a specific function (or a list of functions), and then transfers the output to the next part of the flow. The placement of patterns in a flow affects functionality.

Flows typically solve one end to end enterprise problem in an isolated manner.

For example, you could have an API implementation flow which exposes an API to the outside world and upon receiving requests executes the requested functions and returns the response to the caller.

Another example could be a poller flow which schedules a job to run at a give time and aids in data migration process.


Within a flow depending on the type of source pattern selected, you might have additional interfaces to help achieve the desired functionality.

For example in a API based implementation which could have multiple interface paths (resources), you might want to group the related resources to be implemented using one set of patterns and another set of patterns for the rest of the resources.

Interfaces provide option of whether you would like the accelerator to group and re-use interfaces across the different target routes (resources) or to create a duplicate set of implementations for each distinct path.

For steps to help you get started building applications using IZ Accelerators, see "Generate Project", which is linked to from the See also section at the end of this topic.