Glossary

Understand the terms that are used in various IBM business process and operational decision management products.

The following cross-references are used in this glossary:
  • See refers you from a term to a preferred synonym, or from an acronym or abbreviation to the defined full form.
  • See also refers you to a related or contrasting term.

To view glossaries for other IBM products, go to www.ibm.com/software/globalization/terminology (opens in new window).

Special Characters

.NET Framework
A Microsoft application development environment that consists of the common language runtime and .NET Framework class library that is designed to provide a consistent programming environment for developing and integrating code pieces. See also common language runtime.

A

A2A
See application to application.
abstract schema
Part of the deployment descriptor for an entity bean that is used to define the bean relationships, persistent fields, or query statements.
abstract test
A component or unit test that is used to test Java interfaces, abstract classes, and superclasses; that cannot be run on its own; and that does not include a test suite. See also component test.
abstract type
A type that can never be instantiated and whose members are exposed only in instances of concrete types that are derived from it.
Abstract Window Toolkit (AWT)
In Java programming, a collection of GUI components that were implemented using native-platform versions of the components. These components provide that subset of functionality which is common to all operating system environments. (Sun) See also Standard Widget Toolkit, Swing Set.
access bean
An enterprise bean wrapper that is typically used by client programs, such as JSP files and servlets. Access beans hide the complexity of using enterprise beans and improve the performance of reading and writing multiple EJB properties.
access control
In computer security, the process of ensuring that users can access only those resources of a computer system for which they are authorized.
access control list (ACL)
In computer security, a list associated with an object that identifies all the subjects that can access the object and their access rights.
access ID
The unique identification of a user used during authorization to determine if access is permitted to the resource.
access intent
Metadata that optimizes and controls the runtime behavior of an entity bean with respect to concurrency control, resource management, and database access strategies.
access intent policy
A grouping of access intents that governs a type of data access pattern for enterprise bean persistence.
accessor
In computer security, an object that uses a resource. Users and groups are accessors.
access point group
A collection of core groups that defines the set of core groups in the same cell or in different cells that communicate with each other.
access privilege
An authority that relates to a request for a type of access to data.
accounting
The process of collecting and reporting information about the use of services to apportion cost.
ACID transaction
A transaction involving multiple resource managers using the two-phase commit process to ensure atomic, consistent, isolated, and durable (ACID) properties.
ACL
See access control list.
action
  1. A series of processing steps, such as document validation and transformation.
  2. An activity that is run on a transition or a transaction. See also processing action.
  3. A business process that is generated in response to the processing of an event or a rule.
Action class
In Struts, the superclass of all action classes.
action column
The action part of a decision table.
action mapping
A Struts configuration file entry that associates an action name with an Action class, a form bean, and a local forward.
action object
A subset of fields in the definition of an action.
action phrase
In the vocabulary, a phrase that specifies an action to be executed. An action phrase corresponds to a method that has no return value in the business object model (BOM).
action rule
  1. A rule in which the action is always performed. See also if-then rule, rule set.
  2. A business rule that can be edited in the rule editor. Action rules, decision tables, and decision trees are different representations of business rules.
action rule template
A partly completed action rule that can be used to create a series of rules with the same structure.
action service
A service that triggers a process or notification to inform users about a situation.
action service handler
An entity that is responsible for the invocation mechanism of one or more action services.
action set
  1. The leaf of a branch in a decision tree. Action sets consist of one or more actions to be carried out when the conditions defined in the rule are met.
  2. In Eclipse, a group of commands that a perspective contributes to the main toolbar and menu bar.
action task
In a rule flow, a task that contains rule action statements. These action statements are executed each time the task is called.
activation
In Java, the process of transferring an enterprise bean from secondary storage to memory. (Sun) See also passivation.
activation condition
A Boolean expression in a node within a business process that specifies when processing is to begin.
active option set
In an option set group, the option set that a new scenario uses or that a scenario in progress switches to, if switching becomes necessary.
active site analytics
The instrumentation of pages with metadata that is embedded in themes and skins to provide data to website analytics and search engine optimization tools.
activity
  1. A unit of work or a building block that performs a specific, discrete task. See also task.
  2. An action designed to achieve a particular business process. An activity is performed on a set of targets on a specific schedule.
  3. A logical unit of work that can be completed by a person or a system while the process runs.
  4. Work that a company or organization performs using business processes. An activity can be atomic or non-atomic (compound). The types of activities that are a part of a process model are process, subprocess, and task.
actuator
A device that causes mechanical motion.
adapter
An intermediary software component that allows two other software components to communicate with one another.
adapter foundation classes (AFC)
A common set of services for all resource adapters. The adapter foundation classes conform to, and extend, the Java 2 Connector Architecture JCA 1.5 specification.
adapter object
An object used in the TX Programming Interface that represents a resource adapter.
Address Resolution Protocol (ARP)
A protocol that dynamically maps an IP address to a network adapter address in a local area network.
ad hoc action
An unplanned action, such as starting an activity or a set of activities, that occurs while a process is running.
ad hoc start event
An event that is triggered by a user's interaction with the process, such as through the process portal. The ad hoc start event requires an active process to be triggered. See also start event.
administrative agent
A program that provides administrative support without requiring a direct connection to a database.
administrator
A person responsible for administrative tasks such as access authorization and content management. Administrators can also grant levels of authority to users.
Advanced Integration service
A service that represents and interacts with a corresponding service in Integration Designer. See also integration service, service.
Advanced Program-to-Program Communication (APPC)
An implementation of the SNA LU 6.2 protocol that allows interconnected systems to communicate and share the processing of programs.
AFC
See adapter foundation classes.
after-image
A business object that contains all of the entity data after changes have been made to it during an update operation. An after-image contains the complete business object rather than only the primary key and those elements that were changed. See also delta business object.
agenda
A logical workspace where rule instances that have conditions matching objects in the working memory are put.
agent
A process that performs an action on behalf of a user or other program without user intervention or on a regular schedule, and reports the results back to the user or program. See also subagent.
aggregate interface
The logical grouping of ethernet interfaces, connected to the same subnet, that provide higher levels of availability and bandwidth from the networking substrate. See also link aggregation.
aggregate metric
A metric that is calculated by finding the average, maximum, minimum, sum, or number of occurrences of an instance metric across multiple runs of a process. Examples of aggregate metrics are an average order amount, a maximum order amount, a minimum order amount, the total order amount, or the number of occurrences of $500 for an order amount. See also measure, metric.
aggregation
The structured collection of data objects for subsequent presentation within a portal.
alarm listener
A type of asynchronous bean that is called when a high-speed transient alarm expires.
alert
A message or other indication that signals an event or an impending event. See also rule.
algorithm mapping
A process by which service providers can define the mapping of Uniform Resource Identifier (URI) algorithms to cryptographic algorithms that are used for XML digital signature and XML encryption.
alias
An assumed or actual association between two data entities, or between a data entity and a pointer.
annotate
To add metadata to an object to describe services and data.
anonymous user
A user who does not use a valid user ID and password to log into a site. See also authenticated user, registered user.
AP
See application program.
APAR
See authorized program analysis report.
API
See application programming interface.
API content model
A model that describes how XML documents, and their extended metadata, are represented.
API stub
A piece of glue code that enables the binder to resolve zRule Execution Server for z/OS API calls that COBOL applications make. For example, HBRBSTUB is an API stub that is used for COBOL applications that run as batch applications and HBRCSTUB is an API stub that is used for COBOL applications that run as CICS applications. See also glue code.
APPC
See Advanced Program-to-Program Communication.
applet
A program that performs a specific task and is typically portable between operating systems. Often written in Java, applets can be downloaded from the Internet and run in a web browser.
applet client
A client that runs within a browser-based Java runtime environment, and is capable of interacting with enterprise beans directly instead of indirectly through a servlet.
appliance
A drop-in network device, including hardware and firmware, that simplifies IT deployment for a specific set of business requirements.
Applicability Statement 2 (AS2)
An EDI protocol for securely exchanging data over the Internet, by using HTTP as a transport.
application
One or more computer programs or software components that provide a function in direct support of a specific business process or processes. See also application server.
application assembly
The process of creating an enterprise archive (EAR) file containing all the files related to an application as well as an Extensible Markup Language (XML) deployment descriptor for the application.
application client
In Java EE, a first-tier client component that runs in its own Java virtual machine. Application clients have access to some Java EE platform APIs, for example JNDI, JDBC, RMI-IIOP, and JMS. (Sun)
application client module
A Java archive (JAR) file that contains a client that accesses a Java application. The Java application runs inside a client container and can connect to remote or client-side Java EE resources.
Application Client project
A structure and hierarchy of folders and files that contain a first-tier client component that runs in its own Java virtual machine.
application delivery notification
A delivery notification that is passed to an application. Typically, an application delivery notification is based on a network delivery notification, but has been modified in some way by the service that exchanges data directly with the application. See also network delivery notification.
application edition
A unique deployment of a particular application. Multiple editions of the same application have the same application name, while edition names are unique.
application edition manager
An autonomic manager that manages interruption-free production application deployments.
application infrastructure virtualization
The pool of application server resources that separates applications from the physical infrastructure on which they run. As a result, workload can be dynamically placed and migrated across the application server pool.
application LT
A logical terminal (LT) that is used by one or more applications, but that is not used for LT sessions.
application placement controller
An autonomic manager that can start and stop application instances on servers to meet the fluctuating demand of work requests and varying service policy definitions.
application policy
A collection of policies and attributes governing access to applications.
application program (AP)
A complete, self-contained program, such as a text editor or a web browser, that performs a specific task for the user, in contrast to system software, such as the operating system kernel, server processes, and program libraries.
application programming interface (API)
An interface that allows an application program that is written in a high-level language to use specific data or functions of the operating system or another program.
Application Response Measurement (ARM)
An application programming interface (API), developed by a group of technology vendors, that can be used to monitor the availability and performance of business transactions within and across diverse applications and systems.
Application Response Measurement agent (ARM agent)
An agent that monitors software that is implemented using the Application Response Measurement standard.
application server
A server program in a distributed network that provides the execution environment for an application program. See also application.
application-specific component
The component of a connector that contains code tailored to a particular application or technology. The application-specific component can respond to requests and implement an event-notification mechanism that detects and responds to events initiated by an application or external programmatic entity.
application-specific information
Part of the metadata of a business object that enables the connector to interact with its application (for example, Ariba Buyer) or a data source (for example, a web servlet). See also metadata.
application to application (A2A)
A data transformation from the output of one application to the input of another application.
application virtualization
The separation of an application from the underlying operating environment, which improves portability, compatibility, and manageability of the application.
area
A representation of the physical space within the location to be monitored. Areas are the container for all zones. See also location.
ARFM
See autonomic request flow manager.
ARM
  1. See automatic restart manager.
  2. See Application Response Measurement.
ARM agent
See Application Response Measurement agent.
ARP
See Address Resolution Protocol.
artifact
  1. An entity that is used or produced by a software development process. Examples of artifacts are models, source files, scripts, and binary executable files.
  2. A graphical object that provides supporting information about the process or elements within the process without directly affecting the semantics of the process.
AS2
See Applicability Statement 2.
aspect-oriented connectivity
A form of connectivity that implements or enforces cross-cutting aspects in service-oriented architecture (SOA), such as security, management, logging, and auditing, by removing such aspects from the concern of the service requesters and providers.
assertion
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.
asset
A collection of artifacts that provide a solution to a specific business problem. Assets can have relationships and variability or extension points to other assets.
assisted lifecycle server
A representation of a server that is created outside of the administrative domain but can be managed in the administrative console.
assistive technology
Hardware or software that is used to increase, maintain, or assist the functional capabilities of people with disabilities.
association
  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. A connecting object that is used to link information and artifacts with flow objects. An association is represented as a dotted graphical line with an arrowhead to represent the direction of flow.
  3. In enterprise beans, a relationship that exists between two container-managed persistence (CMP) entity beans. Two types of association exist: one-to-one and one-to-many.
asymmetric algorithm
See public key algorithm.
asymmetric cryptography
See public key cryptography.
asynchronous
Pertaining to events that are not synchronized in time or do not occur in regular or predictable time intervals.
asynchronous bean
A Java object or an enterprise bean that a Java Platform, Enterprise Edition (Java EE) application can run asynchronously.
asynchronous messaging
A method of communication between programs in which a program places a message on a message queue, then proceeds with its own processing without waiting for a reply to its message.
asynchronous replica
A shard that receives updates after the transaction commits. This method is faster than a synchronous replica, but introduces the possibility of data loss because the asynchronous replica can be several transactions behind the primary shard. See also synchronous replica.
atomic activity
An activity that is not broken down to a finer level of process model detail. It is a leaf in the tree-structure hierarchy of process activities.
attribute
  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.
  4. A set of factors that are used as variables to determine the score of an entity. The value of an attribute can be a natural number, a floating point number, a Boolean value, a character, or a character string. An attribute can be the result of the execution of another rule or a combination of other attributes.
attribute list
A linked list that contains extended information that is used to make authorization decisions. Attribute lists consist of a set of name = value pairs.
audit log
A log file containing a record of system events and responses.
augment
To convert a profile to another kind of profile. For example, a server profile can be modified to become a bus profile. See also unaugment.
authenticated user
A portal user who has logged in to the portal with a valid account (user ID and password). Authenticated users have access to all public places. See also anonymous user, registered user.
authentication
A security service that provides proof that a user of a computer system is genuinely who that person claims to be. Common mechanisms for implementing this service are passwords and digital signatures.
authentication alias
An alias that authorizes access to resource adapters and data sources. An authentication alias contains authentication data, including a user ID and password.
authenticator key
A set of alphanumeric characters used for the authentication of a message sent via the SWIFT network.
authorisation
A document that authorizes one SWIFTNet destination to send messages to or receive messages from another SWIFTNet destination.
authorization
  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.
authorization policy
A policy whose policy target is a business service and whose contract contains one or more assertions that grant permission to run a channel action.
authorization table
A table that contains the role to user or group mapping information that identifies the permitted access of a client to a particular resource.
authorized program analysis report (APAR)
A request for correction of a defect in a supported release of a program supplied by IBM.
automatic application installation project
A monitored directory to which the addition of a fully composed EAR, WAR, EJB JAR, or stand-alone RAR file triggers automatic deployment and publication to a target server. Deletion of an EAR or Java EE module file from this directory triggers automatic uninstalling. See also monitored directory.
automatic restart management
The facilities that detect failures and manage server restarts.
automatic restart manager (ARM)
A z/OS recovery function that can automatically restart batch jobs and started tasks after they or the system on which they are running end unexpectedly.
automatic transition
A transition that occurs on completion of the activity within the originating state.
automatic variable
A variable that a user can declare as an instance of a specific business object model (BOM) class.
autonomic request flow manager (ARFM)
An autonomic manager that controls request prioritization in the on-demand router.
availability
  1. 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.
  2. The condition allowing users to access and use their applications and data.
AWT
See Abstract Window Toolkit.
Axis
An implementation of SOAP on which Java web services can be implemented.

B

B2B
See business-to-business.
B2C
See business-to-consumer.
B2E
See business-to-employee.
BA
See basic authentication.
back-end system
A system in a multisystem environment that accepts transactions from the front-end system, calls application programs for transaction processing, and routes replies back to the front-end system for response to the terminal.
BAL
See Business Action Language.
BAM
See business activity monitoring.
bank identifier code (BIC)
A code used to uniquely identify a bank, logical terminal, or branch within a SWIFT network.
BAPI
See Business Application Programming Interface.
base
The core product, for which features can be separately ordered and installed.
base classes
See adapter foundation classes.
base configuration
The part of a storage management subsystem (SMS) configuration that contains general storage management attributes, such as the default management class, default unit, and default device geometry. It also identifies the systems, system groups, or both the systems and system groups that an SMS configuration manages.
baseline
See snapshot.
base object
An object that defines a common set of attributes; more complex objects are then built from a base object, inheriting the common attribute set.
basic analysis
A type of analysis that displays a report for the values of one or more business measures during a specific period of time.
basic authentication (BA)
An authentication method that uses a user name and a password.
basic type
A type whose values have no identity (that is, they are pure values). Basic types include Integer, Boolean, and Text.
batch application
An application that is implemented as part of a bundle or Java archive file and deployed as an archive file.
batch job
A predefined group of processing actions submitted to the system to be performed with little or no interaction between the user and the system.
bean
A definition or instance of a JavaBeans component. See also enterprise bean, JavaBeans.
bean class
In Enterprise JavaBeans (EJB) programming, a Java class that implements a javax.ejb.EntityBean class or javax.ejb.SessionBean class.
bean-managed messaging
A function of asynchronous messaging that gives an enterprise bean complete control over the messaging infrastructure.
bean-managed persistence (BMP)
The mechanism whereby data transfer between an entity bean's variables and a resource manager is managed by the entity bean. (Sun) See also container-managed persistence.
bean-managed transaction (BMT)
The capability of the session bean, servlet, or application client component to manage its own transactions directly, instead of through a container.
bearer token
A Security Assertion Markup Language (SAML) token that uses the bearer subject confirmation method. In a bearer subject confirmation method, a sender of SOAP messages is not required to establish correspondence that binds a SAML token with contents of the containing SOAP message.
BEL
See Business Events Language.
BIC
See bank identifier code.
bidi
See bidirectional.
bidirectional (bidi)
Pertaining to scripts such as Arabic and Hebrew that generally run from right to left, except for numbers, which run from left to right.
big endian
A format for storage or transmission of binary data in which the most significant value is placed first. See also little endian.
binary format
Representation of a decimal value in which each field must be 2 or 4 bytes long. The sign (+ or -) is in the far left bit of the field, and the number value is in the remaining bits of the field. Positive numbers have a 0 in the sign bit and are in true form. Negative numbers have a 1 in the sign bit and are in twos complement form.
binary large object (BLOB)
A block of bytes of data (for example, the body of a message) that has no discernible meaning, but is treated as one entity that cannot be interpreted.
bind
To establish a connection between software components on a network using an agreed-to protocol. In web services, the bind operation occurs when the service requester invokes or initiates an interaction with the service at run time using the binding details in the service description to locate, contact, and invoke the service.
binding
A temporary association between a client and both an object and a server that exports an interface to the object. A binding is meaningful only to the program that sets it and is represented by a bound handle.
black box
A pool in which no content can be seen.
BLOB
See binary large object.
block decryption
Symmetric algorithms that decrypt a block of data at one time.
block encryption
Symmetric algorithms that encrypt a block of data at one time.
BMP
See bean-managed persistence.
BMT
See bean-managed transaction.
BOM
See business object model.
BOM property
A property added to a type in a business object model (BOM). Business properties extend the original type without altering its source.
BOM-to-XOM mapping
A mechanism that defines how business elements are mapped to the Execution Object Model.
Boolean
Characteristic of an expression or variable that can only have a value of true or false.
boot BOM
A set of files that define the system types, such as string or number, for the Business Action Language (BAL).
bootstrap
A small program that starts a computer by loading the operating system and other basic software.
bootstrap authorisation
An authorization that has been recorded but not yet processed by an relationship management application (RMA).
bootstrap member
An application server or cluster that is configured to accept application initialization requests into the service integration bus. The bootstrap member authenticates the request and directs the connection request to a bus member.
bootstrap period
The period during which relationship management (RM) data is recorded and converted into authorization records.
bootstrapping
The process by which an initial reference of the naming service is obtained. The bootstrap setting and the host name form the initial context for Java Naming and Directory Interface (JNDI) references.
bottleneck
A place in the system where contention for a resource is affecting performance.
bottom-up development
In web services, the process of developing a service from an existing artifact such as JavaBeans or an enterprise bean rather than a Web Services Description Language (WSDL) file. See also top-down development.
bottom-up mapping
In Enterprise JavaBeans (EJB) programming, an approach for mapping enterprise beans to database tables, in which the schema is first imported from an existing database and then enterprise beans and mappings are generated.
boundary event
An intermediate event that is attached to the boundary of an activity. A boundary event can be triggered only while the activity is running, either leaving the activity running or interrupting the activity.
boundary zone
A zone that is used for implementing access control to areas that are not covered by event devices and therefore cannot be controlled completely or directly.
bound component
In the Type Designer, a component for which each occurrence of the data can be identified without considering the context in which that occurrence is placed.
bound type
In the Type Designer, a type whose data object can be identified without considering the context in which that data object is placed.
BPD
See business process definition.
BPEL
See Business Process Execution Language.
BPM
See business process management.
BPML
See Business Process Modeling Language.
BPML activity
A step in a business process that provides directions for how data should be handled.
branch
  1. 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 are not displayed on the main trunk or other branches.
  2. In a rule flow, a node that organizes conditional transitions. Several transitions can go to and from a branch node. All transitions created from a branch must have a condition, except the Else transition.
breadcrumb trail
A navigation technique used in a user interface to give users a way to keep track of their location within the program or documents.
breakpoint
A marked point in a process or programmatic flow that causes that flow to pause when the point is reached, typically to allow debugging or monitoring.
bridge
In the connection of local loops, channels, or rings, the equipment and techniques used to match circuits and to facilitate accurate data transmission. See also web application bridge.
bridge interface
A node and a server that run a core group bridge service.
BRLDF
See Business Rule Language Definition Framework.
BRMS
See business rule management system.
broker archive
A file that is the unit of deployment to the broker that can contain any number of compiled message flow and message set files and a single deployment descriptor. A separate broker archive file is required for each configuration that is deployed.
brokerlist section
A section in a customization definition document (CDD) that describes which BAR files are deployed, which execution group and broker the files are deployed to, and which tuning parameters the files use.
broker topology definition (BTD)
A description of the brokers, execution groups, and broker archive (BAR) files that are used in a runtime environment, and the actions that are required to implement the current broker topology (for example, deploying the BAR files for a new service).
broker topology definition document (BTDD)
An XML document that describes a broker topology definition.
browser
A client program that initiates requests to a web server and displays the information that the server returns.
brute force collision
A programming style that relies on computing power to try all the possibilities with a known hash until the solution is found.
BTD
See broker topology definition.
BTDD
See broker topology definition document.
bucket
One or more fields that accumulate the result of an operation.
build
To create or modify resources, typically based on the state of other resources. A Java builder converts Java source files into executable class files, for example, and a web link builder updates links to files whose name or location has changed.
build definition file
An XML file that identifies components and characteristics for a customized installation package (CIP).
build path
The path that is used during compilation of Java source code to find referenced classes that are located in other projects.
build plan
An XML file that defines the processing necessary to build generation outputs and that specifies the machine where processing takes place.
build time data
Objects that are not used by the translator, such as EDI standards, record oriented data document types, and maps.
bulk decryption
See block decryption.
bulk encryption
See block encryption.
bundle
In the OSGi service platform, a Java archive file that contains Java code, resources, and a manifest that describes the bundle and its dependencies. The bundle is the unit of deployment for an application. See also bundle cache, bundle repository, enterprise bundle archive, subagent.
bundle cache
A cell-wide store, or server-wide store for single-server systems, of bundles that OSGi applications refer to and that have been downloaded from both internal and external repositories. See also bundle, bundle repository.
bundle repository
A common store of OSGi bundles that can be shared by multiple OSGi applications. See also bundle, bundle cache.
bus
Interconnecting messaging engines that manage bus resources.
Business Action Language (BAL)
A business rule language that uses an intuitive and natural language-like syntax for writing business rules.
business activity monitoring (BAM)
The collection and presentation of real-time information that describes a business process or a series of activities spanning multiple systems and applications.
business analyst
  1. A specialist who analyzes business needs and problems, consults with users and stakeholders to identify opportunities for improving business return through information technology, and transforms requirements into a technical form.
  2. A decision management user role that is responsible for modeling rule application projects.
Business Application Programming Interface (BAPI)
A programming interface that is used to access SAP databases from with SAP or other development platforms. BAPI is used to achieve integration between the R/3 System and external applications and legacy systems.
business calendar
A calendar that is used to model noncontiguous time intervals (intervals that do not proceed in a sequential manner). For example, a business calendar that defines regular working hours might refer to the non-overtime regular working hours of Monday to Friday, 9:00 a.m. to 5:00 p.m.
business component
A component that defines the structure, behavior, and information displayed by a particular subject, such as a product, contact, or account, in Siebel Business Applications.
business event
An event that occurs during a business process.
Business Event Language
A business rule language that expresses event rules. See also business rule language.
Business Events Language (BEL)
A business rule language that uses an intuitive and natural language-like syntax for writing event rules.
business graph
A wrapper that is added around a simple business object or a hierarchy of business objects to provide additional capabilities, such as carrying change summary and event summary information related to the business objects in the business graph. See also business object.
business integration system
An integration broker and a set of integration adapters that allow heterogeneous business applications to exchange data through the coordinated transfer of information in the form of business objects.
business logic tier
The set of components that reside between the presentation and database tiers. This logic tier hosts the enterprise bean containers, which run the business logic.
business measure
A description of a performance management characteristic that you want to monitor. Business measures include instance metrics, aggregate metrics (also called measures), and key performance indicators (KPI).
business method
  1. A method of an enterprise bean that implements the business logic or rules of an application. (Sun)
  2. A method added to a type in a business object model. Business methods extend the original type without altering its source.
business object
  1. A software entity that represents a business entity, such as an invoice. A business object includes persistent and nonpersistent attributes, actions that can be performed on the business object, and rules that the business object is governed by. See also binding, business graph, data object, private business object, Service Data Objects.
  2. An abstract representation of the fields that belong to the event and action definitions.
business object map
An artifact that assigns values to the target business objects based on the values in the source business objects.
business object model
  1. A model that defines how a system organizes its processes when interacting with business objects. An example of a business object model is the Enterprise JavaBeans (EJB) component model.
  2. A representation of the core concepts of a business and their logical connections. The business object model is the basis for the vocabulary used in business rules. The elements of a business object model (BOM) map to those of a corresponding execution object model.
business policy
  1. A policy that is attached to an object in the ontology known as the business policy target. It optionally specifies a set of conditions that must be met for the business policy to apply. The policies declare a set of assertions that must be satisfied when the conditions are met.
  2. A set of rules that define business processes, industry practices, or the scope and characteristics of business offerings.
business process
A defined set of business activities that represent the required steps to achieve a business objective. A business process includes the flow and use of information and resources.
business process container
A process engine that contains process modules.
business process definition (BPD)
A reusable model of a process that defines the common aspects of all runtime instances of that process model.
Business Process Execution Language (BPEL)
An XML-based language for the formal specification of business processes and business interaction protocols. BPEL extends the web services interaction model and enables it to support business transactions.
business process management (BPM)
The services and tools that support process management (for example, process analysis, definition, processing, monitoring and administration), including support for human and application-level interaction. BPM tools can eliminate manual processes and automate the routing of requests between departments and applications.
Business Process Modeling Language (BPML)
An XML-based language that describes business processes designed by the Business Process Management Initiative (www.bpmi.org).
business rule
  1. A policy, constraint, or required operation that applies to a specific set of business conditions or dependencies. An example of a business rule for a bank is that a credit check is not required when opening an account for an existing customer.
  2. A representation of how business policies or practices apply to a business activity.
business rule application
An application in which a business policy has been implemented by using business rules.
business rule group
A set of scheduled business rules that are available as a service that can be invoked. The business rule group also provides the organizational structure for managing the set of business rules.
business rule language
A language for expressing rules with natural language terms and syntax. See also Business Event Language.
Business Rule Language Definition Framework (BRLDF)
A framework for defining custom business rule languages, using XML schemas and property files.
business rule management
The practices that control and manage business rules through their life cycles.
business rule management system (BRMS)
A system designed to modify and manage business logic independently from the applications within an organization.
business service
An abstract representation of a business function, hiding the specifics of the function interfaces.
business situation
A condition that might require business action. Examples of business situations are a declining sales volume or an unacceptable amount of time to respond to a customer.
business space
A collection of related web content that conveys insight into the business and gives users the ability to react to changes in the business.
business subtype
A subtype of a type in a business object model (BOM). Business subtypes are used to extend an object model using business methods and business properties.
business system
A group of diverse but interdependent applications and other system resources that interact to accomplish specific business functions.
business-to-business (B2B)
Refers to Internet applications that exchange information or run transactions between businesses. See also business-to-consumer.
business-to-consumer (B2C)
Refers to the subset of Internet applications that exchange information or run transactions between businesses and consumers. See also business-to-business.
business-to-employee (B2E)
A business model that supports electronic communications between a business and its employees.
bus member
An application server or server cluster that hosts one or more messaging engines in a service integration bus.
bus topology
A physical arrangement of application servers, messaging engines and queue managers and the pattern of bus connections and links between them.
bytecode
Machine-independent code generated by the Java compiler and executed by the Java interpreter. (Sun)

C

C2A
See Click-to-Action.
CA
See certificate authority.
cache
A buffer that contains frequently accessed instructions and data; it is used to reduce access time.
cache instance resource
A location where any Java Platform, Enterprise Edition (Java EE) application can store, distribute, and share data.
cache replication
The sharing of cache IDs, cache entries, and cache invalidations with other servers in the same replication domain.
calculation strategy
The strategy used to calculate the final score of a scorecard table.
callback handler
A mechanism that uses a Java Authentication and Authorization Service (JAAS) interface to pass a security token to the web service security run time for propagation in the web service security header.
callout
The action of bringing a computer program, a routine, or a subroutine into effect.
callout node
The connection point in a mediation request flow from which a service message is sent to a target. There must be one callout node for each target operation.
callout response node
The starting point for a mediation response flow. There must be one callout response node for each target.
call stack
A list of data elements that is constructed and maintained by the Java virtual machine (JVM) for a program to successfully call and return from a method.
capability
A group of functions and features that can be hidden or revealed to simplify the user interface. Capabilities can be enabled or disabled by changing preference settings, or they can be controlled through an administration interface.
capability list
A list of associated resources and their corresponding privileges per user.
card
  1. A Wireless Markup Language (WML) document that provides user-interface and navigational settings to display content on mobile devices. See also deck.
  2. In the Map Designer, a data object. There are two types of map cards: input and output.
cardinality
The number of elements in a set.
card object
An object used in the TX Programming Interface that represents an input or output card of a map in program memory.
Cascading Style Sheets (CSS)
A language that defines a hierarchical set of style rules for controlling the rendering of HTML or XML files in browsers, viewers, or in print.
case
A process instance and related set of documents, properties, roles, and tasks that are used to facilitate the collaboration of people to achieve a business outcome. See also task.
case property
A property, such as a name or date, that is defined at the solution level and reused in a case type, document type, task, or step in that solution. See also case type, document type.
case type
The definition of a case. The information that a case type provides is similar to that information that a process definition or template provides for a process instance. See also case property.
catalog
A container that, depending on the container type, holds processes, data, resources, organizations, or reports in the project tree.
catalog service
A service that controls placement of shards and discovers and monitors the health of containers.
catalog service domain
A highly available collection of catalog service processes.
catching message intermediate event
An intermediate event that is triggered when a specific message is received. See also intermediate event.
category
  1. A classification of elements for documentation or analyses.
  2. A type class that is used to organize types in a type tree in the Type Designer. Categories organize types that have common properties.
  3. A property that is set on an element of the business object model (BOM) and can be applied to business classes and filtered in business rules. This property allows the user to specify whether a business class and its members are visible in a rule.
  4. A container used in a structure diagram to group elements based on a shared attribute or quality.
category filter
A filter that is set on a business rule and removes the business element to which a category was attached from the completion menu.
CBPDO
See Custom-built Product Delivery Option.
CBR
See content based routing.
CCD table
See consistent-change-data table.
CCI
See common client interface.
CCSID
See coded character set identifier.
CDD
See customization definition document.
CD table
See change-data table.
CEI
See Common Event Infrastructure.
CEI event
An event generated over the Common Event Infrastructure (CEI) and logged in a CEI data store.
CEI target
An application server or server cluster where the Common Event Infrastructure (CEI) server is enabled.
cell
  1. One or more processes that each host runtime components. Each has one or more named core groups.
  2. A group of managed processes that are federated to the same deployment manager and can include high-availability core groups.
cell-scoped binding
A binding scope where the binding is not specific to, and not associated with any node or server. This type of name binding is created under the persistent root context of a cell.
center cell
The only cell in a star topology with the ability to make autonomic decisions.
centralized installation manager
A component that remotely installs and uninstalls product and maintenance packages in server environments.
CEP
See complex event processing.
certificate
In computer security, a digital document that binds a public key to the identity of the certificate owner, thereby enabling the certificate owner to be authenticated. A certificate is issued by a certificate authority and is digitally signed by that authority. See also certificate authority, certificate signing request.
certificate authority (CA)
A trusted third-party organization or company that issues the digital certificates. The certificate authority typically verifies the identity of the individuals who are granted the unique certificate. See also certificate, Globus certificate service, Secure Sockets Layer.
certificate revocation list (CRL)
A list of certificates that have been revoked before their scheduled expiration date. Certificate revocation lists are maintained by the certificate authority and used, during a Secure Sockets Layer (SSL) handshake to ensure that the certificates involved have not been revoked.
certificate signing request (CSR)
An electronic message that an organization sends to a certificate authority (CA) in order to obtain a certificate. The request includes a public key and is signed with a private key; the CA returns the certificate after signing with its own private key. See also certificate, keystore.
CGI
See Common Gateway Interface.
chain
The name of a channel framework connection that contains an endpoint definition.
chameleon schema
A schema that inherits a target namespace from a schema that includes the chameleon schema.
change-data table (CD table)
In SQL replication, a replication table on the Capture control server that contains changed data for a replication source table.
change management
The process of planning for and executing changes to configuration items in the information technology environment. The primary objective of change management is to enable beneficial changes to be made with minimum disruption to services.
change set
A cohesive unit consisting of a number of related changes that need to be made together.
channel
  1. A WebSphere MQ object that defines a communication link between two queue managers (message channel) or between a client and a queue manager (MQI channel). See also message channel, queue manager.
  2. A communication path through a chain to an endpoint.
