Description

The Datapel WMS can be used to service information to and from websites, handheld Wireless devices, FTP file servers and other sources of transactional information.

Datapel WMS can run “as a service” in order to the process data exchange AUTOMATICALLY – that is – not requiring a USER to manually IMPORT and EXPORT files.

This requires the WMS program to run continuously on the Application or Terminal Server and scan various folders for incoming files and to periodically create data files or exchange data documents with external programs.

Depending on the configuration of the server and the Services being handled the application can STOP operating and may require manual intervention to restart. If a problem occurs and the WMS SERVICE stops and does not recover manual intervention is required.

*supports Import of Check In, Transfers and Checkout. File name prefix and file folder paths must be as per setup in Tools, Preferences, Handheld Tab. File type must be XML or CSV.

Detail Steps

The typical process is as following:

  1. STOP the Service using provided SHORTCUTS
  2. End WMS.EXE process for the wmsservice User Name
  3. Check import folder paths
  4. Clear any possible “corrupt” import files
  5. ENBLE/ALLOW the service using provided SHORTCUTS
  6. START the Service using the SHORTCUT
  7. Verify the service is running.

The steps identified above are covered in more detail below.

ReStarting WMS as a Service (WaaS)

Symptoms:

Remotely created Checkins, Checkouts, Transfers, and/or Sales are not consumed or imported into the required WMS Workspace.

Remedy:

To Restart the WaaS it is important to first stop the service, check for potential configuration or DAT (datafile) errors, and then restart the service.

Before attempting the following steps you should complete the procedure on Stopping the WMS Service. If a restart of the WMS Service fails to work you should following these steps:


Identify if the WMS.EXE is still running in service mode


1. Log in to the Application/Terminal Server as the Administrator and right-click on the taskbar.

2. Choose the Task Manager and select the Processes tab. Make sure to TICK Show processes from all users.

3. Click on the Image Name to sort by process names and locate the WMS.EXE entry with User Name of wmsservice.

If the entry can not be found then the WMS as a SERVICE is not currently loaded – follow the procedure on Starting the WMS as a Service.

If the entry is located it must be stopped prior to restarting. It is assumed that you have already attempted to stop the WMS Service by following procedure “Stopping the WMS Service”.

Typically the WMS as a Service program requires between 25MB to 50MB to operate – if the Mem Usage is reported below 10MB then it is most likely the service has failed and not recovered.

4. Click on this Entry then choose End Process by either right clicking on the image name or clicking the End Process command button.

5. Choose Yes to confirm ending the process.


Check FileSystem Paths and access privileges

The (WaaS) can sometimes fail if the information it was processing was corrupt or if the environment causes a file system failure. It is important to verify the network paths are accessible by the WMSSERVICE user especially in the case where for example the source of transaction file is on a different computer system (e.g. FTP Server on a different computer.).

1. Login to the Application/Terminal Server as WMSService User. This is the WINDOWS USER created by your Datapel Partner expressly for running the WaaS application. Login normally to the WMS as superuser and choose tools – preferences.

2. Select the Handheld options tab.

3. Copy the path from the option “Handheld Import Folder” and paste this into the Windows Start – Run. A folder should open.

This folder contains all files that have been sent from other remote sources to be imported by the WaaS. If the folder can not be opened and Windows reports a Folder error you need to contact your IT Administrator and correct the issue ASAP.

If the path opens make sure you can copy a TEST.TXT file into the folder, EDIT it, MOVE it to the PROCESSED FOLDER, then DELETE the file. If this all appears to complete successfully you can progress to the next step.

Checking for “CORRUPT” transaction files 

The following steps are followed to correct possible service issues being created by corrupt DAT files.

Typically the IMPORT folder contains:

DAT files – the raw data sent to the WMS for conversion into an XML Data file. CFM file – this is a CONFIRMATION file and indicates to the WaaS that the DAT file is ready to be imported. XML files – the processed data ready to be imported into the WaaS application.

The format of the files is XX-NNNNNNNN.DAT where NNNNNNNNN is a unique number based on the TIME and DATE STAMP. The XX can be CI/CO/TF or any other combination depending on the transaction type.

For example CI-090115105815.DAT is a CHECK IN.

No other files should be placed in this folder.

CFM/DAT Files are processed every 4 to 5 minutes and if DAT files have MODIFIED DATE(s) older than this the service is not running correctly. The folder should clear automatically and move the ALL processed files into the PROCESSED folder.

It is recommended you create a SHORT-CUT on the desktop of the WMSSERVICE user that allows frequent checking of the IMPORT folder – if a file list begins to accumulate then the service may have stopped or a DAT file corrupt.

Corrupt DAT/CFM files are USUALLY but not always the ONLY files left in the import folder.

By checking the PROCESSED folder MODIFIED DATE the last processing cycle time can be checked.

If the last processed file is more current than the files still in the OUT folder AND you have checked back after 10mins then the DAT/CFM files are most likely corrupt and need to be REMOVED.

If the CFM or DAT files are 0 bytes then they are corrupt and need to be REMOVED.

Only remove files if they appear corrupt OR after a long period they are not cleared automatically by the WaaS.

To REMOVE files – Move BOTH the CFM and DAT files (and XML if exists) to a Problem or Archive folder. If an XML file also exists with the same file name this MUST also be moved. You can OPEN the XML file and check the time stamp of the Transaction after it has been moved.

Once problem file sets (CFM/DAT/XML) have been removed from the import folder restart the WMS Service and check back to see if the imports begin and the files cleared to the PROCESSED folder.

Starting/Stopping the WaaS application

In order to Start the WaaS you need to run a special SHORTCUT on the desktop. Typically there are two operations required – Enable the WaaS (ALLOW SERVICE) and then Start the WaaS (START SERVICE).

There is also a third SHORTCUT called Disable/Stop WaaS (STOP SERVICE).

Typically these actions are linked to a Windows Scheduled Task to automatically manage the starting and stopping of the WaaS process each day.

To Start the Service:

  1. Double-Click Enable WaaS shortcut.
  2. Double-Click Start WaaS shortcut.

To Stop the Service:

  1. Double-Click Disable WaaS shortcut.

Verify the service is running or stopped:

  1. Right Click on the taskbar.

Choose Task Manager

Look for WMS.EXE against User Name WMSSERVICE.

If the process exists it is running otherwise it has been stopped.

Related Information

None