Skip to content

Deploying WSO2 Micro Integrator

The following sections provide information and instructions on how to deploy the Micro Integrator with a third-party load balancer.

The deployment pattern

This deployment scenario uses a two-node Micro Integrator deployment. That is, two Micro Integrator nodes are configured to serve requests with high availability and scalability. As depicted by the following diagram, the product nodes in the deployment are fronted by an external third-party load balancer, which routes requests to the two nodes on a round-robin basis.

Micro Integrator Deployment Pattern

Installing WSO2 Micro Integrator

Follow the instructions on downloading and installing WSO2 Micro Integrator on a single machine.

Setting up the load balancer

Follow the instructions on setting up a load balancer for a two-node deployment of the Micro Integrator.

Setting up the file-based registry

Follow the instructions on configuring the file-based registry for a two-node deployment of the Micro Integrator.

Updating keystores

  1. Create a new SSL certificate and import it to the primary keyStore and trustStore (which are located in the MI_HOME/repository/resources/security/ directory). Your primary keystore can now be configured for SSL communication.
  2. Create a new keystore to use as the internal keystore (for the purpose of data encryption/decryption in internal data stores).

Configuring the Micro Integrator nodes

Follow the steps given below to configure the two nodes in the Micro Integrator deployment.

  1. Open the deployment.toml file of both the nodes. This file is located in the MI_HOME/conf/ directory.
  2. To specify the default settings that should be applicable to the nodes, update the following toml parameters with the required values.

    # The config section that groups the parameters that identify the server.
    [server]
    
    # The hostname of the server.
    hostname = "localhost"
    
    # If you are running both product nodes (of your cluster) on the same VM, set a port offset for on the servers.
    offset = 0
    Find more parameters for deployment settings.

  3. If you have separated the internal keystore of your product, update the [keystore.internal] section in the deployment.toml file.

    See Configuring Keystores for instructions.

(Optional) Configuring Analytics

If you have already done the configurations explained above, you have the option of applying the following configurations for your deployment.

If you wish to view reports, statistics, and graphs related to the message mediation that happens through the Micro Integrator, you need to configure Analytics for the Micro Integrator. Follow configuring WSO2 EI Analytics in a production setup.

Verifying your deployment

Ensure that you have taken into account the respective security hardening factors (e.g., changing and encrypting the default passwords, configuring JVM security etc.) before deploying the Micro Integrator. For more information, see the Production Deployment Checklist.

Starting the Micro Integrator servers

Start the server using the following standard start-up script.

  • On Linux/MacOS/CentOS : cd MI_HOME/bin/ sh micro-integrator.sh
  • ON Windows : cd MI_HOME\bin\ micro-integrator.bat
Top