Mark Wilson I am the creator of TopXML. I am available for international and local (Australia) contracts. I am a Solution Architect/Business Analyst. I have worked in IT in several countries (NZ, Australia, South Africa, UK) building and training teams for government and very large non-governmental organizations. I am ex-Microsoft Consulting Services. I wrote the first book on Microsoft XML published in 2000 called XML Programming with VB and ASP. Most recently I have been building tools for the SEO industry. Ask me for a 37 point SEO health-checkup for your website.
First posted :
03/24/2008
Times viewed :
270
BizTalk and Connectors
Connectors fulfil specialized integration requirements by exposing select functions from
proprietary platforms to external clients. BizTalk solutions can benefit from
the use of connectors in order to expand native workflow logic to incorporate
logic and data sources that exist in disparate environments.
BizTalk Utilities provides sophisticated connector technology that accomplishes instant
connectivity – a cost-effective alternative to the significant effort typically
required to custom develop these types of integration channels.
Connectors versus Adapters
Many associate
connectors with adapters, as both perform similar functions within a typical
integration architecture. Since all BizTalk
Utilities products are designed purely
for the BizTalk Server environment, naming conventions provided by Microsoft
drive the terms used to identify BizTalk
Utilities components. For example,
Microsoft provides a SAP .NET Connector, which is capable of establishing
two-way communication with SAP solutions. BizTalk
Utilities leverages this
Microsoft connector by encapsulating its functionality and integrating it
directly within BizTalk. This product is therefore called the BizTalk
Utilities SAP Connector.
How it Works
As shown in the
diagram below, a
BizTalk Utilities connector closes the gap between BizTalk and
another solution platform.
BizTalk
Utilities connector solutions typically consist of the following components:
1.
An
Application Integration Component (AIC) designed to interface with a vendor
connector proxy or API. This component will likely be built using Microsoft
.NET technology, and will be responsible for transforming messages received by
BizTalk Server into the format expected by the outside application. Below are
some screen shots from the configuration screens used to set up the BizTalk
Utilities SAP Connector.
2.
Depending on
the nature of the two-way communications channel provided by the connector, a
Receive Function may also be supplied. Typically, this component will be
capable of remotely polling external applications for data or documents at
pre-set intervals ranging from seconds to days. Provided here are some sample
dialog screens from the IDoc Receiver receive function, which is part of the BizTalk
Utilities SAP Connector.
3.
A Connector
Proxy client provided by the vendor or development tool manufacturer. This is
the piece of software the BizTalk
Utilities connector interacts with to enable
remote communication between BizTalk and the vendor solution. This component is
generally not part of BizTalk
Utilities. Below are some sample screen shots
from the proxy generator for the SAP .NET Connector from Microsoft.
4.
Configuration
Wizards for various parts of the connector solution. These deployment tools
greatly simplify the installation and configuration of a BizTalk
Utilities connector by stepping you through the implementation process. Below are some
sample screens the Wizard used to set up the IDoc Router component of the BizTalk
Utilities SAP Connector.
It is also worth noting that most connectors are further
supplemented with Import and Output Configuration Wizards that allow for
configuration settings to be stored and retrieved from XML documents.
Summary
BizTalk Utilities
provides progressive support for contemporary connector technology. This can
give you a strategic edge when designing integration solutions around the use
of BizTalk Server.
Connectors play a
key role in almost any integrated environment that includes vendor-specific
platforms. BizTalk
Utilities integration products, such as the SAP Connector,
solve communication incompatibilities through a simple installation and
configuration process. There is really no better way of building
interoperability layers onto your BizTalk architecture. BizTalk
Utilities provides proven, robust, and easy-to-use technology components that literally
enable point-and-click integration.
To learn more about these and other features, download an evaluation copy of BizTalk
Utilities