Microsoft Dynamics™ GP

eConnect Installation and Administration Guide

Release 10.0
Copyright Copyright © 2007 Microsoft Corporation. All rights reserved.

Complying with all applicable copyright laws is the responsibility of the user. Without limiting the
rights under copyright, no part of this document may be reproduced, stored in or introduced into
a retrieval system, or transmitted in any form or by any means (electronic, mechanical,
photocopying, recording, or otherwise), or for any purpose, without the express written
permission of Microsoft Corporation. Notwithstanding the foregoing, the licensee of the software
with which this document was provided may make a reasonable number of copies of this
document solely for internal use.

Trademarks Microsoft, Microsoft Dynamics, Visual Basic, Visual Studio, BizTalk Server, Windows, Windows
Vista, and Windows Server are either registered trademarks or trademarks of Microsoft
Corporation or its affiliates in the United States and/or other countries.

The names of actual companies and products mentioned herein may be trademarks or registered
marks - in the United States and/or other countries - of their respective owners.

Unless otherwise noted, the example companies, organizations, products, domain names, e-mail
addresses, logos, people, places, and events depicted herein are fictitious. No association with
any real company, organization, product, domain name, e-mail address, logo, person, place, or
event is intended or should be inferred.

Intellectual property Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual
property rights covering subject matter in this document. Except as expressly provided in any
written license agreement from Microsoft, the furnishing of this document does not give you any
license to these patents, trademarks, copyrights, or other intellectual property.

Warranty disclaimer Microsoft Corporation disclaims any warranty regarding the sample code contained in this
documentation, including the warranties of merchantability and fitness for a particular purpose.

Limitation of liability The content of this document is furnished for informational use only, is subject to change without
notice, and should not be construed as a commitment by Microsoft Corporation. Microsoft
Corporation assumes no responsibility or liability for any errors or inaccuracies that may appear
in this manual. Neither Microsoft Corporation nor anyone else who has been involved in the
creation, production or delivery of this documentation shall be liable for any indirect, incidental,
special, exemplary or consequential damages, including but not limited to any loss of anticipated
profit or benefits, resulting from the use of this documentation or sample code.

License agreement Use of this product is covered by a license agreement provided with the software product. If you
have any questions, please call the Microsoft Dynamics GP Customer Assistance Department at
800-456-0025 (in the U.S. or Canada) or +1-701-281-6500.

Publication date April 2007 -- Last updated April 16, 2007

Contents
Introduction ................................................................................................................................................. 2
What’s in this manual...................................................................................................................................2
Symbols and conventions ............................................................................................................................2
Product support ............................................................................................................................................3

Part 1: eConnect Basics .............................................................................................................. 6

Chapter 1: eConnect Overview ................................................................................................ 7
What is eConnect?.........................................................................................................................................7
What eConnect can do .................................................................................................................................7
Getting started...............................................................................................................................................8

Chapter 2: eConnect Architecture...................................................................................... 11

Architecture diagram ................................................................................................................................. 11
Configurations.............................................................................................................................................12
Business objects ...........................................................................................................................................13
eConnect API ...............................................................................................................................................14
BizTalk ..........................................................................................................................................................15
Transaction Requester ................................................................................................................................15
Replication Service......................................................................................................................................17

Part 2: Installation .......................................................................................................................... 20

Chapter 3: Prerequisites.............................................................................................................. 21
Operating system ........................................................................................................................................21
Microsoft .NET 2.0 Framework.................................................................................................................21
COM+ user account....................................................................................................................................21
Distributed Transaction Coordinator (DTC)...........................................................................................22
Functional currency ....................................................................................................................................24
Microsoft Message Queueing (MSMQ) ...................................................................................................25

Chapter 4: eConnect Installation ........................................................................................ 27

Installation procedure ................................................................................................................................27
What to do next ...........................................................................................................................................29

Part 3: Administration ............................................................................................................... 32

Chapter 5: Configuring eConnect Services............................................................... 33
Overview......................................................................................................................................................33
Incoming Service.........................................................................................................................................33
Outgoing Service.........................................................................................................................................36
Replication Service......................................................................................................................................39
Transaction Requester ................................................................................................................................42
BizTalk adapter............................................................................................................................................44

Chapter 6: Maintenance .............................................................................................................. 51

ECONNECT INSTALLATION AND ADMINISTRATION GUIDE i

C O N T E N T S

Modifying an eConnect installation.........................................................................................................51

Completing a repair....................................................................................................................................52
Removing eConnect....................................................................................................................................53

Chapter 7: Utilities ........................................................................................................................... 55

eConnect Requester Setup Tool ................................................................................................................55
eConnect MSMQ Control ..........................................................................................................................55
eConnect Release Information ..................................................................................................................57

Chapter 8: Troubleshooting...................................................................................................... 59
Functional currency ....................................................................................................................................59
Connection string problems ......................................................................................................................59
Login problems ...........................................................................................................................................59
Incoming or Outgoing Services ................................................................................................................60
eConnect event log......................................................................................................................................60
Incoming Service problems .......................................................................................................................61
COM+ application ......................................................................................................................................61

Glossary ......................................................................................................................................................... 63

Index ................................................................................................................................................................... 65

ii E C O N N E C T I N S TA L L A T I O N A N D A D M I N I S TR A T I O N G U I D E
INTRODUCTION
Introduction
Welcome to eConnect for Microsoft Dynamics™ GP. This documentation explains
how to install and administer eConnect. An eConnect installation includes files,
tools, and services that allow applications to integrate with Microsoft Dynamics GP.
Before you begin installing and using eConnect, take a few moments to review the
information presented here.

What’s in this manual

The Microsoft Dynamics GP eConnect Installation and Administration Guide is
designed to give you an in-depth understanding of how to install and administer
eConnect. Information is divided into the following parts:

• Part 1, eConnect Basics, provides an overview of eConnect and the components

it supplies to help other applications integrate with Microsoft Dynamics GP.

• Part 2, Installation, describes how to install eConnect or the eConnect runtime.

• Part 3, Administration, explains how to configure and maintain eConnect.

To learn about creating applications that use eConnect for Microsoft Dynamics GP,
refer to the eConnect Programmer’s Guide and Reference document.

Symbols and conventions

To help you use this documentation more effectively, we’ve included the following
symbols and conventions within the text to make specific types of information
stand out.

Symbol Description
The light bulb symbol indicates helpful tips, shortcuts,
and suggestions.

Warnings indicate situations you should be aware of

when completing tasks.

Margin notes summarize Margin notes call attention to critical information and
important information. direct you to other areas of the documentation where
a topic is explained.

Convention Description
Part 1, eConnect Basics Bold type indicates a part name.
Chapter 1, “Overview” Quotation marks indicate a chapter name.
Installing eConnect Italicized type indicates a section name.
using System.IO; This font is used to indicate script examples.
Microsoft Message Acronyms are spelled out the first time they’re used.
Queuing (MSMQ)
TAB or ALT+M Small capital letters indicate a key or a key sequence.

2 E C O N N E C T I N S TA L L A T I O N A N D A D M I N I S TR A T I O N G U I D E
 IN T RO D U C T IO N

Product support
Microsoft Dynamics GP technical support can be accessed online or by telephone.
Go to www.microsoft.com/Dynamics and click the CustomerSource or
PartnerSource link, or call 888-477-7877 (in the US and Canada) or 701-281-0555.

ECONNECT INSTALLATION AND ADMINISTRATION GUIDE 3

4 E C O N N E C T I N S TA L L A T I O N A N D A D M I N I S TR A T I O N G U I D E
PART 1: ECONNECT BASICS
 Part 1: eConnect Basics
This portion of the documentation contains introductory information you should
know before deploying eConnect for Microsoft Dynamics GP. The following
information is discussed:

• Chapter 1, “eConnect Overview,” introduces eConnect and the types of

integration interfaces and tools it provides.

• Chapter 2, “eConnect Architecture,” discusses the underlying components that

are part of an eConnect installation.

6 E C O N N E C T I N S TA L L A T I O N A N D A D M I N I S TR A T I O N G U I D E
Chapter 1: eConnect Overview
eConnect for Microsoft Dynamics GP allows you to integrate your business
applications with Microsoft Dynamics GP. The following topics introduce eConnect
for Microsoft Dynamics GP:

• What is eConnect?
• What eConnect can do
• Getting started

What is eConnect?
eConnect is a collection of tools, components, and interfaces that allow applications
to programmatically exchange data with Microsoft Dynamics GP. The key eConnect
components and interfaces include:

• A .NET managed code assembly

• A Microsoft BizTalk® Application Integration Component (AIC)
• Microsoft Message Queuing (MSMQ) services

These eConnect interfaces allow external applications like web storefronts, web
services, point-of-sale systems, or legacy applications to integrate with Microsoft
Dynamics GP. The external applications can perform actions like creating, updating,
retrieving, and deleting back office documents and transactions.

Throughout the documentation, the terms front office and back office are used. The term
back office refers to the financial management system, in this case, Microsoft Dynamics GP.
The term front office refers to customer relationship management systems, data warehouses,
web sites, or other applications that communicate with the back office.

eConnect allows you to leverage the existing transaction-based business logic of

Microsoft Dynamics GP. This allows you to focus your time and energy on creating
or enhancing custom applications for the front office.

What eConnect can do

eConnect allows you to enhance your applications in the following ways:

1. Add real-time access to Dynamics GP data.

eConnect provides real-time access to back office data. It offers a way to add up-
to-date back office information to existing front office applications like web
storefronts or service applications.

2. Share financial management data across applications.

eConnect allows multiple applications to share financial management data. The
eConnect interfaces can support multiple independent applications. Changes to
financial data in Dynamics GP are simultaneously available to all applications
that use eConnect to access that data in Dynamics GP.

Application developers who use eConnect obtain the following benefits:

1. Reduce development time.

eConnect has a large number of integration points for Microsoft Dynamics GP.
Software developers can quickly add back office integrations to an application.
This simplifies the development effort, while providing fast access to Microsoft

ECONNECT INSTALLATION AND ADMINISTRATION GUIDE 7

PA RT 1 E C O N N E C T B A S I C S

Dynamics GP data. eConnect also reduces development time when the business
logic contained in the back office is reused by new custom applications.

An eConnect integration also reduces data re-entry. An automated eConnect

integration between Microsoft Dynamics GP and a new or existing online
storefront, web service, or other data source eliminates the time and cost of
manually copying data.

2. Use existing development tools.

eConnect allows software developers to select their tool of choice when
working with eConnect. Developers can use Microsoft .NET, Microsoft SQL
Server stored procedures, BizTalk, or MSMQ.

3. Leverage industry-standard technologies.

eConnect includes components for MSMQ and BizTalk Server, which are
industry-standard tools that support integration between applications.

4. Use XML to transfer data.

eConnect uses XML documents to move data into and out of Microsoft
Dynamics GP. The XML documents are a text-based representation of back
office data. An XML schema specifies the data that is included in each type of
XML document. This allows eConnect to provide back office integration to any
application capable of creating or consuming these XML documents.

