CODEWITHSUNDEEP
biztalk
Mehrdad Kamelzadeh
Mehrdad Kamelzadeh

Reputation: 1784

Getting started with BizTalk

I am a .NET developer and I have developed a software for an organization in which there are 2 other different software applications. All these 3 applications are isolated and they don't send and receive data to and from any other software.

The organization's manager asked me to integrate these products.

After some research on the internet I found that I have to use BizTalk. Now I have some basic knowledge about BizTalk (like what are Schema,Maps,Pipelines,Orchestration etc).

The problem is that I don't know the changes I have to make for my own software and the change I have to ask the other developers (of the other software) to make in their own software to be able to integrate them via BizTalk.

Shall we make web services for our software?

Is that possible to connect directly to databases? Is that a good practice at all?

Any other suggestion or resources will be very appreciated.

Upvotes: 0

Views: 725

Answers (1)

DTRT
DTRT

Reputation: 11040

Since this a very broad topic, I'll stick to answering your specific questions:

  1. Sure, this is frequently called a Web Service Facade. It's most useful when many different apps will be calling into it.

  2. If you own the apps and their databases, yes, this is a perfectly valid solution. BizTalk connects natively to SQL Server and Oracle as well as other databases through an ODBC Adpater.

  3. You could also program your existing apps to emit and consume Xml messages.

Upvotes: 2

Related Questions