This document describes how to configure BarTender Commander (up to
BarTender 10) for
label printing for E-WMS.
Starting from BarTender 2016, Commander was replaced by Seagull Scientific with BarTender 'Integration
For the configuration of 'Integration Builder', please refer to
BarTender label printing can be integrated using two methods in E-WMS:
This server method is applied as label printing method, when:
Because the WMS scanner client has no printing capacity, the printing is
initiated by the WMS ASP IIS server, creating 'trigger files' for BarTender
This is how label printing from the hand terminal works:
The 'label print' button is pressed on the hand terminal
A label print screen is shown, the operator has to generate numbers, confirm quantity and/or
number of labels (depending on the process)
WMS creates records in specific tables, on which label printing (the SQL
view) is based:
SKU Management: new SKU numbers are created in table
Generated SSCC: temporary records are created in table
csPickitLabelPrinting, SSCC sequence numbers are increased
S/B Generation: New S/B numbers are created in table ItemNumbers,
temporary records are created in csPickitLabelPrinting
WMS reads the label configuration entered in menu System, E-WMS, Labels
to determine what label(s) are to be used.
It is possible to configure more than one label for the same process. All labels
will be started in sequence.
The IIS server creates a .DD file in the 'BarTender scan folder', which
is in fact a BarTender command XML file, containing amongst other
information:- the label
layout to use- the
unique transaction ID to print the label for (available in the new records
created in step 3)
BarTender Commander (continuously running) is triggered by this new DD file to use the contents of that file to start BarTender, with
the specified BarTender label, and sends the transaction ID as selection into the
BarTender is started and prints the label
When the E-WMS setting 'Bartender method' is configured to 'server', then SQL
data is not accessed by BarTender, instead E-WMS provides text data embedded in the
XML script files created for Commander.
This plan of approach of configuring BarTender Commander describes following steps:
Requirements for using E-WMS with BarTender Integrations
BarTender can be obtained from
BarTender can be downloaded from their site, but you will need a valid license.
Using the demo version is not supported in E-WMS. For the installation procedure, refer
to Seagull Scientific documentation.
For E-WMS, the Bartender Enterprise Automation edition is required.
This edition allows the use of specific
required BarTender Commander XML command options. This
external link provides more information on BarTender editions.
Install the BarTender suite including BarTender
Commander on the IIS server. The 'BarTender scan folder' needs to be a local
folder on the IIS server, because the account used by the IIS process will not
have rights to access network shares. You also need to install the Seagull
License Server on the same or another server in the network, this service will manage your
BarTender licensing based on number of used printers.
The BarTender suite installs some Windows services,
E-WMS only requires BarTender and BarTender Commander ('Commander Service'). The
BarTender System Service (used for BarTender reprinting and logging) and Printer
Maestro are not required for E-WMS, but do offer enhanced BarTender
functionality like reprinting labels and for instance a 'History explorer' which
can offer valuable information in case of BarTender error situations.
Depending on the process you are printing labels for, you need to configure
following WMS settings:
A SQL view is always used in the label process, but
its usage depends on the 'Bartender method':
You can retrieve sample views for
hand terminal label printing from E-WMS - Bartender integration: sample views and
layouts for all processes.
The views require some mandatory fields (like unique transaction ID), besides
that you are free to add any fields to the view (and to the label).
BarTender server method
For creating labels when using the BarTender 'server'
method, please see document
How to create BarTender layouts based on a text file data source.
BarTender client method
Please refer to
this document on how to link a SQL table or SQL view, with a Query Prompt,
in BarTender Designer.
After installation of the BarTender Enterprise Suite, BarTender Commander can be started in Start, Programs, BarTender, Commander. Commander is a job scheduler for BarTender reports, reacting to several triggers.
This step describes how to create a new Commander task, to trigger label
printing based on the creation of specific files by E-WMS.
Choose Task, Add, the Task Options screen is shown:
Fill the task options on tab 'Trigger':
Now choose tab Command(s)
Change Command Type from "Bartender" to "Bartender XML script".
If the option 'Bartender XML script' is missing, then you do not have the
correct BarTender version installed.
Press the button 'BarTender Commander Handler Setup', the following screen will show.
If the button is disabled, first STOP the Commander label task if it was
Choose tab Logon
Enable option Run BarTender Using Account and fill in the account details for a local administrator account on the current PC or server. Enter the local PC or server name at Domain. This account is used to run and print from BarTender.
In BarTender 9.4 this screen looks slightly different, you can enter a local
username just as 'user name', or a domain user as 'domain\user name'.
Press OK twice.
You have now created a new task which:
Now you still have to start this task by selecting Detection, Start Detection.You can save this task (and other tasks in the current task list) by using menu File, Save. But this is not a back-up, when deleting a task it will also be deleted in the saved task list.
For back-up, you will have to copy the TL files to another folder.
This step is optional and is a matter of IT Management. When you have chosen to
rename the trigger (*.DD) files to *.XML you will have a lot of XML files after a while in the BarTender scan folder. To clean those up, you can create and schedule a batch file to delete XML files:
This applies to using the BarTender 'server' or 'client' method.
The created SQL view and BarTender layout have to be linked to a WMS process step. Go to menu System, E-WMS, Labels and create a new label as described in document WMS system menu: Labels.
Choose the BarTender layout and SQL view created earlier, and select
the appropriate applications:
You can retrieve sample labels from WMS Bartender integration: sample views and
layouts for all processes.
You can set up for example NovaPDF printer on the IIS server to save the prints to files automatically, without dialogue screens. Go to Start/Settings/Printers and right-click on 'NovaPDFProv4' (or other PDF printer). Choose printing preferences and tab Save. Enable option 'Use predefined settings' and press 'Configure Save Options'.
Folder: set to a folder where the generated PDF files can be savedFile name: press 'Macro' to choose a predefined file name formatWhen file exists: choose 'Auto number new files'When using this PDF printer as default printer in the BarTender label, prints will be automatically saved as PDF files.
The next step is to determine if the labels would be printed from the hand terminal, when using the SKU button in receipts processes.
For general troubleshooting of this label print process, please see
Troubleshooting label printing when using BarTender Commander.