eConnect Installation and Administration Guide · 2009-01-13 · Server stored procedures, BizTalk, or MSMQ. 3. Leverage industry-standard technologies. eConnect includes components

Microsoft Dynamics™ GP

eConnect Installation and Administration GuideRelease 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

E C O N N E C T I N S T A L L A T I O N A N D A D M I N I S T R A T I O N G U I D E i

Contents

Introduction .................................................................................................................................................2What’s in this manual...................................................................................................................................2

Symbols and conventions ............................................................................................................................2

Product support ............................................................................................................................................3

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

Chapter 1: eConnect Overview ................................................................................................ 7What is eConnect?.........................................................................................................................................7

What eConnect can do .................................................................................................................................7

Getting started...............................................................................................................................................8

Chapter 2: eConnect Architecture......................................................................................11Architecture 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.............................................................................................................. 21Operating 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 ........................................................................................ 27Installation procedure ................................................................................................................................27

What to do next ...........................................................................................................................................29

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

Chapter 5: Configuring eConnect Services............................................................... 33Overview......................................................................................................................................................33

Incoming Service.........................................................................................................................................33

Outgoing Service.........................................................................................................................................36

Replication Service......................................................................................................................................39

Transaction Requester ................................................................................................................................42

BizTalk adapter............................................................................................................................................44

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

ii E C O N N E C T I N S T A L L A T I O N A N D A D M I N I S T R A T I O N G U I D E

C O N T E N T S

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

Completing a repair....................................................................................................................................52

Removing eConnect....................................................................................................................................53

Chapter 7: Utilities ........................................................................................................................... 55eConnect Requester Setup Tool ................................................................................................................55

eConnect MSMQ Control ..........................................................................................................................55

eConnect Release Information ..................................................................................................................57

Chapter 8: Troubleshooting...................................................................................................... 59Functional 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

INT

RO

DU

CT

ION

2 E C O N N E C T I N S T A L L A T I O N A N D A D M I N I S T R A T I O N G U I D E

IntroductionWelcome to eConnect for Microsoft Dynamics™ GP. This documentation explainshow 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 theinformation presented here.

What’s in this manual

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

• Part 1, eConnect Basics, provides an overview of eConnect and the componentsit 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 followingsymbols and conventions within the text to make specific types of informationstand 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 important information.

Margin notes call attention to critical information and 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 Queuing (MSMQ)

Acronyms are spelled out the first time they’re used.

TAB or ALT+M Small capital letters indicate a key or a key sequence.

E C O N N E C T I N S T A L L A T I O N A N D A D M I N I S T R A T I O N G U I D E 3

I N T R O D U C T I O N

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

http://www.microsoft.com/Dynamics


PA

RT

1: E

CO

NN

EC

T B

AS

ICS


Part 1: eConnect BasicsThis portion of the documentation contains introductory information you shouldknow before deploying eConnect for Microsoft Dynamics GP. The followinginformation is discussed:

• Chapter 1, “eConnect Overview,” introduces eConnect and the types ofintegration interfaces and tools it provides.

• Chapter 2, “eConnect Architecture,” discusses the underlying components that are part of an eConnect installation.


Chapter 1: eConnect OvervieweConnect for Microsoft Dynamics GP allows you to integrate your businessapplications with Microsoft Dynamics GP. The following topics introduce eConnectfor 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 applicationsto programmatically exchange data with Microsoft Dynamics GP. The key eConnectcomponents 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, webservices, point-of-sale systems, or legacy applications to integrate with MicrosoftDynamics 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 termback 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 ofMicrosoft Dynamics GP. This allows you to focus your time and energy on creatingor 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 webstorefronts or service applications.

2. Share financial management data across applications.eConnect allows multiple applications to share financial management data. TheeConnect interfaces can support multiple independent applications. Changes tofinancial data in Dynamics GP are simultaneously available to all applicationsthat 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

P A R T 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 businesslogic contained in the back office is reused by new custom applications.

An eConnect integration also reduces data re-entry. An automated eConnectintegration between Microsoft Dynamics GP and a new or existing onlinestorefront, web service, or other data source eliminates the time and cost ofmanually copying data.

2. Use existing development tools.eConnect allows software developers to select their tool of choice whenworking with eConnect. Developers can use Microsoft .NET, Microsoft SQLServer stored procedures, BizTalk, or MSMQ.

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

4. Use XML to transfer data.eConnect uses XML documents to move data into and out of MicrosoftDynamics GP. The XML documents are a text-based representation of backoffice data. An XML schema specifies the data that is included in each type ofXML document. This allows eConnect to provide back office integration to anyapplication capable of creating or consuming these XML documents.

Getting started

How you start depends on your role:

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

• Review Chapter 2, “eConnect Architecture,” to understand the components thatcomprise an eConnect installation. This information can help you to understandhow eConnect will fit with your existing systems.

• Review Chapter 3, “Prerequisites,” to determine whether your system has allthe prerequisites for eConnect. You may need to install some additionalsoftware or configure Dynamics GP before installing eConnect.

