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

    Exporting/Importing the Full Configuration

    This functionality is not relevant to to Primo VE.
    When exporting the full configuration to another Primo environment, it is necessary to perform additional steps and checks in each environment before and after running the export/import tools.
    To create and execute the import/export tools, users must be assigned one of the following roles:
    • Superadmin – Installation and institution levels for on-premises customers.
    • Admin – Installation and institution levels for on-premises customers.
    • Admin – Institution level for Cloud customers.

    Before Running the Export Tool

    These steps should be run before executing the export tool on the source server.
    Perform the following steps on the source server:
    1. Make sure that nobody is working on the system.
    2. Perform a deploy all on the source server.
    3. Make sure that no processes are running.
    4. On the Primo Home > Primo Reports reports page, run the General Parameters report and then export the report to a file to be used on the target server. This is necessary because general parameters are not included in the full configuration export.
    5. Create and execute/schedule the export tool. For more information, see The Export Primo Configuration Tool.

    Before Running the Import Tool

    These steps should be run before executing the import tool on the target server.

    These steps are not relevant to customers in a hosted multi-tenant environment.

    Perform the following steps on the target server:
    1. For classic UI only, enter the following commands to back up custom files under the fe_web directory on the FE server:
      fe_web
      tar czf <your_customer_code>_customization_bck_<todays_date>.tar.gz css/static_htmls/images/help/
    2. If you developed your own OvP adaptor, enter the following commands to back up the gateway XSL directory:
      fe_profile
      tar czf <your_customer_code>_gateway_bck_<todays_date>.tar.gz gateway/

      This step is necessary only when customizations have been made to .JSP files.

    3. Enter the following commands to back up the PDS configuration. The location of the PDS configuration can vary. Contact your PDS consultant for more information.
      pdsroot
      cd ../
      tar czf <your_customer_code>_pds_bck_<todays_date>.tar.gz pds/
    4. Make sure that nobody is working on the system and that no process will run during the import.
    5. Perform a deploy all on the target server.
    6. On the Primo Home > Primo Reports reports page, run the General Parameters report and then export the report to a file for backup.
    7. Create and execute/schedule the export tool. It will be used as a backup if the import fails. For more information, see The Export Primo Configuration Tool.
    8. Review the Primo Version 4.X - Known Issues document.
    9. After the export tool has completed successfully, create and execute/schedule the import tool. For more information, see The Import Primo Configuration Tool.

    After Running the Import Tool

    These steps should be run after executing the import tool on the target server.
    Perform the following steps on the target server:
    1. If you developed your own OvP adaptor, copy the XSL from the source server to the target server. The files are stored under the fe_profile/gateway directory.

      For n-Tier topologies with multiple FEs, copy the files to each FE and BE. This step is not relevant to customers in hosted multi-tenant environments.

    2. In the Primo Back Office, use the Institution Wizard to verify the institution’s configuration and populate the following fields, which are blank after an import:
      • PC key and customer ID
      • bX Token
    3. In the Primo Back Office, use the Views Wizard to reconfigure the following fields if the paths for the sandbox and production environments are different:
      • Update the Static HTML paths to point to the production versions.
      • Change the CSS option to the production version.
      • Check the value of the Session timeout URL field to see that it is correct.
    4. On the Primo Home > Schedule Tasks page, enable any scheduled tasks that may have been disabled in the sandbox environment.
    5. Restart all FE servers to rebuild the entries in the Deploy Targets table.
    6. Perform a deploy all on the target server.
    7. On the Primo Home > Advanced Configuration > General Configuration Wizard page, use the report that was exported from the source server to reconfigure the general parameters, which are not included in the export.
    8. If you customized any Primo files in the source environment, copy them to the target environment.
    9. Run the UPDATE pipes (or INITIAL pipes if no data was loaded in the target server).
    10. Run the Indexing and Hotswapping process.
    • Was this article helpful?