Want Bartender Suite On Network Drive
Hi,
During test and development I had the license server on a network server and the rest of the software on me local development system.
What I would like to be able to do is have the entire Suite on that same network server and access Bartender and Commander from any machine.
My first attempt to do this was not successful. Can this be done or does each system I wish to use the Suite on have to have the software loaded?
I have custom front ends that create the data to be printed. What I was hoping to do is have the labels, Bartender and Commander on the server and have my front ends send XML command files with label and printer commands to the Commander Scan folder. This would essentially be a single install of the Suite being trigger into action from multiple front ends.
When I try to run Bartender or Commander over the network I get an App Error hard crash.
We don't have an issue with placing Bartender and Commander on each system that will be used to print labels. We were just hoping we could make it more centralized in order to reduce maintenance overhead.
Have a nice day,
Jon
During test and development I had the license server on a network server and the rest of the software on me local development system.
What I would like to be able to do is have the entire Suite on that same network server and access Bartender and Commander from any machine.
My first attempt to do this was not successful. Can this be done or does each system I wish to use the Suite on have to have the software loaded?
I have custom front ends that create the data to be printed. What I was hoping to do is have the labels, Bartender and Commander on the server and have my front ends send XML command files with label and printer commands to the Commander Scan folder. This would essentially be a single install of the Suite being trigger into action from multiple front ends.
When I try to run Bartender or Commander over the network I get an App Error hard crash.
We don't have an issue with placing Bartender and Commander on each system that will be used to print labels. We were just hoping we could make it more centralized in order to reduce maintenance overhead.
Have a nice day,
Jon
0
-
Gene Henson
★ BarTender Hero ★
Hello Jon,
I think what might for you is to put Commander and BarTender on a central server, and then set Commander to scan a network directory that is accessible from all of your workstations. Then your custom application can place the XML files in that single scan location from any of the workstations. That will essentially give you a centralized installation of BarTender/Commander that can be triggered from any workstation.
Does that sound like what you are looking for? Have you had any problems getting that setup working?
We have a Commander troubleshooter [url="http://seagullscientific.invisionzone.com/index.php?/topic/55-commander-troubleshooting/"]here[/url].
We also have a Commander White Paper [url="http://s3.amazonaws.com/SeagullBarTender/ftp/WhitePapers/WhitePaper_Commander_English.pdf"]here[/url].
Let me know how that goes for you.
For more in depth troubleshooting you may want to contact your [url="http://www.seagullscientific.com/aspx/technical-support.aspx"]closest support office[/url] for a detailed look at your setup.0 -
Hi,
That was exactly how I was setting it up. The problem was that if I tried to run the applications Bartender or Commander over the network they crashed. Do I have to run them from the server they are installed on? Maybe using VPN or some other remote desktop software?0 -
Gene Henson
★ BarTender Hero ★
You don't need to call Commander or BarTender from the workstations; you just have to submit your XML to Commander's 'scan' folder to initiate the print jobs. So Commander/BarTender are installed and running on the server, and the workstations just drop an XML file into a shared Scan folder. The workstations don't actually need to access Commander or BarTender directly.
If you do need to directly access BarTender/Commander from the workstations, then you will need those users to remote into the machine, or you will need to install local copies of the software on each workstation. However, I'd recommend using the centralized route described above as it does ease long term maintenance.
Does that make sense?0 -
[quote name='Gene H - Seagull Support' timestamp='1312477281' post='334']
You don't need to call Commander or BarTender from the workstations; you just have to submit your XML to Commander's 'scan' folder to initiate the print jobs. So Commander/BarTender are installed and running on the server, and the workstations just drop an XML file into a shared Scan folder. The workstations don't actually need to access Commander or BarTender directly.
If you do need to directly access BarTender/Commander from the workstations, then you will need those users to remote into the machine, or you will need to install local copies of the software on each workstation. However, I'd recommend using the centralized route described above as it does ease long term maintenance.
Does that make sense?
[/quote]
I was all set about the first part. It was the developers that needed to set the task in commander for new trigger events and the label designer that needed to access the software. I figured we would have to remote into the server but wanted to make sure.
Thanks for your help.
Have a nice day,
Jon0
Vous devez vous connecter pour laisser un commentaire.
Commentaires
4 commentaires