Executive summary.........................................................2The business value of SOA..............................................3Management guidelines .................................................3SOA requires visibility, trust and control ............................6Understanding the SOA ecosystem...................................7SOA governance with HP solutions ..................................9Repository and registry ...................................................9Governance Interoperability Framework (GIF)....................9Looking beyond governance:

a lifecycle approach to SOA.......................................10HP SOA quality and management solutions ....................10HP SOA management:

obtain operational business value................................11Conclusion...................................................................12

A practical guide to SOA for IT managementWhite paper

Executive summaryAs a strategy for creating a flexible and agile ITinfrastructure, service-oriented architecture (SOA) hasgained considerable momentum in recent years,largely due to the advent of standards-based businessservices that simplify interoperability and governancetechnologies that make SOA scalable and predictable.Organizations without a strategy for SOA risk being out-paced and out-performed by competitors that are betterequipped to serve customers, seize opportunities andrespond to change. Few other innovations in computingoffer the transformative potential of SOA, and Gartnerestimates that by 2007, 80 percent of IT initiatives will beservice oriented. A basic business driver for implementingSOA today is the need for business agility. SOA makesyour IT organization more responsive to changingbusiness demands and more flexible to changingbusiness processes. Reconfiguring loosely coupledbusiness services is simple, fast and low cost.

• Cost savings. Organizations implementing SOA canachieve significant cost reductions by reusing sharablebusiness services, rather than recreating functionalityto address the needs of each application initiative.SOA simplifies and accelerates your applicationdevelopment, which lets you do more with less. Youreduce the cost of implementing changes as well asyour ongoing maintenance costs.

• Maximizing IT investments. SOA doesn’t require youto rip and replace existing IT investments, but it lets youwrap and reuse existing IT investments and make themavailable to a wider audience. SOA encourages reuseand avoids unnecessary duplication and reinvention.

• Aligning IT with business processes. SOAtransforms your IT systems into self-containedservices that accurately reflect your businessprocesses and operational requirements. WithSOA, your IT activities mirror your businessoperations, improving the utility that IT delivers to your business.

This white paper discusses the business value of SOA and introduces a management framework forimplementing SOA and capitalizing on the advantages itpromises. It reviews the critical elements of visibility, trustand control in implementing SOA, provides a contextfor understanding the SOA ecosystem, explores theimportance of governance and reviews the role of HPSOA Systinet software as the basis for implementingand governing SOA.

2

The business value of SOASOA is a design style for maximizing IT interoperabilityand for sharing and reusing business services in adistributed environment. Service orientation isn’t anew approach to software design, but it has becomeincreasingly viable because of the widespread adoptionof web services technology that makes creating an SOApractical and cost effective. SOA offers distinctadvantages over traditional architectures.

SOA makes interoperability an innate characteristic of ITapplications. Applications built using SOA-based servicesbecome shared resources that are completely platformindependent, language independent and very looselycoupled, based on universally accepted industrystandards. You no longer need to invest inordinateamounts of time and resources writing custom adapters to integrate your applications, only to recode them whenchanges are made to support new business processes.With an SOA, all IT systems have interoperableapplications, so integrating them becomes lessproblematic.

SOA makes IT more agile and more responsive tochanging business demands. New business processescan be supported and integrated across organizationaland IT systems on demand, and you can easily composereusable, shared services to respond to new businesschallenges. In addition, because services are representedin high-level business terms, you can think in terms ofyour business functions. With SOA, your IT systemsquickly and accurately adapt to your corporate goalsand processes. SOA makes IT highly tolerant of change,and reconfiguring loosely coupled services becomesa simple and economical process.

• Respond to change: SOA helps you rapidly respondto unpredictable changes within the businessenvironment, such as competitive assaults, mergersand acquisitions, reorganizations and new channelopportunities.

• Differentiate: SOA lets you differentiate your offeringsby developing innovative, value-added services, suchas a customer-facing tools and applications.

• Drive revenue: SOA allows you to drive incrementalrevenue by simplifying the process of selling throughnew channels or enabling single views of data tosupport cross-selling initiatives.

• Mitigate risk: SOA lets you mitigate risks throughcorporate, IT and regulatory compliance byenforcing enterprise-wide policies within youroperating environment.

ManagementguidelinesAs your organization begins planning for SOA, youshould consider the following guidelines:

