Upgrade or Roll Back a Server Role

You can upgrade a server role Entity that contains a logical, predefined set of components (system software or certified third-party software) deployed in the Data Center and Site Zones that provide specific functionality for the system. to a newer version or rollback an existing server role to a previous version. This section discusses the Enterprise Manager operations that occur when a server role is upgraded or rolled back to a previous version.

Server role upgrades occur when you install a maintenance release (such as a new update release, or component hotfix) on a managed server Server that is managed by the Enterprise Manager application.. The maintenance release must contain a newer version of a server role than the one currently existing on the server for the installation to be an upgrade.

Server role rollbacks occur when you first upgrade a server role, but then roll the server role back to the version that existed before the upgrade. (You roll the server role back by installing the maintenance release containing the older version of the server role).

During a server role upgrade or rollback, the server role metadata file is replaced on the managed server.

If a server role on a server is either upgraded or rolled back, Enterprise Manager detects the change in the role during the server discovery Process performed by the Enterprise Manager application in which the application regularly communicates with each server in the system to determine whether any new software (new release, service pack, hot fix, or patch) or server roles have been added or installed on the server. process. To understand this process, see Server Discovery.

After you install a maintenance release, it can take a little time for the Enterprise Manager to discover the newly installed versions of the server roles. Discovery of newly installed server roles does not happen instantaneously. You can force Enterprise Manager to discover new server roles instantaneously. To discover new server roles instantaneously, follow the procedure to perform server discovery described in Manually discover a server and its server roles.

Upon detection Function of the IAFD product that compares a caller’s voice to one or more voiceprints in a watch list to detect if a target is participating in a call. of an upgraded or rolled back version of a server role on a managed server, the Enterprise Manager must take action. The Enterprise Manager must perform operations in these three areas to ensure that the upgrade or rollback is properly handled:

Active/Inactive Status - Enterprise Manager must apply either an active or inactive status to the changed server role.
Migrate Instance Data - Enterprise Manager must migrate the existing server role instance data to the upgraded or rolled back version of the server role.
Auto-Associations - Enterprise Manager must automatically make any new associations defined in the metadata of the upgraded or rolled back version of the server role.

To support the upgrade process described in this section, there is a specific numbering convention the software developers must follow. Software developers must follow this convention when creating server role metadata files to support software upgrades. For more information, see Numbering Convention for Server Role Metadata Versions When Working on New Software Releases .