Geek Answers Handbook

.NET integration infrastructure as camel integration / spring

I am currently looking for a good infrastructure to integrate several systems with different communication methods, for example

  • FTP
  • post office
  • Queue
  • Web service

in a .NET application. For Java, it seems that many options are available, but I could not find anything like it for the .NET platform.

+4
source share
4 answers

Workflow basics are more suitable for ... well ... workflows that represent business logic. You seem more interested in integrating existing services. In this case, I will focus more on the Windows Communication Foundation. Which were presented together with the (original) workflow. Therefore, WCF is part of .NET versions 3 and higher. WCF will support Webservices, Message Queuing, and FTP out of the box. For email, you probably need some sort of custom channel. However, it is very likely that someone else has already written for you.

According to Microsoft :

"The Windows Communication Foundation (WCF) is the foundation for building service-oriented applications. Using WCF, you can send data as asynchronous messages from one service endpoint to another. A service endpoint can be part of an ongoing service, IIS, or it can be service hosted by the application. An endpoint can be a client of a service that requests data from a service endpoint. Messages can be as simple as a single character or word conveyed as XML or as complex as a binary stream yes data. "

This MSDN page contains resources to help developers speed up development with the Windows Communication Foundation (WCF). Keep in mind that all this applies only to the level of communication. You will have to write the glue code yourself.


If you really want a more “framework” solution, I agree with Tommy Groves. "Service Bus" is a search keyword. In fact, Stackoverflow already provides a lot of hints about which service buses are suitable, which implementations exist, experience with them, and so on. Especially this question on .NET serving buses looks like a promising start.

Greetings

Dave

+1
source
  • For an FTP client, you can use a framework such as FTPclient , or FTP Client Lib for .NET, or can be found on Google to suit your needs.
  • Mail Clien: - What do you want to achieve with the framework and can find the best structure.
  • You can use the WCF environment to create a web service and queue (MSMSQ).

Hope the explanation helps

0
source

I suggest you take a look at the Windows Workflow Foundation (WF) . This is part of the .NET Framework.

It uses the concept of Activity. Activity is a general concept and is also well suited for connectors for other systems. Some pre-defined events are provided ( . NET Framework 4 Built-in Activity Library )

Others can be written in .NET ( Tutorial: Create User-Defined WF Activity ), you can also find many examples of implementations on the Internet ( SendEmail Workflow for Workflow , FTP Activity for Windows Workflow Foundation , MSMQ Workflow Actions , Building and Testing the Web WCF services using Workflow Foundation 4.0 ), or you can also buy specific actions already built by third parties ( Xceed Activities , / n "Working with Workflows , etc.)

0
source

If you want something more entrepreneurial: look at Biztalk, it comes with a bunch of adapters and tools, but it's not free.

0
source

More articles:


All Articles