1 / 18

Enhancing Integration Strategies Across Diverse Stakeholders and Technologies

Uncover the complexities of integration in today’s technology landscape through Arne Jørgensen of QuestPoint AS. This presentation addresses key challenges such as varying stakeholder expectations, infrastructure demands, and the pressing need for standardized practices. Explore service levels, architectural design, testing methodologies, and organizational considerations crucial for successful integration. Gain insights into managing human processes, monitoring business activities, and optimizing workflows to ensure efficient and effective service delivery.

donal
Download Presentation

Enhancing Integration Strategies Across Diverse Stakeholders and Technologies

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Integration Is... Arne Jørgensen QuestPoint AS arne@questpoint.no

  2. ...interesting ”May you live in interesting times” (Chinese saying)

  3. Agenda • Areas of focus: • Service area / level of ambition • Infrastructure • Architecture, design and implementation • Testing • Organization • Process

  4. 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

  5. Service area / level of ambition • ”Simple” integration • Service-to-service • Request-response • Batch/ftp • SOA backbone • Service Broker • Enterprise Service Bus • Event Driven Architecture

  6. Service area / level of ambition • Business Process Management • Workflow management • Integrating human/manual processes • Service monitoring • Business Activity Monitoring • SLA monitoring • Common Information Model

  7. Infrastructure • Monitoring • Availability • Health • Performance • Business processes • Alerts • Tools (e.g. MOM) • Organization

  8. Infrastructure • Service Registry • Documentation • Usage, policies • WSDL, schemas, BPEL • Examples • Dependencies • Endpoint registry • Dynamic client configuration • SLA support • UDDI, custom

  9. Infrastructure • Service consumer registry • Change impact analysis • Communicate changes • Priority management • SLA support • Runtime prioritization, notification • Reporting and statistics

  10. Infrastructure • Environments • Production • Staging • Test • Development • Requirements • Usage/scheduling • Temporary environments

  11. 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

  12. 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?

  13. 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

  14. Architecture, design and implementation • Scalability and load balancing • Reliability and fail-over • Instrumentation • Configuration • Testability and QA

  15. Testing • Infrastructure • Environments and isolation • Ports, firewalls... • Security • Certificates • End-to-end testing • Test-versions of all systems available? • External partner coordination

  16. 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

  17. Process • Pre-analysis • Early estimates • Requirements/specification • Estimates • Analysis (impact, process, architecture, volume/traffic) • Design • Development • Testing, QA • Documentation • Deployment • Operation

  18. Discussions? • IASA: www.iasa.no • NNUG: www.nnug.no • arne@questpoint.no

More Related