Solutions

• Overview
• Design-Time Governance
• Automating SOA COE
• Automating Mainframe Governance
• Industry Frameworks
• Registries and Repositories
• Solutions by Platform
• IBM
• Oracle
• BEA
• HP
• Solutions by Role

Design-Time Governance

Design-time governance is focused on the application of policies for governing the design, development and deployment of services and supporting artifacts. It is of primary concern to business analysts, architects, project teams and developers.

Your First Priority

Before you invest in registries/repositories, ESBs or run-time management systems, make sure you are effectively governing the services being built.  The best SOA infrastructure in the market will not overcome poorly designed and developed services. 

Automation is Required

As your organization expands and matures SOA beyond pilot projects, you need a more
automated way to define and enforce SOA governance. Simple mistakes that are overlooked today will come back to haunt your SOA implementation for years to come. Poorly constructed services will not deliver the reusability and business agility that you envisioned.

The WebLayers Center family of products provides a policy-based approach to automate what has traditionally been a manual, labor intensive process of defining and enforcing governance.

Key Considerations for Design-Time Governance

• Start by defining policies -  WebLayers automates policy definition, association and management.
• Leverage industry best practices – use WebLayers Policy Libraries derived from our experience working with Fortune 500 companies on their SOA implementation projects as well as industry consortia recommendations and standards defined by the W3C and WS-I.
• Enforce policies early and often – the earlier you catch issues in the lifecycle, the more time and money you’ll save. WebLayers can govern artifacts from design specifications to source code to service artifacts.   
• Start small and scale up over time - start governing one project and one part of the infrastructure (like a source control system or registry/repository) and expand over time.
• Establish a baseline for existing services - run them against the WebLayers Policy Libraries to get a baseline compliance level (or scorecard) which details the quality of existing assets and highlights of the areas that need review.
• Certify and score your services - these quality scores are added to the service metadata in your registry/repository and provide better decision making to your run-time systems.
• Visibility to effectively measure your efforts - WebLayers provides the hard evidence about a project, service, artifact, project team or individual.  All governance activities and enforcement data are made available through a COE dashboard to provide enterprise-wide visibility on your SOA initiative.

WebLayers Addresses Critical SOA Governance Concerns

• How can we deliver more services to the business more quickly?

• How can we identify best practices and patterns for better services? How can best practices be enforced? Which services already follow those best practices?

• How can we increase reuse so that costs and the time required to get applications running can be reduced?

• How can we get a handle on the quality of services being deployed and which services are easy to reuse? And how can we identify and improve those hard-to-integrate services?

• How can we ensure that good services are not changed to deviate from these best practices?

• How to I get my project teams, most of which have little expertise in SOA, up to speed quickly?

• How can I overcome the internal barriers to implementing governance?