Skip to main content

Set Up OutSystems on Microsoft Azure

OutSystems

Set Up OutSystems on Microsoft Azure

This article describes the steps to deploy and set up OutSystems on Microsoft Azure.

Prerequisites: OutSystems on Microsoft Azure solution template is available on Microsoft Azure Marketplace under Bring-Your-Own-License (BYOL) pricing model. To deploy OutSystems on Microsoft Azure, start by contacting OutSystems and get your license. 

To deploy and set up OutSystems on Microsoft Azure you must execute the following steps:

  1. Run the solution template wizard in Azure Portal to deploy your OutSystems infrastructure.
  2. Apply the OutSystems license to the deployed environments.
  3. Register the environments on your OutSystems infrastructure management console (LifeTime).

Run the Solution Template Wizard

  1. Go to Azure Marketplace or your Azure Portal and search for OutSystems on Microsoft Azure solution template.
  2. On your Azure Portal, in the OutSystems on Microsoft Azure solution template, click the Create button to proceed to the deployment wizard.
  3. Fill in the information for the Basics blade and click OK to proceed to the next blade. The Solution Identifier you choose will be used to prefix the name of all resources created during the deployment, such as virtual machines or databases.

    image14.png
     
  4. In the Virtual Machine Size blade, choose between a Standalone (1 VM) or a High Availability (2 VMs) production environment. Select the size of each virtual machine, using one of the recommended sizes. Click OK to proceed to the next blade.

    image12.png
     
  5. In the Virtual Network Size blade, confirm the values for the Virtual network and Subnets sections, and click OK in the Subnets section. Click OK to proceed to the next blade.

    image16.png
     
  6. Click OK in the Summary blade.

    image1.png
     
  7. Click the Create button in the Buy blade to start the deployment.

The deployment process might take about 1 hour to complete. You can check the deployment status in the Deployments section of the resource group. OutSystems deployment is finished when all the listed deployments are successful.

image11.png

You will see all the newly created resources in your Azure Portal. All the resources deployed by OutSystems on Microsoft Azure solution template are prefixed with the solution identifier:

image15.png

Apply Your OutSystems License

The next step is to apply your OutSystems license to each environment:

  • Development
  • Test
  • Production
  • LifeTime

To set up OutSystems on Microsoft Azure you must have a valid OutSystems license.

To apply your OutSystems license to the development environment, do the following:

  1. Go to the details of the application gateway created for the development environment to get the DNS name of its public IP address. For example, if your solution identifier is “myid”, the application gateway of the development environment is “myid-dev-appgw”. Click on the Frontend public IP address field to go to the details page of the public IP address.

    image4.png
     
  2. You will access the environment through the DNS name of the public IP address. In the Public IP address details page, use the “Click to copy” option to copy the DNS name.

    image7.png
     
  3. Using the DNS name from the previous step, access the Service Center management console of the environment with the following URL: http://<DNS>/ServiceCenter.
  4. Log on using the default credentials (admin/admin). Don’t change the “admin” user password at this stage, you will do it at the end of the setup process.
  5. Go to the Administration section and select the Licensing tab.
  6. Take note of the Serial Number of the environment. You will need it to get the license file from OutSystems Licensing portal.

    image9.png
     
  7. Go to OutSystems Licensing portal, select your infrastructure and choose ACCESS LICENSING.

    image10.png
     
  8. Register your environment using the serial number you obtained in step 6.
  9. If you are an authorized contact for licensing purposes, proceed with downloading the license file. Otherwise, the license file will be sent to an authorized contact via email.

    image8.png
  10. Once you have the license file (*.lic), go back to the Licensing tab of the Service Center management console of your environment and select Upload New License to upload the license file.

    image3.png

Repeat the same procedure to apply the license to the remaining environments - test, production, and LifeTime.

Register the Environments in LifeTime

Now you need to register the development, test, and production environments in your infrastructure management console, LifeTime.

The environments must be registered in the same order in which they are used in the factory workflow, meaning you must register the development, test, and production environments in LifeTime by this order. This ensures all other environments obtain the applications' definition from the development environment and that the synchronization between LifeTime and the environments is performed correctly.

To register your environments in LifeTime, do the following:

  1. Go to the details of the application gateway created for the LifeTime environment to get the DNS name of its public IP address. For example, if your solution identifier is “myid”, the application gateway of the LifeTime environment is “myid-life-appgw”. Click on the Frontend public IP address field to go to the details page of the public IP address.

    image22.png
     
  2. You will access the environment through the DNS name of the public IP address. In the Public IP address details page, use the “Click to copy” option to copy the DNS name.

    image18.png
     
  3. Using the DNS name from the previous step, access the LifeTime console with the following URL: http://<DNS>/LifeTime.
  4. Log on using the default credentials (admin/admin). Don’t change the “admin” user password at this stage, you will do this at the end of the setup process.

    image19.png
     
  5. To register the development environment, we will use the DNS name of the public IP address associated to its application gateway, for example “myid-devappgw-PIP”. Go to the details of the public IP address and use the “Click to copy” option to copy the DNS name.

    image7.png
     
  6. Go to LifeTime and fill in the Environment Address in the Development card with the DNS name from the previous step (remove any initial “http://” the browser might add when pasting the text).

    image21.png
     
  7. Click the Register button.
  8. At this point, LifeTime connects with the Service Center management console of your development environment and requests from you the administrator credentials. Use the default credentials (admin/admin) and click Next.

    image2.png
     
  9. Since the environments don’t yet have any SSL certificate installed (you can install SSL certificates on your environments later on), click the Next button to proceed with the environment registration using HTTP.

    image5.png
     
  10. Click the Register Environment button.

    image17.png
     
  11. The development environment is now registered in LifeTime. Repeat steps 4 to 9 for test and production environments.

    image23.png

The setup process is now complete.

At this point, we recommend that you change your password for the LifeTime administration user (admin). Choose My Settings on the top right side of the LifeTime header to go to your settings page where you can change your password. Changing the admin password on LifeTime automatically changes the admin password of the Service Center management console of each registered environment.


image20.png

And you are done! At this point, your OutSystems on Microsoft Azure is ready to use. Check this document to learn more about some additional configurations you might want to execute in your OutSystems infrastructure.

 

  • Was this article helpful?