Installing on Azure
  • 03 Jun 2022
  • 3 Minutes to read
  • Dark
    Light

Installing on Azure

  • Dark
    Light

Overview

This tutorial demonstrates how to install the Decisions platform on Azure Infrastructure.

Upgrading from v6 to v7?
Please review the Upgrading Decisions (v6 to v7) article for IMPORTANT CONSIDERATIONS.
For IIS Installations
Ensure that the ASP.NET Core Module V2 in IIS is properly installed. The expected location should be ../ProgramFiles/IIS/Asp.Net Core Module/V2/aspnetcorev2.dll.
Version 7.x .NET Architecture Change: Versions 7.0.1 - 7.1 require .NET Core 3.1 Versions 7.2 - 7.9 require .NET 5 Versions 7.10+ require .NET 6

Impact on Upgrades: 

  • ALL custom libraries will need to be recompiled for the new .NET architecture.
  • Custom assemblies will need to be re-written.
  • Modules may require reinstallation or design refactoring.

Azure Considerations

  1. Create an Azure SQL Server instance.  For guidance, reference How to Create and Configure SQL Database.
  2. Create an Azure VM (any version); the SQL that Decisions generates/executes does not make use of any recent additions to T-SQL or any of the SQL Server-only functionality.
    For guidance, reverence How to use the Management Portal to create a custom virtual machine running Windows Server.

    Note: Select an Azure VM size that meets the following base and *advanced specifications:
  • Production:
    • D-Series D4s v3  (*D8s v3)
    • VCPU: 4  (*8)
    • Memory: 16GB  (*32 GB)
    • HDD Storage: 150 GB
  • Non-Production:
    • D-Series D4s v3
    • VCPU: 4
    • Memory: 16 GB
    • HDD Storage: 100 GB
  • Repo:
    • D-Series D4s v3
    • VCPU: 4
    • Memory: 16 GB
    • HDD Storage: 100 GB

After your Azure VM has been provisioned, log into it, and install IIS and .NET Core 3.1 (Version 7.0 - 7.1) and .NET 5 (Version 7.2+).

SQL Specifications

DB level of at least S3 or P1 should be used since the lower levels greatly restrict transactions per minute, causing timeouts for Decisions SQL queries, especially during installation.


Example

The app server and the Database Server need to be set to the same Time-Zone.
  1. Once a VM and SQL instance has been created, begin installing Decisions. Open the DecisionsInstaller.exe file, select Install.


  2. Read the License Agreement, check I accept the terms of the License Agreement, and select Next.



  3. Select an installation Type that fits our needs. Provide Email for Support and select Next.


  4. Under Database Type, select Azure SQL. Under Connection Type, for DB Server, enter the public address for the Azure DB server. Enter anything for DB Database or leave it at the default of Decisions. Under Connection Settings, select MS SQL Security and enter the Azure SQL admin credentials and select Next.

    Select Test to verify connection status until the Test Connection text box displays, Testing database connection Status: Success. Now select Next.


  5. SQL Full-Text Warning display text box shows, select next to continue.

  6. In the Domain Name, enter the URL by which the Azure server is accessible where Decisions will be installed on. By default, the URL is http://localhost. Select Next.


  7. Select SMTP Direct Server or an SMTP server through which the email should be sent out from, select SMPT Server, enter the SMTP server information, and select  Next.

  8. Search for any existing key files using the search bar. Select Next to continue.

  9. Verify that all requirements checks pass and then select Next.

  10. Review the installation options.  Begin the install process to download the files; select Next.


  11. The installer will begin to download the required files. Select Show Details to see the installation step by step. 


  12. The image will display a message that states Installation Finished. The Decisions application has been installed successfully.

  13. After clicking Finish, the Decisions log in page will load. If the Decisions system was installed on the local machine, the URL will be http://localhost:8081 in the browser’s address bar. The webpage can also be accessed typing in the DNS or IP address with the port number in a browser. This will navigate users to the login screen.

    Note on Port Numbers 
    For the HTML Portal, users must open the port configured in settings for SignalR and then the next. If Decisions is installed to a default Port, SignalIR will no preference for a specific Port.

    Note that without Port specification, the Port is implied from protocol; HTTP uses Port 80, and HTTPS uses 443.

    Default Credentials
    Use the default credentials "admin@decisions.com" and "admin".


Was this article helpful?