XmlSystemOptions Settings for SIRVA

External Application Integration > SIRVA Hub Integration with MoversSuite > SIRVA Hub Order Upload and Download > Initial Administrative Setup for SIRVA

XmlSystemOptions Settings for SIRVA

In addition to the sHub settings described in the SIRVA sHub Port and Location Configurations section, the following settings will need to be made within the XmlSystemOptions table for each system (SIRVA Request Download and SIRVA Registration Upload).

Note: If your system is providing both a SIRVA Hub upload and a download, then each option listed below will need to be defined for each, i.e. a WebServiceURL must be defined for both SIRVA Registration Download and SIRVA Registration Upload, unless otherwise noted.

XmlSystemOptions Name	Description and Example XmlSystemValue
EchoReceiveLocation	For debugging only: This serves as a directory location where a registration request can be copied prior to sending to sHub Local Listener. Example: “E:\mss\WebService\bin\EchoSirvaResponse” NOT REQUIRED FOR EITHER PROCESS
LocalListenerErrorLog	Error log file of the sHub Local Listener. Example: “C:\sHub_Local_Listener\files\logs\errorlog.log” REQUIRED FOR UPLOADS ONLY
QueueName	The address to a public Microsoft Message Queue (MSMQ) that the MoversSuite web service uses to communicate with BizTalk. Example: “.\SIRVARegistrationRequest” REQUIRED FOR DOWNLOADS ONLY
SirvaAgentID	SIRVA Hub issued agent identifier for configuring sHub. Example: “1234567” If needed, multiple SirvaAgentIDs can be listed in this field with semicolons between each entry. Each SirvaAgentID in the list must be pre-appended with the van line code associated with the agent. Example: “A:1234567;N:7654321;”
SirvaBadXmlDirectory	Directory path of where the sHub Local Listener stores order registration responses from sHub mainframe. Example: “C:\sHub_Local_Listener\files\BadXMLFiles\” REQUIRED FOR UPLOADS ONLY
SirvaProcessID	SIRVA-issued identifier that signifies a registration upload or download operation. Example: “123456” If needed, multiple SirvaProcessIDs can be listed in this field with semicolons between each entry. Each SirvaProcessID in the list must be pre-appended with the van line code associated with the process. Example: “A:1234567;N:7654321;”
SirvaReceiveLocation	Directory path of where the sHub Local Listener stores order registration responses from sHub mainframe. Example: “C:\sHub_Local_Listener\files\in\” REQUIRED FOR UPLOADS ONLY
SirvaSendLocation	Directory path of where the sHub Local Listener looks for order registration requests that need to be sent to sHub mainframe. Example: “C:\sHub_Local_Listener\files\data\” REQUIRED FOR UPLOADS ONLY
WebServiceURL	URL of the MoversSuite SIRVA Hub web service, used to communicate with the sHub Local Listener. Example: “http://MoversSuite/MSSExternalInterface/Sirva.asmx”