Considerations for Deployments

Note

Only global administrators, promotion administrators and promotion users can deploy revisions. More information is available in the Authorization section.

Cache

Consider the following aspects related with cache during Solution Manager deployments:

  • It is not possible to define Virtual DataPort properties at cluster level. In the case of cache data sources in multicluster environments, it is necessary to configure the cache manually. Due to this limitation, you should not include any cache data sources in CREATE revisions, otherwise during the deployment process the cache configuration of all clusters will be overwritten, leaving one of them in a possible inconsistent status. Solution Manager shows a warning message when deploying a revision with the features above:

Warning message when deploying revisions with cache data source a in multi-cluster environment

Warning message when deploying revisions with cache data source a in multi-cluster environment.

  • If a revision includes Scheduler VDP Cache jobs, the Solution Manager might execute those jobs after the VQL changes are deployed in the first Virtual DataPort server of each cluster (if swap cache is configured or if a job is marked for execution). If the Virtual DataPort cluster does not use a shared cache, the Solution Manager may not update properly the cache of each Virtual DataPort server. Thus, in Virtual DataPort clusters without shared cache, you must update the cache using the Scheduler Web Tool or the Scheduler API and not the Solution Manager.

  • The cache swap process (in deployments in environments with a single cluster and cache swap enabled) only works with global cache (it does not work with caches defined for particular databases).

Summaries

If your revision includes a summary and that summary is either new or a modification of an existing one, remember to include the Scheduler job that loads the summary and select that job to be executed on the first Virtual DataPort server of the target environment. Otherwise the optimizer will not use the summary on the target environment because the table does not exist yet, or the definition has changed. For more information about summary promotions visit section Summary promotions.