Skip to main content

 

 

 

 

Template:OutSystems/Documentation_KB/Breadcrumb_New_Layout

 

 

Template:OutSystems/OSLanguageSwitcher

 

 

 

OutSystems

How to deploy OutSystems Platform on Azure

This offer (the OutSystems Deployment accelerator) is scheduled to be discontinued soon.

You may still deploy OutSystems on Azure, by simply following the installation checklist.

 

The OutSystems Deployment accelerator, available from the Azure Marketplace, enables you to quickly provision all the servers and network infrastructure required for an OutSystems environment, using a reference network architecture.

Preparation

The following instructions require an Azure account and an OutSystems Platform subscription.

Run the OutSystems Deployment accelerator

  1. Go to the OutSystems page in the Azure Marketplace.

  2. Select OutSystems Deployment Accelerator.

  3. Click Create to start the deployment wizard. If prompted, enter your Azure credentials.

Note: The wizard provides default values for many Azure deployment parameters, such as deployment location, which you are free to change. These parameters are not explicitly described in these instructions.

Wizard step 1: Basics

1. Select an existing resource group or enter the name of your new resource group.

Wizard step 2: Virtual Network setup

The OutSystems Deployment Accelerator will provision all servers in the same Virtual Network. You can choose the Virtual Network. 

The OutSystems Deployment Accelerator will deploy all front-end server and the deployment controller server on to the same subnet, and the database server to a different subnet. You can choose the subnets to use.

  1. By default, the wizard creates a new Azure Virtual  Network, named OutSystems_VN. Click Virtual Network to change this default.
  2. Click Configure Subnets. The wizard proposes default names and address ranges. Even if you don't need to change these defaults, you must  open the Configure Subnets dialog.

Wizard step 3: Front-end setup

This step of the wizard provides safe defaults for other parameters. You can override them: hostnames, public IP address, and virtual machine sizes.

  1. Enter the administrator account credentials (username and password) for the front-end servers.

  2. Click Front-End Storage account. Then, either select an existing storage account or enter the name of your new storage account.

  3. Enter your DNS label.

By default, the wizard provisions 2 front-end servers and a separate server that acts as the deployment controller server. If you want a different number of front-end servers, you have the option of specifying another number. If you plan to run the deployment controller server in one of the front-end servers, you can change that default, too.

 

Wizard step 4: SQL Server

  1. If you plan to reuse an existing SQL Server VM on Azure, select No for the "Deploy SQL Server?" option. For example, if you want to reuse a database in two non-production OutSystems environments, you should not deploy SQL Server while creating your second environment.

  2. Click SQL Storage account. Then, select an existing storage account or enter the name of your new storage account. 

  3. Confirm which SQL Version you wish to deploy: Standard or Enterprise.

If you wish, you can also override the default hostname and virtual machine size.

Wizard step 5: Summary

  1. The Azure Marketplace validates your deployment, reports Validation passed, and enables the OK button.
  2. Click OK to continue.

Wizard step 6: Buy

  1. Confirm that you accept the Terms of Use.

  2. Click Create to start deploying your infrastructure. The deployment will take several minutes.

Successful deployment! What did you get?

Based on the options you selected, you now have a resource group with some or all of these items:

  • A number of virtual machines with Windows Server 2012. Each virtual machine has a copy of the OutSystems Platform installation binaries, which are ready to be installed; all pre-requisites detailed in the OutSystems Platform installation checklist; and remote desktop connectivity from the Azure Portal.

  • A load balancer with a public IP address, routing traffic to the front-end servers in an availability set.

  • A virtual machine with SQL Server 2012.

  • A virtual network with two subnets: one for the database, and the other for the front-end servers.

  • Network security groups with adequate configuration.

Configure SQL Server 

To use your new SQL Server virtual machine with OutSystems Platform:

  1. Connect to the SQL Server virtual machine via remote desktop.

  2. Set SQL Server server authentication to SQL Server and Windows Authentication Mode.

  3. Enable the SQL Server port (1433) in the Windows Firewall.

Install OutSystems Platform

  1. Connect via Remote Desktop to the Deployment Controller Server.

  2. Install OutSystems Platform by double-clickling the shortcut to the OutSystems Platform Server installation binary in the server desktop.

  3. Configure the Windows Firewall to enable communication between the deployment controller server and the front-end servers. 

  4. Repeat for each front-end server.

Post-installation network security hardening

The OutSystems Deployment accelerator default network configuration is designed to simplify the installation process. Once your environment is installed, consider strengthening your network security, following these steps in the Azure portal:

  1. If you have a separate deployment controller server, disable the public IP address of the deployment controller server. 

  2. Disable the public IP address of the SQL Server virtual machine.

  3. Open the Network Security Group of the Backend Subnet.

  4. Set the inbound security rule called rdp_rule to Deny.

  5. Set the outbound security rule called Block_internet to Deny.