Date: Tue, 19 Mar 2024 05:32:59 -0400 (EDT) Message-ID: <950006515.8765.1710840779836@lyrasis1-roc-mp1> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_8764_1134540120.1710840779836" ------=_Part_8764_1134540120.1710840779836 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Title (Goa= l) |
As a reposito= ry manager, I want to change which web service implements an API extension = by pointing to a new address |
Primary Ac= tor |
Repository Manager |
Scope |
|
Level |
|
Author |
Aaron Birkland= |
Story (A p= aragraph or two describing what happens) |
My institution created a web service and configured the API Extension Architecture to direct requests=
from /path/to/object/viz:nifty to it. The im=
plementing web service is running on one of our backend servers, at http://internal-net-12.example.org:8080/nifty-viz. W=
e need to do some server maintenance on that machine, so we've put a new co=
py of the webapp up at http://internal-net-08.example.org/nifty-viz. We'd l=
ike to configure the API Extension architecture to direct requests to the n=
ew webapp instance, so we can take the old one down. Since this is a produc=
tion system with lots of users, we do not want to have to re-start Fedora o=
r the API Extension architecture. We would like to make a simple configurat=
ion change which causes the API Extension Architecture to immediately start=
sending requests to the new service instead of the old. |
API Extension Architecture's role:
Web application's role:
viz:nifty
=
Repository manager's role:
Fedora's role: