Once you have the OpenText Replication Console installed on a Windows machine, you can use it to push the installation out to your other servers. The push installation is a full, client and server installation on Windows servers and a full server installation on Linux servers.
Keep in mind the following items for Windows servers.
-
If you are using the OpenText Replication Console to push installations out to your Windows servers, you will have to open firewall ports for WMI (Windows Management Instrumentation), which uses RPC (Remote Procedure Call). By default, RPC will use ports at random above 1024, and these ports must be open on your firewall. RPC ports can be configured to a specific range by specific registry changes and a reboot. See the Microsoft Knowledge Base article 154596 for instructions. Additionally, you will need to open firewall ports for SMB (server message block) communications which uses ports 135-139 and port 445, and you will need to open File and Printer Sharing. As an alternative, you can disable the Windows firewall temporarily until the push installations are complete.
- Because the installation is pushed to your server using an administrative share, you must perform the installation with a domain administrator account. You will get access denied errors if you are using a local account.
Keep in mind the following items for Linux servers.
- The push installation process uses a combination of SSH (secure shell) and SCP (secure copy) to copy the installation binary files and execute them.
- You can use a non-root user to perform the push installation, as long as the account has sudo permissions to dpkg.
- You can only push the installation process. You cannot push an upgrade.
- If you are installing on Linux servers, you must copy the Linux .deb or .rpm files from your download to a \Linux subdirectory in your OpenText Replication Console installation location. By default the console installation location is \Program Files\OpenText\Replication. Make sure you only have a single version of Linux installation files. The push installation cannot determine which version to install if there are multiple versions in the \Linux subdirectory.
- Add the servers where you want to install OpenText Availability and OpenText Migrate to your console session.
- On the Servers page, highlight all of the servers where you want to install OpenText Availability and OpenText Migrate, and select Install from the toolbar.
- Each source server needs a license key before you can create a job. Target licenses depend on the source license you are using. If you are upgrading and your server already has a license key that is valid for the current version, you can either skip this step to use the existing license key or you can complete this step to replace the existing license key.
- If you have a single license key that can be used on multiple servers, such as a site license or an evaluation key, highlight all of the servers where you want to apply the same license key and click Set License keys. If you have unique license keys for each of your servers, highlight just one server and click Set License keys.
- Type in your license key or click Choose from inventory to open the License Keys dialog box where you can select the license key you want to apply.
- Click OK to configure the installation or upgrade for the selected license key.
- Repeat steps a-c for any additional servers that are using unique license keys.
-
Set your Default Installation Options, which are used for both Windows and Linux installations.
- Activate online after install completes—Specify if you want to activate your OpenText Availability and OpenText Migrate licenses at the end of the installation. The activation requires Internet access from the console machine or the machine you are installing to. Activation will be attempted from the console machine first and if that fails, it will be attempted from the machine you are installing to. If you choose not to have the installation activate your licenses, you will have to activate them through the console license inventory or the server's properties page.
- Location of install folders—Specify the parent directory location where the installation files are located. The parent directory can be local on your console machine or a UNC path.
- Windows—Specify the parent directory where the Windows installation file is located. The default location is where the OpenText Replication Console is installed, which is \Program Files\OpenText\Replication. The console will automatically use the \x64 subdirectory which is populated with the Windows installation files when you installed the console. If you want to use a different location, you must copy the \x64 folder and its installation file to the different parent directory that you specify.
- Linux—Specify the parent directory where the Linux installation files are located. The default location is where the OpenText Replication Console is installed, which is \Program Files\OpenText\Replication. The console will automatically use the \Linux subdirectory, however that location will not be populated with the Linux installation files when you installed the console. You must copy the Linux .deb or .rpm files from your download to the \Linux subdirectory in your OpenText Replication Console installation location. Make sure you only have a single version of Linux installation files. The push installation cannot determine which version to install if there are multiple versions in the \Linux subdirectory. If you want to use a different location, you must copy the \Linux folder and its installation files to the different parent directory that you specify.
-
If you are installing on Windows servers, specify your Default Windows Installation Options.
- Temporary folder for installation package—Specify a temporary location on the server where you are installing OpenText Availability and OpenText Migrate where the installation files will be copied and run.
- Installation folder—Specify the location where you want to install OpenText Availability and OpenText Migrate on each server. This field is not used if you are upgrading an existing version of OpenText Availability and OpenText Migrate. In that case, the existing installation folder will be used.
- Queue folder—Specify the location where you want to store the OpenText Availability and OpenText Migrate disk queue on each server.
- Amount of system memory to use—Specify the maximum amount of memory, in MB, that can be used for OpenText Availability and OpenText Migrate processing.
- Minimum free disk space—This is the minimum amount of disk space in the specified Queue folder that must be available at all times. This amount should be less than the amount of physical disk space minus the disk size specified for Limit disk space for queue.
- Do not use disk queue—This option will disable disk queuing. When system memory has been exhausted, OpenText Availability and OpenText Migrate will automatically begin the auto-disconnect process.
- Unlimited disk queue—OpenText Availability and OpenText Migrate will use an unlimited amount of disk space in the specified Queue folder for disk queuing, which will allow the queue usage to automatically expand whenever the available disk space expands. When the available disk space has been used, OpenText Availability and OpenText Migrate will automatically begin the auto-disconnect process.
- Limit disk space for queue—This option will allow you to specify a fixed amount of disk space, in MB, in the specified Queue folder that can be used for OpenText Availability and OpenText Migrate disk queuing. When the disk space limit is reached, OpenText Availability and OpenText Migrate will automatically begin the auto-disconnect process.
If the servers you are pushing to do not have a C drive, make sure you update the folder fields because the OpenText Replication Console will not validate that the fields are set to a volume that does not exist and the installation will not start.
-
If you are installing on Linux servers, specify your Default Linux Installation Options.
- Temporary folder for installation package—Specify a temporary location on the server where you are installing OpenText Availability and OpenText Migrate where the installation files will be copied and run.
-
Linux installations will occur immediately. If you are installing on Windows servers, specify your Installation Schedule.
- Install now—Select this option to complete the installation immediately.
- Install later—Select this option and specify a date and time to complete the installation.
- Reboot automatically if needed—If selected, the server will automatically reboot after the installation, if a reboot is required. This option applies to the OpenText Availability and OpenText Migrate installation only. It does not apply to the installation of .NET Framework.
- After you have configured your installation options, click Install.
During an upgrade, any existing jobs on the Jobs page may disappear and then reappear. This is expected while certain OpenText Availability and OpenText Migrate files are updated.
If there are errors with the push installation before the installation is executed on the server, check the console log on the machine where you are pushing the installation from. Once the installation execution has started, the installation log will be written on the server where you are installing and then copied back to the console machine. The installation log file will contain the server name, date, and time in the following format: servername YYYY-MM-DD_HH-mm.ss.log. The date and time is when the installation was attempted.
You can set your own default settings for the three default installation sections from the console's Options page. To access these console options, select Options from the toolbar. The defaults you set on the Options page will appear each time you open the Install page. You can then modify any of the settings on the Install page before beginning the installation.
If you want to use your own secure certificate, see the instructions for your operating system.
- Windows—For Windows servers, if you want to use your own secure certificate, you should obtain and install a certificate from an enterprise or commercial Certificate Authority.
- Linux—If you want to use your own secure certificate, you should obtain a certificate from an enterprise or commercial Certificate Authority. Once a certificate is available on your Linux server, you will need to update /opt/dbtk/etc/dtssl.conf with the path and file name of your certificate and the certificate password, if your certificate file has a password. If you want to enable verification, you will need to identify your PEM file or the directory that contains all certificates in the verification chain. See the instructions in the dtssl.conf file. You will be responsible for updating an expired certificate as needed. If you want to revoke a certificate, you must remove it from the server. If a specified certificate is expired or revoked, OpenText Availability and OpenText Migrate will not replicate data.