The material in this document is for informational purposes only. This guide assumes that the most recent version of Rampiva Automate is in use unless otherwise noted in the prerequisites. The products it describes are subject to change without prior notice, due to the manufacturer’s continuous development program. Rampiva makes no representations or warranties with respect to this document or with respect to the products described herein. Rampiva shall not be liable for any damages, losses, costs or expenses, direct, indirect or incidental, consequential or special, arising out of, or related to the use of this material or the products described herein.
Introduction
This article describes the steps required to perform a basic installation of Rampiva Automate on a container hosted by Azure App Services. A similar deployment is possible on other container services, such as DigitalOcean, AWS or Google Cloud.
This deployment mode renders Rampiva Automate accessible from the Internet using a valid HTTPS certificate is recommended for the following scenarios:
Running native workflows
Running or evaluating Legal Hold Notifications
Evaluating the Rampiva Automate features and user interface
If you encounter any issues with the installation, please post a message on the https://community.rampiva.com/.
Prerequisites
Microsoft Azure account
Instructions
A. Install Rampiva Automate
1 | Browse to Microsoft Azure at https://portal.azure.com/ | |
2 | Select the service App Services, or browse to https://portal.azure.com/#view/HubsExtension/BrowseResource/resourceType/Microsoft.Web%2Fsites | |
3 | Click Create to start the configuration of a new service. | |
4 | Create a new resource group named rampiva-automate. | |
5 | Name the instance rampiva-automate-company, where company is the name of your company. | |
6 | Select the publish option Docker Container. | |
7 | Select the operating system option Linux. | |
8 | Use the default region and Pricing plan. | |
9 | Click Next: Docker > | |
10 | Select the image source option Docker Hub. | |
11 | Type in the Image and tag value: rampiva/rampiva.automate.aio:7.3.0-dev The latest tag correspond to the latest Rampiva version from the Quarterly Channel. See https://downloads.rampiva.com/automate/release/index.html | |
12 | Click Review + create. | |
13 | Confirm the estimated price and click Create. | |
14 | Wait for the deployment to complete and click Go to resource. | |
15 | Copy the application URL. | |
16 | Open the copied URL in a new browser tab. At this step, you will not be able to log in, because no authentication providers were defined. | |
17 | In the Azure App Services tab, select Configuration and add the following new settings using the New application setting link:
| |
18 | Click Save and Continue, and wait for the application to restart. The application restart can take several minutes. | |
19 | After the application restarted, you will be prompted to log in. Use the username and password configured at the previous step. | |
20 | Confirm that you can log in with the username and password defined previously. At this step, Rampiva Automate will be unlicensed. For instructions on how to register for a Community license and applying the license, see Automate - Apply a Community License. |
B. Redirect Data to Azure SQL (Optional)
1 | Determine if the redirection of data is required. This section describes the steps required to redirect the data stored by Rampiva Automate from the container to an Azure SQL database. If these steps are not put in place, when the Azure App container is restarted or deleted, the data used in Rampiva Automate will be lost. These steps are recommended in production but are not required for testing Rampiva Automate if the application data does not need to be preserved. | |
2 | Browse to Microsoft Azure at https://portal.azure.com/ | |
3 | Select the service SQL servers, or browse to https://portal.azure.com/#view/HubsExtension/BrowseResource/resourceType/Microsoft.Sql%2Fservers | |
4 | Click Create to add a new SQL server. | |
5 | Name the server rampiva-automate-company, where company is the name of your company. | |
6 | Select the Authentication method: Use SQL authentication | |
7 | Fill out the Server admin login with the SQL admin username, for example rampiva-sa-admin. | |
8 | Fill out the Password with a strong random password that will be associated with the SQL admin username | |
9 | Fill out the Confirm password. | |
10 | Click Review + create. | |
11 | Confirm the estimated price and click Create. | |
12 | Wait for the deployment to complete and click Go to resource. | |
13 | Select the Networking tab. | |
14 | Under the Public access section, select Public network access: Selected networks | |
15 | Scroll down, and select Add a firewall rule | |
16 | Type in the Rule name: Allow all The following steps will allow the SQL server to be accessed from all locations on the Internet. If desired, a stricter firewall rule can be configured. | |
17 | Type in the Start IP: 0.0.0.0 | |
18 | Type in the End IP: 255.255.255.255 | |
19 | Click OK | |
20 | Click Save | |
21 | Browse to Microsoft Azure at https://portal.azure.com/ | |
22 | Select the service SQL databases, or browse to https://portal.azure.com/#view/HubsExtension/BrowseResource/resourceType/Microsoft.Sql%2Fservers | |
23 | Click Create to add a new SQL database. | |
24 | Name the database automate-db1. | |
25 | Select the SQL server previously created. | |
26 | Select the desired Workload environment: Production. | |
27 | Click Review + create. | |
28 | Confirm the estimated price and click Create. | |
29 | Wait for the deployment to complete and click Go to resource. | |
30 | Return to the service App Services, or browse to https://portal.azure.com/#view/HubsExtension/BrowseResource/resourceType/Microsoft.Web%2Fsites | |
31 | Select the application previously created. | |
32 | In the Azure App Services tab, select Configuration and add the following new settings using the New application setting link:
| |
33 | Verify that the environmental variables have been defined correctly by clicking on Show values. | |
34 | Click Save and Continue, and wait for the application to restart. The application restart can take several minutes. | |
35 | To monitor the application logs, select the Advanced Tools tab → Go → Log stream. | |
36 | Confirm that you can log in with the username and password defined previously. |