channel framework
A common model for connection management, thread usage, channel management, and message access within an application server.
character conversion
The process of changing data from one character coding representation to another.
character encoding
The mapping from a character (a letter of the alphabet) to a numeric value in a character code set. For example, the ASCII character code set encodes the letter "A" as 65, while the EBCIDIC character set encodes this letter as 43. The character code set contains encodings for all characters in one or more language alphabets.
chassis
The metal frame in which various electronic components are mounted.
cheat sheet
An interface that guides users through the wizards and steps required to perform a complex task, and that links to relevant sections of the online help.
check in
In certain software configuration management (SCM) systems, to copy files back into the repository after changing them.
check out
In certain software configuration management (SCM) systems, to copy the latest revision of a file from the repository so that it can be modified.
child node
A node within the scope of another node.
choice type
A group type with a subclass equal to choice that is used to define a selection from a set of components. A choice type defines a choice group, which is valid when the data matches one of the components in the choice group.
choreography
An ordered sequence of message exchanges between two or more participants. In a choreography there is no central controller, responsible entity, or observer of the process.
CICS
An IBM licensed program that provides online transaction-processing services and management for business applications.
CIP
See customized installation package.
cipher
A cryptographic algorithm used to encrypt data that is unreadable until converted into plain data with a predefined key.
cipher specifications
Specifications that indicate the data encryption algorithm and key size to use for secure connections.
circular reference
A series of objects where the last object refers to the first object, which can cause the series of references to be unusable.
class
  1. A basic unit of the classification hierarchy used in the Type Designer. There are three classes: item, group, and category.
  2. In object-oriented design or programming, a model or template that can be used to create objects with a common definition and common properties, operations, and behavior. An object is an instance of a class.
class file
A compiled Java source file.
class hierarchy
The relationships between classes that share a single inheritance.
classification hierarchy
The hierarchy of a type tree in the Type Designer. The deeper the subtype, the more specific the data characteristics are. See also compositional hierarchy.
class loader
Part of the Java virtual machine (JVM) that is responsible for finding and loading class files. A class loader affects the packaging of applications and the runtime behavior of packaged applications deployed on application servers.
class path
A list of directories and JAR files that contain resource files or Java classes that a program can load dynamically at run time.
cleanup period
The time period during which a database record that has reached its final state or condition is to remain in the database. After the cleanup period expires for such a record, database cleanup causes the record to be deleted from the database.
CLI
See command-line interface.
Click-to-Action (C2A)
A method for implementing cooperative portlets, whereby users can click an icon on a source portlet to transfer data to one or more target portlets. See also cooperative portlets, wire.
client
A software program or computer that requests services from a server. See also host, server.
client application
An application, running on a workstation and linked to a client, that gives the application access to queuing services on a server.
client message
A message from a client application that is to be sent by means of a network to its destination, or a message that is routed to a client application to acknowledge the receipt of a client message by a network.
client project for RuleApps
A predefined project for Eclipse that contains a class to execute a rule set within a RuleApp.
client proxy
An object on the client side of a network connection that provides a remote procedure call interface to a service on the server side.
client reroute
A method that allows a client application, upon the loss of communication with a database server and the predefinition of an alternative server, to continue working with the original database server or the alternative server with only minimal interruption of the work.
client/server
Pertaining to the model of interaction in distributed data processing in which a program on one computer sends a request to a program on another computer and awaits a response. The requesting program is called a client; the answering program is called a server. See also distributed application.
client type detection
A process in which a servlet determines the markup language type required by a client and calls the appropriate JavaServer Pages file.
clock event
A special system event that is used to initiate a system-generated event.
clone
To prepare a reference computer and create a system profile ready for deployment.
cloud
A network that delivers requested virtual resources as a service.
cloud computing
A computing platform where users can have access to applications or computing resources, as services, from anywhere through their connected devices. A simplified user interface and application programming interface (API) makes the infrastructure supporting such services transparent to users.
cloud group
A collection of hypervisors from a single vendor.
cloud provider
An organization that provides cloud computing resources.
CLR
See common language runtime.
cluster
  1. A collection of complete systems that work together to provide a single, unified computing capability.
  2. A group of application servers that collaborate for the purposes of workload balancing and failover.
CMP
See container-managed persistence.
CO
See configuration object.
coach
A user interface that can be created to collect input that is required for an underlying service.
COA report
See confirm-on-arrival report.
coarse-grained
Pertaining to viewing a group of objects from an abstract or high level. See also fine-grained.
cobrowsing
The interaction of multiple users sharing information about their individual web interactions. With this interaction users can share a view of the same web page simultaneously and share further interactions with the web page they are jointly viewing.
code assist
See content assist.
coded character set identifier (CCSID)
A 16-bit number that includes a specific set of encoding scheme identifiers, character set identifiers, code page identifiers, and other information that uniquely identifies the coded graphic-character representation.
code list
One or many dynamic pairs of code values that contains sender code and receiver code. Each code pair has one description and up to four additional codes relating to the pair.
code list table
A repository for lists of codes that can further define fields.
COD report
See confirm-on-delivery report.
coexistence
The ability of two or more entities to function in the same system or network.
coherent cache
Cache that maintains integrity so that all clients see the same data.
cold start
The process of starting an existing data replication configuration without regard for prior replication activity, causing reinitialization of all subscriptions.
collaboration
  1. A diagram that shows the exchange of messages between two or more participants in a BPMN model.
  2. The ability to connect customers, employees, or business partners to the people and processes in a business or organization, in order to facilitate improved decision-making. Collaboration involves two or more individuals with complementary skills interacting together to resolve a business problem.
collaborative components
UI-neutral API methods and tag libraries that allow developers to add collaborative functionality to their portlets.
collaborative filtering
Personalization technology that calculates the similarity between users based on the behaviors of a number of other people and uses that information to make recommendations for the current user.
collaborative unit
The configuration of the part of a deployment environment that delivers required behavior to an application module. For example, a messaging collaborative unit includes the host of the messaging engine and deployment targets of the application module, and provides messaging support to the application module.
collapsed subprocess
A subprocess that hides its flow details. The collapsed subprocess object has a marker that distinguishes it as a subprocess, rather than a task. The marker is a small square with a plus sign inside.
collection certificate store
A collection of intermediate certificates or certificate revocation lists (CRL) that are used by a certificate path to build up a certificate chain for validation.
collection page
A type of page in the administrative console that displays a collection list of administrative objects. From this type of page, you can typically select objects to act on or to display other pages for.
collective
A set of WebSphere DataPower XC10 appliances that are grouped together for scalability and management purposes.
collision arbiter
A plug-in that specifies how to handle change collisions in map entries.
comma delimited file
A file whose records contain fields that are separated by a comma.
command bean
A proxy that can invoke a single operation using an execute() method.
command line
The blank line on a display where commands, option numbers, or selections can be entered.
command-line interface (CLI)
A type of computer interface in which the input command is a string of text characters.
commit
To apply all the changes made during the current unit of recovery (UR) or unit of work (UOW). After the operation is complete, a new UR or UOW can begin.
common area
In a web page that is based on a page template, the fixed region of the page.
Common Base Event
A specification based on XML that defines a mechanism for managing events, such as logging, tracing, management, and business events, in business enterprise applications. See also situation.
common client interface (CCI)
A standard interface that allows developers to communicate with enterprise information systems (EISs) through specific resource adapters, using a generic programming style. The generic CCI classes define the environment in which a J2EE component can send and receive data from an EIS.
Common Criteria
A framework for independent assessment, analysis, and testing of IT products to a set of security requirements.
Common Event Infrastructure (CEI)
The implementation of a set of APIs and infrastructure for the creation, transmission, persistence, and distribution of business, system, and network Common Base Events. See also event emitter.
Common Gateway Interface (CGI)
An Internet standard for defining scripts that pass information from a web server to an application program, through an HTTP request, and vice versa.
common language runtime (CLR)
The runtime interpreter for all .NET Framework applications. See also .NET Framework.
Common Object Request Broker Architecture (CORBA)
An architecture and a specification for distributed object-oriented computing that separates client and server programs with a formal interface definition. See also Internet Inter-ORB Protocol.
Common Secure Interoperability Version 2
An authentication protocol developed by the Object Management Group (OMG) that supports interoperability, authentication delegation and privileges.
communications enabled application
A software application that uses an IP network and communications technology to accomplish business objectives. Enterprise applications can be communications enabled with web telephony components and collaborative web services that allow users to dynamically interact through shared browser sessions over a secure network.
compensation
The means by which operations in a process that have successfully completed can be undone if an error occurs, to return the system to a consistent state.
compensation flow
Flow that defines the set of activities that are performed while the transaction is being rolled back to compensate for activities that were performed during the normal flow of the process. A compensation flow can also be called from a compensate end or intermediate event.
compensation service
The operation that is performed to compensate for a successful operation when a process generates a fault (which is not handled within the process).
compilation unit
A portion of a computer program sufficiently complete to be compiled correctly.
compiled map component
An Integration Flow Designer object that references an executable map in compiled file format.
compile time
The time period during which a computer program is being compiled into an executable program.
complete lifecycle server
A server that the user can create and manage within the administrative console.
complete type name
The name of a type that represents its hierarchical structure within a type tree, which includes the names of all the types in the path from the root type down.
complex event processing (CEP)
The processing of events that have rules that rely on the data and timing of more than one event.
complex scorecard
A collection of multiple scorecards within one rule flow. The rule flow is used to identify the dependency, the flow and the order in which the score from each of the scorecards will be included in the overall score.
complex type
A type that contains elements and can include attributes. See also simple type.
component
A reusable object or program that performs a specific function and works with other components and applications.
component element
An entity in a component where a breakpoint can be set, such as an activity or Java snippet in a business process, or a mediation primitive or node in a mediation flow.
component instance
A running component that can be running in parallel with other instances of the same component.
component rule
An expression about one or more components, which is defined in the Type Designer. A component rule is used for validating data and specifies what must be true for the data that is defined by that component to be valid.
component test
An automated test of one or more components of an enterprise application, which may include Java classes, EJB beans, or web services. See also abstract test, test pattern.
composer
In Java, a class used to map a single complex bean field to multiple database columns. Composition is needed for complex fields that are themselves objects with fields and behavior.
composite
  1. A group of related data elements used in EDI transactions.
  2. A Service Component Architecture (SCA) element that contains components, services, references, and wires that connect them.
composite service
In service-oriented architecture, a unit of work accomplished by an interaction between computing devices.
composite state
In a business state machine, an aggregate of one or more states that is used to decompose a complex state machine diagram into a simple hierarchy of state machines.
compositional hierarchy
A hierarchy in which the composition of the data is reflected in the structure of the group type in the group window. See also classification hierarchy.
composition unit
A unit that represents a configured asset and enables the asset contents to interact with other assets in the application.
compound activity
An activity that has detail that is defined as a flow of other activities. A compound activity is a branch (or trunk) in the tree-structure hierarchy of process activities. Graphically, a compound activity is a process or subprocess.
concept
A class of entities that are represented by general metadata definitions rather than physical document standards.
concrete portlet
A logical representation of a portlet object distinguished by a unique configuration parameter (PortletSettings).
concrete type
A type that can be instantiated and is derived from an abstract type.
concurrency control
The management of contention for data resources.
condition
  1. A test of a situation or state that must be in place for a specific action to occur.
  2. In a business state machine, an expression that guards the transition and allows transition to the next state only when and if the incoming operation evaluates to 'True'. Otherwise, the current state is maintained.
conditional mean
An alternative method for choosing a reason code assignment. It is a reasoning strategy that the user specifies in the scorecard requirements, which evaluates every attribute’s possible value ranges. The reason codes are determined based on the expected value of the attributes and rank order. Typically, the four lowest expected and their corresponding reason codes are chosen. A conditional mean can be used in neural nets and fused scorecards.
condition column
The condition part of a decision table.
condition node
A node in a decision tree that defines a rule condition and groups a set of branches.
configuration
In a broker domain, the brokers, execution groups, deployed message sets, and deployed message flows, and the defined topics and access control lists.
configuration administration
The administration of the configuration object types (CTs), configuration objects (COs), and configuration object sets (COSs) that comprise the configuration data of organizational units (OUs). This is carried out after the product has been installed and customized.
configuration entity
Entities used to model an organization and to specify how messages are processed. These entities include configuration object types (CTs), organizational units (OUs), configuration object sets (COSs), configuration objects (COs).
configuration object (CO)
An instance of a configuration object type (CT) that represents an object in an organizational unit (OU). Which attributes can be added to a CO is determined by the definition of the CT on which the CO is based.
configuration object set (COS)
A set of configuration objects, used to limit the scope of configuration data provided to message flows.
configuration object type (CT)
A description of the class of configuration objects, including the attributes that each member of this class can have.
configuration repository
A storage area of configuration data that is typically located in a subdirectory of the product installation root directory.
configured name binding
Persistent storage of an object in the name space that is created using either the administrative console or the wsadmin program.
confirm-on-arrival report (COA report)
A WebSphere MQ report message type created when a message is placed on that queue. It is created by the queue manager that owns the destination queue.
confirm-on-delivery report (COD report)
A WebSphere MQ report message type created when an application retrieves a message from the queue in a way that causes the message to be deleted from the queue. It is created by the queue manager.
connection factory
A set of configuration values that produces connections that enable a Java EE component to access a resource. Connection factories provide on-demand connections from an application to an enterprise information system (EIS) and allow an application server to enroll the EIS in a distributed transaction.
connection handle
A representation of a connection to a server resource.
connection pool
A group of host connections that are maintained in an initialized state, ready to be used without having to create and initialize them.
connection pooling
A technique used for establishing a pool of resource connections that applications can share on an application server.
connectivity
The capability of a system or device to be attached to other systems or devices without modification.
connector
  1. 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.
  2. A servlet that provides a portlet access to external sources of content, for example, a news feed from a website of a local television station.
connector packet
The set of data that is passed between the event processing server (runtime server) and external systems using the technology connectors.
consistent-change-data table (CCD table)
In data replication, a type of replication target table that is used for storing history, auditing data, or staging data. A CCD table can also be a replication source.
console
A user interface that allows you to list and manage objects or entities, such as catalogs, hierarchies, and items. See also module.
constant
In a business object model (BOM), a vocabulary element that verbalizes the public static final attribute of a class with the same type as the BOM class. See also verbalization.
constraint
A rule that limits the values that can be inserted, deleted, or updated in a table. See also foreign key, primary key.
consumer portal
A portal that uses the portlets that a producer portal provides. See also producer definition, producer portal.
container
  1. An item that can contain other items. Tags that are added to a container inherit the position of the container.
  2. An entity that provides life-cycle management, security, deployment, and runtime services to components. (Sun) See also connector, resource adapter.
container-managed persistence (CMP)
The mechanism whereby data transfer between an entity bean's variables and a resource manager is managed by the entity bean's container. (Sun) See also bean-managed persistence.
container-managed transaction
A transaction whose boundaries are defined by an EJB container. An entity bean must use container-managed transactions. (Sun)
container server
A server instance or Java virtual machine (JVM) that hosts one or more shard containers. See also shard.
container transaction
See container-managed transaction.
containment hierarchy
A namespace hierarchy consisting of model elements, and the containment relationships that exist between them. A containment hierarchy forms an acyclic graph.
containment relationship
A relationship between two objects where one object is contained within the other. The destination is nested within the source.
content area
In a web page that is based on a page template, the editable region of the page.
content assist
A feature of some source editors that prompts the user with a list of valid alternatives for completing the current line of code or input field.
content based routing (CBR)
An optional feature of the caching proxy that provides intelligent routing to back-end application servers. This routing is based on HTTP session affinity and a weighted round-robin algorithm.
contention
A situation in which a transaction attempts to lock a row or table that is already locked.
content management
Software designed to help businesses manage and distribute content from diverse sources.
content model
The representation of any data that may be contained inside an XML element. There are four kinds of content models: element content, mixed content, EMPTY content and ANY content.
content provider
A source for content that can be incorporated into a portal page as a portlet.
content spot
A class file that is added to a JSP file to designate display of personalized data or content. Each content spot has a name and will accept a specific type of data from a rule.
context authorization
The authority for the owner of a human task to access the BPEL process that contains the human task.
context definition
A set of events, each with an associated context ID, that is used as a group for complex event processing. Rules that are associated with the events can be part of the context definition. Actions that are fired by the rules are also part of the context definition. See also context instance.
context ID
See context identifier.
context identifier
  1. A value that identifies the default values, such as the process instance ID or the activity instance ID, that a task depends on.
  2. A common data value that is used to group events into a context instance.
context instance
A group of events, actions, and context-scoped business objects that occur within the same context definition and have matching context ID values. See also context definition.
context root
The web application root, which is the top-level directory of an application when it is deployed to a web server.
context-scoped business object
A summary object or accumulating array object that is used to share data from events across events in a context.
contracted component
In the Integration Flow Designer, a component that does not display the sources and targets associated with it. See also expanded component.
contribution
The primary asset that can contain Service Component Definition Language (SCDL) with composite definitions, as well as artifacts such as Java classes and Web Services Description Language (WSDL) and XML Schema Definitions (XSD).
control
See widget.
control analysis
A type of analysis that displays variations in values of the business measures over a specific period of time. This type of analysis reduces data variation, and is often used for quality control. Allowable variation is three times the standard deviation of the data.
controlled flow
A flow that proceeds from one flow object to another through a sequence flow link but is subject to either conditions or dependencies from another flow as defined by a gateway. Typically, a controlled flow is a sequence flow between two activities, with a conditional indicator or a sequence flow that is connected to a gateway.
controller
A component or a set of virtual storage processes that schedules or manages shared resources.
control link
An object in a process that links nodes and determines the order in which they run.
control region adjunct
A servant that interfaces with service integration buses to provide messaging services.
conversational processing
An optional IMS facility with which an application program can accumulate information acquired through multiple interchanges with a terminal, even if the program stops between interchanges. See also IMS conversation.
converter
In Enterprise JavaBeans (EJB) programming, a class that translates a database representation to an object type and back.
cooperative portlets
Two or more portlets on the same web page that interact by sharing information. See also Click-to-Action, wire.
Coordinated Universal Time (UTC)
The international standard of time that is kept by atomic clocks around the world.
copy helper
An access bean that contains a local copy of attributes from a remote entity bean. Unlike bean wrappers, copy helpers are optimized for use with a single instance of an entity bean.
CORBA
See Common Object Request Broker Architecture.
core group
A group of processes that is directly accessible to each other and is connected using a local area network (LAN).
core group access point
A definition of a set of servers that provides access to the core group.
core group bridge
The means by which core groups communicate.
core group member
A server included in the cluster of a core group.
correlation
  1. 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.
  2. Data that enables a user to record document-specific correlation parameters generated during translation, by the correlation service, or by document tracking functions.
  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.
correlation property
Data in an event that the runtime server uses to determine which instance of a task, process, or business state machine should receive the input at run time.
correspondent
An institution to which your institution sends and from which it receives messages.
COS
See configuration object set.
counter
A specialized metric used to keep track of the number of occurrences of a specific situation or event. For example, you can use a counter to track the number of times that a task is started within a process, where that task is contained in a loop.
coupling
The dependency that components have on one another.
create method
In enterprise beans, a method defined in the home interface and invoked by a client to create an enterprise bean. (Sun)
credential
  1. In the Java Authentication and Authorization Service (JAAS) framework, a subject class that owns security-related attributes. These attributes can contain information used to authenticate the subject to new services.
  2. Information acquired during authentication that describes a user, group associations, or other security-related identity attributes, and that is used to perform services such as authorization, auditing, or delegation. For example, a user ID and password are credentials that allow access to network and system resources.
critical path
The processing path that takes the longest time to complete of all parallel paths in a process instance, where each path considered begins at a start node or an input to the process and ends at a terminate node.
CRL
See certificate revocation list.
cross-cell communication
The process of information sharing and request routing between cells.
cross-cell environment
A production environment in which one or more servers in one cell can receive events from another server or set of servers in another cell.
cross-cutting concern
A software concern (synchronization, logging, memory allocation, and so forth) that is external and orthogonal to the problem that a software component is designed to address.
cryptographic token
A logical view of a hardware device that performs cryptographic functions and stores cryptographic keys, certificates, and user data.
CSR
See certificate signing request.
CSS
See Cascading Style Sheets.
CSV file
A text file that contains comma-separated values. A CSV file is commonly used to exchange files between database systems and applications that use different formats.
CT
See configuration object type.
cube
A multidimensional representation of data needed for online analytical processing, multidimensional reporting, or multidimensional planning applications.
current customization definition
A customization definition that describes an instance for which the corresponding resources have already been deployed and are running.
custom action
  1. 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)
  2. A Java or non-Java process definition that a user can define as a part of a health policy action plan or elasticity operation.
Custom-built Product Delivery Option (CBPDO)
A software delivery package consisting of uninstalled products and unintegrated service. Installation requires the use of SMP/E. CBPDO is one of the two entitled methods for installing z/OS; the other method is ServerPac.
custom finder
See finder method.
customization definition document (CDD)
An XML document that describes the layout of an instance (that is, its organizational units (OUs) and servers, and which service bundles are assigned to each server-OU combination). The Customization Definition Program (CDP) uses a CDD to determine which deployment data to produce for an instance.
customization definition report
A report that describes the servers, organizational units (OUs), and services of an instance, and how they are distributed within the instance.
customized installation package (CIP)
A customized installation image that can include one or more maintenance packages, a configuration archive file from a stand-alone server profile, one or more enterprise archive files, scripts, and other files that help customize the resulting installation.
customizer
A Java class (implementing the java.beans.Customizer interface) that is associated with a bean to provide a richer user interface for the properties of that bean.
custom profile
A profile that describes an empty node, which becomes operational, as a managed node, when federated into a network deployment cell.
custom relationship
An association between two or more data entities as provided by the user.
custom screen record
A runtime view of the screen that allows access to available screen fields.
custom service
A configurable service that defines a hook that runs when the server starts and shuts down when the server stops.
custom tag
An extension to the JavaServer Pages (JSP) language that performs a specialized task. Custom tags are typically distributed in the form of a tag library, which also contains the Java classes that implement the tags.
custom user registry
A customer-implemented user registry that implements the UserRegistry Java interface. This registry type can support virtually any kind of accounts repository from a relational database and can provide flexibility in adapting product security to various environments.

D

DAD
See document access definition.
DAD script
A file that is used by the DB2 XML Extender, either to compose XML documents from existing DB2 data or to decompose XML documents into DB2 data.
DADX
See document access definition extension.
DADX group
A folder that contains database connection (JDBC and JNDI) and other information that is shared between DADX files within the group.
DADX runtime environment
The DADX runtime environment provides information to the DADX web service, including the HTTP GET and POST bindings, the test page, WSDL generation, and the translation of DTD data into XML schema data.
daemon
A program that runs unattended to perform continuous or periodic functions, such as network control.
dashboard
A web page that can contain one or more widgets that graphically represent business data.
data access bean
A class library that provides a rich set of features and functions, while hiding the complexity associated with accessing relational databases.
database cleanup
The act of deleting from a database those records for which the cleanup period has expired.
database management system (DBMS)
See database manager.
database manager
A program that manages data by providing centralized control, data independence, and complex physical structures for efficient access, integrity, recovery, concurrency control, privacy, and security.
database request module (DBRM)
A data set member that is created by the DB2 for z/OS precompiler and that contains information about SQL statements. DBRMs are used in the bind process.
data binding
A component that converts protocol-specific local data to and from a business object.
data class
An access bean that provides data storage and access methods for caching enterprise bean properties. Unlike copy helpers, data class access beans work with enterprise beans that have local client views as well as remote client views.
data connection
A connection to a repository of data (for example, a DB2 database) with which the runtime server can retrieve data in order to enhance the event being processed.
data definition
A data object that defines a database or table.
Data Definition Language (DDL)
A language for describing data and its relationships in a database.
Data Encryption Standard (DES)
A cryptographic algorithm designed to encrypt and decrypt data using a private key.
Data Exchange SPI architecture (DESPI)
The interface that resource adapters and runtime components use to exchange business object data. The Data Exchange SPI architecture, which is based on the concept of cursors and accessors, abstracts the data type so that an adapter can be written only once and then work on runtime environments that support different data types, such as data objects and JavaBeans.
datagram
A form of asynchronous messaging in which an application sends a message, but does not require a response. See also request/reply.
data graph
A set of Service Data Objects (SDO) interconnected with relationships.
data grid
A system of data that dynamically caches, partitions, replicates, and manages application data and business logic across multiple servers.
data handler
A Java class or library of classes that a process uses to transform data into and from specific formats. In the business integration environment, data handlers transform text data of specified formats into business objects, and transform business objects into text data of specified formats.
data object
  1. Any object (such as tables, views, indexes, functions, triggers, and packages) that can be created or manipulated using SQL statements. See also business object.
  2. An object that provides information about required activities. Data objects can represent one object or a collection of objects.
  3. A portion of data in a data stream that can be recognized as belonging to a specific type.
data object filter
A control that allows the exclusion of data objects (such as tables and schemas) from the tree view of the database.
data source
  1. The means by which an application accesses data from a database.
  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. A repository of data to which a federated server can connect and then retrieve data by using wrappers. A data source can contain relational databases, XML files, Excel spreadsheets, table-structured files, or other objects. In a federated system, data sources seem to be a single collective database.
data store
  1. A data structure where documents are kept in their parsed form.
  2. A place (such as a database system, file, or directory) where data is stored.
data store profile
An object that defines properties used by the default data store plug-in, which is used to persistently store events received by the event server.
data structure
The composition of the data, including repeating sub-structures, nested groupings, sequences, and choices.
Data Transformation Framework (DTF)
An infrastructure that includes data bindings and function selectors, which enables an adapter to convert native data formats to business objects and to convert business objects back to native data formats, such as XML.
data warehouse
A subject-oriented collection of data that is used to support strategic decision making. The warehouse is the central point of data integration for business intelligence. It is the source of data for data marts within an enterprise and delivers a common view of enterprise data.
DBMS
See database management system.
DBRM
See database request module.
DDL
See Data Definition Language.
dead-letter queue (DLQ)
A queue to which a queue manager or application sends messages that cannot be delivered to their correct destination.
deadlock
A condition in which two independent threads of control are blocked, each waiting for the other to take some action. Deadlock often arises from adding synchronization mechanisms to avoid race conditions.
debug engine
The server component of the debugger, whose client/server design enables both local and remote debugging. The debug engine runs on the same system as the program being debugged.
debugger
A tool used to detect and trace errors in computer programs.
debugging session
The debugging activities that occur between the time that a developer starts a debugger and the time that the developer exits from it.
decision
A gateway within a business process where the sequence flow can take one of several alternative paths.
Decision Center console
A designated workspace where business users can work collaboratively to author, edit, organize, and search for business rules.
decision engine
An implementation of the rule engine that is available for the zRule Execution Server for z/OS module. See also rule engine.
decision table
A form of business rule that captures multi-conditional decision-making business logic in a table where the rows and columns intersect to determine the appropriate action. See also rule set.
decision tree
A way of representing business rules in a tree form. Decision trees provide a structure for laying out options and investigating the possible outcomes of choosing those options.
Decision Validation Services (DVS)
A set of testing and simulation capabilities with which business users and policy managers can verify the rules they have written, and determine if potential changes will have the intended outcome.
Decision Warehouse
A warehouse that saves execution traces to a database so that users can query the data store to get information on particular executions or transactions.
deck
An XML document that contains a collection of Wireless Markup Language (WML) cards. See also card.
declaration
In Java programming, a statement that establishes an identifier and associates attributes with it, without necessarily reserving its storage or providing the implementation. (Sun)
declarative security
The security configuration of an application during assembly stage that is defined in the deployment descriptors and enforced by the security run time.
decode
To convert data by reversing the effect of some previous encoding.
decoration
In graphical user interfaces (GUIs), a glyph that annotates a resource with status information, for example to indicate that a file has changed since it was last saved or checked out of a repository.
de-enveloping
The process of removing one or more envelopes from a document or a set of documents.
default portal page
The page that displays to a user at initial portal deployment and before the user completes enrollment. Sometimes used as a synonym for home page.
default public place
A place whose membership automatically includes all users and which appears in the Places selector for every user. A user is always a member of this place.
definition file
A file that defines the content that is displayed within the navigation and work area frames.
delegation
The process of propagating a security identity from a caller to a called object. According to the Java Platform, Enterprise Edition (Java EE) specification, a servlet and an enterprise bean can propagate either the client identity when invoking enterprise beans, or can use another specified identity as indicated in the corresponding deployment descriptor.
delimited format
Data that has data objects that are separated by delimiters.
delimiter
  1. A flag that is formed by a character or a sequence of characters to group or separate items of data by marking the beginning and end of a unit of data. The delimiter is not a part of the flagged unit of data.
  2. A character, such as comma or tab, used to group or separate units of text by marking the boundary between them.
delta business object
A business object used in an update operation. Such a business object contains only key values and the values to be changed. See also after-image.
delta deployment
Deployment of only that data that is required to transform a current runtime environment into a target runtime environment. See also full deployment.
demilitarized zone (DMZ)
A configuration that includes multiple firewalls to add layers of protection between a corporate intranet and a public network, such as the Internet.
denial-of-service attack (DoS)
In computer security, an assault on a network that brings down one or more hosts on a network such that the host is unable to perform its functions properly. Network service is interrupted for some period.
dependency
  1. A requirement that one managed resource has on another managed resource in order to operate correctly.
  2. A relationship that allows a module to use artifacts from a library or that allows a process application to use artifacts from a toolkit. A toolkit can also have a dependency on another toolkit.
dependency relationship
In UML modeling, a relationship in which changes to one model element (the supplier) impact another model element (the client).
deploy
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.
deployment
The process of transferring rules from a local development environment into an operational, or runtime, environment.
deployment code
Additional code that enables bean implementation code written by an application developer to work in a particular EJB runtime environment. Deployment code can be generated by tools that the application server vendor supplies.
deployment data
The resource files, generated during customization, that are used to create the resources for an instance.
deployment data set
A data set containing the resource files generated during customization.
deployment descriptor
An XML file that describes how to deploy a module or application by specifying configuration and container options. For example, an EJB deployment descriptor passes information to an EJB container about how to manage and control an enterprise bean.
deployment directory
  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.
deployment environment
A collection of configured clusters, servers, and middleware that collaborate to provide an environment to host software modules. For example, a deployment environment might include a host for message destinations, a processor or sorter of business events, and administrative programs.
deployment instruction
A set of instructions that describe how to execute the resource files, and deploy, on the runtime systems, the resources required by the instance.
deployment manager
A server that manages and configures operations for a logical group or cell of other servers. See also subprocess.
deployment phase
A phase that includes a combination of creating the hosting environment for your applications and the deployment of those applications. This includes resolving the application’s resource dependencies, operational conditions, capacity requirements, and integrity and access constraints.
deployment policy
  1. An optional way to configure an eXtreme Scale environment based on various items, including: number of systems, servers, partitions, replicas (including type of replica), and heap sizes for each server.
  2. A policy that modifies the domain or service configuration at deployment time to accommodate the environment in which the appliance operates.
deployment topology
The configuration of servers and clusters in a deployment environment and the physical and logical relationships among them.
deployment vehicle
A job or other executable file that is used to deploy resources. Each vehicle corresponds to a particular resource file.
deploy phase
See deployment phase.
deprecated
Pertaining to an entity, such as a programming element or feature, that is supported but no longer recommended and that might become obsolete.
dequeue
To remove items from a queue. See also enqueue.
DER
See Distinguished Encoding Rules.
Derby
An embeddable, all Java, object-relational database management system (ORDBMS).
derivation
In object-oriented programming, the refinement or extension of one class from another.
derived event
See synthetic event.
derived page
One or more child pages that have a shared layout that is inherited from the properties of the parent page.
DES
See Data Encryption Standard.
deserialization
A method for converting a serialized variable into object data. See also serializer.
DESPI
See Data Exchange SPI architecture.
destination
An exit point that is used to deliver documents to a back-end system or a trading partner.
developer
A decision management user role that is responsible for implementing the rule applications.
device
A component that is used for an event provider to provide location, notification, or telemetry data. Devices always belong to a hub and can be grouped in device groups.
device input format (DIF)
The Message Format Service (MFS) control block that describes the format of the data that is entered on the device and presented to MFS.
device output format (DOF)
The Message Format Service (MFS) control block that describes the format of the output data that is presented to the device.
dialog
The recorded interaction between a user and the 3270 application that the user accesses. Users can record a dialog using the Record Dialog function in the 3270 terminal service recorder. A recorded dialog includes the keystrokes, inputs and outputs that move the user from one screen to another in the 3270 application.
dialog editor
A 3270 terminal service development tool that enables a developer to modify the dialog that was recorded with the 3270 terminal service recorder.
dialog file
The result of recording a dialog from the 3270 terminal service recorder. The dialog file is saved to a WSDL file in the workbench.
DIF
See device input format.
digest code
A number that is the result of a message digest function or a secure hash algorithm distilling a document.
digital certificate
An electronic document used to identify an individual, a system, a server, a company, or some other entity, and to associate a public key with the entity. A digital certificate is issued by a certification authority and is digitally signed by that authority.
digital signature
Information that is encrypted with a private key and is appended to a message or object to assure the recipient of the authenticity and integrity of the message or object. The digital signature proves that the message or object was signed by the entity that owns, or has access to, the private key or shared-secret symmetric key.
digital signature algorithm (DSA)
A security protocol that uses a pair of keys (one public and one private) and a one-way encryption algorithm to provide a robust way of authenticating users and systems. If a public key can successfully decrypt a digital signature, a user can be sure that the signature was encrypted using the private key.
dimension
A data category that is used to organize and select monitoring context instances for reporting and analysis. Examples of dimensions are time, accounts, products, and markets. See also member.
dimensional model
The part of the monitor model that defines the cubes and cube content that are used for storing, retrieving, and analyzing the data that is gathered over time.
dimension level
An element or subelement of a dimension that is arranged hierarchically. For example, the time dimension can have years, months, and days as its levels.
directive
A first-failure data capture (FFDC) construct that provides information and suggested actions to assist a diagnostic module in customizing the logged data.
dirty read
A read request that does not involve any locking mechanism. This means that data can be read that might later be rolled back resulting in an inconsistency between what was read and what is in the database.
discover
In UDDI, to browse the business registry to locate existing web services for integration.
discovered server
A server that runs the middleware agent and is found outside of the administrative environment but has a server representation automatically created within the administrative environment. The representation that is created is an assisted life-cycle server.
dispatcher
A standalone application that acts as an intermediary between one or more devices and large event providers. The dispatcher retrieves all location messages from the event providers it is connected to and distributes them to one or more devices.
distinguishable types
Types that do not have common data objects.
Distinguished Encoding Rules (DER)
A standard, based on the Basic Encoding Rules, that is designed to ensure a unique encoding of each ASN.1 value, defined in ITU-T X.690.
distinguished name (DN)
  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.
