Configuration Files

After deploying the application, you can configure it by uploading configuration files in the Configuration section. Admin role is required to upload these files.

Required configuration files

License file

The license file is required for the tests to run.

You can upload the license file in the Configuration section. This is a one-time upload and the license file will be stored in the database. To replace the file later, upload a new version via Configuration.

The file will be provided by Synpulse and it is usually named ast.license.

Global settings file

The global settings file configures the Avaloq business user. This file is required for the tests to run.

This file can be provided by Synpulse and it is usually named ast.globalsettings. You can upload the global settings file in the Configuration section. This is a one-time upload and the global settings file will be stored in the database. To replace the file later, upload a new version via Configuration.

Example of the content of the global settings file:

# ###########################################################
# AST Global Setting File
#  
# $Id$
# ###########################################################

# ###########################################################
# AST
# ###########################################################

ast_user1 = avaloq
ast_user2 = avaloq
ast_bu1 = AAA
ast_bu2 = AAA



# ###########################################################
# 
# ###########################################################

Properties file

The properties file is mainly used for configuring the connection to the Avaloq. This file is required for the tests to run.

This file can be provided by Synpulse and it is usually named ast.properties. You can upload the properties file in the Configuration section or mount it as a volume or secret in the deployment.

When uploaded via Configuration, the file is stored in the database. To replace it later, upload a new version via Configuration.

When mounted, the application reads it from the mounted path (see Deployment).

Example of the Avaloq connection in properties file:

avq.conn.INSTANCE_DEV.host = 100.10.10.20
avq.conn.INSTANCE_DEV.port = 1523
avq.conn.INSTANCE_DEV.sid = sid
avq.conn.INSTANCE_DEV.user = k
avq.conn.INSTANCE_DEV.password = password

avq.conn.INSTANCE_PROD.host = 100.10.10.21
avq.conn.INSTANCE_PROD.port = 1523
avq.conn.INSTANCE_PROD.sid = sid
avq.conn.INSTANCE_PROD.user = k
avq.conn.INSTANCE_PROD.password = password

Info

The INSTANCE_DEV and INSTANCE_PROD are names which will be shown in the application when you select the Avaloq instance to run the tests against. You can change these names to whatever you want, but make sure that the names are unique and do not contain spaces.

Optional files

Report template files

Upload of these files is optional as default templates are provided. The report template files (report_template_for_html_report.xslt and report_template_for_excel_report.xls) are used for customizing the content and format of Excel reports and HTML reports. For more information on report customization, see the Reports documentation. You can upload the report template files in the Configuration section.