Hi all, I would like to further understand srmInstaller.ImportSrm() behaviour when adding/updating components relating to SRM components. These components can include:
- Booking Manager element
- Profile Parameters
- Profile Definitions
- Profile Instances
- Service Definitions
- Resource Pools and Resources
- Automation Scripts
- Functions
For each of the above, I would like to understand:
Q1> How does the srmInstaller decide if a given component already exists or does not exist? (e.g.: by name or GUID or other)
Q2> What happens if the component already exists? (overwrite config, delete & replace or ignore)
Q3> What happens if the component does not exist?
Hi Bing,
The SRM Installer will always attempt to import the components contained in the import ZIP file.
Please find the answers to your questions below:
Q1 - The check is always performed using the component's GUID.
Q2 - If the component already exists, the SRMInstaller overrides its configuration.
Q3 - If the component does not exist, the SRMInstaller creates it.
I hope this helps