Deploying the Worker Server

Worker server deployment is optional. You may want to deploy a worker server for file crawling or to provide support to the master server, depending on the expected workload—see Servers.

Before deploying a worker server, you should have already deployed the pod and the master server—see Deploying the Shared Infrastructure and Deploying the Master Server. It is recommended to leave the tabs open, since you will require information related to shared infrastructure when deploying the worker server.

To deploy additional worker nodes, repeat the following procedure and give each new server a unique identifier.

For assistance, please contact your Support Representative.

  • Navigate to the Worker Server Deployment page.
  • Click Deploy to Azure.
  • Fill in the required fields.
  • Subscription: The default subscription automatically populates..
  • Resource Group: Select the resource group you created during the prerequisites stage—see Resource Group.
  • Location: The location automatically sets after you have selected the resource group.
  • VM Name: Set the name of the worker virtual machine (Windows computer).
  • Admin Username: Create a username. This account will become the administrator of the worker server.
  • Admin Password: Enter the master password.
  • VM size: The default server is a B2S. You can choose other sizing requirements after deploying the shared infrastructure.
  • IMPORTANT
    A B2S server is sufficient for a demo or test environment. However, it is not recommended for a production environment, where more power is required. For considerations regarding sizing requirements, see Virtual Machine Size.
  • Master IP Address: This is the private IP of the master server. To find the IP, go to the Microsoft Azure site and click Virtual Machines in the left pane.
  • Master Admin Username: Re-enter the Admin Username you created above.
  • Master Admin Password: Enter the master password.
  • Virtual Network Name: Enter the virtual network name that you have previously created—see Virtual Network.
  • Subnet Name: Enter the subnet name and address prefix that you have previously created—see Subnet.
  • Read the Microsoft Azure Terms and Conditions and click Agree.
  • Click Purchase to deploy the VMs. A message validation message displays.
  • NOTE
    For information on what you are purchasing or the Azure pricing calculator, consult your Microsoft representative.
  • To monitor deployment progress, go to Notifications > Deployments in Progress and view the various status indicators.