180 likes | 301 Views
Integration Is. Arne Jørgensen QuestPoint AS arne@questpoint.no. ...interesting. ”May you live in interesting times” (Chinese saying). Agenda. Areas of focus: Service area / level of ambition Infrastructure Architecture, design and implementation Testing Organization Process. Why?.
E N D
Integration Is... Arne Jørgensen QuestPoint AS arne@questpoint.no
...interesting ”May you live in interesting times” (Chinese saying)
Agenda • Areas of focus: • Service area / level of ambition • Infrastructure • Architecture, design and implementation • Testing • Organization • Process
Why? • Many stakeholders, internal and external • Several systems involved • Lack of standards • Changing technology • Missing or diverging best practices • ROI is hard to calculate • TCO is hard to calculate • Lack of skilled resources
Service area / level of ambition • ”Simple” integration • Service-to-service • Request-response • Batch/ftp • SOA backbone • Service Broker • Enterprise Service Bus • Event Driven Architecture
Service area / level of ambition • Business Process Management • Workflow management • Integrating human/manual processes • Service monitoring • Business Activity Monitoring • SLA monitoring • Common Information Model
Infrastructure • Monitoring • Availability • Health • Performance • Business processes • Alerts • Tools (e.g. MOM) • Organization
Infrastructure • Service Registry • Documentation • Usage, policies • WSDL, schemas, BPEL • Examples • Dependencies • Endpoint registry • Dynamic client configuration • SLA support • UDDI, custom
Infrastructure • Service consumer registry • Change impact analysis • Communicate changes • Priority management • SLA support • Runtime prioritization, notification • Reporting and statistics
Infrastructure • Environments • Production • Staging • Test • Development • Requirements • Usage/scheduling • Temporary environments
Architecture, design and implementation • Service design • Business domains • Granularity • Asynchronous vs. request-response • Versioning and change management • Layering, modularization and re-use • Ad-hoc services • Dependencies • Internal vs. External use
Architecture, design and implementation • Schema design / information model • Business Objects, Data Transfer Objects • Versioning, change management • Compatibility and extensibility • minOccurs=”0” • <xs:any namespace=”##any”> • Communication model • Asynchronous vs. request-response • Reliable messaging • Retries and duplicate detection • Web services, queues, tcp or ? • WS-*, what to use, when to use?
Architecture, design and implementation • Security • Internal vs. External • Access control • E.g. limit number of calls per day • Exception handling • Schema validation? • Return SOAP errors vs. Message (e.g. FindCustomerById) • Logging/tracking
Architecture, design and implementation • Scalability and load balancing • Reliability and fail-over • Instrumentation • Configuration • Testability and QA
Testing • Infrastructure • Environments and isolation • Ports, firewalls... • Security • Certificates • End-to-end testing • Test-versions of all systems available? • External partner coordination
Organization • Teams and roles • Project related work • Cross-project work • Project independent work • Governance and guidelines • Administration and coordination • Escalation of issues • Operation, maintenance and support
Process • Pre-analysis • Early estimates • Requirements/specification • Estimates • Analysis (impact, process, architecture, volume/traffic) • Design • Development • Testing, QA • Documentation • Deployment • Operation
Discussions? • IASA: www.iasa.no • NNUG: www.nnug.no • arne@questpoint.no