This documentation is for WSO2 Enterprise Integrator version 6.3.0 . View documentation for the latest release in the 6.x.x family and the latest release in the 7.x.x family.
Enterprise Integrator Documentation

All docs This doc
Expand all   Collapse all
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

The Micro Integrator profile (MI profile) of WSO2 Enterprise Integrator (WSO2 EI) is designed to be container-friendly. Because its start-up time is faster than the ESB profile, the Micro Integrator profile allows you to perform advanced scenarios without sacrificing the speed required for a container-based architecture. Also, you can use the Micro Integrator profile to orchestrate atomic microservices into composite microservices that address more complex, real-world scenarios.

For information on what the Micro Integrator profile brings with this release, see About this Release.

Running the Micro Integrator profile

For instructions, see Starting the Micro Integrator profile.

Deploying artifacts in the Micro Integrator profile

After creating your artifacts in an ESB Solutions Project via WSO2 EI Tooling, import the project as a Composite Application, and add the CAR file to the <EI_HOME>/wso2/microIntegrator/repository/deployment/server/carbonapps directory to deploy.

Restart the Micro Integrator profile after deploying the artifacts.

Configuring the Micro Integrator profile

All configuration files related to the Micro Integrator profile are located in the <EI-HOME>/wso2/micro-integrator/conf directory. For more information, go to Directory Structure of WSO2 Products in the WSO2 Administration Guide.

Configuring the file-based registry

The H2 database-based registry is not available in the Micro Integrator profile. Instead, it has a file-system-based registry, which provides the same functionality. Thus, by default, the <EI_HOME>/wso2/micro-integrator/registry directory will act as the registry to store registry artifacts etc. This main registry directory will consist of the following sub-registry directories.

  • Local: To store local artifacts of the product server that are not shared with the other products in the deployment.
  • Config: To store all product-specific artifacts that are shared between similar product instances.
  • Governance: To store all artifacts that re relevant to the governance of the product.

If you want to change the default locations of the Registry directories, uncomment and change the following configuration in the <EI_HOME>/wso2/microIntegrator/repository/deployment/server/synapse-config/default/directoryregistry.xml file.

<registry xmlns="http://ws.apache.org/ns/synapse" provider="org.wso2.carbon.mediation.registry.MicroIntegratorRegistry">
    <parameter name="cachableDuration">15000</parameter>
    <!--
        Uncomment below parameters (ConfigRegRoot, GovRegRoot, LocalRegRoot) to configure registry root paths
        Default : <EI_HOME>/wso2/micro-integrator/registry/{governance | config | local}
    -->
    <!--
    <parameter name="ConfigRegRoot">{Root directory path for configuration Registry}</parameter>
    <parameter name="GovRegRoot">{Root directory path for governance Registry}</parameter>
    <parameter name="LocalRegRoot">{Root directory path for local Registry}</parameter>
    -->
</registry>
  • No labels