Migrating from WSO2 EI 6.3.x to WSO2 API-M 4.0.0

This guide provides the recommended strategy for upgrading from the ESB profile of WSO2 EI 6.3.0 to the Micro Integrator of WSO2 API-M 4.0.0.

Why upgrade to WSO2 API-M 4.0.0?

Listed below are some of the advantages of moving to API-M 4.0.0 from the ESB.

  • The Micro Integrator of API-M 4.0.0 is now the most improved version of the battle-tested WSO2 ESB runtime.


    WSO2 ESB 5.0, the ESB profile of WSO2 EI 6.x, the Micro Integrator of WSO2 EI 7.x, as well as the Micro Integrator of WSO2 API-M 4.0.0 contains versions of the same WSO2 ESB runtime.

  • All the ESB runtimes of WSO2 can use the same developer tool (WSO2 Integration Studio) for developing integrations.

  • All the integration capabilities that you used in the ESB can be used in the Micro Integrator with minimal changes.

  • The Micro Integrator contains improvements to ease your product experience.


    The Toml-based configuration strategy in API-M 4.0.0 replaces the XML configurations in previous versions of the ESB runtime. Some of the features are removed from WSO2 Micro Integrator as they are not frequently used.

Upgrading to WSO2 API-M 4.0.0 is recommended for the following requirements:

  • You need to expose integrations as managed APIs so that integration solutions can be managed and monetized in an API marketplace.
  • You need to switch to a microservices architecture from the conventional centralized architecture.
  • You need a more lightweight, user-friendly version of the battle-tested WSO2 ESB.
  • You need a more lightweight, container-friendly runtime in a centralized architecture.
  • You need native support for Kubernetes.

Before you begin

Note the following:

  • Ports are different in the Micro Integrator of API-M 4.0.0. Find out about ports in the Micro Integrator.
  • The Micro Integrator of API-M 4.0.0 contains changes that impact your migration process. Be sure to read the Comparison: ESB vs the Micro Integrator before you start the migration.

  • Note that API-M 4.0.0 does not allow manual patches. You can use WSO2 Updates to get the latest fixes or updates for this release.

Migrating to the Micro Integrator

Follow the instructions below to start the migration!

Setting up

  • Make a backup of the EI 6.3.0 distribution (<EI_HOME> folder) to back up the product configurations.
  • Make a backup of the database used by the current EI 6.3.0 deployment. This backup is necessary in case the migration causes any issues in the existing database.
  • Download and install the latest Micro Integrator in your environment:


    The home directory of your Micro Integrator will be referred to as <MI_HOME> from hereon.

  • Use WSO2 Updates to get the latest available updates for your Micro Integrator distribution.


    Note that you need a valid WSO2 subscription to use updates in a production environment.

Migrating the user store

Before you begin

Read about users and roles in the Micro Integrator and about how they function. Note the following important facts:

  • Users in the Micro Intgrator are categorized as admin users and non-admin users.
  • All admin users in your existing EI 6.3.0 user store will function as admin users in the Micro integrator.
  • Tenant admins are no longer valid because the Micro Integrator does not support multitenancy.
  • Secondary user stores are currently not supported in the Micro Integrator.

If you are using an LDAP user store with EI 6.2.0, you can simply connect the same to the Micro Integrator of API-M 4.0.0 by updating the configuration details in the Micro Integrator's deployment.toml file.

If you are using a JDBC user store with EI 6.2.0, you need to first update the database before connecting the same to APIM 4.0.0.

Follow the steps given below.

Step 1 - Update the database structure

This step is applicable only if your user store is JDBC.

There are changes in the database structure (schema) that is used in EI 6.3.0. To update the database schema:

  1. Download the database migration scripts.

  2. Unzip the downloaded file and select the script relevant to your database type.

  3. Connect to the database and run the script.

Your database schema is now updated for APIM 4.0.0. Now you can update the configuration details in the Micro Integrator's deployment.toml file.

Step 2 - Connect to the user store

