Purpose

Maintaining the label printers utilized by OnCore BSM Users.

Responsibilities

1. OnCore Application Administrators
   1. Responsible for Server Settings
   2. Responsible for configuration of Bartender
2. Virtual Machine Managers
   1. Managing Virtual Machine server is on
   2. can be contacted at sysops@med.wisc.edu
3. SMPH Networking people
   1. Responsible for communication between label printer and Bartender Server
4. BSM Users 
   1. Communicate any issues, or needed printer label changes

Sections

1. Communication Pathway For Label Printing
2. Managing the Print Server
3. The Bartender License
4. Using Bartender Label Designer
5. Configuring Bartender Integration
6. Deploying Bartender Integration
7. Configuring Javascript tool
8. Checking login for Bartender account

Instructions

1. Communication Pathway For Label Printing
   • Printer:
     • Managed by DOM, reach out to DOM Helpdesk with questions: https://helpdesk.medicine.wisc.edu 
   • UW Network:
     • Managed by DOM, reach out to DOM Helpdesk with questions: https://helpdesk.medicine.wisc.edu
   • Firewalls
     • Managed by DOM, reach out to DOM Helpdesk with questions: https://helpdesk.medicine.wisc.edu
   • Server Virtual Machine
     • Managed by Application Support Team
2. Managing the Print Server
   • Production Environment:144.92.50.112
   • Test Environment: 144.92.50.113
   • Login using your regular UW credentials through your laptops Remote Desktop while on the VPN
   • Current Version is Windows Server 2019
3. The Bartender License
   • Through the company Seagull (https://www.seagullscientific.com/)
     • Support Number: 2V-0D64Q-KC4QK-ZKJE
   • Our license cost is based on the number of printers that we have (currently 3)
   • We have the Enterprise Edition License
4. Using Bartender Label Designer to design Bartender Labels
   • When to update labels: When updating a printer label design because of needed changes or creating a new label design
   • How to design labels: 
     • Done with 'Bartender Designer'
     • The size/dimensions of the label are managed with Page Setup - this is the critical first step to make sure the label is the right size and properly aligned
     • Database Connection Setup controls the data fields expected for the label.
       • You can get a copy of the expected exported data from OnCore
       • You will copy and paste that information into the popup generated after clicking 'Embedded sample data'
       • After clicking next the information is:
         • Encoding: Western European (Windows)
         • Format: Delimited Fields
         • Field Separation: Tab
         • Record Separation: Line Break
       • Click next and finish after selecting 'The first row is a header containing field names'
     • After this you now have the right dimensions and the proper database fields to design your labels
       • You can drag and drop from the top bar to add bar-codes and test boxes to the label
       • After something is added to the label, you can then choose it's data source, font, or barcode type
     • This is ultimately a guess and check process, it is best done on site where you can review the labels immediately after printing.
5. Configuring Bartender Integration
   • What it is used for: This manages the messages that come in from the BSM Listener, and processes them into the printed labels
   • When to update it: This needs changed when adding new labels and adding new printers.
   • How to make updates:
     • Made in the Bartender Integration Builder
     • Make a copy of the current active integration and rename it, then do you work on that new integration file. Do not update the existing one until the new one works.
     • Be on site/communicate with the users that you will be doing integration testing and sending labels to their printers
     • Make sure to use dummy data when working with a test integration, so it is clear that the labels should not be used for subject samples.
     • An integration has two main components
       • Integration portion - handles detecting of label files
       • Action portion - manipulates and executes on label files
         • There are a ton of options for actions, it is best to read through the documentation that Seagull provides
         • Remember that you are manipulating the text file that was passed from Oncore
6. Deploying Bartender Integration
   • Before any new deployments of an integration notify users that there will be a downtime of the bartender system
   • At the start of the downtime, disable the existing integration.
   • After disabling move it to the historical folder and append today's date to the end of the file name
   • The new integration should be in the active folder
   • Deploy the new active integration
   • Check the integration status to ensure it is active
   • Notify end users that the system is back up
7. Configuring Javascript Bar Code Listener tool
   • We have a PDF document provided by Forte with guidance on building the bar code listener here: Barcode Installation Guide
   • Java version to use: JDK 1.8
8. Checking login for Bartender account
   • To verify that the Bartender account is logged in, log into OnCore Production
   • In OnCore, go to the Access Log (Menu -> Admin -> Other Admin -> Access Log)
   • Type 'Bartender' into the search bar, and make sure that there is a login time without a logout time.
   • If there is, the Bartender is listening

Document History

Related Documents

• Link to SOPs
• Link to Controlled Documents