Installing Apama using Command Central

You can provision new and update existing Apama environments using Software AG Command Central. You can do this on any machine on which Platform Manager is running. You can then invoke the Software AG Installer or Software AG Update Manager directly from Command Central and do silent installations and uninstallations of the Apama product and its product fixes.

This topic just provides a brief overview of how to install Apama using Command Central. For detailed information, see the Command Central documentation at http://documentation.softwareag.com/ (Empower login required).

1. Install a Command Central server, install Software AG Platform Manager (SPM) on any machine on which you want to install Apama, and make sure the Command Central and Platform Manager servers/services have been started. The simplest way to do this is to use the Command Central bootstrapper. Configure each SPM instance as an installation in the Command Central server. See Software AG Command Central Help for more details.

Tip: The default credentials for a new installation are "Administrator" for the user name and "manage" for the password.

2. Configure a repository for the Apama product (using either the web user interface or the sagcc command line interface). To do so, you can either create credentials in the Command Central server using your Empower credentials and then define a repository using the credentials, or use a locally generated image.

3. Install Apama and apply the latest fixes using one of the following options:

Using the Command Central web user interface. See Software AG Command Central Help for information on how to install products.

Using the Command Central templates as described at https://github.com/SoftwareAG/sagdevops-templates/tree/master/templates/sag-apama-correlator. This template creates a single correlator. The correlator is configured to use a license if Command Central has been given an appropriate license.

Unlike using the Software AG Installer, Command Central does not lay down a license that all correlators will automatically pick up. If you are not configuring licensing for each correlator individually, ensure that a license is available in APAMA_WORK/license/ or APAMA_HOME/etc/.

Note: The Command Central installation uses the default location of the Apama work directory. On Windows, this is in the all-users %PUBLIC% directory (for example, C:\Users\Public\SoftwareAG\ApamaWork_n.n) and on UNIX this is ~/softwareag/apamawork_n.n.