Skip to main content
B
bbender4-Participant
4-Participant
March 23, 2023
Solved

Arbortext Editor in Azure

  • March 23, 2023
  • 1 reply
  • 1960 views

Hello everyone, has anyone deployed Arbortext Editor in Azure? I am working on setting up a FlexNet license host triad (using 3 Windows VMs) to host our floating licenses. I assume we will deploy Arbortext Editor itself using Azure Virtual Desktops (AVD) where a license can then be checked out from the license pool by the user. Thus far I've hit communication issues between the FlexNet hosts that I'm trying to resolve by looking into networking and license configuration. I just wanted to check with the community to see if this was done by someone else in Azure or perhaps in AWS and if they have any high-level guidance. Thanks!

Best answer by GarethOakes

Yes you will need network connectivity between the Arbortext clients and the FlexNet license server. I haven't done this before but it looks like you need to ensure that the clients and server are on the same subnet and then use network security groups to allow traffic flow between the machines. https://learn.microsoft.com/en-us/azure/virtual-network/tutorial-filter-network-traffic

1 reply

G
GarethOakes16-PearlAnswer
16-Pearl
March 24, 2023

Yes you will need network connectivity between the Arbortext clients and the FlexNet license server. I haven't done this before but it looks like you need to ensure that the clients and server are on the same subnet and then use network security groups to allow traffic flow between the machines. https://learn.microsoft.com/en-us/azure/virtual-network/tutorial-filter-network-traffic

    B
    bbender4-ParticipantAuthor
    4-Participant
    March 27, 2023

    Thanks, Gareth, I have setup the licensing but still have communication issues. I know they are on the same subnet with a configured NSG. I'll check with my DevOps team to make sure everything is configured properly in case I missed something. Previously, this was such an easy setup with our on-premises VMs.

    B
    bbender4-ParticipantAuthor
    4-Participant
    March 31, 2023

    Just a follow up--we finally resolved the issue related to a firewall that was blocking the connection.

    Terms & ConditionsCookie settingsAccessibility statement