This document summarizes an approach to service-oriented architecture (SOA) that was applied to two complex integration systems - an Electronic Health Folder system and a Regional Administration Accounting System. It describes the requirements of integrating heterogeneous legacy systems while allowing incremental development. It then summarizes the key patterns used in the SOA including: a data dictionary, service interface design, business object materialization/dematerialization, business object views, dividing services, and versioning.
Seismi Case Study | Oracle Mining Event | Santiago de Chile | 15 March 2012Seismi Limited
Seismi were invited to present a recent case study of a recent Oracle Hyperion DRM (Data Relationship Manager) and EPM installation. The case study outlines the benefits that Oracle DRM can deliver particularly the elimination of the risks of human middleware and the introduction of a fully automated and integrated financial process.
There is a description by Seismi's client's CFO and project sponsor at the outset as well as the client's reaction to the solution, which Seismi continues to support.
The case study highlighted the flexibility of DRM to be at the core of its network and its ability to integrate with multiple vendors
IBM Smarter Business 2012 - Kundcase: Från 0 till 1000 digitala processer i e...IBM Sverige
Portugisiska bankjätten Banco Espirito Santo (BES) är allmänt erkänd innehavare av en av de mest mogna och avancerade insatser inom Process Excellence inom Financial Services. Safiras djupa partnerskap med BES i hjärtat av Center of Excellence för Business Process Management har kunnat ta itu med några av de mest komplexa processerna först och därefter skapa flexibla ramar som gör det möjligt för affärsanvändare att identifiera och automatisera enklare processer. I den här sessionen får du ett insiderperspektiv på vad som krävdes för att få igång programmet, ta del av erfarenheterna och de viktigaste faktorerna till ett framgångsrikt organisationsövergripande BPM-program, som nu automatiserar 1 process varannan dag.
Talare: Pedro Penedo, Partner på Safira
Besök http://smarterbusiness.se för mer information.
Webcast: Is it Possible to Have Too Many Tools? Featuring George Spalding of ...CA Nimsoft
We’re not talking garden tools or carpentry tools or mechanic’s tools, we are talking ITSM Tools. And the answer is a resounding YES!
Wait a Minute! Is this a webinar, sponsored by a tool vendor, telling me that I should not buy every tool that comes down the pike? Another resounding YES!
Pink Elephant and Nimsoft each have direct (and repeated) experience indicating that most organizations have NO Enterprise-wide strategy governing the acquisition, support, management and retirement of the tools used to run IT. Nearly every tool in the IT inventory is recommended, funded, acquired, and managed by a single technical silo…without the slightest nod to any other department, group or technical function. Unquestionably, the largest undiscovered source of IT operational savings is the elimination of redundant or vastly underutilized toolsets. Acquiring the right tools at the right time for the right reasons is the answer.
Seismi Case Study | Oracle Mining Event | Santiago de Chile | 15 March 2012Seismi Limited
Seismi were invited to present a recent case study of a recent Oracle Hyperion DRM (Data Relationship Manager) and EPM installation. The case study outlines the benefits that Oracle DRM can deliver particularly the elimination of the risks of human middleware and the introduction of a fully automated and integrated financial process.
There is a description by Seismi's client's CFO and project sponsor at the outset as well as the client's reaction to the solution, which Seismi continues to support.
The case study highlighted the flexibility of DRM to be at the core of its network and its ability to integrate with multiple vendors
IBM Smarter Business 2012 - Kundcase: Från 0 till 1000 digitala processer i e...IBM Sverige
Portugisiska bankjätten Banco Espirito Santo (BES) är allmänt erkänd innehavare av en av de mest mogna och avancerade insatser inom Process Excellence inom Financial Services. Safiras djupa partnerskap med BES i hjärtat av Center of Excellence för Business Process Management har kunnat ta itu med några av de mest komplexa processerna först och därefter skapa flexibla ramar som gör det möjligt för affärsanvändare att identifiera och automatisera enklare processer. I den här sessionen får du ett insiderperspektiv på vad som krävdes för att få igång programmet, ta del av erfarenheterna och de viktigaste faktorerna till ett framgångsrikt organisationsövergripande BPM-program, som nu automatiserar 1 process varannan dag.
Talare: Pedro Penedo, Partner på Safira
Besök http://smarterbusiness.se för mer information.
Webcast: Is it Possible to Have Too Many Tools? Featuring George Spalding of ...CA Nimsoft
We’re not talking garden tools or carpentry tools or mechanic’s tools, we are talking ITSM Tools. And the answer is a resounding YES!
Wait a Minute! Is this a webinar, sponsored by a tool vendor, telling me that I should not buy every tool that comes down the pike? Another resounding YES!
Pink Elephant and Nimsoft each have direct (and repeated) experience indicating that most organizations have NO Enterprise-wide strategy governing the acquisition, support, management and retirement of the tools used to run IT. Nearly every tool in the IT inventory is recommended, funded, acquired, and managed by a single technical silo…without the slightest nod to any other department, group or technical function. Unquestionably, the largest undiscovered source of IT operational savings is the elimination of redundant or vastly underutilized toolsets. Acquiring the right tools at the right time for the right reasons is the answer.
Process Director is web-based workflow and BPM software that provides users with business process automation and advanced predictive capabilities -- without programming. Patent-pending Process Timeline technology makes business processes predictable, offering a unique modeling capability that measures and anticipates process execution times.
Final groupassignmentpresentation g4_mode1_2012Bryan Johnson
This report provides a study into the existing information system and operational structure of MC Design & Contracting. It aims to provide an understanding of the relevance and overall effectiveness of its current information system and the company‟s operational structure in line with its strategic objectives and corporate vision. With that in mind this report will identify shortcomings and expansion possibilities within the existing system so as to suggest possible interventions.
Process Director is web-based workflow and BPM software that provides users with business process automation and advanced predictive capabilities -- without programming. Patent-pending Process Timeline technology makes business processes predictable, offering a unique modeling capability that measures and anticipates process execution times.
Final groupassignmentpresentation g4_mode1_2012Bryan Johnson
This report provides a study into the existing information system and operational structure of MC Design & Contracting. It aims to provide an understanding of the relevance and overall effectiveness of its current information system and the company‟s operational structure in line with its strategic objectives and corporate vision. With that in mind this report will identify shortcomings and expansion possibilities within the existing system so as to suggest possible interventions.
The cloud is a way to optimize the use of the hardware, sharing it between different systems.
To properly distribute computing time and space of the applications in the available hw resources, they should be organized in pieces, that can be distributed in a transparent way, that are balanced, that use standard way to communicate, that can be monitored. In a word they should follow the SOA approach.
Some typical SOA pattern that greatly improve the cloud effectiveness.
Un metodo di progettazione di reti locali con esigenze di qualità del servizioClaudio Bortone
Metodologia di progettazione per reti LAN con QoS che ha caratteristiche di ortogonalità rispetto agli strumenti di configurazione e ai produttori degli apparati. Con la metodologia sono forniti anche degli algoritmi che permettono di sfruttare gli ultimi standard per reti locali (come MSTP) in modo da trarne benefici per la QoS.
STARS system:
STARS è un sistema tecnologico che offre soluzioni innovative e flessibili per l’organizzazione e la sicurezza in azienda.
Stars significa
TECNOLOGIA: offre soluzioni efficaci per la gestione dei processi organizzativi e per la sicurezza aziendale, tramite l'uso di smartphone collegati ad un data base gestionale accessibile via internet.
EFFICIENZA: fornisce al lavoratore uno strumento costantemente aggiornato relativo a: procedure operative, misure di sicurezza da rispettare sul luogo di lavoro e DPI da indossare.
GARANZIA: consente all’azienda di verificare in tempo reale l’effettivo recepimento da parte del lavoratore delle informazioni fornite, per mezzo di feedback multimediali.
Wi-Fi, W-USB, Bluetooth, WiMax: how much are wireless technology secure? Some hints to make your wireless connection more secure.
http://www.archive.org/details/SicurezzaInformaticaDiBase-Parte2-A.Tringali.OGG
“XPDL 2.0 and BPMN Tutorial
”. XPDL Tutorial presented by Mike Marin, Keith Swenson, and Justin Brunt, during the Business Process Management Summit (February 1, 2006 – Miami, Florida).
Maximo User Group Keynote - "Facilities" is Strategic!Scott Smith, PE
Enabling enterprise asset management (EAM) by leveraging and extending Maximo. Keynote given at the Facilities Maximo User Group in April 2014. Strategies include ISO 55000 alignment, project/contract integration and system alignment.
Bonita Open Solution represents a complete BPMS framework, with a comprehensive modelling and design studio, portal-oriented user environment, and tunable execution engine.
Bonita BPM an open source business process management and workflow suite created in 2011.
Started in France National for research in Computer science.
Companies are looking forward for single Operation center for entire IT stack, This preso summarize the design components for ESOC which will cater entire IT infrastructure and application stack from a single facility.
Biznology è una società di ingegneria informatica che offre servizi di consulenza e supporto per la progettazione e lo sviluppo di applicazioni per sistemi informativi di differenti dimensioni e complessità.
L’approccio metodologico e la profonda conoscenza delle architetture IT caratterizza tutte le attività di consulenza dei professionisti che operano con Biznology.
Biznology nasce dalla fusione delle parole business e technology.
Noi riteniamo che i risultati veramente apprezzabili in ambito ICT si possano ottenere solo se si riesce ad avere una completa visione d’insieme che coniuga la prospettiva del business con le tecnologie ed il governo delle infrastrutture IT.
Proponiamo soluzioni ed interventi il cui successo si basa fondamentalmente sulla capacità di individuare le vere esigenze di business e sul creare valore attraverso l’uso delle giuste tecnologie ed il miglioramento dei sistemi informativi.
Biznology, precedentemente Master Reseller per l’Italia della soluzione ASF, si posiziona ora come divisione focalizzata su problematiche di application integration nel perimetro delle attività Talend Italia ed affianca la distribuzione di questi prodotti ai già citati servizi di consulenza in ambito Project/Program Management, IT Governance, Enterprise Architecture e supporto per la progettazione e lo sviluppo di sistemi informativi aziendali.
2. >apropos alberto.lagna
• Computer Science graduate, Telco master
• CTO of Biznology
• Working as software architect / team leader
• Consulting on design and development of enterprise systems
mainly based on JavaEE and mobile
• UML, XML, BPM expert
• 18 years of working experience in Europe and USA
• JUGTorino member
• Promoting the use of free software and supporting the open
source movement
2
3. >apropos biznology.it
Organization
• Consulting Company Model and Methodology
Training and tools
• Defined a SOA at 360° approach: Plans
– Methodology and tools Economical
Goal and
Reference
– Reference Architecture Result
Architecture
measuremen
– Communication ts
– Integration and Program Management Integration
Communicati
– Economical Goal and Result Measurement and Program
on
Management
– Organization Model and Training Plans
• Because Applying the SOA approach is not ONLY using the
right technology
3
4. Agenda
• Complex integration system developed
– Electronic Health Folder
– Regional Administration Accounting System
• System requirements
• Pattern applied:
– Data dictionary
– Service Interface Design
– Materialisation / Dematerialisation
– Business Object Views
– Divide et Impera between services
– Versioning
– Logging and Monitoring
4
8. System Requirements (1)
• Integrate many (existing) systems
– Consume eterogeneous interfaces
• Exposed even by legacy C, C++, VB, systems
– Expose long lasting interfaces
• They cannot change too often: consumed by systems
developed in different projects, by different vendors
8
9. System Requirements (2a)
• Integrate the Service Oriented world (mainly wso2)
with the BPMS world (not wso2)
– BPMN processes call Service interfaces
– Provide a way to decouple the lifecycle of the BPMN
processes with the service business entities
9
11. System Requirements (3)
• Services could exchange Business Object that can
be part of a big forest in a selective way
– I don’t want to transport the whole Amazonian if I need
just to transport a small tree
11
12. System Requirements (4)
• Big Bang strategy must be avoided,
therefore we need to define:
– a way to develop, test and deploy the system in small
parts
– a roadmap to program when to roll out every part
12
13. System Requirements (5a)
• What if something goes wrong?
– Need a way to understand
• Why a component XYZ did a certain call to a service (that
went in error for example)
• What were the calls that brought to the error
Exception in thread "main" java.lang.NoSuchMethodError:
org.apache.commons.httpclient.HttpConnectionManager.getParams()Lorg/apache/commons/httpclient/params
/HttpConnectionManagerParams;
at org.apache.axis2.transport.http.AbstractHTTPSender.initializeTimeouts(AbstractHTTPSender.java:454)
at org.apache.axis2.transport.http.AbstractHTTPSender.getHttpClient(AbstractHTTPSender.java:514)
at org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:156)
13
15. System Architecture
• Regional Administration Accounting System BIL
module
siac
15
16. Patterns Applied
• To fulfill all the given requirements, the following
patterns were applied:
– Business Objects level
• Data Dictionary
• Service Interface Design
• Materialisation / Dematerialisation
• Business Object Views
– Service Level
• Divide et Impera between Services
• Versioning
• Logging and Monitoring
16
17. Pattern 1: Data Dictionary (1)
• To integrate with differents systems, technologies
• Divided the whole system into
– Functional areas
– Integration areas
• Every area is responsible of a
– Subset of Business Objects
– Subset of (homogeneous) services
• Business Objects
– are the ONLY objects used within the system
– They become the Lingua Franca of the system
17 – Need MAXIMUM care to be designed
18. Pattern 1: Data Dictionary (2)
SIAC
ALI Atti Liquidazione
BIL - Bilancio di previsione e
pluriennale
GSA SocioAssistenziale ATT - Atti Amministrativi
GEN - Contabilità Generale
APJ - Approvvigionamenti
FIN – Contabilità finanziaria
PER Gestione Personale SCD - Contabilità Divisionale
FPR Formazione Professionale
FIS – Adempimenti Fiscali
IVA Contabilità IVA
18
19. Pattern 2: Service Interface Design
• The service messages are containers of Business Objects
• The integration services do translation to/from the Business
Objects
19
20. Pattern 3:
Materialisation / Dematerialisation (1)
• To decouple The BPMN Process lifecycles with the Business
Objects lifecicles
• The Proxy before the Processes Dematerialise the objects
• The Proxy after the Processes Materialise the objects
siac
20
21. Pattern 3:
Materialisation / Dematerialisation (2)
• The BPMN Processes use Dematerialised Entities
EntitaDem (instead of VariazioneCapitolo) with the following attributes:
• uuid = 1234
• nome = acme
• className = “it.csi.siac.siacbilser.interfacews.dd.VariazioneCapitolo”
• attributes ={
• {“tipo”, DIFFICULT}
}
21
22. Pattern 3:
Materialisation / Dematerialisation (3)
• The BPMN Processes use Dematerialised Entities
22
23. Pattern 4: Business Object Views (1)
• Not to always move the whole Amazonian Forest if
only a tree is needed
• Data Services also accept the View parameter that
tells which part of the forest to carry.
23
26. Pattern 5: Divide et Impera (1)
• To be able to Manage (=Imperare) the whole
system
every Area provides his Data Dictionary library with
– The service interfaces
– The service clients
– A fake service implementation
• Divide
– Every service can be tested stand alone,
with the fake services of the other areas that it needs
– Some real services can be added and a limited
integration test can be run
27
27. Pattern 5: Divide et Impera (2)
SIAC
ALI Atti Liquidazione
BIL - Bilancio di previsione e
pluriennale
GSA SocioAssistenziale ATT - Atti Amministrativi
GEN - Contabilità Generale
APJ - Approvvigionamenti
FIN – Contabilità finanziaria
PER Gestione Personale SCD - Contabilità Divisionale
FPR Formazione Professionale
FIS – Adempimenti Fiscali
IVA Contabilità IVA
28
28. Pattern 6: Versioning (1)
• Service Versioning options:
– use an (optional) attribute at the xs:schema element
– denoting the schema version in XML namespaces
– keep XML namespace values constant and add a special
element for grouping custom extensions
@see B. Lublinsky, Versioning in SOA
http://msdn.microsoft.com/en-us/library/bb491124.aspx
• We choose the namespace level
• The Data Dictionary (jar)
– Is of a specific Area of a specific Version
29 – Contains Service Interfaces and Clients
30. Pattern 7: Logging and Monitoring (1)
• Every request and response contains at least
– User, with his profile
– Operation Token (TokenOperazione class below)
• No SOAP Fault
31
31. Pattern 7: Logging and Monitoring (2)
• How does the Operation Token work?
siac n+1"
n+1.1.1.1.1"
n"
n+1.1"
n+1.1.1"
n.1"
32
32. Pattern 7: Logging and Monitoring (3)
• Using a log aggregator the logs can be easily read and
composed
33
33. The patterns are related together
• Business Objects level
– Data Dictionary
– Service Interface Design
– Materialisation / Dematerialisation
– Business Object Views
• Service Level
– Divide et Impera between Services
– Versioning
– Logging and Monitoring
34
34. Good book to read
• Applied SOA, Mike Rosen
http://www.amazon.com/Applied-SOA-Service-
Oriented-Architecture-Strategies/dp/0470223650
• BPMN Method & Style, Bruce Silver
www.bpmessentials.com
35