Install Command Central
The target machine must have:
At least 5GB of disk space, 2GB of RAM, and 4 CPU cores for
Command Central.
An additional 50G if you are going to use
Command Central to install your products, install fixes on your products, or upgrade your products.
Access restricted to only
Command Central users.
Access to product host machines.
The target operating system must be among those listed in
System Requirements for Software AG Products. Windows operating systems must have the latest Windows updates. In particular, installation on Windows 8.1 and Windows Server 2012 R2 will fail if Microsoft update KB2919355 from April 2014 is not present.
Command Central must be the only product in the target installation directory, so you can easily upgrade
Command Central even when not upgrading your products.
1. On Windows, create an installation user account with Windows system administrator privileges. On UNIX, create a non-root installation user account with full read and write permissions to the target installation directory. The account will own all files you install.
3. Log on to the target machine under the account you just created.
4. The installation process produces many messages. To capture all messages, either increase your buffer or send the output to a file by specifying > bootstrapper.out on the command below.
5. Follow the instructions in your installation email from Software AG to download the Command Central bootstrapper for your operating system.
Note:
Software AG refreshes the bootstrapper with new fixes. Always use the latest bootstrapper to install Command Central.
Note:
If you download the UNIX bootstrapper and then transfer it to another machine, set the transfer tool you are using to binary mode.
6. Launch a command shell. On Windows, launch using Run as Administrator.
7. Run the .exe or .sh script. The basic command using default values is shown below, where --accept-license means you accept the Software AG product license.
cc-def-release-fixnumber-operating_system.{exe|sh} --accept-license
The following table shows arguments you can specify on the command to override the default values.
Note:
Make sure to run the bootstrapper .exe or .sh script using the privileges or permissions stated earlier. On Windows, if you do not run the .exe under a user account with system administrator privileges, the console window will close automatically and you will not be able to see output describing success or errors, nor will you be able to see -help output.
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. In a production environment, Software AG strongly recommends replacing the default with a strong, custom password. | manage |
-p sudo_password | On UNIX, sudo password to use to register daemons for Command Central and Platform Manager. Note:
You can register daemons at a later time by re-running the bootstrapper with this argument. | |
8. After installation is complete, Command Central is running and ready for use. Write down theCommand Central URL and authentication credentials that are listed in the shell so you can log on.
Note:
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. To install new fixes later, get the latest bootstrapper for the same Command Central release and run it against the existing Command Central installation.
9. Secure access to the Command Central using instructions in this help. 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:
cc-def-10.3-fix1-w64.exe -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-fix3-lnxamd64.sh
cc-def-10.2-fix3-lnxamd64.sh -d /opt/sagcc -H cchost.com -c 9090 -C 9091
-s 9092 -S 9093 -p $uperCCAdm1n --accept-license