Migrating UNIFYNow Between Environments

Configuration Migration

UNIFYNow uses a local storage mechanism for persisting its configuration. This is located in a series of XML files located in the Extensibility directory in the UNIFYNow service directory.

Image 3340

Migrating between development, test, and production environments is as simple as copying the contents of this directory into the Extensibility directory of the new environment while the UNIFYNow service is turned off (not just the scheduler). When the UNIFYNow service is restarted, the new configuration will be loaded. The breakdown of these files is as follows:

Filename Description

The configuration for all existing agents


Internal settings that manage UNIFYNow's configuration


Configured in order to enforce additional Security


The configuration for operation list groups


The configuration for all operation lists


Stores metadata about the MIM Auto configuration process.

Unify.Product.EventBroker.MIMReferenceRepositoryPlugInKey.extensibility.config.xmlStores information about MIM MAs and runprofiles. This file should not be edited manually. v4.0+ only.

Used to configure the self-hosted option.


Contains default and additional logging configuration

In addition to the above files, some environments may have also updated the following files:

  • Unify.Service.Event.Debug.exe.config
  • Unify.Service.Event.exe.config
  • Unify.Service.Event32.Debug.exe.config
  • Unify.Service.Event32.exe.config
  • Web.config

If these files have been modified, they should also be migrated.

TIP: read the below section prior to commencing the migration.

Migration Considerations

There are a few issues to consider when migrating configuration between environments:

  • Partial migrations are possible using the table above, however, the absence of configured agents will result in incomplete operation configuration
  • Agent configuration is not currently updated when the configuration is migrated. This means that agents will still use the server names specified in the source environment. Consider the use of aliases to ensure configuration remains consistent.
  • If aliases are not used, Agents will need to be reconfigured to point to the relevant servers in the new environment.
  • Individual operations need not be updated unless they reference items that are located in a different location to the base environment, such as SQL stored procedures or PowerShell Script.
  • When UNIFYNow is enabled, the scheduler is also enabled (see Scheduler). On the initial migration it is advisable to copy out the configuration with startup operation lists turned off, unless aliases are being used between environments.
  • In v4.0+, MIM operations which reference MAs and run profiles are able to persist their reference to these resources after a migration provided the MA/run profiles are migrated as-is and not reconfigured before the first run of UNIFYNow in the new environment. Otherwise, the operations will need to be reconfigured with the updated MA and run profile choice.
Configuration Extensibility

This article was helpful for 1 person. Is this article helpful for you?