• Review Chapter 4, “eConnect Installation,” to acquaint yourself with theeConnect installation procedure.

• Review Chapter 5, “Configuring eConnect Services,” to understand theconfiguration files used to control eConnect’s Windows services and BizTalkadapter. You control the behavior of the services and adapter by changing thevalues stored in the configuration files.

• Review Chapter 6, “Maintenance,” to learn what you can do to revise, repair, orremove an existing eConnect installation.

Software DeveloperIf you are a developer, complete the following:


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 witheConnect’s components. You need to understand how eConnect’s componentswork together to meet your integration requirements.

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

• Review the eConnect Programmer’s Guide and Reference document. Thedocument describes eConnect’s tools, application programming interfaces(APIs), and XML schemas. Use the eConnect Programmer’s Guide andReference to learn how eConnect meets your application integrationrequirements.



Chapter 2: eConnect ArchitectureWhen using eConnect for Microsoft Dynamics GP, it is helpful to understand itsarchitecture. 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 provideprogrammatic access to Microsoft Dynamics GP data. The following diagramillustrates the basic components:

Microsoft

MSMQ

Incoming Outgoing

ReplicationTransactionRequester

XMLXML XML

Service

Service Service

BizTalk

BizTalk

Server

Adapter

Dynamics GP

XML

IntegratingApplications

RuntimeLayer

Data AccessLayer

Business Objects

Pre PostSQL stored procedures

.NET Assemblies

COM+ Object

XML



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

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

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

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

• The eConnect application programming interfaces (APIs) allow you toprogrammatically interact with the eConnect business objects using eConnectXML documents. The eConnect API include a .NET and a MSMQ interface.

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

• The Transaction Requester allows you to publish Microsoft Dynamics GPdocuments to a queue. You typically use the Transaction Requester with theOutgoing Service to publish specified Microsoft Dynamics GP documents aseConnect XML documents. The Transaction Requester identifies the specifictransactions the Outgoing Service needs to publish.

• The Replication Service allows you to replicate transactions that occur inMicrosoft Dynamics GP to another database.

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

Configurations

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

SQL Server with Dynamics GP Data

+eConnect Business

Integrating application+

eConnect APIeConnect COM+ ApplicationeConnect Transaction RequestereConnect Replication Service

Local Network

Objects


C H A P T E R 2 E C O N N E C T A R C H I T E C T U R E

An alternate configuration installs the eConnect runtime on the Microsoft DynamicsGP server. This is shown in the following illustration:

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

Business objects

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

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

The eConnect business objects include Dynamics GP documents and transactionsthat are commonly used in application integration. While eConnect supplies a largenumber of documents, not every Dynamics GP feature is available througheConnect.

See the eConnect Programmer’s Guide and Reference for information about customizing business logic.

You cannot modify eConnect stored procedures. However, eConnect provides analternative that allows you to customize its business logic. Each stored procedureincludes specially named pre and post stored procedures. You customizeeConnect’s business logic by adding SQL queries and commands to these pre andpost procedures. The pre stored procedure runs your custom code immediatelybefore the eConnect stored procedure, while the post stored procedure runsimmediately after the eConnect stored procedure.

SQL Server with Dynamics GP Data

+eConnect Business Objects

eConnect APIeConnect COM+ ApplicationeConnect Transaction Requester eConnect Replication ServiceIntegrating Application



The following diagram illustrates the relationship between an eConnect storedprocedure and its pre and post stored procedures:

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

Once eConnect installs its business objects, the stored procedures are available onthe server and can be utilized by your application. However, a direct call to aneConnect 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 APIsthat eConnect supplies. These API provide a simpler approach to using theeConnect business objects.

eConnect API

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

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

stored procedurecalled

executes prestored procedure

executes poststored procedure

The eConnect stored procedure cannot be modified.

Start

“Pre” storedprocedure

eConnect stored procedure

“Post” stored procedure



Schema information can be found in the eConnect Programmer’s Guide and Reference

To use the eConnect API, your application must create or read eConnect XMLdocuments. eConnect supplies XML schema to specify the contents of eachdocument.

A schema is an XML file (with typical extension .xsd) that describes the syntax andsemantics of XML documents using a standard XML syntax. An XML schemaspecifies the content constraints and the vocabulary that compliant documents mustaccommodate.

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

The COM+ application supports the following APIs:

Microsoft .NETeConnect installs .NET assemblies on your computer and adds them to the globalassembly cache. The assemblies use the COM+ application to access the eConnectbusiness objects. To use eConnect in a .NET development project, add references tothese assemblies.

MSMQThe MSMQ API uses MSMQ queues and Windows services to asynchronouslytransport data between your application and Microsoft Dynamics GP. Yourapplication must be able to access the queues used by the services. Both theIncoming and Outgoing services use the COM+ application to access the eConnectbusiness objects.

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

The eConnect Outgoing Service relies on SQL triggers and the business objects toretrieve specified eConnect documents. The service stores the documents in aspecified queue. Your application must monitor the queue, retrieve the supplieddocuments, 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 adapterallows you to use BizTalk to manage interaction with eConnect business objects.

