Investigate using a different RM API Endpoint for status checks

Priority

Environment

None

Template

None

Description

mod-kb-ebsco-java makes requests to the following HoldingsIQ endpoint when checking status of the HoldingsIQ backend

vendors?search=zz12&offset=1&orderby=vendorname&count=1

This accesses a vendors endpoint. Investigate using a different endpoint for back end status checks. This endpoint was unavailable during a recent outage. Investigate if a different endpoint should be used for status checks

Confirmed with HoldingsIQ team that – GET /{custid} would be a better choice since endpoint is hosted in AWS.

It was also noted that access to this endpoint will contribute to requests per day allocated per customer. Additionally determine if there is any ways to minimize the number of calls made to this endpoint (checks on front end for calls made to status endpoint)

Development Team

Spitfire

Release

None

Story Points

Sprint

relates to

Checklist

hide

TestRail: Results

Activity

Show:
Done

Details

Assignee

Reporter

Fix versions

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created February 21, 2020 at 9:33 PM
Updated March 20, 2020 at 1:32 PM
Resolved March 20, 2020 at 1:32 PM
TestRail: Cases
TestRail: Runs

Flag notifications