Getting started
How you start depends on your role:

System administrator
If you are the system administrator, complete the following:

• Review Chapter 2, “eConnect Architecture,” to understand the components that

comprise an eConnect installation. This information can help you to understand
how eConnect will fit with your existing systems.

• Review Chapter 3, “Prerequisites,” to determine whether your system has all

the prerequisites for eConnect. You may need to install some additional
software or configure Dynamics GP before installing eConnect.

• Review Chapter 4, “eConnect Installation,” to acquaint yourself with the

eConnect installation procedure.

• Review Chapter 5, “Configuring eConnect Services,” to understand the

configuration files used to control eConnect’s Windows services and BizTalk
adapter. You control the behavior of the services and adapter by changing the
values stored in the configuration files.

• Review Chapter 6, “Maintenance,” to learn what you can do to revise, repair, or

remove an existing eConnect installation.

Software Developer
If you are a developer, complete the following:

8 E C O N N E C T I N S TA L L A T I O N A N D A D M I N I S TR A T I O N G U I D E
 C H A P T E R 1 E C O N N E C T O V E R V I E W

• Review Chapter 2, “eConnect Architecture,” to familiarize yourself with

eConnect’s components. You need to understand how eConnect’s components
work together to meet your integration requirements.

• Discuss the installation procedure with the system administrator to learn what
configuration settings were used during the eConnect installation.

• Review the eConnect Programmer’s Guide and Reference document. The

document describes eConnect’s tools, application programming interfaces
(APIs), and XML schemas. Use the eConnect Programmer’s Guide and
Reference to learn how eConnect meets your application integration
requirements.

ECONNECT INSTALLATION AND ADMINISTRATION GUIDE 9

10 E C O N N E C T I N S TA L L A T I O N A N D A D M I N I S TR A T I O N G U I D E
Chapter 2: eConnect Architecture
When using eConnect for Microsoft Dynamics GP, it is helpful to understand its
architecture. Architectural information is divided into the following sections:

• Architecture diagram
• Configurations
• Business objects
• eConnect API
• BizTalk
• Transaction Requester
• Replication Service

Architecture diagram
eConnect installs a collection of components that work together to provide
programmatic access to Microsoft Dynamics GP data. The following diagram
illustrates the basic components:

Integrating
Applications
XML XML

BizTalk MSMQ Transaction Replication

Server Requester Service
XML
XML XML

BizTalk Incoming Outgoing

Adapter Service Service

Runtime
Layer .NET Assemblies

COM+ Object

Business Objects

Pre SQL stored procedures Post

Data Access
Layer
Microsoft
Dynamics GP

ECONNECT INSTALLATION AND ADMINISTRATION GUIDE 11

PA RT 1 E C O N N E C T B A S I C S

The diagram illustrates eConnect’s two key layers and the components each layer
contains.

• The data access layer contains the eConnect business objects. The business
objects are installed on the Microsoft Dynamics GP server.

• The eConnect runtime layer contains the components that simplify using the
eConnect business objects. The eConnect runtime layer installs on the same
computer as the integrating application.

The eConnect runtime includes several components that allow you to access the
eConnect business objects.

• The eConnect application programming interfaces (APIs) allow you to

programmatically interact with the eConnect business objects using eConnect
XML documents. The eConnect API include a .NET and a MSMQ interface.

• The eConnect BizTalk adapter allows you to use BizTalk to configure and
manage the integration between your application and Microsoft Dynamics GP

• The Transaction Requester allows you to publish Microsoft Dynamics GP

documents to a queue. You typically use the Transaction Requester with the
Outgoing Service to publish specified Microsoft Dynamics GP documents as
eConnect XML documents. The Transaction Requester identifies the specific
transactions the Outgoing Service needs to publish.

• The Replication Service allows you to replicate transactions that occur in

Microsoft Dynamics GP to another database.

The diagram also shows that your integrating application can bypass the eConnect
runtime and use the eConnect business objects directly.

Configurations
There are two common configurations for an eConnect installation. The following
illustration shows the most common configuration for eConnect. In this
configuration, the eConnect runtime is installed on a separate server, and accesses
the SQL Server that manages Microsoft Dynamics GP data over the local network.
To obtain optimal performance, you should use the two server configuration
whenever possible.

Local Network

Integrating application SQL Server with

+ Dynamics GP Data
eConnect API +
eConnect COM+ Application eConnect Business
eConnect Transaction Requester Objects
eConnect Replication Service

12 E C O N N E C T I N S TA L L A T I O N A N D A D M I N I S TR A T I O N G U I D E
 C H A P T E R 2 EC O N N EC T A R C HI TE C T U R E

An alternate configuration installs the eConnect runtime on the Microsoft Dynamics

GP server. This is shown in the following illustration:

SQL Server with

Dynamics GP Data
eConnect Business Objects
+
eConnect API
eConnect COM+ Application
eConnect Transaction Requester
eConnect Replication Service
Integrating Application

Which configuration you choose will depend on what types of integration you
need, and what server resources you have available. eConnect can also be part of a
BizTalk integration. Refer to BizTalk documentation for information about the types
of configurations possible with BizTalk Server.

Business objects
The most basic eConnect components are known as business objects. The eConnect
business objects are a collection of SQL stored procedures. The eConnect stored
procedures are added to the system database (DYNAMICS) during the initial
installation of Microsoft Dynamics GP. The eConnect stored procedure are also
included when you create a new company using Microsoft Dynamics GP Utilities.

The stored procedures contain the business logic used by eConnect. In addition, the
stored procedures validate the data and supply default values. Any eConnect action
that queries, creates, updates, or deletes data from Dynamics GP uses one or more
of these stored procedures.

The eConnect business objects include Dynamics GP documents and transactions

that are commonly used in application integration. While eConnect supplies a large
number of documents, not every Dynamics GP feature is available through
eConnect.

See the eConnect You cannot modify eConnect stored procedures. However, eConnect provides an
Programmer’s Guide alternative that allows you to customize its business logic. Each stored procedure
and Reference for includes specially named pre and post stored procedures. You customize
information about eConnect’s business logic by adding SQL queries and commands to these pre and
customizing business post procedures. The pre stored procedure runs your custom code immediately
logic. before the eConnect stored procedure, while the post stored procedure runs
immediately after the eConnect stored procedure.

ECONNECT INSTALLATION AND ADMINISTRATION GUIDE 13

PA RT 1 E C O N N E C T B A S I C S

The following diagram illustrates the relationship between an eConnect stored

procedure and its pre and post stored procedures:

Start

stored procedure The eConnect stored

called procedure cannot be
modified.

executes pre executes post

stored procedure stored procedure

“Pre” stored eConnect stored “Post” stored

procedure procedure procedure

For example, assume you want to modify the business logic for the eConnect stored
procedure named taSopHdrIvcInsert. You complete this modification by adding
custom SQL code to the stored procedure named taSopHdrIvcInsertPost. Your
custom code will run immediately after every execution of the taSopHdrIvcInsert
procedure. To run custom code prior to the execution of the taSopHdrIvcInsert
procedure, place the custom SQL code in the stored procedure named
taSopHdrIvcInsertPre.

Once eConnect installs its business objects, the stored procedures are available on
the server and can be utilized by your application. However, a direct call to an
eConnect stored procedure requires you to:

• Create a connection to the database server.

• Implement security restrictions to prevent unauthorized use of your database
connection.
• Implement transaction management to commit or rollback changes.
• Identify and handle error conditions.
• Update your application whenever changes are made to the parameters for the
stored procedure.

To avoid the extra work of direct calls to the stored procedures, use one of the APIs
that eConnect supplies. These API provide a simpler approach to using the
eConnect business objects.

eConnect API
eConnect provides a collection of APIs that interact with the business objects. There
are APIs for Microsoft .NET, and Microsoft Message Queuing (MSMQ). These
eConnect APIs allows you to use the interface that best fits your integration project
and the available development tools.

To support its API, eConnect supplies a COM+ application that manages interaction
with the eConnect business objects. The COM+ application installs in Component
Services of the computer where you installed the eConnect runtime. The COM+
application requires a user logon. The logon must have sufficient privileges (i.e. be
assigned to DYNGRP) to access the Dynamics GP databases on your SQL server.

14 E C O N N E C T I N S TA L L A T I O N A N D A D M I N I S TR A T I O N G U I D E
 C H A P T E R 2 EC O N N EC T A R C HI TE C T U R E

Schema information To use the eConnect API, your application must create or read eConnect XML
can be found in the documents. eConnect supplies XML schema to specify the contents of each
eConnect document.
Programmer’s Guide
and Reference A schema is an XML file (with typical extension .xsd) that describes the syntax and
semantics of XML documents using a standard XML syntax. An XML schema
specifies the content constraints and the vocabulary that compliant documents must
accommodate.

The eConnect business objects validate documents against the schema and reject
documents that do not comply.

The COM+ application supports the following APIs:

Microsoft .NET
eConnect installs .NET assemblies on your computer and adds them to the global
assembly cache. The assemblies use the COM+ application to access the eConnect
business objects. To use eConnect in a .NET development project, add references to
these assemblies.

MSMQ
The MSMQ API uses MSMQ queues and Windows services to asynchronously
transport data between your application and Microsoft Dynamics GP. Your
application must be able to access the queues used by the services. Both the
Incoming and Outgoing services use the COM+ application to access the eConnect
business objects.

To use the eConnect Incoming Service, create an XML document and place it in the
specified queue. The Incoming Service monitors that queue and periodically
processes the valid XML documents stored in the queue.

The eConnect Outgoing Service relies on SQL triggers and the business objects to
retrieve specified eConnect documents. The service stores the documents in a
specified queue. Your application must monitor the queue, retrieve the supplied
documents, and perform its actions based on the data in the documents.

BizTalk
eConnect provides a BizTalk adapter is an application integration component (AIC)
that you can install on your BizTalk 2004 or BizTalk 2006 server. The BizTalk adapter
allows you to use BizTalk to manage interaction with eConnect business objects.

The BizTalk adapter supports the use of eConnect as a part of a BizTalk

orchestration or in a simple pass-through situation.

Transaction Requester
The Transaction Requester is a collection of SQL database tables and database
triggers that eConnect uses to make Dynamics GP data changes available to other
applications.

ECONNECT INSTALLATION AND ADMINISTRATION GUIDE 15

PA RT 1 E C O N N E C T B A S I C S

The following diagram illustrates the Transaction Requester:

An application creates MSMQ

a new record.

The Outgoing Service

queries the eConnect_Out
Outgoing table. XML representing
Service the new record is sent to
the eConnect outgoing
queue in MSMQ.

Microsoft Dynamics GP eConnect_Out

database table

The Transaction
Requester’s SQL trigger
reacts to the record’s
creation, and inserts an
entry to the eConnect_Out
table.

The Transaction Requester supports other eConnect services that export data from
Dynamics GP to other applications.