distributed application
An application made up of distinct components that are located on different computer systems, connected by a network. See also client/server.
distributed eXtreme Scale
A usage pattern for interacting with eXtreme Scale when servers and clients exist on multiple processes.
DLQ
See dead-letter queue.
DMZ
See demilitarized zone.
DN
See distinguished name.
DNS
See Domain Name System.
document access definition (DAD)
An XML document format used by DB2 XML Extender to define the mapping between XML and relational data.
document access definition extension (DADX)
An XML document format that specifies how to create a web service using a set of operations that are defined by DAD documents and SQL statements.
document envelope
A structure that is applied to a document to prepare it for exchange between trading partners.
document literal wrapped
A convention or style that is used to structure a web service definition to generate a SOAP message that is WS-I compliant and can be easily validated.
Document Object Model (DOM)
A system in which a structured document, for example an XML file, is viewed as a tree of objects that can be programmatically accessed and updated. See also Simple API for XML.
document type
A classification that helps to organize and classify documents that belong to a specific case. Properties can be assigned to a document type to provide additional information about the documents. An example of a document type is a job application form. See also case property.
document type definition (DTD)
The rules that specify the structure for a particular class of SGML or XML documents. The DTD defines the structure with elements, attributes, and notations, and it establishes constraints for how each element, attribute, and notation can be used within the particular class of documents.
DOF
See device output format.
DOM
See Document Object Model.
domain
  1. A partition of the management space of an appliance.
  2. An object, icon, or container that contains other objects representing the resources of a domain. The domain object can be used to manage those resources.
  3. A logical grouping of resources in a network for the purpose of common management and administration. See also federation domain.
Domain Name System (DNS)
The distributed database system that maps domain names to IP addresses.
DOM element
One member of a tree of elements that is created when an XML file is parsed with a DOM parser. DOM elements make it easy to quickly identify all elements in the source XML file.
DoS
See denial-of-service attack.
do-while loop
A loop that repeats the same sequence of activities as long as some condition is satisfied. Unlike a while loop, a do-while loop tests its condition at the end of the loop. This means that its sequence of activities always runs at least once.
downstream
Pertaining to the direction of the flow, which is from the first node in the process (upstream) toward the last node in the process (downstream). See also node.
DSA
See digital signature algorithm.
DSO
See dynamic shared object.
DTD
See document type definition.
DTD document definition
A description or layout of an XML document based on an XML DTD.
DTF
See Data Transformation Framework.
dual authorization
A setting requiring that an action carried out by one person be confirmed by a second person. This prevents a single person from being able to carry out actions requiring a high level of security, for example the distribution of funds or the granting of access rights. See also single authorization.
durable subscription
A Java Message Service (JMS) subscription that persists and stores subscribed messages even when the client is not connected.
DVS
See Decision Validation Services.
dynaform
An instance of a DynaActionForm class or subclass that stores HTML form data from a submitted client request or that stores input data from a link that a user clicked.
dynamic binding
dynamic cache
A consolidation of several caching activities, including servlets, web services, and commands into one service where these activities share configuration parameters and work together to improve performance.
dynamic cluster
A server cluster that uses weights to balance the workloads of its cluster members dynamically, based on performance information collected from cluster members.
dynamic cluster isolation
The ability to specify whether the dynamic cluster runs on the same nodes as other instances of dynamic clusters, or if the dynamic cluster is the only dynamic cluster that runs on a single node.
dynamic domain
A domain in which the set of possible values for a type is defined. With a dynamic domain, the set of values is stored and managed outside the business object model (BOM), and changes to the set of values are automatically reflected in the business object model. When rule authors write business rules using the type, they choose from a list of values that is created dynamically and is always up-to-date.
dynamic operations
Operations that monitor the server environment and make recommendations that are based on the observed data.
dynamic policy
A template of permissions for a particular type of resource.
dynamic property
A property that can be overridden at run time by inserting information into the service message object (SMO).
dynamic reloading
The ability to change an existing component without restarting the server for the changes to become effective. See also hot deployment.
dynamic routing
The automatic routing of a service request, a message, or an event that is based on conditions at the time of the routing.
dynamic shared object (DSO)
A mechanism that provides a way to build a piece of program code in a special format for loading into the address space of an executable program at run time. The DSO gets knowledge of the executable program symbol set as if it had been statically linked with it in the first place.
dynamic web content
Programming elements such as JavaServer Pages (JSP) files, servlets, and scripts that require client or server-side processing for accurate runtime rendering in a web browser.
dynamic web project
A project that contains resources for a web application with dynamic content such as servlets or JavaServer Pages (JSP) files. The structure of a dynamic web project reflects the Java EE standard for web content, classes, class paths, the deployment descriptor, and so on.
dynamic workload manager
A feature of the on demand router that routes workload based on a weight system, which establishes a prioritized routing system. The dynamic workload manager dynamically modifies the weights to stay current with the business goals.

E

EAR
See enterprise archive.
EAR file
See enterprise archive.
early bind
To connect one process to another process so that a specific version of the called process is used. The calling process always uses the specified version of the invoked process even if updated versions are available.
early binding
The connection between two processes that uses a specified version of the invoked process. As a result, the calling process uses the specified version of the process that it is invoking, even when updated versions are available.
EAR project
See enterprise application project.
Eclipse
An open-source initiative that provides independent software vendors (ISVs) and other tool developers with a standard platform for developing plug-compatible application development tools.
ECSA
See extended common service area.
Edge Side Include (ESI)
A technology supporting cacheable and noncacheable web page components that can be gathered and assembled at the edge of a network.
EDI
See electronic data interchange.
EDI composite data element
A group of related EDI data elements, such as the elements that make up a name and address.
EDI envelope
The EDI segments and EDI data elements that make up the headers and trailers that enclose EDI transaction sets, functional groups, and interchanges.
EDI loop
A group of consecutive EDI segments that repeat together in an EDI document definition. There is no object type in Data Interchange Services that defines an EDI loop on its own. EDI loops are logically defined within an EDI document definition.
EDI segment
A group of related EDI data elements. An EDI segment is a single line in an EDI document definition, beginning with a segment identifier and ending with a segment terminator delimiter. The EDI data elements in the EDI segment are separated by data element delimiters.
edition
A successive deployment generation of a particular set of versioned artifacts.
editor area
In Eclipse and Eclipse-based products, the area in the workbench window where files are opened for editing.
EIS
See enterprise information system.
EJB
See Enterprise JavaBeans.
EJB container
A container that implements the EJB component contract of the Java EE architecture. This contract specifies a runtime environment for enterprise beans that includes security, concurrency, life cycle management, transaction, deployment, and other services. (Sun) See also EJB server.
EJB context
In enterprise beans, an object that allows an enterprise bean to invoke services provided by the container and to obtain information about the caller of a client-invoked method. (Sun)
EJB factory
An access bean that simplifies the creating or finding of an enterprise bean instance.
EJB home object
In Enterprise JavaBeans (EJB) programming, an object that provides the life cycle operations (create, remove, find) for an enterprise bean. (Sun)
EJB inheritance
A form of inheritance in which an enterprise bean inherits properties, methods, and method-level control descriptor attributes from another enterprise bean that resides in the same group.
EJB JAR file
A Java archive that contains an EJB module. (Sun)
EJB module
A software unit that consists of one or more enterprise beans and an EJB deployment descriptor. (Sun)
EJB object
In enterprise beans, an object whose class implements the enterprise bean remote interface (Sun).
EJB project
A project that contains the resources needed for EJB applications, including enterprise beans; home, local, and remote interfaces; JSP files; servlets; and deployment descriptors.
EJB query
In EJB query language, a string that contains an optional SELECT clause specifying the EJB objects to return, a FROM clause that names the bean collections, an optional WHERE clause that contains search predicates over the collections, an optional ORDER BY clause that specifies the ordering of the result collection, and input parameters that correspond to the arguments of the finder method.
EJB reference
A logical name used by an application to locate the home interface of an enterprise bean in the target operational environment.
EJB server
Software that provides services to an EJB container. An EJB server may host one or more EJB containers. (Sun) See also EJB container.
elasticity mode
A mode that is used to dynamically grow or shrink a cell by adding or removing nodes. Nodes are added when a particular dynamic cluster is not meeting service policies and all possible servers are started. Nodes are removed if they are unused and service policies can be met without them.
elasticity operation
An operation that adds or removes the resources of the application placement controller depending on the defined runtime behavior.
electronic data interchange (EDI)
The exchange of structured electronic data between computer systems according to predefined message standards.
element
  1. 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.
  2. In Java development tools, a generic term that can refer to packages, classes, types, interfaces, methods, or fields.
  3. A component of a document, such as an EDI, XML, or ROD record. An element can be a simple element or a compound element.
embedded server
A catalog service or container server that resides in an existing process and is started and stopped within the process.
emitter factory
A type of factory that handles the details of event transmission such as the event server location, the filter settings, or the underlying transmission mechanism.
empty activity
An activity with no defined implementation that can be used as a place holder in the design stage.
emulator
A facility of the integration test client that enables the emulation of components and references during module testing. Emulators are either manual or programmatic. See also manual emulator, programmatic emulator.
encode
To convert data by the use of a code in such a manner that reconversion to the original form is possible.
end event
An event that ends a process flow and, therefore, does not have outgoing sequence flow paths. Types of end events are message, terminate, and error. See also error end event, message end event, terminate end event.
end node
A node that identifies where a rule flow stops. A rule flow has at least one end node.
endpoint
  1. The system that is the origin or destination of a session.
  2. A JCA application or other client consumer of an event from the enterprise information system.
endpoint listener
The point or address at which incoming messages for a web service are received by a service integration bus.
enqueue
To put a message or item in a queue. See also dequeue.
enrollment
The process of entering and saving user or user group information in a portal.
enterprise application
See Java EE application.
enterprise application project (EAR project)
A structure and hierarchy of folders and files that contain a deployment descriptor and IBM extension document as well as files that are common to all Java EE modules that are defined in the deployment descriptor.
enterprise archive (EAR)
A specialized type of JAR file, defined by the Java EE standard, used to deploy Java EE applications to Java EE application servers. An EAR file contains EJB components, a deployment descriptor, and web archive (WAR) files for individual web applications. See also Java archive, web archive.
enterprise bean
A component that implements a business task or business entity and resides in an EJB container. Entity beans, session beans, and message-driven beans are all enterprise beans. (Sun) See also bean.
enterprise bundle archive
A compressed file, with a .eba extension, that contains or refers to one or more OSGi bundles that are deployed as one OSGi application. See also bundle.
enterprise data grid
A data grid from which data can be accessed from different applications, such as Java or .NET.
Enterprise Information Portal
Software developed by IBM that provides tools for advanced searching, and content customization and summarization.
enterprise information system (EIS)
The applications that compose an enterprise's existing system for handling company-wide information. An enterprise information system offers a well-defined set of services that are exposed as local or remote interfaces or both. (Sun) See also resource adapter.
Enterprise JavaBeans (EJB)
A component architecture defined by Sun Microsystems for the development and deployment of object-oriented, distributed, enterprise-level applications (Java EE).
enterprise service
A service that typically accesses one or more enterprise information systems.
enterprise service bus (ESB)
A flexible connectivity infrastructure for integrating applications and services; it offers a flexible and manageable approach to service-oriented architecture implementation.
entity
  1. 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.
  2. A simple Java class that represents a row in a database table or entry in a map.
entity bean
In EJB programming, an enterprise bean that represents persistent data maintained in a database. Each entity bean carries its own identity. (Sun) See also session bean.
entry breakpoint
A breakpoint set on a component element that is hit before the component element is invoked.
envelope
A combination of header, trailer, and control segments that define the start and end of an individual EDI message. Each envelope in EDI data begins with a particular segment and ends with a particular segment.
environment
A named collection of logical and physical resources used to support the performance of a function.
environment variable
  1. A variable that defines an aspect of the operating environment for a process. For example, environment variables can define the home directory, the command search path, the terminal in use, or the current time zone.
  2. A variable that provides values for each type of environment in which a process will run (for example, development, test, and production environments). A user can set environment variables for each process application.
  3. A variable that specifies how an operating system or another program runs, or the devices that the operating system recognizes.
ephemeral port number
In some TCP/IP implementations, a temporary port number that is assigned to a process for the duration of a call. Ephemeral port numbers are typically assigned to client processes that must provide servers with a client port number so that the server can respond to the correct process.
epoch
The time and date corresponding to 0 in an operating system's clock and time-stamp values. For most versions of the UNIX operating system, the epoch is 00:00:00 GMT, 01 January 1970. System time is measured as the number of seconds past the epoch.
EPV
See exposed process value.
error
A discrepancy between a computed, observed, or measured value or condition and the true, specified, or theoretically correct value or condition.
error end event
An end event that also throws an error. See also end event.
error event
An event that indicates that an error has been caught or thrown.
error intermediate event
An intermediate event that is triggered by a thrown error.
error log stream
A continuous flow of error information that is transmitted using a predefined format.
error start event
A start event that is triggered by a thrown error. An error start event is used only for event subprocesses as an error handling mechanism. See also start event.
ESB
See enterprise service bus.
ESB server
An application server that provides the execution environment for mediation modules in addition to application programs.
escalation
A course of action that runs when a task is not completed satisfactorily within a specific period of time.
ESI
See Edge Side Include.
ESI processor
A processor that supports fragment caching and fragment assembly into full pages.
ESM
See external security manager.
ETL
See extract, transform, and load.
event
  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. 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 alert, message, situation.
  3. An element that is used to represent a change in state.
event catalog
A repository of event metadata used by applications to retrieve information about classes of events and their permitted content.
event context
An activity or group of activities in an expanded subprocess that can be interrupted by an exception (such as by an error intermediate event).
event correlation sphere
The scope of an ECSEmitter method that allows an event consumer to correlate events. Each event includes the identifier of the correlation sphere to which it belongs and the identifier of its parent correlation sphere from the event hierarchy.
event data
In an event message, the part of the message data that contains information about the event (such as the queue manager name, and the application that gave rise to the event).
event database
A database in which events that can be monitored are stored, and which is required to support the persistence of those events.
Event Designer
An event rule application development tool that is integrated into the Eclipse development environment and dedicated to the creation and management of event rule applications.
event emitter
A component of the Common Event Infrastructure that receives events from event sources, completes and validates the events, and then sends events to the event server based on filter criteria. See also Common Event Infrastructure, event source.
event flow
A visual representation of the event processing that will take place when the application is run.
event gateway
A gateway that represents a branching point in the process where the alternative paths that follow the gateway are based on events that occur rather than the evaluation of expressions using process data (as with an exclusive or inclusive gateway).
event group
  1. 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.
  2. A container for inbound events that enables the user to group events without having to create a new monitoring context. Event groups are purely a visual construct and are not represented in the monitor model.
event listener
A type of asynchronous bean that serves as a notification mechanism and through which Java Platform, Enterprise Edition (Java EE) components within a single application can notify each other about various asynchronous events.
event model
The part of the monitor model that contains references to all of the elements of the event definitions used in the monitor model.
event object
A subset of the fields in the definition of an event.
event part
An XML Schema Definition (XSD) type that provides information about the structure of part of an event. A single event definition can have different event parts that are defined by different XML schemas.
event project
A project in which the user can manage event rules and business objects.
event queue
An ordered list of events.
event rule
A piece of business logic that is evaluated by the runtime server when an event is received.
event rule group
A group of event rules that operate together and typically include an otherwise clause.
event run time
A shared, secured component that runs event assets such as business objects, events, and actions.
event source
An object that supports an asynchronous notification server within a single Java virtual machine. Using an event source, the event listener object can be registered and used to implement any interface.
event store
A persistent cache where event records are saved until a polling adapter can process them.
event subscription
A subscription that obtains information about document or folder events that occur on an Enterprise Content Management (ECM) server.
evictor
A component that controls the membership of entries in each BackingMap instance. Sparse caches can use evictors to automatically remove data from the cache without affecting the database.
exception
  1. An event that occurs during the performance of the process that causes a diversion from the normal flow of the process. Exceptions can be generated by intermediate events, such as time, error, or message.
  2. A condition or event that cannot be handled by a normal process.
exception flow
A set of sequence flow paths that originates from an intermediate event that is attached to the boundary of an activity. The process does not traverse this path unless the activity is interrupted by the triggering of a boundary intermediate event. See also normal flow.
exception handler
A set of routines that responds to an abnormal condition. An exception handler is able to interrupt and to resume the normal running of processes.
exception queue
A queue to which messages associated with certain exceptional conditions, such as errors, are routed.
exception report
A WebSphere MQ report message type that is created by a message channel agent when a message is sent to another queue manager, but that message cannot be delivered to the specified destination queue.
exclusive gateway
A gateway that creates alternative paths in a process flow. The exclusive gateway indicates the diversion point in the flow of a process.
exclusive lock
A lock that prevents concurrently executing application processes from accessing database data. See also shared lock.
executable map
A compiled map.
execution component
A component that authorizes the execution of a rule set by the execution unit (XU).
execution object model (XOM)
A model that references implementation objects used in rules.
execution settings
Settings that influence how a component behaves at execution time. These settings are compiled into the map file or system file. Many of these settings compiled into the map can be overridden (or partially overridden) using execution commands and options.
execution trace
A chain of events that is recorded and displayed in a hierarchal format on the Events page of the integration test client.
execution unit (XU)
A Java EE connector or resource adapter that handles the low-level details of rule set execution for a rule execution server.
exit breakpoint
A breakpoint set on a component element that is hit after the component element is invoked.
exit condition
A Boolean expression that controls when processing at a process node is completed.
exit zone
A zone that defines where a tag exits the area. If a tag can no longer be detected within the zone, the item has left the area.
expanded component
A component that displays the sources and targets that are associated with it in the Integration Flow Designer. See also contracted component.
expanded subprocess
A subprocess that exposes its flow detail within the context of its parent process. An expanded subprocess is displayed as a rounded rectangle that is enlarged to display the flow objects within.
expected value
The average value for a given attribute for a population dataset. This value is ultimately used to determine reason code assignment, it is typically used for linear and logistic models where the interaction of variables is controlled.
explicit format
A format that relies upon syntax to separate data objects. Each data object can be identified by its position or by a delimiter in the data. Delimiters will also appear for missing data objects. See also implicit format.
export
An exposed interface from a Service Component Architecture (SCA) module that offers a business service to the outside world. An export has a binding that defines how the service can be accessed by service requesters, for example, as a web service.
export file
  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.
exposed process value (EPV)
A variable that enables process participants to set or change a value while an instance of a process is running. Process participants use EPVs to adjust specific variable values as constants, thereby affecting the flow of a process or task assignment.
expression
  1. A statement about data objects. Expressions are a combination of literals, object names, operators, functions, and map names. Component rules are expressions that evaluate to either TRUE or FALSE. Map rules are expressions that evaluate to data to produce the desired output.
  2. An SQL or XQuery operand or a collection of SQL or XQuery operators and operands that yields a single value.
extended common service area (ECSA)
A major element of z/OS virtual storage above the 16 MB line. This area contains pageable system data areas that are addressable by all active virtual storage address spaces. It duplicates the common system area (CSA) which exists below the 16 MB line.
extended data element
An application-specific element that contains information relevant to an event.
extended messaging
A function of asynchronous messaging where the application server manages the messaging infrastructure and extra standard types of messaging beans are provided to add functionality to that provided by message-driven beans.
Extensible Access Control Markup Language (XACML)
A language used to express policies and rules for controlling access to information.
Extensible Hypertext Markup Language (XHTML)
A reformulation of HTML 4.0 as an application of XML. XHTML is a family of current and future DTDs and modules that reproduce, subset, and extend HTML.
Extensible Markup Language (XML)
A standard metalanguage for defining markup languages that is based on Standard Generalized Markup Language (SGML).
Extensible Stylesheet Language (XSL)
A language for specifying style sheets for XML documents. Extensible Stylesheet Language Transformation (XSLT) is used with XSL to describe how an XML document is transformed into another document.
Extensible Stylesheet Language Transformation (XSLT)
An XML processing language that is used to convert an XML document into another document in XML, PDF, HTML, or other format.
extension
  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.
extension point
In Eclipse, the specification that defines what attributes and values must be declared by an extension. See also extension.
external command
A command that causes the command-line interface (CLI) to generate a message and send it to a service to be processed.
external link
In the Integration Flow Designer, solid lines displayed in a system definition diagram that visually represent the data flow between two map components.
external security manager (ESM)
A security product that performs security checking on users and resources. RACF is an example of an ESM.
external system
A system that exists outside a particular network.
extract, transform, and load (ETL)
The process of collecting data from one or more sources, cleansing and transforming it, and then loading it into a database.
eXtreme Scale grid
A pattern that is used to interact with eXtreme Scale when all of the data and clients are in one process.

F

fabric
A complex network of hubs, switches, adapter endpoints, and connecting cables that support a communication protocol between devices. For example, Fibre Channel uses a fabric to connect devices.
Faces component
One of a collection of user interface components (such as input fields) and data components (representing data such as records in a database) that can be dragged to a Faces JSP file and then bound to each other to build a dynamic web project. See also JavaServer Faces.
Faces JSP file
A file that represents a page in a dynamic web project and contains JavaServer Faces UI and data components. See also JavaServer Faces.
factory
In object-oriented programming, a class that is used to create instances of another class. A factory is used to isolate the creation of objects of a particular class into one place so that new functions can be provided without widespread code changes.
failed event
An object that records the source, destination, description, and time of failure between two service connector components.
failover
An automatic operation that switches to a redundant or standby system in the event of a software, hardware, or network interruption.
FastCGI
See Fast Common Gateway Interface Protocol.
Fast Common Gateway Interface Protocol (FastCGI)
An extension of the Common Gateway Interface that improves performance and allows for greater scalability.
Fastpath mode
A rule execution mode that uses an optimized sequential algorithm.
fast response cache accelerator (FRCA)
A cache that resides in the kernel on AIX and Windows platforms that provides support for caching on multiple web servers and on servers with multiple IP addresses.
fast view
In Eclipse, a view that is opened and closed by clicking a button on the shortcut bar.
fault message
An object that contains status information and details about a problem with a message.
favorite
A library item that a user has marked for easy access.
feature
In Eclipse, a JAR file that is packaged in a form that the update manager accepts and uses to update the platform. Features have a manifest that provides basic information about the content of the feature, which can include plug-ins, fragments and other files.
Federal Information Processing Standard (FIPS)
A standard produced by the National Institute of Standards and Technology when national and international standards are nonexistent or inadequate to satisfy the U.S. government requirements.
federated search
A search capability that enables searches across multiple search services and returns a consolidated list of search results.
federation
The process of combining naming systems so that the aggregate system can process composite names that span the naming systems.
federation domain
A domain that determines the scope over which the federated REST API provides federation support for business processes and human tasks. A federation domain spans one or many BPM environments. See also domain.
feed
A data format that contains periodically updated content that is available to multiple users, applications, or both. See also Rich Site Summary.
FFDC
See first-failure data capture.
field
In object-oriented programming, an attribute or data member of a class.
field constructor
An element that defines the mapping from an event object to a business object.
FileAct directory
A directory that is used exclusively to store files that are involved in FileAct transfers.
FileNet P8 domain
A domain that represents a logical grouping of physical resources and the Content Engine servers that provide access to those resources. Each resource and server belong to only one domain. A server can access any resource in the domain but cannot access any resource that lies outside of the domain.
file serving
A function that supports the serving of static files by web applications.
file splitting
The division of an event file, based on a delimiter or based on size, to separate individual business objects within the file and send them as if they are each an event file to reduce memory requirements.
file store
A type of message store that directly uses files in a file system through the operating system.
File Transfer Protocol (FTP)
In TCP/IP, an application layer protocol that uses TCP and Telnet services to transfer bulk-data files between machines or hosts.
filter
  1. A reusable set of conditions that is used in an event rule to evaluate whether an event matches certain criteria.
  2. A device or program that separates data, signals, or material in accordance with specified criteria. See also servlet filtering.
FIN
The SWIFT store-and-forward message-processing service defining message standards and protocols. See also SWIFTNet FIN.
final action
An action attached to a rule flow task that is performed after the task has been executed.
final score
An additive function of a continuous collection of weighted attributes.
find
See discover.
finder method
In enterprise beans, a method defined in the home interface and invoked by a client to locate an entity bean. (Sun)
fine-grained
Pertaining to viewing an individual object in detail. See also coarse-grained.
fingerprint
See digest code.
finite state machine (FSM)
The theoretical base describing the rules of a service request state and the conditions to state transitions.
FIPS
See Federal Information Processing Standard.
fire
In object-oriented programming, to cause a state transition.
firewall
A network configuration, typically both hardware and software, that prevents unauthorized traffic into and out of a secure network.
first-failure data capture (FFDC)
A problem diagnosis aid that identifies errors, gathers and logs information about these errors, and returns control to the affected runtime software.
fixed syntax
A group whose components have a fixed size. Each component is padded to a fixed size or its minimum and maximum content size values are equal.
fix pack
A cumulative collection of fixes that is made available between scheduled refresh packs, manufacturing refreshes, or releases. It is intended to allow customers to move to a specific maintenance level. See also interim fix, program temporary fix, refresh pack.
flat file
A file stored on a local file system, as opposed to a more complex set of files, such as those in a structured database.
flow
A directional connector between elements in a process, collaboration, or choreography that represents the overall progression of how a process or process segment is performed. There are two types of flows: sequence flow and message flow.
flow object
A graphical object that can be connected to or from a sequence flow. In a process, flow objects are events, activities, and gateways. In a choreography, flow objects are events, choreography activities, and gateways.
folder
  1. A project element that can be used to group rules according to business logic.
  2. A container used to organize objects.
foreign bus
A service integration bus with which a particular service integration bus can exchange messages.
foreign key
In a relational database, a key in one table that references the primary key in another table. See also constraint, primary key.
forest
A collection of one or more Windows 2000 Active Directory trees, organized as peers and connected by two-way transitive trust relationships between the root domains of each tree. All trees in a forest share a common schema, configuration, and Global Catalog. When a forest contains multiple trees, the trees do not form a contiguous namespace.
fork
  1. A point in the process where one sequence flow path is split into two or more paths that run in parallel within the process, allowing multiple activities to run simultaneously rather than sequentially. BPMN uses multiple outgoing sequence flow paths from activities or events or a parallel gateway to perform a fork.
  2. In a rule flow, a node that splits the execution flow into several parallel transitions. The transitions created from a fork do not have conditions.
for loop
A loop that repeats the same sequence of activities a specified number of times.
form
A display screen, printed document, or file with defined spaces for information to be inserted.
form-based login
An authentication process where a user ID and a password are retrieved using an HTML form, and sent to the server over the HTTP or HTTPS protocol.
form bean
In Struts, a class that stores HTML or JSP form data from a submitted client request or that stores input data from a link that a user clicked. The superclass for all form beans is the ActionForm class.
form logout
A mechanism to log out without having to close all web browser sessions.
forward
In Struts, an object that is returned by an action and that has two fields: a name and a path (typically the URL of a JSP). The path indicates where a request is to be sent. A forward can be local (pertaining to a specific action) or global (available to any action).
forwardable credential
A mechanism-specific security credential that is issued to access a resource, which is used to obtain another credential for access to a different resource.
FQDN
See fully qualified domain name.
frame
In hypertext markup language (HTML) coding, a subset of the web browser window.
frameset
An HTML file that defines the layout of a web page that is composed of other, separate HTML files.
FRCA
See fast response cache accelerator.
free-form project
A monitored directory where Java EE artifacts or module files can be created or dropped. As artifacts are introduced or modified in the free-form project, the artifacts are placed in the appropriate Java EE project structures that are dynamically generated in the workspace. The rapid deployment tools generates deployment artifacts required to construct a Java EE-compliant application and deploy that application to a target server. See also monitored directory.
free-form surface
The open area in a visual editor where developers can add and manipulate objects. For example, the Struts application diagram editor provides a free-form surface for representing JSP pages, HTML pages, action mappings, other Struts application diagrams, links from JSP pages, and forwards from action mappings.
FSM
See finite state machine.
FSM instance directory
A directory used by a finite state machine (FSM) to store temporary files, such as shared memory handles and trace files.
FTP
See File Transfer Protocol.
full build
In Eclipse, a build in which all resources within the scope of the build are considered. See also incremental build.
full deployment
Deployment of all the data required to set up the resources for an entire instance. See also delta deployment.
fully qualified domain name (FQDN)
In Internet communications, the name of a host system that includes all of the subnames of the domain name. An example of a fully qualified domain name is rchland.vnet.ibm.com. See also host name.
function
A named group of statements that can be called and evaluated and can return a value to the calling statement.
functional acknowledgment
An electronic acknowledgment returned to the sender to indicate acceptance or rejection of EDI documents.

G

garbage collection
A routine that searches memory to reclaim space from program segments or inactive data.
gate
An entry to or an exit from an area or zone that is monitored by one device
gate condition
A condition on a message being processed that must be fulfilled for a mediation policy to apply.
gateway
  1. An integration pattern that provides format-independent boundary functions that apply to all incoming messages.
  2. A middleware component that bridges Internet and intranet environments during web service invocations.
  3. An element that is used to control the divergence and convergence of sequence flow paths in a process and in a choreography.
  4. A device or program used to connect networks or systems with different network architectures.
  5. An element that controls the divergence and convergence of sequence lines and determines the branching, forking, merging, and joining of paths that a process can take during execution.
gateway destination
A type of service destination that receives messages for gateway services. Gateway destinations are divided into those that are used for request processing and those that are used for reply processing.
gateway queue manager
A cluster queue manager that is used to route messages from an application to other queue managers in the cluster.
gateway service
A web service that is made available through the web services gateway.
General Inter-ORB Protocol (GIOP)
A protocol that Common Object Request Broker Architecture (CORBA) uses to define the format of messages.
General System service
A service that is used to coordinate other services or to manipulate variable data. See also service.
generic object
An object that is used in API calls and XPATH expressions to refer to concepts, custom entities, or collections. For example, the XPATH expression /WSRR/GenericObject will retrieve all concepts from WebSphere Service Registry and Repository.
generic server
A server or process, such as a Java server, a C or C++ server or process, a CORBA server, or a Remote Method Invocation (RMI) server, that is managed in the product administrative domain and supports the product environment.
generic server cluster
A group of remote servers that need routing by the proxy server.
getter method
A method whose purpose is to get the value of an instance or class variable. This allows another object to find out the value of one of its variables. See also setter method.
GIOP
See General Inter-ORB Protocol.
global
  1. Pertaining to information available to more than one program or subroutine. See also local.
  2. 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.
global asset
A library item that is available to the entire process application in which it is located. For example, environment variables for a process application are global assets and can be called from any implementation.
global attribute
In XML, an attribute that is declared as a child of the schema element rather than as part of a complex type definition. Global attributes can be referenced in one or more content models using the ref attribute.
global element
In XML, an element that is declared as a child of the schema element rather than as part of a complex type definition. Global elements can be referenced in one or more content models using the ref attribute.
global instance identifier
A globally unique identifier that is generated either by the application or by the emitter and is used as a primary key for event identification.
global security
Pertains to all applications running in the environment and determines whether security is used, the type of registry used for authentication, and other values, many of which act as defaults.
global transaction
A recoverable unit of work performed by one or more resource managers in a distributed transaction environment and coordinated by an external transaction manager.
global transaction management (GTX)
The monitoring of transactions that can include operations on two or more different data sources. This feature enables databases or servers to be returned to a pre-transaction state if an error occurs. Either all databases and servers are updated or none are. The advantage of this strategy is that databases and servers remain synchronized and data remains consistent.
global variable
A variable that is used to hold and manipulate values assigned to it during translation and that is shared across maps and across document translations. One of the three types of variables supported by the Data Interchange Services mapping command language.
Globus certificate service
An online service that issues low-quality GSI certificates for people who want to experiment with Grid (or distributed) computing components that require certificates but have no other means to acquire certificates. The Globus certificate service is not a true CA. Certificates from the Globus certificate service are intended solely for experimentation. Use caution when using these certificates, for they are not intended for use in production systems. See also certificate authority.
glue code
A segment of code that is used to connect two pre-existing pieces of code and retain full functionality. See also API stub.
GMT
See Greenwich mean time.
governance
The decision-making processes in the administration of an organization. The rights and responsibilities of these processes are typically shared among the organization's participants, especially the management and stakeholders.
governance lifecycle
A life cycle that represents the states and transitions that can exist in SOA deployment.
governance policy validator
A sample validator that enables the user to control the operations that can be performed on specific entities based on the metadata that is attached to those entities.
governance process
A process that ensures that compliance and operational polices are enforced, and that change occurs in a controlled fashion and with appropriate authority as envisioned by the business design.
governance state
A state defined within the governance life cycle, for example, "created", "planned", or "specified".
governance web service
A service that retrieves information and runs actions, relating to the governance of objects, from a web service client.
governed collection
Group of objects on which an operation may be performed automatically, as a result of an initial operation.
governed entity
Controls visibility of artifacts as well as controlling who can perform which actions on specific governed entities.
GPM
See Graphical Process Modeler.
grammar
A document type definition (DTD) or schema providing a structured format used for successful processing by the trace service.
Graphical Process Modeler (GPM)
A stand-alone graphical interface tool that is used in Sterling B2B Integrator to create and modify business processes. The GPM converts the graphical representation of business processes to well-formed BPML (source code) and saves the effort of writing code.
Greenwich mean time (GMT)
The mean solar time at the meridian of Greenwich, England.
group
  1. A complex data object that consists of components.
  2. A set of elements that is associated with the same category.
  3. A collection of users who can share access authorities for protected resources.