The BizTalk adapter supports the use of eConnect as a part of a BizTalkorchestration or in a simple pass-through situation.

Transaction Requester

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



The following diagram illustrates the Transaction Requester:

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

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

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

• eConnect_Out_Setup This table contains configuration information forthe Transaction Requester. To keep the Transaction Requester working, do notmake changes to this table.

• eConnectOutTemp This table is a temporary data store.

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

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

Microsoft Dynamics GPdatabase

MSMQ

OutgoingService

An application createsa new record.

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

eConnect_Outtable

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



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

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

Replication Service

eConnect includes the Replication Service that copies selected data changes fromMicrosoft Dynamics GP to a specified target database. The Replication Serviceasynchronously updates the target database to reflect changes made in DynamicsGP.

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

The following diagram illustrates the Replication Service:

External application

XML

XML

Microsoft Dynamics GPdatabase

MSMQ

OutgoingService

ReplicationService

The Replication Services retrievesthe XML document from the

eConnect outgoing queue andinserts the new data into the

specified external applicationdatabase.

eConnect_Outtable

database

An application creates a newrecord in Microsoft Dynamics GP.

The Outgoing Service queries theeConnect_Out table, retrieves thedata, creates an XML document,and places the document in the

eConnect outgoing queue.

The data from the record createdin Microsoft Dynamics GP is visible

in the external application.

The Transaction Requester’s SQLtrigger reacts to the record’s

creation, and inserts an entry tothe eConnect_Out table.

eConnectOutgoing queue



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

• The Transaction Requester specifies the documents and transactions toreplicate.

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

• The eConnect Replication Service takes the documents from the OutgoingQueue and uses the data to replicate the transaction directly into the externalapplication’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 theReplication Service, you must configure the service. For a detailed explanation ofhow to configure the Replication Service, see Replication Service on page 39.

PA

RT

2: IN

ST

ALLA

TIO

N


Part 2: InstallationThis portion of the documentation explains how to install eConnect for MicrosoftDynamics GP. The following information is discussed:

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

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


Chapter 3: PrerequisitesBefore installing eConnect for Microsoft Dynamics GP, there are severalprerequisites you must check. This portion of the documentation describes thesoftware requirements and the additional steps to perform before installingeConnect. 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 operatingsystems:

• 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 installerverifies that the Microsoft .NET 2.0 Framework is installed on your computer. If theframework is not found, the eConnect installer stops and instructs you to install theMicrosoft .NET 2.0 Framework.

COM+ user account

The eConnect COM+ application uses SQL Server integrated security to connect tothe eConnect business objects. During the installation of eConnect, you need tosupply 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 DynamicsGP server in a domain environment, select or create a domain user account.

• If you plan to install eConnect on a different computer than the DynamicsGP server in a workgroup environment, select or create a user on theDynamics GP server.

• If you plan to install eConnect on the same server as Microsoft DynamicsGP, select or create a local user account.

P A R T 2 I N S T A L L A T I O N


2. Give the user account database access. Add the user account you selected or created to the DYNGRP role for thesystem (DYNAMICS) database and for each company database that will beused with eConnect.

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

Distributed Transaction Coordinator (DTC)

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

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

1. Open Add or Remove Programs.Choose to add or remove Windows Components. The Windows ComponentsWizard will be displayed.

2. Select the Application Server components.Click Details to display the Application Server Details.

Mark Enable network DTC access. Click OK.


C H A P T E R 3 P R E R E Q U I S I T E S

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

Configuring DTCIf the two computers are in the same domain, the default configuration for DTC canbe used with eConnect. If you have made modifications to the securityconfiguration 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 nothave an established trust relationship, update your DTC security configuration touse No Authentication Required. To configure DTC, complete the followingprocedure:

1. Open Component Services.For Windows XP and Windows Server 2003, use the Start menu to accessAdministrative 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’soperating system.

Windows XP and Windows Server 2003 Expand the ComponentServices node, and then expand the Computer node to display the MyComputer node.

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

Windows Vista Expand the Component Services node, expand the MyComputer node, and expand the Distributed Transaction Coordinator node.Select the Local DTC node. From the Action menu, choose Properties. Select theSecurity tab.



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, completethe following procedure:

1. Open the Multicurrency Setup window in Microsoft Dynamics GP.Choose Tools >> Setup >> Financial >> Multicurrency from the MicrosoftDynamics GP menu. Set the Functional Currency. This example designates USdollars as the functional currency.

Refer to the Microsoft Dynamics GP documentation for additional informationabout currency setup and multicurrency access.

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


C H A P T E R 3 P R E R E Q U I S I T E S

Microsoft Message Queueing (MSMQ)

Application integrations that use the eConnect Incoming, Outgoing and Replicationservices use MSMQ to transport and store XML documents. These XML documentsrepresent data retrieved from or sent to Microsoft Dynamics GP. You can installeConnect prior to installing MSMQ, but the eConnect services will not start untilMSMQ 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 WindowsComponents.

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 WindowsComponents Wizard.



