Page History

...

1. You are upgrading to version 9.7 or higher and want to benefit from the full text search. The aggregates that you already have stored in database must be indexed.
2. All your aggregates are already are indexed and a new version of the model is published to production wit new business logic, so you want to re-index all aggregates so that derived values that are changed with the new logic can be found during the search.

...

The scenario in which this service does not suffice is that you want to (re-)index older versions of an aggregate. This can be needed as an since a specific old version of an aggregate can be referenced from another aggregate. (Re-)Indexing the old aggregate version has to be a conscious choice, and you might wish to keep the old index like it is for older versions. An aggregate that was created in an old version was indexed using the logic valid at that moment of time, so these may belong together. This can be a reason for only (re-)indexing the most recent version of aggregates.

In case that you want to re-index older versions of existing aggregates, we have created a special service that allows you to just index aggregates, without updating them in the database. The first step is to create the service definition in studio, and then call it in an appropriate flow. The new migration service marks the aggregate as changed, without actually creating a new version.

...

1. In Studio add a custom service named AQ_Aggregate_Index_Migrate
2. The service definition looks like this:
   
   
   

3. The

   aggregateId

   AggregateId is always required.
   The aggregate version is optional. In case this is not specified, the latest version of an aggregate will be indexed

   .
    We need a service that is able to update an aggregate

   . This service has the following parameters:

    

   Parameter	Direction	Value	Data Type	Description	Fill
   AggregateType	Input	Module Element	Aggregate	Select the aggregate that you want to update.	Required
   AggregateIDAggregateId	Input	Expression	Integer	Please provide the attribute containing the ID of the aggregate entry to index.	Required
   AggregateVersion	Input	Expression	Integer	If a specific version of the aggregate needs to be updated. If not provided then the latest one is updated.	Optional
   StoreInstances	Input	Expression - Multivalued, Multivalued results	Entity	Specify the starting point instance(s) used for storage.	Optional

    

   Event Name	Event Type	Description
   AppException	Cancel	The service takes this exit if indexing failed for some reason.

   
   

...

Step-by-step guide to model the migration flow

• A project that wants to index the aggregates has to create an exposed migration flow.
• This flow should be called for every aggregate Id in the database. It can be passed as a parameter in the URL, and retrieved from there with the BB_SetRequestParameters service.
• In this flow you then call the AQ_Aggregate_Read to load the existing aggregate into the profile. It might be needed to also load referenced aggregates in order to obtain a complete profile.
• The next step is to use the AQ_Aggregate_Index_Migrate or AQ_Aggregate_Update service to update the aggregate index.

...

...