When eConnect installs the Transaction Requester, it creates three tables in each
specified Dynamics GP database:

• eConnect_Out This table stores data from selected create, update, or delete
operations that occur within Microsoft Dynamics GP. The data identifies the
individual transactions that occurred. Other eConnect services use the data in
the table to create messages that can be used to integrate Dynamics GP data
with other applications.

• eConnect_Out_Setup This table contains configuration information for

the Transaction Requester. To keep the Transaction Requester working, do not
make changes to this table.

• eConnectOutTemp This table is a temporary data store.

To configure the eConnect Transaction Requester, use the eConnect Requester Setup
Tool. The eConnect Requester Setup Tool allows you to specify Dynamics GP
objects and operations you want to export to another application. The utility then
adds SQL triggers to Dynamics GP that populate the eConnect_Out table for the
specified objects and operations. For a detailed explanation of how to configure the
Transaction Requester, see Transaction Requester on page 42.

For example, assume you want an external application to be updated when a new
customer is added to Microsoft Dynamics GP. To begin, use the eConnect Requester
Setup Tool to specify the customer object and the SQL insert operation. The
eConnect Requester Setup Tool adds a SQL trigger to the database. When a new
customer record is inserted, the SQL trigger creates a record of the event in the
eConnect_Out table.

16 E C O N N E C T I N S TA L L A T I O N A N D A D M I N I S TR A T I O N G U I D E
 C H A P T E R 2 EC O N N EC T A R C HI TE C T U R E

The eConnect Outgoing Service periodically queries the eConnect_Out table. The
service uses the record in the table to create an XML document that describes the
new customer transaction.

The Outgoing Service then places the XML document in a message queue where it
can be retrieved and used to notify the external application.

Replication Service
eConnect includes the Replication Service that copies selected data changes from
Microsoft Dynamics GP to a specified target database. The Replication Service
asynchronously updates the target database to reflect changes made in Dynamics
GP.

To use the Replication Service, the target database must have the same table structure as the
Microsoft Dynamics GP database.

The following diagram illustrates the Replication Service:

An application creates a new

record in Microsoft Dynamics GP.

Microsoft Dynamics GP
database
The Transaction Requester’s SQL
trigger reacts to the record’s
creation, and inserts an entry to
the eConnect_Out table. eConnect_Out
table

The Outgoing Service queries the

eConnect_Out table, retrieves the
data, creates an XML document, Outgoing
Service
and places the document in the
eConnect outgoing queue.
XML

MSMQ eConnect
Outgoing queue

The Replication Services retrieves XML

the XML document from the
eConnect outgoing queue and Replication
Service
inserts the new data into the
specified external application
database.

External application
database

The data from the record created

in Microsoft Dynamics GP is visible
in the external application.

ECONNECT INSTALLATION AND ADMINISTRATION GUIDE 17

PA RT 1 E C O N N E C T B A S I C S

The Replication Service uses many of eConnect’s other components and interfaces:

• The Transaction Requester specifies the documents and transactions to

replicate.

• The eConnect Outgoing Service creates the XML documents from the
information provided by the Transaction Requester Service. It places them in
the Outgoing queue in MSMQ.

• The eConnect Replication Service takes the documents from the Outgoing
Queue and uses the data to replicate the transaction directly into the external
application’s database.

Since the Replication Service performs a specific task, it does not provide an API.
You cannot programmatically customize the Replication Service. Before starting the
Replication Service, you must configure the service. For a detailed explanation of
how to configure the Replication Service, see Replication Service on page 39.

18 E C O N N E C T I N S TA L L A T I O N A N D A D M I N I S TR A T I O N G U I D E
PART 2: INSTALLATION
 Part 2: Installation
This portion of the documentation explains how to install eConnect for Microsoft
Dynamics GP. The following information is discussed:

• Chapter 3, “Prerequisites,” describes the software required and the actions you
must perform before you install eConnect for Microsoft Dynamics GP.

• Chapter 4, “eConnect Installation,” describes the process to install eConnect.

20 E C O N N E C T I N S TA L L A T I O N A N D A D M I N I S TR A T I O N G U I D E
Chapter 3: Prerequisites
Before installing eConnect for Microsoft Dynamics GP, there are several
prerequisites you must check. This portion of the documentation describes the
software requirements and the additional steps to perform before installing
eConnect. The following topics are discussed:

• Operating system
• Microsoft .NET 2.0 Framework
• COM+ user account
• Distributed Transaction Coordinator (DTC)
• Functional currency
• Microsoft Message Queueing (MSMQ)

Operating system
To install eConnect, the computer must be running one of the following operating
systems:

• Windows XP Professional
• Windows Server 2003 and Windows Server 2003 R2
• Windows Small Business Server 2003
• Windows Vista Enterprise
• Windows Vista Business
• Windows Vista Ultimate
• Windows Server 2003 x64 Edition
• Windows Server 2003 for Itanium-based Systems

Microsoft .NET 2.0 Framework

eConnect requires the Microsoft .NET 2.0 Framework. The eConnect installer
verifies that the Microsoft .NET 2.0 Framework is installed on your computer. If the
framework is not found, the eConnect installer stops and instructs you to install the
Microsoft .NET 2.0 Framework.

COM+ user account

The eConnect COM+ application uses SQL Server integrated security to connect to
the eConnect business objects. During the installation of eConnect, you need to
supply a user account for the COM+ application. To set up the user account,
complete the following procedure:

1. Select a user account.

Select or create a user account for the eConnect COM+ application.

• If you plan to install eConnect on a different computer than the Dynamics

GP server in a domain environment, select or create a domain user account.

• If you plan to install eConnect on a different computer than the Dynamics

GP server in a workgroup environment, select or create a user on the
Dynamics GP server.

• If you plan to install eConnect on the same server as Microsoft Dynamics

GP, select or create a local user account.

ECONNECT INSTALLATION AND ADMINISTRATION GUIDE 21

PA RT 2 I N S T A LL AT IO N

2. Give the user account database access.

Add the user account you selected or created to the DYNGRP role for the
system (DYNAMICS) database and for each company database that will be
used with eConnect.

When you install eConnect, you will be prompted to supply the credentials for this
user account.

Distributed Transaction Coordinator (DTC)

If eConnect will be running on a different computer than the SQL Server that is
managing Microsoft Dynamics GP data, the Distributed Transaction Coordinator
(DTC) must be active on both systems.

Enabling DTC
For Windows Server 2003 and Windows XP, you enable network DTC through the
Windows Components Wizard. To do this, complete the following procedure:

1. Open Add or Remove Programs.

Choose to add or remove Windows Components. The Windows Components
Wizard will be displayed.

2. Select the Application Server components.

Click Details to display the Application Server Details.

Mark Enable network DTC access. Click OK.

22 E C O N N E C T I N S TA L L A T I O N A N D A D M I N I S TR A T I O N G U I D E
 C H A P T E R 3 PR ER EQ U I SIT E S

3. Complete the changes.

Click Next to complete the changes. Click Finish to close the wizard.

Configuring DTC
If the two computers are in the same domain, the default configuration for DTC can
be used with eConnect. If you have made modifications to the security
configuration for DTC, you must be sure the following settings are used:

• Network DTC Access enabled

• Allow Inbound communications
• Allow Outbound communications
• Mutual Authentication Required (when running in a domain environment)
• No Authentication Required (when running in a Windows workgroup
environment or the client machine is pre-Windows XP SP2)

If the two computers are in a Windows workgroup, or are in domains that do not
have an established trust relationship, update your DTC security configuration to
use No Authentication Required. To configure DTC, complete the following
procedure:

1. Open Component Services.

For Windows XP and Windows Server 2003, use the Start menu to access
Administrative Tools. Choose Component Services.

For Windows Vista™ enter comexp.msc in the search box of the Start menu.

2. Display the MSDTC security settings.

The steps to view the MSDTC security settings depend upon your computer’s
operating system.

Windows XP and Windows Server 2003 Expand the Component

Services node, and then expand the Computer node to display the My
Computer node.

Select the My Computer node. From the Action menu choose Properties. Select
the MSDTC tab, and click the Security Configuration button.

Windows Vista Expand the Component Services node, expand the My

Computer node, and expand the Distributed Transaction Coordinator node.
Select the Local DTC node. From the Action menu, choose Properties. Select the
Security tab.

ECONNECT INSTALLATION AND ADMINISTRATION GUIDE 23

PA RT 2 I N S T A LL AT IO N

3. Review your DTC security settings.

Make the appropriate settings, and click OK.

Functional currency
eConnect requires a functional currency to be set up for Microsoft Dynamics GP,
even if multicurrency is not being used. To set up a functional currency, complete
the following procedure:

1. Open the Multicurrency Setup window in Microsoft Dynamics GP.

Choose Tools >> Setup >> Financial >> Multicurrency from the Microsoft
Dynamics GP menu. Set the Functional Currency. This example designates US
dollars as the functional currency.

Refer to the Microsoft Dynamics GP documentation for additional information

about currency setup and multicurrency access.

2. Complete check links when needed.

If a message prompts you to run check links for the multicurrency table, you
should do so. To run checklinks, open the File menu and select Maintenance >>
Check Links. Select the series and tables to check. Click OK.

24 E C O N N E C T I N S TA L L A T I O N A N D A D M I N I S TR A T I O N G U I D E
 C H A P T E R 3 PR ER EQ U I SIT E S

Microsoft Message Queueing (MSMQ)

Application integrations that use the eConnect Incoming, Outgoing and Replication
services use MSMQ to transport and store XML documents. These XML documents
represent data retrieved from or sent to Microsoft Dynamics GP. You can install
eConnect prior to installing MSMQ, but the eConnect services will not start until
MSMQ is available. To install MSMQ, complete the following procedure:

1. Start the Windows Components wizard.

Open the Add or Remove Programs window. Click Add/Remove Windows
Components.

2. Select Application Server.

In the Windows Components Wizard, select Application Server. Click Details.

3. Select Message Queuing.

Select the Message Queuing check box.

4. Accept the selection.

Click OK to accept the selection. Click Next to begin the installation.

5. Close the wizard.

When the MSMQ install completes, click Finish to close the Windows
Components Wizard.

ECONNECT INSTALLATION AND ADMINISTRATION GUIDE 25

26 E C O N N E C T I N S TA L L A T I O N A N D A D M I N I S TR A T I O N G U I D E
Chapter 4: eConnect Installation
This portion of the documentation describes how to install eConnect for Microsoft
Dynamics GP. The following information is discussed:

• Installation procedure
• What to do next

Installation procedure
To install eConnect, complete the following procedure:

1. Verify the user you are logged in as.

The user you are currently logged in as must be in the Administrator group for
the computer on which you are installing eConnect.

2. Start the eConnect installer.

To install only the eConnect runtime components, start the installer named
eConnectRuntime.exe.

3. Review the license agreement.

After reviewing the license agreement, mark the option to accept the terms.
Click Next to continue.