• Plan for incremental deployment. A completeconversion to SOA principles and practices doesnot happen overnight. You can easily deploy SOAincrementally and still show business value. Forexample, an SOA can show immediate value onprojects with multi-point integration, involvingheterogeneous or legacy applications. Reusing legacycode and integrating diverse platforms is an ongoingchallenge for most enterprises, but that challenge iseasily met using SOA. Define a long-term plan withan overarching vision for SOA, but focus on discreteprojects to build momentum and show business value.

• Focus on interoperability. Innate interoperability is akey benefit of SOA, and it is important that you defineinteroperability standards in advance and govern themas you create and deploy business services. You mustdefine an interoperability architecture and policy tomanage all integration efforts. You must also specifyhow services will be used and what standards mustbe defined and enforced. You should also define areference architecture for migrating point-to-point webservices to reusable business services.

• Focus on business and IT agility. Business and IT agilityshould always be a primary and overarching goal ofyour SOA strategy. IT systems begin to mirror businessprocesses, making it easier to map business changeto system change. SOA technology makes it easier toimplement IT change, because systems are composedof loosely coupled business services. This means thatchanges in services do not interfere with connectionsamong services, and reconfiguring processes isstraightforward. For example, if you change yourbusiness rules for processing payroll, the retirementplan system that depends on the payroll service isunaffected. The business services that compose an SOArepresent a coarse-grained view of IT assets—that is, anSOA defines services around business concepts ratherthan technical details, allowing business analysts toeasily understand and work with business servicesto implement change without turning to IT.

3

• Think in terms of business services. At its core, SOAis about business services, which are the reusablecomponents at the heart of an SOA. Business servicesrepresent a common unit of work—they’re expressedin business terms and must be widely relevant andunderstandable to the business. This defines the level ofgranularity for creating services. Examples of businessservices include: “Get portfolio balance,” “Transferfunds” and “Execute trade.” “Settle books for thequarter” is too coarse to be practical or applicable,and “Encrypt transaction” is too detailed to be relevantin business terms. The right definition of businessservices contributes to the success of an SOA andshouldn’t be overlooked.

• Recognize the cultural implications of SOA. SOAdictates process, and behavioral changes andinitiatives cannot be successful if you ignore essentialhuman factors. SOA introduces two significant culturalimplications: trust and incentives. Potential consumersof services typically develop their own capabilitiesbefore they reuse a service they can’t explicitly trust.That is why the assurance of quality—and the proofof quality—are absolutely essential to the effectivenessof an SOA.

Incentives are another cultural implication of SOA. SOAdemands changes in the behavior of IT professionalswho are used to creating and managing monolithicapplications in highly siloed business settings.Developers need incentives to contribute servicesfor reuse. IT and business line managers need toimplement incentive systems that encourage developersto think beyond their immediate business silo andcontribute to the shared-service environment. Thiscultural change must come from the top, involvingsenior-level sponsorship of SOA, and it needs to bereinforced by processes and incentives that encouragecompliance with an SOA style of development.

• Think beyond web services. Some organizationsconfuse the use of web services with a bona fideSOA initiative. The reality is that web services areonly part of the picture. A complete SOA strategyrequires that you answer the following types ofquestions:

– Are you aware of all of the services that currentlyexist?

– Do potential consumers trust the services theydiscover?

– How can you adequately test and manageservices for performance and quality?

– Do consumers and providers have a way toformalize contracts to bind their relationships?

– Can you monitor and report on service usage,policy compliance and service-level agreements(SLAs)?

– Can you anticipate the expected service demandfor capacity planning?

– How will you handle charge backs to compensateproviders properly?

– Can you perform impact analysis so that servicechanges don’t disrupt your business processes?

• Understand the SOA governance imperative. In atraditional computing model, business functionality isburied in siloed applications, and governance is hard-wired into the applications themselves. SOA introducesa completely new, dynamic and fundamentally differentgovernance model. Business functionality is exposed asstandards-based, shared and reusable services, andgovernance is dictated by the application context,which is in a constant state of change.

4

Managing your SOA isn’t optional—it’s imperative.Without good control and visibility of your services, yourreturn on investment for SOA deployment can be low,and every SOA project out of pilot can be at risk. This isbecause SOA introduces new levels of complexity thatyou must govern so that your SOA doesn’t turn into chaos.

This complexity comes in the form of relationships, bothtechnical and human. Technical relationships involveissues of interoperability; Services must interoperate withthe applications they support and with the other servicesand infrastructure on which they depend. You must defineinteroperability policies and oversee consistentconformance to these policies.

