Managing Version Control › Version Control for Installation Customizations
Version Control for Installation Customizations
If you customize your CA SDM client, you can use version control to monitor and control the installation of the customizations on the clients. To do this, create a server_custom.ver (or server_secondary_custom.ver for secondary servers) file describing your customizations.
Version control uses the two version files (server_default.ver and server_custom.ver) independently to verify the version of components on the clients. Your components should be designed so that a file is never controlled by two or more components. Version control processes each component separately. Version control verifies a file each time it encounters a component that controls the file, which sometimes has unexpected results if the version number or date is not the same.
To use version control to monitor and control the installation of the customizations on the clients, follow these steps:
- Create the server_custom.ver file in one of the following locations:
- Linux—$NX_ROOT/site/mods/server_custom.ver
- Windows—installation‑directory\site\mods\server_custom.ver
- Add components to server_custom.ver for each of your changes, using one of the following setups:
- Create dir_ctl components to implement version control at the directory level. When you do this setup, all files in the directory are considered to be at the same version and are upgraded at the same time. This setup minimizes maintenance to server_custom.ver, but may sometimes result in upgrading files that are already up-to-date on the client.
- Create file_ctl components to implement version control at the file level. This setup provides better documentation and control, but the server_custom.ver file may be larger.
- Update the version number in server_custom.ver whenever you make a change to a customized component. The version number lets version control recognize clients that have a different version.