Chapter 4: eConnect InstallationThis portion of the documentation describes how to install eConnect for MicrosoftDynamics 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 forthe computer on which you are installing eConnect.

2. Start the eConnect installer.To install only the eConnect runtime components, start the installer namedeConnectRuntime.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 thecomponents you have installed on the server. For example, the option to installthe BizTalk 2006 Adapter is available only when the install detects BizTalkServer 2006 is present.

When you click a button for a feature, a pop-up menu of options appears. Referto 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.



To include a feature, click the button and select “Install entire feature.” Toexclude 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 BizTalk2004 application integration component (AIC) adapter.

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

COM+ Components Installs the COM+ application and .NET Assembly inCOM+ Administration. Also registers the .NET Assembly in the globalassembly 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 theeConnect business objects. The eConnect Incoming Service, Outgoing Service,and COM+ application will use this account. Enter the domain\login andpassword credentials for the user account you set up as an eConnectprerequisite. For more information about creating a user account see COM+ useraccount on page 21.

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

Click Next to continue.


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 severalminutes.

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 theeConnect event log, open the Start menu and select Control Panel >>Administrative Tools >> Event Viewer. Click eConnect to view the current listof messages.

What to do next

After eConnect for Microsoft Dynamics GP has installed, consider taking thefollowing steps:

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

• To learn about developing applications that use eConnect for MicrosoftDynamics GP, retrieve and install the eConnect for Microsoft Dynamics GPSoftware Development Kit (SDK).


PA

RT

3: A

DM

INIS

TR

AT

ION


Part 3: AdministrationThis portion of the documentation explains the configuration and maintenanceoptions for eConnect for Microsoft Dynamics GP. The following information isdiscussed:

• Chapter 5, “Configuring eConnect Services,” describes configuration optionsfor eConnect services and the BizTalk adapter.

• Chapter 6, “Maintenance,” describes how to make changes to an existingeConnect installation.

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

• Chapter 8, “Troubleshooting,” discusses how to troubleshoot issues that occurwhen using eConnect.


Chapter 5: Configuring eConnect ServicesAfter installing eConnect, you may need to configure the eConnect services or theBizTalk adapter. The following sections describes how to configure thesecomponents:

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

Overview

The complete eConnect installation adds three Windows services to yourcomputer’s Service Control Manager. The installer initially configures each serviceand stores the configuration information in an XML file. These XML configurationfiles contain keys and values that control the operation of each service. To customizethe behavior of a service or to adjust the service to reflect changes in your serverenvironment, 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 youwill always be able to restore the service if necessary.

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

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

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

Incoming Service

The Incoming Service integrates eConnect XML documents into MicrosoftDynamics GP. The Incoming Service uses a configuration file namedeConnect_Incoming.exe.config to control its operations. This file is found in theeConnect installation location, typically C:\Program files\CommonFiles\Microsoft Shared\eConnect 10\Services\Incoming Service.

The following example displays the contents of an eConnect_Incoming.exe.configfile:

<? 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=""/>

P A R T 3 A D M I N I S 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 theservice 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’sname.

eConnect.Transactional_deadletter_Queue This key specifies whereundeliverable 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 transactionaldeadletter queue.

A value of ”1” stores undeliverable messages in the deadletter queue associatedwith the message queue specified by the eConnect.Incoming_Queue key. If theeConnect.Incoming_Queue key has value="", the service sends undeliverablemessages to machine_name\private$\econnect_incoming_deadletter.

If the eConnect.Incoming_Queue key specifies a queue name, the service sendsundeliverable messages to a queue with a name that appends _deadletter to thespecified queue name. For example, the eConnect.Incoming_Queue key setsvalue="machine_name\private$\TestQueue", the service sends undeliverablemessages to the queue named machine_name\private$\TestQueue_deadletter.

eConnect.Schema.Type This key specifies whether to perform schemavalidation 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 isXSD. You set the value to XSD when you want to validate an eConnect XMLdocuments against the eConnect schema.

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

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


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 thespecified operation is allowed to proceed. No log entry is made about the omittednode. Invalid data values are detected and logged as an error in the eConnect eventlog even when schema validation is not performed. XML documents with invaliddata are discarded after logging the error message.

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

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

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

eConnect.BackOffice.ConnectionString This key stores the connectionstring the service uses to connect to the Microsoft Dynamics GP SQL Server. Thedefault 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. Forexample, you may change the data source or initial catalog parameters to reflectchanges in your server configuration.

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

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

eConnect.LogAll The key specifies the types of messages to log in the eConnectevent 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 theeConnect event log.

eConnect.Threads This key specifies the number of threads that are availablewhen 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 anynumber between 0 and 19. A value of 19 makes 20 threads available when theservice starts. A higher number of threads should allow the service to processdocuments more quickly.



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

Outgoing Service

The Outgoing Service allows you to integrate transaction information originating inMicrosoft Dynamics GP into your application. The Outgoing Service creates XMLdocuments and stores them in a message queue. Your application must retrievethese messages to use the XML documents they contain. The Outgoing Servicecreates a default queue named machine_name\private$\econnect_outgoing to storeoutgoing messages.