To connect the Micro Integrator to the primary user store:

  1. Open the deployment.toml file of your Micro Integrator.
  2. Note that you have the [user_store] section enabled by default.

    type = "read_only_ldap"
  3. See the instructions in the following sections:

  4. If your user store is an RDBMS, be sure to add the client JAR of your RDBMS to the <MI_HOME>/lib folder.

See the instructions on configuring a user store for more information.

Migrating the registry

Before you begin

Note the following:

  • The Micro Integrator uses a file-based registry instead of a database (which is used in your WSO2 EI version).
  • Your WSO2 EI registry may have the following partitions: Local, Config, and Gov. However, you only need to migrate the Config and Gov registry partitions. See the instructions on configuring registry partitions in the Micro Integrator.
  • Message processor tasks stored in the registry should be stored with a new naming convention in the Micro Integrator. Therefore, all entries in the registry with the MSMP prefix (which correspond to message processor tasks) should not be migrated to the Micro Integrator. New entries will be automatically created when you start the Micro Integrator server.
  • If you have shared the registry of your WSO2 EI among multiple nodes, you can do the same for the file-based registry of the Micro Integrator. However, note that registry mounting/sharing is only required for persisting message processor states among nodes of the Micro Integrator.

You can migrate the registry resources by using the registry migration tool as follows:

  1. Download the tool and save it to a location on your computer.

  2. Execute one of the commands given below to start the tool.

    • To start the tool without a log file:

      java -jar <path_to_jar>/registry-migration-service-1.0.0.jar
    • To start the tool with a log file:


      Replace <log_file_location> with the location where you want the log file to be created.

      java -Dlog.file.location=<log_file_location> -jar <path_to_jar>/registry-migration-service-1.0.0.jar
  3. Specify the following input values to log in to your WSO2 EI server from the migration tool:

    Input Value Description
    EI Server URL Specify the EI server URL with the servlet port. The default is https://localhost:9443.
    Internal Truststore Location of the EI Server Specify the location of the internal truststore used by the EI server.
    Internal Truststore Type of EI Server Specify the type of the internal Truststore used by the EI server. The default is JKS.
    Internal Truststore Password of EI Server Specify the password of the internal Truststore used by the EI server. The default is wso2carbon.
    Username of the EI Server admin.
    Password of the EI Server admin.

  4. Select one of the following options and proceed.

    Option Description
    Export as a Registry Resource Module Recommended. If you select this option, the registry resources are exported as a Registry Resources module, which you import to WSO2 Integration Studio. You can then create a CAR file by selecting resources from the registry resources module.
    Export as a Carbon Application If you select this option, the registry resources in your WSO2 EI instance are exported as a single CAR file, which you directly copy to your Micro Integrator distribution.

  5. Specify input values depending on which export option you selected.

    • If you selected Export as a Registry Resource Module, follow the steps given below.

      1. Enter the following input values:

        Input Value Description
        Integration Project Name Specify the name of the Integration project.
        Project’s Group ID Specify the group ID of the integration project. The default value is com.example.
        Project’s Artifact ID Specify the artifact ID of the integration project. The default value is the integration project name.
        Project Version Specify the version of the integration project. The default value is 1.0.0.
        Export Location Specify the location where the integration project should be created.

      2. Verify the following:

        • If the process is successful, the Registry Resource Project is created in the location you specified.
        • A summary report is created at the export location with file name: registry_export_summary_<date>.txt. This report explains whether the registry resource is successfully exported and also provides reasons in case the exprot fails.
      3. Import the Registry Resource Project to the Registry Resources module in WSO2 Integration Studio.

      4. Open the resource editor and make sure that the media type of the resource is set properly.

        Registry Resource Editor

      5. Select the required resources from your registry resources project and export a CAR file.

    • If you selected Export as a Carbon Application, enter the following input values:

      Input Value Description
      CAR File Name Specify the name of the Carbon application.
      CAR File Version Specify the version of the Carbon application. The default value is 1.0.0.
      Export Location Specify the location where the CAR file should be created.

    You should now have a CAR file with the required registry resources.

  6. Copy the CAR file to the <MI_HOME>/repository/deployment/server/carbonapps folder

