Best Practice On Test Vs Production License Server? 追蹤

0
Avatar
Legacy Poster

I know, I've asked a lot of questions lately :)

 

I have a decent sized production enterprise automation environment with its own license server on the same server as the Bartender suite.

 

I have a smaller test/staging enterprise automation environment also with its own license server on the same server as the Bartender suite.

 

When I create labels, I set their license server to "automatic", this way if they are on test they use test's license server, if they are on production they use production's.

 

I like the idea of keeping these separate because if I do something very stupid on test, like somehow print to a ton of different printer instances, the worst case is I mess up test for a week until the print count resets. However, in truth, that's never happened. As such, I'm wondering if I should simply kill this test license server off and increase the production by the same count?

 

  • if I merge, I'll have to explicitly identify license server on existing and future labels, so that as they move from test environment to production they keep using the proper single licensing server
  • I partly want to do this because I want to create a license-only server that has no other Bartender components except the license server (because I need a BT 2016 license server but don't want to upgrade the rest of my 10.1 stuff right now)

 

What is the best practice here? Is insulating the license server in its own test instance overkill?

4 意見

0
Avatar
Ian Cummings
版主

The License Server to use is specified at the BarTender Designer application level via the "Administer>Licensing Setup" menu item; it is not specified at the individual document level. When there is more than one License Server running in the same network, my preference is to disable the auto find option in Licensing setup, and instead set it to the hostname or IP address of the computer desired. If this is to be the same computer then that would be either localhost or 127.0.0.1 which is the loopback address.

For high availability (HA), scaled up solutions, my recommendation is to have License Server and the System Database on its own server/VM, with at least two BarTender installations on their own servers/VMs for load balancing and redundency.
0
Avatar
Legacy Poster

If you want a Test and Production truly separated you could move your Test license server to a different sub net.  Computers wont automatically find a licences server in a different sub-net, but if you explicitly set it as Ian said, it can be reached. 

0
Avatar
Legacy Poster

Thanks, guys.

 

So changing the license server actually is less work than I thought, simply at the machine level.

 

As to the current test vs prod license server, is it overkill? It would be easier to manage if I just chunk everything together and have my test environment point to the single license server.

0
Avatar
Ian Cummings
版主

Depends on what level of redundency you need.  It might be overkill, it might not.  You'll have to decide.

登入寫評論。