Self-Hosted Customers

Overview

Self-hosted customers must install and configure the Lasernet server themselves by following the steps in this section of the guide.

Many customers choose to host their Lasernet server internally, either on-premises or in their own Azure subscription. If that is the case, ensure the following prerequisite steps for non-hosted customers have been carried out before commencing with the installation.

Prerequisites

Azure Resource Group

This is a way of grouping all the relevant Lasernet Azure resources. If your organization already has a suitable resource group, there is no need to create a new one, but it can be helpful to separate Lasernet resources to ensure they are easier to manage. Normally, IT departments have policies regarding when to share or keep separate Azure resource groups.

Azure Service Bus

The Azure Service Bus is the mechanism via which the Lasernet Connector and Lasernet communicate and is, therefore, a crucial part of the solution.

An Azure Service Bus with a Shared Access Policy with Manage, Send, and Listen rights will need to be configured. The connection string for this SAS policy will be used in the Connector configuration.

To find out more information regarding Azure Service Buses, see Microsoft's documentation.

Azure Storage

Lasernet requires both working storage during processing operations and archive storage for documents that have already been processed. Many different options can be configured for both requirements, but to get Lasernet for Dynamics configured quickly and easily, we recommend using the Azure Storage, which comes natively with Finance and Operations (FO). This storage connection will be available once the Lasernet Connector is installed.

To find out more information regarding Azure Storage, see Microsoft's documentation.

Finance and Operations Environment

Access to FO will be required. To install and configure the Lasernet Connector, we recommend that the FO environment also contains some test data, which can either be the Contoso dataset or other organization-specific data.

Lifecycle Services Access

Access to Lifecycle services will be needed to deploy the Lasernet Connector package to the relevant FO environment and to access the Formpipe project, where the deployable packages will be available.

Server Access

If Lasernet is not being hosted by Formpipe, it will need to be installed on a server somewhere. This can be an on-premises machine or a cloud-hosted machine, but whoever is doing the installation will need to be able to connect to the server and have the rights to install software there. It is useful if the server has access to the Internet and a browser installed as well.

It will also be necessary to configure the server so that the machine where the Lasernet Developer is installed will have access to the server. There may be some configuration required to the server firewall and to the Network Security Group in Azure to allow this. Lasernet needs 33443 and 443 ports.

To see the requirements for the Lasernet Server, visit our Lasernet System Requirements page.

See the specific instructions page for how to connect to Lasernet from your local machine.

Installation Permission

As part of the setup process, Lasernet will need to be installed locally, so it is important that whoever is carrying out the installation has admin rights on their machine to enable them to complete the installation.