Human relationships are equally important, starting withconsumers and providers. Consumers and providersare both dependent upon one another and operateindependently, based on their own unique view of aservice. Consumers and providers must have completetransparency to avoid conflicts and establish afunctioning relationship, but they also need the flexibilityto work with the same services based on their ownindependent lifecycles. Since the specific needs ofconsumers and providers are rarely in alignment, theyneed a way to communicate and collaborate throughoutthe course of service usage. But trying to manage theserelationships informally would be chaos, particularlybecause a provider typically supports many consumers.

Collaboration must also occur throughout the process ofbusiness service definition, creation and implementation.Business people need to get involved in the definitionof services in order to map them to specific needsand process requirements. Application architects anddevelopers are responsible for developing services.Enterprise architects typically define policies and overseethe implementation and operational aspects of businessservices. These are just a few examples of the manyparticipants involved in managing an SOA. Again, thiscollaboration cannot happen informally for an SOAto function effectively.

SOA governance consists of the corporate, businessand IT processes and rules required to control andguide the business success of an SOA implementation.SOA governance enhances the quality, consistency,predictability, change and interdependencies of services.Its overarching goal is to manage the complexity createdby SOA by seeing that organizations can capitalize onthe powerful promise of SOA without sacrificing control,predictability and efficiency. SOA governance is aboutblending the flexibility of service orientation with thecontrol of traditional IT architectures.

5

Figure 1: Collaboration betweenservice providers and serviceconsumersFor SOA success, you need newstructures and processes forcollaboration between serviceproviders, who create and providethe service, and service consumers,who compose the services intocompleted composite applications.

Service/service Service/application

Provider Consumer

Service/infrastructure

Technical interoperability• Services depend on infrastructure• Applications depend on services• Services depend on services

Consumer/provider collaboration• Across business units• Across organizational functions• Across different lifecycles

Application

Application

SOA requires visibility, trust and controlAn effective SOA is a marketplace of services, bringingtogether providers, who publish services, with consumers,who discover and reuse services to develop newapplications. As with any marketplace, governance isrequired to create an effective, smoothly functioningand effective operation. At its most basic level, SOAgovernance is about visibility, trust and control.

• Visibility. Consumers must be able to find andunderstand services to gain insight into their intendedfunctions, attributes, characteristics and operatingperformance. This insight helps them make betterand more informed decisions. Additionally, other IT stakeholders need to understand a full breadthof information about these services to manage theoverall health of an SOA. These stakeholders mayneed to ask:

• How many and which consumers are using this service?

– What is the impact of a service change onthese consumers?

– To what extent does a service conform to specificIT, business and regulatory policies?

– Where is this service in its lifecycle?

To provide this visibility, you need a single “systemof record” that captures all of the information aboutthe business services at the heart of an SOA. Thisinformation includes service descriptions, policies,technical documents such as WSDLs and schema,contracts and other metadata to help consumersfully understand the intent, operational realities and the trustworthiness of business services.

• Trust. A significant challenge to SOA adoption is thatwhile managing service quality is paramount, simplyhaving quality is not enough. For the first time, qualitymust be proven and demonstrable to consumers togain their trust and create an effective shared-serviceenvironment. Without trustworthy services, consumerstypically recreate rather than reuse, which underminesthe overall purpose of an SOA. Creating a systemof record helps you capture the information neededto create a “trust profile,” which makes the qualityand trustworthiness of a service visible andapparent to consumers.

6

Figure 2: Increase visibility, trust and controlYou need a trusted system of record for service providers and consumers toincrease visibility, trust and control with governance applications thatimprove collaboration among all SOA constituencies.

Culture

Provisioning

Ince

ntiv

es

Providers Consumers

Visibilitytrust

control

Another aspect of trust is the ability to formalizeconsumer and provider relationships with anenforceable agreement that specifies service levelexpectations and any other terms, conditions anddetails that need to be agreed upon as the basis for service consumption. An informal consumer andprovider relationship can easily lead to conflict andmisunderstood needs and expectations, which cancreate inefficiencies and potentially disruptapplications and business processes.

• Control. You need to manage services just as youmanage other high-value IT assets—fromintroduction to final retirement and at every step inbetween. You must manage access to services so thatthey are only visible and accessible to authorizedstakeholders. You also need to enforce specificprocesses for service introduction. You must defineprocesses and identify people for reviewing andauthorizing the introduction and publication of newservices to minimize duplicate, nonconforming orpoorly defined services and to assess overall fitness foruse. Control is also about service change. As servicesevolve, you must be able to anticipate the impact ofchanges so that modifications to a service do notdisrupt other dependent services and applications.

