Service Oriented Architecture Glossary
BPM - Business Process Management (BPM) is a discipline combining software capabilities and business expertise through people, systems, and information to accelerate time between process improvements, facilitating business innovation.
Composite Business Services - Composite business services are collections of individual business and IT services that work together, along with a client?s existing applications, to provide specific business solutions that support the industry and semantic standards common to each industry, such as HIPAA in Healthcare, ACORD in Insurance, and SWIFT in Banking.
Connectivity - SOA connectivity enables you to exchange information between all your assets within and outside of your business through a secure, reliable, and scaleable messaging backbone for seamless communication among applications, people, and information sources.
Dashboard - Dashboards use SOA to provide a single view into how your business is operating ? unifying fragmented sources of information and applications for monitoring, analysis, decision making, and execution
Entry Points - SOA Entry Points are five distinct but interrelated ways of undertaking SOA projects that encompass both a business and an IT component. They are: People, Process, Information, Connectivity, and Reuse
ESB - An Enterprise Service Bus (ESB) is a flexible connectivity infrastructure for integrating applications and services by performing the following actions between services and requestors: ROUTING messages between services, CONVERTING transport protocols between requestor and service, TRANSFORMING message formats between requestor and service, and HANDLING business events from disparate sources.
Event - An event is a significant real world action or instance which does or does not occur in a specific period of time. Services respond to events in accordance with business rules.
Information - Information as a service is an approach that unlocks information in all its forms from its repository, process, and application silos, providing it as a trusted service to the applications, processes and decision makers who need it.
Process - A process is a set of related business tasks spanning people, systems, and information to produce a specific service or product. The process entry point provides specific tools and services to help streamline and improve processes across the enterprise. The Process entry point provides the foundation for IBM's business process management with SOA.
Registry & Repository - A central reference point within a service oriented architect that stores and manages services information (metadata). It stores information about what the services are, how they are used, and how they are interconnected with other components. This information can be used to foster reuse of services assets and to govern services throughout the lifecycle.
Reuse - Reuse addresses methods of creating the services needed to execute business tasks by service-enabling existing IT assets, consuming reusable services from an external service provider, and creating net-new reusable services from scratch.
SCA - SCA provides an open, technology-neutral model for implementing IT services that are defined in terms of a business function and make middleware functions more accessible to the application developer. SCA also provides a model for the assembly of business solutions from collections of individual services, with control over aspects of the solution such as access methods and security. Vendors working to create SCA include BEA Systems, IBM, IONA, Oracle, SAP, Siebel, and Sybase.
SDO - SDO complements SCA by providing a common way to access many different kinds of data. The specification reduces the skill levels and time required to access and manipulate business data. Today, a multitude of APIs are used to manipulate data. These APIs tend to tightly couple the source and target of the data making their use error-prone and subject to breaking as business requirements evolve. SDO makes it easier to use and realize the value of these APIs without having to code directly to them. Vendors working to create SDO include BEA Systems, IBM, Oracle, SAP, Siebel, Sybase, and Xcalia.
Security - SOA Security helps create a consistent infrastructure to support SOA projects by enableing user-centric, policy driven authentication, authorization and access to applicaitons, information and data, and consistent enforcement and auditing of corporate compliance and security policy.
Service - Services are self-contained, reusable software modules that are independent of applications and the computing platforms on which they run. Services have with well-defined interfaces and allow a 1:1 mapping between business tasks and the exact IT components needed to execute the task.
Service orientation - A way of thinking about your business processes as linked, loosely coupled tasks supported by services.
SOA - Service Oriented Architecture (SOA) is a business-driven IT architectural approach that supports integrating your business as linked, repeatable business tasks, or services. SOA helps today?s businesses innovate by ensuring that IT systems can adapt quickly, easily and economically to support rapidly changing business needs. SOA helps customers increase the flexibility of their business processes, strengthen their underlying IT infrastructure and reuse their existing IT investments by creating connections among disparate applications and information sources.
SOA foundation - Integrated, open-standard-based set of software, best practices and patterns that is designed to provide what you need to get started with your SOA.
SOA infrastructure - As clients adopt SOA this new simplified, virtualized and distributed application frameworks pose challenges for infrastructures that must be addressed. To ensure the new applications can meet their performance, availability, scalability, security and management requirements, the infrastructure needs to be assessed and transformed to support SOA.
SOA infrastructure solution - The SOA infrastructure solution from IBM is designed to help you increase business flexibility, responsiveness and performance by enabling your IT infrastructure for SOA. We start by leveraging your existing IT assets, then evaluate, design and implement the enhancements needed to establish a more flexible and robust infrastructure.
SOA lifecycle - The SOA Lifecycle defines a methodology for conducting successful SOA projects by modeling the business process and the services that will support them, assembling the services into a composite application, deploying the services in a robust, scaleable environment, managing and monitoring key IT resources and business metrics, and doing all of these lifecycle steps while adhering to solid governance and best practices.
SOA Reference Archictecture - SOA Reference Architecture defines the comprehensive IT services required to support your SOA at each stage in the SOA life cycle.
SOA Scenarios - SOA Scenarios define specific SOA projects customers can implement while focusing on a very small number of targeted software products and/or services per project.
Virtualization - Virtualization supports SOA projects by enabling IT infrastructure to be dynamic and responsive, supporting scaling of services in support of business processes, and improving performance and service level attainment of SOA deployments by implementing intelligent service workload management techniques.
Web 2.0 - Web 2.0 encompasses a range of technologies, tools, techniques and standards which focus on enabling people to increase the social factor - how people connect with each other to improve how software works. Key principles involve use of lightweight programming models and standards, and techniques such as mash-ups, wikis, tagging and blogs for richer user interfaces and improved use of data.
Web services - A Web service is a software system designed to support interoperable machine-to-machine interaction over a network. It has an interface described in a machine-processable format (specifically WSDL). Other systems interact with the Web service in a manner prescribed by its description using SOAP messages, typically conveyed using HTTP with an XML serialization in conjunction with other Web-related standards.