Contents tagged with SO-Aware

  • Extending the SO-Aware repository with custom metadata

    One of the main features that SO-Aware provides is the central repository for storing service artifacts (WSLD, schemas, bindings) and configuration that any organization generates. This central repository is completely exposed as an OData service that third party applications and tools can easily consume using Http.

    Read more...

  • Monitoring your services with SO-Aware

    One of the features that you get out of the box with SO-Aware is the ability of monitoring your services. You can either monitoring the traffic for your REST or SOAP services, and see the details of all the incoming or outgoing messages, or any fault that got generated during the execution. In addition, that data is used to compute some metrics and provide several reports about the service usage.

    Read more...

  • SO-Aware integration with Visual Studio 2008

    I am happy to announce today the support in Visual Studio 2008 for adding new service references from the SO-Aware service repository. We have created a simple plugin that you can register in Visual Studio to support this new functionality.

    Read more...

  • SWUtil - A new tool for generating service proxies from the SO-Aware repository.

    As we announced last week, we are shipping a new Visual Studio plugin for generating service proxies as part of the SO-Aware SDK. The functionality is equivalent to what you find today in the “Add Service Reference” command, but the results are much better as you get a proxy that does not require any WCF configuration, and also knows how to resolve bindings and behaviors from the repository.

    Read more...

  • Managing the SO-Aware Repository with PowerShell

    As Jesus mentioned in this post, SO-Aware provides three interfaces for managing the service repository. An OData API in case you want to integrate third applications with the repository. OData is a pure http API that can be easily consumed in any platform using a simple http client library. The management portal, which is an ASP.NET MVC user interface layered on top of the OData API and probably the one most people will use. And finally, a PowerShell provider that also mounts on top of the OData API to allow administrators to automate management tasks over the repository with scripting. 

    The SO-Aware PowerShell provider, in that sense offers around 40 commands that enables simple management scenarios like registering bindings or services or more complex scenarios that involves testing services or sending alerts when a service is not properly working.  

    This provider can be registered as an snapin in an existing script using the following command,

    $snapin = get-pssnapin  | select-string "SOAwareSnapIn"
    if ($snapin -eq $null)
    {
    Add-PSSnapin "SOAwareSnapIn"
    }

    Once you have registered the snapin, you can start using most of the commands for managing the repository.

    The first and more important command is “Set-SWEndpoint”, which allows you to connect to an existing SO-Aware instance. This command receives the OData service location as first argument, and it looks as follow,

    Set-SWEndpoint -uri http://localhost/SOAware/ServiceRepository.svc

     

    As next step, you can start managing or querying data from the repository using the rest of the commands. For instance, the following example registers a new binding in the repository only if it was not created already

    function RegisterBinding([string]$name,[string]$type,[string]$xml)
    {
    $binding = GetBinding($name);
    if(!$binding)
    {
    Add-SWBinding -Name $name -BindingType $type -Configuration $xml
    }
    }


    function GetBinding([string]$name)
    {
    $bindings = Get-SWBindings
    foreach($binding in $bindings)
    {
    if($binding.Name -eq $name)
    {
    return $binding
    }
    }
    }


    RegisterBinding "stsBinding" "ws2007HttpBinding" "<binding>
    <security mode='Message'>
    <message clientCredentialType='UserName' establishSecurityContext='false' negotiateServiceCredential='false'/>
    </security>
    </binding>"
    ;

    As you can see, this provider brings a powerful toy that administrators in any organization can use to manage services or governance aspects by leveraging their scripting knowledge.

    Read more...

  • Visualizing Service Dependencies in SO-Aware

    A common requirement that we received from some customers while we were in the early design stages of SO-Aware was the ability of tracking static dependencies between services. For instance, Service A calls Service B and Service B calls Service X. This feature is not only useful for documentation but also for helping administrators to determine which services are going to affected with a change in one of the existing service. (In that example, a change in the service X would affect Service A and B).

    Read more...