GTX
See global transaction management.

H

HA
See high availability.
HADR
See high availability disaster recovery.
HA group
A collection of one or more members used to provide high availability for a process.
handle
In the Java EE specification, an object that identifies an enterprise bean. A client may serialize the handle, and then later deserialize it to obtain a reference to the enterprise bean. (Sun)
handler
In web services, a mechanism for processing service content and extending the function of a JAX-RPC runtime system.
handshake
The exchange of messages at the start of a Secure Sockets Layer session that allows the client to authenticate the server using public key techniques (and, optionally, for the server to authenticate the client) and then allows the client and server to cooperate in creating symmetric keys for encryption, decryption, and detection of tampering.
HA policy
A set of rules that is defined for an HA group that dictate whether zero (0), or more members are activated. The policy is associated with a specific HA group by matching the policy match criteria with the group name.
hash
In computer security, a number generated from a string of text that is used to ensure that transmitted messages arrived intact.
hashed method authentication code (HMAC)
A mechanism for message authentication that uses cryptographic hash functions.
headless
Pertains to a program or application that can run without a graphical user interface or, in some cases, without any user interface at all. Headless operation is often used for network servers or embedded systems.
health
The general condition or state of the database environment.
health controller
An autonomic manager that constantly monitors defined health policies. When a specified health policy condition does not exist in the environment, the health controller verifies that configured actions correct the error.
health policy
A set of rules that an administrator can define and use to monitor conditions and take actions when the conditions occur.
heap
In Java programming, a block of memory that the Java virtual machine (JVM) uses at run time to store Java objects. Java heap memory is managed by a garbage collector, which automatically de-allocates Java objects that are no longer in use.
heartbeat
A signal that one entity sends to another to convey that it is still active.
HFS
See hierarchical file system.
hidden widget
A fully functional widget that transforms business data so that another widget can use this data. A hidden widget is not displayed on a page, unless all widgets are displayed. When a hidden widget is made visible, the widget has a dashed frame.
hierarchical
Pertaining to data that is organized on computer systems using a hierarchy of containers, often called folders (directories) and files. In this scheme, folders can contain other folders and files. The successive containment of folders within folders creates the levels of organization, which is the hierarchy.
hierarchical file system (HFS)
A system for organizing files in a hierarchy, as in a UNIX system.
hierarchical property
An extended rule property whose values are organized into a hierarchy.
high availability
  1. 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.
  2. 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.
high availability disaster recovery (HADR)
A disaster recovery solution that uses log shipping and provides data to a standby system if a partial or complete site failure occurs on a primary system.
high availability file system
A cluster file system that can be used for component redundancy to provide continued operations during failures.
high availability manager
A framework within which core group membership is determined and status is communicated between core group members.
high-level qualifier (HLQ)
A qualifier that groups tables together with other tables that have different names, but the same qualifier.
HLQ
See high-level qualifier.
HMAC
See hashed method authentication code.
home interface
In enterprise beans, an interface that defines zero or more create and remove methods for a session bean or zero or more create, finder, and remove methods for an entity bean. See also remote interface.
home method
A method in the home interface that is used by a client to create, locate, and remove instances of enterprise beans.
home page
The top-level web page of a portal.
homogeneous rule
A rule for which the conditions are written on the same type and number of objects.
hook
A location in a compiled program where the compiler has inserted an instruction that allows programmers to interrupt the program (by setting breakpoints) for debugging purposes.
horizontal scaling
A topology in which more than one application server running on multiple computing nodes is used to run a single application.
host
  1. In performance profiling, a machine that owns processes that are being profiled. See also server.
  2. 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 client, server.
host name
  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. See also fully qualified domain name, IP address.
  2. The network name for a network adapter on a physical machine in which the node is installed.
host system
An enterprise mainframe computer system that hosts 3270 applications. In the 3270 terminal service development tools, the developer uses the 3270 terminal service recorder to connect to the host system.
hot deployment
The process of adding new components to a running server without stopping and restarting the application server or application. See also dynamic reloading.
hot directory
See monitored directory.
hot servant region
A servant region that had a request dispatched to it previously and now has available threads.
HTTP channel
A type of channel within a transport chain that provides client applications with persistent HTTP connections to remote hosts that are either blocked by firewalls or require an HTTP proxy server. An HTTP channel is used to exchange application data in the body of an HTTP request and an HTTP response that is sent to and received from a remote server.
HTTP over SSL (HTTPS)
A web protocol for secure transactions that encrypts and decrypts user page requests and pages returned by the web server.
HTTPS
  1. See HTTP over SSL.
  2. See Hypertext Transfer Protocol Secure.
human task
An interaction between people and business processes or services. See also inline task, stand-alone task.
human workflow
A business process flow that includes human interactions.
Hypertext Transfer Protocol Secure (HTTPS)
An Internet protocol that is used by web servers and web browsers to transfer and display hypermedia documents securely across the Internet.
hypervisor
A program or a portion of Licensed Internal Code that allows multiple instances of operating systems to run simultaneously on the same hardware.

I

IAMS
See inbound application message store.
ICAP
See Internet Content Adaptation Protocol.
ICMP
See Internet Control Message Protocol.
IDE
See integrated development environment.
identifier
  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.
identifier attribute
An attribute that can be assigned to one component to identify a collection of components, when creating type trees and defining components of a group. An identifier attribute is used during data validation to determine whether a data object exists.
identity
The data that represents a person and that is stored in one or more repositories.
identity assertion
The invocation credential that is asserted to the downstream server. This credential can be set as the originating client identity, the server identity, or another specified identity, depending on the RunAs mode for the enterprise bean.
identity token
A token that contains the invocation credential identity, which with the client authentication token are required by the receiving server to accept the asserted identity.
IDL
See Interface Definition Language.
if-then rule
A rule in which the action (then part) is performed only when the condition (if part) is true. See also action rule, rule set.
IIOP
See Internet Inter-ORB Protocol.
ILOG Rule Language (IRL)
An executable rule language. Rules in ILOG Rule Language (IRL) can reference any execution object and invoke methods on these objects.
i-mode
An Internet service for wireless devices.
implicit format
A format that defines a group type whose data objects are distinguishable by content, not syntax. Implicit format relies on the properties of the component types. Unlike explicit format, if delimiters separate data objects, they do not appear for missing data objects. See also explicit format.
import
  1. 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.
  2. A development artifact that imports a service that is external to a module. See also import file.
import file
A file created during the development process for outbound operations that contains the configuration settings for outbound processing. See also import.
IMS
See Information Management System.
IMS command
A request from a terminal or AO (automated operator) to perform a specific IMS service, such as altering system resource status or displaying specific system information.
IMS Connect
The product that runs on a z/OS platform and through which IMS Connector for Java communicates with IMS. IMS Connect uses OTMA to communicate with IMS. See also Open Transaction Manager Access.
IMS conversation
  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.
IMS transaction
A specific set of input data that triggers the execution of a specific process or job. A transaction is a message destined for an IMS application program.
IMS transaction code
A 1- to 8-character alphanumeric code that invokes an IMS message processing program.
inbound
In communication, pertaining to data that is received from the network. See also outbound.
inbound application message store (IAMS)
A message store, implemented by means of the database table DNF_IAMS, in which WebSphere BI for FN stores messages that are received from remote destinations (OSN messages).
inbound authentication
The configuration that determines the type of accepted authentication for inbound requests.
inbound event
A declaration that a monitoring context or KPI context will accept a specific event at run time.
inbound port
A type of port that takes a message that is received at an endpoint listener and passes it to the service integration bus for forwarding to the appropriate inbound service.
inbound processing
The process by which changes to business information in an enterprise information system (EIS) are detected, processed, and delivered to a runtime environment by a JCA Adapter. An adapter can detect EIS changes by polling an event table or by using an event listener.
inbound service
The external interface for a service that is provided by your own organization and hosted in a location that is directly available through the service destination.
inbound transport
Network ports in which a server listens for incoming requests.
inclusive gateway
A gateway that creates alternative or parallel paths in a process flow where all outgoing sequence flow condition expressions are evaluated independently.
incremental build
In Eclipse, a build in which only resources that have changed since the last build are considered. See also full build.
index
A set of pointers that is logically ordered by the values of a key. Indexes provide quick access to data and can enforce uniqueness of the key values for the rows in the table.
industry capability map
A logical view of the business competencies that an industry needs to process.
information center
A collection of information that provides support for users of one or more products, can be launched separately from the product, and includes a list of topics for navigation and a search engine.
Information Management System (IMS)
Any of several system environments that have a database manager and transaction processing that can manage complex databases and terminal networks.
inheritance
An object-oriented programming technique in which existing classes are used as a basis for creating other classes. Through inheritance, more specific elements incorporate the structure and behavior of more general elements.
initial action
An action attached to a rule flow task that is performed before the task is executed.
initial CDD
A customization definition document (CDD) to which placeholders have not yet been added.
initial context
Starting point in a namespace.
initialization point
A user-defined constant or variable used to initialize the attributes of an object.
initial option set
For a scenario that uses an option set group, the first option set that the scenario used. The initial option set is used to determine when all of the option sets of an option set group have been used at least once.
initial reference
A well-known reference associated with an identifier.
initiator
A syntax object in a data stream that signals the beginning of a data object. For example, if a record begins with an asterisk (*), the asterisk would be the record’s initiator.
inline task
A unit of work that is defined within an implementation of a business process. See also human task, stand-alone task.
inout parameter
A parameter value that is provided as input to a rule set when it is executed. It can be modified by the execution process and is provided as output when the execution is completed.
in parameter
A parameter value that is provided as input to the rule set at execution time.
input activity
The origin of the process that is the source of the invocation data of the entire process.
input card
In the Map Designer, a component that contains the complete definition of input for the map, including information such as source identification, retrieval specifics, and the behavior that should occur during processing.
input node
  1. The point where a service message from a source enters the request flow.
  2. A message flow node that represents a source of messages for a message flow or subflow.
input response node
The end point for a mediation response flow from which the service message object is sent to the source.
input terminal node
A primitive through which a message is received by a subflow. Each input terminal node is represented as an input terminal of the corresponding subflow node.
INS
See Interoperable Naming Service.
insertion
The action of adding a new object into the object set provided to the rule engine for execution.
installation image
A copy of the software, in backup format, that the user is installing, as well as copies of other files the system needs to install the software product.
installation package
An installable unit of a software product. Software product packages are separately installable units that can operate independently from other packages of that software product.
installation target
The system on which selected installation packages are installed.
instance
  1. An active process element, for example, the performance of a process.
  2. A set of servers that share a common runtime database, plus their corresponding brokers and queue managers.
  3. A specific occurrence of an object that belongs to a class. See also object.
instance document
An XML document that conforms to a particular schema.
instantiate
To represent an abstraction with a concrete instance.
integrated development environment (IDE)
A set of software development tools, such as source editors, compilers, and debuggers, that are accessible from a single user interface.
integration broker
A component that integrates data among heterogeneous applications. An integration broker typically provides various services that can route data, as well as a repository of rules that govern the integration process, connectivity to various applications, and administrative capabilities that facilitate integration.
integration service
A service that performs data translation and flat-file conversations, including fax services. See also Advanced Integration service, service.
intelligent page
A page that is based on platform capabilities that deliver a unified presentation and architecture, rapid assembly of multiple component types including feeds, widgets, and portlets, and rich media that provide access to dynamic web pages, enabling real-time web-page analysis and channel-delivery analysis.
interaction endpoint
A service requester or provider.
interaction pattern
A communication method for sending or receiving messages in a service interaction. Examples of interaction patterns include request/reply, one-way interaction, and publish/subscribe.
interactive session
A work session in which there is an exchange of communication between a 3270 application and the 3270 terminal service recorder.
Interactive System Productivity Facility (ISPF)
An IBM licensed program that serves as a full-screen editor and dialog manager. Used for writing application programs, it provides a means of generating standard screen panels and interactive dialogs between the application programmer and the terminal user. See also Time Sharing Option.
interactive view
In 3270 terminal services, real-time access to a host application in the 3270 terminal service recorder editor.
interchange
The exchange of information between trading partners. Also a set of documents grouped together, such as EDI documents enclosed within an EDI envelope.
interface
A collection of operations that are used to specify a service of a class or a component. See also class, port type.
Interface Definition Language (IDL)
In CORBA, a declarative language that is used to describe object interfaces, without regard to object implementation.
interface map
A map that resolves and reconciles the differences between the interfaces of interacting components. There are two levels of interface maps: operation mappings and parameter mappings.
interim fix
A certified fix that is generally available to all customers between regularly scheduled fix packs, refresh packs, or releases. See also fix pack, refresh pack.
intermediate CDD
A customization definition document (CDD) to which placeholders have been added, but for which placeholder values have not yet been specified.
intermediate event
An event that occurs after a process has been started, affecting the flow of the process by showing where messages and delays are expected and distributing the normal flow through exception handling. Intermediate event types are message, timer, tracking, and error. See also catching message intermediate event, message intermediate event, throwing message intermediate event, timer event, tracking intermediate event.
internal command
A command that is processed directly by and that controls the command-line interface (CLI).
internal link
In the Integration Flow Designer, a solid line displayed by an expanded map component that visually represents the source and target of the map.
Internet Content Adaptation Protocol (ICAP)
A high-level protocol for requesting services from an Internet-based server.
Internet Control Message Protocol (ICMP)
An Internet protocol that is used by a gateway to communicate with a source host, for example, to report an error in a datagram.
Internet Inter-ORB Protocol (IIOP)
A protocol used for communication between Common Object Request Broker Architecture (CORBA) object request brokers. See also Common Object Request Broker Architecture.
Internet Protocol (IP)
A protocol that routes data through a network or interconnected networks. This protocol acts as an intermediary between the higher protocol layers and the physical network. See also Transmission Control Protocol.
interoperability
The ability of a computer or program to work with other computers or programs.
Interoperable Naming Service (INS)
A program that supports the configuration of the Object Request Broker (ORB) administratively to return object references.
interoperable object reference (IOR)
An object reference with which an application can make a remote method call on a CORBA object. This reference contains all the information needed to route a message directly to the appropriate server.
interval
The defining range or ranges of an attributes value. Intervals are a one-to-many relationship to the attributes utilized in the scorecard.
introspector
In Java, a class (java.beans.Introspector) that provides a standard way for tools to learn about the properties, events, and methods supported by a target bean. Introspectors follow the JavaBeans specification.
invocation
The activation of a program or procedure.
invocation credential
An identity with which to invoke a downstream method. The receiving server requires this identity with the sending server identity to accept the asserted identity.
invoker attribute
An assembly property for a web module that is used by the servlet that implements the invocation behavior.
IOR
See interoperable object reference.
IP
See Internet Protocol.
IP address
A unique address for a device or logical unit on a network that uses the Internet Protocol standard. See also host name.
IP group
A range of IP addresses that can be selected for use with specific hypervisors.
IP sprayer
A device that is located between inbound requests from the users and the application server nodes that reroutes requests across nodes.
IRL
See ILOG Rule Language.
ISPF
See Interactive System Productivity Facility.
item
  1. A simple data object that does not consist of other objects. An item type is represented by a blue dot next to the type name in the type tree.
  2. An entity within a location that can be equipped with tags and whose positions can therefore be tracked, such as an asset or person.
iteration
See loop.
iterator
A class or construct that is used to step through a collection of objects one at a time.
iWidget
A browser-oriented component, potentially extending a server-side component, that provides either a logical service to the page or a visualization for the user (typically related to a server-side component or a configured data source).
iWidget specification
An open-source specification upon which Business Space widgets are based.

J

J2C
See J2EE Connector architecture.
J2EE
  1. See Java 2 Platform, Enterprise Edition.
  2. See Java Platform, Enterprise Edition.
J2EE Connector architecture (J2C)
See Java EE Connector Architecture.
J2SE
See Java 2 Platform, Standard Edition.
JAAS
See Java Authentication and Authorization Service.
JAF
See JavaBeans Activation Framework.
JAR
See Java archive.
JAR file
A Java archive file. See also Java archive.
JASPI
See Java Authentication for SPI for containers.
Java
An object-oriented programming language for portable interpretive code that supports interaction among remote objects. Java was developed and specified by Sun Microsystems, Incorporated.
Java 2 Connector security
See Java Connector security.
Java 2 Platform, Enterprise Edition (J2EE)
See Java Platform, Enterprise Edition.
Java 2 Platform, Standard Edition (J2SE)
See Java Platform, Standard Edition.
Java API for XML (JAX)
A set of Java-based APIs for handling various operations involving data defined through Extensible Markup Language (XML).
Java API for XML-based RPC (JAX-RPC, JSR 101)
A specification that describes application programming interfaces (APIs) and conventions for building web services and web service clients that use remote procedure calls (RPC) and XML.
Java API for XML Web Services (JAX-WS)
The next-generation web services programming model that is based on dynamic proxies and Java annotations.
Java Architecture for XML Binding (JAXB)
A Java binding technology that supports transformation between schema and Java objects, as well as between XML instance documents and Java object instances.
Java archive (JAR)
A compressed file format for storing all of the resources that are required to install and run a Java program in a single file. See also enterprise archive, JAR file, web archive.
Java Authentication and Authorization Service (JAAS)
In Java EE technology, a standard API for performing security-based operations. Through JAAS, services can authenticate and authorize users while enabling the applications to remain independent from underlying technologies.
Java Authentication for SPI for containers (JASPI)
A specification that supports third-party security providers handling the Java Platform, Enterprise Edition (Java EE) authentication of HTTP request and response messages that are sent to web applications.
JavaBeans
As defined for Java by Sun Microsystems, a portable, platform-independent, reusable component model. See also bean.
JavaBeans Activation Framework (JAF)
A standard extension to the Java platform that determines arbitrary data types and available operations and can instantiate a bean to run pertinent services.
Java class
A class that is written in the Java language.
Java Command Language
A scripting language for the Java environment that is used to create web content and to control Java applications.
Java Connector security
An architecture designed to extend the end-to-end security model for Java EE-based applications to include enterprise information systems (EIS).
Java Database Connectivity (JDBC)
An industry standard for database-independent connectivity between the Java platform and a wide range of databases. The JDBC interface provides a call level interface for SQL-based and XQuery-based database access.
Java Development Kit (JDK)
See Java SE Development Kit.
Javadoc
  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.
Java EE
See Java Platform, Enterprise Edition.
Java EE application
Any deployable unit of Java EE functionality. This unit can be a single module or a group of modules packaged into an enterprise archive (EAR) file with a Java EE application deployment descriptor. (Sun)
Java EE Connector Architecture (JCA)
A standard architecture for connecting the Java EE platform to heterogeneous enterprise information systems (EIS).
Java EE server
A runtime environment that provides EJB or web containers.
Java file
An editable source file (with .java extension) that can be compiled into bytecode (a .class file).
JavaMail API
A platform and protocol-independent framework for building Java-based mail client applications.
Java Management Extensions (JMX)
A means of doing management of and through Java technology. JMX is a universal, open extension of the Java programming language for management that can be deployed across all industries, wherever management is needed.
Java Message Service (JMS)
An application programming interface that provides Java language functions for handling messages.
Java Naming and Directory Interface (JNDI)
An extension to the Java platform that provides a standard interface for heterogeneous naming and directory services.
Java Persistence API
An object/relational mapping facility to Java developers for managing relational data in Java applications.
Java platform
A collective term for the Java language for writing programs; a set of APIs, class libraries, and other programs used in developing, compiling, and error-checking programs; and a Java virtual machine which loads and runs the class files. (Sun)
Java Platform, Enterprise Edition (J2EE, Java EE)
An environment for developing and deploying enterprise applications, defined by Sun Microsystems Inc. The Java EE platform consists of a set of services, application programming interfaces (APIs), and protocols that provide the functionality for developing multitiered, web-based applications. (Sun)
Java Platform, Standard Edition (Java SE)
The core Java technology platform. (Sun)
Java project
In Eclipse, a project that contains compilable Java source code and is a container for source folders or packages.
Java project for Rules
A predefined Java project for Eclipse that contains a single, runnable main class to execute rules contained in a rule project.
Java runtime environment (JRE)
A subset of a Java developer kit that contains the core executable programs and files that constitute the standard Java platform. The JRE includes the Java virtual machine (JVM), core classes, and supporting files.
JavaScript
A web scripting language that is used in both browsers and web servers. (Sun)
JavaScript Object Notation (JSON)
A lightweight data-interchange format that is based on the object-literal notation of JavaScript. JSON is programming-language neutral but uses conventions from languages that include C, C++, C#, Java, JavaScript, Perl, Python.
Java SE
See Java Platform, Standard Edition.
Java Secure Socket Extension (JSSE)
A Java package that enables secure Internet communications. It implements a Java version of the Secure Sockets Layer (SSL) and Transport Layer Security (TSL) protocols and supports data encryption, server authentication, message integrity, and optionally client authentication.
Java SE Development Kit
The name of the software development kit that Sun Microsystems provides for the Java platform.
JavaServer Faces (JSF)
A framework for building web-based user interfaces in Java. Web developers can build applications by placing reusable UI components on a page, connecting the components to an application data source, and wiring client events to server event handlers. See also Faces component, Faces JSP file, JavaServer Pages.
JavaServer Pages (JSP)
A server-side scripting technology that enables Java code to be dynamically embedded within web pages (HTML files) and run when the page is served, in order to return dynamic content to a client. See also JavaServer Faces, JSP file, JSP page.
Java Specification Request (JSR)
A formally proposed specification for the Java platform.
Java virtual machine (JVM)
A software implementation of a processor that runs compiled Java code (applets and applications).
Java virtual machine Profiler Interface (JVMPI)
A profiling tool that supports the collection of information, such as data about garbage collection and the Java virtual machine (JVM) API that runs the application server.
JAX
See Java API for XML.
JAXB
See Java Architecture for XML Binding.
JAX-RPC
See Java API for XML-based RPC.
JAX-WS
See Java API for XML Web Services.
JCA
See Java EE Connector Architecture.
JCA contract
A collaborative agreement between an application server and an EIS system-level. A JCA contract indicates how to keep all mechanisms (for example, transactions, security, and connection management) transparent from the application components.
JCL
See job control language.
JDBC
See Java Database Connectivity.
JDBC connection filter
A control that limits the amount of data that is transferred during the JDBC metadata load. The filter enhances performance.
JDK
See Java Development Kit.
Jetspeed
The open-source portal that is part of the Jakarta project by Apache.
JMS
See Java Message Service.
JMS data binding
A data binding that provides a mapping between the format used by an external JMS message and the Service Data Object (SDO) representation used by a Service Component Architecture (SCA) module.
JMS destination
An object in which message queuing applications use the Java Message Service specification to put messages, and from which they can get messages.
JMS provider
A messaging engine that implements the JMS messaging specification, for example WebSphere MQ or SIBus.
JMX
See Java Management Extensions.
JNDI
See Java Naming and Directory Interface.
job class
Any one of a number of job categories that can be defined.
job control language (JCL)
A command language that identifies a job to an operating system and describes the job requirements. See also xJCL.
job group security
A security model in which groups of users can access and control a common set of jobs owned by that group.
job log
A record of requests submitted to the system by a job, the messages related to the requests, and the actions performed by the system on the job. The job log is maintained by the system program.
job management console
A stand-alone web interface that is used to submit, monitor, view, and manage jobs.
job manager
An administrative process that manages multiple base application servers or network deployment cells.
job scheduler
A component that provides all job-management functions. A job scheduler maintains a history of all jobs and usage data for jobs that have run.
job step
The execution of a computer program explicitly identified by a job control statement. A job may specify that several job steps be executed. [A]
join
  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. A point in the process where two or more parallel sequence flow paths are combined into one sequence flow path. BPMN uses a parallel gateway to perform a join.
  4. In a rule flow, a node that combines all the transitions created from a fork.
join condition
A condition that determines whether to run the next activity.
join failure
A fault that is thrown if a join condition cannot be evaluated.
JRas
A toolkit that consists of a set of Java packages that enable developers to incorporate message logging and trace facilities into Java applications.
JRE
See Java runtime environment.
JSF
See JavaServer Faces.
JSON
See JavaScript Object Notation.
JSP
See JavaServer Pages.
JSP file
A scripted HTML file that has a .jsp extension and allows for the inclusion of dynamic content in web pages. A JSP file can be directly requested as a URL, called by a servlet, or called from within an HTML page. See also JavaServer Pages, JSP page.
JSP page
A text-based document using fixed template data and JSP elements that describes how to process a request to create a response. (Sun) See also JavaServer Pages, JSP file.
JSR
See Java Specification Request.
JSR 101
See Java API for XML-based RPC.
JSSE
See Java Secure Socket Extension.
junction
A logical connection created to establish a path from one server to another.
JUnit
An open-source regression testing framework for unit-testing Java programs.
JVM
See Java virtual machine.
JVMPI
See Java virtual machine Profiler Interface.
Jython
An implementation of the Python programming language that is integrated with the Java platform.

K

kernel
The part of an operating system that contains programs for such tasks as input/output, management and control of hardware, and the scheduling of user tasks.
key
  1. Information that characterizes and uniquely identifies the real-world entity that is being tracked by a monitoring context.
  2. A cryptographic mathematical value that is used to digitally sign, verify, encrypt, or decrypt a message. See also private key, public key.
key attribute
An attribute that is used in warehouse aggregation to identify rows of data that represent the same object.
key class
In EJB query language, a class that is used to create or find an entity bean. It represents the identity of the entity bean, corresponding to the primary-key columns of a row in a relational database.
key database
In security, a storage object, either a file or a hardware cryptographic card, where identities and private keys are stored for authentication and encryption purposes. Some key databases also contain public keys. See also stash file.
key database file
See key ring.
Keyed-Hashing Message Authentication Code
A mechanism for message authentication that uses cryptographic hash functions.
key field
In EJB query language, a container-managed field in an entity bean that corresponds to one of the primary-key columns of a row in a relational database. Each key field is a member of the entity bean key class.
key file
See key ring.
key locator
A mechanism that retrieves the key for XML signing, XML digital signature verification, XML encryption, and XML decryption.
key pair
In computer security, a public key and a private key. When the key pair is used for encryption, the sender uses the public key to encrypt the message, and the recipient uses the private key to decrypt the message. When the key pair is used for signing, the signer uses the private key to encrypt a representation of the message, and the recipient uses the public key to decrypt the representation of the message for signature verification.
key performance indicator (KPI)
A quantifiable measure that is designed to track one of the critical success factors of a business process.
key ring
In computer security, a file that contains public keys, private keys, trusted roots, and certificates.
keystore
In security, a file or a hardware cryptographic card where identities and private keys are stored, for authentication and encryption purposes. Some keystores also contain trusted or public keys. See also certificate signing request, truststore.
keystring
Additional specification of the entry within a naming service.
key-value pair
Information that is expressed as a paired set of parameters. For example, if you want to express that the specific sport is football, this data can be expressed as key=sport and value=football.
keyword
One of the predefined words of a programming language, artificial language, application, or command. See also parameter.
keyword parameter
A parameter that consists of a keyword followed by one or more values.
KPI
See key performance indicator.
KPI context
A container for key performance indicators (KPIs) and their associated triggers and events.
KPI model
The part of the monitor model that contains the KPI contexts, which in turn contain key performance indicators and their associated triggers and events.

L

label
A node in a portal that cannot contain any content, but can contain other nodes. Labels are used primarily to group nodes in the navigation tree.
lane
A container in a pool for the activities and events that take place during process execution. A lane is designated by a user and typically represents departments in a business organization. For example, a Call Center lane would include all activities to be handled by Call Center personnel during process execution.
language code
A two character (ISO 639-1) or three letter (ISO 639-2) abbreviation for a language. For example: en or eng for English. Country codes and language codes together form the basis for locale names.
large object (LOB)
A data object whose data type supports the storage and manipulation of more data than most other data types.
late bind
To connect one process to another process so that the connection is resolved dynamically in the runtime environment and the calling process uses the currently valid version of the process that it is invoking.
late binding
The connection between two processes that is resolved dynamically in the runtime environment. As a result, the calling process uses up the currently valid version of the process that it is invoking.
LAU
See local authentication.
launch configuration
A mechanism for defining and saving different workbench configurations that can be launched separately. Configurable options include run and debug settings.
launchpad
A graphical interface for launching the product installation wizard.
layout box
In Page Designer, a control that web designers can use to move text and images within the page. Layout boxes can be stacked or aligned by using a grid.
layout manager
In programming graphical user interfaces, an object that controls the size and position of Java components within a container. The Java platform supplies several commonly used layout managers for AWT and Swing containers.
lazy authentication
The process whereby the security run time environment obtains the required authentication data when the Java client accesses a protected enterprise bean for the first time.
LDAP
See Lightweight Directory Access Protocol.
LDAP directory
A type of repository that stores information on people, organizations, and other resources and that is accessed using the LDAP protocol. The entries in the repository are organized into a hierarchical structure, and in some cases the hierarchical structure reflects the structure or geography of an organization.
leaf
In a tree, an entry or node that has no children.
library
  1. A collection of model elements, including business items, processes, tasks, resources, and organizations.
  2. In Business Process Management, 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.
lifecycle
One complete pass through the four phases of software development: inception, elaboration, construction and transition.
light path diagnostics
A system of LEDs that are above the control panel and on various internal components of the compute node.
Lightweight Directory Access Protocol (LDAP)
An open protocol that uses TCP/IP to provide access to directories that support an X.500 model and that does not incur the resource requirements of the more complex X.500 Directory Access Protocol (DAP). For example, LDAP can be used to locate people, organizations, and other resources in an Internet or intranet directory.
Lightweight Third Party Authentication (LTPA)
  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.
link
A line or arrow that connects activities in a process. A link passes information between activities and determines the order in which they run.
link aggregation
The grouping of physical network interface cards, such as cables or ports, into a single logical network interface. Link aggregation is used to increase bandwidth and network availability. See also aggregate interface.
link name
A name defined in the deployment descriptor of the encompassing application.
link pack area (LPA)
The portion of virtual storage below 16 MB that contains frequently used modules.
listener
A program that detects incoming requests and starts the associated channel.
listener port
An object that defines the association between a connection factory, a destination, and a deployed message-driven bean. Listener ports simplify the administration of the associations between these resources.
literal
A symbol or a quantity in a source program that is itself data, rather than a reference to data.
Literal XML
An encoding style for serializing data over SOAP protocol. Literal XML is based on an XML schema instance.
little endian
A format for storage or transmission of binary data in which the least significant value is placed first. See also big endian.
load balancing
The monitoring of application servers and management of the workload on servers. If one server exceeds its workload, requests are forwarded to another server with more capacity.
loader
A component that reads data from and writes data to a persistent store.
LOB
See large object.
local
  1. Pertaining to an element that is available only in its own process. See also global.
  2. 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.
local authentication (LAU)
The process of validating a user identity to the system according to the local operating system account to which the user logged in. If the user is authenticated, the user is mapped to a principal.
local database
A database that is located on the workstation in use. See also remote database.
locale
A setting that identifies language or geography and determines formatting conventions such as collation, case conversion, character classification, the language of messages, date and time representation, and numeric representation.
local history
Copies of files that are saved in the workbench in order to compare the current version with previous versions. Subject to configurable preferences, the workbench updates the local history each time an editable file is saved.
local home interface
In EJB programming, an interface that specifies the methods used by local clients for locating, creating, and removing instances of enterprise bean classes. See also remote home interface.
local queue
A queue that belongs to the local queue manager. A local queue can contain a list of messages waiting to be processed. See also remote queue.
local queue manager
The queue manager to which the program is connected and that provides message queuing services to the program. See also remote queue manager.
local server
A predefined server that designates the current computer to run the Integration Flow Designer.
local transaction
A recoverable unit of work managed by a resource manager and not coordinated by an external transaction manager.
local transaction containment (LTC)
A bounded scope that is managed by the container to define the application server behavior in an unspecified transaction context.
location
A physical space that is being monitored. A location can contain many areas. See also area.
location service daemon
A component of the Remote Method Invocation and Internet Inter-ORB Protocol (RMI/IIOP) communication function that works with workload management to distribute RMI requests among application servers in a cell.
lock
A means of preventing uncommitted changes made by one application process from being perceived by another application process and for preventing one application process from updating data that is being accessed by another process. A lock ensures the integrity of data by preventing concurrent users from accessing inconsistent data.
logger
A named and stateful object with which the user code interacts and that logs messages for a specific system or application component.
logging
The recording of data about specific events on the system, such as errors.
logging level
A value that controls which events are processed by Java logging.
log handler
A class that uses loggers, levels, and filters to direct whether events are processed or suppressed.
logical derivation
A derivation from a physical document that can have additional service description metadata allocated to the derivation. See also logical model.
logical model
A set of logical derivations. See also logical derivation.
logical terminal (LT)
In SWIFT, the logical entity through which users send and receive SWIFT messages. A logical terminal is identified by its LT name.
logical terminal table (LTT)
A MERVA table used to define logical terminals, their synonyms, and other attributes.
logical unit of work (LUW)
The work that occurs between the start of a transaction and commit or rollback and between subsequent commit and rollback actions. This work defines the set of operations that must be considered part of an integral set.
login binding
A definition of the implementation to provide login information per authentication methods.
login mapping
A Java Authentication and Authorization Service (JAAS) login configuration that is used to authenticate a security token in a web service security header.
long name
The property that specifies the logical name for the server on the z/OS platform.
long-running process
A process that can come to a complete stop while waiting for input or instructions. The most common form of this interruption is a human interaction or decision.
loop
A sequence of instructions performed repeatedly.
loose coupling
A coupling that supports an extensible software architecture.
LPA
See link pack area.
LT
See logical terminal.
LTC
See local transaction containment.
LT code
The ninth character of an LT name. For example, the LT code of the LT name XXXXUSNYA is A.
LT name
A nine-character name of the form BBBBCCLLX, where BBBBCCLL represents the eight-character bank identifier code (BIC8), and X represents the logical terminal (LT) code.
LTPA
See Lightweight Third Party Authentication.
LTT
See logical terminal table.
LUW
See logical unit of work.

