Overview of service deployment

After you create and build the components for your service, you need to deploy your components to the Dynamics GP server or servers. Before you attempt to deploy your service, verify that your components are built and verify the location of the component files. To deploy a service, you need the following components.

Component	Description
SQL stored procedures	The SQL scripts that add the eConnect SQL stored procedures that create, update, or delete Dynamics GP database records.
Transaction Requester metadata	A SQL script that adds the metadata the eConnect Transaction Requester uses to retrieve fields for a document or summary document.
eConnect error codes	A SQL script that adds custom error codes and messages to the eConnect error reporting system.
Document type assembly	A .NET assembly that contains the classes that define a new type of document, summary document, list criteria, and list. The Dynamics GP Service framework uses the classes in this assembly to create, update, delete, and retrieve data in the Dynamics GP database.
Security metadata	The application and application configuration file you use to add custom security metadata to the Dynamics Security Service.
Policy metadata	The application and application configuration file you use to add custom policy metadata to Dynamics GP services.
Policy resource assembly	A .NET assembly that contains the strings and labels the Dynamics Security Console uses when displaying your policy information.
Service assembly	An assembly and configuration file that define the service interface and its methods. The settings in the configuation file enables the Dynamics GP Service to host your service.
XSLT files	The XSLT files that allow the Dynamics GP Service framework to transform service XML documents to and from the eConnect XML documents.