Skip to main content
ExLibris
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    Manually Installing the SP

    This section contains the steps needed to download, distribute, and install the SP files manually on your Primo system.
    After you have downloaded the installation files from the FTP server, the installer still requires access to the Ex Libris FTP server to download additional information (such as third-party updates).
    Repeat the following steps for each Primo machine and copy. Run all steps as the primo user and make sure that you install the SP on the machine that contains the Back Office (BE) application first.
    If your Primo topology includes a dedicated DB server, do not install the SP on that server.
    To install the SP manually:
    1. Log on to the server as the primo user.
      If your server has more than one copy of Primo, the system prompts you to select a copy.
    2. Enter the following command to change to the Primo software directory, where <v> is the Primo version in which Primo was first installed and <x> is the Primo copy:
      cd /exlibris/primo/p<v>_<x>
    3. Create the SP installation directory if it is not already created.
      mkdir service_pack_install
    4. Enter the following command to move to the service_pack_install directory:
      cd service_pack_install
    5. Enter the following commands to download the SP files from the FTP site, where <v> is the Primo version of the SP, <r> is the minor release, and <u> is the SP number. When prompted, use primo4_sp for the user and 4pgrade for the password.
      ftp ftp.exlibrisgroup.com
      bin
      prompt off
      mget PRIMO-<v>.<r>-ServicePack-<u>.tar.gz *
      quit
      If you have multiple Primo copies on your server, you can just copy the SP files directly from your server.
    6. If the SP is split into multiple files, which is indicated by the suffix on the file name (such as _aa, _ab, and so forth), enter the following command to combine all of the files into a single gz file:
      cat PRIMO-<v>.<r>-ServicePack-<u>.tar.gz_* > PRIMO-<v>.<r>-ServicePack-<u>.tar.gz
    7. Enter the following command to extract the files from the tar file:
      gzip –dc PRIMO-<v>.<r>-ServicePack-<u>.tar.gz | tar -xvf -
    8. The Primo server supports three Primo Application Roles: BE (Back Office), SE (Search Engine), and FE (Front End). Enter the following command to determine which types are supported on this Primo server:
      echo $APP_ROLE
      Make sure that you update the server that contains BE first.
    9. Enter the following commands to stop the Primo Apache server:
      apcb
      ./apachectl stop
      If the Apache server is not running, you will see and can ignore the following error message:
      ./apachectl stop: httpd (no pid file) not running
    10. Stop all Primo servers (be_stop, fe_stop and/or se_stop), as determined by the roles (BE, SE, and FE) supported on this server. For example, if the Primo server supports the BE, FE, and SE roles, enter the following commands:
      be_stop
      fe_stop
      se_stop
      For sites using a multiple FE configuration, you must stop the BE server before stopping the FE servers.
    11. Enter the following command to return to the SP installation directory, where <v> is the Primo version in which Primo was first installed and <x> is the Primo copy:
      cd /exlibris/primo/p<v>_<x>/service_pack_install
    12. Enter the following command to install the SP:
      ./sp.install
      For non-active BO servers in a multiple BO configuration, use the following command instead:
      ./sp.install -i
      After the server checks some conditions (such as database access is available and Primo servers are down), the following message displays:
      You are about to install Primo Service Pack <v>.<r>.<u>
      Are you sure you want to continue? Y/[N]
    13. Enter Y to continue.
      The installation utility runs all mandatory implementation scripts automatically. They will take less than 5 minutes to complete. When complete, the following message displays:
      The Service Pack was installed successfully.
      The Service Pack utility - sp.utility - can be found on /exlibris/primo/p<v>_<x>/service_pack/sp.<v>.<r>.<u>
      Do you want to run it now? Y/[N]
    14. If you would like to run the manual implementation scripts now, enter Y. Otherwise, enter N and run them later using the sp.utility command. See Using the SP Utility.
      To determine which implementation scripts, if any, require you to run them manually, review the Release Notes and run the scripts that apply to your configuration. See Release Notes for more information.
    15. If you are skipping Primo version 4.5 (for example, if you are upgrading from v4.4.1 to v4.7), open a new shell session when the upgrade process has finished in order to execute the updated startup scripts that are used in the remaining steps. Otherwise, continue to the next step.
    16. Start all Primo servers (be_start, fe_start and/or se_start), as determined by the roles (BE, SE, and FE) supported on this server. For example, if the Primo server supports the BE, FE, and SE roles, enter the following commands:
      be_start
      fe_start
      se_start
      To prevent a startup failure, start the FE server before the SE server.
    17. If the Apache server was stopped in step 7, enter the following commands to restart the Primo Apache server:
      apcb
      ./apachectl start
      When port 80 is configured, you must use the following commands as the root user to start the Apache server:
      cd /exlibris/primo/p<v>_<x>/primoe/apache/bin
      ./apachectl_auto
    18. If you need to conserve disk space, you can remove files under the following directory, but you will need to download the SP if you decide to roll back the SP and re-install it:
      /exlibris/primo/p<v>_<x>/service_pack_install
      Do not remove files in the /exlibris/primo/p<v>_<x>/service_pack directory.
    19. From the Primo Back Office home page, click Deploy All to complete the installation.