4. Specify the components to install.

Select the features you would like to install. The list of features reflects the
components you have installed on the server. For example, the option to install
the BizTalk 2006 Adapter is available only when the install detects BizTalk
Server 2006 is present.

When you click a button for a feature, a pop-up menu of options appears. Refer
to the following table for information about each option.

Option What happens

Install this feature. Installs the feature on the local hard disk. This
option installs the feature but not sub
features.
Install entire feature. Installs the feature and all of its sub features.
Do not install feature. Will not install the selected feature. Allows the
feature to be installed later using Add or
Remove Programs.

ECONNECT INSTALLATION AND ADMINISTRATION GUIDE 27

PA RT 2 I N S T A LL AT IO N

To include a feature, click the button and select “Install entire feature.” To
exclude a feature, click the button and select “Do not install feature.”

The install allows you to select from the following features:

BizTalk 2004 Components Installs the files needed to install the BizTalk
2004 application integration component (AIC) adapter.

BizTalk 2006 Components Installs the files needed to install the BizTalk
2006 application integration component (AIC) adapter.

COM+ Components Installs the COM+ application and .NET Assembly in

COM+ Administration. Also registers the .NET Assembly in the global
assembly cache.

Incoming-Outgoing Service Installs the eConnect Incoming Service,

Outgoing Service, and Replication Service into the Service Control Manager.

5. Specify eConnect account information.

Several eConnect components require a user login and password to access the
eConnect business objects. The eConnect Incoming Service, Outgoing Service,
and COM+ application will use this account. Enter the domain\login and
password credentials for the user account you set up as an eConnect
prerequisite. For more information about creating a user account see COM+ user
account on page 21.

The account must be a member of the DYNGRP role in the Microsoft Dynamics GP
system and company databases on your Microsoft Dynamics GP SQL Server.

Click Next to continue.

28 E C O N N E C T I N S TA L L A T I O N A N D A D M I N I S TR A T I O N G U I D E
 C H A P T E R 4 E C O N N E C T I N S T A L L A T I O N

6. Start the installation.

Click Install to begin the installation process. The install will run for several
minutes.

7. Complete the installation.

Once the installation completes, click Exit.

The installation creates the eConnect event log. The log stores all the error,
warning and information messages that eConnect generates. To view the
eConnect event log, open the Start menu and select Control Panel >>
Administrative Tools >> Event Viewer. Click eConnect to view the current list
of messages.

What to do next
After eConnect for Microsoft Dynamics GP has installed, consider taking the
following steps:

• Learn about actions you will need to take to configure and maintain the
eConnect for Microsoft Dynamics GP components you installed. Details are
found in Part 3, Administration.

• To learn about developing applications that use eConnect for Microsoft

Dynamics GP, retrieve and install the eConnect for Microsoft Dynamics GP
Software Development Kit (SDK).

ECONNECT INSTALLATION AND ADMINISTRATION GUIDE 29

30 E C O N N E C T I N S TA L L A T I O N A N D A D M I N I S TR A T I O N G U I D E
PART 3: ADMINISTRATION
 Part 3: Administration
This portion of the documentation explains the configuration and maintenance
options for eConnect for Microsoft Dynamics GP. The following information is
discussed:

• Chapter 5, “Configuring eConnect Services,” describes configuration options

for eConnect services and the BizTalk adapter.

• Chapter 6, “Maintenance,” describes how to make changes to an existing

eConnect installation.

• Chapter 7, “Utilities,” identifies the utilities eConnect supplies to setup and

monitor eConnect.

• Chapter 8, “Troubleshooting,” discusses how to troubleshoot issues that occur

when using eConnect.

32 E C O N N E C T I N S TA L L A T I O N A N D A D M I N I S TR A T I O N G U I D E
Chapter 5: Configuring eConnect Services
After installing eConnect, you may need to configure the eConnect services or the
BizTalk adapter. The following sections describes how to configure these
components:

• Overview
• Incoming Service
• Outgoing Service
• Replication Service
• Transaction Requester
• BizTalk adapter

Overview
The complete eConnect installation adds three Windows services to your
computer’s Service Control Manager. The installer initially configures each service
and stores the configuration information in an XML file. These XML configuration
files contain keys and values that control the operation of each service. To customize
the behavior of a service or to adjust the service to reflect changes in your server
environment, change the values for one or more keys in the configuration file.

Make a backup copy of the configuration file before making any changes. This ensures you
will always be able to restore the service if necessary.

After changing the settings in a configuration file, you must stop and restart the
service. The changes in the configuration file will not be implemented until the
service restarts.

The eConnect install also includes the Transaction Requester that publishes
eConnect XML documents to a specified queue. Use the eConnect Requester Setup
utility to specify which Microsoft Dynamics GP documents to publish.

If you install the eConnect Adapter for BizTalk 2004, you must configure BizTalk
Server 2004 to work with the adapter. You use the BizTalk Server Administration
utility and Visual Studio .NET 2003 to configure the BizTalk server.

Incoming Service
The Incoming Service 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 found in the
eConnect installation location, typically C:\Program files\Common
Files\Microsoft Shared\eConnect 10\Services\Incoming Service.

The following example displays the contents of an eConnect_Incoming.exe.config

file:

<? xml version="1.0"encoding="Windows-1252"?>

<configuration >
<appSettings >
<addkey="eConnect.Incoming_Queue"value=""/>
<addkey="eConnect.Transactional_deadletter_Queue"value="0"/>
<addkey="eConnect.Schema.Type"value=""/>
<addkey="eConnect.Schema"value=""/>

ECONNECT INSTALLATION AND ADMINISTRATION GUIDE 33

PA RT 3 A D M I N IS T R A T I O N

<addkey="eConnect.BackOffice.ConnectionString"value="data
source=MYServer;initial catalog=MyDatabase;integrated
security=SSPI;persist security info=False;packet size=4096"/>
<addkey="eConnect.LogAll"value=""/>
<add key="eConnect.Threads" value="0" />
</appSettings >
</configuration>

The keys are defined as follows:

eConnect.Incoming_Queue This key specifies the message queue that the

service will monitor. The default value is blank.

<addkey="eConnect.Incoming_Queue"value=""/>

The default creates and monitors a queue named machine_name\private$\

econnect_incoming. To use another message queue, set the value to the queue’s
name.

eConnect.Transactional_deadletter_Queue This key specifies where

undeliverable messages are stored. The default value for the key is zero.

<addkey="eConnect.Transactional_deadletter_Queue"value="0"/>

The value “0” stores the undeliverable message in the system’s transactional
deadletter queue.

A value of ”1” stores undeliverable messages in the deadletter queue associated

with the message queue specified by the eConnect.Incoming_Queue key. If the
eConnect.Incoming_Queue key has value="", the service sends undeliverable
messages to machine_name\private$\econnect_incoming_deadletter.

If the eConnect.Incoming_Queue key specifies a queue name, the service sends

undeliverable messages to a queue with a name that appends _deadletter to the
specified queue name. For example, the eConnect.Incoming_Queue key sets
value="machine_name\private$\TestQueue", the service sends undeliverable
messages to the queue named machine_name\private$\TestQueue_deadletter.

eConnect.Schema.Type This key specifies whether to perform schema

validation and the type of schema to use. The default value is blank.

<addkey="eConnect.Schema.Type"value=""/>

A blank key value means there is no schema validation. The other possible values is
XSD. You set the value to XSD when you want to validate an eConnect XML
documents against the eConnect schema.

Schema validation ensures the XML document in the message contains all the
information required for a successful create, update, or delete operation in
Microsoft Dynamics GP. Schema validation verifies the name of each XML node, the
order of each node in the XML document, and the values contained by the node. If
the XML document fails validation, an error is logged in the eConnect event log and
the XML document is discarded.

If you elect not to perform schema validation, the order and name of each XML
node is not verified. When eConnect encounters an XML document that contains a

34 E C O N N E C T I N S TA L L A T I O N A N D A D M I N I S TR A T I O N G U I D E
 C H A P T E R 5 C O N F I G U R I N G E C O N N E C T S E R V I C E S

node with an unrecognized name, the data value for that node is omitted but the
specified operation is allowed to proceed. No log entry is made about the omitted
node. Invalid data values are detected and logged as an error in the eConnect event
log even when schema validation is not performed. XML documents with invalid
data are discarded after logging the error message.

eConnect.Schema This key specifies the location of the XSD schema file. The
default value is blank.

<addkey="eConnect.Schema"value=""/>

A blank key value indicates incoming XML documents will not be validated. If you
have set the eConnect.Schema.Type key to XSD, use this key to supply the path to
the XSD schema file. For example, use value="C:\Program
Files\CommonFiles\Microsoft Shared\eConnect 10\XML Schemas\Incoming XSD
Schemas\eConnect.xsd" to validate against the schema definitions contained in that
XSD file.

eConnect.BackOffice.ConnectionString This key stores the connection

string the service uses to connect to the Microsoft Dynamics GP SQL Server. The
default value is derived from connection string specified during installation.

<addkey="eConnect.BackOffice.ConnectionString"value="data source=MYServer;
initial catalog=MyDatabase;integrated security=SSPI;persist security info=
False;packet size=4096"/>

You change how the connection string works by changing the value parameters. For
example, you may change the data source or initial catalog parameters to reflect
changes in your server configuration.

If you install eConnect on a separate computer from the SQL Server that manages
Microsoft Dynamics GP data, you must change this key’s data source parameter.
The default configuration assumes a single server install. Change the data source
value to specify the SQL Server where the eConnect business objects are installed.

Invalid changes to connection string parameters can prevent the service from working. You
should carefully test changes to ensure the connection string is valid.

eConnect.LogAll The key specifies the types of messages to log in the eConnect
event log. The default value is blank.

<addkey="eConnect.LogAll"value=""/>

The value ““ logs only errors. Change the value to “1” to log all messages in the
eConnect event log.

eConnect.Threads This key specifies the number of threads that are available
when the service starts. The default value is “0”.

<add key="eConnect.Threads" value="0" />

A value of “0” indicates a single thread will be used. You can set the value to any
number between 0 and 19. A value of 19 makes 20 threads available when the
service starts. A higher number of threads should allow the service to process
documents more quickly.

ECONNECT INSTALLATION AND ADMINISTRATION GUIDE 35

PA RT 3 A D M I N IS T R A T I O N

There are scenarios where increasing the number of threads degrades system performance. If
the server cannot support more threads, or custom code added to an eConnect pre or post
stored procedures is not thread safe, adding threads may cause unexpected results. Changes
to this key’s value require careful evaluation and testing.

Outgoing Service
The Outgoing Service 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.

The Outgoing Service works in conjunction with the eConnect Transaction

Requester. Use the Transaction Requester to specify the Dynamics GP documents
you want sent to the message queue. Refer to Transaction Requester on page 42
section for more information.

The Outgoing Service uses a configuration file named

