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

    Configuring Alma and Primo to Use Your Institution-Specific Alma Domain

    Translatable

    Updating Alma Configuration and Bookmarks

    To ensure that all access points to your current Alma URL are updated and accessing your institution-specific Alma domain, it is important to update all users, configuration elements, and applications that access Alma directly.

    Update Bookmarks for Staff and Integrating Systems

    Depending on your Alma implementation, not all of the below may be used.
    # Description Details
    1 Browser bookmarks (HTTPS) All staff accessing Alma and logging in to Alma should update their browser bookmarks with the institution-specific <Alma domain>, where university is replaced with your actual domain. For instance, https://university.alma.exlibrisroup.com.
    APAC customers should use the accelerated Alma domain (HTTP/S). This domain name has the suffix -a added after the university name. For instance:
    https://university-a.alma.exlibrisgroup.com</alma>. For details, see Your Alma Domain Names.
    2 Identify provider IdP - authentication systems (Shibboleth/LDAP/CAS) Ensure that IdP systems are prepared to allow the institution-specific <Alma domain>.
    3 Self-check machine(s) Reconfigure a self-check machine to point to the institution-specific <Alma domain> to test instead of the instance-based previous domain (such as na01.alma.exlibrisgroup.com). Once confirmed, update all self-check machines to point to the institution-specific <Alma domain>. APAC customers should use the <Alma alternate domain> instead of the accelerated Alma domain. For details, see Your Alma Domain Names.
    4 OCLC Connexion Update the OCLC Connexion staff client to the institution-specific <Alma domain> from the previous instance-based domain for one staff workstation. Once confirmed, update all staff workstations to point to the institution-specific <Alma domain>. APAC customers should use the <Alma alternate domain> instead of the accelerated Alma domain. For details, see Your Alma Domain Names.
    5 Z39.50 and OAI-PMH providers Update bookmarks of harvesters to the institution-specific <Alma domain> for Z39.50 and OAI harvest calls. APAC customers: Z39.50 - should use the <Alma alternate domain> instead of the accelerated Alma domain; OAI-PMH - should use the accelerated domain (HTTP/S). For details, see Your Alma Domain Names
    6 Resource sharing Reconfigure third party resource sharing clients/vendors (such as OCLC/NRE) to point to the institution-specific <Alma domain>. APAC customers should use the accelerated Alma domain (HTTP/S). For details, see Your Alma Domain Names
    7 Direct link resolver calls Any integrating system that may directly invoke Alma’s Link Resolver services should update their bookmarks to: <Alma Delivery Domain>. APAC customers should use the accelerated Alma delivery domain (HTTP/S). For more information on this domain, see Your Alma Domain Names.
    As some of the integrations above may involve a third party other than your own library/institution changing a bookmark/URL, it is recommended that you contact any such third parties and coordinate the domain change with them.
    • This domain change does not affect the third party.
    • APAC customers should use the accelerated Alma domain for production only. The sandbox does not support the accelerated Alma domain.

    Updating Primo Configuration

    Primo Back-Office Setup for the Institution-Specific Alma Domain

    The Alma-specific relevant setup in Primo includes four definitions: Alma, RTA, and API on the institution’s Delivery Base URLs page, as well as the PDS/authentication setup in Primo that determines which Alma to authenticate against for any internal users (typically the vast minority of users) in your organization.
    Delivery Base URLs
    For detailed information on configuring the Alma, RTA, and API delivery base URL fields, see Configuring the Primo Institution.
    PDS: If PDS is set up in Primo to direct calls to Alma for authentication (for instance, for internal/staff users for testing), the PDS setup domain parameters need to be adjusted to point to the institution-specific <Alma domain> (see Your Alma Domain Names).
    [AUTHENTICATE]
    program = dps.pl
    params = university.alma.exlibrisgroup.com,443,BOR_AUTH,Y
    [END]
    [BOR_INFO]
    program = dps.pl
    params = university.alma.exlibrisgroup.com,443,BOR_INFO,Y
    [END]
    • Was this article helpful?