The latest version for DAS is WSO2 Data Analytics Server 3.1.0. View documentation for the latest release.
WSO2 Data Analytics Server is succeeded by WSO2 Stream Processor. To view the latest documentation for WSO2 SP, see WSO2 Stream Processor Documentation.

All docs This doc

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

Updating WSO2 DAS

For detailed information about how to apply WUM updates to DAS, see the WSO2 Admin Guide - Updating WSO2 Products.

Best practices

This section covers the common guidelines best practices to follow when applying WUM updates to DAS. The main factors to consider are as follows.

Table of Contents

The unique node ID

The my-node-id.dat file is created in the <DAS_HOME>/repository/conf/analytics directory. If you do not create it, it is automatically created at server start-up. This file contains a unique ID for the DAS node that helps to identify it. The databases are updated with the entries in this file. Therefore, when you apply WUM updates to nodes, use the unique ID in this file to keep track of the nodes.

Indexing data and the indexing queue

When WSO2 DAS uses Lucene for indexing, the indexing related information is stored in the <DAS_HOME>/repository/data directory. The data that requires to be indexed goes through a que that is known as the indexing queue. Once the data is indexed, it is stored in the index_data directory. For detailed information about the indexing process, see Indexing Overview - Indexing Architecture.

Before you discard the old DAS instance, you must take a backup of the <DAS_HOME>/repository/data directory and copy it to the DAS binary pack that is updated with the WUM updates.

Shard allocation

Information relating to the Shard allocation is maintained in the <DAS_HOME>/repository/conf/analytics/local-shard-allocation-config.conf file. This file stores the shard number along with its state (that can be INIT or NORMAL). The INIT is the initial state. Usually this state cannot be seen from outside. This is because the INIT state changes to the NORMAL state once the server starts. If the indexing node is running, the state of shards should be NORMAL and not INIT. The NORMAL state denotes that the indexing node has started indexing. For detailed information about the shard allocation, see Indexing Overview - Indexing Architecture.