M

MAC
See Media Access Control.
macroflow
See long-running process.
mail session
A resource collection of protocol providers that authenticate users and control user access to messaging systems.
maintenance mode
A state of a node or server that an administrator can use to diagnose, maintain, or tune the node or server without disrupting incoming traffic in a production environment.
manageability
The ability to manage a resource, or the ability of a resource to be managed. (OASIS)
manageability capability
A capability associated with one or more management domains. (OASIS)
manageability capability interface
A web service interface representing one manageability capability. (OASIS)
manageability consumer
A user of manageability capabilities associated with one or more manageable resources. (OASIS)
manageability endpoint
A web service endpoint associated with and providing access to a manageable resource. (OASIS)
manageability interface
The composition of one or more manageability capability interfaces. (OASIS)
manageable resource
A resource capable of supporting one or more standard manageability capabilities. (OASIS)
Managed Bean (MBean)
In the Java Management Extensions (JMX) specification, the Java objects that implement resources and their instrumentation.
managed deployment environment
A set of server components that are used to test and deploy applications in a controlled environment.
managed environment
An environment where services, such as transaction demarcation, security, and connections to Enterprise Information Systems (EISs), are managed on behalf of the running application. Examples of managed environments are the web and Enterprise JavaBeans (EJB) containers.
managed file
A library item that is created outside of IBM Process Designer and that is part of a process application, such as an image or Cascading Style Sheet (CSS). Creating managed files ensures that all required files are available and installed when a project is ready for testing or production.
managed mode
An environment in which connections are obtained from connection factories that the Java EE server has set up. Such connections are owned by the Java EE server.
managed node
A node that is federated to a deployment manager and contains a node agent and can contain managed servers. See also node.
managed resource
An entity that exists in the runtime environment of an IT system and that can be managed. See also sensor.
managed server
A server within a managed node, to which SCA modules and applications can be deployed.
management domain
An area of knowledge relative to providing control over, and information about the behavior, health and life cycle of manageable resources.
Management Information Base (MIB)
In the Simple Network Management Protocol (SNMP), a database of objects that can be queried or set by a network management system. See also Simple Network Management Protocol.
manifest
A special file that can contain information about the files packaged in a JAR file. (Sun)
manual emulator
An emulator that requires users to specify response values for an emulated component or reference at run time. See also emulator, programmatic emulator.
map
  1. 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.
  2. A data structure that maps keys to values.
  3. A file that defines the transformation between sources and targets.
map component
An Integration Flow Designer object that encapsulates a reference to an executable map, along with its execution settings. There are three types of map components: source, compiled, and pseudo.
map object
An object used in the TX Programming Interface that represents an instance of a map in the program memory.
mapped expression
Part of an SQL statement that is used to retrieve data from a data connection for a field in a business object.
mapping
  1. The act of developing and maintaining a map.
  2. The relationship between fields in different abstractions of event and action objects.
  3. The process of transforming data from one format to another.
map rule
An expression that evaluates to data and produces the required output. A map rule is entered on an output card in the Map Designer and cannot be longer than 32KB.
marker bar
The gray border at the left of the editor area of the workbench, where bookmarks and breakpoints are shown.
marshal
To convert an object into a data stream for transmission over a network.
mashup
A graphical interface that features two or more reusable web applications (widgets) presenting seemingly disparate data in an understandable combination for a specific purpose.
master configuration
The configuration data held in a set of files that form the master repository for either a deployment manager profile or a stand-alone profile. For a deployment manager profile, the master configuration stores the configuration data for all the nodes in the network deployment cell.
matching rule
The portion of a policy rule in a processing policy that defines the criteria to determine whether the message is processed by its processing rule.
maximum possible score
A score that describes the maximum of the maximum scores of all individual scorecards. The maximum possible score is a complex scorecard property, its value should be the same in all the scorecards used in a complex scorecard.
maximum score
The upper limit in a given interval for an attribute that is used in determining reason code assignment. Typically used for linear and logistic models where variable interaction is controlled.
maximum transmission unit (MTU)
The largest possible unit of data that can be sent on a given physical medium in a single frame. For example, the maximum transmission unit for Ethernet is 1500 bytes.
MBean
See Managed Bean.
MBean provider
A library containing an implementation of a Java Management Extensions (JMX) MBean and its MBean Extensible Markup Language (XML) descriptor file.
MD5
A type of message algorithm that converts a message of arbitrary length into a 128-bit message digest. This algorithm is used for digital signature applications where a large message must be compressed in a secure manner.
MDB
See message-driven bean.
measure
A metric combined with an aggregation type such as average, count, maximum, minimum, sum, or average. See also aggregate metric.
Media Access Control (MAC)
In networking, the lower of two sublayers of the Open Systems Interconnection model data link layer. The MAC sublayer handles access to shared media, such as whether token passing or contention will be used.
mediation
An application of service interaction logic to messages flowing between service requesters and providers.
mediation flow
A sequence of processing steps, or mediation primitives, that run to produce the mediation when a message is received. See also message flow.
mediation flow component
A component that contains one or more mediation primitives arranged into request and response flows. Rather than performing business functions, mediation flow components are concerned with the flow of messages.
mediation framework
A mechanism that supports creation of mediation flows through the composition of mediation primitives.
mediation module
An SCA module that includes a mediation flow component and primarily enables communication between applications by changing the format, content, or target of service requests.
mediation policy
A policy that is held in a registry and is applied to a Service Component Architecture (SCA) module. The mediation policy enables mediation flows, which are in the module, to be configured at run time by using dynamic properties.
mediation policy attachment
An attachment that is a prerequisite for using the mediation policy and gate conditions on the mediation policy.
mediation primitive
The building blocks of mediation flow components.
mediation service
A service that intercepts and modifies messages that are passed between client services (requesters) and provider services.
mediation subflow
A preconfigured set of mediation primitives that are wired together to create a common pattern or use case. Mediation subflows run in the context of a parent flow, and can be reused in mediation flows or in subflows.
meet-in-the-middle mapping
An approach for mapping enterprise beans to database tables in which enterprise beans and database schema are created simultaneously but independently.
member
In the Type Designer, a single occurrence of a component in a group in a type tree. If a component has a range, each occurrence of that component might be referred to as a member of a series.
membership
The state of being a portal user and a place member. Membership in the portal is controlled by the administrator during the installation and set up of portal servers. Membership in places is controlled by a place manager, who determines the level of access for each place member: participant, place designer, or place manager.
membership policy
A subexpression that is evaluated against the nodes in a cell to determine which nodes host dynamic cluster instances.
memory leak
The effect of a program that maintains references to objects that are no longer required and therefore need to be reclaimed.
merge
A point in the process where two or more alternative sequence flow paths are combined into one sequence flow path. No synchronization is required because no parallel activity runs at the join point. BPMN uses multiple incoming sequence flow paths for an activity or an exclusive gateway to perform a merge.
message
  1. An object that depicts the contents of a communication between two participants. A message is transmitted through a message flow and has an identity that can be used for alternative branching of a process through the event-based exclusive gateway.
  2. A string of bytes that is passed from one application to another. Messages typically comprise a message header (used for message routing and identification) and a payload (containing the application data being sent). The data has a format that is compatible with both the sending and receiving application.
  3. A set of data that is passed from one application to another. Messages must have a structure and format that is agreed by the sending and receiving applications. See also category.
message body
The part of the message that contains the message payload. See also message header.
message category
A group of messages that are logically related, such as message that are all used by one application.
message channel
In distributed message queuing, a mechanism for moving messages from one queue manager to another. A message channel comprises two message channel agents (a sender at one end and a receiver at the other end) and a communication link. See also channel.
message definition
Information that describes the structure of the messages of a particular type, the elements that each message of that type can or must contain, how a message of that type is represented in various network formats, and the validation rules that apply to a message of that type.
message digest
A hash value or a string of bits resulting from the conversion of processing data to a number.
message domain
A group of all the message definitions that are required to satisfy a particular business need (for example, transferring SWIFTNet FIN messages, transferring SWIFTNet Funds messages, or transferring SWIFTNet system messages).
message-driven bean (MDB)
An enterprise bean that provides asynchronous message support and clearly separates message and business processing.
message-driven rule bean
An enterprise bean that allows Java EE applications to process messages asynchronously. The bean invokes the execution unit (XU) when a JMS message arrives and posts the results of the rule engine processing to a JMS destination.
message end event
An end event that also sends a message. See also end event.
message event
An event that arrives from a participant and triggers another event. If the message event is attached to the boundary of the activity, it changes the normal flow into an exception flow upon being triggered.
message file
A file containing messages sent in bulk through a message bulking service.
message flow
  1. A connecting object that shows the flow of messages between two collaborating participants. A message flow is represented by a dashed line.
  2. A sequence of processing steps that execute in the broker when an input message is received. Message flows are defined in the workbench by including a number of message flow nodes, each of which represents a set of actions that define a processing step. The connections in the flow determine which processing steps are carried out, in which order, and under which conditions. See also mediation flow, subflow.
Message Format Service (MFS)
An IMS editing facility that allows application programs to deal with simple logical messages instead of device-dependent data, thus simplifying the application development process.
Message Format Service control block (MFS control block)
In MFS, the representation of a message or format that is stored in the IMS.FORMAT library and called into the MFS buffer pool as needed for online execution.
message header
The part of a message that contains control information such as a unique message ID, the sender and receiver of the message, the message priority, and the type of message. See also message body.
message input descriptor (MID)
The Message Format Service (MFS) control block that describes the format of the data presented to the application program. See also message output descriptor.
message intermediate event
An intermediate event that can be used to either receive or send a message. See also intermediate event.
message output descriptor (MOD)
The Message Format Service (MFS) control block that describes the format of the output data produced by the application program. See also message input descriptor.
message processing node
A node in a message flow that represents a processing step. A message processing node can be either a primitive or a subflow node.
message processing unit (MPU)
A message processing unit is used to correlate information within a message, for example reason or completion information, and a message text.
message queue
A named destination to which messages can be sent until they are retrieved by programs that service the queue.
message reception registry (MRR)
The registry where SWIFT stores the central routing rules. Each receiver defines its own rules and submits them to SWIFT. SWIFT uses these rules to determine the destination of message traffic, that is, to which store and forward queue or to which SWIFTNet Link it is to route each message.
message reference number (MRN)
A unique 16-digit number assigned to each message for identification purposes. The message reference number consists of an 8-digit domain identifier that is followed by an 8-digit sequence number.
message sequence number (MSN)
A sequence number for messages.
message standard
A standard that describes a family of message definitions.
message start event
A start event that is triggered when a specific message is received. See also start event.
message type
The logical structure of the data within a message. For example, the number and location of character strings.
message warehouse table
A database table in which the message warehouse service stores index and status information about each message processed by services.
messaging API
A programming interface that enables an application to send and receive messages and attached files over a messaging system.
messaging engine
  1. The messaging and connection point to which applications connect to the bus.
  2. A server component that provides the core messaging functionality of a service integration bus.
messaging middleware
Software that provides an interface between applications, allowing them to send data back and forth to each other asynchronously. Data sent by one program can be stored and then forwarded to the receiving program when it becomes available to process it.
messaging system
Software used to deliver electronic messages.
metadata
Data that describes the characteristics of data; descriptive data. See also application-specific information.
metadata tree
A list in a tree structure, which is prepared and displayed by the external service wizard, that presents all of the objects discovered from the enterprise information system (EIS).
method
  1. In object-oriented programming, an operation that an object can perform. An object can have many methods. See also operation.
  2. A way to implement a function on a class.
method extension
An IBM extension to the standard deployment descriptors for enterprise beans that define transaction isolation methods and control the delegation of credentials.
method permission
A mapping between one or more security roles and one or more methods that a member of a role can call.
metric
A holder for information, typically a business performance measurement, in a monitoring context. See also aggregate metric.
MFS
See Message Format Service.
MFS control block
See Message Format Service control block.
MIB
See Management Information Base.
microflow
A short-running process that runs in one transaction. A microflow, which is an IBM extension to the BPEL programming language, runs automatically from start to finish and cannot be interrupted.
micropattern
A pattern that creates a reusable subprocess from a main process. See also pattern.
MID
See message input descriptor.
middleware agent
An agent that enables the administrative domain to manage servers that run middleware software.
middleware descriptor
An XML file that contains information about different middleware platform types, including discovery sensor intervals and installation information.
middleware node
A node that is federated to the deployment manager. These nodes must include nodes that run the node agent or middleware agent.
MIME
See Multipurpose Internet Mail Extensions.
MOD
See message output descriptor.
model
A representation of a process, system, or subject area, typically developed for understanding, analyzing, improving, and replacing the item being represented. A model can include a representation of information, activities, relationships, and constraints.
modeled fault
A fault message that is returned from a service that has been modeled on the Web Services Description Language (WSDL) port type.
model element
An element that is an abstraction drawn from the system being modeled. In the MOF specification, model elements are considered to be meta-objects.
model view controller (MVC)
A software architecture that separates the components of the application: the model represents the business logic or data; the view represents the user interface; and the controller manages user input or, in some cases, the application flow. See also view.
module
  1. 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.
  2. A program unit that is discrete and identifiable with respect to compiling, combining with other units, and loading.
  3. A software artifact that is used for developing, managing versions, organizing resources, and deploying to the runtime environment.
monitor
  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.
monitor configuration server
The application server installation that owns the overall application server configuration for a cell.
monitor details model
A container for monitoring contexts and their associated metrics, keys, counters, stopwatches, triggers, and inbound and outbound events. The monitor details model holds most of the monitor model information.
monitored directory
The directory where the rapid deployment tools detect added or changed parts and produce an application that can run on the application server. See also automatic application installation project, free-form project.
monitoring context
A definition that corresponds to an object to be monitored, such as a process execution, an ATM, a purchase order, or the stock level in a warehouse. At run time, monitoring contexts process the events for a particular object.
monitor model
A model that describes the business performance management aspects of a business model, including events, business metrics, and key performance indicators (KPIs) that are required for real-time business monitoring.
monitor model CEI configuration owner
The server installation that owns the overall server configuration that contains the monitor model Common Event Infrastructure (CEI) server target.
mount point
A logical drive through which volumes are accessed in a sequential access device class. For removable media device types, such as cartridges, a mount point is a logical drive associated with a physical drive. For the file device type, a mount point is a logical drive associated with an I/O stream.
MPMT
See multiprocess multithread.
MPU
See message processing unit.
MRN
See message reference number.
MRR
See message reception registry.
MSN
See message sequence number.
MTU
See maximum transmission unit.
multidimensional analysis
The process of assessing and evaluating an enterprise on more than one level.
multiple configuration instances
More than one instance of a product running in the same machine at the same time.
multiprocess multithread (MPMT)
A process architecture of the IBM HTTP Server that supports multiple processes as well as multiple threads per process.
Multipurpose Internet Mail Extensions (MIME)
An Internet standard that allows different forms of data, including video, audio, or binary data, to be attached to email without requiring translation into ASCII text.
MVC
See model view controller.

N

named constant
A descriptive name that is given to a value and can be used in a filter in place of a value.
namespace
A logical container in which all the names are unique. The unique identifier for an artifact is composed of the namespace and the local name of the artifact.
naming
An operation that is used to obtain references to objects that are related to applications.
naming context
A logical namespace containing name and object bindings.
naming federation
The process of binding naming systems so that the aggregate system can process composite names that span the naming systems.
naming service
An implementation of the Java Naming and Directory Interface (JNDI) standard.
NAS
See network access server.
NAT
See network address translation.
native
Pertaining to the relationship between a transport user and a transport provider that are both based on the same transport protocol.
navigation bar
A set of links to other web pages in a website. For example, a navigation bar is typically located across the top or down the side of a page and contains direct links to the major sections within the website.
navigation phrase
In the vocabulary, a phrase that associates two business elements. A navigation phrase corresponds to a method that has a return value or an attribute in the business object model (BOM).
near cache
A local, in-process cache in the client Java virtual machine (JVM) that includes a subset of the cached data set that is stored remotely in servers. Data in the near cache can become out of sync with recently changed data in servers.
netmask
See network mask.
network
A system of resources, such as appliances, computers, and storage devices, that are connected virtually or physically.
network access server (NAS)
A device that functions as an access control point for users in remote locations who connect to an internal network or to an ISP. A NAS might include its own authentication services or rely on a separate authentication server. A NAS can be a dedicated server or a software service within a regular server.
network address translation (NAT)
The conversion of a network address that is assigned to a logical unit in one network into an address in an adjacent network.
network delivery notification
A delivery notification that conforms to the network protocol. See also application delivery notification.
network deployment cell
A logical group of servers, on one or more machines, managed by a single deployment manager.
Network File System (NFS)
A protocol, developed by Sun Microsystems, Incorporated, that allows a computer to access files over a network as if they were on its local disks.
network identifier
A single character that is placed before a message type to indicate which network is to be used to send the message; for example, S for SWIFT.
Network Installation Management (NIM)
An environment that provides installation and configuration of software within a network interface.
network mask (netmask)
A number that is the same as an Internet Protocol (IP) address. A network mask identifies which part of an address is to be used for an operation, such as making a TCP/IP connection.
network protocol stack
A set of network protocol layers and software that work together to process the protocols.
Network Time Protocol (NTP)
A protocol that synchronizes the clocks of computers in a network.
NFS
See Network File System.
NIM
See Network Installation Management.
node
  1. A logical group of managed servers. See also managed node.
  2. An endpoint or junction used in a message flow.
  3. In XML, the smallest unit of a valid, complete structure in a document.
  4. Any element in a tree.
node agent
An administrative agent that manages all application servers on a node and represents the node in the management cell.
node federation
The process of combining the managed resources of one node into a distributed network such that the central manager application can access and administer the resources on the node.
node group
A collection of application server nodes that defines a boundary for server cluster formation.
node name
The machine name or host name that must be unique.
nonce
A unique cryptographic number that is embedded in a message to help detect a replay attack.
none start event
A start event that does not have a defined trigger. A none start event can be used in a descriptive process that does not require technical information or in a subprocess where the control of the process flow is passed from its parent process. See also start event.
nonrepudiation
In business-to-business communication the ability of the recipient to prove who sent a message based on the contents of the message. This can derive from the use of a digital signature on the message, which links the sender to the message.
normal flow
All sequence flow paths in a process except those paths that originate from an intermediate event that is attached to the boundary of an activity. See also exception flow.
notation
An XML construct that contains a note, a comment or an explanation about information in an XML file. A notation can be used to associate a binary description with an entity or attribute.
notification
A message that contains the event descriptions that are sent to managed resources, web services and other resources.
notification channel
A mode by which a subscriber uses a business service.
notification program
A program or web service that can be triggered when an event occurs.
NTP
See Network Time Protocol.

O

OAEP
See optimal asymmetric encryption padding.
OAMS
See outbound application message store.
object
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.
object adapter
In Common Object Request Broker Architecture (CORBA), the primary interface that a server implementation uses to access Object Request Broker (ORB) functions.
object-oriented programming
A programming approach based on the concepts of data abstraction and inheritance. Unlike procedural programming techniques, object-oriented programming concentrates not on how something is accomplished but instead on what data objects compose the problem and how they are manipulated.
object reference
In Common Object Request Broker Architecture (CORBA), the information needed to reliably identify a particular object.
Object Request Broker (ORB)
In object-oriented programming, software that serves as an intermediary by transparently enabling objects to exchange requests and responses.
OLAP
See online analytical processing.
on-demand configuration
A component that detects and dynamically configures routing rules, which tell the on demand router (ODR) how to route requests.
on demand router
A proxy server that is the point of entry into the product environment and is a gateway through which prioritized HTTP requests and Session Initiation Protocol (SIP) messages flow to the middleware servers in the environment.
one-way hash
An algorithm that converts processing data into a string of bits; known as a hash value or a message digest.
one-way interaction
A type of messaging interaction in which a request message is used to request function without a reply.
online analytical processing (OLAP)
The process of collecting data from one or many sources; transforming and analyzing the consolidated data quickly and interactively; and examining the results across different dimensions of the data by looking for patterns, trends, and exceptions within complex relationships of that data.
ontology
An explicit formal specification of the representation of the objects, concepts, and other entities that can exist in some area of interest and the relationships among them. See also Web Ontology Language.
Open Mobile Alliance
An industry forum for developing interoperable mobile service enablers.
open relationship
A relationship on an object that no longer points to a second object because the second object has been deleted.
Open Servlet Engine (OSE)
A lightweight communications protocol developed by IBM for interprocess communication.
open source
Pertaining to software whose source code is publicly available for use or modification. Open source software is typically developed as a public collaboration and made freely available, although its use and redistribution might be subject to licensing restrictions. Linux is a well known example of open source software.
Open Transaction Manager Access (OTMA)
A component of IMS that implements a transaction-based, connectionless client/server protocol in an MVS sysplex environment. The domain of the protocol is restricted to the domain of the z/OS Cross-System Coupling Facility (XCF). OTMA connects clients to servers so that the client can support a large network (or a large number of sessions) while maintaining high performance. See also IMS Connect.
operation
An implementation of functions or queries that an object might be called to perform. See also method.
operation mapping
An interface map in which operations of the source interface are mapped to operations of the target interface.
operator
A building block that lets the user compare or establish relationships between the different parts of business rule statements.
optimal asymmetric encryption padding (OAEP)
In cryptography, a padding scheme that is often used with RSA encryption.
optimistic locking
A locking strategy whereby no lock is held between the time that a row is selected and the time that an update or a delete operation is attempted on that row. See also pessimistic locking.
option
A parameter that determines how a message is to be processed.
optional component
Within a group type, a component that can be defined to represent a data object that is not required to be present in the data. The component range maximum specifies how many occurrences of the data object might optionally exist.
option set
A named group of options and their settings that can be specified in a request or in another option set, thereby eliminating the need to specify each option individually.
ORB
See Object Request Broker.
organizational unit (OU)
A body whose data is to be kept separate from that of other, similar bodies. WebSphere BI for FN uses OUs to control access to resources, and to ensure data segregation. Typically, OUs are used to represent different financial institutions, or different departments within a financial institution.
orphaned token
A token that is associated with an activity that was removed from a business process definition (BPD).
OSE
See Open Servlet Engine.
OSGi framework
A general-purpose, secure, and managed Java framework that supports the deployment of extensible and downloadable applications known as bundles.
OSGi service
An interface registered in the OSGi Service Platform and made available for receiving remote or local invocations.
OTMA
See Open Transaction Manager Access.
OU
See organizational unit.
outbound
In communication, pertaining to data that is sent to the network. See also inbound.
outbound application message store (OAMS)
A message store in which messages sent by local applications (ISN messages) and their acknowledgement messages (ISN ACKs) are stored.
outbound authentication
The configuration that determines the type of accepted authentication for outbound requests.
outbound event
An event emitted from a monitoring context or from a KPI context.
outbound port
The mechanism through which an outbound service communicates with the externally hosted web service. Messages pass between the outbound service and the external service through the appropriate port.
outbound processing
The process by which a calling client application uses the adapter to update or retrieve data in an enterprise information system (EIS). The adapter uses operations such as create, update, delete, and retrieve to process the request.
outbound service
The service that provides access through one or more outbound ports to a web service that is hosted externally.
out parameter
A parameter value that is set by the execution process and provided as output from the rule set after the execution is completed.
output
An exit point through which an element can notify downstream elements that they can now start.
output activity
The end point of the business process.
output card
In the Map Designer, a card that contains the complete definition of an output for the map including information such as target identification, destination specifics and the behavior that should occur during processing.
output screen
A screen that a user navigates to based on data entry and keystrokes in a 3270 application. In the 3270 terminal service recorder, the access route from one screen to another can be recorded and saved in a dialog file.
output terminal node
A primitive through which a message is propagated by a subflow. Each output terminal node is represented as an output terminal of the corresponding subflow node.
override
An execution setting that overrides default source and target settings of a map.
OWL
See Web Ontology Language.

P

package
  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.
packet
In data communication, a sequence of binary digits, including data and control signals, that are transmitted and switched as a composite whole. See also frame.
pack type
A container, such as a case or pallet. Each pack type is associated with various pieces of information that are required for converting customer-specific product codes to EPC format.
pad character
A character used to fill empty space. For example, in a database application, a field that is ten characters in length that has the word "file" in it contains four text characters and six pad characters
page
A node in a portal that can contain content in addition to labels and other pages. Pages can contain child nodes, column containers, row containers, and portlets.
page list
An assembly property that specifies the location to forward a request, but automatically tailors that location, depending on the Multipurpose Internet Mail Extensions(MIME) type of the servlet.
page template
In Page Designer, a page that is used as a starting point to define consistent styles and layout for any new HTML or JavaServer Pages (JSP) page within a website.
palette
A range of graphically displayed choices, such as colors or collections of tools, that can be selected in an application.
pallet
An industry standard sized wooden, plastic, or metal platform to facilitate the movement of materials. Cartons are stacked on the pallet allowing movement via pallet jacks or forklift trucks.
PAP
See policy administration point.
parallel garbage collection
A type of garbage collection that uses several threads simultaneously.
parallel gateway
A gateway that creates parallel paths without checking conditions.
parallel job
A job that is run as multiple concurrent steps. A top-level job is submitted to the job scheduler and after submission is divided into subordinate jobs that run at the same time.
parameter (parm)
A value or reference passed to a function, command, or program that serves as input or controls actions. The value is supplied by a user or by another program or process. See also keyword.
parameter mapping
An interface map that is one level deeper than operation mappings because it maps the parameters in the source operation to the parameters in the target operation. There are five types of parameter mappings: move, map, extract, Java, and assign.
parent document
A document whose values are inherited by another document (the child document).
parent process
A process that contains a subprocess.
parm
See parameter.
parse
To break down a string of information, such as a command or file, into its constituent parts.
parser
A module used to break down a document into its component parts and to construct a document from its component parts.
participant
A business entity (such as a company, company division, or a customer) or a business role (such as a buyer or a seller) that controls or is responsible for a business process.
partition
  1. A subset of the data grid that is hosted across multiple shard containers.
  2. A group of cells in a decision table that are in the same condition column and have a common cell immediately to the left.
  3. To divide a type into subtypes that are mutually exclusive.
partitioned data set (PDS)
A data set on direct access storage that is divided into partitions, called members, each of which can contain a program, part of a program, or data.
partitioned type
A type whose subtypes are distinguishable or mutually exclusive.
part reference
An object that is used by a configuration to reference other related configuration objects.
passivation
In enterprise beans, the process of transferring an enterprise bean from memory to auxiliary storage. (Sun) See also activation.
PassTicket
In RACF secured sign-on, a dynamically generated, random, one-time-use, password substitute that a workstation or other client can use to sign on to the host rather than sending a RACF password across the network.
password
In computer and network security, a specific string of characters used by a program, computer operator, or user to access the system and the information stored within it. See also authentication.
password stashing
Saving a password that is encrypted in a file or on a hard disk drive. The keydb password must reside in a file to use secure sockets layer (SSL).
path
  1. The route through a file system to a specific file.
  2. A route that the flow can take through the activities in a process. There may be several alternative paths.
pattern
A reusable solution that encapsulates a tested approach to solving a common architecture, design, or deployment task in a particular context. See also micropattern.
payload
The body of a message that holds content.
PCRE
See Perl-compatible regular expression.
PDP
See policy decision point.
PDS
See partitioned data set.
peer access point
A means by which core groups can communicate with other cells.
PEM
See privacy enhanced mail.
people assignment criterion
A property that defines the members of each of the role groups.
people awareness
The collaboration feature that provides access to people from various contexts. People awareness lets you see references to people and contact people by name through the Sametime online status indicator. Throughout the portal, wherever you see the name of a person, you can view the online status of the person, send email, initiate a chat, or share an application via an electronic meeting. See also person link.
PEP
See policy enforcement point.
Performance Monitoring Infrastructure (PMI)
A set of packages and libraries assigned to gather, deliver, process, and display performance data.
Perl-compatible regular expression (PCRE)
A regular expression C library that is much richer than classic regular expression libraries. See also regular expression.
permission
Authorization to perform activities, such as reading and writing local files, creating network connections, and loading native code.
persist
To be maintained across session boundaries, typically in nonvolatile storage such as a database system or a directory.
persistence
  1. In Java EE, the protocol for transferring the state of an entity bean between its instance variables and an underlying database. (Sun)
  2. 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.
persistence level
A level that determines the degree of detail written to the database as a business process runs. Decreasing the persistence level increases the business process performance at the cost of full tracking for each step of the business process.
persistence service
A service that provides private application programming interface (API) support to store and accesses executable resources.
persistent data store
A nonvolatile storage for event data, such as a database system, that is maintained across session boundaries and that continues to exist after the execution of the program or process that created it.
person
An individual authenticated by the portal and having a person record in one or more corporate directories. Persons can be members of places, public groups within the organization corporate directory, or personal groups that a user defines.
personal group
In Sametime Connect, a group of people designated by the user as a group. A user can choose individuals from the public Directory (public group) and create personal groups, which are then stored locally. Users can add and remove people from a personal group, whereas the membership of the public group is defined by the owner of the public Directory.
personalization
The process of enabling information to be targeted to specific users based on business rules and user profile information.
person link
A reference to a person name or a group name that appears with the Sametime online status indicator. The reference lets you view the online status the person, send an email, start a chat, or share an application using an electronic meeting, among other actions shown on the person link menu. See also people awareness.
perspective
A group of views that show various aspects of the resources in the workbench.
pessimistic locking
A locking strategy whereby a lock is held between the time that a row is selected and the time that a searched update or delete operation is attempted on that row. See also optimistic locking.
phantom read
A read request in which two identical queries run, and the collection of rows returned by the second query is different from the first query.
PHP Hypertext Preprocessor
A widely-used general-purpose scripting language that is especially suited for web development and can be embedded into HTML.
phrase template
A pattern for the verbalization of a business element.
pivot table
A table characterized by having one metric as a column dimension and all the rest of the metrics represented as row dimensions.
PKA
See public key algorithm.
PKCS
See Public Key Cryptography Standards.
PKI
See public key infrastructure.
place designer
A member of a place who can edit place layout and bookmarks. See also participant, place manager.
placeholder
A variable that is replaced with a value.
place manager
A member of a place who can edit place membership, layout, and bookmarks. See also participant, place designer.
place member
A individual or group who has joined or been granted access to a place. Place members have three levels of access to a place: manager, designer, and participant.
plug-in
A separately installable software module that adds function to an existing program, application, or interface.
PMI
See Performance Monitoring Infrastructure.
point
The numeric value that is assigned to an attribute based on the value of the attribute and the interval in which the value is included.
point difference
The upper limit in a given interval for an attribute that is ultimately used to determine reason code assignment. Typically, this limit is used for linear and logistic models where the interaction of variables is controlled.
point-to-point
Pertaining to a style of messaging application in which the sending application knows the destination of the message.
poison message
In a queue, an incorrectly formatted message that the receiving application cannot process. The message can be repeatedly delivered to the input queue and repeatedly backed out by the application.
policy
A set of considerations that influence the behavior of a managed resource or a user. See also policy expression.
policy administration point (PAP)
A capability that provides enterprise service-oriented architecture (SOA) policy administration capabilities, such as policy creation, modification, storage, and distribution.
policy-controlled mediation
A mediation that has dynamic properties that are controlled by mediation policies.
policy decision point (PDP)
A capability that decides, based on environmental conditions, which predefined policies in the environment should be enforced. For example, a policy decision point might use a requester identity to determine whether to limit access to a resource.
policy enforcement point (PEP)
A capability that enforces policy decisions maybe by a policy decision point. For example, a policy enforcement point would permit or deny a requester access to a resource depending on what the policy decision point determined is the correct action.
policy expression
A representation of a policy. See also policy.
policy manager
A decision management user role who is responsible for enforcing decisions through the creation and maintenance of rules.
policy rule
A rule in a processing policy that consists of a matching rule and a processing rule.
policy set
A collection of assertions about how services are defined, which can be used to simplify security configurations.
pool
The graphical representation of a participant in a collaboration.
port
  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 the Internet suite of protocols, a specific logical connector between the Transmission Control Protocol (TCP) or the User Datagram Protocol (UDP) and a higher level protocol or application.
