Customize Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorized as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

No cookies to display.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

No cookies to display.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

No cookies to display.

Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.

No cookies to display.

Advertisement cookies are used to provide visitors with customized advertisements based on the pages you visited previously and to analyze the effectiveness of the ad campaigns.

No cookies to display.

Help

Database Transport

The Database Transport provider enables you to receive data (in the form of a message) from a database query, and send data (as a message) to a database query.  Currently, only SQLServer and Access databases are supported though support for Oracle and MySQL are being implemented.

The Receive Transport requires you to configure a query.  If the query returns XML data (in SQLServer it contains the FOR XML directive), you should check the This query returns XML checkbox.  You also need to specify root and record names (the latter only if the query doesn’t return XML) and an XML namespace in order to form an XML Message.  The Test link allows you to preview the execution of the query, and Generate Schemas creates a compatible schema in your Schema library.

You can also specify a Commit Query, enabling for example the database to delete a record on successful processing.  This query will be executed when the message has been successfully submitted.  You can use the Insert Token link to insert fields from the message into the query as tokens (used to assist in correlation).

The Send Transport requires you to configure an update query, which similarly supports tokens to extract data from the Message or Message Context.  This update query can return a Response Message, which is configured in a similar way as for the Receive Transport, and can be obtained using a Receive Send Port Message Response Workflow Activity.

For example, imagine you have a Database table called CustomerDetails, and you have configured CustomerName and CustomerEmail properties on the General tab of the Send Port Configuration Form to be initialized from the Message Xml. To insert a record into the database, you could enter the following Update Query :

INSERT INTO CustomerDetails (CustRef, CustName, CustEmail) VALUES (’%MessageID%’, ’%CustomerName%’, ’%CustomerEmail%’)

Alternatively it would be better practice to use a stored procedure.  Note the ‘ quotes around the tokens, these are required in order for your query to be valid SQL once the tokens are replaced.

Note the ExecutionScope drop-down, which allows you to specify that the query is repeated for multiple Xml elements in the Message.  If a repeating scope is chosen, the Insert Token link allows you to insert XPath expressions directly.