The Outgoing Service works in conjunction with the eConnect TransactionRequester. Use the Transaction Requester to specify the Dynamics GP documentsyou want sent to the message queue. Refer to Transaction Requester on page 42section for more information.

The Outgoing Service uses a configuration file namedeConnect_Outgoing.exe.config to control its operations. This file is found in theeConnect installation location, typically C:\Program Files\CommonFiles\Microsoft Shared\eConnect 10\Services\OutgoingService\eConnect_Outgoing.exe.config.

The following example displays the contents of an eConnect_Outgoing.exe.configfile:

<?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 wantthe 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 isan insert, update, or delete operation for the Dynamics GP document types selectedusing the Requester Enabler/Disabler utility.



The following is a list of possible action types:

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

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

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

The following is a list of possible output types:

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

Requester.Remove This key specifies whether or not the record is deleted fromthe 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” keepsthe record in the eConnect_Out table.

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.

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.



The service queries the list of records in the eConnect_Out table. It then cyclesthrough 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 duplicatedocument in the message queue each time it runs.

Timer1.Interval This key specifies the number of milliseconds the service pausesbetween 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 onyour computer.

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

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

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

eConnect.BackOffice.ConnectionString This key stores the connectionstring the service uses to connect to the Microsoft Dynamics GP SQL Server. Thedefault 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. Forexample, you may change the data source or initial catalog parameters to reflectchanges in your server configuration.

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

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

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

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

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

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



• Add database3="CONTOSO” as an attribute to the DatabaseNames node of theOutgoing Services’s configuration file. The update to the DatabaseNames nodeappears as follows:

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

Replication Service

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

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

The Replication Service uses a configuration file namedeConnectFrontOfficeService.exe.config to control its operations. This file is found inthe eConnect installation location, typically C:\Program Files\CommonFiles\Microsoft Shared\eConnect 10\Services\ Replication Service\.

The following example displays the contents of aneConnectFrontOfficeService.exe.config file:


<configuration >

<appSettings >

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

source=127.0.0.1;initial catalog=TWO_FRONT;integrated



source=127.0.0.1;initial catalog=DYNAMICS_FRONT;integrated


<addkey="eConnect.Requester.Incoming_Queue.0

"value=".\private$\econnect_company_front"/>


"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 frontoffice databases. The front office database is specified by the key namedeConnect.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 eachkey. The following example shows a connection string key that specifies a secondtarget database:



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

datasource=127.0.0.1;initial catalog=DYNAMICS_FRONT;integrated


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

For example, the eConnect.Requester.Incoming_Queue.0 andeConnect.Requester.DeadLetter_Queue.0 keys specify the queues for theeConnect.FrontOffice.ConnectionString.0 key. The eConnect.Requester.Incoming_Queue.0 value specifies the queue where the Incoming Service is storing XMLdocuments that need to be replicated to the front office database. The followingillustrates these three related keys:

You must add the correct connection string and queue information to the configuration filebefore 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 addressand 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"/>


<configuration >

<appSettings >


source=127.0.0.1;initial catalog=TWO_FRONT;integrated



source=127.0.0.1;initial catalog=DYNAMICS_FRONT;integrated



"value=".\private$\econnect_company_front"/>


"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 connection string keyfor the first database.

The incoming queue keyfor the first database.

The deadletter queue keyfor the first database.



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

eConnect.Requester.Incoming_Queue.0 This key specifies the name andlocation a queue.

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

econnect_company_front"/>

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

eConnect.Requester.Incoming_Queue.1 This key specifies the name andlocation 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 documentsplaced in that queue to update the second front office database. The value specifiesthe queue where the eConnect Outgoing Service is placing the XML documents thatneed to be replicated.

eConnect.Requester.DeadLetter_Queue.0 This key specifies the name andlocation 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 undeliverablemessages for the first incoming queue.

eConnect.Requester.DeadLetter_Queue.1 This key specifies the name andlocation 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 undeliverablemessages for the second incoming queue.

eConnect.Timer.Interval This key specifies the number of milliseconds theservice pauses between checks for new messages in the incoming queues. Thedefault value is 1000 milliseconds.

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

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



Transaction Requester

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

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

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

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



Mark the Integrated Security check box to use your Windows logoninformation. If you clear the Integrated Security check box, you must supply aSQL user name and password that enables the Requester Setup Tool to accessthe 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 sendto MSMQ when a new document of that type is created.

To discontinue the publishing of a document, remove the check from the checkbox 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 tosend to MSMQ when a document of that type is modified.




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 sendto MSMQ when a document of that type is deleted.


7. Specify the queue to use for a document type.You can associate a specific MSMQ queue with a document type. If a queue isspecified, 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 XMLdocuments 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 andoperation. The triggers write to the eConnect_Out table in the databasespecified by the connection string. The eConnect Outgoing Service uses thistable to identify the XML documents to place in the specified queue. If youunmarked a check box to discontinue publishing a document type, the SQLtriggers 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 asimple pass-through situation. A BizTalk orchestration allows applications withdiffering message formats to integrate, while a BizTalk pass-through simply routesmessages between applications.



