Monday, January 10, 2011

Introducing CloudGate API Management

Boulder, CO (January 10th 2011) – Managed Methods Inc., the leading provider of cost effective SOA security and governance products, today announced availability CloudGate, a hosted cloud services management solution. CloudGate delivers security, monitoring, provisioning and goovernance of APIs and services deployed in the public and private cloud infrastructure.

Please read the rest of the post here


Thursday, June 10, 2010

JaxView Internal Secure Token Service

Here is a demo of JaxView and its integration with its internal secure token service. This will allow security federation functionality for SOA and Cloud based services for single sign on functionality. Enjoy!!

JaxView STS Demo


Thursday, January 28, 2010

JaxView WebCast

We recently did a webcast that includes a demonstration of JaxView. You can download the recording here


Tuesday, July 28, 2009

SOA vs Cloud Management

At the SOA world conference a colleague asked me a simple question. What is the difference between SOA and Cloud management?

Its an intersting question. After thinking about it a bit I wasn't able to find much difference. SOA is an architecture that allows you to create a set of services that can be used in many differenct business processes. Basically loosley coupled and built for reuse. Cloud is a set of API's that for the most part perform the same functionality. Therefore, management of them is also very similar.

You need to understand the same basic things

1. Securing the cloud services and API's
2. Measuring performance and availability of these API's and services
3. Measuring usage and SLA's for the cloud
4. Be able to trouble shoot when something goes wrong with the consumer accessing those services.

These are the same management issues that we face in the SOA world. So if you're looking to manage your cloud don't look further than any SOA management tools out there.


Friday, April 24, 2009

Visibility into SOA platforms

I just read one of our competitors has finally added support to provide visibility for IBM DataPower. How? Well they finally wrote an agent for the IBM appliance. An intrusive agent is how they mange to provide visibility into DataPower mediated services.

Well JaxView has been providing visibility into DataPower or any other security or xml appliance for the last few years. How? We don't use agents. Our agentless deployment looks at the network traffic to provide visibility metrics and is independent of protocol or platforms. It supports protocols such as JMS, RMI, HTTP, REST, SSL, JOLT, WTC, JDBC and any other TCP protocol used by services.

And BTW JaxView is about a tenth of the cost of the so called leaders in the Runtime Governance market. You can download JaxView and try it for yourself here.


Tuesday, October 14, 2008

What is SOA Management?

As we sift through the hype of SOA this question comes to mind. How do I effectively manage my SOA. I would have to say the most effective way to manage an SOA infrastructure is to manage it without having to disrupt the SOA.

There are more than a few SOA management vendors out there but for the most part deployment of a SOA management solution is both cumbersome and expensive. The cost of this deployment is more than the cost of the product license. Some of these products are so complicated that there is a need for a resource just to manage the SOA management product. That is a ridiculous notion in my opinion.

Most of these products require an agent to be installed on all the application servers or gateways to be able to provide visibility. Again that's a hidden cost of these products that usually is overseen. Managing the agents and deploying the agents is both time consuming, disruptive and intrusive.

With these agents installed you could then get visibility into different protocols such SOAP, REST, JMS, JDBC, RMI etc. But the over head the agent adds to the server its installed on and the time to configure all the agents etc is too much for many companies that they just go about their SOA without a management tool.

A better way to go about SOA management is to manage the SOA environment without the use of any agents by monitoring at the network layer instead of the server. Many network monitoring tools use this architecture to monitor tcp/udp packets. Why not use the same mechanism to monitor other protocols that are used within the SOA. Well that is exactly how the agentless deployment from JaxView monitors the SOA.

Don't get me wrong there are cases where you need to have an agent or there is a need for a proxy for other enforcement of policies such as authentication and authorization but in general an agentless approach has much less overhead than any other approach. Here are some reasones why agentless approach is more efficient.

  • Platform Independent - Obviously since nothing is installed on the server there is no dependance on what platform the server is installed on
  • No change to Provider or Consumer - Again since this is managing and providing SOA visibility by monitoring out of band traffic there is no change that occurs to either the consumer or the provider. You can actually move intor production within minutues instead of days or weeks
  • No Load - No Latancy - Since the monitoring is done on the network and only out of band traffic this adds virtualy zero latency or load to the system as a whole
  • All Protocols - By dissecting all tcp protocols this deployment can provide visiblity into SOAP, REST, JMS, JDBC, RMI etc.
  • Service Discovery - This is the best way to autodiscover rogue services in the SOA environment. If a service is being published and someone is trying to access it then this will discover it. In agent based solution they will only be discovered if there is an agent on the server the service resides on.

You can read more about this deployment at one of our customer sites in the case study here.


Tuesday, July 29, 2008

JaxView Case Study In Agentless Visibility

We just released a case study that talks in more detail about the advantages of managing the service environment without the use of agents or proxies. You can download the pdf here