Skip to main content

 

 

 

 
Language:
 
 
 
OutSystems

Install OutSystems Trial on Azure

Template:OutSystems/Documentation_KB/ContentCollaboration
  • Edit
    Collaborate with us
    Edit this page on GitHub
  • Are you ready to discover the joy that's developing with OutSystems on Microsoft Azure? Then let's get you started with the Trial. This article explains how to:

    Launch the installation wizard

    The first part of installing your trial is to launch the installation wizard:

    1. Log in to the Azure portal with your Azure account and search for OutSystems 11 Standalone Trial.

    2. Click Create. The Azure Portal starts a standard VM creation wizard.

      Click create to create your OutSystems VM

    3. The creation wizard starts on the Basics blade fill in the details:

      • On the Resource group choose Create new and name your resource.
      • Select your desired Azure region under Region.

        Fill in the basic details

    4. Click Next: OutSystems Trial Setup.

    5. On the OutSystems Trial Setup blade fill in the Username and Password. These will be the credentials:

      • to connect to the VM via remote desktop using the Username and Password;
      • to connect to the SQL server with the username adminand the Password you defined in this step;
      • to connect to your OutSystems trial using Service Studio and Service Center with the username adminand the Password defined.
    6. Click Next: Virtual Machine Setup.

    7. On the Virtual Machine Setup blade, accept the suggested VM size or change it to your preference.

      Choose the VM size

    8. You're almost done, click Next: Review + create.

    9. Click Create.

    Your OutSystems trial starts to deploy. A complete OutSystems platform will be deployed and it can take a while, but you can check its progress:

    Deployment in progress

    Deployment completed, you can now access your new VM.

    Deployment completed

    Start your VM

    Next, make sure the new VM is started. First you'll need to locate the recently created VM. The Azure Portal offers several filtering options for your resources.

    1. You can, for example, click Go to resource group once the deployment has finished and look for the OS11Trial virtual machine.

    2. Click Start.

      Start VM

      If the Start button is disabled your VM is already started and you can proceed.

    Create your OutSystems apps

    You OutSystems Azure Trial is ready to use, so go ahead and take it for a spin! But let's ensure you have all the necessary components first.

    1. Download and install the Development Environment 11 on your local computer.

    2. Connect Service Studio to your environment.

      • You'll need the address of you VM to connect. It's the address associated with the OS11Trial Application gateway that can be found on the Azure Portal:

        Application gateway

      • Click on the OS11Trial Application gateway to see the Frontend public IP address. You can use either the IP or the <my_trial>.cloudapp.azure.com address.

      • Launch Service Studio on your local computer. A Connect to Environment dialog box will appear. On the top right corner click Sign in with environment URL. The login box will look like this:

        Service Studio login

        Your Service Studio may already launch with this login box. No worries, you're in the right place, just follow to the next steps.

      • On the Environment field, fill in the address of the OS11Trial Application gateway. Use the username adminand the password you defined on step 5 of the installation wizard.

      • Click LOG IN. This warning will appear:

        Service Studio connection warning

        You'll see this warning because by default, the OutSystems 11 Standalone Trial doesn't have an SSL certificate installed. You can add a valid certificate or click CONNECT ANYWAY.

    3. You're almost ready to start creating OutSystems apps! One final step, let's install the extended product components.

    Need a hand?

    If you want to learn more before creating your first OutSystems apps, we have a lot of available resources:

    • Was this article helpful?