Azure Client Stack Deployment
CAM Azure Stack utilizes Microsoft Azure services and resources to provide the ability to move documents and content and sync metadata between multiple Document Management Systems (DMS). CAM Content Mover and Data Sync (Content Sync) use Azure storage blobs as an intermediary place while moving content between the supported Document Management Systems.
To deploy the CAM Azure Stack, you need to deploy the Azure template into your Azure environment. The template deploys a complete solution that contains multiple resources such as function apps, MySQL instances, Blob Storages, and others. These resources are provided and hosted by Microsoft Azure in your Azure account to provide more control over moving content.
- 2 Prerequisites to the CAM Azure Stack Deployment
- 2.1 Deploying and Configuring the CAM Azure Stack
- 2.2 Initialize CAM Azure Stack Configuration
- 2.3 Updating the Client Stack
- 2.3.1 Updating MySQL 7 to 8
- 2.3.2 Prerequisites
- 2.3.3 Executing the Script
- 2.3.3.1 Azure login:
- 2.3.3.2 Resource group Input:
- 2.3.3.3 Function App Identification:
- 2.3.3.4 Logging:
- 2.3.3.5 File Management:
- 2.3.3.6 Upgrading Jar Files:
- 2.4 Configure CAM Content Mover to Utilize your Azure Stack
- 2.5 Configure CAM Data Sync to Utilize your Azure Stack
- 2.6 Optional Azure Resources Configurations
- 2.7 Deployment Errors, Workarounds, and Solutions
- 2.8 Azure Pricing and Cost Calculator
- 3 CAM Azure Stack Security
Azure & CAM Integration Notes
As of January 30, 2021, Azure is not allowing custom token expiry settings. The conditional access policies determine how the token expires are configured. This requires at least a P1 license in Azure. See the Microsoft link here.
CAM Azure Stack Architecture
Content Mover in CAM uses REST APIs to work with 7 functions, 4 queues, and two triggers to move content.
Data Sync (Content Sync) uses REST APIs to work with 3 functions, 1 queue, and one trigger to sync content.
Prerequisites to the CAM Azure Stack Deployment
The following items are needed to begin the Azure Stack deployment process. Without these pieces, your stack deployment may fail or you won’t have the necessary pieces to finish.
Administrative access to an Azure subscription where you plan to deploy the CAM Azure stack ( within http://portal.azure.com )- you need this to configure the stack
Administrative access to your organization’s CAM instance- you need this to configure CAM modules to use the stack.
Your CAM instance Tenant Id, Client Encrypted Key, and CAM Secret Key. You need to contact Litera’s Customer Care team (Support@litera.com) to obtain the Tenant Id before you start the deployment process. It may take some time for them to gather this information. Those keys are unique for each CAM instance. If your organization has multiple CAM instances, then you need to request the keys for each instance separately. If you do not have the Tenant Id create a ticket with Litera’s DevOps or Support team before deploying the Azure Client stack. The Encrypted keys and secret key you can obtain in Microsoft’s Azure panel.
Deploying and Configuring the CAM Azure Stack
Updating the Client Stack
Updating MySQL 7 to 8
For Existing Clients Stacks:
We can't upgrade the MySQL version in single server configurations. We need to upgrade to flexible server configurations first if you are not on a flexible server, then we can update the MySQL version afterwards.
If you were on MySQL 5.7, a parameter is set that isn’t supported in 5.8 that needs to be removed.
That parameter is NO_AUTO_CREATE_USER
Go into Server Parameter.
c. Search for the deprecated config in Parameter-> sql_mode.
d. Deselect the NO_AUTO_CREATE_USER parameter.
Now we can update MySQL. The following shows when clicking into the MySql resource.
Click the MySQL version link that says upgrade. Click 8.0 to upgrade to and hit Upgrade.
For info on what changes in MYSQL 8, visit: https://dev.mysql.com/blog-archive/upgrading-to-mysql-8-0-here-is-what-you-need-to-know/
Prerequisites
Azure CLI: Ensure Azure CLI is installed on your machine. You can download it from Microsoft here: Azure Command-Line Interface (CLI) - Overview
Administrator Access: Open Powershell with the “Run as administrator“ privilege.
Go to the Github repo: GitHub - Prosperoware/cam-azure-deployment .
Download functionAppsCodeUpdate.ps1
Function App: The function app should already be created in the Client stack otherwise this Powershell script will fail.
Executing the Script
Azure login:
If you haven’t logged in via
az login
, The script will prompt you to log in through a browser. Please use the Azure account associated with your client stack deployment.If the wrong account is used , you will be prompted to log in again , with up to three attempts allowed.
Resource group Input:
The script will prompt you to enter the resource group name where your stack is deployed.
If an incorrect resource group is entered, you will be prompted to re-enter the correct name, with up to three attempts allowed.
Function App Identification:
The script will list all function apps targeted for the JAR upgrade.
It will automatically determine whether to update ETL (Content Mover), ContentSync (Data Sync), or both options, based on the function apps present in your resource group.
Logging:
The script will maintain a log file named
CAM_Azure_Stack_log_timestamp.txt
to record the latest operationsOlder logs will be deleted each time the script runs.
File Management:
The script will download and upload the ZIP file from the same directory where 'functionAppsCodeUpdate.ps1' is located.
Upgrading Jar Files:
After running the functionappsCodeupdate script the jar files will be updated automatically.