Migrating integration artifacts

Before you begin

Note that the following changes are effective from EI 6.4.0 onwards. Therefore, if you are migrating from an EI version older than EI 6.4.0, you need to apply these changes to the artifacts before the migration.

  • If you have used the $ctx function inline (in the Payload Factory mediator) to get property values, you need to change this to the full XPath. The $ctx function or the get-property() function can be used inside the argument (args) tags to get property values.
  • The XSLT mediator writes response messages to the JSON stream. In ESB versions prior to EI 6.4.0, the XSLT mediator was not doing any changes to the JSON stream after message transformation.
  • There are validations affecting the Enrich mediator, which prevents the source and target in the message body.
  • If you have specified an XPath value in your mediation sequence, the response message generated by the ESB will include the element tags of your XPath value. For example, if your XPath value is "//faultdescription", the response message will be <faultdescription>DESCRIPTION</faultdescription>. If you want the response message to contain only the DESCRIPTION, you need to specify the XPath value as "//faultdescription/text()".
  • If you are using the MailTo transport to send emails through a mediation sequence, note that the email sender specified in the mediation sequence overrides the email sender configured in the Micro Integrator configurations.

The recommended way to create integration artifacts is to use WSO2 Integration Studio:

  • If the artifacts are created in the recommended way, copy the CAR files inside <EI_HOME>/repository/deployment/server/carbonapps to the <MI_HOME>/repository/deployment/server/carbonapps folder.

    Changed package names

    Note that some of the class names of packages used inside your integration artifacts have changed in the Micro Integrator.

    For example, if you have used a Token Store when applying security policy to a proxy service in the ESB, the token store class has changed from org.wso2.carbon.security.util.SecurityTokenStore to org.wso2.micro.integrator.security.extensions.SecurityTokenStore in the Micro Integrator.

    Therefore, these artifacts have to be updated with the correct class name and packaged into a new CAR file before migration.

  • If you have a custom mediator packed in a CAR, do one of the following:

    • Include all the artifacts (using that mediator) in the same CAR.
    • Alternatively, you can add the JAR of the mediator to the <MI_HOME>/lib/dropins folder so that it can be shared by artifacts in multiple CARs.
  • If the artifacts are created using the management console of EI 6.3.0, you need to recreate them using WSO2 Integration Studio and package them as a composite application. See the instructions on packaging artifacts.


For testing purposes, you can copy the artifacts to the same folder structure inside the <MI_HOME>/repository/deployment/server/synapse-configs/default directory.

Migrating deployed Connectors

  • If the connector is added to EI 6.3.0 via a composite application with the Connector Exporter Project, the same can be used in the Micro Integrator seamlessly. Simply copy the CAR file in EI 6.3.0 to the <MI_HOME>/repository/deployment/server/carbonapps folder.
  • If the connector is added to EI 6.3.0 via the management console, pack them using the Connector Exporter Project and deploy via a composite application in the Micro Integrator.

Migrating custom components

Copy custom OSGI components in the <EI_HOME>/dropins folder to the <MI_HOME>/dropins folder. If you have custom JARs in the <EI_HOME>/lib directory, copy those components to the <MI_HOME>/lib folder.


  • To provide seamless integration with RabbitMQ, the Rabbitmq client lib is included in the Micro Integrator by default. Hence, you don't need to manually add any RabbitMQ components.
  • The Micro Integrator no longer contains the VFS/SMB provider by default. If you need to use the VFS SMB feature, download jcifs-1.3.17.jar and add it to the <MI_HOME/lib folder. Since this library is licensed under LGPL version 2.1, you have to comply with the terms of LGPL version 2.1 and its restrictions.
  • If you used an HL7 Message Store (custom message store) implementation, note that the Micro Integrator does not support this functionality. See the list of removed features for details.

