installing a second catalog on another machine for clustering catalog env
Article ID: 144093
Updated On:
Products
Issue/Introduction
We already on service catalog running - now the requirement is switch it into a cluster . When i install second catalog on another machine for it , is a complete installation on the second server really necessary? because the time consuming mdb installation steps are already done in the first installation on server .
The only info we found here and that is not clear enough for me
https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/business-management/ca-service-management/17-1/administering/administering-ca-service-catalog/ca-service-catalog-clustering/how-to-setup-horizontal-clustering-nodes-for-ca-service-catalog.html
Environment
Release : 17.2
Component : CA SERVICE CATALOG
Resolution
Yes, it absolutely necessary . The installer is not going to literally do MDB installation since it is able to know that MDB is already there but it needs to update the second catalog server's related configuration file so that the second catalog server knows where is the MDB and how to connect to it . Also , the installer needs to update some tables ( for example , al_cdb_* tables ) in MDB so that MDB is able to record that there is another catalog server using this MDB and also record the related information about this second server in the MDB .
Additional Information
https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/business-management/ca-service-management/17-1/administering/administering-ca-service-catalog/ca-service-catalog-clustering/how-to-setup-horizontal-clustering-nodes-for-ca-service-catalog.html
Feedback