portal
A single, secure point of access to diverse information, applications, and people that can be customized and personalized.
Portal Administration
The place where portal administrators set and maintain basic collaboration permissions, place records, place membership records, and server settings for companion products for advanced collaboration.
portal farm
A series of identically configured, stand-alone portal server instances that offer a way to maintain a highly scalable and highly available server environment.
port destination
The specialization of a service integration bus destination. Each port destination represents a particular message format and transport protocol that you can use to pass messages to an externally-hosted service.
portlet
A reusable component that is part of a web application that provides specific information or services to be presented in the context of a portal.
portlet API
The set of interfaces and methods that are used by Java programs running within the portal server environment to obtain services.
portlet application
A collection of related portlets that can share resources with one another.
portlet container
A column or row that is used to arrange the layout of a portlet or other container on a page.
portlet framework
The set of classes and interfaces that support Java programs running within the portal server environment.
portlet mode
A form assumed by a portlet to provide a distinctive interface for users to perform different tasks. Portlet modes can include view, edit, and help.
port number
In Internet communications, the identifier for a logical connector between an application entity and the transport service.
port type
An element in a Web Services Description Language (WSDL) document that comprises a set of abstract operations, each of which refers to input and output messages that are supported by the web service. See also interface.
POST
In HTTP, a parameter on the METHOD attribute of the FORM tag that specifies that a browser will send form data to a server in an HTTP transaction separate from that of the associated URL.
precondition
A group of rule statements in which the user defines global variables for a decision table or decision tree and conditions that must be met before any rows or branches in the decision table or tree can be executed.
predefined business process
A business process that is ready to use upon installation of Sterling B2B Integrator.
predicate
A Boolean logic term denoting a logical expression that determines the state of a variable.
presumed trust
A type of identity assertion where trust is presumed and additional trust validation is not performed. Use this mode only in an environment where trust is established with some other mechanism.
primary document
A document that the services in a business process act on or in relation to. A primary document is usually the document passed to a business process by the initiating adapter.
primary key
  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.
primary server
The server on which all resources that are to be deployed exactly once per instance or once per organization unit (OU) are deployed.
primitive
A message processing node that cannot be further subdivided. See also subflow node.
primitive type
In Java, a category of data type that describes a variable that contains a single value of the appropriate size and format for its type: a number, a character, or a Boolean value. Examples of primitive types include byte, short, int, long, float, double, char, boolean.
principal
An entity that can communicate securely with another entity. A principal is identified by its associated security context, which defines its access rights.
priority
A property that determines the order in which business rules are executed in an application.
privacy enhanced mail (PEM)
A standard for secure email on the Internet.
private business object
  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.
private cloud
A cloud computing environment in which access is limited to members of an enterprise and partner networks.
private key
In secure communication, an algorithmic pattern used to encrypt messages that only the corresponding public key can decrypt. The private key is also used to decrypt messages that were encrypted by the corresponding public key. The private key is kept on the user system and is protected by a password. See also key, public key.
private process
A process that is strictly internal to a specific organization.
private service bundle
A service bundle that is not explicitly mentioned in the customization definition document (CDD), but that is included in a service bundle set and provides resources required by another service bundle. In a customization definition report, private service bundles are listed, and their names are followed by the string [private].
probe
A reusable set of Java code fragments and supporting attributes for collecting detailed runtime information about objects, arguments, and exceptions. See also Probekit.
Probekit
A scriptable framework for doing byte-code insertion to probe the workings of a target program. See also probe.
process
  1. A sequence or flow of activities in an organization with the objective of carrying out work. In BPMN, a process is depicted as a graph of flow elements, which are a set of activities, events, gateways, and sequence flow paths that adhere to BPMN execution semantics.
  2. The sequence of documents or messages to be exchanged between the Community Managers and participants to run a business transaction.
  3. A progressively continuing procedure consisting of a series of controlled activities that are systematically directed toward a particular result or end.
process application
A container in the Process Center repository for process models and supporting implementations. A process application typically includes business process definitions (BPDs), the services to handle implementation of activities and integration with other systems, and any other items that are required to run the processes. Each process application can include one or more tracks.
Process Center Console
An interface to the Process Center repository where administrators can create and manage process applications, manage user access to library items, install snapshots on test or production servers, and perform other tasks.
process control information
Map component settings that can be changed at run time by specifying overrides at the command line, in a command file, or by configuring the Launcher.
process data
Data that is accumulated in an XML document about a business process during the life of the process. Activities in the process add elements to the process data and use components of the process data to complete configured processing tasks.
process definition
A specification of the runtime characteristics of an application server process.
process diagram
A diagram that represents the flow of work for a process. The objects within a process diagram include tasks, processes, connections, business items, resources, and decisions.
process flow
The representation of interdependencies between activities in a structured format.
processing action
A defined activity in a processing rule that is performed against messages. See also action.
processing policy
A collection of policy rules that define message processing through a service.
processing rule
The portion of a policy rule in a processing policy that identifies the processing actions to perform against messages.
process model
A representation of a real-time business process. A business process model is composed of the individual steps or activities that make up the process, contains the conditions that dictate when the steps or activities occur, and identifies the resources that are required to run the business process.
process module
A program unit that contains a set of process templates that support administrative tasks.
producer definition
A set of interfaces that are defined for the producer portal. The producer definition can include the producer service description, the producer portal URL, and the security setup. See also consumer portal, producer portal.
producer portal
A portal that provides portlets as a service so that other portals, called consumer portals, can use the portlets and make the portlets available to their users. See also consumer portal, producer definition.
profile
Data that describes the characteristics of a user, group, resource, program, device, or remote location.
programmatic emulator
An emulator that uses a Java or visual snippet to automatically specify response values for an emulated component or reference at run time. See also emulator, manual emulator.
programmatic login
A type of form login that supports application presentation site-specific login forms for the purpose of authentication.
programmatic security
A collection of methods used by applications when declarative security is not sufficient to express the security model of the application.
program temporary fix (PTF)
For System i, System p, and System z products, a package containing individual or multiple fixes that is made available to all licensed customers. A PTF resolves defects and might provide enhancements. See also fix pack.
project
  1. A specific organization of rules and other elements that facilitates the authoring and management of a logical grouping of rules.
  2. An organized collection used to group folders or packages. Projects are used for building, version management, sharing, and organizing resources related to a single work effort. See also library, module.
promoted property
A property of a mediation module made visible by the solution integrator to the runtime administrator, so that its value can be changed at run time.
prompt
A component of an action that indicates that user input is required for a field before making a transition to an output screen.
propagation
The point at which the properties of a type are inherited by its subtypes.
property
A characteristic of an object that describes the object. A property can be changed or modified. Properties can describe an object name, type, value, or behavior, among other things.
protocol
A set of rules controlling the communication and transfer of data between two or more devices or systems in a communication network.
protocol binding
A binding that enables the enterprise service bus to process messages independently of the communication protocol.
protocol-level RAS granularity
The level of RAS granularity at which RAS attribute values are assigned on a protocol-wide basis. RAS attribute values defined at the protocol-level are assigned to all requests for a particular protocol, such as the HTTP protocol or IIOP protocol. See also RAS granularity.
provision
To provide, deploy, and track a service, component, application, or resource.
proxy
An application gateway from one network to another for a specific network application such as Telnet or FTP, for example, where a firewall proxy Telnet server performs authentication of the user and then lets the traffic flow through the proxy as if it were not there. Function is performed in the firewall and not in the client workstation, causing more load in the firewall.
proxy cluster
A group of proxy servers that distributes HTTP requests across the cluster.
proxy peer access point
A means of identifying the communication settings for a peer access point that cannot be accessed directly.
proxy server
  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.
pseudoattribute
An attribute that cannot have a value, and is used to indicate a binary state, such as yes/no or on/off. For example, the attribute local might be present for some resources and absent for others, indicating whether the resource is local. Pseudo attributes are especially useful for implementing access rights, such as read, update, or delete. See also real attribute.
pseudolink
In the Integration Flow Designer, dotted lines manually drawn in a system definition diagram that visually represent a data flow relationship between two map components that has not yet been determined precisely.
pseudomap component
An Integration Flow Designer object that is a placeholder for an executable map that has not yet been implemented.
PTF
See program temporary fix.
public
  1. In the Java programming language, pertains to a method or variable that can be accessed by elements residing in other classes. (Sun)
  2. In object-oriented programming, pertaining to a class member that is accessible to all classes.
public key
In secure communication, an algorithmic pattern used to decrypt messages that were encrypted by the corresponding private key. A public key is also used to encrypt messages that can be decrypted only by the corresponding private key. Users broadcast their public keys to everyone with whom they must exchange encrypted messages. See also key, private key.
public key algorithm (PKA)
An algorithm designed so that the key used for encryption is different from the key used for decryption. The decryption key cannot be derived, at least not in any reasonable amount of time, from the encryption key.
public key cryptography
A cryptography system that uses two keys: a public key known to everyone and a private or secret key known only to the recipient of the message. The public and private keys are related in such a way that only the public key can be used to encrypt messages and only the corresponding private key can be used to decrypt them.
Public Key Cryptography Standards (PKCS)
A set of industry-standard protocols used for secure information exchange on the Internet. Domino Certificate Authority and Server Certificate Administration applications can accept certificates in PKCS format.
public key infrastructure (PKI)
A system of digital certificates, certification authorities, and other registration authorities that verify and authenticate the validity of each party involved in a network transaction. See also public key, SWIFTNet public key infrastructure.
public place
A shared place that is open to all portal users. The person who creates the place (and who automatically becomes the place manager) designates it as a public place during place creation.
public process
The interactions between a private business process and another process or participant.
publish
  1. To make a web site public, for example by putting files in a path known to the HTTP server.
  2. To send a rule to a server for storage and management.
  3. 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.
publish/subscribe
A type of messaging interaction in which information, provided by publishing applications, is delivered by an infrastructure to all subscribing applications that registered to receive that type of information.

Q

QoS
See quality of service.
qualifier
A simple element that gives another generic compound or simple element a specific meaning. Qualifiers are used in mapping single or multiple occurrences. A qualifier can also be used to denote the namespace used to interpret the second part of the name, typically referred to as the ID.
quality of service (QoS)
A set of communication characteristics that an application requires. Quality of Service (QoS) defines a specific transmission priority, level of route reliability, and security level.
quartile analysis
A type of analysis that displays the value of the business measures boundaries at the 25th, 50th, or 75th percentiles of a frequency distribution divided into four parts, each containing a quarter of the population.
query
  1. A statement, or combination of statements, that is used to search a rule project (or other scope) and to select rule project elements that meet certain criteria.
  2. A request for information from a database that is based on specific conditions: for example, a request for a list of all customers in a customer table whose balances are greater than USD1000.
  3. A reusable request for information about one or more model elements
queue
  1. A destination for point-to-point messaging.
  2. An object that holds messages for message-queueing applications. A queue is owned and maintained by a queue manager.
queue destination
A service integration bus destination that is used for point-to-point messaging.
queue manager
A component of a message queuing system that provides queuing services to applications. See also channel.
queuing network
A group of interconnected components.
quiesce
  1. To pause or alter the state of running processes on a computer, particularly those processes that might modify information stored on a disk during backing up, in order to guarantee a consistent and usable backup.
  2. To end a process or shut down a system after allowing normal completion of active operations.

R

RACF
See Resource Access Control Facility.
RADIUS
See remote authentication dial-in user service.
range
  1. The number of consecutive occurrences of the component in the data stream. The range is composed of two numbers separated by a colon.
  2. The categorization of an attribute into different segments.
range operator
The logic used when comparing two attributes in a range.
rank
A property that determines the order of a reason.
rapid deployment tool
One of a set of tools to rapidly develop and deploy Java EE artifacts on the server and package the Java EE artifacts into the deployed EAR file.
RAR
See resource adapter archive.
RAS
See reliability, availability, and serviceability.
RAS attribute
An attribute that the server applies to a request to control how the server processes that request. RAS attribute values can be defined with server-level, protocol-level, or request-level granularity. See also reliability, availability, and serviceability.
RAS granularity
The extent to which a user can assign different RAS attribute values to different sets of requests within the same application server. The user can define RAS attribute values on a per-server, per-protocol, or per-request basis. See also protocol-level RAS granularity, reliability, availability, and serviceability, request-level RAS granularity, server-level RAS granularity.
Rational Unified Process (RUP)
A configurable software development process platform that is used to assign and manage tasks and responsibilities within a development organization.
RC
See return code.
RDMA
See Remote Direct Memory Access.
read-through cache
A sparse cache that loads data entries by key as they are requested. When data cannot be found in the cache, the missing data is retrieved with the loader, which loads the data from the back-end data repository and inserts the data into the cache.
real attribute
An attribute that must have a value. See also pseudoattribute.
realize
In the web diagram editor, to associate a node with an actual resource by creating that resource or by editing the node path so that it points to an existing resource. See also unrealized.
realm
A collection of resource managers that honor a common set of user credentials and authorizations.
realm name
The machine name of a user registry.
reason code
A code assigned to identify a reason. Each scorecard can have multiple reasons.
reasoning strategy
The strategy used to sort and compute the reasons returned from a scorecard table.
receiver bean
In extended messaging, a message-driven bean or a session bean. A message-driven bean is invoked when a message arrives at a JMS destination for which a listener is active. A session bean polls a JMS destination until a message arrives, gets the parsed message as an object, and can use methods to retrieve the message data.
recognition profile
In the 3270 Terminal Services tool, a list of the identifiers that uniquely identify the state of a screen, that is, the set of conditions that apply to the screen at the time the screen was imported from the host. Each screen state needs to be uniquely defined in its own recognition profile.
recognition table
In the 3270 terminal services development tool, the table that appears in the screen editor and provides a screen definition view and a recognition profile view of the screen that was imported.
record processing pattern
A job step pattern that reads and applies business logic to one record at a time from an input data source. The job step writes the results to an output data source and repeats the steps until all input records are processed.
recurring wait time trigger
A trigger that is evaluated based on a period of time. For example, a recurring wait time trigger can be evaluated every 30 minutes and fire if it detects that a specific business situation has occurred.
recursion
A programming technique in which a program or routine calls itself to perform successive steps in an operation, with each step using the output of the preceding step.
reentrance
A situation where a thread of control attempts to enter a bean instance again.
refactor
To make changes across a set of artifacts without changing the behavior of the application or its relationships to other elements.
reference
Logical names defined in the application deployment descriptor that are used to locate external resources for enterprise applications. At deployment, the references are bound to the physical location of the resource in the target operational environment.
reference binding
A binding that maps a logical name (a reference) to a JNDI name.
referential integrity
  1. 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.
  2. 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.
refresh pack
A cumulative collection of fixes and new functions that moves the product up one modification level and a particular service level. For example, a refresh pack might move a product from Version 1 Release 1 Modification level 1 Fix Pack 5 to Version 1 Release 1 Modification level 2 Fix Pack 3. See also fix pack, interim fix.
region
A contiguous area of virtual storage that has common characteristics and that can be shared between processes.
registered user (RU)
A portal user who has a user ID and password for logging in to a portal. See also anonymous user, authenticated user.
registry
A repository that contains access and configuration information for users, systems, and software.
regular expression
A set of characters, meta characters, and operators that define a string or group of strings in a search pattern. See also Perl-compatible regular expression.
rejection code
A code assigned when a score cannot be derived. Typically, one reject code per scorecard only is assigned.
relationship instance
The runtime instantiation of the relationship. The relationship definition is a template for the relationship instance.
relationship management application (RMA)
An application used to manage authorizations. Among other things, it converts bootstrap authorizations created by WebSphere BI for FN into the RMA authorizations required to satisfy FIN PV03.
relationship management data store (RMDS)
A set of database tables in which WebSphere BI for FN stores data about bootstrap and relationship management application (RMA) authorisations.
relationship manager
A tool for creating and manipulating relationship and role data at run time.
relationship role
In EJB programming, a traversal of the relationship between two entity beans in one direction or the other. Each relationship that is coded in the deployment descriptor defines two roles.
relationship service
A service used to model and maintain relationships across business objects and other data
relative type name
The name of a type relative to another type. Relative type names are used when defining components, syntax items, and comment types.
release
To send changed files from the workbench to the team server so that other developers on the team can catch up (synchronize) with the updated version.
release character
The character that indicates that a separator or delimiter is to be used as text data instead of as a separator or delimiter. The release character must immediately precede the delimiter.
reliability, availability, and serviceability (RAS)
A combination of design methodologies, system policies, and intrinsic capabilities that, taken together, balance improved hardware availability with the costs required to achieve it. Reliability is the degree to which the hardware remains free of faults. Availability is the ability of the system to continue operating despite predicted or experienced faults. Serviceability is how efficiently and nondisruptively broken hardware can be fixed. See also RAS attribute, RAS granularity.
remote
Pertaining to a system, program, or device that is accessed through a communication line.
remote authentication dial-in user service (RADIUS)
An authentication and accounting system that uses access servers to provide centralized management of access to large networks.
remote database
A database to which a connection is made by using a database link, while connected to a local database. See also local database.
Remote Direct Memory Access (RDMA)
A communication technique in which data is transmitted from the memory of one computer to that of another without passing through a processor. RDMA accommodates increased network speeds.
remote file system
A file system residing on a separate server or operating system.
remote file transfer instance
A file that contains information about the method used for remotely transferring a file.
remote home interface
In enterprise beans, an interface that specifies the methods used by remote clients for locating, creating, and removing instances of enterprise bean classes. See also local home interface.
remote interface
In EJB programming, an interface that defines the business methods that can be called by a client. See also home interface.
remote messaging, remote support, and web applications pattern
A reusable deployment environment architecture for IBM Business Process Management products and solutions in which the functional components of the environment (messaging, support, web-based components, and application deployment) are split across four clusters.
remote messaging and remote support pattern
A reusable deployment environment architecture for IBM Business Process Management products and solutions in which the functional components of the environment (messaging, support, web-based components, and application deployment) are split across three clusters. Web-based components reside on the support or the application-deployment cluster.
remote method
A business method in the remote interface that is callable by a client. See also Remote Method Invocation.
Remote Method Invocation (RMI)
A protocol that is used to communicate method invocations over a network. Java Remote Method Invocation is a distributed object model in which the methods of remote objects written in the Java programming language can be invoked from other Java virtual machines, possibly on different hosts. See also remote method.
Remote Method Invocation over Internet InterORB Protocol (RMI/IIOP)
Part of the Java Platform, Standard Edition (Java SE) model that developers can use to program in the Java language to work with RMI interfaces, but use IIOP as the underlying transport.
Remote OSE
A transport mechanism that is based on the Open Servlet Engine (OSE) protocol and is used to communicate between two separate machines in the application server environment.
Remote Procedure Call (RPC)
A protocol that allows a program on a client computer to run a program on a server.
remote product installation
A product installation onto a remote workstation that has a pre-installed operating system.
remote queue
A queue that belongs to a remote queue manager. Programs can put messages on remote queues, but they cannot get messages from remote queues. See also local queue.
remote queue manager
A queue manager to which a program is not connected, even if it is running on the same system as the program. See also local queue manager.
remove method
In enterprise beans, a method defined in the home interface and invoked by a client to destroy an enterprise bean.
repertoire
Configuration information that contains the details necessary for building a Secure Sockets Layer (SSL) connection.
replica
A server that contains a copy of the directory or directories of another server. Replicas back up servers in order to enhance performance or response times and to ensure data integrity.
replication
  1. 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.
  2. 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.
replication domain
A collection of application server components that share data. These components might include HTTP sessions, dynamic cache, stateful session beans, or the session initiation protocol (SIP) component.
replication entry
A runtime component that handles the transfer of internal data.
reply message
A type of message used for replies to request messages. See also report message, request message.
reply-to queue
The name of a queue to which the program that issued an MQPUT call wants a reply message or report message sent.
report message
A type of message that gives information about another message. A report message can indicate that a message has been delivered, has arrived at its destination, has expired, or could not be processed for some reason. See also reply message, request message.
repository
A persistent storage area for data and other application resources.
repository checkpoint
A function that backs up copies of files from the master configuration repository. The backup files can be used to restore the configuration to a previous state if future configuration changes cause operational problems.
Representational State Transfer (REST)
A software architectural style for distributed hypermedia systems like the World Wide Web. The term is also often used to describe any simple interface that uses XML (or YAML, JSON, plain text) over HTTP without an additional messaging layer such as SOAP. See also RESTful.
request
In a request/response interaction, the role performed by a business object that instructs a connector to interact with an application or other programmatic entity.
request consumer binding
A definition of the security requests for the request message that is received by a web service.
requester
The source of a request to access data at a remote server.
request flow
The flow of the message from the service requester.
Request for Comments (RFC)
In Internet communication, one of a series of numbered documents that describe Internet communication protocols.
request generator binding
A definition of the security requests for the request message that is sent to a web service.
request-level RAS granularity
The level of RAS granularity at which RAS attributes are assigned on a request-by-request basis to all requests for a particular request classification, such as HTTP requests that end in .jpg, a specific HTTP request for a URI such as /PlantsByWebSphere/index.html, or all IIOP requests for a particular EJB. See also RAS granularity.
request message
A type of message used to request a reply from another program. See also reply message, report message.
request metrics
A mechanism to monitor and troubleshoot performance bottlenecks in the system at an individual request level.
request receiver binding
A definition of the security requirements for the request message that is received from a request to a web service.
request/reply
A type of messaging application in which a request message is used to request a reply from another application. See also datagram.
request sender binding
A definition of the security requirements for the request message that is sent to a web service.
required component
A component that can be defined within a group type to represent a data object that must be present in the data. The component range minimum specifies how many occurrences of the data object are required.
resource
A person, piece of equipment, or material that is used to perform an activity.
Resource Access Control Facility (RACF)
An IBM licensed program that provides access control by identifying users to the system; verifying users of the system; authorizing access to protected resources; logging unauthorized attempts to enter the system; and logging accesses to protected resources.
resource adapter
  1. Map input and output data sources that are used to retrieve and route data. Resource adapters provide access to databases, files, messaging systems, and other data sources and targets. Each adapter includes a set of adapter commands that can be used to customize its operation.
  2. A system-level software driver that is used by an EJB container or an application client to connect to an enterprise information system (EIS). A resource adapter plugs in to a container; the application components deployed on the container then use the client API (exposed by adapter) or tool-generated, high-level abstractions to access the underlying EIS. (Sun) See also container, enterprise information system.
resource adapter archive (RAR)
A Java archive (JAR) file that is used to package a resource adapter for the Java 2 Connector (J2C) architecture.
resource class
An attribute of a resource that is used to group resources according to the subsystem to which they belong and the purpose for which they are used.
resource collection
Jython objects that represent collections of resources which have a specific characteristic in common.
resource distribution report
A report, generated by the Customization Definition Program (CDP), that describes the resources required by an instance.
resource environment reference
A reference that maps a logical name used by the client application to the physical name of an object.
resource file
A file that is used to create, in a runtime environment, one or more resources of a particular class.
resource manager
  1. A participant, in the execution of a one-phase or two-phase commit, that has recoverable resources that could have been modified. The resource manager has access to a recovery log so that it can commit or roll back the effects of the logical unit of work to the recoverable resources.
  2. An application, program, or transaction that manages and controls access to shared resources such as memory buffers and data sets. WebSphere MQ, CICS, and IMS are resource managers.
resource manager local transaction (RMLT)
A resource manager view of a local transaction that represents a unit of recovery on a single connection that is managed by the resource manager.
resource property
A property for a JDBC data source in a server configuration, for example the server name, user ID, or password.
Resource Recovery Services (RRS)
A component of z/OS that uses a sync point manager to coordinate changes among participating resource managers.
resource set
A collection of resources that are members of the same class and that share a common scope. A resource set also determines which other resource sets are its prerequisites and which place holders are used within the corresponding resource file templates.
response file
A file containing predefined values that is used instead of someone having to enter those values one at a time. See also silent installation.
response flow
The flow of the message from the service provider to the service requester.
response generator binding
A definition of the security requests for the response message that is sent to a web service.
response receiver binding
A definition of the security requirements for the response message that is received from a request to a web service.
response sender binding
A definition of the security requirements for the response message that is sent to a web service.
REST
See Representational State Transfer.
restart attribute
An attribute that specifies that processing of the input data should continue even though a data object of the component is invalid. The restart attribute provides instructions for handling errors encountered in a data stream and can be assigned to a component within a group type.
RESTful
Pertaining to applications and services that conform to Representational State Transfer (REST) constraints. See also Representational State Transfer.
result
The consequence of reaching an end event. Types of results include message, error, compensation, and signal. There can be multiple results, such as a result that produces a message and another result that sends a signal.
result event
An action that is generated by the technology connectors and sent back to the runtime server to be processed as a new event.
result set
A set of row values as returned by, for example, a cursor or procedure.
result tree
The output document that is created when an XSL file is used to transform an XML file.
resume
To continue execution of an application after an activity has been suspended.
RetePlus mode
A rule execution mode for matching patterns with objects. The RetePlus mode is used by the rule engine to minimize the number of rules and conditions that need to be evaluated, compute which rules should be executed, and identify in which order these rules should be fired.
retraction
The action of removing an object bound to a rule variable from the working memory.
return code (RC)
A value returned by a program to indicate the result of its processing. Completion codes and reason codes are examples of return codes.
reverse proxy
An IP-forwarding topology where the proxy is on behalf of the back-end HTTP server. It is an application proxy for servers using HTTP.
RFC
See Request for Comments.
rich media
In a web page, content that is aural, visual, or interactive, such as audio or video files.
Rich Site Summary (RSS)
An XML-based format for syndicated web content that is based on the RSS 0.91 specification. The RSS XML file formats are used by Internet users to subscribe to websites that have provided RSS feeds. See also feed.
rich text
A field that can contain objects, file attachments, or pictures as well as text with formatting options such as italics or boldface.
ripplestart
An action where the system waits for a member in a cluster to start before starting the next member of the cluster.
RMA
See relationship management application.
RMA authorisation
An authorisation that has been processed by a relationship management application (RMA).
RM distribution file
A file used to exchange relationship data with an relationship management application (RMA). It is the file that is created when you export bootstrap authorizations, and it is the file from which you import authorizations from an RMA.
RMDS
See relationship management data store.
RMI
See Remote Method Invocation.
RMI/IIOP
See Remote Method Invocation over Internet InterORB Protocol.
RMLT
See resource manager local transaction.
RM report
A report used to determine whether all the relationships that are required when using PV03 exclusively have already been recorded, and whether corresponding authorisations already exist.
role
  1. A logical group of principals that provides a set of permissions. Access to operations is controlled by granting access to a role.
  2. 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.
  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. 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.
  5. 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.
role-based authorization
The use of authorization information to determine whether a caller has the necessary privilege to request a service.
role-based security
Security that provides access rights to certain files, business processes, web templates, and features, according to the permissions associated with the user account.
role mapping
The process of associating groups and principals recognized by the container to security roles specified in the deployment descriptor.
rollback
The process of restoring data that was changed by an application program or user.
root
The user name for the system user with the most authority.
root element
The implicit highest-level node of a parsed XML document. You may not always be able to predict which element will be the document element of a parsed instance, but it will always have a root node that you can count on being able to use for preliminary or setup processing.
root type
The type from which all other types stem. The root type represents the data objects of all the types in the tree.
routing policy
A set of rules that determine how the server routes incoming requests.
row
The horizontal component of a table, consisting of a sequence of values, one for each column of the table.
RPC
See Remote Procedure Call.
RRS
See Resource Recovery Services.
RSA encryption
A system for public-key cryptography used for encryption and authentication. It was invented in 1977 by Ron Rivest, Adi Shamir, and Leonard Adleman. The security of the system depends on the difficulty of factoring the product of two large prime numbers.
RSS
See Rich Site Summary.
RU
See registered user.
rule
  1. The criteria or circumstances that are defined to trigger an event. For example, rules can be triggered during entry to or exit from a zone and can be specified for a tag ID, class, or group.
  2. A statement that defines or constrains some aspect of the business. See also business rule, event rule.
rule analysis
A mechanism for checking whether business rules are semantically consistent. Inconsistencies can be found either in the rule itself, or with respect to other rules.
RuleApp
A deployment and management unit for Rule Execution Server that can contain one or more rule sets.
RuleApp archive
An archive that allows RuleApps to be stored to a file system. RuleApp archives are saved in a strict directory structure.
RuleApp project
An Eclipse project that performs the deployment of a RuleApp to a running Rule Execution Server.
rule artifact
An item used to express a business policy in a business rule application. Action rules and decision tables are examples of rule artifacts.
Rule Designer
A business rule application development tool integrated into the Eclipse development environment and dedicated to the creation and management of business rule applications.
RuleDoc
A document containing business rules and rule metadata that can be edited.
rule editor
A graphical tool used to create rules.
rule engine
A software component that evaluates and executes business rules. See also decision engine.
Rule Execution Server
A module that integrates into the Java EE environment, and as such offers the standard services of an application to execute, control, and monitor rule sets contained in RuleApps.
Rule Execution Server configuration project
A project in which a server configuration persists. The configuration provides the information necessary to make a connection to the rule execution server when a RuleApp is applied.
Rule Execution Server console
A web user interface that provides support for deploying RuleApps and the management of executable resources on Rule Execution Server.
rule execution set
A collection of rules that are intended to be executed together.
rule flow
A method of controlling and ordering the execution of rule artifacts. A rule flow is defined in terms of tasks.
rule instance
An occurrence of a rule that includes the combination of objects in the working memory that match the patterns specified in the rule. More than one instance of the same rule may exist in the agenda at any time because the rule patterns may be satisfied by more than one object or set of objects.
rule logic
The business logic, which is expressed by a business rule, that consists of decisions that affect how a business responds to specific business conditions. For example, a decision that determines how much of a discount to give to a preferred customer is rule logic.
rule model
A model that defines the set of items that are managed in a rule and event projects, and their associated properties.
rule package
A container for organizing rule artifacts according to business logic. Rule packages become folders after they have been published to Decision Center.
rule perspective
An Eclipse perspective that defines the initial set and layout of views in the workbench window that will be used in the development of a rule project.
rule project
A type of project in which the user can manage and organize rule artifacts and business object models.
rule project template
A partly completed rule project that can be used to create a series of rule projects with the same structure.
rules-based personalization
Personalization technology that enables you to customize web content based on user needs and preferences, and business requirements.
rule schedule
An interface for modifying the values of a business rule in the rule logic selection record.
rule session
A runtime connection between a client and a rule engine. A rule session may consume initialized rule engine resources.
rule set
  1. An if-then statement that is composed of a set of textual statements, or rules, that are evaluated sequentially. If is the condition and then is the action. Each condition that evaluates to true is acted upon. See also action rule, decision table, if-then rule.
  2. A set of rules that can be executed by the rule engine and includes rule artifacts and non-rule artifacts.
rule set extractor
A mechanism for selecting the rules of the rule set to be deployed. Selection is typically based on the value of rule properties.
rule set interceptor
A mechanism that allows services to be added to an execution component transparently and to be triggered automatically when certain events occur.
rule set parameter
A parameter that can be defined to set and retrieve values on a rule set. Rule set parameters are accessible from outside of the rule set, and therefore are a bridge between the business logic and the application.
rule set signature
The list of in, out, and inout parameters of a rule set.
rule set variable
A variable that can be defined to be used in all the rule artifacts of a rule set.
rule task
In a rule flow, a task that refers to rule artifacts and orders them.
rule template
A partly completed business rule that can be used to create a series of rules with the same structure.
RunAs role
A role used by a servlet or an enterprise bean component to invoke and delegate a role to another enterprise bean.
run map
An executable map that is called using the RUN function.
runtime
Pertaining to the time period during which a computer program is running.
run time
The time period during which a computer program is running.
runtime environment
A set of resources that are used to run a program or process.
runtime rule selection
In a rule task, a way to filter rule artifacts at run time. Runtime rule selection is expressed in rule statements.
runtime task
A generated administrative action plan that contains recommendations to improve the health and performance of a runtime environment.
runtime topology
A depiction of the momentary state of the environment.
RUP
See Rational Unified Process.

S

SAAJ
See SOAP with attachments API for Java.
SACL
See State Adaptive Choreography Language.
SAF
See System Authorization Facility.
SAG
See SWIFTAlliance Gateway.
SAG MQ connection
An entity within an SAG that encapsulates a WebSphere MQ connection.
SAML
See Security Assertion Markup Language.
SAS
See Secure Association Service.
SAX
See Simple API for XML.
SCA
See Service Component Architecture.
SCA component
A building block of the Service Component Architecture, used to build SCA modules such as mediation modules.
SCA export binding
A concrete definition that specifies the physical mechanism used by a service requester to access an SCA module; for example, using SOAP/HTTP.
SCA export interface
An abstract definition that describes how service requesters access an SCA module.
SCA import binding
A concrete definition that specifies the physical mechanism used by an SCA module to access an external service; for example, using SOAP/HTTP.
SCA import interface
An abstract definition that describes how an SCA module accesses a service.
scalability
The ability of a system to expand as resources, such as processors, memory, or storage, are added.
SCA module
A module with interfaces that conforms to the Service Component Architecture (SCA).
SCA request
A service request that conforms to the Service Component Architecture (SCA). An SCA module routes the request to a service provider, after having done any additional processing specified by the module.
SCA run time
The server functions that provide support for the Service Component Architecture.
scenario
  1. A set of actions representing a business process within the context of a collaboration. Scenarios can be used to partition collaboration logic. For example, if a collaboration handles one type of business object with various possible verbs, the user might develop Create, Update, and Delete scenarios. See also activity.
  2. A real or fictitious use case that can be used to validate the behavior of rules with test suites or simulations. Each scenario contains all the necessary information required for rules to execute properly.
scenario provider
An object that defines how scenarios are loaded for test suites and simulations.
scheduler
A service that provides time-dependent services.
schema
A collection of database objects such as tables, views, indexes, or triggers that define a database. A schema provides a logical classification of database objects.
schema document definition
A description or layout of an XML document based on an XML schema.
SCM
See software configuration management.
scope
  1. In web services, a property that identifies the lifetime of the object serving the invocation request.
  2. A specification of the boundary within which system resources can be used.
