Container Manager

Active Environment

In the Container Manager you can define multiple Environments, and place both Static and Dynamic Containers under each Environment. Moreover, Container names in different Environments can have the same name. When running scripts, queries, and code packages against Containers, Combine will run the scripts against Containers in the currently active Environment. Furthermore, only a single Environment can be active at any given time and the active Environment is the one with bold letters in the Container Manager. To demonstrate the functionality of the active Environment, consider the images below. When running scripts against the Container named All User Databases when the Development Environment is active, each script will be run against all databases in that Container. If you set the Production Environment to be active instead of Development, running the same script against the Container with the same name will execute the code on the databases defined in the All User Databases Container under the Production Environment.

As stated above, the active Environment is the one having bold letters in the Container Manager. For example, the Development Environment is the active Environment in the figure below.

Figure 56:  The Container Manager when Development is the active Environment.

You can set other Environments to be active by right-clicking the desired Environment icon and selecting Set As Active Environment from the options menu. Doing so will "deactivate" the previously active environment and will set the new Environment as active.

Figure 57:  Setting Production as the new active Environment.

© 2001-2018 JNetDirect, Inc. All Rights Reserved.