Understanding theSOA ecosystemA practical guide to SOA requires an understandingof the complexities and interrelationships of the SOAecosystem. Recognize that no single vendor can deliveryour “SOA solution.” The reality is that many softwarevendors participate in the SOA ecosystem, and ITmanagers need a framework for analyzing the rolea vendor can play in the creation of an SOA.

Data sources consist of packaged or internally developedlegacy applications. They contain the data and thefunctionality for repackaging and exposing asreusable services.

The Integration layer provides an intermediary to theunderlying data, which needs to be accessed and sharedwithin an SOA. Organizations typically introduce thislayer when they have large-scale requirements and needto maintain consistent performance and response timesor when they need to transform or enhance data. Thislayer typically includes technologies, such as enterpriseapplication integration (EIA), enterprise service bus(ESB) and enterprise information integration (EII).

7

Figure 3: SOA ecosystemThe SOA ecosystem is complex andcan include many vendors’solutions.

Presentation layer

Portals, mobiles, composite, application display

Infrastructure services

Security, identity, application management

Orchestration layer: BPM, workflow, BAM, bus rules

Business logic, sequencing, exception handling, process decomposition

Business logic layer

Discrete business services

Integration layer: EAI, ESB, web services, EIIData integration, mediation service

(transformation, routing, guaranteed messaging)

Governance

SOA modelsPolicy management

TaxonomiesPublishingDiscovery

Contract managementSubscriptionsVersioningReporting

Management/security

AvailabilityMonitoringProvisioning

SLA enforcingSecurity enforcing

AnalyticsAlertingAuditing

Data sources: systems of record, enterprise applications

Legacy ERP CRM Finance

The Business logic layer consists of commercial softwareapplications developed with reusable and self-containedservices that can be combined and composed to meetthe specific needs of your business processes. This layerrepresents the new paradigm for commercial softwaredevelopment and delivery and is often prominent inan enterprise SOA strategy.

The Orchestration layer provides tools for creatingapplications, defining workflows and assemblingbusiness processes. The orchestration layer is the focusof the business process management (BPM), workflow,business activity monitoring (BAM) and business rulesvendors, and it is where IT and technically orientedbusiness analysts assemble SOA-based componentsto build new applications.

The Presentation layer is how services and theapplications they comprise are displayed to endusers. Examples include web portals, compositeapplication frameworks, mobile devices andpersonal digital assistants (PDAs).

Infrastructure services are the tools and technologies that“keep the lights on.” These services include capabilitiesfor user provisioning, providing security and managingidentity, as well as application testing, monitoringand management so that services meet functionality,performance and availability requirements.

Governance includes a trusted and authoritative systemof record for the discovery of services, capabilities formanaging collaboration between technical and businessstakeholders in an SOA, tools for enhancing the qualityand conformance of services, and capabilities forformalizing consumer and provider relationships. SOAgovernance is centered on visibility, trust and control.

Management/security includes web service management(WSM) and XML security vendors. WSM focuses onenforcing policies within an operational environment topermit conforming and reject nonconforming servicebehaviors at run time. XML security encrypts and securesXML-based messages “over the wire” so to secure dataend to end and to preclude packet sniffing.

While governance is critical to the success and viabilityof an SOA initiative, it represents but one important pieceof the puzzle. SOA is as much about people and processas it is about technology. But even in the narrow scope oftechnology, be cautious of vendors who claim to havea “complete solution” for SOA—no single vendorcan deliver on such a lofty claim. SOA is inherentlyheterogeneous, involving both existing “legacy”technology as well as point solutions from a number ofdifferent vendors. You should evaluate interoperabilityand look for deep partner networks when selectingcommercial software vendors.

8

SOA governance withHP solutionsHP has been a leader in SOA for more than five years.HP has earned a distinguished reputation of trust throughaward-winning products and guiding customers of allsizes to design and deploy effective SOA infrastructures.

HP SOA Systinet software is a complete SOAgovernance and lifecycle management platform,providing a trusted system of record and a complete setof capabilities for establishing the visibility, trust andcontrol that are so critical to SOA success. HP SOASystinet provides consistent access, management andgovernance of the reusable business services, associatedartifacts and information that enable SOA.

Repository and registryThe promise of SOA cannot materialize unless you havevisibility, trust and control within you SOA. This meanscreating a foundation for SOA governance that balancesthe flexibility and agility promised by SOA with thecontrol and predictability of traditional IT. HP SOASystinet provides capabilities for:

