|
Term |
Definition |
|
A basic unit of work that performs a specific function. | |
|
The Unwired Orchestrator Agent is a daemon that provides administrative, packaging, and deployment services to the graphical user interface. Each server machine hosts a single Agent process that manages the servers and runtime instances on that machine. It retrieves configuration information from a central UDDI registry and from a design-time repository. The Agent acts as a proxy for the Command and Control interface, handles runtime instance configuration and file system management tasks, and invokes the various metadata translators required by the deployment process. | |
|
During deployment, the process that links the logical endpoints of an orchestration project to its physical resources. | |
|
The runtime instance document that contains the user-defined bindings between the logical design endpoints and the physical resources on a runtime server. | |
|
Business Process Modeling Language; see http://www.bpmi.org/ | |
|
Business Process Specification Schema defines how two trading partners collaborate and transact to each other. BPSS uses ebXML language. | |
|
A collection of activities or events constituting a specific business function. | |
|
When exposing a business process as a Web service, this term refers to the portion of a business process that provides the functionality for a Request or Request-Reply type web service. Specific requirements for the business process are defined in Characteristics of a Business Process that can be Used as a Web Service. | |
|
A directive, policy, or procedure in an organization. Business rules represent conditional logic at the activity level. | |
|
The graphical user interface (GUI) of an editor on which business processes and elements of business processes are created, maintained, and viewed. | |
|
|
A group of entries in the Directory that share a common quality. Categories are used to organize the contents of the Directory. |
|
Consistency and completeness verification. | |
|
Clustering is a server architecture that emulates multiprocessing by connecting two or more computers in such a way that they behave like a single computer. Clustering is used for failover (fault tolerance) and distribution (parallel processing and load balancing). In Unwired Orchestrator, these multiprocessing rings operate in one of two modes: failover or distributed. | |
|
An interface that provides users the ability to control server functions. Using Command and Control, the server can be stopped, started, and queried to determine its current state. | |
|
A composite of activities or other complex activities with drill-down capability. | |
|
A business process-specific property that represents the runtime environment. | |
|
A set of data with values having predefined characteristics. Examples of data types are integer, floating point unit number, character, string, and complex. | |
|
The process of transferring a design-time instance to a runtime instance. | |
|
The process of transferring application metadata from a design-time environment to a runtime environment. | |
|
See parse. | |
|
A series of activities, such as defining rules, service interaction, schemas, and transformations of schemas, that provide the logical foundation of a business process project. | |
|
The directory contains information used across multiple projects to perform a variety of activities. Users interact with the Directory through special-purpose browsers built into the tooling. | |
|
Distribution spreads the workload among multiple servers to avoid having some servers idle while others have tasks queuing for execution. Distribution also allows for parallel processing. | |
|
Drag and Drop is the action of selecting a GUI item by holding the left mouse button down, dragging the cursor to the destination by moving the mouse, and dropping the item by releasing the left mouse button. Section 508 compliancy recommends using the Control key as a substitute for the left mouse button hold, and the arrow keys for the drag. | |
|
See schema. | |
|
Dynamic-link library. | |
|
Document Type Definition is a set of rules that define the schema of XML. | |
|
Electronic Business using eXtensible Markup Language. A standard method to exchange business messages, conduct trading relationships, communicate data in common terms and define and register business processes. ebXML is the language used in the Business Process Specification Schema (BPSS). | |
|
The view used to browse, edit, or input documents or objects. | |
|
Event Definition Language is a proprietary New Era of Networks representation of runtime business process definition language. | |
|
EventId. | |
|
Failover is the implementation of mirrored servers that automatically switch to a clone upon the failure or abnormal termination of the engine. After being configured, failover happens without human intervention. | |
|
A resource editor contained within another editor, for example, a rule builder. | |
|
The people, process, and software involved in consumption and production of information essential to a business process. This includes applications, processes, or other systems from which your business process gets information or to which your business process sends information. Database, Messaging, Engine Cluster, and Web Services are types of endpoints. Endpoint connections are administered in the Endpoint Manager. Services, such as database services, messaging services and replication event services, require an endpoint. | |
|
A component of an endpoint. The endpoint connection is configured using parameters associated with the endpoint type to facilitate the actual connection to the physical external system. For example, for a database endpoint, the database endpoint connection defines the database name, server, user id and password parameters that facilitate the connection to the physical database. Endpoint connections are administered in the Endpoint Manager. | |
|
A component architecture for the development and deployment of object-oriented, distributed, transactional, enterprise-level applications. This architecture separates low-level details from business logic. | |
|
An inbound message. The arrival of a document or a notification within a business process are examples of an event. | |
|
Graphical Editing Framework. GEF is an IBM Eclipse Platform plug-in enabling diagramming environment programming, similar to Microsofts Visio design tool palette. | |
|
GEF Extension Libraries. | |
|
Graphical Editing Manager for GEF. | |
|
Health Level Seven is one of several ANSI-accredited Standards Developing Organizations (SDOs) operating in the healthcare industry. Most SDOs produce standards (sometimes called specifications or protocols) for a particular healthcare domain such as pharmacy, medical devices, imaging or insurance (claims processing) transactions. Health Level Sevens domain is clinical and administrative data with focus on the interface requirements of the entire health care organization. | |
|
Internationalization. The process of producing a product free of any dependency on a particular locale or coded character set. | |
|
A single copy of an object or running program. Multiple instances of a program mean that the program has been loaded into memory several times. All instances of that object or program share the same copy of its contents. | |
|
Java 2 Enterprise Edition. An environment standard for developing and deploying enterprise applications. The J2EE platform consists of a set of services, application programming interfaces (APIs), and protocols that provide the functionality for developing multi-tiered, web-based applications. | |
|
J2EE Connector Architecture. | |
|
Java Database Connectivity is a Java API that enables Java programs to execute SQL statements. JDBC makes it possible to write a single database application that can run on different platforms and interact with different DBMSs. | |
|
Localization. The process of adapting an internationalized product to a specific locale. | |
|
A repository that uses the lightweight Directory Access Protocol to store user-specific information. | |
|
One or more resources that represent either a business process or components of a business process. These resources are devoid (as much as possible) of any physical attributes. Physical attributes are applied only to the logical model during deployment. | |
|
The transformation of one or more document instances to other document instances based on schema. | |
|
Multi-byte character set. | |
|
Message driven bean. A message driven bean consumes asynchronous messages generated by a client. A message consumer that implements some business logic. The bean registers interest in a queue or topic of its choice, implements the MessageListener interface, and waits for the arrival of asynchronous messages. | |
|
The exchange of documents within and between applications. | |
|
Definitional data that provides information about other data managed within an application. The information that describes each component of an enterprise information system. Metadata is documented information (not raw statistics) about data, processes, and systematic functions. | |
|
Used for a chain of conditions that must be evaluated in a specified order. Evaluation of a multi-rule results in a single outbound path. | |
|
A hierarchical view of resources. | |
|
The storage of data or object information in volatile memory; a database is not used to track information on data or objects. Messages from non-persistent queues cannot be recovered in cases when the queue manager cycles. Contrast with persistence. Compare with non-persist mode. | |
|
A processing mode used by the runtime engine that stores data or information in memory only during processing. A business process that expects only a single instance of one event, or message type, runs in non-persist mode. When processing completes, it results in a commit to complete the transaction, or error that results in a rollback. A rollback in this case pushes the message back to the input transport. Compare with persist mode. | |
|
In a schema, non-terminal elements are parent elements that do have element children. See terminal element. | |
|
A messaging service that sends a message to a client but does not expect a reply. | |
|
Open database management system is a standard database access method developed by Microsoft Corporation. The goal of ODBC is to make it possible to access any data from any application, regardless of which database management system (DBMS) is handling the data. | |
|
An abstract description of a function including the messages it consumes or produces. An operation definition is part of a port type for a service and indicates whether the port will send a document, receive a document, or both, and an abstract description of the business documents to be exchanged. | |
|
The metadata associated with a business process that the engine uses at runtime. | |
|
The transformation of formatted data into an object that is used by the runtime engine. See serialization. | |
|
A programming or system property where created objects and variables continue to exist and retain their values between runs of the program. For system processing, this can be the database storage of data or object information for later use. For queues, persistence allows the messages to be 'kept' between queue or queue manager life cycles. Contrast with non-persistence. Compare with persist mode. References to persist and persistent describe the use of database storage and queues. References to persistent mode or non-persistent mode describe the method of processing used by the runtime engine. | |
|
A processing mode used by the runtime engine that stores data and object information to a database for use throughout the business process life cycle. A business process that expects multiple events, or messages, and uses information from each message it expects to receive, runs in persist mode. With persistent storage, full recoverability at any stage of the business process life cycle is guaranteed. Compare with non-persist mode. | |
|
The arrangement of views and editors in Unwired Orchestrator. A perspective provides the interface to tools associated with accomplishing a specific type of task. Examples of perspectives for Unwired Orchestrator include: Orchestration Design, Orchestration Administration, and Orchestration Services. | |
|
An instance of a logical model with sufficient information that can be run at a service location. Both the layout and structure of the enterprise network and installed services, as well as properties of these services, such as queue names or transports. | |
|
ProcessID. | |
|
The network address at which specific operations are available. A port associates operations with specific endpoints. | |
|
A collection of operations in a service. Added to a service to hold one or more operations, a port type is associated with a port. | |
|
The top level of the orchestrator hierarchy. Projects contain resources that make up one or more business processes. | |
|
The characteristics of an object or the attributes associated with a data structure. | |
|
A location where documents are temporarily stored for communication within and between applications. | |
|
In a schema, repeating source and target elements have defined cardinality. To be a repeating element, maxOccurs must have a value greater than one. | |
|
Any component used to build a business process in UnwiredOrchestration. Resources are displayed in the Orchestration Navigator, for example, a project, business process, service, map, or rule set. | |
|
A logical expression, for example, a > 5. | |
|
A collection of rules that can have multiple true conditions, but only one false condition. Every rule in a rule set is evaluated. | |
|
The phase in which a software product is actively processing. Before a software product can be in a runtime state, it must contain the necessary configuration and metadata, which are done at design time. | |
|
The logical environment containing the metadata and configuration necessary for processing documents. A runtime instance is a single instance of the runtime engine and hosts business processes that can be executed in the runtime environment. Runtime instances are administered from the Server Explorer in the Administration perspective. Runtime instance and server instance terms are used interchangeably. | |
|
The machine that contains one or more runtime instances. | |
|
The definition of the organization, content, and semantics of a document. | |
|
The in-memory transformation of objects into streams of formatted data for the purpose of moving the information between locations. See parse. | |
|
server instance |
See runtime instance. |
|
Self-describing application modules that provide access to business logic and data in networked software components. All endpoints are modeled as services by using WSDL documents that contain a set of operations and can be used in a business process. | |
|
A specific example of a self-describing application module encapsulating access to business logic and data in networked software components. Service instance definitions provide documentation for distributed systems and provide models for automating the details involved in communicating between application modules. | |
|
An Unwired Orchestrator object that models the use of a specific operation within a business process. | |
|
A collection of attributes that can be used to connect to a transport. A session contains connectivity information to the underlying transport implementation. | |
|
Simple Object Access Protocol is a lightweight XML-based messaging protocol used to encode the information in Web service request and response messages before sending them over a network. SOAP messages are independent of any operating system or protocol and may be transported using a variety of Internet protocols, including SMTP, MIME, and HTTP. For additional information, see http://www.w3.org. | |
|
Schema Object Model. This is a UML object model that defines an object structure for XML schema. | |
|
In a schema, terminal elements are nodes that have data to be translated and no children. Contrast with non-terminal element. | |
|
A means of conveying documents. A transport is a named location used for exchanging business documents with messaging-enabled applications. | |
|
Universal Description, Discovery, and Integration. This provides a platform-independent framework to find and register services and is used to support the URL (Uniform Resource Locator) for the repository connection. UDDI is similar to a traditional phone book's yellow and white pages for Web Services. The UDDI registry stores descriptions about companies and the services they offer in a common XML format so their services can be discovered by others WSDL is an integral part of UDDI, an XML-based worldwide business registry. | |
|
Universal Unique Identifier is a 128-bit number assigned to any object within a DCE cell, which is guaranteed to be unique. The mechanism that is used to guarantee that UUIDs are unique is through combination of hardware addresses, time stamps and random seeds. | |
|
Version Control Module is the Eclipse abstraction layer to a source control system. | |
|
A pane within a perspective. A view provides ways to navigate and work with Unwired Orchestrator information. | |
|
World Wide Web Consortium; see http://www.w3.org. | |
|
A software resource that initiates and responds to service requests and that can be discovered and run over the Internet using agreed-upon standards such as XML, SOAP, and WSDL. | |
|
Description of the physical structure of a message, including such components as delimiters, tags, and datatypes. | |
|
A container for document objects to be worked on or deployed together. | |
|
A collection of projects that can be imported into the navigator. The projects are located in a Workspace folder on the hard drive. | |
|
Web Services Description Language is a general purpose XML language for describing interface, protocol bindings, and deployment details of network services. As an XML-formatted language, WSDL is used to describe a Web Service's capabilities as collections of communication endpoints capable of exchanging messages. The WSDL details the service's available methods and parameters types as well as the actual SOAP endpoint for the service. WSDL is the language used by UDDI. For more information, see http://www.w3.org. | |
|
Extensible Markup Language is a standardized meta-language used to allow easy interchange of documents. It provides a syntactic system for describing metadata, allowing you to define the tags (markup) needed to identify the content, data, and text, in XML documents.. | |
|
A message or file encoded using XML production rules. XML documents typically have content (or data), which conforms to a particular content model or schema. The content model may travel with the data content as a doctype but most often valid structure for documents of a particular type or class is provided by an external content model or schema such as DTD, XSD, or XDR based syntax. | |
|
XML Schema Definition is a document that defines the content of an XML document. | |
|
Extensible Stylesheet Language Transformation is an XML-based language for translating one set of XML into another set of XML, HTML, or plain text. This is especially beneficial for web-based messages where the same data need to be converted into different representations of XML, since not all companies use the same programs, applications, and computer systems. |