| Excerpt | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Changes
| Jira Legacy | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Additionally, in dcb-service
v4.3.x
Cluster management
Use hazelcast to maintain a map of DCB nodes which are reported back in the info endpoint
Evict member info if we detect a node is no longer present. Trialling leader election for cluster operation
Add the node start date and if the node is running scheduled tasks to the cluster information shared via hazelcast. Subsequently, these should now appear in the app info endpoint giving the admin app visibility of all DCB nodes.
Reference hazelcast in ingest service ready for FencedLock integration
FOLIO
Polaris
Add defensive code to make sure items array length > 0
Use patron home location for item location when creating an item
Logging and error checking:
Add patron request id to create item command for more useful logging in failure scenarios
Request and Circulation workflow: NA
GraphQL: NA
Sierra: NA
Miscellaneous
Additionally, in dcb-admin-ui
NA
Deployment
Summary
Environments to deploy to:
Integration
Beta
Change Category | Required | Recommended | Not Required |
|---|---|---|---|
Complete reset | |||
Environment configuration |
| ||
Host LMS configuration or setup | |||
Service configuration | |||
Ingest | |||
Index | |||
Library configuration | |||
Deploy new Executables |
|
Instructions
Verification
After clear down
After deployment
4