Migrating tenants

Multitenancy within one JVM is not supported in the Micro Integrator. Therefore, if you used multiple tenants in your EI 6.3.0 deployment, you can replicate the setup by using separate Micro Integrator nodes.

Migrating keystores

Copy the JKS files from the <EI_HOME>/repository/resources/security folder to the <MI_HOME>/repository/resources/security folder.

Migrating configurations

Before you begin

Note the following:

  • Configuration management was handled in EI 6.3.0 via multiple files such as carbon.xml, synapse.properties, and axis2.xml.
  • The Micro Integrator uses a new configuration model where most of the product configurations are managed by a single configuration file named deployment.toml (stored in the <MI_HOME>/conf directory).
  • Log configurations are managed with log4j2, which are configured in the log4j2.properties file. Prior to EI 6.6.0, all ESB versions use log4j instead of log4j2.

The following sections of this document will guide you to migrate the product configurations including log4j.


Note that WSO2 API Manager 3.0.0, 3.1.0, 3.2.0, and 4.0.0 are affected by the Log4j2 zero-day vulnerability, which has been reported to WSO2 on 10th December 2021. You can mitigate this vulnerability in your product by following our instructions and guidelines.

Migrating to TOML configurations


If you have a WSO2 subscription, it is highly recommended to contact WSO2 Support before attempting to proceed with the configuration migration.

Given below are the main configurations that have changed in the Micro integrator. Expand the sections to find the TOML configurations corresponding to the XML configurations.

Clustering configurations

In the Micro Integrator, you don't need to enable clustering as you did with previous EI versions. Instead, you need to configure all nodes in the cluster to coordinate through an RDBMS. Find out more about cluster coordination.

<clustering class="org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent"
<parameter name="clusteringPattern">nonWorkerManager</parameter>
# Cluster coordination database connection.
url= "jdbc:mysql://localhost:3306/clusterdb"

# Identifying nodes in the cluster.
node_id = "node-1"

Find more parameters.

Analytics configurations

If you used EI Analytics with your ESB profile, you have configured the following to be able to publish statistics to the Analytics server.

  • <EI_HOME>/repository/deployment/server/eventpublishers/MessageFlowConfigurationPublisher.xml
  • <EI_HOME>/repository/deployment/server/eventpublishers/MessageFlowStatisticsPublisher.xml

If you are using EI Analytics with your new Micro Integrator solution, you can follow the instructions in Setting up the EI Analytics Profile for Observability.

Given below are some of the most critical XML configuration files in the ESB profile of EI 6.3.0. Expand each section to find the TOML configurations corresponding to the XML configurations in the file.

  • Hostname

    hostname = "www.wso2.org"

    Find more parameters.

  • Port offset

    offset  = 0

    Find more parameters.

  • Primary keystore

    file_name = "wso2carbon.jks"
    type = "JKS"
    password = "wso2carbon"
    alias = "wso2carbon"
    key_password = "wso2carbon"

    Find more parameters.

  • Internal keystore

    file_name = "wso2carbon.jks"
    type = "JKS"
    password = "wso2carbon"
    alias = "wso2carbon"
    key_password = "wso2carbon"

    Find more parameters.

  • Truststore

    file_name = "client-truststore.jks"  
    type = "JKS"                        
    password = "wso2carbon"            
    alias = "symmetric.key.value"      
    algorithm = "AES"

    Find more parameters.

  • Admin user

    username = "admin"              # inferred
    password = "admin"              # inferred
    admin_role = "admin"            # inferred
  • User datasource

             <Property name="isCascadeDeleteEnabled">true</Property>
             <Property name="dataSource">jdbc/WSO2CarbonDB</Property>
    data_source = "WSO2CarbonDB"       
    properties.isCascadeDeleteEnabled = true   
  • LDAP userstore

    <UserStoreManager class="org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager">
        <Property name="TenantManager">org.wso2.carbon.user.core.tenant.CommonHybridLDAPTenantManager</Property>
        <Property name="ConnectionURL">ldap://localhost:10389</Property>
        <Property name="ConnectionName">uid=admin,ou=system</Property>
    enable = false
    type = "read_only_ldap" # inferred default read_only_ldap # OR  read_write_ldap
    class = "org.wso2.micro.integrator.security.user.core.ldap.ReadOnlyLDAPUserStoreManager" # inferred
    connection_url = "ldap://localhost:10389"   #inferred
    connection_name = "uid=admin,ou=system"   #inferred

    Find more parameters.

  • JDBC userstore

     <UserStoreManager class="org.wso2.carbon.user.core.jdbc.JDBCUserStoreManager">
        <Property name="TenantManager">org.wso2.carbon.user.core.tenant.JDBCTenantManager</Property>
    enable = false
    class = "org.wso2.micro.integrator.security.user.core.jdbc.JDBCUserStoreManager"
    type = "database"