• Publishing and discovering services so that servicescan be found and reused

• Creating policies and validating conformance so thatservices put into production are of high quality

• Creating consumer and provider contracts to lessenconflict and set appropriate expectations

• Managing the lifecycle of services to control servicesfrom introduction to retirement

• Reporting on various dimensions, including impactanalysis to understand how service changes affectother services and ultimately business processes

Specific HP SOA Systinet capabilities include:

• Standards-based registry. HP SOA Systinet Registrysoftware is a widely adopted business service registry.It provides a simple and standards-based way todiscover and publish reusable business service. It alsointegrates with the HP SOA Systinet repository toprovide a complete “system of record” for all SOA information.

• SOA repository. The SOA repository is the foundationfor the rich governance applications that HP SOASystinet delivers. The repository provides a way tocapture, catalog and discover all of the metadata,artifacts and relationships at the heart of an enterpriseSOA. It also provides capabilities for rich reporting,impact analysis and synchronization with otherrepositories.

• Service catalog. The service catalog simplifies theprocess of publishing and discovering services witha straightforward and intuitive application for providersto publish and consumers to discover business services.

• Policy management. Policy management transformsdesign-time validation of services from a manualeffort to the click of a button. This takes the time andcomplexity out of service validation and improvesthe quality and conformance of reusable services.

• Contract and consumer management. Contract andconsumer management promotes consumer andprovider trust by facilitating SLAs and other termsand conditions that bind service providers and theconsumers who reuse services.

• Lifecycle management. Lifecycle management withconfigurable workflow capabilities provides controlover versioning and state change of business servicesfrom initial introduction to final retirement.

GovernanceInteroperabilityFramework (GIF)Because of the complexity and heterogeneity of an SOA,interoperability is absolutely critical. The GovernanceInteroperability Framework (GIF) defines a set of technicalspecifications and brings together leading SOA vendorsfor seamless interoperability. GIF spans management,security, integration, composite applications and businessintelligence vendors, providing an easier way for todeploy a multi-vendor SOA. In doing so, GIF enablesand simplifies governance, compliance and policy-driven solutions for an enterprise SOA.

Through the GIF specification, software vendors canpublish services and associated policy to a system of record in a standardized way, and have access tometadata about the range of services that make up anSOA. HP SOA Systinet supports GIF and can serve asthe system of record for managing business services.

9

Looking beyondgovernance: a lifecycle approach to SOAWhile governance is the typical starting point forscalable SOA initiatives, many organizations now realizethat they must take a full lifecycle approach to managingtheir SOA implementations. This means that, in additionto having visibility, trust and control, they should test thefunction, performance, interoperability and complianceof services and monitor the behaviors of services withina production environment. In addition to enterprise-classSOA governance offerings, HP also provides a broaderset of SOA capabilities that build upon our strengthand leadership in application testing andmanagement. This helps you make go/no-go-decisionswith confidence, understand the realities of services inan operating environment and answer key questions,such as:

• Do my services meet my enterprise’s functionalrequirements?

• Will my services scale in production?

• How do I manage the complexity of testing dozensor hundreds of services?

• How can I quickly identify and resolve serviceproblems in production?

• What is the overall impact of service changes?

• Will my services meet SLAs?

HP SOA quality and management solutionsIn addition to HP SOA Systinet, HP SOA solutionsinclude the following capabilities.

HP SOA quality management: control the risk of delivering servicesHP is a market leader of SOA application delivery withsolutions and processes that address all aspects of qualityassurance. Quality is the basis for trust and predictabilitywithin an SOA. HP offers integrated Centers ofExcellence with functional verification, performancevalidation and quality management capabilities. Thesecenters help you implement SOA services that are tested,validated and optimized in order to align withfunctionality and performance requirements described bypolicies and contracts. Our complete set of qualityassurance solutions support the specific quality needs ofSOAs.

HP business technology optimization solutions includehigh-performance application delivery software that helpsdrive business outcomes. By increasing the quality andperformance of your services and managing changesthroughout their lifecycles, your IT organization candirectly affect the business value associated with yourcritical services. HP quality management softwareincludes HP Quality Center software, HP PerformanceCenter software, HP Service Test software, the HP ServiceTest Management module, HP QuickTest Professionalsoftware and HP LoadRunner software. This set of qualitymanagement software lets you:

10

• Drive the rapid delivery of services and compositeapplications

• Make better-informed “go-live” decisions

• Reduce the cost and time of deploying new services

• Decrease software defects

• Gain real-time visibility into the health of yourservices and infrastructure

