Creating an Azure VM Engine Image

Last published : Jul 27, 2026
To use the adapter with Azure, you must first create an Azure VM Engine Image for DataSynapse GridServer® Engine for your choice of OS.
Prerequisites
Before creating an Engine Image, ensure that the following requirements are met:
  1. Disable the firewall on the machine or open all the appropriate ports for the Engine.
  2. Install the Engine. You can install the Engine with the Director you plan to use for production or for a Director you use for a Development or QA grid.
Related information

Creating an Engine Image on Linux

Procedure
  1. Launch any Linux VM on Azure and use Managed disk to launch the VM.
  2. Shut down the Engine Daemon after the Engine starts running against the first Director.
  3. Verify that the Engine Daemon does not start automatically at boot time.
  4. Create Azure VM scale sets (VMSS) by selecting the appropriate engine image. For more information, see Creating VM Scale Set on Azure. For more information about saving VM Image disks in Azure, see How to create a managed image of a virtual machine or VHD.
  5. Once the VM scale set is created, add a custom script in extension for configuring engine machines that is launched in VM scale set. For more information, see Virtual machine extensions and features for Linux. Sample script:
    #!/bin/bash
    #Stopping the engine
    cd /opt/datasynapse/engine
    ./engine.sh stop
    #running the configure utility
    ./configure.sh -s DIRECTOR_HOST:DIRECTOR_MESSAGE_PORT
    #Re-Starting the engine
    ./engine.sh start
    If you are configuring the adapter over an SSL enabled Manager, then configure by using the following command:
    //running the configure utility
    ./configure.sh -s DIRECTOR_HOST:DIRECTOR_MESSAGE_PORT -l y
  6. Update the VM scale set name in a cloudprovider.properties file for VM_SCALESET_NAME property.

Creating an Engine Image on Windows

Procedure
  1. Shut down the Engine Daemon after the Engine starts running against the first Director and delete the Daemon entry from the Director's Daemon Admin page.
  2. Verify that the Engine Daemon does not start automatically at boot time. This is very important for Windows since it installs as a service by default. The service needs to be set for Manual start.
  3. Access gpedit.msc to enable PowerShell scripts. Go to Local Computer Policy > Computer configuration > Administrative Templates > Windows Components > Windows PowerShell > Turn on Script Execution.
  4. In the Turn on Script Execution window, select Enabled in the top left, then in the Options section, select Allow all scripts.
  5. Create Azure VM scale sets (VMSS) by selecting the appropriate engine image. For more information, see Creating VM Scale Set on Azure. For more information about saving VM Image disks in Azure, see How to create a managed image of a virtual machine or VHD.
  6. Once the VM scale set is created, add a custom script in extension for configuring engine machines that is launched in VM scale set. Sample script:
    Stop-Service DataSynapse
    $directorIP="gridDirectorIp"
    $directorPort="8000"
    $datfile="C:\TIBCO\DataSynapse\engine\intranet.dat"
    $newPrefix="http://"
    "$($newPrefix)$($directorIP):$($directorPort)/livecluster/public_
    html/register/register.jsp".Trim() | Out-File -Encoding Ascii $datfile
    Start-Service DataSynapse
  7. Update the VM scale set name in a cloudprovider.properties file for VM_SCALESET_NAME property.