Initializing help system before first use

Manual Installation

In the unlikely event that the provided installers fail to function correctly, the software can be extracted manually.

To perform a manual installation on Windows, you must have a program capable of uncompressing zip files. WinZip or WinRar are suitable, although any program with this functionality should work.

Unix and Linux variants should by default contain the necessary programs to unzip and extract from the tar archives. If you do not have an extraction program, you will need to install one. If this is the case and your previous attempt at automatic installation using the install script failed, then the lack of an extraction program may be the cause. In this case, install the required tools and attempt an automatic installation again.

The differences between the automatic and manual installation methods are as follows:

  • Files are not installed selectively as the whole archive will be uncompressed.
  • Not all environment variables are automatically set.
  • The dongle driver installation will not be run automatically (Windows).
  • The file shortcuts will not automatically be added to the Start menu (Windows).
  • The XPserver license manager will not be automatically configured to run as a service.

Manual Microsoft Windows Installation

Should the InstallShield installation fail, the files may be extracted using any program capable of reading and extracting from zip files as follows:

  1. Rename the downloaded installation file extension from .exe to .zip.
  2. Extract the files from the zip file to the folder from where you want to install.
  3. Copy your license file in to the bin folder of the installation directory. If you are working with a Community License, rename or copy the provided file community-xpauth.xpr to xpauth.xpr.
  4. Read the license.txt file in your installation folder and make sure you agree with the terms and conditions. (If you do not agree, then cancel the installation and delete the software.)
  5. Add the XPRESSDIR environment variable and point towards the xpressmp folder of the installation directory. You can set this by going to the Start menu » Settings » Control Panel » System » Advanced » Environment Variables, and creating a new environment variable. Use the full path.
  6. Add the path %XPRESSDIR%/bin to the PATH environment variable. (This allows the system to find the relevant Xpress libraries and executables.)
  7. To add links to the programs on the Start menu, select Start menu » Settings » Taskbar and Start Menu. Click on the Start Menu tab and click Customize.
    Click Add. The Microsoft Windows wizard will display so that you can add the programs to the Start menu. You may want to add optimizer.exe and xpworkbench.exe as basic links, although a number of other executables are available. (See the bin folder in the installation directory.)
    If you installing a floating server license, you need only add links to XPserver.exe, or the configuration batch file runlmgr.bat.
  8. If you installing a floating server license, you can delete all files and folders except the following:
    • xpserver.exe in the bin folder.
    • xphostid.exe in the bin folder.
    • xplicstat.exe in the bin folder.
    • xprl.dll in the bin folder.
    • runlmgr.bat in the bin folder.
    • The tools folder, if you require dongle licensing, from the main Xpress folder.
    • License.txt from the main Xpress folder.
    • The licensing folder from the docs folder.
  9. If you are going to use dongles for licensing, then install the dongle drivers found in the tools\dongle\hasp directory of your Xpress folder. Use a Windows console as it requires the addition of command-line arguments. You can open a Windows console by running cmd using the Start » Run menu. See Dongle Licenses (for Microsoft Windows Machines) for more information.
  10. Set up the XPserver license manager. See FICO Xpress Licensing for instructions.

Manual Linux/Unix Installation

As mentioned previously, if the installation fails, it is likely that there was a problem using the standard zip and tar programs. If this is not the case, then you can manually install the software by following these steps:

  1. If you have not done so, untar the downloaded installer (if you have attempted to install via the automated install script then you have already performed this step). This command extracts the files from the tar archive:
    tar xf name_of_downloaded_installer.tar
  2. The extracted files include the installation script install.sh. Move the .gz file to the directory where you want to install the software.
    Decompress the .gz file using the following command:
    gunzip name_of_gz_file.gz
  3. The preceding command extracts another tar archive which itself contains the installation files and may be unarchived using the following:
    tar xf name_of_new_tar_file.tar
  4. The installation directory should now contain several directories of files and several license and html files. Read the license files and make sure you agree with the terms and conditions; if you do not agree to them, delete the software and discontinue the installation.
  5. Copy your xpauth.xpr license file to the bin directory of the Xpress installation. If you are working with a Community License, rename or copy the provided file community-xpauth.xpr to xpauth.xpr.
  6. Set the relevant environment variables so that your system can find the Xpress executables, runtime libraries and license file. For example, on a Linux system using the C shell:
    setenv XPRESSDIR your_xpress_install_directory
    setenv PATH $XPRESSDIR/bin:$PATH
    setenv LD_LIBRARY_PATH $XPRESSDIR/lib:$LD_LIBRARY_PATH
    setenv CLASSPATH $XPRESSDIR/lib/xprs.jar:$CLASSPATH
    setenv CLASSPATH $XPRESSDIR/lib/xprb.jar:$CLASSPATH
    setenv CLASSPATH $XPRESSDIR/lib/xprm.jar:$XLASSPATH
    setenv XPRESS $XPRESSDIR/bin
    The name of the environment variable used to find shared libraries varies by system; on Linux and Solaris it's usually LD_LIBRARY_PATH and on macOS you should use DYLD_LIBRARY_PATH instead. If unsure, consult your system administrator.
    You may find it useful to create a small shell script that sets these variables, or to set them in a script that runs automatically as you log in.
  7. If you plan to use the xssh: protocol to connect to a Mosel optimization service running from this installation of FICO Xpress, execute the following commands to generate a unique machine key:
    cd $XPRESSDIR/bin
    ./xprmsrv -key new
  8. If you are performing a Linux installation and require the use of dongles for licensing, install the dongle drivers now. See Dongle Licenses (for Linux Machines).
  9. If you are installing a floating server license, you only need a few of the files and can remove the rest. You must keep the following files in order for the XPserver license manager to function correctly:
    • xpserver in the bin directory.
    • xplicstat in the bin directory.
    • runlmgr in the bin directory.
    • All files which begin with libxprl in the lib directory.
    • The licensing directory in the docs directory.
    • xphostid in the utils directory.
    • license.txt from the main Xpress installation directory.
  10. To setup the XPserver license manager, follow the instructions as described in FICO Xpress Licensing.

© 2001-2020 Fair Isaac Corporation. All rights reserved. This documentation is the property of Fair Isaac Corporation (“FICO”). Receipt or possession of this documentation does not convey rights to disclose, reproduce, make derivative works, use, or allow others to use it except solely for internal evaluation purposes to determine whether to purchase a license to the software described in this documentation, or as otherwise set forth in a written software license agreement between you and FICO (or a FICO affiliate). Use of this documentation and the software described in it must conform strictly to the foregoing permitted uses, and no other use is permitted.