eConnect_Outgoing.exe.config to control its operations. This file is found in the
eConnect installation location, typically C:\Program Files\Common
Files\Microsoft Shared\eConnect 10\Services\Outgoing
Service\eConnect_Outgoing.exe.config.

The following example displays the contents of an eConnect_Outgoing.exe.config

file:

<?xmlversion="1.0"encoding="Windows-1252"?>
<configuration>
<appSettings>
<addkey="BackOffice.ConnectionString"value="data
source=MyServer;initial catalog=MyDatabase;Integrated
Security=SSPI;persist security info=False;packet size=4096"/>
<add key ="Requester.ACTION" value ="0" />
<add key ="Requester.OutputType" value ="2" />
<add key ="Requester.Remove" value ="1" />
<add key ="Timer1.Interval" value ="1000" />
<add key ="Delay.Interval" value ="5" />
</appSettings >
<DatabaseNames database1="DYNAMICS" database2="TWO" />
</configuration>

The keys are defined as follows:

Requester.ACTION This key specifies the type of database operations you want
the service to monitor. The default value is “0”.

<addkey="Requester.ACTION"value="0"/>

The value “0” creates and stores an XML document in the queue whenever there is
an insert, update, or delete operation for the Dynamics GP document types selected
using the Requester Enabler/Disabler utility.

36 E C O N N E C T I N S TA L L A T I O N A N D A D M I N I S TR A T I O N G U I D E
 C H A P T E R 5 C O N F I G U R I N G E C O N N E C T S E R V I C E S

The following is a list of possible action types:

Value Description
0 Creates an XML document and stores it in a message queue for each
Transaction Requester enabled insert, update, or delete operation.
1 Creates an XML document and stores it in a message queue for each
Transaction Requester enabled insert operation. The Outgoing Service ignores
any Transaction Requester enabled update or delete operations.
2 Creates an XML document and stores it in a message queue for each
Transaction Requester enabled update operation. The Outgoing Service ignores
any Transaction Requester enabled insert and delete operations.
3 Creates an XML document and stores it in a message queue for each
Transaction Requester enabled delete operation. The Outgoing Service ignores
any Transaction Requester enabled insert and update operations.
4 Creates an XML document and stores it in a message queue for each
Transaction Requester enabled insert or update operation. If a record is updated
multiple times, the queue contains an XML document for each update
operation. The Outgoing Service ignores any Transaction Requester enabled
delete operations.
5 Creates an XML document and stores it in a message queue for Transaction
Requester enabled insert and update operations. Inserts and updates to the
same record produce only a single XML document in the queue. The Outgoing
Service ignores any Transaction Requester enabled delete operations.

Use this key to specify the types of XML documents produced by the Outgoing
Service.

Requester.OutputType This key specifies the type of the XML document that is
created. The default value is “2”, which retrieves the complete document.

<addkey="Requester.OutputType"value="2"/>

The following is a list of possible output types:

Value Description
0 Retrieves key information. The XML document contains the record’s unique key
value and the database and table in Microsoft Dynamics GP where it is stored.
1 Retrieves the master document only. The XML master document contains all
the eConnect schema fields for that record. For example, the XML document
produced for a new customer will include every field defined by the eConnect
customer schema.
2 Retrieves the complete document. The XML document contains the master
document data and any child documents related to the master document. For
example, the XML document for a customer will also include the address
documents for that customer.

Use this key to adjust the amount of data the Outgoing Service places in each XML
document.

Requester.Remove This key specifies whether or not the record is deleted from
the eConnect_Out table after the service places the document in the message queue.
The default value is “1”.

<addkey="Requester.Remove"value="1"/>

A value of ”1” deletes the record from the eConnect_Out table. A value of ”0” keeps
the record in the eConnect_Out table.

ECONNECT INSTALLATION AND ADMINISTRATION GUIDE 37

PA RT 3 A D M I N IS T R A T I O N

The service queries the list of records in the eConnect_Out table. It then cycles
through the list of records to identify the documents to place in the message queue.
If the record in the eConnect_Out table is not deleted, the service creates a duplicate
document in the message queue each time it runs.

Timer1.Interval This key specifies the number of milliseconds the service pauses
between queries of the eConnect_Out table. Default value is ”1000”

<addkey="Timer1.Interval"value="1000"/>

Change the value when you need to optimize the workload the service places on
your computer.

Delay.Interval This key specifies the number of seconds a record must exist in
the eConnect_Out table to be eligible for processing by the service. The default
value is ”5”.

<addkey=”Delay.Interval"value="5"/>

The default value indicates a record will not be processed until it has been in the
eConnect_Out table for a minimum of five seconds.

eConnect.BackOffice.ConnectionString This key stores the connection

string the service uses to connect to the Microsoft Dynamics GP SQL Server. The
default value is the connection string specified during installation.

<addkey="BackOffice.ConnectionString"value="data source=MyServer;initial
catalog=MyDatabase;Integrated Security=SSPI;persist security
info=False;packet size=4096"/>

You change how the connection string works by changing the value parameters. For
example, you may change the data source or initial catalog parameters to reflect
changes in your server configuration.

If you install eConnect on a separate computer from the SQL Server that manages
Microsoft Dynamics GP data, you must change this key’s data source parameter.
The default configuration assumes a single server install. Change the data source
value to specify the SQL Server where the eConnect business objects are installed.

Invalid changes to connection string parameters can prevent the service from working. You
should carefully test changes to ensure the connection string is valid.

DatabaseNames This XML node contains attributes that specify the databases
the Outgoing Service monitors. The default includes all of the Dynamics GP
databases that existed when the service was installed.

<DatabaseNames database1="DYNAMICS" database2="TWO" />

The Outgoing Service monitors the databases in the order they are listed. Each
specified database must include the eConnect business objects and the
eConnect_Out, eConnect_Out_Setup, and eConnectOutTemp tables.

To add a company to the Outgoing Service, you must identify the company
database in the configuration file’s DatabaseNames node. For example, assume you
added a new company named CONTOSO to Microsoft Dynamics GP. To add this
company to the Outgoing Service, complete the following:

38 E C O N N E C T I N S TA L L A T I O N A N D A D M I N I S TR A T I O N G U I D E
 C H A P T E R 5 C O N F I G U R I N G E C O N N E C T S E R V I C E S

• Add database3="CONTOSO” as an attribute to the DatabaseNames node of the

Outgoing Services’s configuration file. The update to the DatabaseNames node
appears as follows:

<DatabaseNames database1="DYNAMICS" database2="TWO" database3="CONTOSO”/>

Replication Service
The Replication Service allows you to integrate information originating in Microsoft
Dynamics GP with another application’s database. A typical example uses the
Replication Service to update a front office sales and service application with key
data from Microsoft Dynamics GP. The term front office database describes this
type of target database.

The Replication Service requires the Outgoing Service to retrieve documents from
Microsoft Dynamics GP. The Replication Service uses the XML documents in the
outgoing queue to replicate the data changes to the front office database.

The Replication Service uses a configuration file named

eConnectFrontOfficeService.exe.config to control its operations. This file is found in
the eConnect installation location, typically C:\Program Files\Common
Files\Microsoft Shared\eConnect 10\Services\ Replication Service\.

The following example displays the contents of an

eConnectFrontOfficeService.exe.config file:

<? xml version="1.0"encoding="Windows-1252"?>

<configuration >
<appSettings >
<addkey="eConnect.FrontOffice.ConnectionString.0" value="data
source=127.0.0.1;initial catalog=TWO_FRONT;integrated
security=SSPI;persist security info=False;packet size=4096"/>
<addkey="eConnect.FrontOffice.ConnectionString.1" value="data
source=127.0.0.1;initial catalog=DYNAMICS_FRONT;integrated
security=SSPI;persist security info=False;packet size=4096"/>
<addkey="eConnect.Requester.Incoming_Queue.0
"value=".\private$\econnect_company_front"/>
<addkey="eConnect.Requester.Incoming_Queue.1
"value=".\private$\econnect_system_front"/>
<addkey="eConnect.Requester.DeadLetter_Queue.0‘
"value=".\private$\econnect_company_front_deadLetter"/>
<addkey="eConnect.Requester.DeadLetter_Queue.1
"value=".\private$\econnect_system_front_deadLetter"/>
<addkey="eConnect.Timer.Interval"value="1000"/>
</appSettings >
</configuration>

The configuration settings allow the Replication Service to target one or more front
office databases. The front office database is specified by the key named
eConnect.FrontOffice.ConnectionString.0.

Additional databases can be added by creating new connection string keys.

Increment the integer value appended to the key name to uniquely identify each
key. The following example shows a connection string key that specifies a second
target database:

ECONNECT INSTALLATION AND ADMINISTRATION GUIDE 39

PA RT 3 A D M I N IS T R A T I O N

<addkey="eConnect.FrontOffice.ConnectionString.1" value="
datasource=127.0.0.1;initial catalog=DYNAMICS_FRONT;integrated
security=SSPI;persist security info=False;packet size=4096"/>

Each connection string key requires the configuration file to specify the queues that
the Replication Service uses for its XML documents. The configuration file specifies
the incoming and deadletter queues. The key names must contain the same integer
value as the connection string key it supports.

For example, the eConnect.Requester.Incoming_Queue.0 and

eConnect.Requester.DeadLetter_Queue.0 keys specify the queues for the
eConnect.FrontOffice.ConnectionString.0 key. The eConnect.Requester.Incoming_
Queue.0 value specifies the queue where the Incoming Service is storing XML
documents that need to be replicated to the front office database. The following
illustrates these three related keys:

<? xml version="1.0"encoding="Windows-1252"?>

<configuration >
<appSettings >
The connection string key
<addkey="eConnect.FrontOffice.ConnectionString.0" value="data
for the first database. source=127.0.0.1;initial catalog=TWO_FRONT;integrated
security=SSPI;persist security info=False;packet size=4096"/>
<addkey="eConnect.FrontOffice.ConnectionString.1" value="data
source=127.0.0.1;initial catalog=DYNAMICS_FRONT;integrated
security=SSPI;persist security info=False;packet size=4096"/>
The incoming queue key
<addkey="eConnect.Requester.Incoming_Queue.0
for the first database. "value=".\private$\econnect_company_front"/>
<addkey="eConnect.Requester.Incoming_Queue.1
"value=".\private$\econnect_system_front"/>
The deadletter queue key <addkey="eConnect.Requester.DeadLetter_Queue.0‘
for the first database. "value=".\private$\econnect_company_front_deadLetter"/>
<addkey="eConnect.Requester.DeadLetter_Queue.1
"value=".\private$\econnect_system_front_deadLetter"/>
<addkey="eConnect.Timer.Interval"value="1000"/>
</appSettings >
</configuration>

You must add the correct connection string and queue information to the configuration file
before starting the Replication Service.

The keys from the example are defined as follows:

eConnect.FrontOffice.ConnectionString.0 This key provides the con-

nection string to a front office database.

<addkey="eConnect.FrontOffice.ConnectionString.0" value="data source=

