Transfer installation packages on remote machines

To transfer the installation package simultaneously on several remote machines, you can use the Installer's upload feature. The upload feature transfers the installation files to the target machine. After the upload, connect to each remote machine where the package was uploaded and run the installation locally.

There are two ways of performing an upload. Each way depends on the configuration of the remote machine. Here are the differences:

  Kit archived Kit ready
Prerequisites FTP server is mandatory

SSH server is mandatory. It is not recommended to use this feature to upload on Windows machines, as there is no standard SSH server and the feature may throw a random exception.

FTP server is optional. FTP server will provide better transfer time.

Target environment (OS, processor architecture) You must specify the target environment. It can be the local machine. The Installer detects what the target environment is using the ssh connection.
Transferred files An AxwayInstallationPackage is created on the remote machine. A set of archived files, additional files and a ArrangeKit.sh file are sent. An AxwayInstallationPackage directory is created on the target environment. It contains all the necessary files to run the installation on the platform.
Installation

Go to the AxwayInstallationPackage directory created on your remote host.

Execute the ArrangeKit.sh script to uncompress the various transferred files and then run the setup file to start the Installer. You must execute the script from its current location otherwise it will not work.

See the procedure section below for the commands.

Go to the AxwayInstallationPackage directory created on the remote host and start the Installer. See the procedure section below for the commands.
Note   This specific feature can also be used if you want to create an installation package that contains only certain products and then distribute it to your entire network.

When performing an upload, the existence of the directory AxwayInstallationPackage is verified on the target machine:

  • If another version of the Installer is detected on the target machine in the folder AxwayInstallationPackage, an error is displayed and you must change the path in order to continue with the upload.
  • If the target machine has detected the same version of the Installer, the upload continues without any warning or error.
  • If the folder AxwayInstallationPackage already exists but there is no version of the Installer uploaded in this folder, a warning that the folder already exists is displayed.

Connection timeout

This is the amount of time it takes the Installer to return an error if the connection to the remote FTP server is not established. We recommend setting the value for transfer timeout to 300 seconds.

Prerequisites

The uname of the machine must be set with the proper architecture information.

If the uname of the machine is not set, 32-bit is the default. If the architecture is 64-bit there will be an error during installation because the wrong JRE has been uploaded.

Upload procedure

To upload the installation files to the target machine:

Insert the installation package

Insert the installation package and place it on a machine that is in the same network as the target machine or machines.

Launch Installer in upload mode

Run the setup command for your operating system and desired mode.

GUI

UNIX: setup.sh -u -m gui

Windows:

  • setup32.exe -u -m gui
  • setup64.exe -u -m gui

Console

UNIX: setup.sh –u –m console

Windows:

  • setup32 –u –m console
  • setup64 –u –m console

Package options

Temporary directory: Select the local directory where archived files are temporarily stored before transferring. The default is the local temp directory.

Select the Type of the packaging you want to create:

  • Kit Ready (requires SSH): Select this option if you have a SSH server installed on the remote machine. The package is uploaded on the remote host first and then automatically unzipped.
  • Kit Archived: Select this option if you are uploading to a Windows host or to hosts that do not have the SSH protocol installed. The package is only transferred and a file named ArrangeKit.sh (UNIX)/ArrangeKit.bat (Windows) is created.
  • You must manually give execution rights to this file so that you can execute it to automatically unzip the archives.

Transfer configuration

Select the machines you want to upload the installation files to.

  1. Click Add. A blank line is added to the table.
  2. Click a cell to enter general transfer information:
  3. Remote Address: The remote hostname. Files are transferred to this machine.
  4. User: The login used to connect to the remote machine.
  5. Password: The password corresponding to the user.
  6. Target directory: The remote directory where the installation kit will be sent. By default, it is the user's home directory.
  7. When you have finished defining the hosts, click Next.

Depending on the package option you selected, the following information is required.

For Kit Ready

Transfer protocol: The protocol used to transfer files over the network.

  • FTP: Requires FTP in addition the mandatory SSH server.
  • Secure FTP: The transfer is done using the SSH connection. Note: The transfer is much slower.

FTP port: The port used to connect to the FTP server. Fill in this field only if you selected FTP as the Transfer Protocol. The default is 21.

SSH port The port used to connect to the remote SSH server. This port is mandatory, as the SSH protocol is used to perform additional tasks and not only the file transfer. The default is 22.

Connection timeout The delay (in seconds) after which the connection attempt to the remote server will fail. The default is 300 seconds.

For Kit Archived

Transfer protocol: The protocol used to transfer files over the network.

  • FTP: Requires an FTP server on the remote host.
  • Local: Uploads the files to the local machine.

FTP port: For the FTP protocol, you must define the transfer port. The default is 21.

Target environment

  • Select the target machine's system environment in order to create a kit that contains only the necessary installation files.
  • Windows and Linux (x86): If you select the 32/64 bit option, the Installer creates an installation package with 32 and 64 bit binaries. Note that the 64-bit architecture will have a 32-bit compatibility layer.
  • If you select the pure 64-bit option, the creates an Installer installation package with ONLY the 64-bit binary.
  • The platform selection available in the target environment only contains the list of platforms that are supported by a product or products.
  • If you select more than one product for installation, only the environment that is common to both products is available for selection.

Click Add again to add additional machines. To delete a machine, select the row and click Delete. To avoid repetitive server configuration, the load/save process can be used. Save creates a text file with the list of servers. Load fills the table configuration from that saved file.

Upload tasks

Review the products and click Upload to begin transferring.

Summary

Verify the products were successfully uploaded. If errors are listed, check the log for more details:

  • If you launch the Installer from a directory with write permissions, the log file is written in the Components directory.
  • The TEMP directory on Windows could be one of the following environment variables: TMPDIR; TMP or TEMP.
  • The TEMP directory on UNIX or Linux could be one of the following: /tmp; /var/tmp; /usr/tmp; $HOME; $PWD

Click OK to exit the Limitations related to managing Java 7.

After you upload the installation files to the target machine, you can start the Installer and begin the installation process. However, if there are modifications to make before you can start the Installer, verify that you have performed all the steps in the tables above.

Related Links