Documents plugin setup

Search…
The plugin is available as a docker image.
It has the following dependencies:
a postgres database
a mongodb database in case the html templates feature is needed
needs to be able to connect to the Kafka instance used by the engine
a redis instance for caching 
an S3 compatible file storage solution (we have successfully used Min.io)
The plugin comes with most of the needed configuration properties filled in, but there are a few that need to be set up using some custom environment variables.
Dependencies
Postgres database
Basic Postgres configuration - helm values.yaml
1
documentdb:
2
  existingSecret: {{secretName}}
3
  metrics:
4
    enabled: true
5
    service:
6
      annotations:
7
        prometheus.io/port: {{phrometeus port}}
8
        prometheus.io/scrape: "true"
9
      type: ClusterIP
10
    serviceMonitor:
11
      additionalLabels:
12
        release: prometheus-operator
13
      enabled: true
14
      interval: 30s
15
      scrapeTimeout: 10s
16
  persistence:
17
    enabled: true
18
    size: 4Gi
19
  postgresqlDatabase: document
20
  postgresqlUsername: postgres
21
  resources:
22
    limits:
23
      cpu: 500m
24
      memory: 512Mi
25
    requests:
26
      cpu: 200m
27
      memory: 256Mi
28
  service:
29
    annotations:
30
      fabric8.io/expose: "false"
Copied!
Redis server
The plugin can use the Redis component already deployed for the engine.
Document storage
You need to have an S3 compatible file storage solution deployed in your setup.
Configuration
Authorization configuration
The following variables need to be set in order to connect to the identity management platform:
SECURITY_OAUTH2_BASE_SERVER_URL
SECURITY_OAUTH2_CLIENT_CLIENT_ID
SECURITY_OAUTH2_REALM
Enable html template types
In case you want to use html templates for documents, you need to override the following config by setting the FLOWX_HTML_TEMPLATES_ENABLED environment variable to true.
Datasource configuration
To store data related to document templates and documents the service uses a Postgres / Oracle database.
The following configuration details need to be added using environment variables:
SPRING_DATASOURCE_URL
SPRING_DATASOURCE_USERNAME 
SPRING_DATASOURCE_PASSWORD
You will need to make sure that the user, password, connection link and db name are configured correctly, otherwise you will receive errors at start time.
The datasource is configured automatically via a liquibase script inside the engine. All updates will include migration scripts.
Database schema is managed by a liquibase script that will create, manage and migrate future versions.
MongoDB configuration
The only thing that needs to be configured is the DB access info, the rest will be handled by the plugin. 
SPRING_DATA_MONGODB_URI - the uri for the mongodb database
Redis configuration
The following values should be set with the corresponding Redis related values. 
SPRING_REDIS_HOST
SPRING_REDIS_PASSWORD
REDIS_TTL
All the data produced by the service will be stored in Redis under a specific key. The name of the key can be configured using the environment variable:
SPRING_CACHE_REDIS_KEY_PREFIX
Kafka configuration
The following Kafka related configurations can be set by using environment variables:
SPRING_KAFKA_BOOTSTRAP_SERVERS - address of the Kafka server
SPRING_KAFKA_CONSUMER_GROUP_ID - group of consumers
KAFKA_CONSUMER_THREADS - the number of Kafka consumer threads
KAFKA_AUTH_EXCEPTION_RETRY_INTERVAL - the interval between retries after AuthorizationException is thrown by KafkaConsumer
KAFKA_MESSAGE_MAX_BYTES - this is the largest size of the message that can be received by the broker from a producer.
Each action available in the service corresponds to a Kafka event. A separate Kafka topic must be configured for each use-case.
The Engine is listening for messages on topics with names of a certain pattern, make sure to use correct outgoing topic names when configuring the documents plugin.
File storage configuration
Based on use case you can use directly a file system or an S3 compatible cloud storage solution (for example min.io).
The file storage solution can be configured using the following environment variables:
APPLICATION_FILE_STORAGE_S3_SERVER_URL
APPLICATION_FILE_STORAGE_S3_ACCESS_KEY
APPLICATION_FILE_STORAGE_S3_SECRET_KEY
APPLICATION_FILE_STORAGE_S3_BUCKET_PREFIX
Make sure to follow the recommended bucket naming rules when choosing the bucket prefix name.
The maximum file size allowed for uploads can be set by using the SPRING_SERVLET_MULTIPART_MAX_FILE_SIZE & SPRING_SERVLET_MULTIPART_MAX_REQUEST_SIZE variables.
Custom font path for docx templates
The following config needs to be set in order to choose the font to be used when generating documents based on docx templates: FLOWX_PDF_GENERATION_FONT_PATH
Custom font paths for html templates
In case you want to use some specific fonts in your html templates, you need to override the following config: FLOWX_HTML_TEMPLATES_PDFFONTPATHS
If you don't override FLOWX_HTML_TEMPLATES_PDFFONTPATHS, you have Calibri and DejaVuSans as default fonts that you can use.
After making this configuration, these fonts will become available to be used inside the html template.
Logging
The following environment variables could be set in order to control log levels:
LOGGING_LEVEL_ROOT - root spring boot microservice logs
LOGGING_LEVEL_APP - app level logs
LOGGING_LEVEL_MONGO_DRIVER - mongo db driver logs