Installer functions

This section describes functions you can perform with the installer.

Display command

The display command lists information about all installed products. The command is named display.bat on Windows and display.sh on UNIX and Linux. Run it from the root installation directory.

When run without parameters, the command lists all installed products and versions and all applied service packs.

Use the name parameter to display the installation history of a single product. For example:

display -n <product name>

Install product

To start the installer to install a product:

Locate and run the setup file in the root folder of the installation package you downloaded from the Axway support site and uncompressed or unzipped.

GUI mode

  • setup32.exe or setup64.exe

Console mode

  • setup32.exe -m console or setup64.exe -m console

setup32.exe is a 32-bit build executable and will run on a 64-bit platform provided that the compatibility layer has been installed.

Windows installations

The same user that did the initial installation (or at least the same type of user) must start the installer.

Services modification

Some products support an installation in service mode with a user other than the default (Local System Account).

If the domain field is not shown in the products service configuration dialog, then it must be introduced in the username field, using this format:

<domain>\<username>

If it is a local user (a user that was created on the local machine) then the <domain> field can be . or the <hostname>.

Example

Local user: user1

.\user1

<hostname>\user1

Network user: user2

<domain_name>\user2

Configure product

This section describes running the installer in configure mode to change a product's configuration.

The following describes running the installer in configure mode.

GUI mode

  • In the Windows Start menu, select Axway Software > Axway [installation name] > Configure

Console mode

  • configure32.exe –m console
  • configure64.exe –m console
Note If you do not want to use either the GUI or console modes to configure your installation, refer to the Silent mode.

About host name

Host name corresponds to the object assigned to a physical server. In the installer, host name is required for the following reasons:

  • In a license key page, to validate that the entered key matches the host name. In this case, enter only the host name (without the domain name) and make sure not to confuse Hostname with Logical Server Name.
  • In a page where you configure which network interface the product is going to listen for an incoming connection. In this case, enter one of the following values:
    • Host name
    • The fully qualified name (host name and domain name)
    • IP address of the machine
    • Specific string (0.0.0.0 or *) indicating that you want the product to listen on all network interfaces if your machine has more than one
    • Logical host name or IP address if you are doing an installation on a machine that is part of a cluster
  • In a page where you configure how your product is going to connect to another product. In this case, it is strongly recommended to use either the fully qualified name or the IP address of the remote machine. If the remote machine you are connecting to is a cluster, then use the logical, fully qualified cluster host name or IP address.

Using a temporary directory

The installer needs a temporary directory when it starts to unzip and prepare the environment it requires for product or update installation. The temporary directory it uses is the first %TMPDIR%, %TMP% or %TEMP% environment variable that is not null. It is very important that the value of the variable does not contain any spaces. If it does, a NullPointerException java error occurs.

You can force the use of another temporary directory by setting the following environment variable, TEMPORARY_DIR.

If you do this make sure the temporary directory has:

  • Enough disk space
  • Read/write access for starting the installer

Installation modes

You can use the following installer installation modes.

  • GUI mode is supported on Windows, UNIX and Linux. However, to use on UNIX platforms, the installer requires an X-Window environment. To use an X-Window distributed environment, you must export the DISPLAY environment variable: export DISPLAY=myhost.mydomain:0.0 
  • Console mode displays a series of prompts requiring user responses or actions.
  • Silent mode enables you to perform an installation or configuration in a non-interactive mode. You do not have to enter any parameters in the GUI or console.

Installer functions

The installer command files are for invoking installer functions in GUI or console mode.

Before installing, install is the only available function, invoked with the setup file in the root directory of the installation package.

After installing, the configure, update and uninstall functions are available. The scripts for those functions are in the root installation directory.

Function

Mode

Windows

Install

GUI

setup32.exe

setup64.exe

Console

setup32 –m console

setup64 –m console

Configure

GUI

configure32.exe

configure64.exe

Console

configure32.exe –m console

configure64.exe –m console

Update

GUI

update32.exe

update64.exe

Console

update32 –m console

update64 –m console

Uninstall

GUI

uninstall32.exe

uninstall64.exe

Console

uninstall32.exe –m console

uninstall64.exe –m console

The configure function lets you change settings that were applied during installation.

The update function lets you apply or remove service packs and patches.

After installing the following functions are available:

  • Install product
  • Configure product
  • Update product and Remove updates
  • Uninstall product
  • Transfer installation packages on remote machines

Related Links