Welcome Serena Central users! CLICK HERE
The migration of the Serena Central community is currently underway. Be sure to read THIS MESSAGE to get your new login set up to access your account.
Acclaimed Contributor.. Joshua Hutley Acclaimed Contributor..
Acclaimed Contributor..
330 views

Upgrading IDOL index from TRIM 7.34 to RM 8.3

Hi

I am planning our upgrade from TRIM 7.3 to RM 8.3

Usually when we upgrade we create a complete copy of the prod server environment and populate with test database and test doc store. This new environment is setup at RM 8.3 and all UAT is completed on the environment. It would also have a test IDOL index.

On upgrade day, we point the new prod environment to real prod database and doc store and people start using.

One thing that is different is the IDOL indexes.

How are others handling this who are upgrading from an existing IDOL setup?

Do you move the idol indexes to the new prod environment on upgrade day?

Another option might be to recreate the IDOL index in 8.3 pre-production on a complete copy of doc store and then just reindex and new and changed documents once you go live.

 

 

 

 

0 Likes
2 Replies
Grundy Acclaimed Contributor.
Acclaimed Contributor.

Re: Upgrading IDOL index from TRIM 7.34 to RM 8.3

The version of IDOL has gone from 7 to 10.
It is highly recommended that you perform a full reindex with HPE RM 8.3.

Fortnately in 8.2 onwards there's an option to reindex ahead of time using a specified dataset ID, so even if your UAT environment has a different ID to PROD, you can still perform the reindex before go live.

 



::::::::::::::::::::::
NOT A HP EMPLOYEE
::::::::::::::::::::::

INFORMOTION.com.au
0 Likes
Acclaimed Contributor.. Joshua Hutley Acclaimed Contributor..
Acclaimed Contributor..

Re: Upgrading IDOL index from TRIM 7.34 to RM 8.3

Ok it is good to hear an idol reindex is recommended from 7.3 to RM 8.3

If possible I would like to reindex in pre-prod prior to go live.

Maybe I can do this using a copy of the document store. create all the indexes and just not enable content indexing in the events processor to avoid UAT and testing documents getting indexed. 

On go live, re-enable events processing for IDOL and reindex any missed created and updated records.

Still keen to hear from others.

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.