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

    Importing MetaLib QuickSets to Primo

    With Primo version 4.2 and later releases, you can use the script to import MetaLib QuickSets to Primo. This script creates a personal set for all QuickSets in every Primo institution linked to the exported MetaLib institutions. If a single MetaLib institution is linked to mutliple Primo institutions, a set will be created for each.
    It is possible to run the export/import multiple times. The script only adds new databases, and will not override existing sets.
    To import MetaLib QuickSets to Primo:
    1. Run the export script in MetaLib.
      For more information, see the MetaLib System Configuration and Administration Guide.
    2. If the tar files have not been copied from the MetaLib server, FTP all of the files that were exported on the MetaLib server to the Primo Back Office server. The files should be added to a directory that the Primo import script can read.
    3. On the Back Office server, enter the following commands to access the mquicksets directory:
      cd mquicksets
    4. Add the following parameter to the file.
      source_path – The full path of the qs_exports directory.
      For example:
    5. Enter the following command to open the hibernate.cfg.xml file:
      vi hibernate.cfg.xml
    6. Modify the following lines in the file:
      <property name="hibernate.connection.url">jdbc:oracle:thin:@{hostname of DB server}:{DB port}:{SID}</property>
      <property name="hibernate.connection.username">{oracle login}</property>
      <property name="hibernate.connection.password">{oracle password}</property>
      For example:
      <property name="hibernate.connection.url">jdbc:oracle:thin:@il-primo12:1521:prm2</property>
      <property name="hibernate.connection.username">P42_PRM00</property>
      <property name="hibernate.connection.password">P42_PRM00</property>
    7. Save the changes to the file.
    8. Enter the following commands to perform the import:
      By default, the script’s output displays on the screen. It is possible to redirect the output to an output file by using the following command: > output.txt &]]