Configure Cora SeQuence applications

V9.6.1

Overview

You can now configure the Cora SeQuence applications with an XML Document Transformation (XDT) that transforms any Cora SeQuence application configuration files. The Cora SeQuence applications are either services or sites.

You might often want to change some settings in the services and sites config files based on the host environment. For example, you may want to change the app settings, connection strings, or security settings. XDT transformations help to change the existing settings and also helps to add new settings during deployment.

Configurations may include tokens that need to be replaced while transformation. For more details, see the Tokens section in this article.

You can create and apply your custom configurations in the application config files or apply predefined configurations with the Set-CoraSeQuenceApplicationConfiguration PowerShell function. With this function, you can also apply various customizations on pre-built applications without the need of building custom applications.

Configure applications using predefined configurations

Each Cora SeQuence application comes with a predefined configuration. To fetch this predefined configuration for an application, you can use the following GET commands:

• Get-CoraSeQuenceService: For service applications
• Get-CoraSeQuenceSite: For site applications

Both the commands return a collection of properties in a single property called CoraSeQuenceProperties.

In the Configurations property in the config files, you can add various available configurations and their required tokens.
For example:

$flowtime = Get-CoraSeQuenceSite -SiteType Flowtime
$flowtime.CoraSeQuenceProperties.Configurations

To filter a configuration and find its required tokens you can use the Where-Object command and then select the Tokens property. 

For example:

$flowtime.CoraSeQuenceProperties.Configurations | Where-Object -FilterScript { $_.Configuration -eq "SAML" } | Select-Object -Property Tokens

The ConfigurationName parameter accepts a string array so you can apply multiple configurations in one go. The configurations are applied in the same order as they are listed in the parameter.

For the list of all the predefined configurations packaged with the Cora SeQuence applications, see this article.

Create custom configurations

You can set the ConfigurationLocation attribute to create your own custom configuration and customizations for the applications. The ConfigurationLocation parameter contains the XDT files with matching names and relative paths for the configuration files that you want to modify in the target application.

For example,

• to apply configurations and customizations to the Flowtime application, add your updated XDT config file to the ConfigurationLocation root folder.  
• for customized Workflow Explorer create the path Shared Resources\Components\WorkflowExplorer\Config and place an XDT file of the name WorkflowExplorer.config.

For your custom configurations and customizations, you can create fixed values or use tokens.

Using the tokens

Tokens in the configuration files start with a prefix #{ and end with a suffix }#. As part of the transformation, the system automatically replaces the Tokens with the values taken from the environment variables of the host.

You can also provide tokens as a hashtable in the TokenValues parameter. The system considers the token value in the TokenValues parameter above the value set in the environment variables.
The token value is set as an empty string if you do not provide any value in the environment variables or the TokenValues parameter.