Installing Applications

Applications are available for download as RPM package files from the Customer Portal. These files can then be downloaded and installed on the Application Server using the Yum Package Manager and then installed across all Application Server components using the Application Manager.

Pre-Installation Checklist

  • The Application Manager must be installed and configured as described in Installing Evolve IMSWorkX Application Manager.

  • If doing an offline installation, perform the following steps:

    1. Run the xpressworkx_app_manager prepare offline command.

    2. Copy the identified, required RPM dependencies to the NIUs, including the epel-release and python-pip packages.

    3. Install these RPMs manually on both the NIU and AS using yum install.

    4. On the NIU, run the touch /etc/yum.repos.d/epel.repo command to create an empty epel.repo file.

    5. Copy the required python dependencies to /root/python_dependencies.

Install an Application

  1. Access the Customer Portal.

  2. Log in with your provided Username and Password.

    _images/LogIn.png

  3. Click Software Downloads on the portal’s main menu.

    _images/SoftwareDownloads.png

  4. Locate the application package in the software list.

    _images/AllDownloads.png

  5. Click the link to download the file.

  6. Log in as root on the primary NIU of the Application Server.

  7. If needed, transfer the downloaded RPM package file to the NIU.

Tip

You can use the xpressworkx_app_manager version command to verify that you are using the latest available version of the Application Manager.

  1. Run the yum install <filename> script with the name of the RPM file to unpack the application package on the NIU for that Application Server. The application package will register with the Application Manager so that the application can be installed on the Application Server.

  2. Run the xpressworkx_app_manager install <shortname> <version> command with the application short name and version number to install the application on the NIU.

Note

The Application Manager will automatically push the application to each AS that is registered and the secondary NIU.

The installation is finished when the Complete! message appears on the command line.

The application must be started using the Console or by configuring it to automatically start in the Application Server’s ps_master_config.xml file. For more information, see the Application Server User’s Guide and the specific application User’s Guide for additional configuration requirements.

If another AS is added after installing an application, you can use the xpressworkx_app_manager synchronize command at any time to move the application to the new AS.