It sounds like you may be using eConnect's Incoming and Outgoing service.
--The eConnect Incoming Service for Microsoft Dynamics GP 2013 integrates
eConnect XML documents into Microsoft Dynamics GP. The Incoming Service uses
a configuration file named eConnect_Incoming.exe.config to control its operations.
This file is typically found in the following location
C:\Program files\Microsoft Dynamics\eConnect 12.0\Service\Incoming Service.
--The eConnect Outgoing Service for Microsoft Dynamics GP allows you to
integrate transaction information originating in Microsoft Dynamics GP into your
application. The Outgoing Service creates XML documents and stores them in a
message queue. Your application must retrieve these messages to use the XML
documents they contain. The Outgoing Service creates a default queue named
machine_name\private$\econnect_outgoing to store outgoing messages.
Typically, you use the Outgoing Service in conjunction with the eConnect
Transaction Requester. You use the Transaction Requester to specify the Dynamics
GP documents you want sent to the message queue. Refer to Transaction Requester
on page 38 section for more information.
The Outgoing Service uses a configuration file named
eConnect_Outgoing.exe.config to control its operations. This file is typically found
in the following location:
C:\Program Files\Microsoft Dynamics\eConnect 12.0\Service\Outgoing
Service\eConnect_Outgoing.exe.config.
