Guide for keeping LDP software current for LDP Production Environments
1. How to Get Support for running the LDP software
· use the LDP documentation (admin and user guides) posted on GitHub at https://github.com/library-data-platform/ldp/tree/main/doc
· post questions to the #devops channel on the Metadb/LDP Slack
2. There are 3 Components of the LDP Software, each with separate release schedules
· LDP - https://github.com/library-data-platform/ldp/releases
· ldpmarc - https://github.com/library-data-platform/ldpmarc/releases
· folio-analytics - https://github.com/folio-org/folio-analytics/releases
· The milestones for folio-analytics are posted here - https://github.com/folio-org/folio-analytics/milestones
3. Consider What Versions of the LDP Components to install
· See the Library Data Platform section of the FOLIO documentation, which includes a recommendation matrix for the 3 components by FOLIO release
· In general, install the latest production release for each component of the LDP software. The LDP and ldpmarc software components do not have a dependency on FOLIO (flower release) software versions, but the folio-analytics software component is intended to be used with specific FOLIO releases - https://github.com/folio-org/folio-analytics#releases
· It is safer to install only releases (tags) and to read the release notes and make adjustments to your environment if necessary
· Do not install beta versions in production environments, as they need to be tested before they are used in production
LDP1 Production Support Troubleshooting Checklist
Error logs
- Ask for EBSCO error log
- Ask if verbose logging can be turned on (takes longer for data transfer)
Daily Data Transfer Logs
- review how long each part of the data transfer took
- compare data transfers between days
- compare data transfers between Test and Production instances
LDP1 System Configuration Settings
LDP Production
- current software versions
- data transfers for LDP (component), ldpmarc, and folio analytics running sequentially
- statement_timeout = 7200000 parameter for postgres
- ldpmarc update set to -full
- ldpmarc verbose logging off
- LDP (component) verbose logging off
- recording history disabled
LDP Test
- current software versions
- data transfer runs first for LDP (component), then ldpmarc and folio analytics run in parallel
- data transfers for LDP, ldpmarc, and folio analytics running sequentially
- statement_timeout = 7200000 parameter for postgres
- ldpmarc update set to -full
- ldpmarc verbose logging off
- LDP (component) verbose logging off
- recording history disabled