Understanding 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).
Install fixes and support patches on instances.
View key performance indicators (KPIs) and alerts. Three KPIs are provided for an installation: system CPU, disk space, and system memory usage. Each KPI shows a marginal threshold, which indicates that performance or stability might soon be affected, and a critical threshold, which indicates that performance or stability are probably affected. Alerts are raised when the value of a KPI changes from normal to marginal or critical, or from marginal to critical. Alerts are cleared when KPI values return to normal.
Up to three KPIs are provided for some, but not all, instances and components when they are online. Command Central retrieves KPIs regularly from the instance or component by polling. Alerts are raised when the status of an instance or component changes from online to stopped, unresponsive, failed, or unknown, or when a KPI value changes from normal to marginal or critical or from marginal to critical. Alerts are cleared when status or KPI values return to normal.
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 maintenance 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 update existing environments with new fixes, instances, configurations, and files.
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.