Timeframe for Community portal to reflect changes to the Service Catalog
I have successfully deploy the Community portal and have been running it side by side with the SCSM native portal to compare. I have noticed that while the Microsoft portal reflects changes I make to request offerings and service offerings pretty much straight away the Cireson portal takes some time to before it shows those changes. I assume this is as a result of the Microsoft portal connecting directly to the Service Manager database while the Cireson portal connects to the cachebuilder database.
So my questions are:
How frequently is the cachebuilder database from the Service Manager database?
Is it the Cireson Cache Builder service that manages that updating process?
Is there anyway to force an update to occur or configure updates to occur more frequently?
Best Answer
-
Joe_Burrows Cireson Devops Super IT Monkey ✭✭✭✭✭Hi Eds
Thanks for connecting with the Cireson Community!How frequently is the cachebuilder database from the Service Manager database?
On start up and every 24 hours the service catalog schedule runs - this schedule can be changed however its easier to just restart the cache builder when a change as made. As once you have your catalog setup changes are pretty static.
Is it the Cireson Cache Builder service that manages that updating process?
Correct
Is there anyway to force an update to occur or configure updates to occur more frequently?
Yes indeed, a restart or a change of the time in the cachebuilder config file
For more information please review Appendix 3 – Cachebuilder Overview on page 21 of the install guide. This has a helpful table showing all the different schedules for the different objects that get synced and at what times and how to change the defaults.
Hope that helps! Let us know if you have any further questions
Regards
Joe
6
Answers
Thanks for connecting with the Cireson Community!
How frequently is the cachebuilder database from the Service Manager database?
On start up and every 24 hours the service catalog schedule runs - this schedule can be changed however its easier to just restart the cache builder when a change as made. As once you have your catalog setup changes are pretty static.
Is it the Cireson Cache Builder service that manages that updating process?
Correct
Is there anyway to force an update to occur or configure updates to occur more frequently?
Yes indeed, a restart or a change of the time in the cachebuilder config file
For more information please review Appendix 3 – Cachebuilder Overview on page 21 of the install guide. This has a helpful table showing all the different schedules for the different objects that get synced and at what times and how to change the defaults.
Hope that helps! Let us know if you have any further questions
Regards
Joe