Command Central 10.1 | Getting Started with Command Central | Understanding Command Central | Creating Standalone Product Installations
 
Creating Standalone Product Installations
If you have existing product installations that were created using the Software AG Installer, you can quickly connect Command Central to those product installations and organize them into development, test, and production environments. You can then easily monitor and maintain the product instances in your installations. You can:
*Compare instance configurations across installations and environments.
*Change the status of an instance (start, stop, and so on).
*View key performance indicators (KPIs) and alerts for instances.
*Install fixes on instances.
You can use Command Central to create product installations, product instances, and database components within environments. The set of environments that are managed by a particular Command Central is called a landscape.
You can perform these tasks from the Command Central GUI or by running Command Central commands.
You can automate installation, maintenance, and upgrade tasks for product environments by developing composite templates that define an environment using domain specific language (CC DSL) and applying the templates using commands. Templates can do the following:
*Provision new development, test, and production environments on empty host machines.
*Update existing environments with new fixes, instances, configurations, and files.
*Upgrade and migrate environments to the latest product releases.
Note:
The term "instance" as used in this section includes both runtime instances and runtime instance components. The latter are independent modules that run within a runtime instance but have their own configurable elements. For example, Task Engine is a runtime instance component on My webMethods Server.