Table of Contents

Configuring indexing settings in DataMiner Cube

The indexing settings in System Center determine which information is stored in the indexing database. To configure these settings, go to System Center > Search & Indexing.

Tip
  • From DataMiner 10.3.0/10.3.3 onwards, for systems with a dedicated clustered storage setup, essential indexing database settings that are required to set up the database are available in System Center along with the general database settings. See Configuring the general database settings.
  • For earlier DataMiner versions or for setups with storage per DMA, the indexing setup is configured in DB.xml. See indexing database settings.

The following settings are available:

  • Enable indexing on alarms: Enables indexing of alarms. If this option is not enabled, the enhanced search options in the Alarm Console are not available.

  • Migrate booking data to Indexing Engine: Starts a wizard that allows you to migrate booking data from the Cassandra database to the indexing database. Only displayed in case booking data have not been migrated yet.

    Note

    If you are using a DaaS system, Indexing Engine settings cannot be customized. As such, from DataMiner 10.3.0 [CU15]/10.4.0 [CU3]/10.4.6 onwards, the Indexing Engine settings are no longer available for DaaS.

    Please note the following regarding the migration of booking data:

    • Property names must not start with an underscore (“_”) or contain any of the following characters: . # * , " '
      As such, the wizard will ask you to rename certain booking properties before starting the migration. To ensure the correct functionality of the Service & Resource Management module, some properties will be renamed automatically. For example, the Visual.Background and Visual.Foreground properties will automatically be renamed as VisualBackground and VisualForeground.

    • After migrating the booking data to the indexing database, make sure to check your Automation scripts and Visio files and adjust the booking property names where necessary.

    • After the migration is complete, you can use the Retrieve report button in the wizard to get a summary report of the migration.

    • An indexing database takes about twice as much disk space to store booking data compared to a Cassandra database.

Note
  • The indexing configuration is saved in the file Indexing.xml in the folder C:\Skyline DataMiner\Database.
  • To include booking data from the indexing database in a custom backup, select Include SRM in backup in the content tab of the Backup page. See Configuring the DataMiner backups.
  • Resources are not automatically migrated to the indexing database as well. For more information on how to migrate these, see Migrating SRM resources to the indexing database.
Tip

See also: Indexing database settings

Propose changes