127.0.0.1;initial catalog=TWO_FRONT;integrated security=SSPI;persist security
info=False;packet size=4096"/>

The value sets the data source and initial catalog parameters to the server address
and database of a front office application that the Replication Service targets.

eConnect.FrontOffice.ConnectionString.1 This key provides the con-

nection string to a second front office database.

<addkey="eConnect.FrontOffice.ConnectionString.1" value="data source=

127.0.0.1;initial catalog=DYNAMICS_FRONT;integrated security=SSPI;persist
security info=False;packet size=4096"/>

40 E C O N N E C T I N S TA L L A T I O N A N D A D M I N I S TR A T I O N G U I D E
 C H A P T E R 5 C O N F I G U R I N G E C O N N E C T S E R V I C E S

The value sets the data source and initial catalog parameters to the server address
and database of a second front office application that the Replication Service targets.

eConnect.Requester.Incoming_Queue.0 This key specifies the name and

location a queue.

<addkey="eConnect.Requester.Incoming_Queue.0" value=".\private$\
econnect_company_front"/>

The Replication Service monitors the specified queue and uses the XML documents
placed in that queue to update the front office database. The value specifies the
queue where the eConnect Outgoing Service is placing the XML documents that
need to be replicated.

eConnect.Requester.Incoming_Queue.1 This key specifies the name and

location of a second queue.

<addkey="eConnect.Requester.Incoming_Queue.1 " value=".\private$\

econnect_system_front"/>

The Replication Service monitors the specified queue and uses the XML documents
placed in that queue to update the second front office database. The value specifies
the queue where the eConnect Outgoing Service is placing the XML documents that
need to be replicated.

eConnect.Requester.DeadLetter_Queue.0 This key specifies the name and

location of a deadletter queue.

<addkey="eConnect.Requester.DeadLetter_Queue.0" value=".\private$\
econnect_company_front_deadLetter"/>

The value specifies the queue the Replication Service uses to store undeliverable
messages for the first incoming queue.

eConnect.Requester.DeadLetter_Queue.1 This key specifies the name and

location of a second deadletter queue.

<addkey="eConnect.Requester.DeadLetter_Queue.1" value=".\private$\
econnect_system_front_deadLetter"/>

The value specifies the queue the Replication Service uses to store undeliverable
messages for the second incoming queue.

eConnect.Timer.Interval This key specifies the number of milliseconds the

service pauses between checks for new messages in the incoming queues. The
default value is 1000 milliseconds.

<addkey="eConnect.Timer.Interval" value="1000"/>

The default value causes the service to pause for one second before checking the
incoming queues for new messages. Increase the number of milliseconds to lessen
the workload the Replication Service places on your computer.

ECONNECT INSTALLATION AND ADMINISTRATION GUIDE 41

PA RT 3 A D M I N IS T R A T I O N

Transaction Requester
The Transaction Requester allows you to specify Microsoft Dynamics GP
documents to publish as eConnect XML documents. You also specify whether to
publish for an insert, update, or delete operation in a Microsoft Dynamics GP
database. You configure the Transaction Requester, complete the following
procedure:

1. Start eConnect Requester Setup.

In the Start menu, select Programs >> Microsoft Dynamics >> eConnect 10 >>
Requester Setup >> Requester Setup. The Requester Setup Tool window
opens.

2. Create a connection string.

The first time you open the Requester Setup Tool, you must create a
connection string that enables the Requester Setup Tool to access to your
Microsoft Dynamics GP SQL Server. If you previously configured the
connection string, proceed to the next step.

To create the connection string, choose Setup Connection from the Connection
Settings menu. The Connection Setup window opens. Enter the name of the
Microsoft Dynamics GP SQL Server and the company database you will use
with the Transaction Requester.

42 E C O N N E C T I N S TA L L A T I O N A N D A D M I N I S TR A T I O N G U I D E
 C H A P T E R 5 C O N F I G U R I N G E C O N N E C T S E R V I C E S

Mark the Integrated Security check box to use your Windows logon
information. If you clear the Integrated Security check box, you must supply a
SQL user name and password that enables the Requester Setup Tool to access
the specified database.

Click Save.

3. Connect to the database.

To complete the connection to your database, click Connect. The Insert, Update,
Delete, and Message Queues tabs display the list of available document types.

4. Select the Insert document types to publish to MSMQ.

On the Insert tab, mark the check box of each document type you want to send
to MSMQ when a new document of that type is created.

To discontinue the publishing of a document, remove the check from the check
box for that document type.

5. Select the Update document types to publish to MSMQ.

On the Update tab, mark the check box of each document type you want to
send to MSMQ when a document of that type is modified.

To discontinue the publishing of a document, remove the check from the check
box for that document type.

ECONNECT INSTALLATION AND ADMINISTRATION GUIDE 43

PA RT 3 A D M I N IS T R A T I O N

6. Select the Delete document types to publish to MSMQ.

On the Delete tab, mark the check box of each document type you want to send
to MSMQ when a document of that type is deleted.

To discontinue the publishing of a document, remove the check from the check
box for that document type.

7. Specify the queue to use for a document type.

You can associate a specific MSMQ queue with a document type. If a queue is
specified, the XML documents will be stored in that queue. To specify a queue,
mark the check box and enter the queue name in the QUEUEPATH column.

If you do not specify a queue, the eConnect Outgoing Service places the XML
documents in the econnect_outgoing10 queue.

8. Click Update to save your Requester Setup Tool changes.

The Requester Setup Tool creates SQL triggers for each selected document and
operation. The triggers write to the eConnect_Out table in the database
specified by the connection string. The eConnect Outgoing Service uses this
table to identify the XML documents to place in the specified queue. If you
unmarked a check box to discontinue publishing a document type, the SQL
triggers for that document type and operation are removed.

9. Close the Requester Setup Tool.

Click Exit to close the Requester Setup Tool window.

BizTalk adapter
The BizTalk adapter allows you to use eConnect in a BizTalk orchestration or in a
simple pass-through situation. A BizTalk orchestration allows applications with
differing message formats to integrate, while a BizTalk pass-through simply routes
messages between applications.

44 E C O N N E C T I N S TA L L A T I O N A N D A D M I N I S TR A T I O N G U I D E
 C H A P T E R 5 C O N F I G U R I N G E C O N N E C T S E R V I C E S

To configure the eConnect BizTalk 2004 adapter, you must have already installed Microsoft
Visual Studio .NET 2003 on the computer. To configure the eConnect BizTalk 2006 adapter,
you must have already installed Microsoft Visual Studio 2005 on the computer.

To configure the BizTalk adapter, complete the following procedure:

1. Open the BizTalk Administration console.

In the Start menu, select All Programs >> Microsoft BizTalk Server >> BizTalk
Server Administration. The BizTalk Administration Console opens. In BizTalk
Server 2004, right-click Adapters and select New >> Adapter.

In BizTalk Server 2006, click BizTalk Server 2006 >> BizTalk Group >> Platform
Settings. Right-click Adapters and select New >> Adapter.

The Adapter Properties window opens.

ECONNECT INSTALLATION AND ADMINISTRATION GUIDE 45

PA RT 3 A D M I N IS T R A T I O N

2. Add the adapter.

In the Name box, enter eConnect as a name for the send adapter. In the Adapter
box, select Dynamics GP eConnect.

Click OK to continue.

3. Open the Adapter Handler Properties window.

Double-click the eConnect adapter you created in the previous step. If you are
using BizTalk Server 2004, double-click the Send Handlers folder that displays
in the right pane.

The right pane displays a Host Name of BizTalkServerApplication. Right-click

BizTalkServerApplication and select Properties. The Adapter Handler
Properties window opens. BizTalk Server 2004 labels the window
BizTalkServerApplication Properties.

In BizTalk Server 2004, select the Properties tab. In BizTalk Server 2006, click the
Properties button. The eConnect Transport Properties window opens.

46 E C O N N E C T I N S TA L L A T I O N A N D A D M I N I S TR A T I O N G U I D E
 C H A P T E R 5 C O N F I G U R I N G E C O N N E C T S E R V I C E S

4. Edit the connection string property.

Change the data source to point to your Microsoft Dynamics GP server and set
the initial catalog to DYNAMICS or the company database you want to work
with. Click OK to continue.

5. Close the Adapter Handler Properties window.

Click OK to close the Adapter Handler Properties window. Close the BizTalk
Server Administration Console.

6. Create a new Send Port.

Open Microsoft Visual Studio. From the View menu, select BizTalk Explorer.
The BizTalk Explorer window opens in Visual Studio.

Expand the node for your BizTalk server. Right-click Send Ports. Select Add
Send Port. The Create New Send Port dialog opens. Select Static One-Way
Port. Click OK.

7. Select eConnect as the transport type.

The Static One-Way Send Port Properties - Configurations - Transport -
Primary window opens. In the Transport Type drop down list box, select the
eConnect adapter you created earlier.

ECONNECT INSTALLATION AND ADMINISTRATION GUIDE 47

PA RT 3 A D M I N IS T R A T I O N

8. Open the Transport Properties window.

Select Address (URI) and click the ellipsis(...) button to open the eConnect
Transport Properties dialog box. Set the connection string’s data source
parameter to point to your Microsoft Dynamics GP SQL Server. Set the initial
catalog parameter to the Dynamics GP database you want to work with.

Click OK to continue.

9. Verify the Send Pipeline.

Click the Send folder in the left pane. Verify that the Send Pipeline property is
set to Microsoft.BizTalk.DefaultPipelines.PassThrough.

48 E C O N N E C T I N S TA L L A T I O N A N D A D M I N I S TR A T I O N G U I D E
 C H A P T E R 5 C O N F I G U R I N G E C O N N E C T S E R V I C E S

10. Select Filters and Maps (when needed).

If you are planning to use a BizTalk orchestration, continue to the next step.

If you are not using BizTalk orchestration, click the Filters & Maps folder in the
left pane. Select Filters to open Static One-Way Send Port Properties -
Configurations - Filters and Maps - Filters window. In the Property drop-
down list, select BTS.ReceivePortName. In the Value text box, enter the name
of the receive port.

Click OK to continue.

11. Save the send port configuration.

Click OK. Close Visual Studio.

ECONNECT INSTALLATION AND ADMINISTRATION GUIDE 49

50 E C O N N E C T I N S TA L L A T I O N A N D A D M I N I S TR A T I O N G U I D E
Chapter 6: Maintenance
This portion of the documentation provides information about modifying,
repairing, or removing an existing eConnect installation. The following items are
discussed:

• Modifying an eConnect installation

• Completing a repair
• Removing eConnect

Modifying an eConnect installation

eConnect allows you to add or remove individual features from an existing
installation. To add or remove features, complete the following steps:

1. Start the eConnect installer.

Open Add or Remove Programs, choose eConnect Runtime for Microsoft
Dynamics GP 10.0. Click Change.

2. Choose Add/Remove Features.

