Downloading Xi Software from the Customer Portal

Download Portal Access

Xi Software distributions are available through the customer portal:

Portal URL: https://product-management.xisl.com/login

One portal now covers licensing and software downloads together. It replaced two separate sites, and the former download address downloads.xisl.com was retired at the changeover and redirects to the portal, so an old bookmark still reaches the right place.

Access is by account, not by serial number. Sign in with your Xi account reference and the email address held on your account; the portal emails a six-digit one-time code to that address, and entering the code completes the sign-in. There is no password to remember.

Builds and licence codes are released together, on one condition, applied per registered system: the system is active (Xi has confirmed its registration), the account is not on credit hold, and a current support contract covers that serial. When any of the three does not hold, the portal withholds the build list and the licence-code button together and names the reason on that system. Where no support contract has ever been recorded against the account, the portal serves the account as it did before contracts existed.

Product manuals are the exception: they are offered for any product you are entitled to, whether or not a contract is current.

What's Available

Latest builds only

The portal lists the newest build of each package. There is no version history page.

Builds for your registered systems

Files are listed under each registered system, and only files matching the platform recorded for that system are offered.

RPM packages (Red Hat family Linux)

Native package format for RHEL and the distributions binary-compatible with it.

Debian packages (Debian)

Native .deb package format.

Tarball archives (Unix and Linux)

tar.gz archives with an interactive installer script.

Graphical front end

Where one is built, the GUI ships as a separate package alongside the main one, marked with a +gtk3 component in its name.

Product manuals

The current Administration, User, Reference and API manuals as PDFs, listed separately from the builds.

No checksum and no signature is published. The portal shows each file's name, and its date when you hover over it; it publishes no SHA-256 digest, and the RPM and Debian packages are not GPG-signed. Integrity rests on the HTTPS session you download over, so do not expect rpm -K to report a signature check.

Accessing Downloads

Step 1: Sign in

Visit https://product-management.xisl.com/login and enter your account reference and the email address held on your account.

Step 2: Enter the code

The portal emails a six-digit sign-in code to that address. Enter it to sign in. For security the form does not reveal whether an account or an email address exists, so an unrecognised entry produces the same response as a recognised one.

Step 3: Find your system

Your entitlements are shown as serial-number panels. Expand a serial to see the systems registered against it. Each active system shows the platform captured for it, the blend it runs, and the builds available for that platform, newest first.

Step 4: Check the file before you take it

Read the file name and confirm four things: the product, the blend, the version, and the platform. The list is filtered to your system's platform, so the platform is generally right; the blend is not filtered. See the versioning article for how to read each field of a distribution file name.

Step 5: Download

Click the file name. The file is served from the signed-in session. Manuals are listed under a separate Documentation heading on the same system.

If your account is entitled to a custom blend, read the blend field. The portal offers builds for every blend the account is entitled to, standard included, so a blend customer's list contains standard builds as well as their own. Installing the wrong one puts the product in a different set of directories, and a package manager will not move a system from one blend to the other afterwards.

Distribution Types

RPM Packages (Red Hat, Rocky, Alma, CentOS)

Example:

xibatch-standard-1.9.0+1782482597-x86_64-linux-rockylinux9.rpm
xitext-standard-1.25.2+1782476379-x86_64-linux-rockylinux9.rpm

Older files carry an earlier naming scheme; both appear on a download list, and the versioning article covers how to read either.

Features:

• Native RPM package management
• Dependencies declared in the package and checked at install time
• Integrated file permissions
• Clean uninstallation
• A 45-day trial licence written during installation

Supported platforms:

• Red Hat Enterprise Linux (RHEL) 7, 8, 9, 10
• Rocky Linux, AlmaLinux and CentOS of the same release families

Packages are built on one distribution per release family, and the family is binary-compatible: a package built on Rocky 9 installs on RHEL 9, AlmaLinux 9 and CentOS Stream 9 alike. The distribution named in the file name is the one the build was made on, not a restriction on where it runs.

Debian Packages (Debian)

Example:

xitext-standard-1.25.2+1782476379-x86_64-linux-debian13.deb

