The Micro Integrator profile (MI profile) of WSO2 Enterprise Integrator (WSO2 EI) is architectured to be container-friendly so that it allows you to perform advanced scenarios without sacrificing the speed required for a container-based architecture. Because its start-up time is faster than the ESB profile, microservices are designed to start up very quickly, perform a specific task, and then shut down. Also, you can use the Micro Integrator profile to orchestrate atomic microservices into composite microservices that address more complex, real-world scenarios.
...
Open a terminal and navigate to the
<EI_HOME>/bin/
directory.Execute the following command to extract the Micro Integrator profile.
Panel borderColor #542989 bgColor #ffffff borderWidth 1 Localtabgroup Localtab title On MacOS/Linux/CentOS Open a terminal and execute the following command:
Code Block sh profile-creator.sh
Localtab title On Windows Open a terminal and execute the following command:
Code Block profile-creator.bat
The profiles available in the WSO2 EI distribution are listed as shown below.
Code Block WSO2 Enterprise Integrator Supports following profiles. 1.Integrator profile 2.Analytics Profile 3.Business Process profile 4.Broker profile 5.Msf4j profile 6.Micro Integrator profile Please enter the desired profile number to create the profile specific distribution.
Insert the value '6' (for the Micro Integrator profile) on the terminal and execute the command. As a result of this command, the original WSO2 EI distribution is modified, and a ZIP file with a new Micro Integrator distribution is generated. Note that the new Micro Integrator ZIP file is stored in the same directory as your original WSO2 EI distribution.
Tip Important!
Note that you now have two product distributions:
The new Micro Integrator distribution (ZIP file) that you just generated in step 4.
The original WSO2 EI distribution that you downloaded and extracted.
...
Once you have started the Micro Integrator profile, you can view details of the REST APIs and proxy services that are deployed in the server by RESTfully invoking the URLs shown below. For example, you can copy the following URLs to your browser to view the details.
- For REST APIs: http://localhost:8290/wso2-micro-integrator/apis
- For proxy services: http://localhost:8290/wso2-micro-integrator/proxy-services
...
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.
...