Glossary
Draft comment:
This topic was viewed 178 times since its publication
Understand the terms that are used in process and case management.
This topic was viewed 178 times since its publication
The following cross-references are used in this glossary:
- See refers you from a nonpreferred term to the preferred term or from an abbreviation to the spelled-out form.
- See also refers you to a related or contrasting term.
A
- abstract class
- In object-oriented programming, a class that represents a concept; classes derived from it represent implementations of the concept. An object cannot be constructed from an abstract class; that is, it cannot be instantiated. See also base class.
- 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 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.
- 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 right
- A designation of the rights that users have, such as read, modify, create, delete, and admin (RMCDA).
- 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
-
- A business process that is generated in response to the processing of an event or a rule.
- An activity that is run on a transition or a transaction.
- A series of processing steps, such as document validation and transformation.
- Action class
- In Struts, the superclass of all action classes.
- action column
- The action part of a decision table.
- action definition file
- A JSON file that provides detailed information about a custom action that is used for page widgets. A definition file must be provided for each custom action in a custom widget package.
- 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
-
- A rule in which the action is always performed. See also if-then rule, rule set.
- 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 set
-
- In Eclipse, a group of commands that a perspective contributes to the main toolbar and menu bar.
- 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.
- 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.
- activity
-
- 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.
- Work performed by a user or system, such as within a BPMN process, BPEL process, or case. An activity can be atomic or non-atomic (compound).
- 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.
- add-on
- See service.
- add-on extension
- A set of modules that contain custom metadata and data that is stored in object stores. The custom metadata includes classes that are derived from base Content Engine classes. These add-on extensions provide the core object model, history, and analytics support for IBM® Case Manager.
- 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 search
- A search that runs but is not saved.
- 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.
- ad hoc task
- A task that is performed as a result of external conditions that are not part of the regular task sequence.
- administration client
- A web-based application that is used to administer a case management system. The administration client stores settings for the case deployment profile in a profile.
- administrative agent
- A program that provides administrative support without requiring a direct connection to a database.
- administrative group
- A group of related computers. An administrator can create administrative groups to organize target systems into meaningful categories, and to facilitate deployment of software to multiple computers.
- 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 Rule Language (ARL)
- An executable rule language that is used by the decision engine. Rules that are compiled into Advanced Rule Language (ARL) can reference any execution object and can invoke methods on these objects.
- advanced search
- A search function to search for a case within a specific case type or by using more complex criteria. Case workers can use the advanced search to find cases in a specific case type or to narrow the search based on various properties.
- 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 component that contains the business logic that is applied to incoming events, and that is usually bound to an entity. See also Java agent, rule 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.
- agent descriptor
- An agent.adsc file in which an intuitive and natural syntax is used to write the business logic for an agent.
- 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.
- 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.
- analytics
- The science of studying data in order to find meaningful patterns in the data and draw conclusions based on those patterns.
- annotation
- An added descriptive comment, note, line, or shape.
- anonymous user
- A user who does not use a valid user ID and password to log in to a site. See also registered user.
- APAR
- See authorized program analysis report.
- API
- See application programming interface.
- 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.
- 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 hardware device with integrated software that is dedicated to a specific task or set of business requirements.
- 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 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 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 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 space
- An area that is used to organize the resources for a custom application that uses a workflow.
- 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 virtualization
- The separation of an application from the underlying operating environment, which improves portability, compatibility, and manageability of the application.
- archive
-
- Persistent storage used for long-term information retention, typically very inexpensive for each stored unit and slow to access, and often in a different geographic location to protect against equipment failures and natural disasters.
- To copy programs, data, or files to another storage media, usually for long-term storage or security.
- ARFM
- See autonomic request flow manager.
- ARL
- See Advanced Rule Language.
- ARM
- ARM agent
- See Application Response Measurement agent.
- array
- A structure that contains an ordered collection of elements of the same data type in which each element can be referenced by its index value or ordinal position in the collection.
- artifact
-
- An entity that is used or produced by a software or systems development process. Examples of artifacts include designs, requirements, source files, plans, scripts, simulations, models, test plans, and binary executable files. In an HTTP context, artifacts have a URI and are called resources.
- A graphical object that provides supporting information about the process or elements within the process without directly affecting the semantics of the process.
- 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.
- assisted lifecycle server
- A representation of a server that is created outside of the administrative domain but can be managed in the administrative console.
- association
-
- 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.
- 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.
- 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.
- 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. See also asynchronous send.
- asynchronous send
- In JMS, the action of sending of a message by an application to a server without waiting for a reply from the server so that the application can engage in other events, such as sending further messages or performing other processing. See also asynchronous messaging.
- ATAssertion
- See Atomic Transaction Assertion.
- 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.
- Atomic Transaction Assertion (ATAssertion)
- The policy that a web service provides to qualify the transactional processing of messages associated with the particular operation to which the assertion is scoped.
- attribute
-
- 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.
- 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 element.
- audit configuration package
- A file that is imported from one environment to another by using the importSolutionAuditManifest command.
- audit definition
- The results that are imported into production from the completed audit configuration.
- audit manifest
- See audit configuration package.
- 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.
- 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. See also authorization.
- 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.
- authorization
- The process of granting a user, system, or process either complete or restricted access to an object, resource, or function. See also authentication.
- 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.
- automated business process
- A set of business-related activities that are invoked to achieve a business goal.
- 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 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.
- autoscaling
- A capability of Liberty servers that dynamically adjusts the number of Java virtual machines (JVMs) used to service a workload.
- AWT
- See Abstract Window Toolkit.
- Axis
- An implementation of SOAP on which Java web services can be implemented.
B
- B2B
- See business-to-business.
- BA
- See basic authentication.
- BAL
- See Business Action Language.
- BAM
- See business activity monitoring.
- base
- The core product, for which features can be separately ordered and installed.
- base class
- A class from which other classes or beans are derived. A base class may itself be derived from another base class. See also abstract class.
- base classes
- See adapter foundation classes.
- baseline
- See snapshot.
- 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 container
- An entity that, after receiving work, provides lifecycle management, security, deployment, and runtime services to batch applications.
- batch data stream (BDS)
- A Java object that provides an abstraction for the data that is processed by a step in a batch application.
- 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.
- batchlet step
- A step that is started, runs to completion, and returns an exit status. A batchlet step performs task-oriented processing such as running a command or transferring a file.
- BDS
- See batch data stream.
- 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.
- 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.
- 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.
- black box
- A pool in which no content can be seen.
- 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.
- BMN
- See Decision Model and Notation.
- 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.
- boot BOM
- A set of files that define the system types, such as string or number, for the Business Action Language (BAL).
- 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.
- 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.
- BPD
- See business process definition.
- BPEL
- See Business Process Execution Language.
- BPM
- See business process management.
- BPMN
- See Business Process Modeling Notation.
- branch
-
- 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.
- An optional subdivision in a process application that is based on team tasks, process application versions, or both. When enabled, branches allow parallel development to occur with isolation from changes in other branches. For example, using branches 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.
- 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.
- 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 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.
- browser-based client
- A browser-based software program or computer that requests services from a server.
- 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.
- 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).
- building block
- The model of an image that is created by combining models of a base operating system and software bundles. Each building block contains a semantic and functional model that describes the contents of the components, for example, the installed products, supported operating systems, prerequisites, and requirements.
- 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.
- 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.
- 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
-
- A decision management user role that is responsible for modeling rule application projects.
- 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.
- 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 context
- A collective reference graph of the process variables and managed object instances that are included in a process.
- 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 method
-
- A method added to a type in a business object model. Business methods extend the original type without altering its source.
- A method of an enterprise bean that implements the business logic or rules of an application. (Sun)
- business object
-
- An abstract representation of the fields that belong to the event and action definitions.
- 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 business graph, data object, private business object, Service Data Objects.
- 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 (BOM)
-
- 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.
- 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.
- business policy
- 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)
- See process.
- 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 Notation (BPMN)
- A standardized graphical notation for creating diagrams of business processes.
- business rule
-
- A representation of how business policies or practices apply to a business activity.
- An expression used to perform calculations or otherwise manipulate the value of attributes. For example, a business rule could be a formula that can check the quality of requirements, implement a complete workflow, or aggregate sales figures for a large corporation.
- 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.
- business rule application
- An application in which the decision-making process is automated and managed 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, rule agent.
- 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 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.
- 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.
- 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 function
- Executable code that allows a lower-level software layer to call a function defined in a higher-level layer.
- 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.
- caller
- A function that calls another function.
- 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.
- canvas
- An area within a dashboard or workspace that users interact with to create, view, and manipulate content and data.
- 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.
- cardinality
- The number of elements in a set.
- 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 group of data, documents, team members, and activities that address a specific business situation. A case can be as simple as a container that holds documents and records or can be as complex as a compilation of structured or unstructured activities and tasks that users or teams work on concurrently or consecutively.
- A group of related activities that address a specific business situation. The user or predefined conditions, instead of a defined flow, determines the sequence in which activities are performed. See also case type.
- case analytics tool
- A tool that can be used to monitor and manage daily business operations. The tools can also provide historical trend information that can be used to adjust future operations as needed.
- case document
- A document that is associated with a case and made available from the Documents tab.
- case folder
- A folder that holds information pertaining to a case. The case folder stores case related information obtained from search queries. A case folder contains the tasks, history, and comments that are associated with the case.
- case history
- The history of a case that shows information such as creation dates, comments, and so forth. Event log data is included in the case history, which uses the same security as is applied to case instances.
- case identifier
- A predefined property assigned to a case. The case identifier is displayed at the top of the Case Information widget with a link to open the case in the Case Details page. For example, a case type named Credit Application with a unique identifier of EXPL_CreditApplication might have a case identifier of EXPL_CreditApplication_00000010001.
- case management master group
- A group that controls access to a case management object store.
- case operation
- An operation that is used to perform a case-related action like creating a case by using a specified case type or adding a comment to a current case.
- case synchronizer utility
- A utility that can be run to update existing instances to match the changes that were made after modifying a solution after it is deployed.
- case title property
- The specific title property that can be controlled on an individual case type. By default, the case title property is Case Identifier.
- case type
- The definition of the activities that make up case to address a specific type of business situation. Case types make up a solution. See also case, process.
- catching message intermediate event
- An intermediate event that is triggered when a specific message is received. See also intermediate event.
- category
-
- A classification of elements for documentation or analyses.
- 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.
- 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.
- CCI
- See common client interface.
- CDI
- See Contexts and Dependency Injection.
- 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
- 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 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.
- chain
- The name of a channel framework connection that contains an endpoint definition.
- channel
-
- A communication path through a chain to an endpoint.
- An IBM 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 queue manager.
- 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.
- 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.
- checkpoint
- A place in a program at which a check is made, or at which a recording of data is made to allow the program to be restarted.
- 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.
- chunk step
- A step that follows a preconfigured checkpoint policy. A chunk step performs item-oriented processing by using a reader-processor-writer batch pattern.
- 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.
- class
- 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.
- classifier
- An XPath expression that determines the transformation to apply to an inbound event.
- 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.
- 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.
- client
- A software program or computer that requests services from a server. See also host, server.
- client authentication
- In CSIv2 security, a token-based client authentication mechanism for which Generic Security Services Username Password (GSSUP) is the minimum requirement, but additional requirements, such as Lightweight Third Party Authentication (LTPA), might exist.
- client context
- A mapping from keys to values. If a provider returns a client context for a particular object, that context is merged with the context specified through setClientContext(), if any. The client context can then be tailored for the specific objects being processed.
- client project for RuleApps
- A predefined project for Eclipse that contains a class to execute a ruleset 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, server.
- client-side human service
- A human service that runs in the web browser and can call the server to obtain data. A client-side human service can be used to implement an interactive task, a dashboard, or a user interface for a case or process instance that users can use to manage cases or processes in an application. See also heritage human service, human service.
- 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.
- 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 or application programming interface (API), or both, makes the infrastructure supporting such services transparent to users.
- cloud image
- An information technology (IT) resource that can be provisioned for use on a cloud.
- cluster
- A group of application servers that collaborate for the purposes of workload balancing and failover.
- cluster environment
- A topology in which an application server is defined over several machines or CPUs.
- CMIS
- See Content Management Interoperability Services.
- CMP
- See container-managed persistence.
- coach
- A user interface, such as screens or forms, that process authors create to collect input from users that is required for an underlying service.
- coach view
- A reusable unit used in coaches and other coach views to generally define the user interface for a particular type of data. Coach views are responsive and run on multiple device types, such as mobile and desktop devices.
- 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.
- coexistence
- The ability of two or more entities to function in the same system or network.
- cold start
- The process of starting an existing data replication configuration without regard for prior replication activity, causing reinitialization of all subscriptions.
- collaboration
-
- A diagram that shows the exchange of messages between two or more participants in a BPMN model.
- 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 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.
- 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 Liberty servers in one management domain that has at least one server with the collective-controller feature enabled.
- collective controller
- A centralized administrative control point where operations such as MBean routing, file transfer, and cluster management in a collective are performed. A core role of the collective controller is to receive information from the members within the collective so that the data can be retrieved readily without having to invoke an operation on each individual member.
- 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.
- 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.
- 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 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.
- 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.
- 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 queue
- A queue holding work items that can be completed by an external entity that interacts with the workflow.
- 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
- A Service Component Architecture (SCA) element that contains components, services, references, and wires that connect them.
- 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.
- 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.
- concrete portlet
- A logical representation of a portlet object distinguished by a unique configuration parameter (PortletSettings).
- concurrency control
- The management of contention for data resources.
- condition
-
- 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.
- A test of a situation or state that must be in place for a specific action to occur.
- 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 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.
- 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
-
- 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.
- 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.
- 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.
- container
- 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 transaction
- See container-managed transaction.
- 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.
- content event
- An event that responds to document or folder changes on an Enterprise Content Management (ECM) system. See also event.
- contention
- A situation in which a transaction attempts to lock a row or table that is already locked.
- Content Management Interoperability Services (CMIS)
- An open standard designed to facilitate the interoperability of content management systems using web protocols.
- 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
-
- A value that identifies the default values, such as the process instance ID or the activity instance ID, that a task depends on.
- 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.
- Contexts and Dependency Injection (CDI)
- A set of services that provides improved modularity in Java EE applications.
- context-scoped business object
- A summary object or accumulating array object that is used to share data from events across events in a context.
- 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.
- 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.
- 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
- 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.
- 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.
- create method
- In enterprise beans, a method defined in the home interface and invoked by a client to create an enterprise bean. (Sun)
- credential
- 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.
- 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-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.
- CSS
- See Cascading Style Sheets.
- custom action
-
- A Java or non-Java process definition that a user can define as a part of a health policy action plan or elasticity operation.
- 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)
- 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.
- 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 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 graphical user interface that enables users to monitor and manage activities. A dashboard provides a consolidated view of status information that is obtained from various sources.
- data access bean
- A class library that provides a rich set of features and functions, while hiding the complexity associated with accessing relational databases.
- 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 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 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
-
- Any object (such as tables, views, indexes, functions, triggers, and packages) that can be created or manipulated using SQL statements. See also business object.
- An object that provides information about required activities. Data objects can represent one object or a collection of objects. See also shared managed object.
- 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 point
- A name-value pair that represents a unit of business data or a point on a graph. On a graph, a data point is represented as a slice for pie plots, a bar for bar plots, or one point for line plots and area plots. See also data series, name-value pair.
- data series
- A set of data points. See also data point.
- data source
-
- The means by which an application accesses data from a database.
- 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.
- data store
-
- A data structure where documents are kept in their parsed form.
- 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 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.
- DDL
- See Data Definition Language.
- 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 compiles rulesets into executable or intermediate code and can optimize the performance of the rulesets. See also rule engine.
- Decision Model and Notation (BMN)
- An industry standard for describing and modeling organizational decisions that was published by the Object Management Group to support decision management and business rules.
- decision operation
- A function that defines the decision-making logic and the input and output data for a decision. A decision operation is implemented as a ruleset.
- decision service
- A set of related decisions that are contained in a business rule application. Rules make up the decision service and determine its behavior. Decision services can be organized into one or more rule projects.
- 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 ruleset.
- 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.
- 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.
- 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.
- DEF
- See Dynamic Event Framework.
- 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.
- 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.
- 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.
- dependency
- 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.
- 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 configuration
- The manner in which decision operations are packaged into RuleApps, managed, and then deployed to business rule applications.
- 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
- 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 manager
- A server that manages and configures operations for a logical group or cell of other servers. See also subprocess.
- deployment scope
- A setting in the deployment manager that determines the rules of deployment. For example, if a highly available Case Management Client application is being deployed, the deployment scope in the deployment manager must be changed.
- deployment task
- A profile task that must be edited and run before case management solutions can be created and deployed.
- deployment topology
- The configuration of servers and clusters in a deployment environment and the physical and logical relationships among them.
- deprecated
- Pertaining to an entity, such as a programming element or feature, that is supported but no longer recommended and that might become obsolete.
- Derby
- An embeddable, all Java, object-relational database management system (ORDBMS).
- derived event
- See synthetic event.
- deserialization
- A method for converting a serialized variable into object data. See also serializer.
- design object store
- The object store in which solutions are stored in a development environment that is typically in a dedicated IBM Content Cortex domain.
- DESPI
- See Data Exchange SPI architecture.
- developer
- A decision management user role that is responsible for implementing the rule applications.
- 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.
- dictionary
- A set of business model definitions that specify linguistic properties such as translation, plural form, and grammatical gender of one or more terms.
- 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.
- directive
- A first-failure data capture (FFDC) construct that provides information and suggested actions to assist a diagnostic module in customizing the logged data.
- 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.
- discretionary task
- A task that is reserved for activities that are routinely performed for a case but might not be performed regularly.
- distinguished name (DN)
- 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.
- distributed application
- An application made up of distinct components that are located on different computer systems, connected by a network. See also client/server.
- 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 class
- See document type.
- 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.
- 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.
- DOF
- See device output format.
- DOM
- See Document Object Model.
- domain
-
- 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.
- 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.
- drain approach
- A migration approach in which users migrate artifacts to the new system and let the existing process instances in the old system run to completion. See also milestone-transfer approach.
- DTF
- See Data Transformation Framework.
- due-in time
- The expected length of time required for an activity or an entire process instance to complete.
- durable subscription
- A subscription that is retained even while the connection from a subscribing application to a messaging resource, such as a queue, a topic, or a message, is closed. See also nondurable subscription, shared subscription.
- 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
- See late 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 Event Framework (DEF)
- A mechanism for emitting and delivering events about significant system or business occurrences, as defined in a monitor model.
- 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.
- A way to route HTTP requests to members of a Liberty collective without having to regenerate the WebSphere® plug-in configuration file when the environment changes.
- 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.
- EBA
- See enterprise bundle archive.
- 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.
- ECM
- See Enterprise Content Management.
- 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.
- edition
- A successive deployment generation of a particular set of versioned artifacts.
- 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, lifecycle 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 lifecycle 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.
- element
-
- 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. See also attribute.
- In Java development tools, a generic term that can refer to packages, classes, types, interfaces, methods, or fields.
- 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.
- 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
-
- The system that is the origin or destination of a session.
- 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.
- enriched attribute
- An attribute for which the value of an object is accessed from an external data service.
- 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 (EBA)
- 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 Content Management (ECM)
- The strategies, methods and tools used to capture, manage, store, preserve, and deliver content and documents related to organizational processes. ECM tools and strategies allow the management of an organization's unstructured information, wherever that information exists.
- 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
-
- An object that has a unique identifier that permits other objects to refer to it logically. See also entity type.
- 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.
- entity aggregate
- A value that is computed from a collection of entities.
- 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.
- entity relationship
- A unidirectional association between entity types.
- entity type
- A set that identifies entities that share common attributes. For example, Joe Bloggs might be an entity that has an entity type "customer". See also entity.
- entry breakpoint
- A breakpoint set on a component element that is hit before the component element is invoked.
- environment
- A named collection of logical and physical resources used to support the performance of a function.
- environment variable
-
- A variable that specifies how an operating system or another program runs, or the devices that the operating system recognizes.
- 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.
- 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.
- event
-
- An element that is used to represent a change in state.
- 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. See also content event, message event.
- 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.
- An object that has a timestamp that captures when it occurs, and possibly the time zone in which it occurs. See also event type.
- event aggregate
- A value that is computed from a collection of events.
- event binding
- A binding that describes the connection of a set of event types to an endpoint. See also inbound endpoint, outbound endpoint.
- 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 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 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
- 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.
- 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 object
- A subset of the fields in the definition of an event.
- event project
- A project in which the user can manage event rules and business objects.
- 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.
- event type
- A set that identifies events that share common attributes. For example, a "purchase" event might have an amount, an item and a time. See also event.
- exception
- 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.
- 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.
- 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.
- execution component
- A component that authorizes the execution of a ruleset by the execution unit (XU).
- execution object model (XOM)
- A model that references implementation objects used in rules.
- 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 ruleset 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.
- expanded subprocess
- A subprocess that exposes its flow detail within the context of its parent process. An expanded subprocess is enlarged to display the flow objects within.
- expected value
- The average value for a given attribute for a population data set. 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.
- 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
- A file created during the development process for inbound operations that contains the configuration settings for inbound processing.
- exposed process value (EPV)
- A variable that enables the participants of a process to set or change a value while an instance of a process is running, thereby assigning constants and affecting the flow of a process or task assignment.
- 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 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
-
- In Eclipse, the mechanism that a plug-in uses to extend the platform. See also extension point.
- A class of objects designated by a specific term or concept; denotation.
- An element or function not included in the standard language.
- extension point
- In Eclipse, the specification that defines what attributes and values must be declared by an extension. See also extension.
- external system
- A system that exists outside a particular network.
F
- 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 or node in the event of a software, hardware, or network interruption.
- 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.
- A manifest file and a collection of OSGI bundles that correspond to a solution project.
- 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.
- fetchless instantiation
- The use of a factory method that instantiates an object using a name or a path and does not make a round trip to the server.
- 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.
- Content Cortex domain
- A domain that represents a logical grouping of physical resources and the Content Platform 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
-
- In JAX-RS, one or classes that can modify HTTP request and response headers. See also Java API for RESTful Web Services.
- A device or program that separates data, signals, or material in accordance with specified criteria. See also servlet filtering.
- A reusable set of conditions that is used in an event rule to evaluate whether an event matches certain criteria.
- 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)
- fingerprint
- See digest code.
- 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.
- fix pack
- A cumulative collection of fixes that is released between scheduled refresh packs, manufacturing refreshes, or releases. A fix pack updates the system 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.
- flavor
- The settings of a virtual machine that are used for configuration.
- flow
-
- A series of connected steps in a process or service that represents the overall progression of how the process is performed. See also human service, sequence 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
-
- A container used to organize objects.
- A project element that can be used to group rules according to business logic.
- 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 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
-
- 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.
- 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.
- 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.
- 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.
- 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.
- function
- A named group of statements that can be called and evaluated and can return a value to the calling statement.
G
- garbage collection
- A routine that searches memory to reclaim space from program segments or inactive data.
- gate condition
- A condition on a message being processed that must be fulfilled for a mediation policy to apply.
- gateway
-
- A network point that is used to control the divergence and convergence of sequence flow paths in a process and in a choreography.
- A middleware component that bridges Internet and intranet environments during web service invocations.
- 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.
- An integration pattern that provides format-independent boundary functions that apply to all incoming messages.
- 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 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.
- generative AI (gen AI)
- A class of AI algorithms that can produce various types of content including text, source code, imagery, audio, and synthetic data.
- 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 aggregate
- A value that is computed from a collection of objects. Examples of global aggregates are average, count, maximum, minimum, and sum.
- 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 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.
- 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.
- golden topology
- A topology that has a deployment manager, application cluster, messaging cluster and an optional support cluster.
- grammar
- A document type definition (DTD) or schema providing a structured format used for successful processing by the trace service.
- group
-
- A collection of users who can share access authorities for protected resources.
- A set of elements that is associated with the same category.
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.
- 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 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.
- heritage human service
- A human service that runs on the server and provides user interfaces to the web browser. A heritage human service can be used to implement an interactive task or dashboard that users can use in an application. See also client-side human service, human service.
- HFS
- See hierarchical file system.
- 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 (HA)
-
- 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.
- 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.
- 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 key
- The current maximum value for a primary key for each table when the primary key is a number.
- High Performance Extensible Logging (HPEL)
- A log and trace facility that is provided as a part of WebSphere Application Server.
- histogram
- A graphical display of the distribution of values for a numeric field, in the form of a vertical bar chart in which taller bars indicate higher values.
- 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.
- horizontal scaling
- A topology in which more than one application server running on multiple computing nodes is used to run a single application.
- host
-
- In performance profiling, a machine that owns processes that are being profiled.
- 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, Uniform Resource Locator.
- hostname
-
- 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.
- 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.
- HPEL
- See High Performance Extensible Logging.
- 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
- human service
- A service flow that provides user interfaces for web-based applications. See also client-side human service, flow, heritage human service, sequence flow.
- human task
- An interaction between people and business processes or services. See also inline task, stand-alone task.
- 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.
I
- IBM BPM Advanced content
- Content that is developed in IBM Integration Designer and is part of IBM BPM Advanced. When advanced content is deployed, it includes entities like WebSphere Application Server business-level applications, EAR files, and JAR files that are built at deployment time from the artifacts in the database.
- IDE
- See integrated development environment.
- identifier
-
- 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.
- The name of an item in a program written in the Java language.
- 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.
- image
- A static, predefined container that provides specific functions. See also virtual image.
- i-mode
- An Internet service for wireless devices.
- import
-
- A development artifact in a module that obtains a service, which exists outside of the module. Imports are used so that services can be called from within the module. See also import file.
- 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.
- 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
-
- A dialog between a terminal and a message processing program using IMS conversational processing facilities. See also conversational processing.
- 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 authentication
- The configuration that determines the type of accepted authentication for inbound requests.
- inbound binding
- A definition that determines how inbound events via HTTP or JMS are received.
- inbound endpoint
- The origin of inbound events. An inbound endpoint must specify an inbound binding. See also event binding, outbound endpoint.
- 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.
- industry accelerator
- A set of code assets that contains processes, rules, and data objects that are specific to an industry use case and are used to accelerate the time to production.
- 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 context
- Starting point in a namespace.
- initialization point
- A user-defined constant or variable used to initialize the attributes of an object.
- initial reference
- A well-known reference associated with an identifier.
- 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 ruleset 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 ruleset at execution time.
- input activity
- The origin of the process that is the source of the invocation data of the entire process.
- input node
- The point where a service message from a source enters the request flow.
- input response node
- The end point for a mediation response flow from which the service message object is sent to the source.
- 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
-
- An active process element, for example, the performance of a process.
- A process at run time or a deployed pattern.
- A workflow, such as a process or a case, at run time.
- instance document
- An XML document that conforms to a particular schema.
- instantiate
- To represent an abstraction with a concrete instance.
- instrumentation
- In application or system software, the monitoring functions that provide performance information and other information to a management system, or the use of such monitoring functions.
- 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.
- 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 diagram
- An infographic that includes hotspots and hover help that a user can access to get further information or examples.
- 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.
- interceptor
- In JAX-RS, one or more classes that can modify the reading and writing of an HTTP entity body. See also Java API for RESTful Web Services.
- interface
- A collection of operations that are used to specify a service of a class or a component. See also 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 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.
- 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 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.
- isolated region
- A logical subdivision of the workflow database that contains both transferred workflows and the data for all active workflows. Work cannot be shared across or moved between isolated regions. Isolated regions can be used to separate groups of users as appropriate for the organization.
- ISPF
- See Interactive System Productivity Facility.
- iteration
- See loop.
- 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).
J
- J2C
- See J2EE Connector architecture.
- 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 2 Connector security
- See Java Connector security.
- Java 2 Platform, Standard Edition (J2SE)
- See Java Platform, Standard Edition.
- Java agent
- An agent that processes events by using Java code. See also agent.
- Java API for RESTful Web Services (JAX-RS)
- A specification of a Java programming language application programming interface (API) that provides support in creating web services using the Representational State Transfer (REST) architecture. See also filter, interceptor, Java API for RESTful Web Services 2.0.
- Java API for RESTful Web Services 2.0 (JAX-RS 2.0)
- A second generation of JAX-RS that introduces a standardized client API so that users can make HTTP requests to remote RESTful web services. See also JAX-RS. See also Java API for RESTful Web Services.
- 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
- 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)
- 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 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 (Java EE)
- An environment for developing and deploying enterprise applications, defined by Oracle. 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. (Oracle)
- Java Platform, Standard Edition (Java SE)
- The core Java technology platform. (Oracle)
- 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. (Oracle)
- 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 various languages.
- 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-RS
- See Java API for RESTful Web Services.
- JAX-RS 2.0
- See Java API for RESTful Web Services 2.0.
- 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.
- 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
- A separately executable unit of work.
- 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.
- join
-
- In a rule flow, a node that combines all the transitions created from a fork.
- An SQL relational operation in which data can be retrieved from two tables, typically based on a join condition specifying join columns.
- 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.
- 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.
- 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.
- JSON schema
- A JavaScript Object Notation (JSON) document that describes the structure and constrains the contents of other JSON documents.
- 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 that is 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.
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
- A cryptographic mathematical value that is used to digitally sign, verify, encrypt, or decrypt a message. See also private key, public key.
- 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.
- 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 locator
- A mechanism that retrieves the key for XML signing, XML digital signature verification, XML encryption, and XML decryption.
- 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 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. See also tag group.
- 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.
L
- 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.
- large language model (LLM)
- A language model with a large number of parameters, trained on a large quantity of text.
- 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.
- 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.
- Liberty Asset repository service
- An open source service that can be used to create an on-premises Liberty repository that is remotely accessible behind the firewall of an enterprise and that contains assets.
- Liberty repository
- A repository that stores Liberty and other assets, including new product capabilities and configuration and administration resources.
- library
- 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, interfaces, subflows, ESQL modules, message definitions, and Java utilities. See also project.
- library server
- The workstation or node that users must go through to access the system.
- 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)
-
- A protocol that uses cryptography to support security in a distributed environment.
- An authentication framework that allows single sign-on across a set of web servers that fall within an Internet domain.
- 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 XML
- An encoding style for serializing data over SOAP protocol. Literal XML is based on an XML schema instance.
- 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.
- local
- Pertaining to a device, file, or system that is accessed directly from a user system, without the use of a communication line.
- local directory-based repository
- A Liberty repository that is created on the local file system when assets are downloaded using the installUtility download command.
- 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 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 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.
- 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 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.
- LPA
- See link pack area.
- LTC
- See local transaction containment.
- LTPA
- See Lightweight Third Party Authentication.
- LUW
- See logical unit of work.
M
- macroflow
- See long-running process.
- magazine view
- A format for document lists in which properties appear in a phrase, such as created by [property] on [date].
- 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.
- 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 lifecycle of manageable resources.
- manifest
-
- A special file that can contain information about the files packaged in a JAR file. (Sun)
- A file that describes the resources, the location of supporting artifacts, application prerequisites, and services that are included in a bundle.
- 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
-
- 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.
- A file that defines the transformation between sources and targets.
- mapped condition
- A mapped expression that specifies a mapping between the columns in a table and the fields of a business object, and an SQL WHERE clause that determines the data that is retrieved from the database. See also mapped expression, mapped key, mapped query.
- mapped expression
- A relationship between the data in a database and the fields of a business object, and an associated statement that determines the data that is retrieved from the database. See also mapped condition, mapped key, mapped query.
- mapped key
- A mapped expression that specifies a mapping between the columns in a table and the fields of a business object, and that specifies which of these fields are used to determine the data that is retrieved from the database. See also mapped condition, mapped expression, mapped query.
- mapped query
- A mapped expression that specifies an SQL SELECT query or a stored procedure call that determines the data that is retrieved from a database, and a mapping between the columns in the query result set and the fields of a business object. See also mapped condition, mapped expression, mapped key.
- mapping
-
- The act of developing and maintaining a map.
- The relationship between fields in different abstractions of event and action objects.
- mapping service
- A service that intercepts requests that are sent from a client to a provider so that the requests can be transformed or rerouted to a different provider.
- marker bar
- The vertical column along the left edge of the editor area of the workbench, where icons representing bookmarks, breakpoints, and error conditions 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.
- master installation
- In an environment configured to swing profiles, an installation to which service from fix packs or interim fixes is applied. See also swing.
- maximum high key
- The high key that has the maximum value.
- 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.
- 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.
- 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.
- 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.
- 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
-
- 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.
- 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.
- 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.
- message digest
- A hash value or a string of bits resulting from the conversion of processing data to a number.
- 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. See also event.
- message flow
- A connecting object that shows the flow of messages between two collaborating participants. A message flow is represented by a dashed line.
- 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 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 start event
- A start event that is triggered when a specific message is received. See also start event.
- messaging engine
- The messaging and connection point to which applications connect to the bus.
- 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
-
- In object-oriented programming, an operation that an object can perform. An object can have many methods. See also operation.
- 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.
- MFS
- See Message Format Service.
- MFS control block
- See Message Format Service control block.
- 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.
- microservice
- A set of small, independent architectural components, each with a single purpose, that communicate over a common lightweight API.
- 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.
- milestone-transfer approach
- A migration approach in which users transfer the process instance state midstream, let the existing process instances in the old system run to a designated set of business milestones, and then start new instances in the new system from those milestones. See also drain approach.
- MIME
- See Multipurpose Internet Mail Extensions.
- mobile
- See mobile device.
- mobile device (mobile)
- A telephone, tablet, or personal digital assistant that operates on a radio network.
- MOD
- See message output descriptor.
- modeled fault
- A fault message that is returned from a service that has been modeled on the Web Services Description Language (WSDL) port type.
- module
-
- A program unit that is discrete and identifiable with respect to compiling, combining with other units, and loading.
- A software artifact that is used for developing, managing versions, organizing resources, and deploying to the runtime environment.
- 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.
- monitor
-
- 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.
- In performance profiling, to collect data about an application from the running agents that are associated with that application.
- 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.
- mount point
- A logical drive through which volumes are accessed in a sequential access device class. For removable media device types, such as tape, 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.
- 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.
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.
- name-value pair
- A parameter containing a name and a value in the format name=value. See also data point.
- 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.
- 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).
- 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 deployment cell
- A logical group of servers, on one or more machines, managed by a single deployment manager.
- network protocol stack
- A set of network protocol layers and software that work together to process the protocols.
- node
-
- In XML, the smallest unit of a valid, complete structure in a document.
- A logical group of managed servers. See also managed node.
- 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.
- nondurable subscription
- A subscription that exists only while the connection from the subscribing application to a messaging resource, such as a queue, a topic, or a message, remains open. See also durable subscription, shared subscription.
- 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.
- nonproduction system
- A system on which application programs that are in development are run and tested.
- 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.
O
- 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.
- object store
- A set of services that is used to access and manage documents and other objects. An object store resides in a domain, which can contain many object stores.
- on-demand configuration
- A component that detects and dynamically configures routing rules, which tell the on demand router (ODR) how to route requests.
- 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.
- on-prem
- See on-premises.
- on-premises (on-prem)
- Pertaining to software that is installed and run on the local computers of a user or organization.
- Open Mobile Alliance
- An industry forum for developing interoperable mobile service enablers.
- 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.
- Open Virtual Appliance
- See Open Virtualization Format Archive.
- Open Virtualization Format (OVF)
- A Distributed Management Task Force (DMTF) standard that describes a packaging format for virtual server images. See also Open Virtualization Format Archive, virtual appliance.
- Open Virtualization Format Archive (OVA)
- A package that is deployed in a virtual environment to create virtual appliances. The OVA package is an archive file that contains the OVF directory. See also Open Virtualization Format.
- 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.
- ORB
- See Object Request Broker.
- orphaned token
- A token that is associated with an activity that was removed from a process.
- 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.
- outbound
- In communication, pertaining to data that is sent to the network. See also inbound.
- outbound authentication
- The configuration that determines the type of accepted authentication for outbound requests.
- outbound binding
- A definition that determines how outbound events are delivered via HTTP or JMS to an endpoint.
- outbound endpoint
- The destination for outbound events. An outbound endpoint must specify an outbound binding. See also event binding, inbound endpoint.
- 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 ruleset 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 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.
- OVA
- See Open Virtualization Format Archive.
- OVF
- See Open Virtualization Format.
P
- PaaS
- See platform as a service.
- package
-
- In Java programming, a group of types. Packages are declared with the package keyword. (Sun)
- To assemble components into modules and modules into enterprise applications.
- 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.
- 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.
- parallel job manager
- A facility and framework that submits and manages transactional batch jobs that run as a coordinated collection of independent parallel subordinate jobs.
- 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 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.
- 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
- A group of cells in a decision table that are in the same condition column and have a common cell immediately to the left.
- 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.
- path
- 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.
- A model of physical or virtual assets that is used as a template for a solution. A pattern specifies components, links, and policies that follow architecture and design best practices and is used for repeatable deployment of applications, databases, and other resources. A pattern is deployed as a single virtual environment that includes hardware and the workloads that run on it and all related components, links, and policies. See also virtual application pattern, virtual system pattern.
- payload
- The body of a message that holds content.
- PDP
- See policy decision point.
- peer access point
- A means by which core groups can communicate with other cells.
- 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.
- 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
-
- 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.
- In Java EE, the protocol for transferring the state of an entity bean between its instance variables and an underlying database. (Sun)
- 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.
- 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.
- 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
- See PHP Hypertext Preprocessor.
- PHP Hypertext Preprocessor (PHP)
- 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.
- PKA
- See public key algorithm.
- place designer
- A member of a place who can edit place layout and bookmarks. See also place manager.
- place manager
- A member of a place who can edit place membership, layout, and bookmarks. See also 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.
- platform as a service (PaaS)
- The delivery of a computing platform, including applications, optimized middleware, development tools, and Java and Web 2.0 runtime environments, in a cloud-based environment.
- 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.
- 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 manager
- A decision management user role who is responsible for enforcing decisions through the creation and maintenance of rules.
- 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
- 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.
- 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.
- 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 definition of what must be true when a task or process starts.
- 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.
- 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 key
-
- An object that uniquely identifies an entity bean of a particular type.
- In a relational database, a key that uniquely identifies one row of a database table. See also foreign key.
- 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.
- private business object
-
- 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.
- In XSD, a business object attribute that defines an anonymous complex type instead of referencing a named complex type.
- private key
- 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.
- 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
-
- A sequence or flow of activities and tasks 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.
- A progressively continuing procedure consisting of a series of activities that are systematically directed toward a particular result or end. See also case type.
- process application
- A container for process models and supporting implementations. A process application typically includes processes, 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 branches.
- 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 module
- A program unit that contains a set of process templates that support administrative tasks.
- production installation
- A production-grade installation that includes security, high availability, sizing, and scale considerations. Production installations are intended for real world use cases. Typically, production installations require additional system and storage resources from a starter installation.
- profile
-
- Data that describes the characteristics of a user, group, resource, program, device, or remote location.
- A set of files that defines a unique runtime environment, with separate command files, configuration files, and log files.
- 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
-
- A specific organization of rules and other elements that facilitates the authoring and management of a logical grouping of rules.
- 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.
- Data, such as text or an image, that prepares, instructs, or conditions a foundation model's output.
- property
- A characteristic of an object that describes the object. A property can be changed. Properties describe an object name, type, value, or behavior, among other things.
- 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.
- proxy cluster
- A group of proxy servers that distributes HTTP requests across the cluster.
- proxy document
- A document that is a place holder document for documents that are stored in an external repository. Documents that are filed in the same Case folder or sub-folder share a single proxy.
- proxy peer access point
- A means of identifying the communication settings for a peer access point that cannot be accessed directly.
- proxy server
-
- 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.
- 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.
- PTF
- See program temporary fix.
- public
-
- In the Java programming language, pertains to a method or variable that can be accessed by elements residing in other classes. (Sun)
- In object-oriented programming, pertaining to a class member that is accessible to all classes.
- public key
- 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 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
-
- 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.
- To make a website public, for example by putting files in a path known to the HTTP server.
- To send a rule to a server for storage and management.
- 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.
- 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.
- query
- 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.
- queue
- An object that holds messages for message-queuing 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.
R
- RACF
- See Resource Access Control Facility.
- range
- 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.
- 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.
- recorder
- A program that uses HTTP to record tests for SOAP-based, XML, plain text, or binary services.
- 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.
- 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.
- reference object
- A shared object that is referenced within the same report, or in a different report. A reference object does not contain its own content.
- referential integrity
-
- 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.
- 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.
- 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.
- registry
- A repository that contains access and configuration information for users, systems, and software.
- 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 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
- 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.
- 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 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.
- 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 set
- A set of collective controllers where each collective controller can replicate its data to the other collective controllers in the set.
- replication
-
- 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.
- 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.
- repo
- See repository.
- repository (repo)
- 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.
- request flow
- The flow of the message from the service requester.
- 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 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.
- 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
- 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 bundle
- A structured collection of data that provides a key-value mapping for data (resources) used in localizing a program. The values are commonly strings, but may themselves be structured data.
- resource environment reference
- A reference that maps a logical name used by the client application to the physical name of an object.
- resource manager
- An application, program, or transaction that manages and controls access to shared resources such as memory buffers and data sets. IBM 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.
- 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.
- responsive
- Key differentiating property of an on-demand business which is able to respond almost intuitively to dynamic, unpredictable changes in demand, supply, pricing, labor, competitors' moves, capital markets, and the needs of all its constituencies -- customers, partners, suppliers, and employees.
- REST
- See Representational State Transfer.
- 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.
- results algorithm
- An algorithm that manipulates the return codes of batch jobs or provides placeholders for triggers that are based on batch step return codes. A results algorithm is applied to batch steps in a batch application by using xJCL. See also xJCL.
- 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.
- 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.
- rich media
- In a web page, content that is aural, visual, or interactive, such as audio or video files.
- 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.
- RMI
- See Remote Method Invocation.
- RMI/IIOP
- See Remote Method Invocation over Internet InterORB Protocol.
- RMLT
- See resource manager local transaction.
- role
-
- 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.
- The function of an entity that participates in a relationship. 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.
- A logical group of principals that provides a set of permissions. Access to operations is controlled by granting access to a role.
- 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.
- role-based authorization
- The use of authorization information to determine whether a caller has the necessary privilege to request a service.
- role in-basket
- An in-basket that contains work items that are assigned to a role, but not to a specific person. A role in-basket provides access to work items that are assigned to a group of people who share the same role.
- role mapping
- The process of associating groups and principals recognized by the container to security roles specified in the deployment descriptor.
- rolling upgrade
- In clustered systems, updating the system software on a cluster without interrupting service to the users of the cluster.
- 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.
- routing policy
- A set of rules that determine how the server routes incoming requests.
- RPC
- See Remote Procedure Call.
- RRS
- See Resource Recovery Services.
- RU
- See registered user.
- rule
- A statement that defines or constrains some aspect of the business. See also business rule, event rule.
- rule agent
- An agent that includes a set of rules that are written in a business rule language and that are applied to incoming events. See also agent, business rule language.
- 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 rulesets.
- RuleApp archive
- An archive that allows RuleApps to be stored to a file system. RuleApp archives are saved in a strict directory structure.
- rule application
- See RuleApp.
- 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 rulesets 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 project in which business rules and business object models are managed and organized.
- rule project template
- A pattern that defines the folder structure and options for a new rule project.
- 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.
- ruleset
- A decision-making program that can be processed by a rule engine to yield a decision, based on input and output parameters. The decision-making logic is implemented as rules, decision tables, and ruleflows. See also decision table.
- rule set
- 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, if-then rule.
- ruleset extractor
- A mechanism for selecting the rules of the ruleset to be deployed. Selection is typically based on the value of rule properties.
- ruleset interceptor
- A mechanism that allows services to be added to an execution component transparently and to be triggered automatically when certain events occur.
- ruleset parameter
- A parameter that can be defined to set and retrieve values on a ruleset. Ruleset parameters are accessible from outside of the ruleset, and therefore are a bridge between the business logic and the application.
- ruleset signature
- The list of in, out, and inout parameters of a ruleset.
- ruleset variable
- A variable that can be defined to be used in all the rule artifacts of a ruleset.
- 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.
- 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.
- RUP
- See Rational Unified Process.
S
- S4U2Proxy
- See Service-for-User-to-Proxy.
- S4U2Self
- See Service-for-User-to-Self.
- SAAJ
- See SOAP with attachments API for Java.
- SAF
- See System Authorization Facility.
- SAML
- See Security Assertion Markup Language.
- sandbox
- A personal workspace that is used as a staging area for the processing of solution assets.
- SAS
- See Secure Association Service.
- save service
- A service that validates data. The system invokes the save service after the data from the shared business object is merged and before the changes are saved.
- 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
-
- 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.
- 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
-
- In web services, a property that identifies the lifetime of the object serving the invocation request.
- 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.
- 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.
- 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 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.
- 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 context
-
- The digitally signed token that identifies a principal, lists the roles and access rights for the principal, and contains information about when the token expires.
- For an RMI-IIOP request, information that is used to prescribe what the security characteristics are for a particular operation on an object in an Object Request Broker (ORB).
- security domain
- The set of all the servers that are configured with the same user registry realm name.
- security permission
- Authorization granted to access a system resource.
- security policy
- A set of rules that determine the type of security event an agent detects, the priority of each event, and the way an agent responds to an event.
- 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.
- Security Token Service (STS)
- A web service that acts as a trusted third party to broker trust relationships between a web service requester and a web service provider according to the WS-Trust protocol.
- 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.
- 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. See also flow, human service.
- 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.
- 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.
- serializer
- A method for converting object data to another form such as binary or XML. See also deserialization.
- 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, which are called clients. A server can also process requests from other servers. See also client, client/server, 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 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 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
-
- A program that performs a primary function within a server or related software.
- An action that provides functions for a business process, whether performed by a program or a person. A service can be a sequence of services.
- 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.
- An external component that is called by a Java agent or rule agent to access external data or to perform advanced computation.
- service application
- An application used to deploy mediation modules.
- 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-for-User-to-Proxy (S4U2Proxy)
- The Kerberos constrained delegation that allows a service to use the ticket that can be obtained through S4U2Self to obtain another ticket to an external service on behalf of the client. See also Service-for-User-to-Self.
- Service-for-User-to-Self (S4U2Self)
- The Kerberos protocol transition that allows a service to obtain a ticket to itself from the KDC on behalf of a client. See also Service-for-User-to-Proxy.
- 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 level agreement (SLA)
- 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).
- service mapping
- A connection between one client and one or more providers, allowing mismatching service interfaces, service endpoints, or both to be mapped to each other.
- 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 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 stub
- A functional simulation of an existing service that is used for prototyping, entering specific data into a service under test, or replacing a service that is unavailable or impractical to use in a test environment. See also stub server.
- 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
-
- 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.
- In Java EE, an object used by a servlet to track user interaction with a web application across multiple HTTP requests.
- 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.
- 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.
- 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 managed object
- A data object that is shared, defined, and managed independently of active work. Instances of shared managed objects exist beyond the end of the process applications that the shared managed objects were created in. See also data object.
- 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 subscription
- A subscription in which a client shares the work of receiving messages from multiple consumers. See also durable subscription, nondurable subscription.
- 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 name
- In personal communications, the one-letter name (A through Z) of the presentation space or emulation session.
- short-running process
- See microflow.
- SIBus
- See service integration bus.
- 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.
- 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 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.
- 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-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).
- 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.
- A folder in which to organize artifacts to access them easily. A smart folder might contain artifacts that share properties or a smart folder might contain all the artifacts that were modified within a specific period.
- 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.
- snapshot
- A capture of information at a specific time for analysis. The information can be data, a project, or a branch.
- snippet
- An excerpt of source code.
- 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 envelope
- An element in the SOAP standard that describes what is in the SOAP message and provides instructions about how to process it.
- SOAP header
- An element in the SOAP envelope of a SOAP message that contains application-specific context information (for example, security information) that is associated with the SOAP request or response message.
- 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.
- 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.
- software bundle
- A collection of software installation files, configuration files, and metadata that can be deployed on a virtual machine instance.
- 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
-
- An application that processes events. A solution consists of agents, business object models, connectivity, and supporting OSGi services.
- 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.
- solution definition
- A set of solution assets as defined in the design object store.
- Solution Document Generator (deprecated)
- A command line tool that is used to generate a solution description document.
- solution locale
- The locale of display names, such as case properties, case types, tasks, and other solution artifacts that are created with Case Manager Builder.
- solution package
- A package that is created when a solution is exported and refers to the archive file of the solution.
- source
- See source code.
- source code (source)
- 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 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.
- SQL
- See Structured Query Language.
- SQLJ
- See Structured Query Language for Java.
- SQL query
- A component of certain SQL statements that specifies a result table.
- 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.
- stand-alone server
- 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 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.
- starter installation
- A concise installation that is designed to handle starter workloads. Starter installations are typically used for proofs of concept or experimentation with the core product.
- 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.
- state
- In a business state machine, one of several discrete individual stages that are organized in sequence to compose a business transaction.
- stateful
-
- Of or pertaining to a system or process that keeps track of the state of interaction. See also stateless.
- In CSIv2 security, pertaining to a security context that can be reused by multiple requests after it is established and until the target security service or client security service invalidates it.
- 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
-
- In CSIv2 security, pertaining to a security context that can be used only for the duration of a request and not for subsequent requests.
- Having no record of previous interactions. A stateless server processes requests based solely on information that is provided with the request itself, and not based on memory from earlier requests. See also stateful.
- stateless session bean
-
- A session bean that is a collection of operations. The server can optimize resources by reusing bean instances on every method call.
- A session bean with no conversational state. All instances of a stateless bean are identical. (Sun) See also session bean, stateful session bean.
- static
- A Java programming language keyword that is used to define a variable as a class variable.
- static binding
- See early 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.
- 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.
- 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.
- 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.
- STS
- See Security Token Service.
- 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.
- stub server
- An application server that is dedicated to running service stubs. See also service stub.
- subclass
- In Java, a class that is derived from a particular class, through inheritance.
- 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.
- superclass
- In Java, a class from which a particular class is inherited, perhaps with one or more classes in between.
- supertype
- In a type hierarchy, a type that subtypes inherit attributes from.
- swimlane
- 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.
- swing
- To dynamically change profiles to a new service level of a product release. See also master installation.
- 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.
- sync
- See synchronize.
- synchronization
- The process of publishing and updating changes in a rule to a server.
- synchronize (sync)
- 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.
- 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.
- 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.
- sysplex
- A set of z/OS systems that communicate with each other through certain multisystem hardware components and software services.
- System Authorization Facility (SAF)
- A z/OS interface with which programs can communicate with an external security manager, such as RACF.
- 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.
T
- tag
-
- A word or phrase that users create and assign to an asset. Users create tags to develop search criteria that is meaningful to themselves.
- An identifier that groups related artifacts.
- tag group
- A key-value pair that associates a service in a process. See also key-value pair.
- 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.
- takeover
- An automatic operation that switches from a redundant or standby system or node when the primary system or node becomes available after a software, hardware, or network interruption.
- target
- The destination for an action or operation.
- target component
- A component that is the final target of a client service request.
- 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
-
- The basic unit of organization in a rule flow.
- 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.
- An atomic unit of work that is included in a workflow activity, case, or process.
- A unit of work to be accomplished by a user, device, or process.
- 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).
- 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
- A group of people assigned to work on a process, task, or case.
- 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.
- 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.
- 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 driver
- A software module or application used to invoke a test and, often, provide test data, control and monitor execution, and report test outcomes. A test driver sequences and controls the automated execution of one or more 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
-
- 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.
- 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.
- 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 working draft of a project before it is versioned.
- 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
-
- A particular message or bit pattern that signifies permission or temporary control to transmit over a network.
- 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.
- 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.
- touchpoint system
- An external business system that generates events or receives actions.
- track
- See branch.
- 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 processes 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
- 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.
- 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.
- transform
-
- Programming logic that converts data from one format into another format.
- 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.
- 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.
- transition
- A connection between two tasks in a rule flow. Transitions are unidirectional, and they can have conditions attached to them.
- transition condition
-
- A Boolean expression that determines when processing control should be passed to the targeted node.
- In a rule flow, a specification of a transition that dictates when the target task can be executed.
- 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.
- transparent decision service
- A web service for rulesets that are deployed to a Rule Execution Server instance.
- 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 chain
- A network protocol stack that is used for I/O operations in an application server environment. Transport chains are part of the channel framework function that provides a common networking service for all components.
- transport channel chain
- A specification of the transport channels that are used by a server for receiving information. Transport channel chains contain end points
- Transport Layer Security (TLS)
- A set of encryption rules that uses verified certificates and encryption keys to secure communications over the Internet. TLS is an update to the SSL protocol.
- tree
- A data structure whose elements are linked in a hierarchical fashion.
- trigger
-
- In database technology, a program that is automatically called whenever a specified action is performed on a specific table or view.
- A mechanism that detects an occurrence and can cause additional processing in response.
- 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.
- trust file
- A file that contains signer certificates.
- 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.
- TSO
- See Time Sharing Option.
- TTL
- See time to live.
- type
-
- In Java programming, a class or interface.
- In a WSDL document, an element that contains data type definitions using some type system (such as XSD).
- type hierarchy
- The complete context for a Java class or interface including its superclasses and subclasses.
U
- UCA
- See undercover agent.
- 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.
- 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.
- undercover agent (UCA)
- An agent that is attached to a message event in a process 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.
- 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)
-
- A unique address that is used to identify content on the web. 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 location of the resource on that computer. See also Uniform Resource Name.
- A compact string of characters for identifying an abstract or physical resource.
- 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. See also host.
- 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.
- unit test
- To determine the usability of units of code.
- 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.
- 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 lifecycle 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.
- unmatched request
- A SIP request that has To and From tags but whose related dialog is not found in the SIP container because the dialog was never created or is in the invalidated state.
- unmatched response
- A SIP response that is received in the SIP container but is not matched to any outgoing requests.
- 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.
- URI
- See Uniform Resource Identifier.
- URL
- See Uniform Resource Locator.
- URL scheme
- A format that contains another object reference.
- URN
- See Uniform Resource Name.
- 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.
- 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.
- utility class
- A class that contains computer programs that support computer processes, like diagnostics programs, trace programs, and sort programs.
- 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
-
- A representation of a changeable value.
- 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.
- 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 control
- The coordination and integration of the history of work submitted by a team.
- version policy
- A set of characteristics that determines how versions of RuleApps and rulesets are numbered and whether to augment or replace what is deployed on a Rule Execution Server instance.
- 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
- 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.
- virtual appliance
- A prepackaged software application that provides some well-defined business workflow, making it easier to deploy a solution with minimal configuration. Many tiers of operating systems and applications can be packaged as a single virtual appliance. See also Open Virtualization Format.
- virtual application
- A deployment of a standardized set of middleware and resources that is used to run specified types of workloads. Virtual applications are created with optimized patterns and offer more convenience than virtual systems by abstracting the middleware infrastructure and allowing users focus on developing applications. See also virtual application pattern, virtual system.
- virtual application instance
- A single deployment of a virtual application pattern.
- virtual application pattern
- An application-centric pattern that defines the resources that are required to support virtual applications, including web applications, databases, user registries, and more. These patterns are the deployment unit for a virtual application. See also pattern, virtual application, virtual system pattern.
- 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
- A stand-alone virtual environment, including operating system and binary files, that is used to define a virtual system. See also image.
- virtualization
- The substitution of virtual resources for actual resources, where the virtual resources have the same functions and external interfaces as their counterparts, but differ in attributes, such as size, performance, and cost. Virtualization is commonly applied to physical hardware resources by combining multiple physical resources into shared pools from which users receive virtual resources.
- virtual machine
- An abstract specification for a computing device that can be implemented in different ways in software and hardware.
- 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
- A deployment of a flexible set of middleware and resources that is used to define editable application environments. Virtual systems are created with customized topologies and offer more control than virtual applications by allowing users to configure middleware and tune OS settings. See also virtual application, virtual system pattern.
- virtual system pattern
- One or more middleware-centric 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. See also pattern, virtual application pattern, virtual system.
- 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.
- visual snippet
- A diagrammatic representation of a fragment of Java programming language that can be manipulated with the visual snippet editor.
- vocabulary
-
- A repository for storing reusable business elements, such as terms, business item definitions, roles, messages, and errors, that are used in a business process.
- The set of terms and phrases that are used for rule editing.
- VS
- See virtual synchrony.
W
- W3C
- See World Wide Web Consortium.
- WAB
- See web application bundle.
- waiter
- A thread waiting for a connection.
- WAP
- See Wireless Application Protocol.
- WAR
- See web archive.
- WAR file
- See web archive.
- 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 app
- See web application.
- web application (web app)
- 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 bundle (WAB)
- A bundle that contains a web application, and that can be deployed in an OSGi container. A WAB is an OSGi bundle version of a web archive (WAR) file.
- 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 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 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
-
- An application that performs specific tasks and is accessible through open protocols such as HTTP and SOAP.
- 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 binding file
- A file that contains information that CICS uses to transform data formats between XML or JSON and structured application data.
- 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 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 Security (WSS, 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 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.
- 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
- A sequence of activities and tasks that define work, such as a business process, case, or workstream. Workflows can be automated or performed by people.
- workgroup
- A group that is dedicated to a particular task or set of tasks.
- 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
-
- In the human task editor, the representation of a task. Staff members can browse all work items that they have the authority to claim.
- See also inline task, stand-alone task.
- 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
-
- 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.
- A temporary repository of configuration information that administrative clients use.
- workstream
- 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
-
- An alternate and supported interface that hides unsupported data types required by a server object behind a thin intermediate server object.
- An object that encapsulates and delegates to another object to alter its interface or behavior in some way. (Sun)
- 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.
- 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.
- WSI
- See Web Services Interoperability Organization.
- WSIF
- See Web Services Invocation Framework.
- WSIL
- See Web Services Invocation Language.
- WSS
- See Web Services Security.
- WS-Security
- See Web Services Security.
- WYSIWYG
- See what you see is what you get.
X
- X.509 certificate
- A certificate that contains information that is defined by the X.509 standard.
- 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, results algorithm.
- 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 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
- See XML Schema Definition Language.
- 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
- 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.
This topic is shared by BAW, CP4BA. Last updated on 2025-03-13 12:15