- This topic has 1 reply, 1 voice, and was last updated 8 years, 3 months ago by
.
-
Posts
-
-
Hi:
We are building an application (2 tier fat client) in .NET. The application has a requirement to notify all other instances of application running on different machine if records in database changes. for this, we are thinking to build a notification service running on a central server that the application which is changing the data will talk to and that service will notify all the other machines running the same application. All the applications need to susbcrivbe to the notification service, obviously.
My question is .. can we use Biztalk for this problem? In other words, can we have all the instances of the application running on different computer “register” with the biztalk and when one application changes data – it will send the message to Biztalk and Biztalk can “notify” all the other machines..How can this be done…can you provide some detail
thanks so much.
Dino
-
Absoultely! as a matter of fact, thats pretty much what BizTalk was designed to do. Now, you can do this is a variety of ways depending on whats on the other end. One way can be to trigger all these events based on files being dropped to certain locations that Biztalk is watching. Another is to use messages, and yet another is to listen to events. Basically, anything you can get data to will work in the adapter stage.
Think of BizTalk as an Exchange server that has been supercharged and has very few limitations. You can then either route the message as is, send it to several recipients, change the data entirely and send it back, even get a message, trigger a workflow, wait for human intervension then resume from there.
The short answer is “yep”, the suggestion is to read up on BizTalk and decide how deep you want to get into it and how thorough you need your solution to be within it.
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.