Remote system setup
The Dynamicweb Integration Framework is a collection of components for transferring data and maintaining data consistency between a Dynamicweb solution and a remote system.
The integration data-flow is as follows:
- The Dynamicweb solution makes a request for data in XML format
- The request is relayed to the remote system by the Dynamicweb Connector service
- The plugin/code unit reacts by extracting data from the remote system
- The data is wrapped in an XML format understood by Dynamicweb (or - for passive plugins - returned as is, and transformed using XSLT on the Dynamicweb side)
- The XML is returned via the Dynamicweb Connector service to the Dynamicweb solution as a response
This article covers installing and configuring a plugin on the remote system, which will expose a web service that can be queried for data by both the DynamicwebConnector TestTool (during setup) and the DynamicwebConnector Service (during test and production).
All data entering a Dynamicweb solution must be wrapped in an XML format understood by Dynamicweb. Not surprisingly, data in other systems is not immediately compatible with this format.
There are basically two scenarios for handling this issue:
- The remote system allows you to install an active plugin or code unit, which can extract and transform data before returning it to Dynamicweb
- The remote system is passive, and data transformation must be handled on the Dynamicweb side using e.g. XSLT, or via third party software
The installation and configuration of the active plugin varies depending on the remote system – select an appropriate setup guide below.
Passive remote systems
For passive remote systems, the transformation of data into the Dynamicweb format must be handled using e.g. XSLT on the Dynamicweb side of the integration, or by developing a custom scheduled task add-in.
Please see the Data Integration Module documentation for more information.
Once the plugin has been installed and configured, the web service can be queried for data.
If you follow the recommended project process, the next phase involves two tasks:
- Use the Dynamicweb Connector TestTool to extract data from the remote system and deliver it to the Dynamicweb side of the integration.
- Install and configure the Dynamicweb Connector Service, which makes it possible for the Dynamicweb solution to query the remote system for real data.