CDM search index are not updated during application startup

Data Services
1

Hi There,

I’m trying to figure out how the search index works with regards to CDM during application startup, for non-cdm data this can be configured using mgmtp.a12.dataservices.search.index.initialization.mode but this does not update the search index for cdm. my scenario was migration where the data in the database were correctly migrated but the UI remained unchanged, is there a way to trigger this type of index update ?

Again for non cdm data this works like a charm

2

Could you please provide which DS version exactly?

3

data service version is 35.0.0, ty

4

I propose verifying with mgmtp.a12.dataservices.search.index.initialization.mode=rebuild_index,
and with cddsync profile activated, cddsync consists of

mgmtp.a12.dataservices.cdd.dirtyDocuments.sync.enabled=true
mgmtp.a12.dataservices.cdd.dirtyDocuments.producer.enabled=false
mgmtp.a12.dataservices.cdd.dirtyDocuments.consumer.enabled=false
5

Hi,
There are some difference ways to setup the server for CDD, depend on your system architecture.
If you are using single DS server. You can use the setup that @loi-risen-dale propose.
If you are using multiple servers. You have to setup an external MQ broker and connect the application to it using.
You can verify yourself server setup with this documentation GetA12 Login.
With the correct setup you have to restart the server, re-build the index to index all the documents, both cdd and none-cdd documents: mgmtp.a12.dataservices.search.index.initialization.mode=rebuild_index

6

Thanks for the response, I updated our configurations as suggested and with extra Hazelcast configuration and this now works as expected.

7

Thanks, we currently have a single DS server and hence I followed @loi-risen-dale suggestion

8

Hi,
Glad it resolved your problem
But please be aware this sync mode is considered a bad practice in PROD, for more details please have a look at DS documentation.