Friday, December 06, 2013

Sentinet – Service Virtualization Part 1

A team of Microsoft consultants developed Managed Services Engine(MSE) as an open source project a few years ago. End of December 2009 it was the final CTP release. MSE was meant to facilitate service virtualization to support versioning, abstraction, management, routing, and run-time policy enforcement for Services. It used a service repository to provide easier and faster deployment of services, change management, and reuse.

MSE was a promising product, yet it has never been released as a complete, mature product and ultimately was discontinued. However there is a product called Sentinet from Nevatech, which implements all of theMSE concept (and many more) in its product. Sentinet services virtualization platform is built on the latest .NET Framework and related technologies like WCF and WIF. The repository supports MS SQL Server. It has matured over the years and currently is in version 3.4. Basically you can view Sentinet as a replacement of the MSE, and even as an evolution of MSE into advanced and modern SOA and APIs Management Platform.

In this and upcoming posts I will discuss the product installation & configuration (deployment), user experience, management, some practical use cases and the partner ecosystem. The installation and configuration i.e. the deployment will be discussed here.

A fully functional evaluation copy of Sentinet can be downloaded from their site. Like any product the installation depends on a couple of prerequisites. For Sentinet this means a Windows Server OS (2008/2012), or client like Windows 7 or 8, a .NET runtime, SQL Server and a few OS specific components like IIS and WAS. The prerequisites are outlined in the installation documentation that is provided with the product download.

Depending on the OS architecture you install the 32- or 64 bit msi. The installation depends on your deployment scenario. For a development and/or test environment you can do a single computer deployment. In that case the Sentinet Node(s), Sentinet Repository Web Services Application and its Repository database are all deployed on individual computer system.

The single machine deployment will be used for this and all the upcoming posts. For a high available production environment the nodes and repositories are distributed over multiple machines. The installation guide will provide guidance regarding the deployment you will follow.

Configuration of Sentinet means configuring the repository using the repository wizard: database, application, certificate, reporting, mail server and administrator account(s), and configuring the nodes.



The Sentinet node(s) are configured through IIS.



The installation guide will provide guidance for configuration and is concise and thorough. So to conclude with installation guide in hand the deployment of Sentinet can’t go wrong!

In next (second) post on Sentinet – Service Virtualization I will discuss the user experience and the management of the repositories.

Cheers,

Steef-Jan

3 comments:

mbrimble said...

Hi Steef-Jan
really looking forward to you next post about Sentinet. We used SOAware on one of our customner sites to do the same thing but got badly burnt. SOAware was a good product but Tellago just disappeared without trace. I have been following Sentinet for some time and are realy interested to know what you think of the product. What is the company behind Sentinet?
Regards Mark

Steef-Jan Wiggers said...

Well I will follow up on this post with a few others discussing my exploration of Sentinet. The company behind it is Nevatech and I very confident this company will be around for a long time!

Andrew said...

Hello Mark,
Please send us email at info@nevatech.com and we will be happy to tell you all about Nevatech and its product. We are aware of SOAware situation. It was built using the concept of agents embedded into WCF service deployment effectively being a tool that remotely configures WCF bindings. Sentinet is built on top of services virtualization concept (which is intermediary or broker agents). Service Virtualization is much more powerful and efficient approach that does tightly couple your services deployment with vendor product and provides a lot of diverse management capabilities.
Regards,
Andrew