Create a Software Stack

1. If you must manually install Platform Manager on target nodes (for example, because the user account created to install products does not allow remote access from Command Central), use the same password for every Platform Manager that will be included in the stack you are going to create.

2. Create aliases that specify credentials you will need for the stack. Go to Environments > ALL > Instances > CCE > Command Central Server > Configuration > Credentials, click the plus icon

, and follow the steps below.

If you manually installed Platform Manager on target nodes, or if you are going to create an infrastructure layer that connects to new remote nodes that are already equipped with Platform Manager but that are not yet registered in Command Central, click User name and password and create an alias for the Platform Manager credentials.

If you are going to create an Infrastructure layer that creates remote nodes, create these aliases:

Click User name and password and specify the credentials to use as the Administrator user name and password for the Platform Managers that will be installed on the remote nodes.

If you are installing on Windows systems, click User name and password and specify the credentials for the Windows installation user account you created earlier.

If you are installing on UNIX systems, click User name and password or SSH private key as appropriate and specify the credentials for the UNIX installation user account you created earlier.

Note:
Note that Command Central supports only the PKCS #1 definition of the ASN.1 syntax for representing the SSH private keys.

3. Develop and register micro templates for layers that install products, install fixes, and create database components. For instructions, see the template instructions in this help. Micro templates are intended to be modular and reusable; when you create an instance of a layer for a stack, you will be able to override template parameters and customize them for that stack.

4. Create definitions of layers to use in stacks using the methods below. A software stack must have at least one Infrastructure layer and at least one Runtime layer. When you create a layer instance for a stack, the layer definition will show micro template values by default, and you will be able to override these values.

Use basic layer definitions provided by Software AG. You can use these definitions as they are or you can customize them. Basic layer definitions are available at https://github.com/SoftwareAG/sagdevops-templates.

Go to Environments > ALL > Instances > CCE > Command Central Server > Configuration > Layer Definitions, click the plus icon

, and provide the requested values.

5. Go to Views > Stacks and click the plus icon

. Add the stack and then add layers. At the end of the wizard, provisioning begins automatically.

6. If one or more of your products require a license key, do the following:

a. Go to Environments > All > Instances and click the instance or component that requires the license key.

b. Click Configuration, click Licenses, click the license key, click Edit, and click the license key to use.

7. If any product you installed or instance you created has a default password, change that password as soon as possible using the instructions in Administering Software AG Products Using Command Central.

8. Connect the products to their database components using the instructions in the installation guide for your products.

9. For additional actions you can take with product installations, see the topics for managing existing standalone product installations.