Azure Submission Data Storage Service

   Journey Manager (JM) Previously known as Transact Manager (TM). |   System Manager / DevOps |   v20.05 This feature was updated in v20.05.

Manager provides the Azure submission data storage service to persist form submissions and related transactions in the AzureMicrosoft Azure is a cloud computing service created by Microsoft for building, testing, deploying, and managing applications and services through Microsoft-managed data centers. Cloud Storage. The service requires an Azure service connection to connect to the cloud using the Azure Key Vault service.

This service is the default submission data storage service for Azure cloud installations. For more information, see the installation guide.

Note

Cloud specific services and some service connections are not available and can't be manually created, unless the deployment environment matches your installation mode.

To check the installation mode of your Manager server, select System > System Info, find the Build Properties section, and check the deployment.env value. For more information, see system info.

Manager's implementation of an Azure service caches a connection to the Azure cloud service for 5 minutes to improve server performance, reduce network bandwidth, and prevent unnecessary load on the systems. However, if an error occurs when configuring the storage service, there may be a delay up to 5 minutes once the problem is rectified for the changes to have effect.

To create the Azure submission data storage service:

  1. Select Services > Core Global Services and click New.
  2. Select Submission Data Storage from the Service Type dropdown list.
  3. Select Azure Submission Data Storage from the Service Template dropdown list.
  4. Provide a unique service name in the New Name field.
  5. Specify a version in the Version Number field.
  6. Select an organization from the Organization dropdown list.
  7. Click Save to update the changes.

To configure the Azure submission data storage service:

  1. Select Services > Core Global Services.
  2. Locate the Azure Submission Data Storage service and click Edit.
  3. Click the Service Definition tab to configure the service.
  4. Select the Azure Storage service connection from the Service Connection dropdown list, which the service will use to publish the events to. Alternatively, click the Edit link to configure the selected service connection.
  5. Click Save to update the changes.
  6. Click the Parameters Edit tab to configure the service parameters used for encryption key management. For more information, see Microsoft Azure documentation.
  7. Select a submission data encryption mode from the Encryption Mode dropdown list, which can be Local, or Azure.
  8. Provide a key vault client id in the Key Vault Client ID. field.
  9. Enter a key vault client secret in the Key Vault Client Secret field.
  10. Specify a key vault master key mappings as JSONJSON (JavaScript Object Notation) is a syntax for storing and exchanging data and is used in Maestro to store forms. If a Form Builder wants to transfer their form to another system, they can do so by using the Download JSON file button. document in the KeyVault Master Key Mapping field.
  11. Enter a key vault tenant id in the Key Vault Tenant Id field.
  12. Click Save to update the changes.
Note

For AWS installations, check the Amazon Submission Data Storage service that persists form submissions and related transactions.

Next, learn how to view all core global services.