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

Versions Compared

Old Version 21

changes.mady.by.user Praneesha Chandrasiri

Saved on

compared with

New Version Current

changes.mady.by.user Praneesha Chandrasiri

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Microservices are designed to start up very quickly, perform a specific task, and then shut down. The Micro Integrator profile (MI profile) of WSO2 Enterprise Integrator (WSO2 EI) is designed in a highly container-friendly manner to be used , and thereby, it is ideal for you to use it for Microservices Architecture (MSA)-based solutions that , which are deployed in container-based environments. Microservices are designed to start up very quickly, perform a specific task, and then shut down. Because its start-up time is faster than the ESB profile, the Micro Integrator profile allows you to perform advanced integration scenarios without sacrificing the speed required for a container-based deployment architecture. 

...

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.

Info

These sub-

...

registry directories will be created automatically when you deploy registry artifacts. If you did not deploy any registry artifacts, you can create them manually.

  • 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 are relevant to the governance of the product.

...

Code Block
languagexml
<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>

Trying out a sample scenario

For instrcutions on trying out a simple use case using the micro Integrator proifle, see Sending a Simple Message to a Service Using the Micro Integrator.