Introducing TeleSharp

Hello

Last week, Tellago Studios launched our latest product: TeleSharp.

TeleSharp is an application metadata repository that enables true agility in enterprise .NET applications.

TeleSharp provides:

• Application Asset Repository:  Architects and developers can keep an up-to-date data catalog of the different .NET assets used by their enterprise .NET applications. Using this feature, an architect can effectively catalog the Web Services, Databases, Windows Services and other .NET components used by specific applications. 
• Centralized Configuration Management:Configuration management is by far the biggest challenge of .NET enterprise applications. TeleSharp addresses this challenge by providing a centralized configuration repository for your .NET applications. Using this repository, you can keep an organized catalog of the different configuration files used by your .NET applications.
• Configuration File Authoring: TeleSharp provides a drag and drop editor to model your configuration files by reusing existing configuration sections or creating new ones.
• .NET Configuration File Versioning: TeleSharp keeps track of different versions of configuration sections which allow IT professionals to rollback specific changes as well as track the history of a specific configuration file.
• .NET Configuration File Security:  TeleSharp brings security to a first class citizen of your .NET configuration management experience by enabling the ability to sign and encrypt specific sections of a configuration file
• .NET Configuration File Publishing:  TeleSharp provides a publishing system that allows IT professional to publish new or updated configuration files to a large number of servers simultaneously.
• Centralized Logging and Error Handling: TeleSharp includes a high performance centralized repository to store the logging and exception information of your .NET applications.
• Log & Error Visualization:  TeleSharp provides various intuitive and yet sophisticated mechanisms to visualize the logging and exception information of your applications. For instance, you can visualize your log information using tables, charts and even a pivot view that allows you to quickly find information in your application logs.
• Native Logging Framework: TeleSharp includes a simple and highly performant logging framework that allows developers to instrument their applications from a central place. TeleSharp also integrates with popular logging technologies such as the Microsoft Enterprise Library or Log4Net.
• Visual Studio Integration:  TeleSharp integrates natively with Visual Studio enabling developers to leverage the centralized configuration and application metadata management capabilities during their development experience.
• Assembly Visualization:  TeleSharp allows you to visualize your deployed .NET assemblies making it easy to detect and track changes that could impact your applications.

for more details, please see here.

good luck

Uri

Read Full Post »

Tellago Technology Updates webinar series

Hello

We are living in very exciting times for the software industry as we are witnessing revolutions in areas such as cloud computing, mobility, NOSQL databases among others that are changing the way we think and implement applications.

Over the last two years, Tellago has developed some internal programs that allow us to keep up to date with the most relevant technologies across a variety of spaces such as enterprise software, open source, cloud computing, mobility and other technology areas that are changing the enterprise software ecosystem. Those programs have allowed us to adopt new technologies really efficiently in our daily work with customers.

Today, we are really pleased to announce the Tellago Technology Updates series. This program is a periodic series of webinar that will explore in detail debate some of the emerging technologies in the software industry as well as some of our implementation experiences. These Technology Updates are targeted to both IT executives trying to adopt these new technologies as well as developers and architects trying to implement them.

The first 2 webinars will be for “NOSQL DATABASES FOR THE .NET DEVELOPER” and “DEVELOPING .NET APPLICATIONS FOR IPHONE AND ANDROID”

You can follow the Technology Updates series at http://tellago.com/what_we_says/tellago-technology-updates

Good Luck

Uri

Read Full Post »

Submitting messages to BizTalk using c# code

 Hello

Ever needed to send a message to BizTalk using c# native code?

if your answer is yes, you are reading the right post.

I will demonstrate 2 ways of submitting a message to BizTalk, one using a netPipe receive location and the other is using the ESB.OnRamp.Itinerary.WCF receive location. (Vishal Mody has a very good post on the netPipe bindings at his blog)

as the code below shows, it is all about the bindings…

The code

• Add reference to the following assemblies:
  • System.ServiceModel
  • System.Runtime.Serialization
• For both scenarios (netPipe and ESB on ramp) we create the interface:

//Using statements

using System.ServiceModel;
using System.ServiceModel.Channels;
using System.Xml;
using System.IO;

[ServiceContract()]
        private interface IBizTalkSubmission
        {
            [OperationContract(Action="*", ReplyAction="*")]
            void Submit(System.ServiceModel.Channels.Message msg);
        }

• NetPipe receive location

public void SubmitDocument(string Xml)
        {

            //Create the Message
            System.ServiceModel.Channels.Message msg = System.ServiceModel.Channels.Message.CreateMessage(MessageVersion.Default, “*”, XmlTextReader.Create(new StringReader(Xml)));

            //Set required properties
            string uriLocationEsbOnRamp = “net.pipe://BizTalk/someName”;
            NetNamedPipeBinding b = new NetNamedPipeBinding();
            //Handle security if needed
            b.Security.Mode = NetNamedPipeSecurityMode.None;

            EndpointAddress epa = new EndpointAddress(uriLocationEsbOnRamp);
            IBizTalkSubmission proxy = ChannelFactory.CreateChannel(b, epa);
            //submit the message
            proxy.Submit(msg);

        }

• ESB.OnRamp.Itinerary.WCF receive location

 public void SubmitDocumentUsingESB(string Xml)
        {
            Message msg = System.ServiceModel.Channels.Message.CreateMessage(MessageVersion.Default, “*”,
                                                                             XmlTextReader.Create(new StringReader(Xml)));

            string uriLocationEsbOnRamp = “http://localhost/ESB.ItineraryServices.WCF/ProcessItinerary.svc“;

            WSHttpBinding b = new WSHttpBinding();
            EndpointAddress epa = new EndpointAddress(uriLocationEsbOnRamp);
            IBizTalkSubmission proxy = ChannelFactory<IBizTalkSubmission>.CreateChannel(b, epa);

            proxy.Submit(msg);

        }

BTS admin console settings

 NetPipe receive location

make sure that the URI you have in the code ( string uriLocationEsbOnRamp = “net.pipe://BizTalk/someName” in our example) is the same in the URI section for  the transport properties.(see image below)

ESB.OnRamp.Itinerary.WCF receive location

 No need to modify any settings.

if you get an error regarding the body of the incoming message, look at the “Messages” tab for this receive location. in this example the “Body” element was in the “soap:Body” element so the settings is as shown below.

 

Read Full Post »