We’re specifically using Plumbline’s Bartender extension, but basically it’s making calls to the Bartender server’s Web services to print the barcodes. Easy enough to do right now while we’re on prem, but what’s the best way to get this thing connected in SaaS(we’re in the middle of upgrading)? Their documentation’s exceedingly light on the subject so I thought I’d ask here. My partner was reaching out to Plumbline to get their recommendation, but I haven’t gotten anything back from that route yet and I’d prefer to get this resolved sooner rather than later.
1 Like
I can think of three ways.
Use the multitenant BarTender Cloud with the print connector.
Take the on-premises BarTender server and put it on Azure.
Create a secure relay in Azure for the on-premises BarTender server.
Using the Cloud version is likely more future proof than trying to host or expose the on-prem version.
Hi Bryan,
This is a common challenge when moving from on-prem to SaaS, since BC SaaS can’t directly call your local Bartender Web Services. You’ll need a secure bridge.
A couple of approaches that work well:
-
API Proxy Layer – Expose Bartender Web Services via a REST API (Azure API Management or an Azure Function). BC SaaS calls the API, and it forwards requests to Bartender.
-
On-prem Data Gateway – Similar to Power Platform, it lets BC SaaS talk to your local Bartender server without opening firewall ports.
-
Cloud-native Options – If available in your Bartender version, consider upgrading to one that supports cloud connectors.
In practice, the API proxy route is usually the most flexible long-term, especially if you’re already in Azure. I’d start by testing with a simple REST call to validate connectivity before wiring it up to the extension.