This section describes the setup necessary to support the Atlas SUDS Order Upload process for XML formatted requests. Additional setup maybe needed as specified within the Atlas SUDS Order Download and Atlas Integration Initial Setup topics.
Prerequisites
The following instructions operate under the assumption that the basic support for Atlas Integration is enabled as described within the Atlas Integration Initial Setup section, which details all initial setting required to support the various Atlas Integration processes.
Create Atlas Queue Service
Establish a queue service for the Atlas SUDS Xml Upload within Queue Service Server Setup. This record defines the process and the folders referenced for XML files. Provide the specified options to enable the Atlas queue service.
Figure 15: Queue Service Server Setup
|
Field |
Value |
|
Queue Service System |
MoversSuite Queue Service |
|
Queue Server Name |
Atlas SUDS Xml Upload |
|
Discard All Bad Messages |
Unchecked |
|
Inactive |
Unchecked |
|
Parent Folder for File System Queues |
Provide the base location for downloaded files managed on your system. For example, if you make available a path of D:\QueueService\AtlasMQ, then files within the server for request, retries, and errors are stored on the D: drive within the QueueService\AtlasMQ folder. |
|
Queue Service Server Queue |
Establish roles for a Mirror Queue, Request Queue, Retry Queue, and Error Queue detailed in the following section. |
For the same Atlas SUDS Xml Upload record, create the following roles.
Request Queue Role
Figure 16: Server queue sample within Queue Service Server Setup
|
Field |
Value |
|
Queue Role |
Request Queue (Incoming messages to be processed) |
|
Queue Type |
Microsoft Messaging |
|
Path to the Microsoft Messaging Queue |
Provide the path to the directory for message files to be processed, e.g. .\suds_export_request. This needs to be a public folder so that the MoversSuite API Service running on the network can send messages to this queue. This same path must match what is set for the XML System Option titled AtlasSenderQueueName for the AtlasSuds record within XML System Setup. |
Retry Queue Role
Figure 17: Server queue sample within Queue Service Server Setup
|
Field |
Value |
|
Queue Role |
Retry Queue (Holds messages for later re-processing) |
|
Queue Type |
Microsoft Messaging |
|
Path to the Microsoft Messaging Queue |
Provide the path to the directory for message files to be reprocessed, e.g. .\private$\suds_export_retry. This is generally a private folder within the Microsoft Queuing System folder structure. |
Error Queue Role
Figure 18: Server queue sample within Queue Service Server Setup
|
Field |
Value |
|
Queue Role |
Error Queue (Holds bad messages that cannot be processed) |
|
Queue Type |
Microsoft Messaging |
|
Path to the Microsoft Messaging Queue |
Provide the path to the directory for message files that cannot be reprocessed, e.g. .\private$\suds_export_error. This is generally a private folder within the Microsoft Queuing System folder structure. |
Mirror Queue Role
Figure 19: Server queue sample within Queue Service Server Setup
|
Field |
Value |
|
Queue Role |
Mirror Queue (Send copy of incoming message as is) |
|
Queue Type |
File System Folder |
|
Queue Folder Name |
Provide the sub-directory for initial message files downloaded to your system. This sub-directory lists beneath what is specified for the Parent Folder for File System Queues. For example, if you set this to Data\In and the parent folder is D:\QueueService\AtlasMQ, then the application puts the request files within the D:\QueueService\AtlasMQ\Data\In directory. This folder must also be a directory that the Atlas Sender program is monitoring and the Filter (below) must be compatible to the Search Mask for the Atlas Sender program as well. |
|
Filter |
SUDSUP*.XML |
|
Minimum Message Age |
5000 |
|
Message Type |
XML Messages |