This glossary includes terms and definitions for WebSphere Business Modeler, WebSphere Integration Developer, WebSphere Business Monitor, WebSphere Process Server for Multiplatforms, WebSphere Process Server for z/OS, WebSphere Enterprise Service Bus, WebSphere Enterprise Service Bus for z/OS, WebSphere Application Server, WebSphere Business Services Fabric, WebSphere Adapters, WebSphere Portal, WebSphere B2B, WebSphere Service Registry and Repository, WebSphere Business Integration for Financial Networks, WebSphere Business Events, WebSphere DataPower, WebSphere Extended Deployment, WebSphere Virtual Enterprise, WebSphere eXtreme Scale, WebSphere Extended Deployment Compute Grid, and WebSphere Business Compass.
To view glossaries for other IBM products, go to www.ibm.com/software/globalization/terminology.
1. A Lucent Technologies switch.
2. The ISDN protocol implemented on the 5ESS switch, providing 23 B-channels and a D-channel over a T1 trunk.
1. See application connectivity link.
2. See access control list.
1. A business process that is generated in response to the processing of an event.
2. A series of processing steps, such as document validation and transformation.
3. An activity that is run on a transition.
4. In a business rule, the event that results from the evaluation of the condition.
1. A unit of work or a building block that performs a specific, discrete programmatic task. See also task.
2. An element of a process, such as a task, a subprocess, a loop, or a decision. Activities are represented as nodes in process diagrams.
1. An added descriptive comment or explanatory note.
2. In speech recognition, an alphanumeric string used to mark a grammar when it is defined. When the grammar is used in an application, both the word and the alphanumeric string are returned to the application.
1. See automatic restart manager.
2. See Application Response Measurement.
1. A concept in the meta-model that is used to specify a policy requirement and evaluating endpoints at run time. An assertion is also used to describe the capabilities of an endpoint.
2. A logical expression specifying a program state that must exist or a set of conditions that program variables must satisfy at a particular point during program execution.
1. For XML documents, the linkage of the document itself to the rules that govern its structure, which might be defined by a Document Type Definition (DTD) or an XML schema.
2. In enterprise beans, a relationship that exists between two container-managed persistence (CMP) entity beans. There are two types of association: one-to-one and one-to-many.
1. A characteristic or trait of an entity that describes the entity; for example, the telephone number of an employee is one of the employee attributes. See also entity, identity.
2. A property, quality, or characteristic whose value contributes to the specification of an element or program function. For example, "cost" or "location" are attributes that can be assigned to a resource.
3. In markup languages such as SGML, XML, and HTML, a name-value pair within a tagged element that modifies features of the element.
1. In computer security, the right granted to a user to communicate with or make use of a computer system.
2. The process of granting a user, system, or process either complete or restricted access to an object, resource, or function.
1. The condition allowing users to access and use their applications and data.
2. The time periods during which a resource is accessible. For example, a contractor might have an availability of 9 AM to 5 PM every weekday, and 9 AM to 3 PM on Saturdays.
1. In process modeling, a distinct path leading to or originating from an element in a process model.
2. In the CVS team development environment, a separate line of development where changes can be isolated. When a programmer changes files on a branch, those changes do not appear on the main trunk or other branches.
1. A significant occurrence in a business process, generally identified by a business analyst, that warrants monitoring over time to reveal a key performance indicator (KPI).
2. An event that occurs during a business process.
1. A group of managed processes that are federated to the same deployment manager and can include high-availability core groups.
2. One or more processes that each host runtime components. Each has one or more named core groups.
1. A communication path through a chain to an endpoint.
2. A link along which signals can be sent, such as the channel that handles the transfer of data between processor storage and local peripheral equipment. See also trunk.
3. A mode by which a business service is consumed by a subscriber.
4. An entry point to the Web services gateway that carries requests and responses between Web services and the gateway.
1. In WebSphere Voice Server, the system process that manages call flow.
2. The AIX process that executes the logic of the state table; each active caller session has one active channel process.
1. A device used to connect a digital phone line to a multiplexer, a channel bank, or directly to another device producing a digital signal. A CSU performs certain line-conditioning and equalization functions, and responds to loopback commands sent from the central office (CO).
2. An American Telephone and Telegraph (AT&T) unit that is part of the AT&T nonswitched digital data system.
1. A group of application servers that collaborate for the purposes of workload balancing and failover.
2. In high-availability cluster multiprocessing (HACMP), a set of independent systems (called nodes) that are organized into a network for the purpose of sharing resources and communicating with each other.
1. See central office.
2. See configuration object.
1. A reusable object or program that performs a specific function and works with other components and applications.
2. In Eclipse, one or more plug-ins that work together to deliver a discrete set of functions.
1. A test of a situation or state that must be in place in order for a specific action to occur.
2. In a business state machine, an expression that guards the transition and only allows the transition to the next state when and if the incoming operation evaluates to 'True'. Otherwise, the current state is maintained.
1. A servlet that provides a portlet access to external sources of content, for example, a news feed from a Web site of a local television station.
2. In Java EE, a standard extension mechanism for containers to provide connectivity to enterprise information systems (EISs). A connector consists of a resource adapter and application development tools (Sun). See also container.
1. A set of one or more grammars that are enabled and used during a recognition action.
2. An object created for a service request in the business service model. The object contains one or more of the following details of information captured from the metadata: a business process, organization, role, channel, and domain specific information. See also context propagation.
1. A mechanism that bridges a point in a process flow between two or more process instances.
2. A record used with business processes and state machines to allow two partners to initialize a transaction, temporarily suspend an activity, and then recognize each other again when that activity resumes.
3. The relationship, captured in a correlation expression, that describes how an incoming event is matched with one or more monitoring context instances to which it will be delivered.
1. A Java or non-Java process definition that you can define as a part of a health policy action plan.
2. In JSP programming, an action described in a portable manner by a tag library descriptor and a collection of Java classes and imported into a JSP page by a taglib directive. (Sun)
1. A repository of data (for example, a DB2 database) to which the runtime server can connect and retrieve data in order to enhance the event being processed.
2. In JDBC, an interface that provides a logical representation of a pool of connections to a physical data source. Data source objects provide application portability by making it unnecessary to supply information specific to a particular database driver.
3. The means by which an application accesses data from a database.
1. To place files or install software into an operational environment. In Java Platform, Enterprise Edition (Java EE), this involves creating a deployment descriptor suitable to the type of application that is being deployed.
2. To transfer assets from a local development environment into an operational, or runtime, environment.
1. The directory containing the subdirectories and resource files created during customization.
2. The directory where the published server configuration and Web application are located on the machine where the application server is installed.
1. A set of name-value pairs (such as CN=person name and C=country or region) that uniquely identifies an entity in a digital certificate.
2. The name that uniquely identifies an entry in a directory. A distinguished name is made up of attribute:value pairs, separated by commas.
1. A Northern Telecom switch.
2. The custom ISDN protocol implemented on the DMS100 switch, providing 23 B-channels and a D-channel over a T1 trunk.
1. A call transfer method in which the primary and secondary lines remain bridged until a call is completed. See also call transfer.
2. See trombone.
1. A component of a document, such as an EDI, XML, or ROD record. An element can be a simple element or a compound element.
2. In Java development tools, a generic term that can refer to packages, classes, types, interfaces, methods, or fields.
3. In markup languages, a basic unit consisting of a start tag, end tag, associated attributes and their values, and any text that is contained between the two.
1. A JCA application or other client consumer of an event from the enterprise information system.
2. The system that is the origin or destination of a session.
1. An entitlement for an organization to subscribe to a business service.
2. The process of entering and saving user or user group information in a portal.
1. A simple Java class that represents a row in a database table or entry in a map.
2. In markup languages such as XML, a collection of characters that can be referenced as a unit, for example to incorporate often-repeated text or special characters within a document.
1. A change to a state, such as the completion or failure of an operation, business process, or human task, that can trigger a subsequent action, such as persisting the event data to a data repository or invoking another business process.
2. A change to data in an enterprise information system (EIS) that is processed by the adapter and used to deliver business objects from the EIS to the endpoints (applications) that need to be notified of the change.
3. An occurrence of significance to a task or system. Events can include completion or failure of an operation, a user action, or the change in state of a process. See also resource model, receiver.
1. A container for inbound events that enables the user to group events without the overhead of creating a new monitoring context. Event groups are purely a visual construct and are not represented in the monitor model.
2. A set of criteria that is applied to events to identify a subset of those events. The criteria include constraints expressions that define the filter conditions.
1. A file created during the development process for inbound operations that contains the configuration settings for inbound processing.
2. The file containing data that has been exported.
1. A class of objects designated by a specific term or concept; denotation.
2. An element or function not included in the standard language.
3. In Eclipse, the mechanism that a plug-in uses to extend the platform. See also extension point.
1. An area into which a particular category of data or control information is entered.
2. In object-oriented programming, an attribute or data member of a class.
1. A device or program that separates data, signals, or material in accordance with specified criteria. See also servlet filtering.
2. Business logic that is applied to the content of an event to determine whether the event matches certain criteria.
1. A group of data bits, surrounded by a beginning sequence and an ending sequence or other control information.
2. In hypertext markup language (HTML) coding, a subset of the Web browser window.
1. A component of a Voice over Internet Protocol that provides a bridge between VoIP and circuit-switched environments. See also Voice over Internet Protocol.
2. A middleware component that bridges Internet and intranet environments during Web service invocations.
3. An element that controls the splitting and recombining of paths in a process flow.
4. An integration pattern that provides format-independent boundary functions that apply to all incoming messages.
5. See destination.
1. Pertaining to an element that is available to any process in the workspace. A global element appears in the project tree and can be used in multiple processes. Tasks, processes, repositories, and services can be either global (referenced by any process in the project) or local (specific to a single process). See also local.
2. Pertaining to information available to more than one program or subroutine. See also local.
1. A document type definition (DTD) or schema providing a structured format used for successful processing by the trace service.
2. A structured collection of words and phrases bound together by rules. A grammar defines the set of all words, phrases and sentences that might be spoken by a caller and are recognized by the engine. A grammar differs from a vocabulary in that it provides rules that govern the order in which words and phrases can be joined together. See also voice model.
1. A collection of users who can share access authorities for protected resources.
2. A set of related documents within an interchange. An interchange can contain zero to many groups.
3. In places, two or more people who are grouped for membership in a place.
1. Pertaining to a clustered system that is reconfigured when node or daemon failures occur, so that workloads can be redistributed to the remaining nodes in the cluster.
2. The ability of IT services to withstand all outages and continue providing processing capability according to some predefined service level. Covered outages include both planned events, such as maintenance and backups, and unplanned events, such as software failures, hardware failures, power failures, and disasters.
1. A computer that is connected to a network and that provides an access point to that network. The host can be a client, a server, or both a client and server simultaneously. See also server, client.
2. In performance profiling, a machine that owns processes that are being profiled. See also server.
1. In Internet communication, the name given to a computer. The host name might be a fully qualified domain name such as mycomputer.city.company.com, or it might be a specific subname such as mycomputer.
2. The network name for a network adapter on a physical machine in which the node is installed.
1. See HTTP over SSL.
1. In the 3270 terminal services development tool, a field on a screen definition that uniquely identifies the state of the screen. Users can choose which fields will be identifiers when creating recognition profiles.
2. The name of an item in a program written in the Java language.
1. A development artifact that imports a service that is external to a module. See also import file.
2. The point at which an SCA module accesses an external service, (a service outside the SCA module) as if it was local. An import defines interactions between the SCA module and the service provider. An import has a binding and one or more interfaces.
1. A dialog between a terminal and a message processing program using IMS conversational processing facilities. See also conversational processing.
2. In IMS Connector for Java, the dialog between a Java client program and a message processing program.
1. A message flow node that represents a source of messages for a message flow or subflow.
2. The point where a service message from a source enters the request flow.
1. A set of servers that share a common runtime database, plus their corresponding brokers and queue managers.
2. A specific occurrence of an object that belongs to a class. See also object.
1. See Internet Protocol.
2. See intelligent peripheral.
1. A tool that parses the declarations and documentation comments in a set of source files and produces a set of HTML pages describing the classes, inner classes, interfaces, constructors, methods, and fields. (Sun)
2. Pertaining to the tool that parses the declarations and documentation comments in a set of source files and produces a set of HTML pages describing the classes, inner classes, interfaces, constructors, methods, and fields.
1. See Java SE Development Kit.
2. See Java Development Kit.
1. A process element that recombines and synchronizes parallel processing paths after a decision or fork. A join waits for input to arrive at each of its incoming branches before permitting the process to continue.
2. An SQL relational operation in which data can be retrieved from two tables, typically based on a join condition specifying join columns.
3. The configuration on an incoming link that determines the behavior of the link.
1. A button on a keyboard or key pad.
2. A cryptographic mathematical value that is used to digitally sign, verify, encrypt, or decrypt a message. See also private key, public key.
3. Information that characterizes and uniquely identifies the real-world entity that is being tracked by a monitoring context.
1. A collection of model elements, including business items, processes, tasks, resources, and organizations.
2. A project that is used for the development, version management, and organization of shared resources. Only a subset of the artifact types can be created and stored in a library, such as business objects and interfaces. See also project.
1. A protocol that uses cryptography to support security in a distributed environment.
2. An authentication framework that allows single sign-on across a set of Web servers that fall within an Internet domain.
1. Pertaining to a device, file, or system that is accessed directly from a user system, without the use of a communication line. See also remote.
2. Pertaining to an element that is available only in its own process. See also global.
1. A data structure that maps keys to values.
2. A file that defines the transformation between sources and targets.
3. In the EJB development environment, the specification of how the container-managed persistent fields of an enterprise bean correspond to columns in a relational database table or other persistent storage.
1. The act of developing and maintaining a map.
2. The process of transforming data from one format to another.
3. The relationship between fields in different abstractions of event and action objects.
1. A program unit that is discrete and identifiable with respect to compiling, combining with other units, and loading.
2. A software artifact that is used for developing, managing versions, organizing resources, and deploying to the runtime environment.
3. In Java EE programming, a software unit that consists of one or more components of the same container type and one deployment descriptor of that type. Examples include EJB, Web, and application client modules. (Sun) See also project.
1. A facility of the integration test client that listens for requests and responses that flow over the component wires or exports in the modules of a test configuration.
2. In performance profiling, to collect data about an application from the running agents that are associated with that application.
1. A logical grouping of managed servers. See also managed node.
2. Any item on a tree control, including a simple element, compound element, mapping command, comment, or group node.
3. In XML, the smallest unit of valid, complete structure in a document.
4. The fundamental shapes that make up a diagram.
1. A message that contains the event descriptions that are sent to managed resources, Web services and other resources.
2. An occurrence within a process that can trigger an action. Notifications can be used to model conditions of interest to be transmitted from a sender to a (typically unknown) set of interested parties (the receivers).
1. An abstract representation of the fields in an event or action definition.
2. In object-oriented design or programming, a concrete realization (instance) of a class that consists of data and the operations associated with that data. An object contains the instance data that is defined by the class, but the class owns the operations that are associated with the data.
1. In Java programming, a group of types. Packages are declared with the package keyword. (Sun)
2. The wrapper around the document content that defines the format used to transmit a document over the Internet, for example, RNIF, AS1, and AS2.
3. To assemble components into modules and modules into enterprise applications.
1. A route that the flow can take through the activities in a process. There may be several alternative paths.
2. The route through a file system to a specific file.
1. A characteristic of data that is maintained across session boundaries, or of an object that continues to exist after the execution of the program or process that created it, typically in nonvolatile storage such as a database system.
2. In Java EE, the protocol for transferring the state of an entity bean between its instance variables and an underlying database. (Sun)
1. As defined in a Web Services Description Language (WSDL) document, a single endpoint that is defined as a combination of a binding and a network address.
2. In time-slot management, one end of a 64 kbps unidirectional stream which can be attached to the SCBus.
1. See primary rate interface.
2. See primary rate ISDN.
1. An object that uniquely identifies an entity bean of a particular type.
2. In a relational database, a key that uniquely identifies one row of a database table. See also constraint, foreign key.
1. A message processing node that cannot be further subdivided. See also subflow node.
2. A message sent from one process to another.
1. A business object that is contained within other business objects. Private business objects are visible only to the containing business object, thereby making them private. See also business object.
2. In XSD, a business object attribute that defines an anonymous complex type instead of referencing a named complex type.
1. A progressively continuing procedure consisting of a series of controlled activities that are systematically directed toward a particular result or end.
2. The sequence of documents or messages to be exchanged between the Community Managers and participants to run a business transaction.
1. A component of an action that indicates that user input is required for a field before making a transition to an output screen.
2. A message or a displayed symbol that requests information or user action. The user must respond to allow the program to proceed.
3. A program that uses logic to determine dynamically the voice segments to be played as a voice prompt.
1. A server that acts as an intermediary for HTTP Web requests that are hosted by an application or a Web server. A proxy server acts as a surrogate for the content servers in the enterprise.
2. A server that receives requests intended for another server and that acts on behalf of the client (as the client's proxy) to obtain the requested service. A proxy server is often used when the client and the server are incompatible for direct connection. For example, the client is unable to meet the security authentication requirements of the server but should be permitted some services. See also server.
1. In object-oriented programming, pertaining to a class member that is accessible to all classes.
2. In the Java programming language, pertains to a method or variable that can be accessed by elements residing in other classes. (Sun)
1. In UDDI, to advertise a Web service so that other businesses can find it and bind with it. Service providers publish the availability of their services through a registry.
2. To make a Web site public, for example by putting files in a path known to the HTTP server.
1. A key on a telephone key pad.
2. In a window or dialog box, a rectangular control that, when clicked, immediately causes an action to be performed. Push buttons can be labeled with text, graphics, or both. The most familiar push buttons are OK and Cancel.
1. A request for information from a database based on specific conditions: for example, a request for a list of all customers in a customer table whose balances are greater than USD1000.
2. A reusable request for information about one or more model elements
1. In Extensible Markup Language (XML) tools, the condition that exists when all references to items in the XML schema editor or DTD editor are automatically cleaned up when the schema is detected or renamed.
2. The condition that exists when all intended references from data in one column of a table to data in another column of the same or a different table are valid.
1. The process of copying objects from one node in a cluster to one or more other nodes in the cluster, which makes the objects on all the systems identical.
2. The process of maintaining a defined set of data in more than one location. Replication involves copying designated changes for one location (a source) to another (a target) and synchronizing the data in both locations.
1. A discrete asset, for example application suites, applications, business services, interfaces, endpoints, and business events.
2. A facility of a computing system or operating system required by a job, task, or running program. Resources include main storage, input/output devices, the processing unit, data sets, files, libraries, folders, application servers, and control or processing programs.
3. A person, piece of equipment, or material that is used to perform a task or a project. Each resource is a particular occurrence or example of a resource definition.
1. A collection of access rights that can be assigned to a user, group of users, system, service, or application that enable it to carry out certain tasks.
2. A description of a function to be carried out by an individual or bulk resource, and the qualifications required to fulfill the function. In simulation and analysis, the term role is also used to refer to the qualified resources.
3. A job function that identifies the tasks that a user can perform and the resources to which a user has access. A user can be assigned one or more roles.
4. A logical group of principals that provides a set of permissions. Access to operations is controlled by granting access to a role.
5. In a relationship, a role determines the function and participation of entities. Roles capture structure and constraint requirements on participating entities and their manner of participation. For example, in an employment relationship, the roles are employer and employee.
1. A condition that must be satisfied when a business activity is being performed.
2. See interaction block.
1. A specification of the boundary within which system resources can be used.
2. In Web services, a property that identifies the lifetime of the object serving the invocation request.
1. A series of commands, combined in a file, that carry out a particular function when the file is run. Scripts are interpreted as they are run.
2. The logical flow of actions for a 3270 server program.
1. A component that accepts as input a message, and processes the message. For example, a service translates its payload into a different format, or routes it to one of several output queues. Most services are implemented as message flows or primitives.
2. In service-oriented architecture, a unit of work accomplished by an interaction between computing devices.
1. A company or program that provides a business function as a service.
2. Any company that provides services for a fee to its customers, such as telecommunication companies, application service providers, enterprise IT, and Internet service providers.
1. A logical or virtual connection between two stations, software programs, or devices on a network that allows the two elements to communicate and exchange data for the duration of the session. See also transaction.
2. A series of requests to a servlet originating from the same user at the same browser.
3. In Java EE, an object used by a servlet to track user interaction with a Web application across multiple HTTP requests.
1. A character other than a digit, a letter, or one of these characters: $, #, @, ., or _. For example, the following characters are special characters: *, +, and %.
2. A character that is not alphabetic, numeric, or blank. For example, a comma (,) or an asterisk (*).
1. See single system image.
2. See server-side include.
1. A catalog service or container server that is managed from the operating system that starts and stops the server process.
2. A fully operational server that is managed independently of all other servers, using its own administrative console.
1. In a business state machine, one of several discrete individual stages that are organized in sequence to compose a business transaction.
2. One step in the logical sequence of actions that comprises a voice application. See also state table action.
1. A session bean that is a collection of operations. The server can optimize resources by reusing bean instances on every method call.
2. A session bean with no conversational state. All instances of a stateless bean are identical. (Sun) See also session bean, stateful session bean.
1. A line in a state table that is only partially displayed.
2. A small program routine that substitutes for a longer, possibly remote, program. For example, a stub might be a program module that transfers procedure calls (RPCs) and responses between a client and a server. In Web services, a stub is an implementation of a Java interface generated from a Web Services Description Language (WSDL) document.
1. In voice mail, any person who owns a mailbox.
2. The consumer of a business service.
1. A text string attached to any instance of a word in a grammar. A tag can be used to distinguish two occurrences of the same word in a grammar, or to identify more than one word in a grammar as having the same meaning.
2. In UN/EDIFACT EDI Standards, the segment identifier. In export and import, a code that is assigned to each field in the database and used to identify the field in the export file. Such export files are known as tagged files.
1. A value that a Key Performance Indicator (KPI) should achieve, such as "300" or "5 days."
2. The destination for an action or operation.
3. See receiver.
1. A marker used to track the current state of a process instance during a simulation run.
2. A particular message or bit pattern that signifies permission or temporary control to transmit over a network.
1. A process in which all of the data modifications that are made during a transaction are either committed together as a unit or rolled back as a unit.
2. An exchange between two programs that carries out an action or produces a result. An example is the entry of a customer's deposit and the update of the customer's balance. See also conversation, session.
1. A mechanism that detects an occurrence and can cause additional processing in response.
2. In database technology, a program that is automatically called whenever a specified action is performed on a specific table or view.
1. A telephone connection between two central offices or switching devices. In DirectTalk, a trunk refers to 24 or 30 channels carried on the same T1 or E1 digital interface. See also channel.
2. In the CVS team development environment, the main stream of development, also referred to as the HEAD stream.
1. In Java programming, a class or interface.
2. In a WSDL document, an element that contains data type definitions using some type system (such as XSD).
1. See Uniform Communication Standard.
2. See universal character set.
1. A compact string of characters for identifying an abstract or physical resource.
2. A unique address that is used to identify content on the Web, such as a page of text, a video or sound clip, a still or animated image, or a program. The most common form of URI is the Web page address, which is a particular form or subset of URI called a Uniform Resource Locator (URL). A URI typically describes how to access the resource, the computer that contains the resource, and the name of the resource (a file name) on the computer. See also Uniform Resource Name.
1. A self-contained, self-describing modular application that can be published, discovered, and invoked over a network using standard network protocols. Typically, XML is used to tag the data, SOAP is used to transfer the data, WSDL is used for describing the services available, and UDDI is used for listing what services are available. See also SOAP, Universal Description, Discovery, and Integration, Web Services Description Language.
2. An application that performs specific tasks and is accessible through open protocols such as HTTP and SOAP.
1. A connector used to pass control and data from a component or an export to a target.
2. To connect two or more components or cooperative portlets so that they work together. In an application, wiring identifies target services; for portlets changes in the source portlet automatically update the target portlets.
1. A directory on disk that contains all project files, as well as information such as preferences.
2. A temporary repository of configuration information that administrative clients use.
3. In Eclipse, the collection of projects and other resources that the user is currently developing in the workbench. Metadata about these resources resides in a directory on the file system; the resources might reside in the same directory.
1. An alternate and supported interface that hides unsupported data types required by a server object behind a thin intermediate server object.
2. An object that encapsulates and delegates to another object to alter its interface or behavior in some way. (Sun)
1. See XML Schema Definition Language.
2. See XML Schema Infoset Model.
1. See XSL Transformation.