You are here

SkyVault Process Services 1.6 » Administering SkyVault Process Services

Configuring SkyVault Process Services

Configure SkyVault Process Services using a properties file named activiti-app.properties. This file must be placed on the application server’s classpath to be found.

Additionally, the properties file is available with the following options:

  • An activiti-app.properties file with default values in the WAR file (or exploded WAR folder) under the WEB-INF/classes/META-INF/activiti-app folder.

  • An activiti-app.properties file with custom values on the classpath. For example, the WEB-INF/classes folder of of the WAR, the /lib folder of Tomcat, or other places specific to the web container being used.

The values of a configuration file on the classpath have precedence over the values in the WEB-INF/classes/META-INF/activiti-app/activiti-app.properties file.

For the SkyVault Process Services user interface, there is an additional configuration file named app-cfg.js. This file is located inside the .war file’s script directory.

  • Minimal configuration At minimum, the application requires the following settings to run:
  • General Server settings By default, the following properties are defined for general server that can be modified.
  • Database configuration Set the following properties to change the database.
  • Language Support
  • Configuring CORS To enable Cross Origin Resource Sharing (CORS) in SkyVault Process Services, set the cors.enabled property to true in the activiti-app.properties file.
  • Business Calendar settings Business Calendar is used to calculate relative due dates for tasks. To exclude weekends when calculating a task’s relative due date, set the calendar.weekends property as follows:
  • Initial User Created on First Start Up When the application starts for the first time, it will verify that there is at least one user in the system. If not, a user with superuser rights will be created.
  • Email Server configuration The application sends out emails to users on various events. For example, when a task is assigned to the user.
  • Elasticsearch configuration
  • Application Access and default example app It is possible to configure whether users get access to the model editors (the App Designer application) and the analytics application.
  • Group Manager Involvement When a task is created that has one or more candidate groups assigned, the group managers for those groups will be automatically involved with the created task. To stop group managers from being involved, set the following property to false.
  • Process Definition Cache The Process Engine operates in a stateless way. However, there is data that will never change, which makes it a prime candidate for caching.
  • Content StorageSkyVault Process Services enables you to upload content, such as attaching a file to a task or a form. This content is stored on a disk with the following configuration settings for the path:
  • Microsoft Office integration The Microsoft Office integration (opening an Office document directly from the browser) doesn’t need any specific configuration. However, the protocol used for the integration mandates the use of HTTPS servers by default. This means that SkyVault Process Services must run on a server that has HTTPS and its certificates are correctly configured.
  • Logging back-end metrics The application uses SLF4J bounded to Log4j. The log4j.properties configuration file can be found in the WEB-INF/classes folder of the WAR file.
  • External Identity Management (LDAP/Active Directory) It’s possible to hook up a centralized user data store with SkyVault Process Services. Any server supporting the LDAP protocol can be used. Special configuration options and logic has been included to work with Active Directory (AD) systems too.
  • Integration with external systems You can integrate SkyVault Process Services with external systems.
  • Validator configuration By default, SkyVault Process Services is configured in a way that process modelers have access to all powerful features of the Process Engine. In many organizations this is not a problem, as the people who are modeling are trusted IT people or business analysts.
  • License configuration It is possible to start up the application without a license (it will then enter read only mode) and later upload one from the user interface. See below for settings that apply to that scenario.
  • Multi-schema multi-tenancy (MS-MT) It is possible to run SkyVault Process Services in so-called "multi-schema multi-tenancy" mode (MS-MT). This is a multi-tenant setup, where every tenant has its own database schema. This means that the data of one tenant is completely separated from the data of other tenants.
  • Cross-Site Request Forgery (CSRF) Cross-Site Request Forgery, also referred to as CSRF, is one of the most common form of attacks plaguing web browsers. This type of attack results in a malicious request being submitted on a user’s behalf without their consent.
Parent topic: Administering SkyVault Process Services

© 2017 TBS-LLC. All Rights Reserved.