Skip to main content
Version: 2.0

Static Configuration

Static configuration is the microservice configuration set before microservice startup in a property file. This configuration is common to all tenant.

Static configuration for Order service is :

NameTypeDefault ValueDescription
regards.order.secretstringuse to generate auth token to use on order endpoints
regards.order.max.storage.files.jobs.per.userinteger2Max number of concurrent storage files retrieval jobs per user
regards.order.client.response.batch.sizeinteger1000Max bulk size of AutoOrderEvent managed in a row
regards.order.cancel.request.bulk.sizeinteger1000Max bulk size of OrderCancelEvent managed in a row
regards.order.request.bulk.sizeinteger1000Max bulk size of OrderRequestEvent managed in a row
regards.order.batch.sizeinteger10000Page size of the search request generated (destinated to rs-catalog)
regards.order.basket.upload.file.max.linesinteger1000Max number of provider ids of uploaded file (see basket upload file api)
regards.order.files.bucket.size.Mbinteger100Max size of files to retreive in a single storage job (single suborder)
regards.order.clean.expired.rate.msinteger3600000 (1h)Frequency of check order expiration.
regards.order.computation.update.rate.msinteger1000 (1s)Scheduled method frequency to update all current running orders completions values and all order available files count values into database
regards.order.periodic.files.availability.check.croncron0 0 7 * * MON-FRI (every working day at 7 am)Frequency of sending email to users, for remind that some orders are waiting for him
info

Some of these properties are customizable in ansible inventory. see installation guide. link

To make missing properties customizable, you have to update regards ansible playbook : the regards-mconfig role.