|
|
|
|
|
|
Glossary
adapter
A software component that provides an interface between an enterprise information system and an integration server.
application adapter
A software component that provides an interface between an enterprise information system and an integration server.
application server
Servers that provide not only for the sharing and processing of application logic, but also the connections to back-end resources. These resources include databases, ERP applications, and even traditional mainframe applications. Application servers also provide user interface development mechanisms. Additionally, they usually provide mechanisms to deploy the application to the platform of the Web.
application view
The application view represents a business-level interface to the specific functionality in an application. An adapter represents a system-level interface to all the functionality in the application. An application view is configured for a single business purpose and contains only the services related to that business purpose. These services require only business-relevant data to be specified in the request document and return only business-relevant data in the response document. Under the covers, the application view combines this business-relevant data with stored metadata necessary for the adapter. The adapter takes both the busines-relevant data and the stored metadata and executes a system-level function on the application.
In addition, the application view represents both events and services that support a business purpose. This allows the business user to interact with the application view for all communication with an application. This bidirectional communication is actually supported by two adapter components (the event adapter and service adapter). The application view abstracts this fact from the user and presents them with a unified business interface to the application.
Enterprise Information System (EIS)
An enterprise information system is a software system that provides the information infrastructure for an enterprise. An EIS offers a set of services to its clients. These services are exposed to clients as local and/or remote interfaces. Examples of an EIS include:ERP System, e.g. SAP R/3, PeopleSoft Mainframe transaction processing system, e.g. CICS Legacy database system, e.g. Oracle
BizTalk
BizTalkTM is an industry initiative started by Microsoft and supported by a wide range of organizations, from technology vendors like SAP, CommerceOne, and Ariba to technology users like BASDA. BizTalk is not a standards body. Instead, we are a community of standards users, with the goal of driving the rapid, consistent adoption of XML to enable electronic commerce and application integration. We are defining the BizTalk Framework, a set of guidelines for how to publish schemas in XML and how to use XML messages to easily integrate software programs together in order to build rich new solutions. Our design emphasis is to leverage what you have today - your existing data models, solutions, and application infrastructure - and adapt it for electronic commerce through the use of XML. [http://www.biztalk.org]
business-to-business Integration
Inter-enterprise application integration that includes supply chain integration between enterprises.
Business-to-consumer Integration
is the process of exposing information within your enterprise to people or entities, known and unknown, that exist outside of your enterprise [Linthicum 2000, p. 17]
client connector interface (CCI)
An interface that allows a J2EE-based application to connect to and access back-end systems. The CCI manages the flow of data between the client application and the back-end system and does not have any visibility into what either the container or the application server are doing with the adapter.
E-business
The practice of using electronic mechanisms to conduct business between your trading partners and your customers [Linthicum 2000, p. 17]
E-commerce
Conducting business electronically.
EDI
See Electronic Data Interchange
EIS
See Enterprise Information System
Electronic Data Interchange (EDI)
A standard for sharing information between trading partners in support of supply chain integration. [Linthicum 2000, p. 354]
Enterprise Application Integration (EAI)
The unrestricted sharing of information between two or more enterprise applications. A set of technologies that allow the movement and exchange of information between processes within and between organizations. [Linthicum 2000, p. 354]
Enterprise Information System (EIS)
An enterprise information system is a software system that provides the information infrastructure for an enterprise. An EIS offers a set of services to its clients. These services are exposed to clients as local and/or remote interfaces. Examples of an EIS include:
Enterprise JavaBeans (EJB)
A component architecture for the development and deployment of object-oriented, distributed, enterprise-level applications. Applications written using the Enterprise JavaBeans architecture are scalable, transactional, and secure.
event
An event is something that happens within some system (generally an EIS). This event, if it is deemed to be of interest to some external party, will cause the generation of an event object that will be delivered to interested parties as part of an event notification.
event notification
A one-way asynchronous notification of an event within some system (generally an EIS). An event notification is achieved by delivering an event object representing the event to a subscriber for that type of event.
event object
A data object the represents an event within some system (generally an EIS). Event objects generally contain data sufficient to describe the event and the context in which it occurred. Event objects are often referred to simply as events. This is because event objects are the only representation of an event possible after the event has passed, and thus are the lasting outcome of an event. An event object has a type that is a name used to refer to all events with the same cause. An event object contains an XML document that contains the data for the event.
event object
A data object represents an event within some system (generally an EIS). Event objects generally contain data sufficient to describe the event and the context in which it occurred. Event objects are often referred to simply as events. This is because event objects are the only representation of an event possible after the event has passed, and thus are the lasting outcome of an event. An event object has a type that is a name used to refer to all events with the same cause. An event object contains an XML document that contains the data for the event.
Extensible Markup Language (XML)
A text-processing standard defined by the World Wide Web Consortium (W3C). XML is a text-based markup language for crafting structured documents. For more information regarding XML, see: http://www.w3c.org.
FIX
The Financial Information Exchange (FIX) protocol is a messaging standard developed specifically for the real-time electronic exchange of securities transactions [Linthicum 2000, p. 54
HTML
See Hypertext Markup Language
Hypertext Markup Language (HTML)
The set of markup symbols inserted in a file intended for display on a World Wide Web browser. The markup instructs the Web browser how to display the page. [Linthicum 2000, p. 355]
i18n - Internationalization
The ability to easily tailor an application to the local customs and languages of specific locales, without recompilation or use of different binaries.
interaction specification
A static XML document that contains secondary metadata about a service; for example, for a DBMS service adapter, the interaction spec would contain the SQL statement used to invoke a process on the database.
Internet
The worldwide distributed network of computer networks that communicate via the TCP/IP protocols.
J2EE
See Java 2 Enterprise Edition
J2EE-CA
See Java 2 Enterprise Edition Connector Architecture
Java 2 Enterprise Edition (J2EE)
The Java TM 2 Platform, Enterprise Edition (J2EE) defines the standard for developing multitier enterprise applications. J2EE simplifies enterprise applications by basing them on standardized, modular components, by providing a complete set of services to those components, and by handling many details of application behavior automatically, without complex programming. [http://java.sun.com/j2ee/overview.html]
Java 2 Enterprise Edition Connector Architecture (J2EE-CA)
The J2EE Connector architecture provides a Java solution to the problem of connectivity between the many application servers and EISs already in existence. By using the J2EE Connector architecture, EIS vendors no longer need to customize their product for each application server. Application server vendors who conform to the J2EE Connector architecture do not need to add custom code whenever they want to add connectivity to a new EIS. The J2EE Connector architecture is based on the technologies that are defined and standardized as part of the Java 2 Platform, Enterprise Edition (J2EE). The J2EE Connector architecture is proposed to be part of version 1.3 of the J2EE platform. [http://java.sun.com/j2ee/connector/]
Java Authentication and Authorization Service (JAAS)
The JavaTM Authentication and Authorization Service (JAAS) is a Java package that enables services to authenticate and enforce access controls upon users.
Java Message Service (JMS)
A standard application programming interface (API) and provider framework that enables the development of portable, message-based applications in the Java programming language.
JavaTM Transaction API (JTA)
An API that allows applications and J2EE servers to access transactions.
JavaTM Transaction Service (JTS)
Specifies the implementation of a transaction manager which supports JTA and implements the Java mapping of the OMG Object Transaction Service (OTS) 1.1 specification at the level below the API.
JCA - J2EE Java Connector Architecture
The J2EE Connector Architecture defines a standard architecture for connecting the Java 2 Platform, Enterprise Edition (J2EE) platform to heterogeneous EISs. The JCA defines a set of functionality that application server vendors must provide and which back-end system vendors (e.g., SAP, PeopleSoft, Siebel, Oracle and/or third-party connector developers) can use to plug into J2EE.
The architecture does not specify how this capability is implemented — that is up to the platform provider or the connector developer. The JCA has two basic components, the Common Client Interface (CCI) and a set of system-specific services. An adapter developer provides an interface to CCI along with its side of the system contracts specified as part of the connector architecture. The application server vendor implements its side of the system contracts as part of its base J2EE platform.
Joy
A user interface toolkit developed by BEA Systems, Inc. that takes XML documents as input and creates an application's graphical user interface from the documents' content. Joy allows for the construction of extensible and highly customizable user interfaces as evidenced by the WLAI Integrated Development Environment, which incorporates the WebLogic Process Integrator Studio user interface. For more information on Joy, see [Carroll 2000].
JSP - Java Server Page
Part of the J2EE which extends the Servlet class, which allows for rapid server-side development of HTML interfaces co-mingled with Java
l10n - Localization
The application of the principles of internationalization to remove hard-coded values (for items such as text, numbers, icons, etc.) from source code, and replace them with resource bundles which provide appropriate versions for specific locales.
Legacy application
"Stovepipe" applications that might exist with many other stovepipe applications in a centralized environment. While mainframes continue to make up the majority of traditional systems, minicomputers and even large UNIX systems may also correctly be called [legacy applications] [Linthicum 2000, p. 12] Legacy applications include an enterprise's internally developed applications.
packaged application
Any type of application that is purchased rather than developed. These applications contain reusable business processes that represent best-of-breed business models and don't require a full-scale development effort. [Linthicum 2000, pp. 13-14]
resource adapter
A resource adapter (also referred to as an "adapter") is a system-level software driver used by an application server or an application client to connect to an EIS. [http://java.sun.com/j2ee/connector]
RosettaNet
RosettaNet is an independent, self-funded, non-profit consortium dedicated to the development and deployment of standard electronic business interfaces to align the processes between supply chain partners on a global basis. Launched in June 1998, RosettaNet is currently in the pilot phase of its implementation cycle. More than 200 companies representing $1 trillion in annual information technology and electronic component revenues currently participate in RosettaNet's standards development, strategy and implementation activities. [www.rosettanet.or]
security realm
A component of the WebLogic Server that contains user, role, and organization information.
service
A named business function representing functionality within an EIS, implemented in terms of interactions provided by the adapter for the EIS. Services provide a two-way synchronous or asynchronous communication mechanism to an EIS.
service provider interface
The Service Provider Interface (SPI) contains the objects that provide and manage connectivity to the EIS, establish transaction demarcation, and provide a framework for event listening and request transmission. All J2EE Connector Architecture-compliant adapters must provide an implementation for these interfaces in the javax.resource.spi package.
servlet
A Java program that extends the functionality of a Web server, generating dynamic content and interacting with Web clients using a request-response paradigm.
SWIFT
SWIFT (Society for Worldwide Interbank Financial Telecommunications) is the industry-owned co-operative supplying secure global messaging services and interface software to close to 7,000 financial institutions in more than 190 countries. (http://www.swift.com)
transaction
An atomic unit of work that modifies data. A transaction encloses one or more program statements, all of which either complete or roll back. Transactions enable multiple users to access the same data concurrently.
WebLogic Application Integration (WLAI)
A JCA standards-based integration broker developed by BEA Systems for inter- and intra-enterprise integration.
WebLogic Server (WLS)
BEA's award-winning, J2EE-compliant application server.
WLAI
See WebLogic Application Integration
WLS
See WebLogic Server
World Wide Web (WWW, W3, W 3 )
A worldwide network of computers that serve hypertext information primarily through the HTTP protocol.
XML
See Extensible Markup Language
XML Schema
XML Schemas express shared vocabularies and allow machines to carry out rules made by people. They provide a means for defining the structure, content and semantics of XML documents. [http://www.w3.org/XML/Schem]
XSLT
a language for transforming XML documents into other XML documents. XSLT is designed for use as part of XSL, which is a stylesheet language for XML. In addition to XSLT, XSL includes an XML vocabulary for specifying formatting. XSL specifies the styling of an XML document by using XSLT to describe how the document is transformed into another XML document that uses the formatting vocabulary. [http://www.w3.org/TR/xsltl].
|
|
|
|
|
|
Copyright © 2001 BEA Systems, Inc. All rights reserved.
|