Reading the configuration

Out of the box the runtime uses an embedded cloudconfig server to retrieve the values of property files.
This server reads all property files it finds in the assigned folder, and the runtime asks the server for the value of the property it needs.

If you wish to run the cloud config server on its own, that is also possible. In a cloud environment you want to be sure that all nodes run under the same configuration so that the all show the same behavior. Having a local configuration on each node is difficult to maintain as any change to the configuration should be made to the configuration of each node at the same time. Therefore it is better to lead each node read the configuration from one central position. This is what the spring cloudconfig server can do.
To accomplish this, some changes must be made:

• In the bootstrap.properties you must place the url to reach the server (example:spring.cloud.config.uri=http://ipadress:portnumber)
• Add the following annotation on the standalone config server:

@Configuration
@EnableAutoConfiguration
@EnableConfigServer
public class Application {

public static void main(String[] args) {
         SpringApplication.run(ConfigServerApplication.class, args);
         }
}

Also see: Reading properties from file system [editor]

Creating documents

To generate a document the runtime uses an IBEX renderer. This renderer requires two adjustments by the customer before being usable.

(1) No physical paths can be used in a cloud environment. Therefore, the folder containing the xsl files (required to generate documents) must be inside the WAR. To do this you must unpack the WAR and add the folder to the WEB-INF/classes/ folder inside the unpacked WAR and repack the WAR.
When doing so, the property blueriq.documents.base-folder must be given the value "classpath:/", using this value the runtime uses the documents folders inside the WAR.

(2) The IBEX renderer also uses windows fonts when creating a pdf-A file. These fonts also should not be read from the file system, as they might be missing on one of the cloud nodes. It is not possible for us to include these fonts due to copyright limitations. Therefor, it is required for customers to add them to the WAR themselves. To do this the WAR has to be unpacked and the windows fonts should be added to the WEB-INF/classes/ folder inside the unpacked WAR and repack the WAR.

Usage of exports

When using the spring cloud config server embedded, all the exports can be placed in the exports folder in the aquima.home folder.
However if config server is running standalone, these exports must be explicitly named with the full path to each file in the application.properties file.
Resulting in a line like: blueriq.exports.files=D:\exports\example.zip, D:\exports\example2.zip, etc.
These exports must be on the same server as the runtime is running on.

Git

The spring cloud config server reads its values from file system (possible on one central location). It is possible to stop using files on the filesystem, and read property files out of git. This has advantages also the properties are version managed using a standard approach.
To be able to do this, these change have to be made:

bootstrap.properties - for using the file system

spring:
   profiles:
      active: native
   cloud:
      config:
         server:
            native:
                   searchLocations: file:D:/local-properties

bootstrap.properties - for using GIT - basic authentication

spring:
    cloud:
       config:
           server:
               git:
                  uri: https://git.blueriq.com/config-repo.git
                  basedir: target/config
                  username: <git_username>
                  password: <git_password>

Changes in the future

We foresee these changes for the future, but can not indicate the version in which they will be released.

The development plugin cannot write in property files that are read out of GIT. This is something will not be changing. However this results in the fact that the development plugin can only read properties, and this changes its usage. Either the development plugin, or the compatibility with GIT based property storing will be changed.

Currently static resources are not managed by the spring cloud config server (for example frontend sources and exports). When spring cloud config server manages those as well, they can be versioned using GIT.