Skip to end of metadata
Go to start of metadata

DoveTrack™ TXP/WMS Host Interface Options

Overview

The purpose of this document is to describe the various host interfaces available for use with DoveTrack©®™ TXP/WMS.  The flat file interface is standard.  The other described interfaces are custom quoted.  Also custom quoted are changes to the data content for the flat file interface. 

It is assumed that the customer's host is a WMS, which has location management capabilities.  The DoveTrack©®™ TXP/WMS system executes transactions created by the customer's WMS.

This document does not describe each WMS transaction type and the corresponding DoveTrack©®™ TXP/WMS response, but describes the method of transmitted transactions between systems.

Flat File Interface

The most simple interface between customer's WMS and DoveTrack©®™ TXP/WMS. 

The host WMS creates files of a fixed record length format.  These files are ASCII files with carriage return/ line feed record terminators.  Unix style files may be used, but Dove Tree Canyon Software, must be informed first. 

File Name Conventions

A naming convention must be established.

All file names from WMS should begin with a unique prefix or suffix.  The carousel system will process only files with these names. 

All confirmation files from carousel system will begin with a prefix indicating the type of confirmation records contained with in confirmation file.  These are I(ssue, P(utaway, and C(ycle count.  The date and time stamp are appended to the prefix.  The combination of file contents type and date time stamp creates a unique file name. 

Using Semaphores to Prevent Processing Partially Transferred Files

It is possible for the receiving system to SEE a file before its contents has been completely transferred.

There are two methods 1) name change and 2) semaphore file used to avoid this problem.

Name Change

A dummy file name is used during file transfer. Once the file transfer has complete, the file is renamed. This assures that the data transmission is completed before the receiving system sees file name in directory.

Semaphore File

The receiving system looks for a semaphore file name.  Once a file transfer has completed, an additional file is created by the sending system which use the same file name, but the suffix is changed. The receiving system looks for semaphore file. If it exists this implies that the real data file transfer has completed.

File Transfer Method

There are two preferred methods.

FTP

Both systems will use FTP to transfer files between the two systems. One system will be the server side and the other the client. As a blend it is possible for both sides to be servers. This implies that all files are pushed from one system to the other system.

NFS

The WMS side would be the NFS server and an NFS client would be run on carousel side.  Commercially available packages such as WRQ Reflections NFS Client work well and are easy to setup.

Initiation of File Transfers Between Systems

Files are transferred between systems by the using the above mentioned methods. This still leaves the question as to which side initiates the transfer.

There are three choices 

  1. WMS Pushes and Pulls Files to/from DoveTrack©®™ TXP/WMS
  2. DoveTrack©®™ TXP/WMS Pulls and Pushes Files from/to WMS
  3. WMS pushes flat files to DoveTrack©®™ TXP/WMS and DoveTrack©®™ TXP/WMS pushes confirmation files to WMS

Microsoft Message Queues Interface

Another interface utilizes Microsoft's Message Queue system running under Windows OS. This is a standard product which comes with Windows NT server.  It is VERY reliable.   

The WMS will need to write messages into the MS MQ and DoveTrack©®™ TXP/WMS reads them out.  When transactions complete DoveTrack©®™ TXP/WMS will write into an MS MQ and WMS must read these completion messages. 

The message content must be define in a design document. 

AS400 MQ Interface

Another interface utilizes AS400 MQ system running under OS400. This is a standard product from IBM. It is VERY reliable.

The AS400 WMS will need to write messages into the MQ and DoveTrack©®™ TXP/WMS reads them out. When transactions complete DoveTrack©®™ TXP/WMS will write into an MS MQ and WMS must read these completion messages.

The message content must be define in a design document.

TCP/IP Messaging Interface

Similar to Microsoft Message Queue Interface above, except that instead of using Message Queues the interface uses TCP/IP protocol.   

In order to implement TCP/IP message the design must include who is to be the client and who is to be the server/listener. 

The message content must be define in a design document. 

SQL Table Interface

In this interface the WMS transactions are written into a SQL table located on a database server. DoveTrack©®™ TXP/WMS supports Oracle versions 9 and 10 MS SQL versions 6.5, 7 through 2012. Using ODBC drivers from their respective vendors, we have successfully selected and updated tables in DB/400, Progress, etc.

Completion transactions are written to a separate table which is then read by the WMS.

The table definitions must be defined in a design document.

Labels
  • None