Example Design Pattern Instantiation

The figure below provides an example design pattern instantiation. Specifically, several of the Seros Product Suites have been instantiated with a appropriate vendor/open source foundation products. Five core enterprise services are represented in the figure that provide Security and Identity Management, Service Registry and Discovery, Enterprise Service Monitoring, Messaging and Transformation, and Recurring Operational Patterns.

For each core enterprise service, a representative subset of the commoditized service capabilities provided by the instantiated service is shown below. Additionally, some examples of how the commoditized services can be composed together are provided. For example, the commodity services for Service Registry and Discovery can be composed with the commodity services for Enterprise Service Management to create a more seamless service governance capability. In this example, as services are successfully registered, to include a Service Level Agreement (SLA); they can also be automatically provisioned for service monitoring against the specified SLA. Simultaneously, service performance statistics can be automatically provided back to the Service Registry on a recurring basis to provide potential users with quick reference data on the performance of discovered services. Another example shows how Messaging and Transformation can be composed with Enterprise Service Management to create an enterprise wide capability for the exchange of performance data. For this example, a message topic is created that utilizes an XML schema for performance data reporting. Note that this approach is compliant with the Oasis Web Service Distributed Management (WSDM) Standard along with WSDM subordinate standards such as Management of Web Services (MOWS). Performance from a variety of enterprise wide resources can now be reported to the Enterprise Service Management capability for enterprise wide reporting. This is performed by simply sending and receiving performance data, formatted in accordance with the XML schema, on the appropriate message topics. As a final example, Messaging and Transformation can be composed with the Seros Content Awareness Suite to provide an automated publishing capability for all, or selected message traffic. The automated publishing will be based on a user-defined vocabulary that then allows for precision search of message traffic to satisfy business domain needs.

Example SOA Core Services Instantiation and Composition

The figure also illustrates how the JSR-168 compliant portlets available with each Seros Product Suite can be composed into an overall SOA Dashboard contained within a Portal Framework. A partial list of capabilities provided by the SOA Dashboard is also shown in the figure.

Lastly, the figure highlights the additional business value Seros brings to an organization with respect to significantly reducing back-end product integration and maintenance costs. Specifically, Seros assumes responsibility for the Foundation Product(s) integration and maintenance. This eliminates individual organizations from having to bear the brunt of these costs. Therefore, organizations can now focus on the business domain aspects of their reference architecture along with implementing their business domain services. Seros also assumes responsibility for evolving the commoditized web services as open standards, technologies, and the vendor market space changes over time. All of this adds up to cost savings for organizations wanting to put a business value focused SOA implementation in place in a measured, timely, and cost effective way.

Determining exactly which Seros Product Suites (or parts of product suites) should be purchased and how they apply to an organization’s current level of SOA implementation maturity is further discussed under the Consulting tab.

Download this document