Journey Manager (JM) The transaction engine for the platform. | System Manager / DevOps | 23.10This feature was updated in 23.10
Manager provides a functionality enabling you to quickly and easily reconfigure a server instance by uploading a configuration file containing all relevant information. The configuration file is a JSONJSON (JavaScript Object Notation) is an open standard file format and data interchange format that uses human-readable text to store and transmit data objects consisting of attribute–value pairs and arrays. file with a flat structure defining server's properties as name / value pairs. The Configuration Service consumes this file and runs all configuration tasks that it defines. However, the Configuration Service can't create new configurations; it can only update the existing ones. That is, the Manager instance has to be installed and configured prior to be able to use the Configuration Service.
The Configuration Service comes with several template files, which you can use to create your own configuration deployments. As you upload the JSON configuration file, the Configuration Service parses it and runs import operations for each section of configuration, such as form spaces, organizations, forms, service connections and so on. This means that you need to have correct import permissions assigned to your account.
You can upload and deploy the Configuration Service file using one of following options:
Let's look at each of them in more detail.
To upload and deploy a Configuration Service file via Manager:
The Journey Manager SDK Maven plugin provides the tm-sdk:configuration-service-archive-deploy goal to upload and deploy a Configuration Service file.
The Journey Manager REST API provides the endpoint URL to upload and deploy a Configuration Service file.
To call this REST API, you need:
http(s)://<JM_SERVER>/manager/secure/rest/configuration-service/v1/
--header ‘Authorization: Basic <USE-NAME-AND-PASSWORD-BASE64-ENCODED>’
- an HTTP header containing 'username:password'
encoded as base64.
--form ‘archiveFile=@“/Users/my-configuration-service-v2.0.json”’
- a path to a Configuration Service file to be uploaded and deployed.
--form ‘importOptions=“CLIENT_PROPERTIES,PORTAL_PROPERTIES,FORM_PROPERTIES,SERVICE_PARAMETERS”’
- a comma-separated list of import options to perform. The option names are the same as described in the Deploy Using UI section but they use an underscore, for example, DEPLOYMENT_PROPERTIES
for Deployment Properties.
200 OK
status code.
{
“archiveName”: “config-service.json”,
“importMessage”: “Configuration Service archive/file config-service.json was imported. Number of successful changes: 11 .“,
“importStatus”: “Completed”,
“importTime”: “2024-02-07T10:28+1100"
}
example with warnings
{
“archiveName”: “my-configuration-service-v2.0.json”,
“detailMessages”: [
“Portal not found : [Work Space]“,
“Service definition for service name [Amazon Submission Data Storage] not found”,
“Service definition for service name [Amazon Submission Data Storage] not found”,
“Service definition for service name [Amazon Submission Data Storage] not found”,
“Service connection for service connection name [Amazon KMS] not found”
],
“importMessage”: “Configuration Service archive/file my-configuration-service-v2.0.json was imported. Number of failed changes: 5 . Number of successful changes: 11 .“,
“importStatus”: “Completed”,
“importTime”: “2024-02-06T14:38+1100"
}
curl --location --request PUT ‘https://<JM_SERVER>/manager/secure/rest/configuration-service/v1/’ \
--header ‘Authorization: Basic <USE-NAME-AND-PASSWORD-BASE64-ENCODED>’ \
--form ‘archiveFile=@“/Users/my-configuration-service-v2.0.json”’ \
--form ‘importOptions=“CLIENT_PROPERTIES,PORTAL_PROPERTIES,FORM_PROPERTIES,SERVICE_PARAMETERS, \
CLIENT_SERVICE_PARAMETERS,SERVICE_CONNECTIONS,CLIENT_SERVICE_CONNECTIONS,DEPLOYMENT_PROPERTIES,CLIENT_PAYMENT_GATEWAY”’
Next, learn how to create a server node.