After a huge growth of our company Tellago in the last couple of years, we are proud to announce the launch of our new software development division, Tellago Studios. Basically this division is going to put everything we learn as enterprise consultants into our own software developments. And this begins today, with our SO-Aware product.
SO-Aware is a Web Services repository that enables the cataloging, management, monitoring and testing of Web Services. Contrasted against the complexity of traditional UDDI-centric SOA governance products, SO-Aware uses a simple and unique design based on the principles of REST and OData which enables the manipulation of service artifacts using standard http verbs like GETs or POSTs. Whether SO-Aware can manage Web Services developed on any technology stack, it excels in the management of Windows Communication Foundation (WCF) solution enabling capabilities that are very needed in enterprise SOA-WCF solutions. Specifically, the first version of SO-Aware focuses on the following aspects:
- Service cataloging: SO-Aware provides the infrastructure to organize different versions of web services using a simple category-based taxonomy. SO-Aware extends these capabilities beyond traditional SOAP services by supporting REST and OData services.
- Centralized configuration management: SO-Aware provides a creative model for the centralization and configuration of WCF services and endpoints that removes the need for maintaining large and complex configuration files. Additionally, SO-Aware facilitates the modeling and creating of configuration artifacts such as bindings or behaviors in a way that is accessible to non-WCF experts.
- Testing: The first release of SO-Aware includes a sophisticated testing subsystem that enables the testing of WCF services. The tests created using SO-Aware can either be executed on-demand using the management portal or periodically using the test scheduling system. Additionally, SO-Aware tracks the execution of tests and enables specific analytics that help testers and members of IT operations teams accurately monitor the behavior of the tests.
- REST-OData API: SO-Aware is 100% OData centric. In that sense, every capability of SO-Aware from service cataloging to testing is accessible through simple HTTP interfaces using OData as the encoding mechanism.
- Service activity monitoring: SO-Aware enables a simple model for tracking the message flow for the various services in your SOA. Using this information, SO-Aware provides specific analytics that help to accurately describe the runtime behavior of services.
- Dependency modeling: Services that depend on other services are very common in SOA environments. SO-Aware enables developers and architects to model the dependencies between services using a simple visual interface included in the management portal.
- Management Portal: SO-Aware is 100% OData centric. In that sense, every capability of SO-Aware from service cataloging to testing is accessible through simple HTTP interfaces using OData as the encoding mechanism.
- PowerShell provider: SO-Aware can be completely managed using a scripting environment based on Windows PowerShell. The current version of SO-Aware includes a PowerShell provider that contains a large number of commands that abstract the different SO-Aware capabilities.
Feel free to download our Express Edition of SO-Aware at the SO-Aware site: http://www.tellagostudios.com/products/so-aware™
At Tellago have opened a new codeplex workspace, the Tellago DevLabs.
We’ll be posting there all the open source projects we work on, we’ve already posted a second version of the Biztalk Data Services project, a RESTful API to manage and operate MS Biztalk Server 2009.
A couple of related posts by Tellago’s Chief Architect, Jesus Rodriguez:
Last month I finally got graduated in Information Systems Engineering at Universidad Tecnológica Nacional FRBA!
I’m now thinking which post-graduate course to take… so I’m accepting suggestions!
I’m thinking in getting into a Data Mining & Market Research master, but I’m still not decided.
Shub ratri! (as my friend Vishal would say)
Leandro.
I’m working on developing some WCF-Custom adapters for Biztalk 2009, so I needed to add some binding configuration to machine.config.
If you are trying to modify the computer WCF Configuration with the Service Configuration Editor to add a binding extension, behavior, binding element extension, etc., and you are working in a 64 bit environment, this error may occur:
An extension of name ‘persistenceProvider’ already appears in extension collection. Extension names must be unique. (C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\CONFIG\machine.config (line 224)
If you open the configuration file (C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\CONFIG\machine.config), you’ll probably find that it’s not repeated in that file. But it actually appears in another machine.config file.
Read more…
First, this release got delayed about 3 years!. But, it still works fine and I’ve used it in many Biztalk Project over the last years, so I think it may be of use for every other BTS developer out there.
The idea behind this project is to be able to build custom Biztalk Functoids through a wizard. When this was built, there was not much information on the web about developing custom functoids, so it was a little hard to work on it. It’s based on Boudewijn van der Zwan and Scott Woodgate’s Biztalk Adapter Wizard. I’ve also based this development in Martijn Hoogendoorn’s Biztalk Pipeline Component Wizard. These are the original releases for this components: Adapter Wizard, Pipeline Wizard.
Basically a custom functoid is very similar to a Scripting Functoid with the same code copied once and again. The idea of developing a custom functoid instead of a Scripting Functoid is to avoid code repetition and to be able to modify it in every map that uses it simultaneously. This concept is known as DRY (Don’t repeat yourself).
I’ve built an original version for 2004 for an enormous project which required around 50 custom functoids to be built, of course building them by hand would be very time consuming. Adrian Lopez helped me adapt this version to Biztalk Server 2006, special thanks to him for the help!.
I’m posting both versions here, for Biztalk 2004 (and Visual Studio .NET 2003) and Biztalk 2006 (and Visual Studio .NET 2005).
Installation and usage is quite simple but I’ll show the usage step by step in a simple “Hello world” functoid sample.
Read more…
I’ve been working on how to recycle the current application pool for my ASP .NET application.
There are 3 steps for doing this:
- Verify if application is running on IIS that supports application pools (if not, there’s nothing to recycle).
- Get application pool name (obtained from the DirectoryServices entry corresponding to our virtual directory).
- Invoke Recycle method in the DirectoryServices entry corresponding to the application pool.
Read more…
I’m working on an architecture project now, and I needed to create an HttpModule which would measure the request time for pages.
So I needed to save information (the time and some other data) in the Begin_Request event and then read it in the End_Request event. I could have used Request.Context, but part of the idea of the project is this information in the current thread because it can be used both in Winforms and in Webforms.
This information is saved in the current thread using a class that implements ILogicalThreadAffinative. When I saved my information in the current thread (using CallContext.SetData()), suddenly an exception (not debuggeable) came up, which said:
System.Runtime.Serialization.SerializationException: Type is not resolved for member 'xxx'.
at Microsoft.VisualStudio.WebHost.Server.GetProcessToken()
at Microsoft.VisualStudio.WebHost.Host.GetProcessToken()
at Microsoft.VisualStudio.WebHost.Request.GetUserToken()
at Microsoft.VisualStudio.WebHost.Request.GetServerVariable(String name)
at System.Web.Security.WindowsAuthenticationModule.OnEnter(Object source, EventArgs eventArgs)
at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
Read more…
I was creating a performance counter collection to register the processing time for ASP.NET requests, and I decided the best way to name instances was to use Request.Url.Authority + Request.Url.PathAndQuery. This counters would allow me to check average response time, total requests and requests per second, for each Request.Url.Authority + Request.Url.PathAndQuery.
I built the counters and I decided to create a _total instance too, to sum up all the requests being made to the server.
Rarely, the _total instance worked like a charm when looking at it in PerfMon, but the other instances (for example, localhost/Test.aspx?query=x) didn’t show a value, they all showed “—” in the report view of PerfMon. I had no idea what the problem was, but I saw that the failing counters showed up in the counters list with localhost in the Parent column and Test.aspx?query=x in the Instance column.
Read more…
I’ve searched over the internet for this and couldn’t find anything.
A method I’m working on should have a different behavior when called in a Web Application (Webforms) and a Windows Application (Winforms).
Read more…
Hello, let me introduce myself.
I’m Leandro Díaz Guerra, from Buenos Aires, Argentina, I’m almost 23 years old, I’m a developer, I’ve been working with .NET Framework since 2003.
I’m studying Information Systems Engineering in the Universidad Tecnológica Nacional, I should be finishing my current studies in about 2 years.
This will be mainly a development blog, but probably some personal stuff will get online too!
Recent Comments