eConnect Adapter
The Neuron eConnect adapter receives messages from Neuron and publishes them to Microsoft Dynamics Great Plains 10, via eConnect. The adapter supports data submission to, and data retrieval from, Great Plains.
Requirements
Microsoft Dynamics Great Plains 10 eConnect must be installed on the Neuron ESB Server. Additionally, one should ensure the eConnect business objects are installed on the Great Plains 10 server.
Adapter Modes
The adapter supports the following modes of operation.
| Mode | Description |
| Subscribe | For data submission. Send an eConnect XML message from Neuron to Great Plains. |
| SubscribeTwoWay | For data submission. Send an eConnect XML message from Neuron to Great Plains. The requestor will receive a standard fixed response message. |
| Query | For data retrieval. Send an eConnect out XML message from Neuron to Great Plains. The requestor will receive the response message. |
Subscribe Mode
This mode is used when one is submitting data to Great Plains.
When the adapter receives a message from Neuron, the body of the ESBMessage is sent to Great Plains via eConnect and no response message is published.
The XML document will be validated against the eConnect schema provided in the eConnect Schema Location property.
SubscribeTwoWay Mode
This mode is used when one is submitting data to Great Plain.
When the adapter receives a message from Neuron, the body of the ESBMessage is sent to Great Plains and, if successful, a standard XML response message is sent to the requestor.
The XML document will be validated against the eConnect schema provided in the eConnect Schema Location property.
Query Mode
This mode allows one to retrieve data from Microsoft Dynamics GP.
When the adapter receives a message from Neuron, the body of the ESBMessage is sent to Great Plains and, if successful, the response message is sent to the requestor.
Adapter Properties
| Property Name | Description |
| Connection String | Sets the connection string for the SQL database used by eConnect and MS Dynamics GP 10. |
| Enable Error Handling | Set this property to true, to send eConnect exception messages back to the requestor when in Query or SubscribeTwoWay mode. |
| eConnect Schema Location | Sets the full path location of the eConnect.xsd file. This schema is used for validation when in Subscribe or SubscribeTwoWay mode. |
Adapter Metadata
This adapter does not use any metadata properties.
Message Format
The body of the ESBMessage received from Neuron must be an eConnect document that conforms to the eConnect XML document structure. For additional detail on the message format, please see:
- Microsoft Dynamics GP 10.0 eConnect programmer’s guide and reference
- The eConnect schema reference
- The eConnect XML documents and examples
Subscribe Mode
This mode is for data submission and the eConnect XML document format should be that of one for data submission. A data submission XML example can be found here. An example of how to use the eConnect objects to create eConnect XML files can be found here: eConnect serialization example.
SubscribeTwoWay Mode
This mode is for data submission and the eConnect XML document format should be that of one for data submission. A data submission XML example can be found here. An example of how to use the eConnect objects to create eConnect XML files can be found here: eConnect serialization example.
This mode functions that same as subscribe mode with the exception that a standard reply message will be sent back to the party that submitted the XML.
To use this mode properly, the Semantic header of the ESBMessage must be set to Request. If the Semantic header is not set to Request, then the message will be discarded.
The reply that is returned is the following fixed message.
<eConnect>
<SuccessTransactionType>
<Message>Transaction successfully processed into Great Plains</Message>
</SuccessTransactionType>
</eConnect>
Query Mode
To request data using eConnect, the ESBMessage body must be an XML document that is typically used to request data. The <eConnectOut> XML node gives you the ability to query Microsoft Dynamics GP using eConnect’s XML-based syntax. A data retrieval XML example can be found here. An example of how to use the eConnect object to create eConnectOut XML files can be found here: eConnectOut serialization example.
To use this mode properly, the Semantic header of the ESBMessage must be set to Request. If the Semantic header is not set to Request than the message will be discarded.
The reply that is returned to the requestor will be the XML document returned from eConnect that represents the requested data. The eConnectOut serialization example contains a sample XML reply.
Error Reply Message
When the enable error handling property is set and an exception occurs during data submission to eConnect, an error reply message will be generated in the following format.
<eConnect>
<ErrorTransactionType>
<ErrorMessage></ErrorMessage>
<Source></Source>
</ErrorTransactionType>
</eConnect>