Sage Connection

Overview

Sage Connection Manager is SSIS Connection Manager for establishing Sage SData connections. Use the API to build components based on Sage Connection Manager.

Setup

Use the Sage Connection Manager dialog to specify properties for connecting to Sage SData service.

Server Options

Server

Specify the name or IP address of the Sage data server.

Application

Specify SData application identifier. The following list of identifiers are known:

Id	Application
slx	SalesLogix
sageERP	Accpac (not tested)
crmj	Sage CRM (not tested)
x3	Sage X3 (not tested)

Contract

Specify SData contract identifier. The following list of identifiers are known:

Id	Application
dynamic	SalesLogix
accpac	Accpac
sagecrm	Sage CRM
erp	Sage X3

DataSet

Specify SData DataSet identifier. The following list of identifiers are known:

Id	Application
-	SalesLogix
<company>	Accpac
-	Sage CRM
<company>	Sage X3

User name

Specify user name to access Sage.

Password

Specify password to access Sage.

Time-out (secs)

Specify the number of seconds before timing out session connect. The default value of this property is 100 seconds.

RetainSameConnection

Specify if all clients should use the same connection. This property has the options listed in the following table.

Value	Description
True	All clients use same connection (default).
False	Every client use different connection.

Test Connection

Confirm connection manager configuration by clicking Test Connection.

Proxy Options

Host

Specify the name or IP address of the proxy server. If not specified, proxy server is not used.

Port

Specify the port number on the proxy server to use for the connection.

User name

Specify user name to access the proxy server.

Password

Specify password to access the proxy server.

How to trace the web services calls in use?

You can use the regular .NET network tracing facilities to trace the web services calls. Follow these steps to enable tracing:

1. Go to DTS\Binn folder and open DtsDebugHost.exe.config file in your favorite text editor.
2. Include following settings inside configuration element:
   

       <system.diagnostics>
         <trace autoflush="true" />
         <sources>
           <source name="System.Net" maxdatasize="1024" tracemode="protocolonly">
             <listeners>
               <add name="MyTraceFile" />
             </listeners>
           </source>
         </sources>
         <sharedListeners>
           <add
             name="MyTraceFile"
             type="System.Diagnostics.TextWriterTraceListener"
             initializeData="c:\System.Net.trace.log" />
         </sharedListeners>
         <switches>
           <add name="System.Net" value="Verbose" />
         </switches>
       </system.diagnostics>
   

initializeData attribute controls where the trace log file is saved. Now when you execute a package inside Visual Studio, "c:\System.Net.trace.log" file will contain the web services tracing information. If you want to trace when you execute packages outside Visual Studio, include the settings above in DTExec.exe.config configuration file.

Make sure you comment or remove the tracing settings after you finish testing. Otherwise this may slow down your package execution speed considerably.