Before Installing Products

Work with your administrators, Software AG Global Consulting Services, and best practices documentation to plan a production environment.

For information on supported operating systems, see the system requirements for your products.

Important: Command Central does not distinguish among versions (Windows) or flavors (UNIX) of an operating system. Make sure you install products only on the supported versions or flavors listed in the products' system requirements.

For information on product hardware requirements and instructions on preparing the target machines for product installation, see the installation guide for your products.

Open your installation email from Software AG. The email might have these attachments:

License manifest files, identifiable by file names that do not include any product name. Each license manifest file contains all contracts for one location of your organization.

Individual product license key files, identifiable by file names that include product names. Each license key contains the license for a product, a component, or a product feature.

Copy the attachments to a machine that can access the Command Central from which you will install your products and then do the following:

If you have license manifest files, add them to Command Central. Go to Licensing > Manifests, click

, and provide the requested values. Then open each file; if the LicenseManifest Version at the top is 3.0 or higher, license keys are embedded within the file, and you need take no further action.

If you do not have manifest files, or if you have manifest files but they do not contain embedded license keys, add the individual license key files to Command Central. Go to Licensing > Keys, click

, choose the appropriate option, and provide the requested values.

Create an installation user account on each target machine and give the accounts Windows system administrator privileges. This account will own all files you install.

If you are going to install remotely from Command Central on Windows 2008 or higher systems, enable remote access on each target machine using Windows Remote. You must also have Powershell 5.0 or higher and DotNet 4.5 or higher.

1. Open a Powershell window as administrator and run this command:

2. Increase the Powershell script memory by running this command:

3. Adjust your firewall rules to allow access to the HTTP/S ports on which Command Central is listening.

4. Make sure the machines have 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.

Note: You can only install Software AG products on a local hard drive on Windows machines. You cannot install the products on a network-mounted drive.

Create a non-root installation user account on each target machine to own the directory that will contain the product installation, but that otherwise has minimal rights on the target machine. The account must have write and execute access to the target installation directory. The account will own all files you install.

If you are going to install remotely from Command Central, give the user accounts SSH privileges.

If you are going to register a daemon for the Platform Manager on each machine, ask your system administrator for the sudo password.

To avoid problems with shared system resources, run only one installation job at a time on the machines. Make sure the entire product installation is complete before starting any other installation jobs on those machines.

If your temporary directory contains thousands of files, the installation startup process might take one minute or longer. You might see messages about Initializing system resources during this time. If you want to speed up this process, delete the files in your temporary folder.

Only install products from a single release in an installation directory. Do not mix products from different releases in the same installation directory, or you will experience problems and be unable to access functionality.

If you want to use a symlink for the installation directory, you must use the symlink every time you install into the directory. For example, you cannot install some products using a directory name and then later create a symlink and use it to install more products into the same directory, or vice versa.

The installer installs a JDK for the products. Do not apply maintenance updates from the vendor of the JDK. If an update is required, Software AG will provide the update in the form of a fix.

Do not modify or remove files that are installed or created by Command Central when installing products unless specifically instructed to do so by Software AG. Do not modify or remove files from the Software AG_directory/install directory.