To configure the eConnect BizTalk 2004 adapter, you must have already installed MicrosoftVisual 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 >> BizTalkServer Administration. The BizTalk Administration Console opens. In BizTalkServer 2004, right-click Adapters and select New >> Adapter.

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

The Adapter Properties window opens.



2. Add the adapter.In the Name box, enter eConnect as a name for the send adapter. In the Adapterbox, 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 areusing BizTalk Server 2004, double-click the Send Handlers folder that displaysin the right pane.

The right pane displays a Host Name of BizTalkServerApplication. Right-clickBizTalkServerApplication and select Properties. The Adapter HandlerProperties window opens. BizTalk Server 2004 labels the windowBizTalkServerApplication Properties.

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



4. Edit the connection string property.Change the data source to point to your Microsoft Dynamics GP server and setthe initial catalog to DYNAMICS or the company database you want to workwith. Click OK to continue.

5. Close the Adapter Handler Properties window.Click OK to close the Adapter Handler Properties window. Close the BizTalkServer 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 AddSend Port. The Create New Send Port dialog opens. Select Static One-WayPort. 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 theeConnect adapter you created earlier.



8. Open the Transport Properties window.Select Address (URI) and click the ellipsis(...) button to open the eConnectTransport Properties dialog box. Set the connection string’s data sourceparameter to point to your Microsoft Dynamics GP SQL Server. Set the initialcatalog parameter to the Dynamics GP database you want to work with.


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



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 theleft 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 nameof the receive port.


11. Save the send port configuration.Click OK. Close Visual Studio.



Chapter 6: MaintenanceThis portion of the documentation provides information about modifying,repairing, or removing an existing eConnect installation. The following items arediscussed:

• Modifying an eConnect installation• Completing a repair• Removing eConnect

Modifying an eConnect installation

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

1. Start the eConnect installer.Open Add or Remove Programs, choose eConnect Runtime for MicrosoftDynamics GP 10.0. Click Change.

2. Choose Add/Remove Features.The Modify eConnect Runtime for Microsoft Dynamics GP 10.0 Installationwindow opens.

Click Add/Remove Features.

3. Specify the features to add or remove.The Select Features window opens. Additional information about selectingeConnect features can be found in Chapter 4, “eConnect Installation.” ClickNext.

4. Begin the installation.Click Install to add or remove the specified features. The installer may takeseveral minutes to complete the update.

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



Completing a repair

If the eConnect for Microsoft Dynamics GP application becomes damaged, therepair 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:


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

Click Repair.

3. Specify eConnect account information.You must supply the domain, user name and password of the windows accountthat the eConnect Incoming Service, Outgoing Service, Replication Service andCOM+ application use. Refer to Chapter 4, “eConnect Installation,” foradditional information about the eConnect windows account. Click Next tocontinue.

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

5. Installation completeWhen the Installation Complete window appears, click Exit to close thewizard.


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 eConnectfolders and files. It deletes only the files and folders created in the local machine’sfile system.

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


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

Click Remove.

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

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



Chapter 7: UtilitieseConnect includes several utilities that help to configure and administer somecomponents. 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 GPdocument types to publish as eConnect XML documents to a Microsoft messagequeue (MSMQ). The utility also allows you to specify a queue for each document.

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

eConnect MSMQ Control

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

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



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

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

To view or edit a specific message, click its label in the list box. The MessageContents textbox at the bottom of the screen displays the message. If you want tochange 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 targetqueue in the Queue Path for Resending text box. Click Resend. The Message Logtextbox logs any messages from resending the message. The eConnect MSMQControl also allows you to indicate whether to leave the original messages in thequeue or have the original message deleted once the messages is resent. TheeConnect MSMQ Control also allows you to relabel a message.


C H A P T E R 7 U T I L I T I E S

eConnect Release Information

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

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

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

To use your Windows logon credentials, mark the Windows Integrated Securitycheck 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 WindowsIntegrated Security check box. Enter your SQL user name and password.

Click Connect or choose Retrieve from the menu.



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

To close the eConnect Release Information window, choose Close.


Chapter 8: TroubleshootingIf you encounter problems with eConnect for Microsoft Dynamics GP, the followingsections may be helpful. They describe some of the most common situations thatcan 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 eConnectbusiness object for the new company, you may encounter problems when eConnectattempts a create, update, or delete operation. Common examples include:

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

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

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

To use the eConnect business objects, you must define a functional currency for thenew company. eConnect requires a currency ID for the company, even ifmulticurrency is not being used. Review the setup procedure, Functional currency onpage 24, to specify a functional currency.

Connection string problems

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

Integrated Security is required.

Please ensure that the ConnectionString input parameter is valid.

To eliminate the error, check the connection string. The connection string mustcontain:

Integrated Security=SSPI;

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

Login problems

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



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

• Verify that the login account can access the SQL Server where the eConnectbusiness objects are installed. The login must be able to access the MicrosoftDynamics GP server.

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