scorecard
A set of measurements on a subject to help to make a business decision. See also scoring strategy.
scorecard property
A property that defines the reasoning strategy and the scoring strategy. Scorecard properties are used together to determine the final score and the reason codes that are displayed.
scoring strategy
A strategy to calculate the final score from each of the attribute scores for the overall scorecard. See also scorecard.
scratchpad area (SPA)
A work area used in conversational processing to retain information from an application program across executions of the program.
screen
The display that the user sees when connected to a 3270 application on the host system. A single 3270 application can include many screens, each of which has a purpose within the context of the application.
screen editor
A 3270 terminal service development tool that enables a developer to create and modify recognition profiles for an imported screen and to assign names to the fields on the screen definition.
screen file
The result of importing a screen definition from a 3270 application into the 3270 terminal service development workbench. A screen file represents a screen definition. The screen definition contains identifiers such as the number of fields on the screen and the row and column position of fields on the screen. There are multiple screen files per 3270 terminal service project. Each screen file can have multiple recognition profiles assigned to it.
screen import
The process of importing a screen definition (in its current state) and saving it to a screen file within the 3270 terminal service tools workbench, for the purpose of generating recognition profiles and custom screen records. Use the 3270 terminal service recorder to import screens.
screen recognition
A runtime function that determines the state of a screen and processes the screen in accordance with the identifiers in the recognition profiles. Screen recognition compares the screen as presented by the 3270 application to the defined recognition profiles to determine which screen state applies.
screen state
The set of conditions (at the time the screen was imported from the host) that determine the allowed and required processing on the screen. A screen state operates on input to change the status, cause an action, or result in a particular output screen. A single screen can have multiple states and the allowed user actions for the screen vary depending on which state the screen is in.
script
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.
scripting
A style of programming that reuses existing components as a base for building applications.
scriptlet
A mechanism for adding scripting language fragments to a source file.
script package
A compressed file consisting of an executable file and supporting files that are added to pattern topologies to customize the behavior of a cell.
SDK
See software development kit.
SDO
See Service Data Objects.
SDO repository
A database that is used for storing and serving the Web Services Description Language (WSDL) definitions of web services. For example, the WSDL definitions for service integration bus-enabled web services are stored as service data objects in an SDO repository.
search center
A portlet that enables site users to search for keywords. See also search collection, search service.
search collection
A searchable collection of documents that can span multiple content sources. See also search center, search service.
search service
A service that is used to define the configuration parameters for a search collection. A search service can be local, remote, inside the product, or outside the product. See also search center, search collection.
secret key
A key that both encrypts and decrypts information. In symmetric cryptography, both communicating parties use a secret key. In asymmetric or public key cryptography, a public key and a private key are used to encrypt and decrypt information.
Secure Association Service (SAS)
An authentication protocol used to communicate securely for the client principal by establishing a secure association between the client and server.
Secure FTP
An FTP protocol that uses Secure Sockets Layer (SSL) protocol.
Secure Hash Algorithm (SHA)
An encryption method in which data is encrypted in a way that is mathematically impossible to reverse. Different data can possibly produce the same hash value, but there is no way to use the hash value to determine the original data.
Secure Internet Protocol Network
A SWIFT network based on the Internet Protocol (IP) and related technologies.
Secure Shell (SSH)
A network protocol for secure data exchange between two networked devices. The client can use public-key and private-key authentication, or password authentication, to access the remote server.
Secure Sockets Layer (SSL)
A security protocol that provides communication privacy. With SSL, client/server applications can communicate in a way that is designed to prevent eavesdropping, tampering, and message forgery. See also certificate authority.
security administrator
The person who controls access to business data and program functions.
Security Assertion Markup Language (SAML)
An XML framework for exchanging authentication and authorization information.
security attribute propagation
The transportation of security attributes from one server to another server in an application server configuration.
security constraint
A declaration of how to protect web content, and how to protect data that is communicated between the client and the server.
security domain
The set of all the servers that are configured with the same user registry realm name.
security entity
Entities used to specify what a user is authorized to do. Security entities include roles and users.
security permission
Authorization granted to access a system resource.
security policy
A written document that defines the security controls that you institute for your computer systems. A security policy describes the risks that you intend these controls to minimize and the actions that should be taken if someone breaches your security controls.
security role
In Java EE, an abstract logical grouping of users that is defined by the application assembler. When an application is deployed, the roles are mapped to security identities, such as principals or groups, in the operational environment. (Sun)
security role reference
A role that defines the access levels that users have and the specific resources that they can modify at those levels.
security token
A representation of a set of claims that are made by a client that can include a name, password, identity, key, certificate, group, privilege, and so on.
segment
An EDI logical unit of information. EDI segments are made up of data elements and composites. Segments are delimited; their components are separated by a delimiter.
segmentation
A strategy that is used for building complex scorecards. This strategy defines segments or subgroups where a scorecard split might be necessary.
segmentation score
The maximum score of the scorecard when complex reasoning is not used. It is used to tune the contribution factor of a scorecard within the complex scorecard. The segmentation score is a property in a complex scorecard.
selector component
A component that provides a means of interposing a dynamic selection mechanism between the client application and a set of target implementations.
sender bean
In extended messaging, an enterprise bean (stateless session bean) that can be built to send asynchronous messages. A sender bean translates its method invocation into a JMS message, then passes that message to JMS. It can also retrieve a response message, translate that message into a result value, and return it to the caller.
sensor
A program that reads information from a managed software system to create configuration information.
sequence flow
A connecting object, represented by a solid graphical line, that shows the order of flow objects in a process or choreography. A sequence flow can cross the boundaries between swimlanes of a pool, but cannot cross the boundaries of a pool. There are two types of sequence flows: exception flow and normal flow.
sequence grouping
The specification of the order in which entity beans update relational database tables.
sequence line
An element that controls the sequence of activities and events during process execution.
sequence number
A number assigned to each message exchanged between two nodes. The number is increased by one for each successive message. It starts from zero each time a new session is established.
sequential mode
A rule execution mode for stateless pattern-matching. With this mode, rules can be processed sequentially, which can improve the speed of rule processing in specific cases. The sequential mode can be selected for individual tasks in a rule flow.
serialization
In object-oriented programming, the writing of data in sequential fashion to a communications medium from program memory.
serializer
A method for converting object data to another form such as binary or XML. See also deserialization.
series
The consecutive occurrences of a component. In map rules, the [ ] characters denote an indexed member of a series.
servant region
A contiguous area of virtual storage that is dynamically started as load increases and automatically stopped as load eases.
server
A software program or a computer that provides services to other software programs or other computers. See also client, host.
server and bus environment
The environment in which servers, service integration buses, and their resources are configured and managed.
server cluster
A group of servers that are typically on different physical machines and have the same applications configured within them, but operate as a single logical server.
server configuration
A resource that contains information required to set up and deploy to an application server.
server definition
A definition for a computer that hosts a command server, to which systems under development in the Integration Flow Designer can be assigned as the intended execution server.
server group
A group of Rule Execution Server for z/OS instances that are configured to be transferred to another if a server fails or if there is a planned outage. A server group can include one to 32 server instances.
server implementation object
Enterprise beans that client applications require to access and implement the services that support those objects.
server-level RAS granularity
The level of RAS granularity at which RAS attribute values are assigned on a server-wide basis. RAS attribute values defined at the server-level are assigned to all requests that the server processes. See also RAS granularity.
server message
A message that is routed to a server application for processing, or a delivery notification that is routed to a client application to acknowledge the receipt of a client message by its destination.
server operation
A collection of Java or non-Java process definitions that you can define to run on middleware servers. You can create server operations to enable or disable tracing, start or stop applications, query the running state of a server, and so on.
server project
A project that contains information about test and deployment servers and their configurations.
server-side
Pertaining to an application or component of an application that runs on a server rather than on the client. JSP and servlets are two examples of technologies that enable server-side programming.
server-side include (SSI)
A facility for including dynamic information in documents sent to clients, such as current date, the last modification date of a file, and the size or last modification of other files.
service
  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. A program that is used to implement activities or to perform one-time or recurring system tasks.
  3. In service-oriented architecture, a unit of work accomplished by an interaction between computing devices.
  4. An offering that provides skilled assistance to customers. A service may include consulting, education and training, offering enabling services, managed operations, integration and application development. Services are distinguished from products by their intangibility, inseparability, perishability and variability. See also Advanced Integration service, General System service, integration service.
service application
An application used to deploy mediation modules.
service bundle (SVB)
A set of services that logically belong together, for example, because they share resources such as a status table or error processing queue. A service bundle contains the definition files for all resources required to provide the services, for example definition files for message flows, queues, and database tables. A service bundle has a unique name in the scope of an instance. A service bundle must be assigned to an organizational unit and loaded into a server before it is operational.
service bundle set
A group of service bundles that are packaged together to simplify ordering. A definition file that defines the resource classes, resource file types, place holders, and server types that can be used by the service bundles in the set is associated with each service bundle set.
service class
A group of work that has the same service goals or performance objectives, resource requirements, or availability requirements. For workload management, a service goal and, optionally, a resource group is assigned to a service class.
service client
A requester that invokes functions in a service provider.
service component
A component that configures a service implementation. A service component consists of an implementation and one or more interfaces, which defines its inputs, outputs, and faults, and also its references, if applicable.
Service Component Architecture (SCA)
An architecture in which all elements of a business transaction, such as access to web services, Enterprise Information System (EIS) service assets, business rules, workflows, databases and so on, are represented in a service-oriented way.
service context
Part of a General InterORB Protocol (GIOP) message that is identified with an ID and contains data used in specific interactions, such as security actions, character code set conversion, and Object Request Broker (ORB) version information.
Service Data Objects (SDO)
An open standard for enabling applications to handle data from heterogeneous data sources in a uniform way, based on the concept of a disconnected data graph. See also business object.
service definition
One or more WSDL files that describe a service. Service definitions are produced by the Definition, Deployment, Adapter, Skeleton, and Proxy wizards.
service description
The description of a web service, which can be defined in any format such as WSDL, UDDI, or HTML.
service destination
A specialization of a service integration bus destination. Each service destination can directly represent the web service implementation or can indirectly represent the service through a Web Services Description Language (WSDL) document.
service document
A document that describes a web service, for example a Web Services Description Language (WSDL) document.
service input queue
The queue from which a service retrieves the messages it is to process. In WebSphere BI for FN, this queue is implemented as a WebSphere MQ local queue.
service integration bus (SIBus)
A managed communication mechanism that supports service integration through synchronous and asynchronous messaging. A bus consists of interconnecting messaging engines that manage bus resources.
service integration bus link
A link between messaging engines on different service integration buses. This enables requests and messages to pass between the buses.
service integration bus web services enablement
A software component that enables web services to use IBM service integration technologies. This capability provides a quality of service choice and message distribution options for web services, with mediations that support message rerouting or modification.
service integration logic
Integration logic on an enterprise service bus to mediate between requesters and providers. The logic performs a number of functions such as to transform and augment requests, convert transport protocols, and route requests and replies automatically
service integration technology
Technology that provides a highly-flexible messaging system for a service-oriented architecture (SOA). This supports a wide spectrum of quality of service options, protocols, and messaging patterns. The technology supports both message-oriented and service-oriented applications.
service interface queue
The queue into which applications place messages that are to be processed by a service. In WebSphere BI for FN, each OU that uses a particular service has its own service interface queue, and this queue is implemented as a WebSphere MQ alias queue.
service level agreement (SLA)
  1. In IBM Business Process Management, a rule that a user creates to analyze the performance of business processes over time. An SLA establishes a condition that triggers a consequence and creates a report for one or more activities. Conditions in SLAs are based on a standard or custom key performance indictator (KPI).
  2. A contract between a customer and a service provider that specifies the expectations for the level of service with respect to availability, performance, and other measurable objectives.
service message object (SMO)
A service data object that can exist only in a mediation flow component. The service message object is composed of a body and headers. The body contains the parameters of the invoked interface operation, and the headers may contain information such as service invocation, transport protocol, mediation exception, JMS properties, or correlation information.
service-oriented architecture (SOA)
A conceptual description of the structure of a software system in terms of its components and the services they provide, without regard for the underlying implementation of these components, services and connections between components.
service policy
A performance goal that is assigned to a specific application URI to help designate the business importance of different request types.
service project
A collection of related items used to build a service.
service provider
A company or program that provides a business function as a service.
service registry
A repository that contains all of the information that is required to access a web service.
service requester
The application that initiates an interaction with a web service. The service requester binds to the service by using the published information and calls the service.
services
Collections of network endpoints or ports that are used to aggregate a set of related ports.
service task
A task that uses a service implementation, such as a web service, that a BPM execution engine runs. This task does not require user interaction and does not appear on a task list.
service type definition
In Universal Discovery Description and Integration (UDDI), a description of specifications for services or taxonomies.
service virtualization
A virtualization that compensates for the differences in the syntactic details of the service interactions so that the service requester and provider do not have to use the same interaction protocol and pattern or the same interface, nor do they have to know the identities of the other participants.
servlet
A Java program that runs on a web server and extends the server functions by generating dynamic content in response to web client requests. Servlets are commonly used to connect databases to the web.
servlet archive
A file that contains the same components as a servlet application. Unlike web archives, servlet archives can have only a sip.xml deployment descriptor and not a web.xml deployment descriptor.
servlet container
A web application server component that invokes the action servlet and that interacts with the action servlet to process requests.
servlet filtering
The process of transforming a request or modifying a response without exposing the resource used by the servlet engine. See also filter.
servlet mapping
A correspondence between a client request and a servlet that defines their association.
session
  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. In Java EE, an object used by a servlet to track user interaction with a web application across multiple HTTP requests.
  3. A series of requests to a servlet originating from the same user at the same browser.
session affinity
A method of configuring applications in which a client is always connected to the same server. These configurations disable workload management after an initial connection by forcing a client request to always go to the same server.
session bean
An enterprise bean that is created by a client and that typically exists only for the duration of a single client/server session. (Sun) See also entity bean, stateful session bean, stateless session bean.
session facade
A mechanism for separating the business and client tiers of an enterprise application by abstracting the data and business methods so that clients are not tightly coupled with the business logic and not responsible for data integrity. Implemented as session enterprise beans, session facades also decouple lower-level business components from one another.
Session Initiation Protocol (SIP)
A protocol for initiating interactive multi-media sessions. See also siplet.
session sequence number
A sequentially incremented 10 byte identifier that is assigned to each request unit in an LT session. It is formed by concatenating the 4 byte session number with a 6 byte sequence number.
setter method
A method whose purpose is to set the value of an instance or class variable. This capability allows another object to set the value of one of its variables. See also getter method.
severity code
A number that indicates the seriousness of an error condition.
SHA
See Secure Hash Algorithm.
shadow zone
A zone where the tags might not be visible temporarily because they are out of reach of the tag reader infrastructure or the signals are shielded. WebSphere Sensor Events assumes that a tag continues to be in the shadow zone at the last reported position after it has been seen. No alert is generated if the tag is no longer visible.
shard
An instance of a partition. A shard can be a primary or replica. See also container server.
shared library file
A file that consists of a symbolic name, a Java class path and a native path for loading Java Native Interface (JNI) libraries. Applications that are deployed on the same node as this file can access this information.
shared lock
A lock that limits concurrently running application processes to read-only operations on database data. See also exclusive lock.
shared place
A place created for a community of people with a common purpose. Shared places can be public or restricted. The place creator (who automatically becomes the place manager) specifies whether a place is public or restricted during place creation.
shared service instance
An application capability that is made available in the cloud as an always-on, multitenant, elastic service for multiple users or applications.
shell script
A program, or script, that is interpreted by the shell of an operating system.
shortcut bar
In Eclipse, the vertical toolbar at the left side of the workbench window that contains buttons for open perspectives and for fast views.
Short Message Service (SMS)
A message service that is used to send alphanumeric messages that are 160 characters or less between mobile phones.
short name
In personal communications, the one-letter name (A through Z) of the presentation space or emulation session.
short-running process
See microflow.
showcase
A business space that displays example widgets and data that describes a particular scenario to the user.
shredding
The process of breaking up an XML document for storage in database tables.
SIBus
See service integration bus.
side effect
An undesirable result caused by altering the values of nonlocal variables by a procedure or function.
signer certificate
The trusted certificate entry that is typically in a truststore file.
silent installation
An installation that does not send messages to the console but instead stores messages and errors in log files. A silent installation can use response files for data input. See also response file.
silent mode
A method for installing or uninstalling a product component from the command line with no GUI display. When using silent mode, you specify the data required by the installation or uninstallation program directly on the command line or in a file (called an option file or response file).
Simple API for XML (SAX)
An event-driven, serial-access protocol for accessing XML documents, used. A Java-only API, SAX is used by most servlets and network programs to transmit and receive XML documents. See also Document Object Model.
simple event processing
The processing of events that have rules that rely only on the data and timing that is associated with a single event.
Simple Mail Transfer Protocol (SMTP)
An Internet application protocol for transferring mail among users of the Internet.
Simple Network Management Protocol (SNMP)
A set of protocols for monitoring systems and devices in complex networks. Information about managed devices is defined and stored in a Management Information Base (MIB). See also Management Information Base, SNMP agent, SNMP trap.
simple type
A characteristic of a simple element that defines the type of data in a message (for example, string, integer, or float). In XML, a simple type cannot have element content and cannot carry attributes. See also complex type.
simple type name
The type name that appears next to the type icon in the type tree.
simulation
A faster-than-real-time performance of a process. Simulation enables organizations to observe how a process will perform in response to variations of inputs to the process, just as in a real-life work environment.
simulation snapshot
A record of the complete process model in a state that you want to preserve for simulation purposes. This record contains a copy of all the project elements the process uses, as well as any additional project elements.
single authorization
A setting allowing an action to be carried out by a single person. See also dual authorization.
single-cluster pattern
A reusable deployment environment architecture for IBM Business Process Management products and solutions in which the functional components of the environment (messaging, support, web-based components, and application deployment) are on one cluster.
single sign-on (SSO)
An authentication process in which a user can access more than one system or application by entering a single user ID and password.
singleton
A class that can be instantiated only once. A singleton class cannot be an interface.
SIP
See Session Initiation Protocol.
siplet
A Session Initiation Protocol (SIP) servlet that performs SIP signaling to back-end applications of the SIP server, such as the presence server or instant messaging server. See also Session Initiation Protocol.
situation
A significant occurrence that is detected when a set of conditions are met. For example, exceeding the limits of a Key Performance Indicator (KPI).
situation event
A Common Base Event that is emitted when a defined situation occurs.
sized attribute
An attribute that can be assigned to one or more components within a group type, whose value specifies the size, in bytes, of the component immediately following it.
skeleton
Scaffolding for an implementation class.
skin
An element of a graphical user interface that can be changed to alter the appearance of the interface without affecting its functionality.
SLA
See service level agreement.
smart card
An intelligent token that is embedded with an integrated circuit chip that provides memory capacity and computational capabilities.
smart folder
A view on a rule project that allows the user to display project elements grouped by property.
SMO
See service message object.
SMP/E
See SMP/E for z/OS.
SMP/E for z/OS (SMP/E)
An IBM licensed program that is used to install software and software changes on z/OS systems.
SMS
See Short Message Service.
SMTP
See Simple Mail Transfer Protocol.
snapshot
  1. In Business Process Manager, a capture of a process application or toolkit at a point in time. With a snapshot, a user can revert to a different version of a process or artifact.
  2. A capture of data at a point time for performance analysis.
  3. The state of a project or branch as captured at a specific time.
snippet
An excerpt of source code.
SNL
See SWIFTNet Link.
SNMP
See Simple Network Management Protocol.
SNMP agent
A server process that resides on a network node and is responsible for communicating with managers regarding that node. The node is represented as a managed object, which has various fields or variables that are defined in the appropriate MIB.
SNMP trap
An SNMP message sent from the SNMP agent to the SNMP manager. The message is initiated by the SNMP agent and is not a response to a message sent from the SNMP manager. See also Simple Network Management Protocol.
SOA
See service-oriented architecture.
SOAP
A lightweight, XML-based protocol for exchanging information in a decentralized, distributed environment. SOAP can be used to query and return information and invoke services across the Internet. See also web service.
SOAP encoding
Rules for serializing data over the SOAP protocol. SOAP encoding is based on a simple type system that is a generalization of the common features found in type systems in programming languages, databases, and semi-structured data.
SOAP with attachments API for Java (SAAJ)
An application programming interface (API) that is used to send XML documents over the Internet from a Java base.
Society for Worldwide Interbank Financial Telecommunication (SWIFT)
An industry-owned cooperative that supplies standardized messaging services and software to financial institutions.
socket
An identifier that an application uses to uniquely identify an end point of communication. The user associates a protocol address with the socket by associating a socket address with the socket.
Sockets Secure
A client/server architecture that transports TCP/IP traffic through a secure gateway. A SOCKS server performs many of the same services that a proxy server does.
softcopy
One or more files that can be electronically distributed, manipulated, and printed by a user.
software configuration management (SCM)
The tracking and control of software development. SCM systems typically offer version control and team programming features.
software development kit (SDK)
A set of tools, APIs, and documentation to assist with the development of software in a specific computer language or for a particular operating environment.
solution
A set of one or more related case types, tasks, steps, and other components that provide documents, data, business processing, and routing to case workers. For example, a solution for a human resources department might include a case type for new hires, a case type for retirement, and a case type for employee termination.
source code
A computer program in a format that is readable by people. Source code is converted into binary code that can be used by a computer.
source interface
In a mediation flow component, the interface that allows the service requester to access the mediation flow through an export.
source map component
An object that references an executable map within a source map file.
source tree
The XML input document that is transformed by an XSL stylesheet.
SPA
See scratchpad area.
special-subject
Generalization of a particular class of users; a product-defined entity independent of the user registry.
SPUFI
See SQL Processor Using File Input.
SQL
See Structured Query Language.
SQLJ
See Structured Query Language for Java.
SQL Processor Using File Input (SPUFI)
A facility of the TSO attachment subcomponent that enables the DB2I user to run SQL statements without embedding them in an application program.
SQL query
A component of certain SQL statements that specifies a result table.
SSH
See Secure Shell.
SSH File Transfer Protocol
A network protocol that provides the ability to transfer files securely over any reliable data stream.
SSI
See server-side include.
SSL
See Secure Sockets Layer.
SSL channel
A type of channel within a transport chain that associates a Secure Sockets Layer (SSL) configuration repertoire with the transport chain.
SSO
See single sign-on.
stack
An area in memory that typically stores information such as temporary register information, values of parameters, and return addresses of subroutines and is based on the principle of last in, first out (LIFO).
stack frame
A section of the stack that contains the local variables, arguments, and register contents for an individual routine, as well as a pointer to the previous stack frame.
stacking number
The number of application servers that are required for a dynamic cluster to use all the power of a node.
staff activity
An activity in a process that queries human interaction for decisions on how to proceed. A staff activity is used in a long-running process where the process will halt to await the outcome of the human interaction.
staging
The process of returning return data or an object from an offline or low-priority device to an online or higher priority device, typically on demand of the system or on request of the user.
stand-alone
Independent of any other device, program, or system. In a network environment, a stand-alone machine accesses all required resources locally.
stand-alone server
  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.
stand-alone task
A unit of work that exists independently of a business process, and implements human interaction as a service. See also human task, inline task.
standard portlet
A portlet that complies with one of the OASIS portlet standards: JSR168 or JSR286.
Standard Widget Toolkit (SWT)
An Eclipse toolkit for Java developers that defines a common, portable, user interface API that uses the native widgets of the underlying operating system. See also Abstract Window Toolkit, Swing Set.
star schema
A type of relational database schema that is composed of a set of tables comprising a single, central fact table surrounded by dimension tables.
start event
An event that indicates where a process starts. The start event starts the flow of the process and does not have any incoming sequence flow but can have a trigger. Start event types are none, message, timer, ad hoc, and error. See also ad hoc start event, error start event, message start event, none start event, timer start event.
start node
A node that identifies where a rule flow begins. A rule flow has one and only one start node.
star topology
In network architecture, a network topology in which every node on the network is connected to a central node or "hub," through which they communicate with each other.
stash file
  1. A file that hides other data files within it.
  2. A file that stores an encrypted version of the key database password. See also key database, key file.
state
In a business state machine, one of several discrete individual stages that are organized in sequence to compose a business transaction.
State Adaptive Choreography Language (SACL)
An XML notation that is used to define state machines.
stateful session bean
A session bean that acts on behalf of a single client and maintains client-specific session information (called conversational state) across multiple method calls and transactions. See also session bean, stateless session bean.
stateless session bean
  1. A session bean with no conversational state. All instances of a stateless bean are identical. (Sun) See also session bean, stateful session bean.
  2. A session bean that is a collection of operations. The server can optimize resources by reusing bean instances on every method call.
state machine
A behavior that specifies the sequences of states that an object or an interaction goes through during its life in response to events, together with its responses and actions.
static
A Java programming language keyword that is used to define a variable as a class variable.
static binding
static cluster
A group of application servers that participates in workload management. Membership for the static cluster is manually managed.
static web page
A web page that can be displayed without the additional client- or server-side processing that would be required for JavaServer Pages, servlets, or scripts.
static web project
A project that contains resources for a web application with no dynamic content such as servlets or JavaServer Pages (JSP) files, or Java code. A static web project can be deployed to a static HTTP server and does not require additional application server support.
step
A stage in a workflow where a distinct, well-defined action is performed. Each step on a workflow map represents a specific activity or task in the business process described by the map. For example, in insurance claims processing, verify account number and calculate deductible could be individual steps. A workflow consists of two or more steps.
storage node
A node used to provide the back-end storage and file system to store the data in a system.
stored procedure
A block of procedural constructs and embedded SQL statements that is stored in a database and that can be called by name. Stored procedures allow an application program to be run in two parts, one on the client and the other on the server, so that one call can produce several accesses to the database.
STP
See straight through processing.
straight through processing (STP)
A series of uninterrupted electronic processes across and throughout an enterprise which (1) secures an initial transaction as an electronic message, (2) transforms and transports it to its initial execution/processing location and (3) passes it through the processing cycle with little, if any, human intervention.
stream
In the CVS team programming environment, a shared copy of application resources that is updated by development team members as they make changes. The stream represents the current state of the project.
stream decryption
A symmetric algorithm that decrypts data one bit or byte of data at a time.
stream encryption
A symmetric algorithm that encrypts data one bit or byte of data at a time.
stream object
An object used in the TX Programming Interface that permits overrides to the loaded map input and output specifications.
string
In programming languages, the form of data used for storing and manipulating text.
Structured Query Language (SQL)
A standardized language for defining and manipulating data in a relational database.
Structured Query Language for Java (SQLJ)
A standard for embedding SQL in Java programs, defining and calling Java procedures and user-defined functions, and using database structured types in Java.
structured viewing
The tabular aspect of the Design view of the XML editor that separates the structural constituents of an XML document, such as elements and attribute types, from values, such as attribute values and textual content.
Struts
An open source framework designed to help developers create web applications that keep database code, page design code, and control flow code separated from each other.
Struts action
A class that implements a portion of a web application and returns a forward. The superclass for a Struts action is called the Action class.
Struts module
A Struts configuration file and a set of corresponding actions, form beans, and web pages. A Struts application comprises at least one Struts module.
Struts project
A dynamic web project with Struts support added.
stub
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.
style sheet
A specification of formatting instructions that, when applied to structured information, provides a particular rendering of that information (for example, online or printed). Different style sheets can be applied to the same piece of structured information to produce different presentations of the information.
subagent
An agent that the coordinator agent enlists to speed up SQL processing.
subarea
An area that is nested within another area.
subclass
In Java, a class that is derived from a particular class, through inheritance.
subflow
A sequence of processing steps, implemented using message flow nodes, that is designed to be embedded in a message flow or in another subflow. A subflow must include at least one Input or Output node. A subflow can be executed by a broker only as part of the message flow in which it is embedded, and therefore it cannot be deployed. See also message flow.
subflow node
A message flow node that represents a subflow. See also primitive.
subflow task
In a rule flow, a task that refers to another rule flow. A subflow task can reference a rule flow in the current project, or in a parent project.
subnet
See subnetwork.
subnet mask
For internet subnetworking, a 32-bit mask used to identify the subnetwork address bits in the host portion of an IP address.
subnetwork (subnet)
A network that is divided into smaller independent subgroups, which still are interconnected.
subprocess
A local process that is also a part of another process. See also deployment manager.
subquery
In SQL, a subselect used within a predicate, for example, a select-statement within the WHERE or HAVING clause of another SQL statement.
subscription
A record that contains the information that a subscriber passes to a local broker or server to describe the publications that it wants to receive.
substate
A state that is part of a composite state.
subsystem component
An Integration Flow Designer object that references another system which a user has defined.
subtree
A branch of a type tree that includes a type and all of the subtypes that stem underneath it.
subtype
A type that extends or implements another type; the supertype.
superclass
In Java, a class from which a particular class is inherited, perhaps with one or more classes in between.
superset
Given two sets A and B, A is a superset of B if and only if all elements of B are also elements of A. That is, A is a superset of B if B is a subset of A.
supertype
In a type hierarchy, a type that subtypes inherit attributes from.
suspend
To pause a process instance.
SVB
See service bundle.
SWIFT
See Society for Worldwide Interbank Financial Telecommunication.
SWIFT address
See bank identifier code.
SWIFTAlliance Gateway (SAG)
A SWIFT interface product extending SWIFTNet Link by additional services such as profile-based processing, and offering a WebSphere MQ interface.
SWIFTNet FileAct
A SWIFT interactive communication service supporting exchange of files between two applications.
SWIFTNet FIN
A SWIFT service providing FIN access using the Secure IP Network (SIPN) instead of the SWIFT Transport Network (STN). See also FIN.
SWIFTNet FIN batching
The transporting of more than one FIN message within a single InterAct message.
SWIFTNet InterAct
A SWIFT interactive communication service supporting exchange of request and response messages between two applications.
SWIFTNet Link (SNL)
A SWIFT mandatory software product to access all SWIFTNet services.
SWIFTNet PKI
See SWIFTNet public key infrastructure.
SWIFTNet public key infrastructure (SWIFTNet PKI)
SWIFT's mandatory security software and hardware installed with SWIFTNet Link. See also public key infrastructure.
SWIFTNet service
A SWIFT IP-based communication service that runs on the SIPN.
SWIFTNet service application
An application that uses SWIFTNet services. Financial organizations such as Continuous Linked Settlement (CLS) or the Global Straight Through Processing Association (GSTPA) offer such applications to financial institutions.
SWIFT transport network
A SWIFT network providing FIN and IFT service based on X.25 technology.
swimlane
  1. A visually separated row within a process flow diagram that groups all the activities in the process that are performed by a particular combination of roles, resources, organization units, or locations.
  2. See pool.
Swing Set
A collection of GUI components that runs consistently on any operating system that supports the Java virtual machine (JVM). Because they are written entirely in the Java programming language, these components provide functionality above and beyond that provided by native-platform equivalents. See also Abstract Window Toolkit, Standard Widget Toolkit.
SWT
See Standard Widget Toolkit.
symbolic link
A type of file that contains a pointer to another file or directory.
symmetric algorithm
An algorithm where the encryption key can be calculated from the decryption key and vice versa. In most symmetric algorithms, the encryption key and the decryption key are the same.
synchronization
The process of publishing and updating changes in a rule to a server.
synchronize
To add, subtract, or change one feature or artifact to match another.
synchronous process
A process that starts by invoking a request-response operation. The result of the process is returned by the same operation.
synchronous replica
A shard that receives updates as part of the transaction on the primary shard to guarantee data consistency, which can increase the response time compared with an asynchronous replica. See also asynchronous replica.
sync point
A point during the processing of a transaction at which protected resources are consistent.
sync point manager
A function that coordinates the two-phase commit process for protected resources, so that all changes to data are either committed or backed out.
syntax
The rules for the construction of a command or statement.
syntax highlighting
In source editors, the ability to differentiate text and structural elements, such as tags, attributes, and attribute values, using text highlighting differences, such as font face, emphasis, and color.
syntax object
One or more characters used as separators between portions of data. A syntax object can be a number separator, a delimiter, a terminator, an initiator, or a release character.
synthesized event
See synthetic event.
synthetic event
An event that is triggered in response to a condition that was detected while processing the current event. Unlike an action, which is also triggered in response to a condition that was detected during the processing of the current event, a synthetic event is not sent to an external system.
syslog
In a UNIX system, the subsystem that collects and manages logging data that is created by other subsystems.
sysplex
A set of z/OS systems that communicate with each other through certain multisystem hardware components and software services.
system
A collection of referenced executable maps that are organized into a unit.
System Authorization Facility (SAF)
A z/OS interface with which programs can communicate with an external security manager, such as RACF.
system configuration administration
The administration of configuration object types, organizational units, and roles. This is carried out after the product has been installed and is running.
system definition diagram
The graphical representation of a system viewed within a system window in the Integration Flow Designer. A user can interact with system definition diagrams to design systems.
system logger
An integrated logging facility that is provided by MVS and can be used by system and subsystem components. For example, it is used by the CICS log manager.
system menu
A drop-down menu that is activated by clicking the icon at the left of a window title bar and that allows users to restore, move, size, minimize, or maximize the window.
system task
See service task.
system window
A window in the Integration Flow Designer in which system definition diagrams are created, maintained, and displayed.

T

tag
An item that contains identifying information about a person or device. Tags enable tracking and monitoring of assets within locations, areas, and zones.
taglib directive
In a JSP page, a declaration stating that the page uses custom tags, defines the tag library, and specifies its tag prefixes. (Sun)
tag library
In JSP technology, a collection of tags identifying custom actions described using a taglib descriptor and Java classes. A JSP tag library can be imported into any JSP file and used with various scripting languages. (Sun)
TAI
See trust association interceptor.
target
  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.
target CDD
A customization definition document (CDD) to which placeholders have been added, and for which placeholder values have been specified. A target CDD describes a particular target customization definition.
target component
A component that is the final target of a client service request.
target customization definition
A customization definition that describes a changed version of a current customization definition. Each target customization definition has a target CDD that describes it.
target namespace
A unique logical location for information about the service that associates a namespace with a WSDL location.
target service
A service that exists outside of the gateway.
task
  1. An atomic activity that is included within a process. A task is used when the work in the process is not broken down to a finer level of process model detail. Generally, an end-user, an application, or both perform the task. A task object is the same shape as the subprocess, which is a rectangle that has rounded corners.
  2. A unit of work to be accomplished by a device or process.
  3. One or more actions associated with a case. A task has one or more steps that must be completed to finalize the task. For example, a task might be to review new hire applications. A case is not complete until all required tasks are completed or manually disabled. Each task has roles that are associated with it. See also activity, case.
  4. The basic unit of organization in a rule flow.
