Custom configuration object versions
Custom configuration objects are versioned.
BMC Server Automation assigns version numbers to the custom configuration objects that it distributes. Each version number has a <Vvssbbbb> format, where:
- <V> — Major version
- <v> — Minor version
- <ss> — Service pack
- <bbbb> — Build number, which can provide patch or hotfix numbers
BMC Server Automation assigns numbers to custom configuration objects using a scheme that provides the major and minor release level as well as an identifier for the custom object itself.
Version compatibility and availability
Several factors determine what version of custom configuration objects are available when you access a server.
- If your Application Server is newly installed, then the custom configuration objects provided for that release are available when you install an agent running the same release. In fact, for the configuration objects to work properly, the RSCD agent version must match the version of the Application Server. For example, if you have just installed an Application Server of version 8.8, you must install an agent of version 8.8, and custom configuration objects that correspond to version 8.8 are automatically installed and ready for your use on that server.
- If your Application Server has been upgraded from an earlier release, then you should be able to see and use custom configuration objects on servers running versions of agents that correspond to the version history of the Application Server. For example, if your Application Server was originally running version 8.3 and then was upgraded to version 8.7, you should be able to see and use custom configuration objects on servers running version 8.3 and version 8.7.
- However, if agents were added to your system when they were running an earlier version and those agents were later upgraded, to see and use custom configuration objects on those servers, you must run an Update Server Properties Job on those servers.