Software AG CentraSite Community

Written by Tony Baer, Associate Analyst, ZapThink.

Governance is drawing significant attention from the boardroom down as a result of heightened regulation, increased competition, and constant change in the marketplace. There are two faces to SOA governance. On one hand, SOA governance simply means governing a SOA implementation initiative—for example, communicating corporate policies to developers implementing Services, and giving them the tools they need to follow those policies as they assemble the various elements of the SOA implementation. On the other hand, there’s a broader, more strategic definition of SOA governance: IT governance in the context of SOA.

Software AG takes a big picture view to SOA governance, based on the premise that SOA governance extends well beyond the governing of Web Services. It believes that the extensible nature of SOA requires a similarly extensible strategy to governance. Software AG has established the CentraSite Community as its strategy for providing a SOA governance solution that customers can adapt to their unique business and technology needs. Organizationally, the CentraSite Community promotes shared wisdom through its collaborative online presence. Architecturally, Software AG CentraSite registry/repository supports the community through its extensible data model and broad standards based approach. Because the CentraSite Community does not impose a one-size-fits-all governance solution, customers can implement the right governance recipe to meet their unique business needs.

Service Orientation Market Trends

While Web Services have been getting the attention through 2003, in 2004 the IT computing story will be focused squarely on Service Orientation. Offering an evolutionary approach to distributed computing that provides greater business agility while enabling companies to use heterogeneous resources more efficiently, Service Orientation, based on established Web Services standards, is set to fundamentally change many different IT markets as enterprises transition to Service-Oriented Architectures.

In particular, the markets of application security, security appliances, system management, application integration, data integration, and business process management are six key markets that will become transformed as vendors in those markets Service-enable their products. Furthermore, there is a window of opportunity for new entrants in each of these markets to build Service-oriented offerings. Those windows will soon close, however, as the established, incumbent vendors in each space consolidate their respective markets.

These consolidation trends will continue through the rest of the decade, as large vendors round out their suites of software that support Service Orientation, resulting in a combined market consisting of vendors offering a full-function SOA Implementation Framework. These frameworks will offer enterprises all the functionality they need to build, run, and manage SOAs. The market for SOA Implementation Frameworks is still nascent as of 2004, but will dominate the distributed computing arena by 2010.

Service-Oriented Process

Download File

Overview of Web Services Management

Download File

Service-Oriented Process to Cannibalize Integrators

As Web services support for business processes matures, companies may be able to throw out expensive and complicated integration systems through a “Service-Oriented Process” approach, according to a new report by XML research firm ZapThink.
“A process is a set of activities that are linked together into a logical flow that meets business requirements,” Ronald Schmelzer, ZapThink co-founder and senior analyst, told internetnews.com.

Read more at: Internetnews.com

Service-Oriented Process

Business processes have always been an important, if understated, asset of enterprises. The nature and methods by which a company runs its business changes on a daily basis at various different levels in the company — from high-level strategic changes to lower-level implementation details. As a result of these changes, enterprises constantly struggle to make their businesses more responsive to business changes by connecting their business requirements to their IT and human capabilities.

However, automating business processes has historically been a difficult-to-achieve goal for most enterprises due to the flexibility of their IT infrastructure. Fortunately, businesses have a solution in Service-Oriented Process: a separate abstraction layer for business process definition and execution that leverages the capabilities of Service-oriented Architectures. Service-Oriented Process provides businesses an approach to tying business requirements to the Service model represented in the SOA metamodel, thereby providing a flexible approach towards implementing architectures that promote business agility.

ZapNote: Mega

Download File

ZapNote: Akazi

Download File

SOA Tools and Best Practices

From its inception through 2002, the primary application for Web Services in the enterprise was to simplify point-to-point integration between systems, thereby reducing the cost of integration. This application of Web Services, however, only scratches the surface of the true potential of Web Services — enabling companies to build agile business processes and IT systems that can respond to change through the use of loosely coupled, standards-based Service-oriented architectures.

The business value of such architectures in terms of the business agility they provide is substantial, but as of early 2003, only a few early adopter enterprises have built such architectures, partly because few tools for building Service-oriented architectures are available on the market, and furthermore, there is little understanding of the best practices companies should follow to build such architectures. This report seeks to clarify the requirements for realizing the value of Web Services by providing a set of emerging best practices as well as an analysis of the tools that are currently available for building Service-oriented architectures.

SOA Tools

From its inception through 2002, the primary application for Web Services in the enterprise was to simplify point-to-point integration between systems, thereby reducing the cost of integration. This application of Web Services, however, only scratches the surface of the true potential of Web Services — enabling companies to build agile business processes and IT systems that can respond to change through the use of loosely coupled, standards-based Service-oriented architectures.

The business value of such architectures in terms of the business agility they provide is substantial, but as of early 2003, only a few early adopter enterprises have built such architectures, partly because few tools for building Service-oriented architectures are available on the market, and furthermore, there is little understanding of the best practices companies should follow to build such architectures. This report seeks to clarify the requirements for realizing the value of Web Services by providing a set of emerging best pra