Skip to end of banner
Go to start of banner

Vega - ECS requests, Mediated requests, Secure requests deployment

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Back-end

Some BE modules only need to be enabled in some tenants:

  • mod-tlr - Central tenant only

  • mod-requests-mediated - Secure tenant only

Environment variables

mod-inventory-storage

Name: ECS_TLR_FEATURE_ENABLED , value: true.

edge-patron

Name: SECURE_TENANT_ID , value: secure tenant ID.

Potential Liquibase issues

If you’re deploying mod-tlr from scratch, there shouldn’t be any issue, but if you upgrade it from an older version, you might encounter an issue with Liquibase checksums. In order to fix you should clean Liquibase tables in mod-tlr’s DB as well as drop mod-tlr’s own tables:

delete from {TENANTID}_mod_tlr.databasechangelog;
delete from {TENANTID}_mod_tlr.databasechangeloglock;
drop table {TENANTID}_mod_tlr.ecs_tlr;
drop table {TENANTID}_mod_tlr.tlr_settings;

Front-end

Add new variable enableEcsRequests: true, to platform-complete → stripes.config.js → config.

Secure tenant

Secure tenant is a non-central tenant that will be used for handling secure requests.

It should be a separate tenant with the property security=true set as described here MGRTENANT-32 - Getting issue details... STATUS

As mentioned in the Back end section, in LoC-like environments, Secure tenant should be the only one where mod-requests-mediated module is enabled.

Manual set-up after deployment

  • Allow TLR in all tenants (Settings → Circulation → General)

  • Enable ECS TLR feature in the central tenant (Settings → Circulation → General)

  • Optionally, check manually that the feature has been enabled in both mod-tlr and mod-circulation-storage:
    GET /tlr/settings
    GET /circulation-settings-storage/circulation-settings

  • No labels