The Modify eConnect Runtime for Microsoft Dynamics GP 10.0 Installation
window opens.

Click Add/Remove Features.

3. Specify the features to add or remove.

The Select Features window opens. Additional information about selecting
eConnect features can be found in Chapter 4, “eConnect Installation.” Click
Next.

4. Begin the installation.

Click Install to add or remove the specified features. The installer may take
several minutes to complete the update.

5. Close the wizard.

When the Installation Complete window appears, click Exit to close the
wizard.

ECONNECT INSTALLATION AND ADMINISTRATION GUIDE 51

PA RT 3 A D M I N IS T R A T I O N

Completing a repair
If the eConnect for Microsoft Dynamics GP application becomes damaged, the
repair operation may help resolve the issue. The Repair wizard fixes the following:

• Missing or corrupt files

• Missing or corrupt shortcuts
• Missing or corrupt registry entries

The repair operation cannot perform the following:

• Restore default configuration settings for the COM+ application, MSMQ, or the
Incoming, Outgoing, and Replication services.
• Remove or restore your customizations made to any Pre or Post stored
procedure.

To complete a repair, perform the following steps:

1. Start the eConnect installer.

Open Add or Remove Programs, choose eConnect Runtime for Microsoft
Dynamics GP 10.0. Click Change.

2. Choose Repair.
The Modify eConnect Runtime for Microsoft Dynamics GP 10.0 Installation
window opens.

Click Repair.

3. Specify eConnect account information.

You must supply the domain, user name and password of the windows account
that the eConnect Incoming Service, Outgoing Service, Replication Service and
COM+ application use. Refer to Chapter 4, “eConnect Installation,” for
additional information about the eConnect windows account. Click Next to
continue.

4. Ready to repair.
Click Repair to begin. The repair will run for several minutes.

5. Installation complete
When the Installation Complete window appears, click Exit to close the
wizard.

52 E C O N N E C T I N S TA L L A T I O N A N D A D M I N I S TR A T I O N G U I D E
 C H A P T E R 6 M A I N T E N A N C E

Removing eConnect
The eConnect remove operation allows you to delete all of the installed eConnect
folders and files. It deletes only the files and folders created in the local machine’s
file system.

To remove eConnect from a computer, complete the following steps:

1. Start the eConnect installer.

Open Add or Remove Programs, choose eConnect Runtime for Microsoft
Dynamics GP 10.0. Click Change.

2. Click Remove.
The Modify eConnect Runtime for Microsoft Dynamics GP 10.0 Installation
window opens.

Click Remove.

3. Begin the uninstall.

The Ready to Remove window opens. Click Remove to begin the uninstall. The
uninstall will run for several minutes.

4. Close the wizard.

When the Installation Complete window appears, click Exit to close the
wizard.

ECONNECT INSTALLATION AND ADMINISTRATION GUIDE 53

54 E C O N N E C T I N S TA L L A T I O N A N D A D M I N I S TR A T I O N G U I D E
Chapter 7: Utilities
eConnect includes several utilities that help to configure and administer some
components. The following sections describe these utilities:

• eConnect Requester Setup Tool

• eConnect MSMQ Control
• eConnect Release Information

eConnect Requester Setup Tool

The eConnect Requester Setup Tool allows you to specify Microsoft Dynamics GP
document types to publish as eConnect XML documents to a Microsoft message
queue (MSMQ). The utility also allows you to specify a queue for each document.

For more information about the Requester Setup Tool, see Transaction Requester on
page 42.

eConnect MSMQ Control

The eConnect MSMQ Control utility allows you to view, manipulate, and resend
messages in MSMQ. You use the eConnect MSMQ Control to debug MSMQ
message issues, to resubmit messages from a deadletter queue, or to direct
messages to a different queue.

If you install using the eConnect runtime installer, the eConnect MSMQ control is not
available. To use the eConnect MSMQ control, you must install the eConnect SDK. The
runtime install does not include the eConnect MSMQ control.

ECONNECT INSTALLATION AND ADMINISTRATION GUIDE 55

PA RT 3 A D M I N IS T R A T I O N

To use the eConnect MSMQ Control, open the Start menu and select All Programs
>> Microsoft Dynamics >> eConnect 10 >> eConnect MSMQ Control. This opens
eConnect Queue Messaging in Internet Explorer.

Select the type of queue. The eConnect MSMQ Control allows you to work with
private queues, public queues, or the Deadletter queue. Enter the path for the queue
in the Queue Path text box. Click Open. The Messages list box displays the label of
each message in that queue.

To view or edit a specific message, click its label in the list box. The Message
Contents textbox at the bottom of the screen displays the message. If you want to
change the contents of the message, use the textbox to find and edit the XML.

To resubmit the message or to send it to another queue, enter the path to the target
queue in the Queue Path for Resending text box. Click Resend. The Message Log
textbox logs any messages from resending the message. The eConnect MSMQ
Control also allows you to indicate whether to leave the original messages in the
queue or have the original message deleted once the messages is resent. The
eConnect MSMQ Control also allows you to relabel a message.

56 E C O N N E C T I N S TA L L A T I O N A N D A D M I N I S TR A T I O N G U I D E
 C H A P T E R 7 UT IL IT IE S

eConnect Release Information

The eConnect Release Information utility displays the eConnect release number of
the business objects installed for a Microsoft Dynamics GP database.

To use the utility, open the Start menu and select All Programs >> Microsoft
Dynamics >> eConnect 10 >> Release Information >> Release Info. The eConnect
Release Information window opens.

Choose the Set Connect String command from the Connection menu. When the
Connection Properties window opens, specify the name of your Microsoft
Dynamics GP SQL Server.

To use your Windows logon credentials, mark the Windows Integrated Security
check box. Click Connect or choose Retrieve from the menu.

If your Windows logon account cannot access the Microsoft Dynamics GP server,
you may use a SQL logon. To use a SQL logon, you must clear the Windows
Integrated Security check box. Enter your SQL user name and password.

Click Connect or choose Retrieve from the menu.

ECONNECT INSTALLATION AND ADMINISTRATION GUIDE 57

PA RT 3 A D M I N IS T R A T I O N

The eConnect Release Information windows displays the company name, and the
eConnect release number for each company on the specified server.

To close the eConnect Release Information window, choose Close.

58 E C O N N E C T I N S TA L L A T I O N A N D A D M I N I S TR A T I O N G U I D E
Chapter 8: Troubleshooting
If you encounter problems with eConnect for Microsoft Dynamics GP, the following
sections may be helpful. They describe some of the most common situations that
can occur when using eConnect. The following items are discussed:

• Functional currency
• Connection string problems
• Login problems
• Incoming or Outgoing Services
• eConnect event log
• Incoming Service problems

Functional currency
If you add a new company to Microsoft Dynamics GP and you install the eConnect
business object for the new company, you may encounter problems when eConnect
attempts a create, update, or delete operation. Common examples include:

• The eConnect Incoming Service fails to update the company database. You find
Microsoft message queuing (MSMQ) messages that target the new company in
the system’s Transactional dead-letter messages queue.

• Applications using the eConnect API generate error messages that indicate a
functional currency is needed.

• You find the eConnect event log contains entries that report a functional
currency has not been set up and is required.

To use the eConnect business objects, you must define a functional currency for the
new company. eConnect requires a currency ID for the company, even if
multicurrency is not being used. Review the setup procedure, Functional currency on
page 24, to specify a functional currency.

Connection string problems

After creating or editing an eConnect connection string, attempts to use the
Microsoft.Dynamics.GP.eConnect.dll (.NET assembly) log the following error
message:

Integrated Security is required.

Please ensure that the ConnectionString input parameter is valid.

To eliminate the error, check the connection string. The connection string must
contain:

Integrated Security=SSPI;

If this parameter is missing from the connection string or is not set to SSPI, edit the
connection string to supply the correct integrated security setting.

Login problems
After installing eConnect, any attempt to use the eConnect API or start an eConnect
service creates an error message in the eConnect event log. The log entries indicate

ECONNECT INSTALLATION AND ADMINISTRATION GUIDE 59

PA RT 3 A D M I N IS T R A T I O N

the user login is invalid or cannot perform the requested action. To resolve these
issues, review the following:

• Verify that the login account can access the SQL Server where the eConnect
business objects are installed. The login must be able to access the Microsoft
Dynamics GP server.

• Verify that the login account can access the DYNAMICS database and the
company databases where the eConnect business objects are installed. SQL
Server must authorize the login account to access these databases.

• Verify that the login account is assigned to the DYNGRP database role. The
login account must have the DYNGRP role for the DYNAMICS database and
each company database where the eConnect business objects are installed.

Incoming or Outgoing Services

When you attempt to start the eConnect Incoming Service, you see the following
error message:

Could not start the Microsoft Business Solutions - Great Plains eConnect
Incoming Service on the Local Computer.
Error 1075: The dependency service does not exist or has been marked for
deletion.

A similar message is displayed when attempting to start the Outgoing Service.

The message indicates MSMQ was not installed on the computer with the eConnect
Incoming and Outgoing services. Refer to Microsoft Message Queueing (MSMQ) on
page 25 for instructions on installing MSMQ.

eConnect event log

The eConnect install creates an event log that records error, warning and
informational messages generated by eConnect. To view the eConnect event log,
open the Start menu and select Control Panel >> Administrative Tools >> Event
Viewer. Click the eConnect log to view the list of messages.

You will want to check the eConnect event log in the following situations:

• Your application produces error messages. Check the event log to see if
eConnect is logging any messages that specify the cause of the error.

• You find insert, update, or delete operations performed by eConnect are not
visible in the Microsoft Dynamics GP client. Review the eConnect event log to
see whether operations are being aborted. The log will contain an error message
that explains why the operation was not completed.

• If you validate incoming XML documents, the event log will contain error
messages about the documents that failed validation. Use the messages in the
event log to correct the XML so the documents can be resubmitted.

The information in the error messages specifies the type of error and its source. Use
the information contained in the messages to identify the corrective actions that are
needed.

60 E C O N N E C T I N S TA L L A T I O N A N D A D M I N I S TR A T I O N G U I D E
 C H A P T E R 8 TR O U B L E S H O O T I N G

Incoming Service problems

After starting the Incoming Service, you find that expected Microsoft Dynamics GP
data changes do not occur. The Incoming Service processes the incoming XML
documents, but some insert, update, or delete operations are not completed. The
missing operations may result from using schema validation with the Incoming
Service.

To see whether validation is the cause, open the configuration file for the Incoming
Service and check the eConnect.Schema.Type key. If the key value is XSD, the
Incoming Service is validating the XML of all the incoming documents. For
additional information about configuring the Incoming Service, see the Incoming
Service on page 33.

When validation is enabled, the Incoming Service checks all incoming documents
for compliance with eConnect’s schema definition for that document. A validation
error occurs if the document contains improperly named nodes, the sequence of the
nodes within the document differs from the schema, or the nodes contain
unexpected values. If the Incoming Service encounters a validation error, it logs an
error message in the eConnect event log. After logging the error message, the
operation is aborted.

