Linkedin
Facebook
Whatsapp
Whatsapp
What is an Azure Service Bus?
From a very high level, an Azure Service Bus is the mechanism that Lasernet uses to send messages.
The description given by Microsoft is: “Azure Service Bus is a fully managed enterprise message broker with message queues and publish-subscribe topics(in a namespace).”
For more technical information about the Azure Service Bus see the Microsoft documentation.
The creation and configuration of the Azure Service Bus require users to create new resources in Azure. If you are unsure of how to work within Azure, then please contact your system administrator.
Where do we use it?
Azure Service Buses are used in several locations in the Lasernet products, such as the Connector to link Finance and Operations (FO) and Business Central (BC) to Lasernet, or linking to Cloud Printers. The following is an example Azure Service Bus referenced in the connections in the FO Connector.
How do I create an Azure Service Bus?
In this article, we will show an example of how a service bus can be created, however for the latest information always refer to the Microsoft guide.
1. Navigate to the Azure portal, and log in.
2. The Service Bus can be accessed from the list of services at the top of the page, or using the search bar.
3. Click the Service Bus icon. You will be taken to a page with a list of all the Service Buses currently configured.
The following screen will be displayed:
1. Subscription | The Azure subscription to which the service bus will be billed, accept the default, or check with your system administrator to confirm which subscription to use. |
2. Resource Group | Resource Groups are used to help better organize Azure resources, customers usually have a “Lasernet” Resource Group to select here. |
3. Namespace Name | The name of the Azure Service Bus. If your organization has a naming convention then be sure to follow it. |
4. Location | The location of the physical hardware which hosts the Service Bus, for a test instance the default will be fine but it is best practice to select the location closest to your Finance and Operations and Lasernet resources for a production instance. If you’re unsure ask a system administrator. |
5. Pricing Tier | For most use cases, the Basic Tier for Test and Production is sufficient. Unless you print 500K reports per month (or 250K per month using Cloud Print) you will not reach the limit of Basic Tier. |
5. Fill out the fields as described above.
6. Click Review + create.
Azure will run basic checks on your configuration, and then display a “Validation succeeded” message.
7. Click Create.
The deployment will begin, and Azure will confirm that it is in progress.
Once the deployment is complete the following message will be displayed:
8. Click Go to resource to be taken to the new Service Bus.
Generate a connection string for Lasernet
Now the service bus has been created, we need to get the information that allows Lasernet to use it to send messages, this is the connection string. When you click Go to resource in the previous section, you will be directed to this page:
1. Under Settings, click Shared access policies.
There are different keys and strings displayed.
3. Copy the Primary Connection String by using the copy icon indicated.
The string can be copied into the Lasernet Connector, or into the Azure Service Bus input in Lasernet to allow the product to communicate using the Azure Service Bus.
An example:
Create a Queue Name
In this example, the configuration also needs a Queue Name. This can be created from within FO, or from within the service bus.
1. From the Resource Overview page, select Queues.
3. Give the queue a sensible name, keep the other fields as default, and click Create.
When you copy the connection string into FO, you will be able to select the queue name from the drop-down.
Add a comment
Please log in or register to submit a comment.