Index
A
- actor type, service / Actor type
- ad hoc business need
- about / Ad hoc business need
- Advanced Message Queuing Protocol (AMQP) / Interfaces for events
- agents / Contracts and Policies
- agile methodologies / Methodology
- Ant / Deployment using scripting
- Applicable Service Principles / Service definition revisited
- Application Cycle Management processes (strategic) / Methodology
- Application Development Framework(ADF) / User interface
- application management
- about / Application management
- activities, example / Application management
- Application Services Library (ASL) / Methodology
- methodology / Methodology
- SOA, impact / Impact of SOA
- Application Services Library (ASL)
- Application Cycle Management processes (strategic) / Methodology
- Organizational Cycle Management processes (strategic) / Methodology
- management processes (tactical) / Methodology
- Service Organization processes (operational) / Methodology
- development and Maintenance processes (operational)Topicn / Methodology
- connecting processes (operational) / Methodology
- approaches, SOA realization
- about / Approaches
- example, document management service / Example – Document Management Service
- Top-down identification / Top-down identification
- bottom-up identification / Bottom-up identification
- meet in the middle approach / Meet in the middle
- architectural layer, service
- about / Architectural layer
- business architecture layer / Architectural layer
- information architecture layer / Architectural layer
- technical layer / Architectural layer
- architecture
- about / Architecture as a tool, Architecture ontology
- definition, URL / Architecture as a tool
- layering / Layering of architecture
- models / Models
- requisites / Requirements
- enterprise architecture / Enterprise architecture
- reference architecture / Reference architecture
- solution architecture / Solution architecture
- project architecture / Project architecture
- software architecture / Software architecture
- Service Oriented Architecture / Service Oriented Architecture
- Architecture Capability Framework / Enterprise architecture
- Architecture Development Method (ADM) / Enterprise architecture
- architecture process
- about / Architecture process
- Ad hoc business need / Ad hoc business need
- solution, defining / Define the solution
- deviations / Deviations
- solution architecture, integration / Integration in the solution architecture
- planned feature project / Planned feature
- picking your battles / Pick your battles
- SOA governance / Pick your battles
- ASL (Application Services Library) / Methodology
- Atom Publishing Protocol
- about / Standards
- autonomy / Isolation
B
- best of breed
- about / Comprehensive suite or best of breed
- versus comprehensive suite / Comprehensive suite or best of breed
- Big Design Up Front / Methodology
- BizTalk orchestration / BizTalk Server
- BizTalk Server
- about / BizTalk Server
- messaging component / BizTalk Server
- orchestration component / BizTalk Server
- bottom-up development / Services
- bottom-up identification
- about / Bottom-up
- BreakfastService / Combining classifications
- bug and issue tracker system / Bug and issue tracker system
- Business-to-Business (B2B) / Organizational boundaries
- Business-to-Consumer (B2C) / Organizational boundaries
- Business Activity Monitoring / Business Activity Monitoring
- Business Activity Monitoring (BAM) / Business Process Management, Events, Business Activity Monitoring (BAM), Oracle BPM Suite, Business Activity Monitoring
- business architecture layer / Architectural layer
- business case
- about / Business case – benefits for different stakeholders, Business case explained
- benefits / Business case explained
- company, as whole / Company as a whole, Summary of scenarios
- example, WATB (We Are The Best) company / Example 1 – insurance company WATB needs shorter time to market, Summary of scenarios, Analysis of the scenarios
- example, TPIR (The Price Is Right) company / Example 2 – insurance company TPIR needs to decrease operational cost, Summary of scenarios, Analysis of the scenarios
- IT / IT
- example, TMS (Too Many Systems) company / Example – insurance company TMS needs to consolidate systems
- departmental benefits / Departmental benefits, Example – insurance company X wants to cut cost, Analysis of the scenarios
- business faults / Fault-prevention and handling, Business faults
- Business Information Services Library (BISL)
- URL / Solution architecture
- Business Process Execution Language (BPEL) / Business Process Management
- Business Process Management (BPM) tool / Business Process Management tool
- Business Process Modeling Notation (BPMN) / Business Process Management, Oracle BPM Suite
- business risk / Mismatch between business and IT
- Business Rule Management Systems Suite (BRMS)
- about / Business rules
- business rules, Microsoft / Business rules
- business rules, Oracle
- about / Business rules
- business rules, SOA platform
- about / Business rules
- examples / Business rules
- components / Business rules
- Business Rules Engines (BRE) / Business rules
- Business Rules Management Systems (BRMS) / Business rules
- business service identification
- about / Business service identification
C
- call information / Example – insurance company
- case management platform / Case Management
- CaseService / Example 2 – service invocation
- CCS / Example – insurance company
- CDM / Canonical Data Model
- change management
- about / Change management
- pick your battles / Pick your battles
- channel, service / Channel
- claim information / Example – insurance company
- ClaimService / Top-down identification, Meet in the middle
- Closing a Project (CP) / Impact of SOA
- common systems solutions / Solution architecture
- company as a whole, business case
- about / Company as a whole
- example, WATB (We Are The Best) company / Example 1 – insurance company WATB needs shorter time to market, Summary of scenarios
- company as a whole, business case
- example, TPIR (The Price Is Right) company / Example 2 – insurance company TPIR needs to decrease operational cost, Summary of scenarios, Analysis of the scenarios
- Complex Event Processing (CEP) / Events, Complex Event Processing (CEP)
- complex events
- about / Passing information from smaller to larger services
- composite services
- about / Service classification revisited, Composite services
- DocumentService as / Example – DocumentService as a composite service
- composite logic, locating / Where to put the composition logic?
- implementing / Implementation, Example 1 – database link, Example 2 – service invocation
- and process services, differences / Process services
- comprehensive suite
- versus best of breed / Comprehensive suite or best of breed
- comprehensive suites
- advantages / Comprehensive suite or best of breed
- disadvantages / Comprehensive suite or best of breed
- Compression parameter / Example – good or bad service?
- Configuration Management Database (CMDB) / Configuration Management Database
- connecting processes (operational) / Methodology
- content based routing / Enterprise Service Bus
- content framework / Enterprise architecture
- Content Management System (CMS) / Example – insurance company, Example – good or bad service?
- Continuous Query Language (CQL) / WebSphere Operational Decision Management
- contract / Elements of a service – contract, interface, and implementation
- about / Contracts and Policies
- of service states / Changing the contract
- contract-first development / Services
- Controlling a Stage (CS) process / Impact of SOA
- CSS / Example – insurance company
- customer information / Example – insurance company
- Customer Relationship Management (CRM) application / Change management
- CustomerService.getCustomer operation / Canonical Data Model
D
- database link / Example 1 – database link
- decision logic / Business rules
- decoupling / Isolation
- demand management
- demand side / Demand management
- about / Demand management
- supply side / Demand management
- activities / Demand management
- methodology / Methodology
- BiSL / Methodology
- SOA, impact / Impact of SOA
- demand side / Demand management
- departmental benefits, business case / Departmental benefits, Example – insurance company X wants to cut cost, Analysis of the scenarios
- deployment tooling, IBM
- about / Deployment tooling
- from IDE / Deployment from the IDE
- from web interface server / Deployment from the web interface of the server
- deployment scripts / Deployment scripts
- deployment tooling, Microsoft
- about / Deployment tooling
- BizTalk Server / BizTalk Server
- deployment tooling, Oracle
- about / Deployment tooling
- from IDE / Deployment from the IDE
- from console / Deployment from the console
- scripting used / Deployment using scripting
- deployment tools / Comparison
- deprecated stage / Service stages
- designed stage / Service stages
- design tooling, IBM
- about / Design tooling
- services / Services
- composite services / Composite services
- design tooling, Microsoft / Design tooling
- design tooling, Oracle
- about / Design tooling
- for developers / Design tooling for developers
- for business anlaysts / Design tooling for business analysts
- design tooling, SOA platform / Design tooling
- development and Maintenance processes (operational)
- / Methodology
- development process
- about / Development process
- pick your battles, / Pick your battles
- development tooling, IBM / Development tooling
- development tooling, Microsoft / Development tooling
- development tooling, Oracle
- about / Development tooling
- development tooling, SOA platform / Development tooling
- deviations
- about / Deviations
- Directing a Project (DP) / Impact of SOA
- Document Management System (DMS) / Designing the solution
- duplication of data and functionality / Duplication of functionality and data
E
- ebXML RegRep
- about / Standards
- elementary events
- about / Passing information from smaller to larger services
- elementary services
- about / Service classification revisited, Elementary services
- implementing, ways for / Realization
- enterprise architecture / Enterprise architecture
- Enterprise architecture tools / Enterprise architecture tools
- enterprise content management systems / Example – insurance company
- enterprise continuum and tools / Enterprise architecture
- Enterprise Edition (JEE) / Interfaces for events
- Enterprise Information Systems (EIS) / Services
- Enterprise Service Bus (ESB) / Pick your battles
- error-handling mechanisms / Comparison
- error handling, IBM
- about / Error handling
- error handling, Oracle
- about / Error handling
- error handling. Microsoft / Error handling
- ESB
- about / Enterprise Service Bus
- validation / Enterprise Service Bus
- composite services / Enterprise Service Bus
- routing / Enterprise Service Bus
- content based routing / Enterprise Service Bus
- transformation / Enterprise Service Bus
- Event-delivery Network (EDN) / Events
- Event Definition Language (EDL) / Events
- events, IBM
- about / Events
- WebSphere Operational Decision Management / WebSphere Operational Decision Management
- IBM Business Monitor / IBM Business Monitor
- events, Microsoft
- Microsoft Message Queuing (MSMQ) / Message-oriented middleware
- Message-oriented middleware / Message-oriented middleware
- Complex Event Processing (CEP) / Complex Event Processing (CEP)
- Business Activity Monitoring / Business Activity Monitoring
- events, Oracle
- about / Events
- Java Messaging Service (JMS) / Events
- Oracle Advance Queuing (AQ) / Events
- Event-delivery Network (EDN) / Events
- Event Definition Language (EDL) / Events
- Complex Event Processing (CEP) / Events
- Business Activity Monitoring (BAM) / Events, Business Activity Monitoring (BAM)
- Oracle Event Processing (OEP) / Oracle Event Processing (OEP)
- events, SOA platform
- about / Events
- queuing / Events
- publish/subscribe / Events
- interface for / Interfaces for events
- event sinks / Oracle Event Processing (OEP)
- example, insurance company
- management processes / Example – insurance company
- operational processes / Example – insurance company
- supporting processes / Example – insurance company
- examples
- insurance company / Example – insurance company, Example – insurance company, Example – insurance company
- utility companies / Example – utility companies
- international software company / Example – international software company
- software company / Example – a software company
- exception shielding / Technical and software faults
- eXtensible Business Reporting Language (XBRL) / Canonical Data Model
- external events
- about / Passing information from smaller to larger services
- Extreme Programming (XP) / Methodology
F
- faults, service
- preventing / Fault-prevention and handling
- business faults / Fault-prevention and handling, Business faults
- faulty user input / Fault-prevention and handling, Faulty user input
- technical and software faults / Fault-prevention and handling, Technical and software faults
- faulty user input / Fault-prevention and handling, Faulty user input
- feature by feature, roadmap / Feature by feature
- Federal Enterprise architecture (FEA)
- URL / Reference architecture
- foundation solutions / Solution architecture
G
- gap-analysis / Top-down
- gateway / Contracts and Policies
- Geek and Poke
- URL / Reuse
- getVersion method / Making the version explicit for service consumers
- governance
- about / Governance
- granularity, service / Granularity
H
- Health Level 7 (HL7) / Canonical Data Model
- HR-XML standard
- URL / Analysis of the scenarios
I
- IBM
- services / Comparison, Services
- events / Comparison, Events
- service composition / Comparison, Service composition, IBM WebSphere Enterprise Service Bus
- business rules / Comparison, Business rules
- user interface / Comparison, User interface
- security / Comparison, Security
- registry and repository / Comparison, Registry and repository
- design tooling / Comparison, Design tooling
- development tooling / Comparison, Development tooling
- test tooling / Comparison, Test tooling
- deployment tooling / Comparison, Deployment tooling
- monitoring / Comparison, Monitoring
- error handling / Comparison, Error handling
- about / IBM
- runtime environments / IBM Business Process Manager
- IBM Business Monitor / IBM Business Monitor
- IBM Business Process Manager
- about / IBM Business Process Manager
- IBM Rational Application Developer (RAD) / Services
- IBM WebSphere Application Server (WAS) / Services
- IBM WebSphere ILOG Decision Validation Services / Business rules
- IBM WebSphere ILOG Rule Solutions for Office / Business rules
- IBM WebSphere ILOG Rule Team Server / Business rules
- Idempotency, service / Idempotency, Idempotency and statefulness
- idempotency, service / Idempotency and statefulness
- identified stage / Service stages
- Identity and Access Management (IAM) tooling
- about / Security
- identity management / Security
- authentication / Security
- authorization / Security
- ILOG BRMS
- about / Business rules
- implementation / Elements of a service – contract, interface, and implementation
- existing software, using / Using existing software
- building / Build the implementation
- changing / Changing the implementation
- implemented stage / Service stages
- industry solutions / Solution architecture
- information architecture layer / Architectural layer
- information service identification
- about / Information service identification
- Information Technology Infrastructure Library (ITIL)
- about / Methodology
- activities / Methodology
- input or facts / Business rules
- Insurance Administration System (IAS) / Example – insurance company TMS needs to consolidate systems
- Integrated Development Environments (IDEs) / Development tooling
- interface / Elements of a service – contract, interface, and implementation
- types / Interfaces
- proprietary interfaces / Proprietary interfaces
- web services / Web services
- changing / Changing the interface
- internal events
- about / Passing information from smaller to larger services
- interoperability, service / Interoperable
- isolation, service / Isolation
- about / Isolated, Isolation and composition – a contradiction?
- print service, example / Example: print service
- IT
- about / The importance of information
- importance / The importance of information
- insurance company, example / Example – insurance company, Example – insurance company
- and business, mis match / Mismatch between business and IT
- risk, managing / Mismatch between business and IT
- data and functionality, duplication / Duplication of functionality and data
- strategies / Strategies to stay ahead
- software company, example / Example – a software company
- IT, business case
- example, TMS (Too Many Systems) company / Example – insurance company TMS needs to consolidate systems
- ITIL / Configuration Management Database
- ITIL (Information Technology Infrastructure Library) / Methodology
- IT service and operations management
- about / IT service and operations management
- Information Technology Infrastructure Library (ITIL) / Methodology
- methodology / Methodology
- SOA, impact / Impact of SOA
J
- Java Enterprise Edition (JEE) / Services
- Java Message Service (JMS) / Interfaces for events, IBM WebSphere Enterprise Service Bus
- Java Messaging Service (JMS) / Events
K
- Kanban / Methodology
L
- loose-coupling / Isolation
- about / Isolation and composition – a contradiction?
M
- management processes / Example – insurance company
- management processes (tactical) / Methodology
- Managing Product Delivery (MP) / Impact of SOA
- mash up / User interface
- maturity model
- about / Maturity and stages
- SOA, starting with / Stage 0: Starting with SOA
- Newlyweds / Stage 1: Newlyweds
- live / Stage 2: Live
- growing up / Stage 3: Growing up
- experience / Stage 4: Experience
- maintenance mode / Stage 5: Maintenance
- Maven / Deployment using scripting
- MediationFlows / IBM WebSphere Enterprise Service Bus
- meet -in-the-middle development / Services
- meet in the middle / Meet in the middle
- Message Oriented Middleware (MOM) / Events
- messaging component / BizTalk Server
- Microsoft
- services / Comparison, Services
- events / Comparison, Message-oriented middleware
- service composition / Comparison, Service composition
- business rules / Comparison, Business rules
- user interface / Comparison, User interface
- security / Comparison, Security
- registry and repository / Comparison, Registry and repository
- design tooling / Comparison, Design tooling
- development tooling / Comparison, Development tooling
- test tooling / Comparison, Test tooling
- deployment tooling / Comparison, Deployment tooling
- monitoring / Comparison, Monitoring
- error handling / Comparison, Error handling
- BizTalk ServerTopicnabout / BizTalk Server
- Microsoft BizTalk Server
- Visual Studio / BizTalk Server
- BTSTask command-line tool / BizTalk Server
- Scripting and APIs / BizTalk Server
- Microsoft Message Queuing (MSMQ) / Message-oriented middleware
- monitoring, Microsoft / Monitoring
- monitoring, Oracle
- about / Monitoring
- monitoring tools / Comparison
- Multipurpose Internet Mail Extensions (MIME) / Making the version explicit for service consumers
N
- .NET Messaging (NMS) API / Interfaces for events
- NORA
- URL / Reference architecture
O
- OASIS
- about / From sunny-side-up eggs to IT
- URL / From sunny-side-up eggs to IT
- order-to-cash business process / From sunny-side-up eggs to IT
- example, international software company / Example – international software company revisited, Interface, Implementation
- Open Group Definition / Service definition revisited
- operational processes / Example – insurance company
- operations
- about / Operations
- pick your battles, / Pick your battles
- Oracle
- services / Comparison, Services
- events / Comparison, Events
- service composition / Comparison, Service composition
- business rules / Comparison, Business rules
- user interface / Comparison, User interface
- security / Comparison, Security
- registry and repository / Comparison, Registry and repository
- design tooling / Comparison, Design tooling
- development tooling / Comparison, Development tooling
- test tooling / Comparison, Test tooling
- deployment tooling / Comparison, Deployment tooling
- monitoring / Comparison, Monitoring
- error handling / Comparison, Error handling
- Oracle Advance Queuing (AQ) / Events
- Oracle BPM Suite / Oracle BPM Suite
- Oracle Business Process Manager (OBPM) / Oracle BPM Suite
- Oracle Enterprise Pack for Eclipse (OEPE) / Development tooling
- Oracle Enterprise Repository (OER) / Registry and repository
- Oracle Event Processing (OEP) / Oracle Event Processing (OEP)
- Oracle Service Bus (OSB)
- service management / Oracle Service Bus
- service virtualization / Oracle Service Bus
- security / Oracle Service Bus
- adaptive messaging / Oracle Service Bus
- configuration framework / Oracle Service Bus
- Oracle SOA Suite / Oracle SOA Suite
- Oracle WebCenter
- about / User interface
- WebCenter Content / User interface
- WebCenter Sites / User interface
- Application Adapters for Oracle WebCenter / User interface
- WebCenter Portal / User interface
- WebCenter Social / User interface
- Oracle Web Services Manager (OWSM)
- about / Security
- orchestration component / BizTalk Server
- order-to-cash business process / From sunny-side-up eggs to IT
- OrderService
- contract / Contract
- interface / Interface
- implementation / Implementation
- consumer / Consumer and provider
- provider / Consumer and provider
- reuse / Reuse
- OrderService.getOrderDetails operation / Canonical Data Model
- ordinary events / Oracle Event Processing (OEP)
- organization-specific solutions / Solution architecture
- organizational boundaries, service / Organizational boundaries
- Organizational Cycle Management processes (strategic) / Methodology
- organizational risk / Mismatch between business and IT
- organizational silos
- about / Process silos
- output or decisions / Business rules
P
- PaymentService / Top-down identification, Meet in the middle
- picking your battles
- about / Governance
- policies
- about / Contracts and Policies
- gateway / Contracts and Policies
- agents / Contracts and Policies
- policy information / Example – insurance company
- portal / Integrated user interfaces
- portlets / Integrated user interfaces
- PRINCE2
- about / Methodology
- process by process, roadmap / Process by process
- process services
- about / Service classification revisited, Process services
- and composite services, differences / Process services
- implementing / Implementation
- process silos
- about / Process silos
- utility companies, example / Example – utility companies
- international software company, example / Example – international software company
- insurance company, example / Example – insurance company
- product information / Example – insurance company
- products
- about / What is a service?
- elements / Elements of a service – contract, interface, and implementation
- project architecture
- purpose / Project architecture
- project management
- about / Project management
- PRojects IN Controlled Environments 2 (PRINCE2) / Methodology
- methodology / Methodology
- SOA, impact / Impact of SOA
- Starting Up a Project (SU) phase / Impact of SOA
- Directing a Project (DP) / Impact of SOA
- Managing Product Delivery (MP) / Impact of SOA
- Closing a Project (CP) / Impact of SOA
- proprietary interfaces / Proprietary interfaces
- publish/subscribe / Events
Q
- QoS
- about / Service design
- queuing / Events
R
- reference architecture
- about / Reference architecture
- advantages / Reference architecture
- disadvantages / Reference architecture
- reference models / Enterprise architecture
- registry
- standards / Standards
- service consumer, benefits for / Information needed
- benefits / Information needed
- services, finding / Information needed, Find services
- troubleshooting / Information needed, Troubleshooting
- process, changing / Information needed
- change process, supporting / Change process
- in IT landscape / Registries and repositories in your IT landscape
- Enterprise architecture tools / Enterprise architecture tools
- Business Process Management (BPM) tool / Business Process Management tool
- Configuration Management Database (CMDB) / Configuration Management Database
- bug and issue tracker system / Bug and issue tracker system
- ESB / ESB
- Business Activity Monitoring (BAM) / Business Activity Monitoring
- infrastructure monitoring / Infrastructure monitoring
- registry and repository, IBM / Registry and repository
- registry and repository, Microsoft / Registry and repository
- registry and repository, Oracle / Registry and repository
- Representational State Transfer (REST) / RESTful services
- RESTful services / RESTful services
- RETE algorithm / Business rules
- retired stage / Service stages
- retrieveData operation / Example – good or bad service?
- reusability, service
- about / Reusability
- example / Example – reusability
- roadmap
- about / Roadmap
- service by service / Service by service
- process by process / Process by process
- feature by feature / Feature by feature
- system by system / System by system
- routing / Enterprise Service Bus
- Rule Execution Server / Business rules
- Rule Studio / Business rules
S
- Scrum / Methodology
- security, IBM / Security
- security, Microsoft / Security
- security, Oracle / Security
- security, service
- about / Security
- security, SOA platform
- Identity and Access Management (IAM) tooling / Security
- about / Security
- applying, in SOA / Applying security in your SOA
- applying / Applying security in your SOA
- Security Assertion Markup Language (SAML) protocol / Security
- Server Faces (JSF) / User interface
- service
- about / What is a service?
- components / Elements of a service – contract, interface, and implementation
- contract / Elements of a service – contract, interface, and implementation, Type of change – contract, interface, and implementation
- interface / Elements of a service – contract, interface, and implementation, Type of change – contract, interface, and implementation
- implementation / Elements of a service – contract, interface, and implementation, Type of change – contract, interface, and implementation
- example, lets have breakfast / Example – let's have breakfast, Interface
- example, ordering passport / Example – ordering a passport
- provider / Consumer and provider
- consumer / Consumer and provider, Reusability
- registry / Dealing with lots of service providers – service registry
- reused / How can you make sure that people use a service?
- drivers / Drivers for services
- myths / Common myths, Consumers of services are always IT systems
- designing / Service design
- value, providing / Provide value
- implementation, hiding / Implementation hiding
- idempotent / Idempotent
- isolation / Isolated
- interoperability / Interoperable
- isolation (autonomy) / Isolation
- print service, example / Example: print service
- security / Security
- faults, types / Fault-prevention and handling
- idempotency / Idempotency
- idempotency and statefulness / Idempotency and statefulness
- granularity / Granularity
- classifying / Classification, Service classification revisited
- reusability / Reusability
- client / Reusability
- reusability, example / Example – reusability
- good or bad / Example – good or bad service?
- storeData operation / Example – good or bad service?
- retrieveData operation / Example – good or bad service?
- defining / Service definition revisited
- Open Group Definition / Service definition revisited
- Applicable Service Principles / Service definition revisited
- elementary services / Service classification revisited
- composite services / Service classification revisited
- process services / Service classification revisited
- information, passing within services / Passing information from smaller to larger services
- information, passing from smaller service to larger service / Passing information from smaller to larger services
- administrator / Troubleshooting
- consumers / Troubleshooting, Change process
- version / Troubleshooting, Change process
- owner / Change process
- service, components
- contract / Elements of a service – contract, interface, and implementation
- interface / Elements of a service – contract, interface, and implementation
- implementation / Elements of a service – contract, interface, and implementation
- service, drivers
- flexibility / Drivers for services
- standardization / Drivers for services
- cost reduction / Drivers for services
- service, SOA platform
- about / Services
- bottom-up development / Services
- meet-in-the-middle development / Services
- top-down development / Services
- contract-first development / Services
- implementation / Implementation
- interface / Interfaces
- contract / Contracts and Policies
- policies / Contracts and Policies
- service aggregation
- about / Aggregation versus orchestration
- service by service, roadmap / Service by service
- service classification
- about / Service classification revisited
- insurance company, example / Example – insurance company
- actor type / Actor type
- channel / Channel
- organizational boundaries / Organizational boundaries
- security level / Security level
- architectural level / Architectural layer
- combining / Combining classifications
- benefits / Why classify your services?
- Service Component Architecture (SCA) / Oracle SOA Suite, IBM WebSphere Enterprise Service Bus
- service composition
- about / Composability, Aggregation versus orchestration
- service composition, IBM
- about / Service composition
- IBM WebSphere Enterprise Service Bus (ESB) / IBM WebSphere Enterprise Service Bus
- Mediation Flow / IBM WebSphere Enterprise Service Bus
- Service Component Architecture (SCA) / IBM WebSphere Enterprise Service Bus
- Java Message Service (JMS) / IBM WebSphere Enterprise Service Bus
- IBM Business Process Manager / IBM Business Process Manager
- service composition, Microsoft
- BizTalk Server / BizTalk Server
- Windows Server AppFabric / Windows Server AppFabric
- service composition, Oracle
- about / Oracle Service Bus
- Oracle Service Bus (OSB) / Oracle Service Bus
- Oracle SOA Suite / Oracle SOA Suite
- Oracle BPM Suite / Oracle BPM Suite
- service composition, SOA platform
- about / Service composition
- Enterprise Service Bus (ESB) / Enterprise Service Bus
- Business Process Management (BPM) / Business Process Management
- case management platform / Case Management
- service consumer / Service design
- version, making explicit / Making the version explicit for service consumers
- versioning changes, steps for / Communicating change
- service identification
- about / Service identification
- top-down service identification / Top-down
- bottom-up service identification / Bottom-up
- service orchestration
- about / Aggregation versus orchestration
- Service Organization processes (operational) / Methodology
- service provider / Service design
- service registry / Dealing with lots of service providers – service registry
- service registry, SOA platform / Service registry and service repository
- service repository, SOA platform / Service registry and service repository
- services, IBM / Services
- services, Microsoft / Services
- services, Oracle / Services
- service stages
- about / Service stages
- identified stage / Service stages
- designed stage / Service stages
- implemented stage / Service stages
- deprecated stage / Service stages
- retired stage / Service stages
- service states
- contract, changing / Changing the contract
- interface, changing / Changing the interface
- implementation, changing / Changing the implementation
- service versioning
- about / Versioning of services
- contract, service / Type of change – contract, interface, and implementation
- interface, service / Type of change – contract, interface, and implementation
- implementation, service / Type of change – contract, interface, and implementation
- contract, changing / Changing the contract
- interface, changing / Changing the interface
- implementation, changing / Changing the implementation
- Simple Object Access Protocol (SOAP) / SOAP-based services
- Single Point of Truth (SPOT) / Example – insurance company TMS needs to consolidate systems
- SOA
- about / Putting it together – what is SOA?
- features / Putting it together – what is SOA?
- solutions / Solutions
- example, utility company / Example – utility company
- example, international software company / International software company – changing existing processes
- application landscapes, rationalizing / Functional duplication – rationalizing application landscapes
- standardization / Standardization – enabling change
- maturity model / Maturity and stages
- SOA governance / Governance
- SOAP-based services / SOAP-based services
- SOA platform
- about / Overview
- implementation / Overview
- interface / Overview
- policies (contract) / Overview
- events / Overview, Events
- Enterprise Service Bus / Overview
- case management / Overview
- business process management / Overview
- business rules / Overview, Business rules
- user interface / Overview, User interface
- registry and repository / Overview
- Identity and Access Management / Overview
- design tooling / Overview, Design tooling
- development tooling / Overview, Development tooling
- services / Services
- service composition / Service composition
- security / Security
- service registry / Service registry and service repository
- service repository / Service registry and service repository
- example, order to cash / Example – Order-to-cash revisited, Developing the solution
- SOA realization
- about / Organize the SOA effort
- goals and approach, identifying / Organize the SOA effort
- initial business case, creating / Organize the SOA effort
- high-level solution architecture, designing / Organize the SOA effort
- roadmap, defining / Organize the SOA effort
- feature, determining / Organize the SOA effort
- feature, realizing / Organize the SOA effort
- solution, defining / Organize the SOA effort
- solution, delivering / Organize the SOA effort
- solution, implementing / Organize the SOA effort
- handle failure / Organize the SOA effort
- feature, evaluating / Organize the SOA effort
- solution, integrating / Organize the SOA effort
- business case, refining / Organize the SOA effort
- roadmap impact, determining / Organize the SOA effort
- features / Organize the SOA effort
- approaches / Approaches
- software architecture / Software architecture
- software development
- activities / Software development
- TMap / Software development
- methodology / Methodology
- waterfall methodologies / Methodology
- agile methodologies / Methodology
- SOA, impact / Impact of SOA
- solution architecture
- about / Solution architecture
- foundation solutions / Solution architecture
- common systems solutions / Solution architecture
- industry solutions / Solution architecture
- organization-specific solutions / Solution architecture
- Starting Up a Project (SU) phase / Impact of SOA
- statefulness, service / Idempotency and statefulness
- storeData operation / Example – good or bad service?
- stovepiped / User interface
- Straight-Through Processing / Implementation
- supply side / Demand management
- supporting processes / Example – insurance company
- system
- about / Architecture as a tool
- system by system, roadmap / System by system
- System Center Operations Manager (SCOM) / Monitoring
- System Development Methodology (SDM) / Methodology
T
- technical and software faults / Fault-prevention and handling, Technical and software faults
- technical layer / Architectural layer
- technical risk / Mismatch between business and IT
- technical service identification
- about / Technical service identification
- test-driven development (TDD) / Methodology
- test tooling, IBM / Test tooling
- test tooling, Microsoft / Test tooling
- test tooling, Oracle
- about / Test tooling
- transformations / Testing transformations
- SCA testing framework / SCA testing framework
- from console / Testing from the console
- test tools / Comparison
- TMap / Software development
- TM Forum Frameworx and eTOM for telecommunications
- URL / Reference architecture
- TMS (Too Many Systems) company / Example – insurance company TMS needs to consolidate systems
- TOGAF
- about / Layering of architecture
- Architecture Development Method (ADM) / Enterprise architecture
- content framework / Enterprise architecture
- enterprise continuum and tools / Enterprise architecture
- reference models / Enterprise architecture
- Architecture Capability Framework / Enterprise architecture
- tooling
- registry / Tooling
- repository / Tooling
- top-down development / Services
- top-down identification / Top-down identification
- top-down service identification
- about / Example of top-down service identification
- business service identification / Business service identification
- information service identification / Information service identification
- technical service identification / Technical service identification
- top-down service identification
- about / Top-down
- business service identification / Top-down
- information service identification / Top-down
- technical service identification / Top-down
- business service identification, example / Top-down
- information service identification, example / Top-down
- technical service identification, example / Top-down
- TPIR (The Price Is Right) company / Example 2 – insurance company TPIR needs to decrease operational cost, Summary of scenarios, Analysis of the scenarios
U
- UDDI
- about / Tooling, Standards
- user interface, IBM / User interface
- user interface, Microsoft / User interface
- user interface, Oracle / User interface
- user interface, SOA platform
- about / User interface
- capabilities / User interface
- integrated user interface, benefits / Integrated user interfaces
- information mismatch / Information mismatch
V
- Validate-Enrich-Transform-Route-Operate (VETRO) / Enterprise Service Bus
- Vecoz company / Example 1 – insurance company WATB needs shorter time to market
- version control / Versioning of services
- versioning scheme
- about / Versioning of services
- versioning schemes
- about / Versioning schemes
- versioning and lifecycle stages / Versioning and life cycle stages
- for service consumers / Making the version explicit for service consumers
W
- WATB (We Are The Best) company / Example 1 – insurance company WATB needs shorter time to market
- waterfall methodologies / Methodology
- web content management systems / Example – insurance company
- WebLogic Scripting Tool (WLST) / Deployment using scripting
- Web Service Description Language (WSDL) / Interface, SOAP-based services
- web services
- about / Web services
- SOAP-based services / SOAP-based services
- RESTful services / RESTful services
- WebSphere ESB Registry edition / Registry and repository
- WebSphere Operational Decision Management / WebSphere Operational Decision Management
- WebSphere Registry and Repository (WSRR) / Registry and repository
- whiteboards / Design tooling
- Windows Server AppFabric / Windows Server AppFabric
- Windows Workflow Foundation (WF) / Windows Server AppFabric
- World Wide Web Consortium (W3C) / SOAP-based services
- WS-* / SOAP-based services
X
- XML Process Definition Language (XPDL) / Business Process Management
- XML Schema (XSD) / Interface
Z
- Zachman
- URL / Architecture as a tool