The key to a successful Service Orientated Architecture (SOA ...
The key to a successful
Service Orientated Architecture
The Casewise Service Orientated Architecture Accelerator
It is widely known that Service Orientated Architecture (SOA) is a paradigm for organizing and
utilizing distributed capabilities that may be under the control of different ownership domains.
In general, entities (people and organizations) create capabilities to solve or support a solution
for the everyday problems they face in the course of their business. It is therefore natural to
think of one person’s needs being met by someone else. In the world of distributed computing,
one computer agent’s requirement may be met by a computer agent belonging to a different owner.
Service Orientated Architecture and Event Driven Architecture (EDA) are the proclamation of the moment, but how
many implementations have really succeeded beyond application integration or point-to-point connection between
partners or application development? What really is SOA and EDA, and how can it be implemented easily and efficiently?
These are some of the many problems IT architects repeatedly face.
Empower decision makers Align IT with business operations
Increase operational efficiency Employ best practice methodology
The core components which make up an SOA implementation
Organizations across all industries sectors are planning an SOA program
with the main focus being to develop an SOA solution that fits their own
bespoke requirements. These types of implementations up until now have
focused on application development making use of services technology,
namely web services. Due to this approach, the level of reusability of the
services becomes very limited reducing the benefits promised by the SOA.
Limited service lifecycle management removes the capability of engineering better services bringing back the
‘application spaghetti model’. Many of these implementations are IT driven and not business driven leaving the
service without a business domain or ownership.
How should we look at SOA? Solution
We should look at SOA in the terms of 3 main areas: Casewise has placed a strong focus on SOA
architectural framework by providing full support
1. A management perspective where IT architects for the enterprise architecture of SOA and
deal with IT process governance, SOA processes, SOA governance.
business and IT convergence.
The Casewise Service Oriented Architecture
2. An architectural framework whereby business Accelerator provides a fully mapped insight into the
requirements are identified and help to define comprehensive SOA standards world by providing
architectural governance and their specifications. an overview of the enterprise services model and
application development environment within an
3. A deployment framework whereby operational SOA approach. It also can highlight all the necessary
infrastructures, service management, standards guidance on how to approach, use and catalog the
and policies are designed and mapped. services available within the enterprise.
These three main concepts provide all the necessary By using a Service Oriented Architecture
steps towards a successful implementation giving Accelerator approach, architects are able to
architects a thread from the design / modeling deliver business oriented application solutions
stages down to the daily execution and activity with greater speed and flexibility. The service
monitoring. All these elements combined provide oriented solutions produced result in lower
the best practice into achieving total business agility. lifecycle costs to customers and increased ROI.
Policies can therefore be defined whilst taking into
account compliance, standards and policies to make By bridging the gap between design and operations,
the implementation across into IT simple, successful the SOA Accelerator utilizes the Casewise BPEL
and highly cost effective. interface in which designs can be transformed in
to the execution language bridging the Enterprise
architect and Technical architect’s worlds for faster
and more effective deployment.
EAI SOA EDA
(Enterprise Application Integration) (Service Orientated Architecture) (Event Driven Architecture) SOA 2.0
The Casewise SOA Accelerator Principle using 3rd wave technology
This concept of a services layer is one of the most important concepts within
any SOA infrastructure.
The service principle is based on the principles of: The work of creating this meta data layer can
be significantly reduced by using Casewise’
Channel neutrality – deployment of the same market leading Corporate Modeler solution
service but into different channels combined with the SOA Accelerator component.
This is achieved by introducing a specific
Reusability – whereby architects can reuse the methodology within the solution itself which
software functionality by different business processes allows describes the multiple layers of services
(fine grain and gross grain services) within the
Replaceability – this defines the ability to replace infrastructure.
the software components with others providing the
same functionality without losing the software service. From this specification, detailed maps can
be created of the implementation which helps
This service layer reflects specific business evaluate the possible risks associated when
processes that take advantage of the defined implementing the services. As a result, this can
business processes whilst abstracting the depict the increases in the maintainability of
consumer from the complexity of the the application which is fed through from
implementations. business services.
Service Execution Management
Another integral part which much be addressed for an enterprise is the service
At the first stage, architects need to / SO
design and model the service and then hi
deploy along with the specific policies
and business rules which define the
execution stage. During the execution
stage, architects monitor the service
retrieving multiple types of information g
including operational and business
activity that will feed to improve and Business Process
adjust that service. Improvement
By using the modeler and simulation
capabilities of the Casewise Corporate xe
Modeler Suite, architects are able to tion
improve services on a higher level e
to fully adapt their business process A Se
needs and requirements. The whole SOA/E
lifecycle can be recorded within the
Corporate Modeler repository for full
analysis and evaluation purposes. The Business Activity Monitoring (BAM) Process Cycle
Service orchestration mapped insight into the comprehensive SOA
Service orchestration is achieve by using standards world by providing an overview of
another standard mainly BPEL. BPEL (Business the enterprise services model and application
Process Execution Language) for Web services development environment within an SOA approach.
(BPEL 4WS) is an XML-based language designed It also can highlight all the necessary guidance on
to enable service orchestration and automation how to approach, use and catalog the services
of processes even across multiple organizations available within the enterprise.
- using a combination of Web services. Using BPEL,
a user is able to formally describe a business Bridging the gap between design and operations,
process that will take place across the Web in such the SOA Accelerator utilizes the Casewise BPEL
a way that any co-operating entity can perform one interface in which designs can be transformed in
or more steps in the process the same way. to the execution language bridging the Enterprise
architect and Technical architect’s worlds for
Casewise capabilties faster and more effective deployment.
The Casewise Service Oriented Architecture
Accelerator “SOA Accelerator” provides a fully
The Casewise SOA Accelerator Benefits
Casewise’s experience in implementing service oriented solutions, coupled with the
SOA methodology, provides a full-lifecycle approach to establishing and implementing
a successful enterprise SOA. Benefits an organization can expect to see include:
• Reduced time to integrate all your business activities • Improved earnings by reduced loss/expense costs
• Automation which reduces staff processing and • Increased take up due to better services
• ultimately leads to more reliable processes • Reduced costs by making implementation more
• Easier methods to apply and document changes • reusable and more flexible to change
• Integration of suppliers and customer width using
Efficiency • one approach
• Real time information and data consistency for • Better management of applications and services cycle
• decision making
• Reduction in work and time to manage internal For further information on the Caswise SOA
• activities and manage their evolution Accelerator, contact your Casewise Account
• Enhanced knowledge by providing transparency Manager or:
• and visibility T: +44 (0)1923 830 300
USA UK Germany France Belgium
T: +1 856-380-1400 T: +44 (0)1923 830 300 T: +49 (0)69 677 33 414 T: +33 (0)1 53 43 93 73 T: +32 2 709 29 21
F: +1 856-380-1499 F: +44 (0)1923 830 301 F: +49 (0)69 677 33 200 F: +33 (0)1 53 43 93 93 F: +32 2 709 29 22
Casewise Systems Inc. Casewise Limited Casewise Systems Casewise Systems France Casewise Belgium
100 Century Parkway 64 Clarendon Road Germany 17 Square Edouard VII Pegasuslaan 5
Suite 150 Watford Frankfurt Eurohouse 75009 1831 Diegem
Mount Laurel Hertfordshire Lyonerstrasse 26 Paris Brussels
New Jersey WD17 1DA 60528 France Belgium
08054 United Kingdom Frankfurt