• Make applications ready to deliver their intendedbusiness results

HP offers a comprehensive solution for testing SOA services and interfaces, managing quality andenhancing performance throughout the lifecycle ofservices and composite applications. With HP QualityCenter and HP Performance Center, your IT staff canintegrate testing with your SOA ecosystem to test servicesthroughout their lifecycle and to enable your compositeapplications to use shared services continuously.

HP SOA management:obtain operationalbusiness valueOur approach to application management for SOAenvironments deals first and foremost with helpingenterprises achieve the expected value from SOA-basedapplications during the normal day-to-day operations ofthe business. HP Business Availability Center softwareincludes functionality that helps you manage andoptimize SOA environments so that associated businessservices deliver as much value as possible.

HP Business Availability Center delivers value in SOAenvironments in three key areas:

• Service level management: Enables business and ITto agree on, manage and provide visibility into howan SOA is delivering the actual business service inreal time and over time

11

Figure 4: Governance Interoperability FrameworkThe Governance Interoperability Framework definestechnical specifications for seamless interoperabilityamong heterogeneous vendor SOA solutions.

Gov

ernance Interpretability Framew

ork

Service catalogAn intuitive end-user application for publishing, discovering and managing services

Policy managementAutomates the process of policy conformance checking before services are published for reuse

Lifecycle managementManages the stage-change of a service as it evolves across its lifecycle

Consumer managementAllows consumers and providers to formalize their relationship by negotiating a contract

SOArepository

and registry

Servicecatalog

Lifecyclemanagement

Consumermanagement

Policymanagement

• Problem resolution: Facilitates fast problem detectionand notification so that despite SOA complexity, youcan quickly diagnose performance issues quickly andreduce mean time to repair (MTTR)

• Change impact: Decreases the risk of frequent changesin SOA environments by quickly detecting them andestablishing their impact

HP Business Availability Center consists of multipleapplications that work together to deliver SOAmanagement including a real-time, correlatedcentralized dashboard. HP Business AvailabilityCenter software includes:

• HP End User Management software, which providesreal and synthetic monitoring of end-to-end webservice transactions

• HP Service Level Management software, which enablessetting, measuring and reporting on performancecriteria as it relates to your business

• HP System Availability software, which deliversagentless monitoring of the underlying SOAinfrastructure, including operating systems,hardware, applications, application componentsand networking, as well as third-party data

• HP Application Mapping software, whichautomatically and dynamically discovers and mapsSOA environments and provides the foundation foraddressing change

• HP Diagnostics software, which supplies critical, low-level problem analysis and troubleshooting for J2EEand .Net environments

In addition, HP SOA Manager software helps youenforce compliance for your services in production.

HP SOA Manager integrates with HP SOA Systinet andprovides policy enforcement for policies declared in theSystem of Record feature of HP SOA Systinet. The WSMBroker feature of HP SOA Manager offers a sophisticatedPolicy Enforcement Point (PEP). Brokered services usethe WSM Broker’s handlers, which mediate thecommunication between a client and a web service.Common handlers include:

• Monitoring handlers

• Logging handler

• Auditing handler

• Schema validation handler

• Business content alerting handler

• Security handlers

ConclusionSOA can help you be more flexible in responding toevolving business demands. SOA presents a tremendousopportunity to help you respond to changing businessconditions, differentiate your offerings, increase yourrevenue and mitigate your risks by providing corporate,IT and regulatory compliance through enforcing policiesacross the enterprise. But the reality is that SOA itself canintroduce new risks that must be managed by startingwith a foundation for governance. This can help youcapitalize on the promise of SOA without creating anuncontrolled and uncontrollable IT environment.

IT managers are increasingly leading SOA initiatives.Governance is critical to managing and scaling SOAenvironments over time so that you can have afunctioning marketplace of services for SOA consumersand providers. SOA can help you transform yourbusiness, but successful deployment of SOA requiresgovernance, based on visibility, trust and control.Managing the complexities of an SOA ecosystem is a major challenge. HP offers comprehensive SOAgovernance, quality and management software thatprovides a trusted system of record and a complete setof capabilities for establishing the visibility, trust andcontrol essential for a successful SOA.

To learn more, visit www.hp.com/go/soa© Copyright 2007 Hewlett-Packard Development Company, L.P. The information contained herein is subject tochange without notice. The only warranties for HP products and services are set forth in the express warrantystatements accompanying such products and services. Nothing herein should be construed as constituting anadditional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

4AA1-2327ENW, May 2007