Page Comparison

...

Go to the <DAS-3.2.0_HOME>/repository/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 that you made in the above step.
For detailed instructions to configure the user-mgt.xml file, see User Management.
For detailed instructions to configure the registry.xml file, see Registry.
Compare the configuration files in the <DAS_HOME>/repository/conf/data-bridge directory for DAS 3.1.0, and 3.2.0.

Compare the configuration files in the <DAS_HOME>/repository/conf/analytics directory for DAS 3.1.0, and 3.2.0. Change the default values in DAS 3.2.0 to the same values you have specified in DAS 3.1.0.

Info

In DAS 3.2.0 following files are moved to <DAS_HOME>repository/conf/data directory because these runtime configuration files are required for the indexing operation. This is further explained also mentioned under Migrating indexing information.

my-node-id.conf
local-shard-allocation.conf

Change the default values in <DAS_3.2.0_HOME>/repository/conf/event-processor.xml file to the same values you have specified in the <DAS_3.1.0_HOME>/repository/conf/event-processor.xml file.

Info

In DAS 3.2.0, we have introduced a parameter for single-node persistence in the event-processor.xml file. The deployment mode is set to single-node deploment by default as shown below.
<mode name="Single" enable="true"> If the existing mode in DAS_3.1.0 is HA, you have to disable the Single mode and enable the HA mode in DAS_3.2.0 as shown below.
<mode name="Single" enable="false">
<mode name="HA" enable="true">

If you enable the HA mode for WSO2 DAS 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

language	xml

<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>

Check for any other configurations that were done for DAS 3.1.0 based on your solution and update the configuration files in DAS 3.2.0 accordingly. For example, configurations related to external user stores, caching, mounting, transports etc.

...

Localtabgroup

Localtab

title	Fresh setup with reindexing

All the index data and configurations are initialized when you start WSO2 DAS 3.2.0 for the first time. Therefore, if your WSO2 DAS 3.2.0 setup is a fresh setup and you want to reindex all the data after migrating analytics tables, you do not need to copy any of the indexing related configurations.

Localtab

title	Using reindexing command

This method involves running the analytics data backup/restore tool with the -reindexEvents setting to index the data. Here, the indexing is done using the existing data in the database to which you already connected WSO2 DAS 3.2.0 in the Migrating the configurations section. For more information, see Backing Up or Restoring Analytics Data.

Localtab

title	Copying indexing data

Follow the steps below to migrate the index information from DAS 3.1.0 to DAS 3.2.0.

Copy the contents of the <DAS_3.1.0>/repository/data directory and replace the contents of the <DAS_3.2.0>/repository/data directory with it.
Take copies of the following files in the <DAS_3.1.0_HOME> and use them to replace the new files in DAS 3.2.0 that are in the locations given below.
- <DAS-3.1.0_HOME>/repository/conf/analytics/my-node-id.dat file
  The following needs to be done when copying this file:
  1. Rename the file to datamy-node-id.dat.
  2. Copy this file to the <DAS_3.2.0_HOME>/repository/data directory.
- <DAS-3.1.0_HOME>/repository/conf/analytics/local-shard-allocation-config.conffile
  Copy this file to the <DAS_3.2.0_HOME>/repository/data directory.

Note
Make sure that you do not mix the configuration files between nodes. The configuration files and index data of DAS 3.1.0 - node 1 should be copied to DAS 3.2.0 - node 1, and the configuration files and index data of DAS 3.1.0 - node 2 should be copied to DAS 3.2.0 - node 2 etc.

Migrating encrypted data

To migrate encrypted data in WSO2 DAS 3.1.0 when you upgrade to WSO2 3.2.0, follow the steps below:

...

Versions Compared

Old Version 10

New Version 11

Key

Migrating encrypted data