To prevent operations from being lost to validation errors, perform one of the
following actions:

• Use the error information to determine what is causing the validation problem.
Change the application that generates the XML documents to comply with the
eConnect schema.

• Use the error messages in the log to identify documents that failed validation.
Use the information in the error message to correct each XML document.
Resubmit the documents to the Incoming Service.

• Disable validation for the Incoming Service. This will stop eConnect from
logging an error when an XML document contains an unknown element name,
or the order of the elements in the document differ from the document’s
schema.

COM+ application
Your eConnect application suddenly stops producing changes in Microsoft
Dynamics GP. Your investigation finds that the application was previously working.
You cannot find any recent changes to the application or the eConnect
configuration. To determine whether the eConnect COM+ application is causing the
unexpected result, perform the following actions:

• Check whether the eConnect COM+ application is using the correct login
credentials. The installation requires you to provide a user name and password
for the COM+ application. If the you later change that user’s password and do
not update the COM+ application with the new password, the COM+
application will not start. To update the COM+ password, open the eConnect
COM+ application in the Component Services console. Right-click the
eConnect 10 for Microsoft Dynamics GP application and select Properties.
Click the identity tab. Update Password with the specified user’s current
password.

ECONNECT INSTALLATION AND ADMINISTRATION GUIDE 61

PA RT 3 A D M I N IS T R A T I O N

• Check whether the COM+ application has been disabled. Open the eConnect
COM+ application in the Component Services Console. Right-click the
eConnect 10 for Microsoft Dynamics GP application and select Start. If you
receive an error message stating you must enable the application, right-click
eConnect 10 for Microsoft Dynamics GP and select Enable.

62 E C O N N E C T I N S TA L L A T I O N A N D A D M I N I S TR A T I O N G U I D E
Glossary Microsoft message queuing
(MSMQ)
A message infrastructure and development
Application programming interface platform for creating distributed, loosely-
(API) coupled messaging applications.
A set of functions or features you access to
programmatically use or manipulate a Outgoing Service
software component or application. A Microsoft Windows service that publishes
eConnect XML documents to a specified
Back office queue. The XML documents represent
A financial management system. In an documents that were created, updated, or
eConnect environment, this refers to deleted in Microsoft Dynamics GP.
Microsoft Dynamics GP.
Post stored procedure
BizTalk server A customized SQL stored procedure that
A Microsoft platform that manages the runs immediately after an eConnect stored
exchange of data between applications. procedure.

BizTalk adapter Pre stored procedure

A preconfigured BizTalk Application A customized SQL stored procedure that
Integration Component (AIC) that allows runs immediately before an eConnect stored
BizTalk server to use eConnect. procedure.

Business objects Replication Service

The collection of SQL stored procedures that A Microsoft Windows service that copies
contain eConnect’s business logic. selected data changes from Microsoft
Dynamics GP to a specified target database.
COM+ application
A programming structure encapsulating Schema
data and functionality. In eConnect, this An XML file (with typical extension .XSD)
structure calls the SQL stored procedures that describes the syntax and semantics of
(business objects). XML documents using a standard XML
syntax. An XML schema specifies the content
Connection string constraints and vocabulary that compliant
A text representation of the initialization documents must accommodate.
properties needed to connect to a data store.
Services
eConnect Microsoft Windows services are long-
A collection of tools, components, and APIs running applications that perform some
that provide programmatic integration with system function. They typically do not
Microsoft Dynamics GP. display any user interface. eConnect uses
eConnect XML document several services for moving eConnect XML
documents in and out of various message
A text document that describes Microsoft
queues.
Dynamics GP data. The eConnect XML
schema specifies the content and structure of Stored procedure
data in the document. A group of Transact-SQL statements
Front office compiled into a single execution plan. The
business logic for eConnect is contained in
An application that communicates with the
stored procedures.
back office. Examples include customer
relationship management systems, data Transaction Requester
warehouses, and web sites. The Transaction Requester publishes
Functional currency eConnect XML documents to a queue. The
XML documents represent Microsoft
The currency an organization uses to keep
Dynamics GP documents. Use the eConnect
the bulk of its financial records.
Requester Setup utility to specify the
Incoming Service documents to publish.
A Microsoft Windows service that monitors
a queue for new eConnect XML documents.
Trigger
A special class of SQL stored procedure that
Valid documents are used to create, update,
executes automatically when an update,
or delete records in Microsoft Dynamics GP.
insert, or delete statement is issued for a
Integrated security table or view.
The SQL server security option that
leverages Windows authentication to supply
XML
A text-based format that uses markup tags
the user’s login credentials. It allows a
(words surrounded by ‘<‘ and ‘>’) to
network user to access a SQL server database
without supplying separate login describe how a document is structured and
the data it contains.
credentials.

ECONNECT INSTALLATION AND ADMINISTRATION GUIDE 63

64 E C O N N E C T I N S TA L L A T I O N A N D A D M I N I S TR A T I O N G U I D E
Index configurations (continued)
single server 12
eConnect.Requester.Incoming_Queue.1 41
eConnect.Schema 35
connection string eConnect.Schema.Type 34
A defined 63 eConnect.Threads 35
Administration, part 32-62 Incoming Service 35 eConnect.Timer.Interval 41
API, see application programming Outgoing Service 38 eConnect.Transactional_deadletter_Queu
interface Release Information 57 e 34
application programming interface Replication Service 40 event log
BizTalk 15 Transaction Requester 42 described 29
defined 63 troubleshooting 59 troubleshooting 60
Microsoft .NET 15 conventions, in documentation 2
MSMQ 15 corrupt files, repairing 52 F
Replication Service 17 currency, see functional currency front office, defined 63
requirements 15 customizing, business logic 13 front office database, described 39
architecture functional currency
chapter 11-18 D defined 63
diagram 11 DatabaseNames, setting for the Outgoing setup 24
layers Service 38 troubleshooting 59
API 11 Delay.Interval 38
data 11 Distributed Transaction Coordinator I
described 11 configuring 23 Incoming Service
assemblies, .NET 15 described 22 configuration 33-36
enabling 22 configuration keys 34-36
B documentation, symbols and conventions connection string 35
back office, defined 63 2 event log 35
backups, configuration files 33 message queues 34
BizTalk adapter E multithreading 35
configuration 44-49 eConnect schema validation 34
defined 63 application programming interface 14 defined 63
requirements 44 architecture diagram 11 described 15
BizTalk integration business logic 13 installation
described 15 business objects 13 chapter 27-29
types 44 components described 15 customizing the installed
BizTalk server, defined 63 customizing business logic 14 components 28
business logic, customizing 13 defined 63 eConnect event log 29
business objects described 7 part 20-29
see also stored procedures event log 29 prerequisites 21
after removing eConnect 53 modifying 51 procedure for eConnect 27-29
business logic 13 prerequisites 21 required login role 27
customizing business logic 13 removing 53 results 29
defined 63 repairing 52 system configurations
described 13 Replication Service 17 BizTalk Server 13
stored procedures 14 stored procedures 14 client/server 12
support 3 single server 12
C uses 7 integrated security, defined 63
COM+ object XML documents 8
defined 63 eConnect Basics, part 6-18 L
described 14 eConnect Overview, chapter 7-9 light bulb symbol 2
logon requirements 14 eConnect.BackOffice.ConnectionString 35,
troubleshooting 61 38 M
user account 21 eConnect.FrontOffice.ConnectionString.0 Maintenance, chapter 51-53
components, described 28 40 margin notes 2
Configuration, chapter 33-49 eConnect.FrontOffice.ConnectionString.1 Microsoft .NET Framework 21
configuration files 40 Microsoft message queuing
backup copy 33 eConnect.Incoming_Queue 34 defined 63
Incoming Service 33 eConnect.LogAll 35 described 25
Outgoing Service 36 eConnect.Requester.DeadLetter_Queue.0 installing 25
Replication Service 39 41 monitor queue activity 56
restarting the service 33 eConnect.Requester.DeadLetter_Queue.1 MSMQ Control 55
configurations 41 services 15
client/server 12 eConnect.Requester.Incoming_Queue.0 41 start the MSMQ control 55

ECONNECT INSTALLATION AND ADMINISTRATION GUIDE 65

IN DEX

Microsoft Visual Studio .NET 2003, Replication Service (continued) troubleshooting (continued)
BizTalk configuration 44 defined 63 services 60
missing files, repairing 52 described 17
modifying Requester Tool 42-44, described 55 U
described 51 Requester.Action 36 uninstall
eConnect installation, procedure 51 Requester.OutputType 37 described 53
MSMQ, see Microsoft message queuing Requester.Remove 37 removing eConnect 53
MSMQ Control roles user account
described 55 software developer 8 COM+ object 21
monitoring queue activity 56 system administrator 8 troubleshooting 61
starting 55 utilities
multithreading, Incoming Service 35 S chapter 55-58
schema MSMQ Control 55
N defined 63 Release Information 57
.NET assembly 15 described 15 Requester Tool 55
.NET Framework 21 files 35
schema validation, see validation V
O services validation
operating system, required 21 see also Incoming Service, Outgoing described 34
Outgoing Service Service, Replication Service error messages 34
see also Transaction Requester defined 63 schema files 35
configuration 36-39 described 33 troubleshooting 61
configuration keys 36-39 restarting 33 Visual Studio .NET, BizTalk configuration
action types 36 troubleshooting 60 44
connection string 38 software developer, responsibilities 8
database names 38 SQL trigger W
delay interval 38 defined 63 warning symbol 2
output types 37 Requester Tool 16 windows services, see services
remove record 37 stored procedures
time interval 38 see also business objects
X
defined 63 XML, defined 63
calling 14
described 15 XML document
defined 63
defined 63
described 14
P modifying 13
described 8
performance, optimizing 35 post 63
Prerequisites pre 63
chapter 21-25 support, for Microsoft Dynamics GP
COM+ user account 21 eConnect 3
Distributed Transaction Coordinator symbols in documentation 2
22 system administrator, responsibilities 8
functional currency 24
Microsoft .NET Framework 21 T
operating system 21 technical support, for Microsoft Dynamics
product support, for Microsoft Dynamics GP eConnect 3
GP eConnect 3 threads, Incoming Service 35
Timer1.Interval 38
R Transaction Requester
registry entries, repairing 52 configuration 42-44
Release Information connection string 42
connection string 57 database tables 16
described 57 defined 63
viewing the release number 57 described 15
removing eConnect 53 Requester Tool 42, 55
repair, described 52 troubleshooting
repairing eConnect, procedure 52 chapter 59-62
Replication Service COM+ object 61
adding a database 39 connection string 59
configuration 39-41 event log 60
configuration keys 40-41 functional currency 59
connection string 40 Incoming Service 61
message queues 41 login problems 59
time interval 41

66 E C O N N E C T I N S TA L L A T I O N A N D A D M I N I S TR A T I O N G U I D E