Features:

• Native Debian package management
• Dependencies declared in the package
• Clean uninstallation
• A 30-day trial licence written during installation

Supported platforms:

• Debian 11, 12 and 13

Tarball Archives (Unix and Linux)

Example:

x86_64-linux-rockylinux9-xibatch_legacy-standard-1.9.0+1782482597.tar.gz

Tarball names put the platform first, where the package formats put the product first. Again, see the versioning article.

Features:

• Includes INSTALL and DEINSTALL scripts
• An interactive installation, answered at the terminal
• The route for platforms with no native package format
• A 45-day trial licence written during installation

Supported platforms:

• Solaris 10 and 11 on SPARC, Solaris 11 on x86_64
• AIX 7.1, 7.2 and 7.3 on POWER
• HP-UX 11.23 and 11.31 on Itanium, HP-UX 11.23 on PA-RISC
• Linux, where a native package is not wanted

These are the platforms the portal supports, which is a wider list than the builds published at any moment. Builds for the proprietary Unix platforms are produced on request rather than with every release, so a supported platform may show no file. Ask support for one.

Platform Selection Guide

Red Hat family Linux (RHEL, Rocky, Alma, CentOS)

Use the RPM package for your release family.

Debian

Use the Debian package for your release.

Ubuntu and SUSE

Both can be registered as systems, but no build is published for either. Contact support.

HP-UX

Use the Itanium or PA-RISC tarball matching your hardware.

AIX

Use the POWER tarball.

Solaris

Use the SPARC or x86_64 tarball matching your hardware.

ARM-based systems

aarch64 can be registered, and builds for it are not currently published. Contact support.

Xi Software builds are platform-specific, and the portal lists only files matching the platform captured for a registered system. If the platform shown against your system is wrong, the registration needs correcting by Xi - the platform fields cannot be edited.

After Download

Confirm the file:

Check the name for the product, blend, version and platform you intended, then check the size is plausible for a distribution rather than an error page. No published checksum exists to compare against.

Extract tarball (if applicable):

gunzip -c x86_64-linux-rockylinux9-xibatch_legacy-standard-1.9.0+1782482597.tar.gz | tar xf -
cd xibatch_legacy-standard-1.9.0/

The archive extracts to a directory named for the product, blend and version. The build reference is not part of the directory name. Decompressing in a separate step keeps the command working on Solaris, AIX and HP-UX, whose tar has no -z option; on Linux tar xzf is equivalent.

Run installer (tarball):

cd xibatch_legacy-standard-1.9.0/
sudo ./INSTALL

Install RPM (if applicable):

sudo rpm -ivh xibatch-standard-1.9.0+1782482597-x86_64-linux-rockylinux9.rpm

Install Debian package (if applicable):

sudo dpkg -i xitext-standard-1.25.2+1782476379-x86_64-linux-debian13.deb

Accessing Older Versions

The portal lists only the newest build of each package for each platform and blend, and no policy states how long an older build is retained. Keep your own copy of the file you deployed - that is the only guaranteed way to reinstall exactly what is running.

To ask for an older build:

1. Contact Xi Software support
2. Give the product, the platform, the blend, and the version - or better, the build reference from the file name of the build you are running
3. Support will supply the file or a direct link if it still exists

Support for Download Issues

Cannot sign in

The account reference and the email address must both match the account record. The code is sent only to the address on file. Contact support to change the address or reset the account.

"Licence codes cannot be generated and downloads not available"

The portal names the reason next to that message - a support contract that has ended, an account on credit hold, a system Xi has not yet confirmed, or a system that has been retired. Contact your account manager.

No builds listed for a system

Nothing is currently published for that system's platform. Contact support to request a build.

Platform shown against the system is wrong

Platform fields are set at registration and are read-only. Contact support; a change of machine means registering the new one and taking new licence codes.

Downloaded the wrong blend

A blend-entitled account sees standard builds as well as its own. Check the blend field in the file name before installing.

Download interrupted

Sign in and start the download again.

Contact support@xisl.com for download assistance.