Create a Software Stack

To watch a video that shows how to create a stack with layers and use the stack to create product installations, click https://www.youtube.com/watch?v=spAZk9SUe-c&feature=youtu.be.

Command Central can automatically install Platform Manager automatically in the new product installation. To do so, Command Central uses the Command Central bootstrapper. Follow the instructions in your installation email from Software AG to download the bootstrapper of the new release for your operating system, and then store the bootstrapper in the Command Central_directory/profiles/CCE/data/installers directory.

If the user account created to install products does not allow remote access from Command Central, you will need to manually install Platform Manager on target nodes using the instructions on installing Platform Manager using the Command Central bootstrapper in this help. 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 aliases for 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 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. 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. See the micro template instructions in this help.

4. Create definitions of layers to use in stacks using the methods below. At minimum, 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. For instructions and locations, see instructions on connecting to the default templates repository in this help.

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

, and provide the requested values.

5. Go to Stacks, hover over the the plus icon

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

6. 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.

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

8. For additional actions you can take with product installations, see the topics for managing existing standalone product installations in this help.