Installing on Azure

Last Updated: 02/14/2019 Introduced in Version: 2.0
To begin your installation of Decision on Azure Infrastructure you will first need to have created an Azure SQL Server instance and VM.
Note:  DB level of at least S3 or P1 should be used since the lower levels greatly restrict transactions per minute which can cause timeouts for Decisions sql queries especially during install.
  • Processing:  3.0 GHz – 8 cores
  • Memory:  16 GB RAM minimum,  32 GB RAM recommended
  • Disk Space: 50 GB minimum
Configure the Endpoints of your Azure VM (and Windows Firewall if enabled) to allow the following TCP ports: 80 (HTTP), 443 (HTTPS if Decisions is installed using HTTPS), 943 (Silverlight Policy) and 4502 – 4534 (Silverlight Data).
Note: for Silverlight Data port range, only 4502 is needed unless someone else on the Decision server is already using port 4502 in which case Silverlight will try to use the next available port in that full range. These ports need to be open for Decisions versions older than 4.0.
For guidance on editing Azure Endpoints please see: How to set up communication with the virtual machine
After your Azure VM has been provisioned, log into it and install IIS and .net 4.5.
Once you have created a VM and SQL instance you are ready to install Decisions. Open the DecisionsInstaller.exe file (Figure 1), select Install.

Figure 1

Read the License Agreement, check I agree with License Agreement and select Next (Figure 2). 

Figure 2


Select an Installation Type that fits our needs. Provide Email for Support and select Next (Figure 3). 

Figure 3

Select Show Advanced Settings During Installation to add an Email for support for any future event, select Next (Figure 4). 

Figure 4

Under Database Type select Azure SQL. Under Connection Type, for DB Server enter the public address for your Azure DB server. Enter anything you want for DB Database or leave it at the default of Decisions. Under Connection Settings select MS SQL Security and enter your admin credentials for your Azure SQL instance and select Next ( Figure 5). 

Figure 5

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

Figure 6


SQL Full-Text Warning display text box shows, select Next to continue (Figure 7). 

Figure 7

In Base Url enter the URL by which your Azure server is accessible with the virtual directory you want Decisions installed to. By default this virtual directory is /decisions but can be changed to whatever you want. Select Web Site and Application Pool. Select Next (Figure 8).

Figure 8


Web Application, advanced settings, select Next to continue (Figure 9). 

Figure 9


Select SMTP Direct Server or if you have an SMTP server through which you want to email to be sent out, select SMPT Server and enter your SMTP server information and select Next (Figure 10).

Figure 10


 Encryption Keys, search for any existing key files use the search bar. Select Next to continue (Figure 11).

Figure 11

Verify that all requirements checks pass and then select Next (Figure 12).

Figure 12

Review your installation options.  Begin the install process to download the files, select Next (Figure 13).

Figure 13

The installer will begin to download the required files. Proceed to Install Modules by checking Selected Modules in Classic Mode or continue the installation process by selecting Next. The installer begins downloading required files and installing Decisions (Figure 14).

Figure 14


 The next Installing display shows details of the installation process (Figure 15). 


Figure 15

The image will display a message that states Installation Finished. The Decisions application has now installed successfully (Figure 16).

Figure 16

After choosing Finish you will be directed to the Decisions login page. If Decisions system was installed on the local machine we can see localhost/decisions/… in the browser’s address bar. If a different address is used to install a portal you will would see something like… in the browser’s address bar.  

Note: For the HTML Portal you must open the port configured in settings for SignalR and then the next. Select Login (Figure 17).


Figure 17


After the User logs into Decisions, the Decisions Portal will open up to the user (Figure 18).

Figure 18


Additional Resources