• Verify that the login account is assigned to the DYNGRP database role. Thelogin account must have the DYNGRP role for the DYNAMICS database andeach 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 followingerror 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 eConnectIncoming and Outgoing services. Refer to Microsoft Message Queueing (MSMQ) onpage 25 for instructions on installing MSMQ.

eConnect event log

The eConnect install creates an event log that records error, warning andinformational messages generated by eConnect. To view the eConnect event log,open the Start menu and select Control Panel >> Administrative Tools >> EventViewer. 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 ifeConnect is logging any messages that specify the cause of the error.

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

• If you validate incoming XML documents, the event log will contain errormessages about the documents that failed validation. Use the messages in theevent 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. Usethe information contained in the messages to identify the corrective actions that areneeded.


C H A P T E R 8 T R 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 GPdata changes do not occur. The Incoming Service processes the incoming XMLdocuments, but some insert, update, or delete operations are not completed. Themissing operations may result from using schema validation with the IncomingService.

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

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

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

• Use the error information to determine what is causing the validation problem.Change the application that generates the XML documents to comply with theeConnect 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 fromlogging an error when an XML document contains an unknown element name,or the order of the elements in the document differ from the document’sschema.

COM+ application

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

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



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


GlossaryApplication programming interface(API)

A set of functions or features you access toprogrammatically use or manipulate asoftware component or application.

Back officeA financial management system. In aneConnect environment, this refers toMicrosoft Dynamics GP.

BizTalk serverA Microsoft platform that manages theexchange of data between applications.

BizTalk adapterA preconfigured BizTalk ApplicationIntegration Component (AIC) that allowsBizTalk server to use eConnect.

Business objectsThe collection of SQL stored procedures thatcontain eConnect’s business logic.

COM+ applicationA programming structure encapsulatingdata and functionality. In eConnect, thisstructure calls the SQL stored procedures(business objects).

Connection stringA text representation of the initializationproperties needed to connect to a data store.

eConnectA collection of tools, components, and APIsthat provide programmatic integration withMicrosoft Dynamics GP.

eConnect XML documentA text document that describes MicrosoftDynamics GP data. The eConnect XMLschema specifies the content and structure ofdata in the document.

Front officeAn application that communicates with theback office. Examples include customerrelationship management systems, datawarehouses, and web sites.

Functional currencyThe currency an organization uses to keepthe bulk of its financial records.

Incoming ServiceA Microsoft Windows service that monitorsa queue for new eConnect XML documents.Valid documents are used to create, update,or delete records in Microsoft Dynamics GP.

Integrated securityThe SQL server security option thatleverages Windows authentication to supplythe user’s login credentials. It allows anetwork user to access a SQL server databasewithout supplying separate logincredentials.

Microsoft message queuing(MSMQ)

A message infrastructure and developmentplatform for creating distributed, loosely-coupled messaging applications.

Outgoing ServiceA Microsoft Windows service that publisheseConnect XML documents to a specifiedqueue. The XML documents representdocuments that were created, updated, ordeleted in Microsoft Dynamics GP.

Post stored procedureA customized SQL stored procedure thatruns immediately after an eConnect storedprocedure.

Pre stored procedureA customized SQL stored procedure thatruns immediately before an eConnect storedprocedure.

Replication ServiceA Microsoft Windows service that copiesselected data changes from MicrosoftDynamics GP to a specified target database.

SchemaAn XML file (with typical extension .XSD)that describes the syntax and semantics ofXML documents using a standard XMLsyntax. An XML schema specifies the contentconstraints and vocabulary that compliantdocuments must accommodate.

ServicesMicrosoft Windows services are long-running applications that perform somesystem function. They typically do notdisplay any user interface. eConnect usesseveral services for moving eConnect XMLdocuments in and out of various messagequeues.

Stored procedureA group of Transact-SQL statementscompiled into a single execution plan. Thebusiness logic for eConnect is contained instored procedures.

Transaction RequesterThe Transaction Requester publisheseConnect XML documents to a queue. TheXML documents represent MicrosoftDynamics GP documents. Use the eConnectRequester Setup utility to specify thedocuments to publish.

TriggerA special class of SQL stored procedure thatexecutes automatically when an update,insert, or delete statement is issued for atable or view.

XMLA text-based format that uses markup tags(words surrounded by ‘<‘ and ‘>’) todescribe how a document is structured andthe data it contains.



IndexAAdministration, part 32-62API, see application programming

interfaceapplication programming interface

BizTalk 15defined 63Microsoft .NET 15MSMQ 15Replication Service 17requirements 15

architecturechapter 11-18diagram 11layers

API 11data 11described 11

assemblies, .NET 15

Bback office, defined 63backups, configuration files 33BizTalk adapter

configuration 44-49defined 63requirements 44

BizTalk integrationdescribed 15types 44

BizTalk server, defined 63business logic, customizing 13business objects

see also stored proceduresafter removing eConnect 53business logic 13customizing business logic 13defined 63described 13stored procedures 14

CCOM+ object

defined 63described 14logon requirements 14troubleshooting 61user account 21