Carbon database (WSO2_CARBON_DB).

    <description>The datasource used for registry and user manager</description>
    <definition type="RDBMS">
url= "jdbc:h2:./repository/database/WSO2CARBON_DB;DB_CLOSE_ON_EXIT=FALSE;LOCK_TIMEOUT=60000"
pool_options.maxWait = 60000 # wait in milliseconds
pool_options.testOnBorrow = true

Find more parameters.

  • Hot deployment

    <parameter name="hotdeployment" locked="false">true</parameter>
    hot_deployment = true
  • Enable MTOM

    <parameter name="enableMTOM" locked="false">false</parameter>
    enable_mtom = false

    Find more parameters.

  • Enable SWA

    <parameter name="enableSwA" locked="false">false</parameter>
    enable_swa = false

    Find more parameters.

  • Message formatters

            <messageFormatter contentType="application/x-www-form-urlencoded"
            <messageFormatter contentType="multipart/form-data"
            <messageFormatter contentType="application/xml"
            <messageFormatter contentType="text/xml"
            <messageFormatter contentType="application/soap+xml"
            <messageFormatter contentType="text/plain"
            <messageFormatter contentType="application/octet-stream"
            <messageFormatter contentType="application/json"
    form_urlencoded =  "org.apache.synapse.commons.formatters.XFormURLEncodedFormatter"
    multipart_form_data =  "org.apache.axis2.transport.http.MultipartFormDataFormatter"
    application_xml = "org.apache.axis2.transport.http.ApplicationXMLFormatter"
    text_xml = "org.apache.axis2.transport.http.SOAPMessageFormatter"
    soap_xml = "org.apache.axis2.transport.http.SOAPMessageFormatter"
    text_plain = "org.apache.axis2.format.PlainTextFormatter"
    application_json =  "org.wso2.micro.integrator.core.json.JsonStreamFormatter"
    octet_stream = "org.wso2.carbon.relay.ExpandingMessageFormatter"
    # Custom message formatters.
    content_type = "application/json/badgerfish"
    class = "org.apache.axis2.json.JSONBadgerfishMessageFormatter"

    Find more parameters.

  • Message builders

            <messageBuilder contentType="application/xml"
            <messageBuilder contentType="application/x-www-form-urlencoded"
            <messageBuilder contentType="multipart/form-data"
            <messageBuilder contentType="text/plain"
            <messageBuilder contentType="application/octet-stream"
            <messageBuilder contentType="application/json"
    application_xml = "org.apache.axis2.builder.ApplicationXMLBuilder"
    form_urlencoded = "org.apache.synapse.commons.builders.XFormURLEncodedBuilder"
    multipart_form_data = "org.apache.axis2.builder.MultipartFormDataBuilder"
    text_plain = "org.apache.axis2.format.PlainTextBuilder"
    application_json = "org.wso2.micro.integrator.core.json.JsonStreamBuilder"
    octet_stream =  "org.wso2.carbon.relay.BinaryRelayBuilder"
    # Custom message builders
    content_type = "application/json/badgerfish"
    class = "org.apache.axis2.json.JSONBadgerfishOMBuilder"

    Find more parameters.

  • HTTP transport receiver

    <transportReceiver name="http" class="org.apache.synapse.transport.passthru.PassThroughHttpListener">
            <parameter name="port" locked="false">8280</parameter>
            <parameter name="non-blocking" locked="false">true</parameter>
            <parameter name="bind-address" locked="false">hostname or IP address</parameter>
            <parameter name="WSDLEPRPrefix" locked="false">https://apachehost:port/somepath</parameter>      
    listener.enable = true                     
    listener.port = 8280    
    listener.wsdl_epr_prefix ="https://apachehost:port/somepath"
    listener.bind_address = "hostname or IP address"

    Find more parameters.

  • HTTPS transport receiver

    <transportReceiver name="https" class="org.apache.synapse.transport.passthru.PassThroughHttpSSLListener">
        <parameter name="port" locked="false">8243</parameter>
        <parameter name="non-blocking" locked="false">true</parameter>
        <parameter name="HttpsProtocols">TLSv1,TLSv1.1,TLSv1.2</parameter>
        <parameter name="bind-address" locked="false">hostname or IP address</parameter>
        <parameter name="WSDLEPRPrefix" locked="false">https://apachehost:port/somepath</parameter>
        <parameter name="keystore" locked="false">
        <parameter name="truststore" locked="false">
    listener.secured_enable = true              
    listener.secured_port = 8243        
    listener.secured_wsdl_epr_prefix = "https://apachehost:port/somepath"  
    listener.secured_bind_address = "hostname or IP address"
    listener.secured_protocols = "TLSv1,TLSv1.1,TLSv1.2"   
    listener.keystore.location ="repository/resources/security/wso2carbon.jks"
    listener.keystore.type = "JKS" listener.keystore.password = "wso2carbon"
    listener.keystore.key_password = "wso2carbon"
    listener.truststore.location = "repository/resources/security/client-truststore.jks"
    listener.truststore.type = "JKS" listener.truststore.password = "wso2carbon"

    Find more parameters.

  • VFS transport receiver

    <transportReceiver name="vfs" class="org.apache.synapse.transport.vfs.VFSTransportListener"/>                                            
    listener.enable = true

    Find more parameters.

  • Mailto transport receiver

    <transportReceiver name="mailto" class="org.apache.axis2.transport.mail.MailTransportListener"/>    ```
    enable = true
    name = "mailto"

    Find more parameters.

  • JMS transport receiver

    <transportReceiver name="jms" class="org.apache.axis2.transport.jms.JMSListener">
            <parameter name="myTopicConnectionFactory" locked="false">
                <parameter name="java.naming.factory.initial" locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory</parameter>
                <parameter name="java.naming.provider.url" locked="false">tcp://localhost:61616</parameter>
                <parameter name="transport.jms.ConnectionFactoryJNDIName" locked="false">TopicConnectionFactory</parameter>
                <parameter name="transport.jms.ConnectionFactoryType" locked="false">topic</parameter>
    listener_enable = true
    name = "myTopicListener"
    parameter.initial_naming_factory = "org.apache.activemq.artemis.jndi.ActiveMQInitialContextFactory"
    parameter.provider_url = "tcp://localhost:61616"
    parameter.connection_factory_name = "TopicConnectionFactory"
    parameter.connection_factory_type = "topic" # [queue, topic]
    parameter.cache_level = "consumer"

    Find more parameters.

  • FIX transport receiver

    <transportReceiver name="fix" class="org.apache.synapse.transport.fix.FIXTransportListener"/>
    listener.enable = true

    Find more parameters.

  • RabbitMQ transport receiver

    <transportReceiver name="rabbitmq" class="org.apache.axis2.transport.rabbitmq.RabbitMQListener">
            <parameter name="AMQPConnectionFactory" locked="false">
                <parameter name="rabbitmq.server.host.name" locked="false">localhost</parameter>
                <parameter name="rabbitmq.server.port" locked="false">5672</parameter>
                <parameter name="rabbitmq.server.user.name" locked="false">guest</parameter>
                <parameter name="rabbitmq.server.password" locked="false">guest</parameter>
    listener_enable = true
    name = "AMQPConnectionFactory"
    parameter.hostname = "localhost"
    parameter.port = 5672
    parameter.username = "guest"
    parameter.password = "guest"

    Find more parameters.

  • HL7 transport listener

        <transportReceiver name="hl7" class="org.wso2.carbon.business.messaging.hl7.transport.HL7TransportListener">
            <parameter name="port">9292</parameter>
    protocol = "hl7"
    parameter.'transport.hl7.TimeOut' = 10000
  • HTTP transport sender


    Do not duplicate the [transport.http] TOML header when you enable both the JMS listener and sender. Use the TOML header once and add both parameters (listener_enabled and sender_enabled).

    <transportSender name="http" class="org.apache.synapse.transport.passthru.PassThroughHttpSender">
            <parameter name="non-blocking" locked="false">true</parameter>
    #listener_enable = true
    sender.enable = true

    Find more parameters.

  • HTTPS transport sender

    <transportSender name="https" class="org.apache.synapse.transport.passthru.PassThroughHttpSSLSender">
            <parameter name="non-blocking" locked="false">true</parameter>
            <parameter name="keystore" locked="false">
            <parameter name="truststore" locked="false">
    sender.secured_enable = true
    sender.keystore.location ="repository/resources/security/wso2carbon.jks"
    sender.keystore.type = "JKS"
    sender.keystore.password = "wso2carbon"
    sender.keystore.key_password = "wso2carbon"
    sender.truststore.location = "repository/resources/security/client-truststore.jks"
    sender.truststore.type = "JKS"
    sender.truststore.password = "wso2carbon"

    Find more parameters.

  • VFS transport sender

    <transportSender name="vfs" class="org.apache.synapse.transport.vfs.VFSTransportSender"/>
    sender.enable = true

    Find more parameters.

  • VFS transport sender

    <transportSender name="mailto" class="org.apache.axis2.transport.mail.MailTransportSender">
            <parameter name="mail.smtp.host">smtp.gmail.com</parameter>
            <parameter name="mail.smtp.port">587</parameter>
            <parameter name="mail.smtp.starttls.enable">true</parameter>
            <parameter name="mail.smtp.auth">true</parameter>
            <parameter name="mail.smtp.user">synapse.demo.0</parameter>
            <parameter name="mail.smtp.password">mailpassword</parameter>
            <parameter name="mail.smtp.from">[email protected]</parameter>
    name = "mailto"
    parameter.hostname = "smtp.gmail.com"
    parameter.port = "587"
    parameter.enable_tls = true
    parameter.auth = true
    parameter.username = "synapse.demo.0"
    parameter.password = "mailpassword"
    parameter.from = "[email protected]"

    Find more parameters.

  • FIX transport sender

    <transportSender name="fix" class="org.apache.synapse.transport.fix.FIXTransportSender"/>
    sender.enable = true

    Find more parameters.

  • RabbitMQ transport sender

    <transportSender name="rabbitmq" class="org.apache.axis2.transport.rabbitmq.RabbitMQSender"/>
    sender_enable = true

    Find more parameters.

  • JMS transport sender

    <transportSender name="jms" class="org.apache.axis2.transport.jms.JMSSender"/>
    sender_enable = true

    Find more parameters.

  • HL7 transport sender

        <transportSender name="hl7" class="org.wso2.carbon.business.messaging.hl7.transport.HL7TransportSender">
        <!--parameter name="non-blocking">true</parameter-->
    protocol = "hl7"

Synapse thread pool properties:

synapse.threads.core = 20
synapse.threads.max = 100
synapse.core_threads = 20
synapse.max_threads = 100

Find more parameters.

  • HTTP/S worker pool properties

    core_worker_pool_size = 400         # inferred default: 400
    max_worker_pool_size = 400          # inferred default: 400
    worker_pool_queue_length = -1

    Find more parameters.

  • Preserve headers

    preserve_http_user_agent = false
    preserve_http_server_name = true
    preserve_http_headers = ["Content-Type"]

    Find more parameters.

  • JMS connection factory

    connectionfactory.QueueConnectionFactory = amqp://admin:[email protected]/carbon?brokerlist='tcp://localhost:5675'
    connectionfactory.TopicConnectionFactory = amqp://admin:[email protected]/carbon?brokerlist='tcp://localhost:5675'
    'connectionfactory.QueueConnectionFactory' = "amqp://admin:[email protected]/carbon?brokerlist='tcp://localhost:5675'"
    'connectionfactory.TopicConnectionFactory' = "amqp://admin:[email protected]/carbon?brokerlist='tcp://localhost:5675'"

    Find more parameters.

  • JMS queue


    Find more parameters.

  • JMS topic

    topic.MyTopic = example.MyTopic
    MyTopic = "example.MyTopic"

    Find more parameters.

resolver_class = "org.wso2.micro.integrator.ntask.coordination.task.resolver.RoundRobinResolver"

task_server_count = "3"

Find more parameters.

The complete list of TOML configurations for the Micro Integrator are listed in the product configuration catalog.

Migrating Log4j configurations

All ESB versions prior to EI 6.6.0 use log4j. In the Micro Integrator, the carbon.logging.jar file is not included and the pax-logging-api is used instead. With this upgrade, the log4j version is also updated to log4j2.

See the topics given below to configure log4j2 in the Micro Integrator.

Follow the instructions given below if you have used a custom log4j component in your older EI version.

  1. Replace carbon logging or commons.logging dependencies with pax-logging dependency as shown below.

    <!-- Pax Logging -->
    <!-- Pax Logging Version -->

  2. If log4j dependency is directly used, apply one of the options given below.

    • Replace the log4j dependency (shown below) with log4j2 and rewrite the loggers accordingly.
    • Replace the log4j dependency with pax-logging dependency and rewrite the loggers using commons.logging accordingly.
  3. If commons.logging is imported using Import-Package, add the version range.


  4. Follow the instructions on configuring log4j2 to register the Appenders and Loggers.

Migrating encrypted passwords

To migrate the encrypted passwords from EI 6.3.0, you need to first obtain the plain-text passwords. Once you have them, follow the normal procedure of encrypting secrets in the Micro Integrator for API-M 4.0.0. See Encrypt Secrets for instructions.

In case you need to obtain the plain-text passwords by decrypting the encrypted passwords in the EI 6.3.0, you can use the password decryption tool.

Follow the instructions given below to use the password decryption tool.

  1. Download the tool.

  2. Copy the org.wso2.mi.migration-1.2.0.jar into the EI_HOME/dropins folder in the server.

  3. Create a directory named migration in EI_HOME.

  4. Copy the migration-conf.properties file into the migration directory and update the following property.

    Property Description
    admin.user.name The user name of the system administrator.
  5. Start the server using the migrate.from.product.version system property as follows:

    sh integrator.sh -Dmigrate.from.product.version=ei
    integrator.bat -Dmigrate.from.product.version=ei


    Upon successful execution, the decrypted (plain-text) values in the secure-vault.properties and cipher-text.properties files will be written respectively to the <EI_HOME>/migration/secure-vault-decrypted.properties file and the <EI_HOME>/migration/cipher-text-decrypted.properties file in EI 6.3.0.

The encrypted passwords are now decrypted and you have access to the plain-text password values.

  1. Use the plain-text passwords and follow the normal procedure of encrypting secrets in the Micro Integrator of API-M 4.0.0. See Encrypting Secrets for instructions.

Migrating the Hl7 Transport

HL7 transport is not shipped by default in the API-M 4.0.0 Micro Integrator distribution. Therefore, the jars need to be added to the Micro Integrator server manually. See Configuring the HL7 transport for details.