The Service Interface and Integration Area, as illustrated in Figure 11, defines the discovery, interaction and communication technologies joining disparate systems and information providers. Component-based architectures leverage and incorporate Service Interface and Integration specifications to provide interoperability and scalability.
The Service Interface and Integration Categories, Standards, and Specifications are defined below:
4.1 Integration
Integration defines the software services enabling elements of distributed business applications to interoperate. These elements can share function, content, and communications across heterogeneous computing environments. In particular, service integration offers a set of architecture services such as platform and service location transparency, transaction management, basic messaging between two points, and guaranteed message delivery.
4.1.1 Middleware - Middleware increases the flexibility, interoperability, and portability of existing infrastructure by linking or "gluing" two otherwise separate applications.
Remote Procedure Call (RPC) - RPC is a protocol allowing a program on a client computer to invoke a program on a server computer. http://www.faqs.org/rfcs/rfc1831.html
4.1.2 Message-Oriented Middleware (MOM) - Software residing in both sides of the client/server architecture providing support for asynchronous calls, or messages, between applications. Message queues are used to track and store requests waiting for execution by the source application. Messaging allows otherwise complex programming and networking details to be abstracted from the developer. http://www.middleware.org/general/mqm.html
4.1.2.1 IBM Websphere MQ - Software solution providing APIs, queue management, message routing, automatic fail-over, and workload balancing. http://www-3.ibm.com/software/ts/mqseries/
4.1.2.2 Microsoft Message Queue (MSMQ) - Software technology providing synchronous and asynchronous message queueing, routing, and security. http://www.microsoft.com/msmq/
4.1.3 Database Access - Provides access to and across multiple database technologies in a distributed environment. Database Access is provided through the use of native database Application Programming Interfaces (APIs), client-side APIs, or server-side database gateways.
4.1.3.1 PL/SQL - Oracle's procedural extension to industry-standard SQL. http://www.orafaq.org/faqplsql.htm
4.1.3.2 ISQL/w - Microsoft's implementation of ANSI SQL. http://www.microsoft.com/sql/
4.1.3.3 OPEN ANSI SQL/92 (ISO/IEC9075:1992 /ANSI X3.135-1992) - SQL is the information processing industry standard language of relational database management systems (RDMS). ANSI X3.135-1992 (also referred to as SQL-92 and ANSI SQL) is the industry standard for Database Language SQL. This standard promotes the portability and interoperability of database application programs and facilitates maintenance of database systems across heterogeneous data processing environments. SQL-92 provides a standardized way for embedding SQL statements into application development languages. http://www.odbmsfacts.com/articles/sql-92.html
4.1.3.4 NET8 - NET8 (called SQL*NET prior to Oracle8) is Oracle's client/server middleware product that offers transparent connection from client tools to the database, or from one database to another. SQL*Net/ Net8 works across multiple network protocols and operating systems. Previous versions referred to as SQL*Net.
http://www.orafaq.org/faqnet.htm
4.1.4 Transaction Processing Monitor - Software providing synchronous messaging and queuing along with other transaction management services designed to support the efficient processing of high volumes of transactions. Core services include load balancing, rollback/commit, and recovery. Transaction Processing provides cost-effective scalability to applications and database systems by managing and throttling transactions on behalf of the database system.
4.1.5 Object Request Broker (ORB) - A technology enabling distributed objects to communicate and exchange data with remote objects. ORB encapsulates the locality and implementation of the objects, allowing users to develop applications that leverage components by accessing the components interface.
4.1.5.1 CORBA (Common Object Request Broker Architecture) - An architecture that enables objects to communicate with one another regardless of what programming language they were written in or what operating system they're running on. http://www.corba.org
4.1.5.2 COM (Component Object Model) - A software architecture created by Microsoft to design and build component-based applications. COM object capabilities are accessible from exposed interfaces.
http://msdn.microsoft.com/library/default.asp?url=/nhp/Default.asp?contentid=28000520
4.1.5.3 DCOM (Distributed Component Object Model) - An extension of the Component Object Model (COM) that allows COM components to communicate across network boundaries. Traditional COM components can only perform interprocess communication across process boundaries on the same machine.
http://msdn.microsoft.com/library/default.asp?url=/nhp/Default.asp?contentid=28000520
4.1.5.4 COM+ (Component Object Model +) - COM+ is an extension of the COM that provides a runtime and services that are readily used from any programming language or tool, and enables extensive interoperability between components regardless of how they were implemented.
http://msdn.microsoft.com/library/default.asp?url=/nhp/Default.asp?contentid=28000520
4.1.6 Enterprise Application Integration - Refers to the processes and tools specializing in updating and consolidating applications and data within an enterprise. EAI focuses on leveraging existing legacy applications and data sources so that enterprises can add and migrate to current technologies.
4.1.6.1 Business Process Management - This process is responsible for the definition and management of cross-application business processes across the enterprise and/or between enterprises.
4.1.6.2 Application Connectivity - This process provides reusable, non-invasive connectivity with packaged software. This connectivity is provided by uni- or bidirectional adapters.
4.1.6.3 Transformation & Formatting - This process is responsible for the conversion of data, message content, information structure, and syntax to reconcile differences in data amongst multiple systems and data sources.
4.2 Interoperability
Interoperability defines the capabilities of discovering and sharing data and services across disparate systems and vendors.
4.2.1 Data Format / Classification - Defines the structure of a file. There are hundreds of formats, and every application has many different variations (database, word processing, graphics, executable program, etc.). Each format defines its own layout of the data. The file format for text is the simplest.
4.2.1.1 XML (eXtensible Markup Language) - XML has emerged as the standard format for web data, and is beginning to be used as a common data format at all levels of the architecture. Many specialized vocabularies of XML are being developed to support specific Government and Industry functions. http://www.w3.org/XML/
4.2.1.2 XLINK (XML Linking Language) - A language used to modify XML documents to include links, similar to hyperlinks, between resources. XLINK provides richer XML content through advanced linking integration with information resources. http://www.w3.org/TR/xlink/
4.2.1.3 Namespaces - Namespaces are qualified references to URI (Uniform Resource Identifier) resources within XML documents. http://www.w3.org/TR/REC-xml-names/
4.2.1.4 EDI (Electronic Data Interchange) - Defines the structure for transferring data between enterprises. EDI is used mainly used for purchase-related information. ANSI X.12 refers to the approved EDI standards.
http://www.disa.org/
4.2.2 Data Types / Validation - Refers to specifications used in identifying and affirming common structures and processing rules. This technique is referenced and abstracted from the content document or source data.
4.2.2.1 DTD (Document Type Definition) - DTD is used to restrict and maintain the conformance of an XML, HTML, or SGML document. The DTD provides definitions for all tags and attributes within the document and the rules for their usage. Alterations to the document are validated with the referenced DTD.
http://www.w3.org/TR/REC-html40/sgml/dtd.html
4.2.2.2 XML Schema - XML Schemas define the structure, content, rules and vocabulary of an XML document. XML Schemas are useful in automation through embedding processing rules. http://www.w3.org/XML/Schema
4.2.3 Data Transformation - Data Transformation consists of the protocols and languages that change the presentation of data within a graphical user interface or application.
4.2.3.1 XSLT (eXtensible Stylesheet Language Transform) - Transforms XML document from one schema into another. Used for data transformation between systems using different XML schema, or mapping XML to different output devices. http://www.w3.org/Style/XSL/
4.3 Interface
Interface defines the capabilities of communicating, transporting and exchanging information through a common dialog or method. Delivery Channels provide the information to reach the intended destination, whereas Interfaces allow the interaction to occur based on a predetermined framework.
4.3.1 Service Discovery - Defines the method in which applications, systems or web services are registered and discovered.
4.3.1.1 UDDI (Universal Description Discovery and Integration) - UDDI provides a searchable registry of XML Web Services and their associated URLs and WSDL pages. http://www.uddi.org/about.html
4.3.2 Service Description / Interface - Defines the method for publishing the way in which web services or applications can be used.
4.3.2.1 WSDL (Web Services Description Language) - WSDL is an XML based Interface Description Language for describing XML Web Services and how to use them.
http://www.w3.org/TR/wsdl
4.3.2.2 API (Application Program Interface) / Protocol - A language and message format used by an application program to communicate with the operating system or some other control program such as a database management system (DBMS) or communications protocol. APIs are implemented by writing function calls in the program, which provide the linkage to the required subroutine for execution. Thus, an API implies that some program module is available in the computer to perform the operation or that it must be linked into the existing program to perform the tasks.
您对本站有任何意见或建议，请直接与管理员联系
Copyright© 1998-2008 ITCore版权所有. All
rights reserved.