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

All docs This doc
Expand all   Collapse all

Versions Compared

Old Version 5

changes.mady.by.user Lahiru Madushanka

Saved on

compared with

New Version 6

changes.mady.by.user Lahiru Madushanka

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: json-path result change

...

Info
iconfalse

Before you begin, note the following changes that may affect your ESB artifacts.

  • If you have created a messages store in your configuration and configured the provider path as repository/conf/jndi.properties in your ESB 5.0.0 instance, this needs to be updated with the jndi.properties file path in EI 6.5.0 (which is conf/jndi.properties).
  • 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 arguments (args) tags to get property values. Inline $ctx support (in the payload factory) has been deprecated since WSO2 EI 6.4.0.
  • From WSO2 EI 6.4.0 onwards, the XSLT mediator writes response messages to the JSON stream. Note that in WSO2 ESB 5.0.0, the XSLT mediator was not doing any changes to the JSON stream after message transformation.
  • From WSO2 EI 6.4.0 onwads, there are validations affecting the Enrich mediator, which prevents the source and target in the message body.

  • From WSO2 EI 6.4.0 onwards, 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()".

  • From WSO2 EI 6.4.0 onwards, 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 axis2.xml file.
  • If you have used json-path expression without the dot notation ( ex: $key ), you need to change them by adding the dot after the dollar sign. ( ex: $.key )
  • If you have used json-path expression with recursive descent ( ex: $..key ), it will return an array (even the resultset has just one element), whereas in ESB it returns just the value when there is only one matching element.

You should manually deploy the Composite Application Archive (CAR) files that you have in WSO2 ESB 5.0.0 to WSO2 EI 6.5.0.

...

  1. Update the configuration files with information of the migrated keystores and truststores. See Configuring Keystores in WSO2 products for more information.
  2. Go to the <EI_HOME>/wso2/analytics/conf/datasources directory and update the Carbon datasource configuration in the master-datasources.xml file with the details of the Carbon database. For instructions, see Changing the Carbon Database and select your database type.
  3. Go to the <EI_HOME>/wso2/analytics/conf/datasources directory and update the datasource configuration in the analytics-datasources.xml file with the details of the Analytics-specific databases.
  4. Go to the <EI_HOME>/wso2/analytics/conf directory and update the datasource references in the user-mgt.xml and registry.xml files to match the updated configurations in the master-datasources.xml file. The instructions are available in Changing the Carbon Database.
  5. Go to the <EI_HOME>/wso2/analytics/conf/analytics/ directory and update the rdbms-config.xml file according to the configurations in the same file of your previous Analytics installation.
  6. Go to the <EI_HOME>/wso2/analytics/conf/data-bridge directory in WSO2 EI 6.5.0 and update the configuration files according to the configurations in the previous installation.

  7. Go to the <EI_HOME>/wso2/analytics/conf directory and update the event-processor.xml file according to the configurations in the previous installation.

    Info

    If you enable the HA mode for ESB Analytics by setting the <mode name="HA" enable="true"> property in the event-processor.xml file, state persistence is enabled by default. If there is no real-time use case that requires any state information after starting the cluster, you should disable event persistence by setting the persistence attribute to false in the same file as shown below.

    Code Block
    languagexml
    <persistence enable="false">
    <persistenceIntervalInMinutes>15</persistenceIntervalInMinutes>
    <persisterSchedulerPoolSize>10</persisterSchedulerPoolSize>
    <persister class="org.wso2.carbon.event.processor.core.internal.persistence.FileSystemPersistenceStore">
        <property key="persistenceLocation">cep_persistence</property>
    </persister>
</persistence>

  8. Enable WSO2 EI 6.5.0 to publish ESB statistics to the Analytics profile by following the instructions in Publishing ESB Analytics Data to the Analytics Profile.

    Info

    Note that in EI 6.5.0, you need to configure the <EI_HOME>/conf/carbon.xml file to enable the ESB server to publish statistics, whereas in WSO2 ESB, you need to configure the <ESB_HOME>/repository/deployment/server/eventpublishers/MessageFlowConfigurationPublisher.xml and <ESB_HOME>/repository/deployment/server/eventpublishers/MessageFlowStatisticsPublisher.xml file instead.

  9. Check for any other configurations that were done for WSO2 ESB 5.0.0 Analytics based on your solution and update the configurations in WSO2 EI 6.5.0 accordingly. For example, check the configurations related to external user stores, caching, mounting, transports etc.

...