components, described 28Configuration, chapter 33-49configuration files

backup copy 33Incoming Service 33Outgoing Service 36Replication Service 39restarting the service 33

configurationsclient/server 12

configurations (continued)single server 12

connection stringdefined 63Incoming Service 35Outgoing Service 38Release Information 57Replication Service 40Transaction Requester 42troubleshooting 59

conventions, in documentation 2corrupt files, repairing 52currency, see functional currencycustomizing, business logic 13

DDatabaseNames, setting for the Outgoing

Service 38Delay.Interval 38Distributed Transaction Coordinator

configuring 23described 22enabling 22

documentation, symbols and conventions 2

EeConnect

application programming interface 14architecture diagram 11business logic 13business objects 13components described 15customizing business logic 14defined 63described 7event log 29modifying 51prerequisites 21removing 53repairing 52Replication Service 17stored procedures 14support 3uses 7XML documents 8

eConnect Basics, part 6-18eConnect Overview, chapter 7-9eConnect.BackOffice.ConnectionString 35,

38eConnect.FrontOffice.ConnectionString.0

40eConnect.FrontOffice.ConnectionString.1

40eConnect.Incoming_Queue 34eConnect.LogAll 35eConnect.Requester.DeadLetter_Queue.0

41eConnect.Requester.DeadLetter_Queue.1

41eConnect.Requester.Incoming_Queue.0 41

eConnect.Requester.Incoming_Queue.1 41eConnect.Schema 35eConnect.Schema.Type 34eConnect.Threads 35eConnect.Timer.Interval 41eConnect.Transactional_deadletter_Queu

e 34event log

described 29troubleshooting 60

Ffront office, defined 63front office database, described 39functional currency

defined 63setup 24troubleshooting 59

IIncoming Service

configuration 33-36configuration keys 34-36

connection string 35event log 35message queues 34multithreading 35schema validation 34

defined 63described 15

installationchapter 27-29customizing the installed

components 28eConnect event log 29part 20-29prerequisites 21procedure for eConnect 27-29required login role 27results 29system configurations

BizTalk Server 13client/server 12single server 12

integrated security, defined 63

Llight bulb symbol 2

MMaintenance, chapter 51-53margin notes 2Microsoft .NET Framework 21Microsoft message queuing

defined 63described 25installing 25monitor queue activity 56MSMQ Control 55services 15start the MSMQ control 55

I N D E X


Microsoft Visual Studio .NET 2003, BizTalk configuration 44

missing files, repairing 52modifying

described 51eConnect installation, procedure 51

MSMQ, see Microsoft message queuingMSMQ Control

described 55monitoring queue activity 56starting 55

multithreading, Incoming Service 35

N.NET assembly 15.NET Framework 21

Ooperating system, required 21Outgoing Service

see also Transaction Requesterconfiguration 36-39configuration keys 36-39

action types 36connection string 38database names 38delay interval 38output types 37remove record 37time interval 38


Pperformance, optimizing 35Prerequisites

chapter 21-25COM+ user account 21Distributed Transaction Coordinator

22functional currency 24Microsoft .NET Framework 21operating system 21

product support, for Microsoft Dynamics GP eConnect 3

Rregistry entries, repairing 52Release Information

connection string 57described 57viewing the release number 57

removing eConnect 53repair, described 52repairing eConnect, procedure 52Replication Service

adding a database 39configuration 39-41configuration keys 40-41

connection string 40message queues 41time interval 41

Replication Service (continued)defined 63described 17

Requester Tool 42-44, described 55Requester.Action 36Requester.OutputType 37Requester.Remove 37roles

software developer 8system administrator 8

Sschema

defined 63described 15files 35

schema validation, see validationservices

see also Incoming Service, Outgoing Service, Replication Service

defined 63described 33restarting 33troubleshooting 60

software developer, responsibilities 8SQL trigger

defined 63Requester Tool 16

stored proceduressee also business objectscalling 14defined 63described 14modifying 13post 63pre 63

support, for Microsoft Dynamics GP eConnect 3

symbols in documentation 2system administrator, responsibilities 8

Ttechnical support, for Microsoft Dynamics

GP eConnect 3threads, Incoming Service 35Timer1.Interval 38Transaction Requester

configuration 42-44connection string 42database tables 16defined 63described 15Requester Tool 42, 55

troubleshootingchapter 59-62COM+ object 61connection string 59event log 60functional currency 59Incoming Service 61login problems 59

troubleshooting (continued)services 60

Uuninstall

described 53removing eConnect 53

user accountCOM+ object 21troubleshooting 61

utilitieschapter 55-58MSMQ Control 55Release Information 57Requester Tool 55

Vvalidation

described 34error messages 34schema files 35troubleshooting 61

Visual Studio .NET, BizTalk configuration 44

Wwarning symbol 2windows services, see services

XXML, defined 63XML document


Documents

eConnect Installation and Administration Guide · 2009-01-13 · Server stored procedures, BizTalk, or MSMQ. 3. Leverage industry-standard technologies. eConnect includes components