Deploying the Shared Infrastructure

Assuming that you have all the resources specified in Prerequisites, the next step is to deploy the IPRO shared infrastructure, called the pod. It contains the following servers:

Server

Description

CentOS

Hosts LDAP services.

CentOS

Hosts the SOLR indexing compoment.

Windows OS

Hosts the client web interface used by the end user or managers to search the contents. Also known as the remote provider in IPRO terminology.

Windows OS

Hosts the file shares for the clients (Windows File Shares)

After the pod is deployed, you can add multiple master servers to host the individual clients. At a minimum, a hosted client requires one (1) master server but may require more master servers or some worker servers depending on the size and types of data being archived (Microsoft SharePoint, Microsoft OneDrive, Citrix FileShare, and so on.)

The following steps pertain to deploying shared infrastructure for a multi-tenant solution using a template.

NOTE
BYOL stands for Bring Your Own License.
  • Navigate to the Azure Marketplace and search for NetGovern.
    • IMPORTANT
    In Azure Marketplace, you can find ARCHIVE products by searching for NetGovern.
  • Select NetGovern Multi-Tenant and click Get It Now.
  • Fill in the required contact info and click Continue.
  • On the Microsoft Azure Portal page, click Create.
  • In Basics, configure basic settings.
  • Username and Password: The username and password that will be used for all VMs deployed using this solution template.
  • 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.
  • In Virtual Infrastructure Settings, define a new or existing network.
  • Subnet Name: Enter the subnet name and address prefix that you have previously created—see Subnet.
  • In Shared Layer VM Settings, define the server size and OS disk type for each of the VMs that are part of the pod.
  • OS Disk Type: Standard HDD appears as the default.
  • Index VM Size: The default server is a B2S. You can choose a different size 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.
  • LDAP DB VM Settings: Premium SSD appears as the default.
  • Shared Storage VM Settings: The default server is a B2S. You can choose a different size after deploying the shared infrastructure.
  • In NetGovern Application Settings, enter the master server settings.
  • Azure Tenant ID: Enter the Azure Tenant ID that you have previously identified during prerequisites—see Multi-Tenant Requirements.
  • Master Server VM Name: Enter the name of the first master server.
  • OS Disk Type: Standard HDD appears as the default.
  • In Summary, validate your settings.
  • In Buy, click Create.
  • NOTE
    For information on costs, consult your Microsoft representative or the Azure pricing calculator.
  • Click Notifications to view the deployment progress.
  • The pod is ready to use.