This procedure describes how to configure BarTender Integration Builder (from BarTender
2016) for label printing integrated with E-WMS.
In earlier BarTender releases (up to version 10),
BarTender Commander was to be used. Please refer to
this document for
configuration of BarTender Commander.
When you are upgrading from BarTender Commander to BarTender Integration
this document provided by Seagull may be useful.
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 Integration.
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 for the current process step, as 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
configured label layouts
will be started in sequence.
The IIS server creates a .DD file in the 'BarTender scan folder'; this
file is a BarTender XML script file, containing amongst other, following
information:- the path and the name of the label
layout to use- the
unique transaction ID to print the label for (available in the new records
created in step 3), or embedded text data to be printed
BarTender Integration (continuously running) is triggered by this new DD
file to use the contents of that file to start BarTender, with the specified
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, but E-WMS provides text data embedded in the
XML script files.
This plan of approach 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,
to Seagull Scientific documentation.
For E-WMS, the Bartender Enterprise Automation edition is required. You
can read more about E-WMS requirements for BarTender
This edition allows the use of specific required
BarTender Integration XML command options. This
external link provides more information on BarTender editions.
Install the BarTender suite including the
Integration Builder, preferably on the IIS server acting as webserver for E-WMS. 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 the service 'BarTender Integration Service' (and of course
the 'Seagull License Server'). 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 or 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).
When using the 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.
When using the 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.
This applies to using both 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.
After installation of the BarTender Enterprise Suite, Integration Builder can be started in Start, Programs, BarTender
2016, Integration Builder.
This step describes how to create a new 'integration', to trigger label
printing based on files created by E-WMS.
Please note that only the basic required steps are documented. For any specific
configurations or problems, please refer to Seagull Scientific
When you already used BarTender Commander before and upgraded to BarTender 2016 or
later, you can convert existing Commander tasks:
Creating a new integration
To create the new task which handles E-WMS labels, choose:
In the first configuration tab 'File Detection', the following marked
settings have to be changed:
In the next configuration tab 'Input Data', following has to be changed:
Default, an entry 'Print Document' will be created under section 'Actions'.
Remove 'Print Document' by pointing at this option and choosing the red X.
Then press the '+' sign behind Actions and choose: Print BTXML script.
The configuration as default created does not have to be changed.
Press the 'save' icon in the left upper corner of the screen.
You can now save the integration as 'Bartender integration file' in a folder,
preferably use the name 'WMS' in the file; for instance 'WMSIntegrationFile.btin'.
In the top of the screen, select 'Test integration' and next 'Deploy
Next, you can create a deployment. Assign a name, optionally in a specific
folder, and press OK:
Running integrations are monitored in a separate program; the BarTender
Administration console. This program can be started from the BarTender
programs folder, and is also started automatically from the Integration Builder.
You can set up for example NovaPDF printer to save the prints to files automatically, without dialogue screens. Go to Start/Settings/(Devices
and) Printers and right-click on 'NovaPDFProv4'. 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.
Please note that configured printer settings may be user-specific.
For general troubleshooting of this label print process, please see
Troubleshooting label printing.