Install Command Central
You install Command Central using the Command Central bootstrapper. The bootstrapper also automatically installs Platform Manager and the Command Central command line interface (CLI), as well as all fixes that were available for Command Central and the other tools when the bootstrapper was created.
Each time a new fix for Command Central or the other tools is created, the bootstrapper is refreshed to include the new fix. To install new fixes, get the latest bootstrapper for the same Command Central release and run it against the existing Command Central installation. Whenever you install a new Command Central, always use the latest bootstrapper, to get the most recent fixes.
Machines on which you install Command Central need at least 5GB of disk space. Command Central then needs 2GB of RAM and 4 CPU cores to run. If you plan to install products, install fixes, or upgrade products from Command Central, you will need an additional 50GB of disk space. Command Central host machines must have access to the host machines of all products you want to manage. Restrict user access to only those people who need to use Command Central.
Important: Do not install any other Software AG products in the Command Central directory. One reason is to enable you to restrict access. A second reason is that you should upgrade Command Central when new releases come out, even if you are not yet upgrading your products, and keeping Command Central separated from the products makes upgrading it easier.
For supported operating systems and browsers, see System Requirements for Software AG Products.
You can watch a demo relating to this task in the
Command Central area of the Software AG TECHcommunity website at
http://techcommunity.softwareag.com.
Note: To upgrade Command Central and the other tools to a new release, see the upgrade topic in this help.
2. If you are going to install on a Windows system:
Make sure the machine has the latest Windows updates. On Windows 8.1 and Windows Server 2012 R2, installation will fail if the Microsoft update KB2919355 from April 2014 is not present.
Create an installation user account and give the account Windows system administrator privileges. This account will own all files you install.
If you are going to install on a UNIX system, create a non-root installation user account and give the account full read and write permissions to the target installation directory. If you want to register daemons for Command Central and Platform Manager, ask your system administrator for the sudo password. The account will own all files you install.
3. Log on to the target machine under the account you just created.
4. Open your installation email from Software AG and follow the instructions to download the Command Central bootstrapper for the appropriate operating system. If you are installing on a Windows system, extract the ZIP archive to the directory into which you are going to install Command Central.
Note: If you download the UNIX bootstrapper .sh script and then transfer it to another machine, set the transfer tool you are using to binary mode.
5. The installation process produces many messages. To capture all messages, either increase your buffer or send the output to a file by specifying --params > bootstrapper.out on the command below.
6. Open a command window as Administrator for Windows or a shell window for UNIX and run the .bat file or .sh script with the arguments in the table below. Arguments that have defaults are optional.
Argument | Value | Default |
-H host_name | DNS name or IP address for the machine on which to install Command Central. | Machine on which you are running the bootstrapper. |
-d path | Full path to the installation directory in which to install Command Central. | Directory from which you are running the bootstrapper. |
-c port_number | HTTP port to use for Command Central. | 8090 |
-C port_number | HTTPS port to use for Command Central. | 8091 |
-s port_number | HTTP port for Command Central to use to communicate with the local Platform Manager. | 8092 |
-S port_number | HTTPS port for Command Central to use to communicate with the local Platform Manager. | 8093 |
-p password | Password to use for the Command Central Administrator user account. If you are installing in a production environment, Software AG strongly recommends you replace the default with a strong, custom password. | manage |
-P sudo_password | If you are installing on a UNIX system and want to register daemons for Command Central and Platform Manager, the sudo password. | |
--accept-license | Indicates that you accept the Software AG product license. | |
7. After installation is complete, Command Central is running and ready for use. The bootstrapper lists the Command Central URL and authentication credentials in the command or shell window. Note this information so you can log on.
Note: If you did not register daemons when you installed Command Central but want to do so at a later time, you can run the bootstrapper again with the argument -P sudo_password.
8. If the Command Central managing an environment., secure access to the Command Central. This is especially important if you are using the Command Central to manage production environments.
Examples
To install on a Windows system in the c:\sagcc directory and set the password for the
Command Central Administrator user account to $uperCCAdm1n:
unzip cc-def-10.2-fix1-w64.zip
cc-def-10.2-release-w64.bat -d c:\sagcc -P $uperCCAdm1n --accept-license
To install on a UNIX system in the /opt/sagcc directory on the UNIX system cchost.com, set the port values, and set the password for the
Command Central Administrator user account to $uperCCAdm1n:
chmod +x cc-def-10.2-fix1-lnxamd64.sh
./cc-def-10.2-fix1-lnxamd64.sh -d /opt/sagcc -H cchost.com
-c 9090 -C 9091 -s 9092 -S 9093 -P $uperCCAdm1n --accept-license