Software Stacks
BETA
If you are following DevOps practices, you can create a software stack. A stack is a set of product runtimes and related database components that serve one or more purposes, such as business process management, application integration, or API management. For information on types of software stacks you might create, see Understanding Software AG Products.
Stacks are made up of at lease one of each of the layers described below.
Layer Type | Layer Content |
Infrastructure | Platform Manager and the physical and virtual machines on which Platform Manager runs. |
Runtime | Instances of one type of runtime, identically configured. The runtime instances in one stack cannot be used in any other stack. |
In development, you can create all layers of a stack on the same machine. In production, you distribute the layers across machines. You can install different types of runtime instances on the same machine, but if you install on multiple machines, the installations must be identical. For example, if you install product A on machines 1 and 2, you can install product B on machines 1 and 2, but you cannot also install product B on machine 3. The set of products, fixes, and configurations, and assets must be consistent across machines.
You create a layer based on micro templates you develop using domain specific language (CC DSL). Micro templates are modular and reusable, and can do the following:
Provision new stacks on empty host machines.
Update existing stacks with new fixes, instances, configurations, and files.
You can create the stacks from the Command Central GUI or by running Command Central commands.
You can easily monitor and maintain the runtime instances in a software stack using bulk operations. You can:
Monitor the overall status of the stack to see whether all instances are running, some instances are down, or all instances are down.
Change the status of all instances in a layer simultaneously (start, stop, and so on).
Update the configuration and fixes for one instance in a layer and then sychronize all other instances in the layer to match the updated instance.
You can also compare instance configurations, products, and fixes, and view key performance indicators (KPIs) and alerts for individual instances.
The set of software stacks that are managed by a particular Command Central is called a landscape.
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.