Configure storage to index collaborative data

The following procedures describe how to configure your index to use data coming from the storage.

It includes:

  • the Exalead CloudView document cache has to be enabled on the document build group.

  • the RepushFromCache setting must be set to true in StorageService.xml.

  • the StorageServiceDocumentProcessor must be configured in the Analysis pipeline.

  • the data of the collaborative widget should be mapped to metas.

This task shows you how to:

See Also
Storage Administration
Troubleshooting

Requirements

When you use a collaborative widget with the “DOCUMENT” scope, it uses the build group, the source and the doc URI, to identify each document. These values are required and must be set to be used for hit content.

  1. In the Administration Console, go to Search Logics > Facets, expand the Source category.
  2. Make sure that the Root property is set to Top/source. This source category is required to retrieve the hit information used to create primary keys in the storage mechanism, so as to link the collaborative widget to a document.
  3. Make sure that the Use for hit content option is selected. Otherwise, your collaborative will have no source on the Mashup Builder.

Enable the build group cache

  1. In the Administration Console, go to Deployment > Build groups.
  2. Select Document cache.

Enable the RepushDocuments property

  1. Go to your Exalead CloudView <DATADIR>/config/360 directory.
  2. Open the StorageService.xml file.
  3. Set the RepushDocuments property to true.

Configure the StorageServiceDocumentProcessor in the Analysis pipeline

  1. In the Administration Console, go to Index > Data Processing.
  2. Select your analysis pipeline, for example ap0.

    The Document Processors tab displays.

  3. From the Processor Types panel:
    1. expand the Other node,
    2. drag a Storage Service Document Processor to the list of Current Processors (preferably near the top of the list).
  4. Click the StorageServiceDocumentProcessor link and define the Instance property.

    Usually the instance is sts0. You can check the instance name from the Roles menu, by expanding the Storage Service role.

  5. Click Save and then Apply your configuration changes.

Make data searchable

  1. In Mashup Builder, check the meta name property of your collaborative widget.

    For example, the Tags meta name for a Tags widget is set by default to tags[].

  2. In the Administration Console, go to Data Model.
  3. Click Add Property to add a property matching the meta name specified in the Mashup Builder (see step 1). For example:
    • Name: tags
    • Data Type: Alphanum
    • Semantic Type: text
    • Field Type: Dedicated field only
  4. Click Accept.

    By default the property is searchable.

  5. Select the Preview to check your configuration changes.
  6. Click Apply.

You should now be able to search on your meta in the Mashup Builder. For example, you can search on your tag values by entering tags:MyTag

Index aggregated results

  1. Make sure you followed the standard indexing workflow described in the previous procedures.
  2. Go to your Exalead CloudView <DATADIR>/config/360/applications/<APPLICATION NAME> directory.
  3. Open the Storage.xml file.
  4. Add as many StorageKey nodes containing Aggregate nodes as necessary. In the following example, we want to index the COUNT and SUM aggregation values for the bagkey StorageKey. 

    <Storage xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation=">
   <Indexing>
     <StorageKey name="bagKey[]">
     <Aggregate type="COUNT"/>
     <Aggregate type="SUM"/>
     </StorageKey>
    </Indexing>
</Storage>

  5. Build your configuration:
    1. Go to your Exalead CloudView <DATADIR>/bin/ directory.
    2. Launch the following command: buildgct.<sh|bat>

The StorageServiceDocumentProcessor will create the corresponding metas with aggregate operations as suffixes. For our example: bagKey_count and bagKey_sum