task-related user exit (TRUE)
A user exit program that is associated with specified events in a particular task, rather than with every occurrence of a particular event in CICS processing (as is the case with global user exits).
taxonomy
The hierarchical classification of information according to a known system that is used to easily discuss, analyze, or retrieve that information.
TC
See test case.
TCP
See Transmission Control Protocol.
TCP channel
A type of channel within a transport chain that provides client applications with persistent connections within a local area network (LAN).
TCP/IP
See Transmission Control Protocol/Internet Protocol.
TCP/IP monitoring server
A runtime environment that monitors all requests and responses between a web browser and an application server, as well as TCP/IP activity.
team development
The practice of several members of a team contributing to a single project, with the potential for multiple team members to work in parallel on the same files.
technical rule
A rule written in a technical rule language, such as ILOG Rule Language (IRL).
technology adapter
An adapter that is designed for interactions that conform to a specific technology. For example, the WebSphere Adapter for FTP, is an intermediary through which an integration broker sends data to a file system that resides on a local or remote FTP server.
technology connector
An API that passes data between the event processing server (runtime server) and external systems using a standard protocol such as SMTP, HTTP, FTP, or SOAP.
template
A group of elements that share common properties. These properties can be defined only once, at the template level, and are inherited by all elements that use the template.
template library
The database, known as the Portal Template Catalog, that stores place template specifications and portlets forms, subforms, and profiles.
temporary file system (TFS)
A temporary, in-memory physical file system that supports in-storage mountable file systems. Normally, a TFS runs in the kernel address space, but it can be run in a logical file system (LFS) colony address space.
terminal file
The resource in a 3270 service project that contains the information necessary for connecting to the host system during build time. Terminal files are automatically generated when the 3270 terminal service project is created. In the Navigator view, if a terminal file is selected, the 3270 terminal service recorder opens in the editor area.
terminate end event
An end event that will stop all parallel activities within its process level and all lower process levels. See also end event.
terminate node
A node that marks the end of a process. When a flow reaches a terminate node while the process is running, the process immediately terminates, even if there are other currently executing flows within the process.
terminator
A syntax object that signifies the end of a data object. For example, a carriage return/linefeed at the end of a record might be the record's terminator.
test case (TC)
A set of tasks, scripts, or routines that automate the task of testing software.
test configuration
A property of the integration test client that is used to specify modules for testing and to control the tests.
test harness
A series of script files used to enable a DB2 database for use by the DB2 XML Extender. A test harness is optionally created when a DAD file is generated from a relational database to XML mapping. Once enabled, it tests composing XML from data as well as decomposing XML files into relational data.
test pattern
A template used for the automatic generation of component tests. There are several test patterns available for testing both Java and EJB components. See also component test.
test suite
  1. A set of usage scenarios with which the user can verify that business rules are correctly designed and written. Running test suites produces a report comparing the expected results and the actual results obtained when applying rules to the scenarios.
  2. A collection of test cases that define test behavior and control test execution and deployment.
text annotation
An artifact that provides additional textual information about a BPMN diagram.
TFS
See temporary file system.
theme
The style element that gives a place a particular look. The portal provides several themes, similar to virtual wallpaper, which can be chosen when creating a place.
thin application client
A lightweight, downloadable Java application run time capable of interacting with enterprise beans.
thin client
A client that has little or no installed software but has access to software that is managed and delivered by network servers that are attached to it. A thin client is an alternative to a full-function client such as a workstation.
thread
A stream of computer instructions that is in control of a process. In some operating systems, a thread is the smallest unit of operation in a process. Several threads can run concurrently, performing different jobs.
thread contention
A condition in which a thread is waiting for a lock or object that another thread holds.
threshold
A setting that applies to an interrupt in a simulation that defines when a process simulation should be halted based on a condition existing for a specified proportion of occurrences of some event.
throughput
The measure of the amount of work performed by a device, such as a computer or printer, over a period of time, for example, number of jobs per day.
throwing message intermediate event
An intermediate event that sends a message. See also intermediate event.
thumbnail
An icon-sized rendering of a larger graphic image that permits a user to preview the image without opening a view or graphical editor.
TID
See transaction identifier.
time-delayed rule
The delay before an event rule or event rule group is evaluated.
timeout
A time interval that is allotted for an event to occur or complete before operation is interrupted.
timer
An event that is triggered by an occurrence at a specific time.
timer event
An event that is triggered when a time condition is satisfied. See also intermediate event.
timer intermediate event
An intermediate event that is triggered when a time condition is satisfied. A timer intermediate event can delay the flow of the process or can generate a timeout for activities that exceed the time condition.
timer start event
A start event that is triggered when a time condition is satisfied. A timer start event is used only for event subprocesses. See also start event.
Time Sharing Option (TSO)
A base element of the z/OS operating system with which users can interactively work with the system. See also Interactive System Productivity Facility.
timetable
A schedule of times. In business process modeling, timetables are typically associated with resources or costs. For resources, timetables indicate availability (such as Monday to Friday). For costs, timetables are useful if the cost varies with time of day (such as electricity) or time of year (such as seasonal foods).
time to live (TTL)
The time interval in seconds that an entry can exist in the cache before that entry is discarded.
timing constraint
A specialized validation action used to measure the duration of a method call or a sequence of method calls. See also validation action.
tip
The current working version of a process application or toolkit.
Tivoli Performance Viewer
A Java client that retrieves the Performance Monitoring Infrastructure (PMI) data from an application server and displays it in various formats.
TLS
See Transport Layer Security.
token
  1. A particular message or bit pattern that signifies permission or temporary control to transmit over a network.
  2. A marker that progresses through a process instance and indicates which element is currently running. A process instance can generate several tokens. A token can take only one path.
token-bucket
A mechanism that controls data flow. As an application requests permission into a network, the token bucket adds characters (or tokens) into a buffer (or bucket). If enough room is available for all the tokens in the bucket, the application is allowed to enter the network.
toolkit
A container where artifacts can be stored for reuse by process applications or other toolkits.
top-down development
In web services, the process of developing a service from a Web Services Description Language (WSDL) file. See also bottom-up development.
top-down mapping
An approach for mapping enterprise beans to database tables, in which existing enterprise beans and their design determines the database design.
topology
The physical or logical mapping of the location of networking components or nodes within a network. Common network topologies include bus, ring, star, and tree.
touchpoint system
An external business system that generates events or receives actions.
track
An optional subdivision in a process application that is based on team tasks, process application versions, or both. When enabled, tracks allow parallel development to occur with isolation from changes in other tracks. For example, using tracks one team can fix the current version of a process, while another team builds a completely new version based on new external systems and a new corporate identity.
track event
An event that tracks certain data as it passes through the event run time.
tracking group
A group of tracked process variables and data, such as KPIs, from one or more BPDs or process applications. Tracking groups are used to monitor performance and report analyses of information.
tracking intermediate event
An intermediate event that indicates a point in a process when runtime data is captured for reporting. See also intermediate event.
transaction
  1. A subprocess that represents a set of coordinated activities that are carried out by independent, loosely coupled systems in accordance with a contractually defined business relationship. This coordination leads to an agreed, consistent, and verifiable outcome across all participants.
  2. 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.
transaction class
A subcontainer of a service policy that is used for finer-grained monitoring.
transaction ID
See transaction identifier.
transaction identifier (TID, transaction ID, XID)
A unique name that is assigned to a transaction and is used to identify the actions associated with that transaction.
transaction manager
A software unit that coordinates the activities of resource managers by managing global transactions and coordinating the decision to commit them or roll them back.
transaction set
The basic business document in EDI data. Transaction sets are enclosed in an envelope that separates one transaction set from another. Groups of transaction sets that are functionally related are enclosed in a functional group envelope.
transcoding technology
Content adaptation to meet the specific capabilities of a client device.
transform
  1. To convert a document from one form to another, such as using a purchase order formatted as an XML document to create the same purchase order formatted as an EDI document.
  2. Programming logic that converts data from one format into another format.
transform algorithm
A procedure that is used to transform the message for web services security message processing, such as the C14N (canonicalization) transform that is used for XML digital signatures.
Transformation API for XML (TrAX)
A programming interface that can transform XML and related tree-shaped data structures.
transformer
A kernel services that converts the application model from a logical description into a topology document that is used to deploy the virtual application.
transition
A connection between two tasks in a rule flow. Transitions are unidirectional, and they can have conditions attached to them.
transition condition
  1. A Boolean expression that determines when processing control should be passed to the targeted node.
  2. In a rule flow, a specification of a transition that dictates when the target task can be executed.
translation object
A source map that has been compiled to provide instructions for translating from one format to another in a way that can be interpreted by the translator.
Transmission Control Protocol (TCP)
A communication protocol used in the Internet and in any network that follows the Internet Engineering Task Force (IETF) standards for internetwork protocol. TCP provides a reliable host-to-host protocol in packet-switched communication networks and in interconnected systems of such networks. See also Internet Protocol.
Transmission Control Protocol/Internet Protocol (TCP/IP)
An industry-standard, nonproprietary set of communication protocols that provides reliable end-to-end connections between applications over interconnected networks of different types.
transmission type
The largest object in an EDI type tree. A transmission might include many interchanges from or to many trading partners.
transparent decision service
A reusable decision service that is easily accessible to all participants of its lifecycle: developers, business analysts, and policy managers. It is easy to adapt and contributes to an enterprise compliance strategy.
transport
The request queue between a web servers plug-in and a web container in which the web modules of an application reside. When a user requests an application from a web browser, the request is passed to the web server, then along the transport to the web container.
transport adapter
An adapter (such as an HTTP Adapter) that is used with an encoding/decoding adapter to support various protocols (for example, SOAP) in a transport-independent way. The transport adapter is used to transport the data either from the source or to the destination.
transport chain
A representation of a network protocol stack that is operating within an application server.
transport channel chain
A specification of the transport channels that are used by a server for receiving information. Transport channel chains contain end points
transporting
A method of conveying data using a specified adapter following either an encode or decode command.
Transport Layer Security (TLS)
An Internet Engineering Task Force (IETF)-defined security protocol that is based on Secure Sockets Layer (SSL) and is specified in RFC 2246.
TrAX
See Transformation API for XML.
tree
A data structure whose elements are linked in a hierarchical fashion.
trend analysis
A type of analysis that displays the analysis of the changes in a given item of information over a period of time.
trigger
  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.
triple Data Encryption Standard (triple DES)
A block cipher algorithm that can be used to encrypt data transmitted between managed systems and the management server. Triple DES is a security enhancement of DES that employs three successive DES block operations.
triple DES
See triple Data Encryption Standard.
TRUE
See task-related user exit.
trunk
In the CVS team development environment, the main stream of development, also referred to as the HEAD stream.
trust anchor
A trusted keystore file that contains a trusted certificate or a trusted root certificate that is used to assert the trust of a certificate.
trust association
An integrated configuration between the security server of the product and third-party security servers. A reverse proxy server acts as a front-end authentication server, while the product applies its own authorization policy onto the resulting credentials passed by the proxy server.
trust association interceptor (TAI)
The mechanism by which trust is validated in the product environment for every request received by the proxy server. The method of validation is agreed upon by the proxy server and the interceptor.
trusted identity evaluator
A mechanism that is used by a server to determine whether to trust a user identity during identity assertion.
trusted root
A certificate signed by a trusted certificate authority (CA).
trust file
A file that contains signer certificates.
trust policy
A trusted list of certificates that are used to control the trust and validity period of certificates. It enables the trust of certificates issued by a certificate authority to be limited.
trust relationship
An established and trusted communication path through which a computer in one domain can communicate with a computer in the other domain. Users in a trusted domain can access resources in the trusting domain.
truststore
In security, a storage object, either a file or a hardware cryptographic card, where public keys are stored in the form of trusted certificates, for authentication purposes in web transactions. In some applications, these trusted certificates are moved into the application keystore to be stored with the private keys. See also keystore.
truststore file
A key database file that contains the public keys for a trusted entity.
TSO
See Time Sharing Option.
TTL
See time to live.
tuple
See row.
type
  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).
  3. The definition of a data object or set of data objects that is graphically represented in a type tree in the Type Designer.
type hierarchy
The complete context for a Java class or interface including its superclasses and subclasses.
type tree
In the Type Designer, the graphical representation of the definition and organization of data objects.

U

UCA
See undercover agent.
UCS
See universal character set.
UDDI
See Universal Description, Discovery, and Integration.
UDDI Business Registry
A collection of peer directories that contain information about businesses and services.
UDDI node
A set of web services that supports at least one of the Universal Description, Discovery, and Integration (UDDI) APIs. A UDDI node consists of one or more instances of a UDDI application running in an application server or a cluster of application servers with an instance of the UDDI database.
UDDI node initialization
The process by which values are set in the Universal Description, Discovery, and Integration (UDDI) database and the behavior of the UDDI node is established.
UDDI node state
A description of the current status of the Universal Description, Discovery, and Integration (UDDI) node.
UDDI policy
A statement of the required and expected behavior of a Universal Description, Discovery, and Integration (UDDI) registry that is specified through policy values that are defined in the UDDI specification.
UDDI property
A characteristic or attribute that controls the behavior of a Universal Description, Discovery, and Integration (UDDI) node.
UDDI registry
A distributed registry of businesses and their service descriptions that adheres to the Universal Description, Discovery, and Integration (UDDI) standard for managing the discovery of web services. UDDI registries come in two forms, public and private, both of which are implemented in a common XML format.
UDF
See user-defined function.
UML
See Unified Modeling Language.
unaugment
To remove the last template that was augmented to a profile. A profile must be unaugmented before it is deleted. See also augment.
unbound set
The set of all possible types of data that might be listed last in a group.
uncontrolled flow
A flow that proceeds without dependencies or conditional expressions. Typically, an uncontrolled flow is a sequence flow between two activities that do not have a conditional indicator (mini-diamond) or an intervening gateway.
undelivered message queue
See dead-letter queue.
undercover agent (UCA)
An agent that is attached to a message event in a business process definition (BPD) and that calls a service to handle the event. For example, when a message event is received from an external system, a UCA is needed to invoke the appropriate service in response to the message.
Unicode
A character encoding standard that supports the interchange, processing, and display of text that is written in the common languages around the world, plus many classical and historical texts.
Unified Modeling Language (UML)
A standard notation for the modeling of real-world objects as a first step in developing an object-oriented design methodology.
Uniform Resource Identifier (URI)
  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.
Uniform Resource Indicator (URI)
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.
Uniform Resource Locator (URL)
The unique address of an information resource that is accessible in a network such as the Internet. The URL includes the abbreviated name of the protocol used to access the information resource and the information used by the protocol to locate the information resource.
Uniform Resource Name (URN)
A name that uniquely identifies a web service to a client. See also Uniform Resource Identifier.
United Nations Standard Products and Services Classification (UNSPSC)
An open global standard for classifying products and services based on common function, purpose, and task.
universal character set (UCS)
The ISO standard that allows all data to be represented as 2 bytes (UCS-2) or 4 bytes (UCS-4). Encoding in the UCS-2 form can accommodate the necessary characters for most of the written languages in the world.
Universal Description, Discovery, and Integration (UDDI)
A set of standards-based specifications that enables companies and applications to quickly and easily find and use web services over the Internet. See also web service.
universal integration hub
A unified page presentation architecture that enables site designers to create web portal pages by using various components, including HTML and web content, feeds, portlets, iWidgets, and elements that are derived from frameworks such as Adobe Flex.
Universally Unique Identifier (UUID)
The 128-bit numeric identifier that is used to ensure that two components do not have the same identifier.
UNIX System Services
An element of z/OS that creates a UNIX environment that conforms to XPG4 UNIX 1995 specifications and that provides two open-system interfaces on the z/OS operating system: an application programming interface (API) and an interactive shell interface.
unmanaged node
A node that is defined in the cell topology that does not have a node agent that manages the process. An unmanaged node is typically used to manage web servers.
unmanaged web application
A web application with a life cycle that is managed outside of the administrative domain. By creating a representation of these applications that are deployed through external tools, the on demand router can prioritize and route HTTP requests to the application.
unmodeled fault
A fault message that is returned from a service that has not been modeled on the Web Services Description Language (WSDL) port type.
unrealized
Pertains to a web diagram node that is not yet associated with an actual resource. See also realize.
unrecognized screen
In the 3270 terminal service development tools, a screen that cannot be identified by any of the recognition profiles currently defined.
UNSPSC
See United Nations Standard Products and Services Classification.
upgradeable lock
A lock that identifies the intent to update a cache entry when using a pessimistic lock.
upstream
Pertaining to the direction of the flow, which is from the start of the process (upstream) toward the end of the process (downstream).
URI
  1. See Uniform Resource Identifier.
  2. See Uniform Resource Indicator.
URL
See Uniform Resource Locator.
URL scheme
A format that contains another object reference.
URN
See Uniform Resource Name.
use case
The specification of a sequence of actions that a system can perform, interacting with users of the system. Use cases are used in system analysis to identify system requirements. See also scenario.
user account
The login directory and other information that gives a user access to the system.
user-defined function (UDF)
A function that is defined to the DB2 database system by using the CREATE FUNCTION statement and that can be referenced thereafter in SQL statements. See also function.
user group
A group consisting of one or more defined individual users, identified by a single group name.
user name token
A type of token that is represented by a user name and optionally, by a password.
user registry
A database of known users and user-provided information that is used for authentication purposes.
UTC
See Coordinated Universal Time.
UTF-8
Unicode Transformation Format, 8-bit encoding form, which is designed for ease of use with existing ASCII-based systems. The CCSID value for data in UTF-8 format is 1208.
UUID
See Universally Unique Identifier.

V

validation
The checking of data or code for correctness or for compliance with applicable standards, rules, and conventions.
validation action
A mechanism for verifying whether the actual value of a variable at run time corresponds to the expected value of that variable. See also timing constraint.
validator
A program that checks data or code for correctness or for compliance with applicable standards, rules, and conventions.
variable
  1. Data that passes from one step to another in a process. For example, a process that automates escalation of customer issues needs variables to hold information, such as the customer's name and the issue ID.
  2. A representation of a changeable value. See also global variable.
variable component name
A component of a group type that includes the literal at the end of the name because it represents more than one type. The literal ANY acts like a wild card, which represents any type whose name could appear in that place.
variant action
An action that is derived from another action so that the content of the action can vary. A field in the variant action object can derive its value in a different way from the way that the same field derives its value in the base action object.
verb
See people assignment criterion.
verbalization
The process of associating terms and phrases to elements of the business object model (BOM). See also constant.
version
A separately licensed program that typically has significant new code or new function.
version control
The coordination and integration of the history of work submitted by a team.
vertical scaling
Setting up multiple application servers on one machine, typically by creating cluster members.
vertical stacking
The process of starting more than one instance of the dynamic cluster on a node to manage bottlenecks.
view
  1. In Eclipse-based user interfaces, a pane that is outside the editor area, which can be used to look at or work with the resources in the workbench.
  2. A logical table that is based on data stored in an underlying set of tables. The data returned by a view is determined by a SELECT statement that is run on the underlying tables.
  3. A reusable user interface that is used for a business object or human service. A view consists of one or more other views, data bindings, layout instructions, and behavior.
view synchronous high-availability manager group
A special class of high availability (HA) group that can be created and used by components that require a certain virtual synchrony (VS) quality of service (QoS) for group communication.
VIPA
See virtual IP address.
virtual application layer
A group of components in a virtual application pattern that facilitate complex virtual application design. A virtual application layer enables virtual application patterns to be reused in different contexts; one virtual application pattern is used as a reference layer in another virtual application pattern.
virtual application pattern plug-in
The resources and automation that provide the specific capabilities for a virtual application component. See also virtual application pattern type.
virtual application pattern type
A set of virtual application pattern plug-ins for a specific type of application or application capability. For example, the IBM Web Application Pattern pattern type provides the components, links, policies, and automation that are required to deploy web applications. See also virtual application pattern plug-in.
virtual host
A configuration that enables one host to resemble multiple logical hosts. Each virtual host has a logical name and a list of one or more DNS aliases by which it is known.
virtual image
The operating system and product binary files that are required to create a virtual system pattern.
virtual IP address (VIPA)
An IP address that is shared among multiple domain names or multiple servers. Virtual IP addressing enables one IP address to be used either when insufficient IP addresses are available or as a means to balance traffic to multiple servers.
virtualization
A technique that encapsulates the characteristics of resources from the way in which other systems interact with those resources.
virtual local area network (VLAN)
A logical association of switch ports based upon a set of rules or criteria, such as Medium Access Control (MAC) addresses, protocols, network address, or multicast address. This concept permits the LAN to be segmented again without requiring physical rearrangement.
virtual machine
An abstract specification for a computing device that can be implemented in different ways in software and hardware.
virtual private network (VPN)
An extension of a company intranet over the existing framework of either a public or private network. A VPN ensures that the data that is sent between the two endpoints of its connection remains secure.
virtual synchrony (VS)
A property of group communication that guarantees how messages are delivered when the view changes, for example, when existing members fail or new members join.
virtual system instance
The virtual environment that runs on a hypervisor in the cloud.
virtual system pattern
One or more virtual images, which can include script packages, that implement a deployment topology. A virtual system pattern is a shared topology definition used for repeatable deployment.
visibility
In a user interface, the property of a control that declares whether the control is to be displayed or not displayed during run time.
visualization
An association between a Scalable Vector Graphics (SVG) diagram and the set of actions that describe how the diagram should be updated based on the values of metrics or key performance indicators (KPIs).
visual snippet
A diagrammatic representation of a fragment of Java programming language that can be manipulated with the visual snippet editor.
VLAN
See virtual local area network.
vocabulary
  1. A repository for storing reusable business elements, such as terms, business item definitions, roles, messages, and errors, that are used in a business process.
  2. The set of terms and phrases that are used for rule editing.
VPN
See virtual private network.
VS
See virtual synchrony.

W

W3C
See World Wide Web Consortium.
waiter
A thread waiting for a connection.
WAP
See Wireless Application Protocol.
WAR
See web archive.
WAR file
See web archive.
watch
A map, including the set of events that initiate it, as defined from the Integration Flow Designer.
watchdog
A process that monitors a server. If the server appears to be locked, the watchdog forces it to restart.
watchpoint
A breakpoint that suspends execution when a specified field or expression is modified.
WBMP
See wireless bitmap.
WCCM
See WebSphere Common Configuration Model.
web analytics page overlay
Web page and channel delivery analysis that is rendered in place on the website.
web application
An application that is accessible by a web browser and that provides some function beyond static display of information, for instance by allowing the user to query a database. Common components of a web application include HTML pages, JSP pages, and servlets.
web application bridge
A virtual web application that passes request data, including selected HTTP headers, cookies, and POST data, to the content provider. The web application bridge sends the response data back to the requester, including selected HTTP headers, cookies, and POST data. See also bridge.
web archive (WAR)
A compressed file format, defined by the Java EE standard, for storing all the resources required to install and run a web application in a single file. See also enterprise archive, Java archive.
web component
A servlet, JavaServer Pages (JSP) file, or a HyperText Markup Language (HTML) file. One or more web components make up a web module.
web container
A container that implements the web component contract of the Java EE architecture. (Sun)
web container channel
A type of channel within a transport chain that creates a bridge in the transport chain between an HTTP inbound channel and a servlet or JavaServer Pages (JSP) engine.
web crawler
A crawler that explores the web by retrieving a web document and following the links within that document.
web diagram
A Struts file that uses icons and other images on a free-form surface to help application developers visualize the flow structure of a Struts-based web application.
web module
A unit that consists of one or more web components and a web deployment descriptor. (Sun)
Web Ontology Language (OWL)
A language that is used to explicitly represent the meaning of terms in vocabularies and the relationships between those terms. OWL is intended to be used when the information contained in documents needs to be processed by applications, as opposed to situations where the content only needs to be presented to humans. See also ontology.
web project
A container for other resources such as source files and metadata that corresponds to the Java EE-defined container structure and hierarchy of files necessary for web applications to be deployed.
web property extension (WPX)
IBM extension to the standard deployment descriptors for web applications. These extensions include Multipurpose Internet Mail Extensions (MIME) filtering and servlet caching.
web resource
Any one of the resources that are created during the development of a web application for example web projects, HTML pages, JavaServer Pages (JSP) files, servlets, custom tag libraries, and archive files.
web resource collection
A list of URL patterns and HTTP methods that describe a set of resources to be protected. (Sun)
web server
A software program that is capable of servicing Hypertext Transfer Protocol (HTTP) requests.
web server plug-in
A software module that supports the web server in communicating requests for dynamic content, such as servlets, to the application server.
web server separation
A topology where the web server is physically separated from the application server.
web service
  1. An application that performs specific tasks and is accessible through open protocols such as HTTP and SOAP.
  2. 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.
web service endpoint
An entity that is the destination for web service messages. A web service endpoint has a Uniform Resource Identifier (URI) address and is described by a Web Service Definition Language (WSDL) port element.
web service interface
A group of operations described by the content of a Web Service Definition Language (WSDL) 1.1 port element. These operations can provide access to resource properties and metadata. (OASIS)
Web Services Business Process Execution Language (WS-BPEL)
See Business Process Execution Language.
Web Services Description Language (WSDL)
An XML-based specification for describing networked services as a set of endpoints operating on messages containing either document-oriented or procedure-oriented information. See also web service.
Web Services Interoperability (WS-I)
An open industry organization that is chartered to promote web services interoperability across platforms, operating systems, and programming languages.
Web Services Interoperability Organization (WSI)
An open industry organization that promotes web services interoperability across platforms, operating systems, and programming languages.
Web Services Invocation Framework (WSIF)
A Java API that supports dynamic invoking of web services, regardless of the format in which the service is implemented or the access mechanism.
Web Services Invocation Language (WSIL)
An XML document format that facilitates the discovery of existing web services and provides a set of rules for how inspection-related information should be made available for consumption.
Web Services Policy Framework (WS-Policy)
A model and framework for describing the capabilities, requirements, and general characteristics of a web service as a policy assertion or a collection of policy assertions.
Web Services Security (WS-Security)
A flexible standard that is used to secure web services at the message level within multiple security models. SOAP messages can be secured through XML digital signature, confidentiality can be secured through XML encryption, and credential propagation can be secured through security tokens.
website
A related collection of files available on the web that is managed by a single entity (an organization or an individual) and contains information in hypertext for its users. A website often includes hypertext links to other websites.
WebSphere BI for FN message
A WebSphere MQ message that has a folder labeled ComIbmDni in the MQRFH2 header. This folder provides the data that is required by WebSphere BI for FN to process the message.
WebSphere Common Configuration Model (WCCM)
A model that provides for programmatic access to configuration data.
weight
See point.
weighted sum
The result of multiplying the weight by the score assigned to an attribute. The weight is a percentage. An attribute with a higher weight is more significant than other attributes as it contributes a bigger share to the final score.
what you see is what you get (WYSIWYG)
A capability of an editor to continually display pages exactly as they will be printed or otherwise rendered.
while loop
A loop that repeats the same sequence of activities as long as some condition is satisfied. The while loop tests its condition at the beginning of every loop. If the condition is false from the start, the sequence of activities contained in the loop never runs.
widget
A portable, reusable application or piece of dynamic content that can be placed into a web page, receive input, and communicate with an application or with another widget.
wire
A connector used to pass control and data from a component or an export to a target.
Wireless Application Protocol (WAP)
An open industry standard for mobile Internet access that allows mobile users with wireless devices to easily and instantly access and interact with information and services.
wireless bitmap (WBMP)
A graphic format that is optimized for mobile computing devices. WBMP is part of the Wireless Application Protocol, Wireless Application Environment Specification.
Wireless Markup Language (WML)
A markup language based on XML that is used to present content and user interfaces for wireless devices such as cellular phones, pagers, and personal digital assistants.
wizard
An active form of help that guides users through each step of a particular task.
WML
See Wireless Markup Language.
workbench
The user interface and integrated development environment (IDE) in Eclipse and Eclipse-based tools such as IBM Rational Application Developer.
work class
A mechanism for grouping specific work together that must be associated with a common service policy or routing policy. Work classes group Uniform Resource Identifiers (URIs) or web services from an application.
workflow
The sequence of activities performed in accordance with the business processes of an enterprise.
working data set
A data set containing customized JCL that is used to configure and run an execution environment in Decision Server for z/OS.
working directory
The active directory. When a file name is specified without a directory, the current directory is searched.
working memory
A part of the rule engine that contains the current state of objects. It is this current state that determines which rules are added to the agenda, and in which order these rules are executed.
work item
  1. See also inline task, stand-alone task.
  2. In the human task editor, the representation of a task. Staff members can browse all work items that they have the authority to claim.
workload management
The optimization of the distribution of incoming work requests to the application servers, enterprise beans, servlets and other objects that can effectively process the request.
work manager
A thread pool for Java Platform, Enterprise Edition (Java EE) applications.
work object
A type of asynchronous bean that applications implement to run code blocks asynchronously.
workspace
  1. 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.
  2. A directory on disk that contains all project files, as well as information such as preferences.
  3. A temporary repository of configuration information that administrative clients use.
World Wide Web Consortium (W3C)
An international industry consortium set up to develop common protocols to promote evolution and interoperability of the World Wide Web.
WPX
See web property extension.
wrapper
  1. An object that encapsulates and delegates to another object to alter its interface or behavior in some way. (Sun)
  2. An alternate and supported interface that hides unsupported data types required by a server object behind a thin intermediate server object.
wrapper business object
A top-level business object that groups child business objects for a component to use in a single operation or contains processing information about its child business object.
write-behind cache
A cache that asynchronously writes each write operation to the database using a loader.
write-through cache
A cache that synchronously writes each write operation to the database using a loader.
WS-BPEL
See Web Services Business Process Execution Language.
WSDL
See Web Services Description Language.
WSDL document
A file that provides a set of definitions that describe a web service in Web Services Description Language (WSDL) format.
WSDL file
See WSDL document.
WS-I
See Web Services Interoperability.
WSI
See Web Services Interoperability Organization.
WSIF
See Web Services Invocation Framework.
WSIL
See Web Services Invocation Language.
WS-Policy
See Web Services Policy Framework.
WS-Security
See Web Services Security.
WYSIWYG
See what you see is what you get.

X

X.25
A CCITT standard that defines an interface to packet-switched communication services.
X.500
The directory services standard of ITU, ISO, and IEC.
X.509 certificate
A certificate that contains information that is defined by the X.509 standard.
XA
A bidirectional interface between one or more resource managers that provide access to shared resources and a transaction manager that monitors and resolves transactions.
XACML
See Extensible Access Control Markup Language.
Xalan processor
An XSLT processor that is part of the Apache project. See also XSL Transformation.
XDoclet
An open, source code generation engine that uses special JavaDoc tags to parse Java source files and generate output such as XML descriptors or source code, based on templates.
XHTML
See Extensible Hypertext Markup Language.
XID
See transaction identifier.
xJCL
An XML-based job control language that is used to define a batch job. See also job control language.
XML
See Extensible Markup Language.
XML catalog
A catalog that contains rules specifying how an XML processor should resolve references to entities. Use of a catalog eliminates the need to change URIs within XML documents as resources are moved during development.
XML digital signature
A specification that defines the XML syntax and the processing rules to sign and verify the digital signatures for the digital content.
XML document definition
A reference to either an XML DTD document definition or an XML schema document definition.
XML encryption
A specification that defines how to encrypt the content of an XML element.
XML parser
A program that reads XML documents and provides an application with access to their content and structure.
XML Path Language (XPath)
A language that is designed to uniquely identify or address parts of source XML data, for use with XML-related technologies, such as XSLT, XQuery, and XML parsers. XPath is a World Wide Web Consortium standard.
XML schema
A mechanism for describing and constraining the content of XML files by indicating which elements are allowed and in which combinations. XML schemas are an alternative to document type definitions (DTDs) and can be used to extend functionality in the areas of data typing, inheritance, and presentation.
XML Schema Definition Language (XSD, XSDL)
A language for describing XML files that contain XML schema.
XML Schema Infoset Model (XSD)
A library that provides an API for manipulating the components of an XML Schema, as described by the W3C XML Schema specifications.
XML token
A security token that is in an XML format, such as a Security Assertion Markup Language (SAML) token.
XOM
See execution object model.
X/Open XA
The X/Open Distributed Transaction Processing XA interface. A proposed standard for distributed transaction communication. The standard specifies a bidirectional interface between resource managers that provide access to shared resources within transactions, and between a transaction service that monitors and resolves transactions.
XPath
See XML Path Language.
XPath expression
An expression that searches through an XML document and extracts information from the nodes (any part of the document, such as an element or attribute) in that document.
XSD
  1. See XML Schema Definition Language.
  2. See XML Schema Infoset Model.
XSDL
See XML Schema Definition Language.
XSL
See Extensible Stylesheet Language.
XSL style sheet
Code that describes how an XML document should be rendered (displayed or printed).
XSLT
  1. See Extensible Stylesheet Language Transformation.
  2. See XSL Transformation.
XSLT function
Function that is defined by the XSL Transform (XSLT) specification for the manipulation of numbers, strings, Boolean values, and node-sets.
XSL Transformation (XSLT)
A standard that uses XSL style sheets to transform XML documents into other XML documents, fragments, or HTML documents. See also Xalan processor.
XU
See execution unit.

Z

zone
  1. A function that enables rules-based shard placement to improve grid availability by placing shards across different data centers, whether on different floors or even in different buildings or geographies.
  2. A logical section within an area. A zone can overlap areas but belongs only to the area where it was created. Zones are the units on which rules can be defined and run.