Look up terms and definitions that you find in IBM WebSphere products and documentation.
To view glossaries for other IBM products, go to www.ibm.com/software/globalization/terminology.
1. A business process that is generated in response to the processing of an event.
2. An activity that is run on a transition.
3. A series of processing steps, such as document validation and transformation.
4. In a business rule, the event that results from the evaluation of the condition.
1. A unit of work or a building block that performs a specific, discrete task. See also task.
2. An element of a process, such as a task, a subprocess, a loop, or a decision. Activities are represented as nodes in process diagrams.
3. 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.
1. See Application Response Measurement.
2. See automatic restart manager.
1. A graphical object that provides supporting information about the process or elements within the process without directly affecting the semantics of the process.
2. An entity that is used or produced by a software development process. Examples of artifacts are models, source files, scripts, and binary executable files.
1. A logical expression specifying a program state that must exist or a set of conditions that program variables must satisfy at a particular point during program execution.
2. A concept in the meta-model that is used to specify a policy requirement and evaluating endpoints at run time. An assertion is also used to describe the capabilities of an endpoint.
1. In enterprise beans, a relationship that exists between two container-managed persistence (CMP) entity beans. There are two types of association: one-to-one and one-to-many.
2. A connecting object that is used to link information and artifacts with flow objects. An association is represented as a dotted graphical line with an arrowhead to represent the direction of flow.
3. 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.
1. In markup languages such as SGML, XML, and HTML, a name-value pair within a tagged element that modifies features of the element.
2. A characteristic or trait of an entity that describes the entity; for example, the telephone number of an employee is one of the employee attributes. See also entity, identity.
3. A property, quality, or characteristic whose value contributes to the specification of an element or program function. For example, "cost" or "location" are attributes that can be assigned to a resource.
1. The process of granting a user, system, or process either complete or restricted access to an object, resource, or function.
2. In computer security, the right granted to a user to communicate with or make use of a computer system.
1. The condition allowing users to access and use their applications and data.
2. The time periods during which a resource is accessible. For example, a contractor might have an availability of 9 AM to 5 PM every weekday, and 9 AM to 3 PM on Saturdays.
1. In the CVS team development environment, a separate line of development where changes can be isolated. When a programmer changes files on a branch, those changes do not appear on the main trunk or other branches.
2. A distinct path leading to or originating from an element in a process model or UML diagram.
1. An event that occurs during a business process.
2. A significant occurrence in a business process, generally identified by a business analyst, that warrants monitoring over time to reveal a key performance indicator (KPI).
1. In the Map Designer, a data object. There are two types of map cards: input and output.
2. WML document that provides user-interface and navigational settings to display content on mobile devices. See also deck.
1. A container used in a structure diagram to group elements based on a shared attribute or quality.
2. A classification of elements for documentation or analyses.
3. A type class that is used to organize types in a type tree in the Type Designer. Categories organize types that have common properties.
1. A group of managed processes that are federated to the same deployment manager and can include high-availability core groups.
2. One or more processes that each host runtime components. Each has one or more named core groups.
1. A mode by which a business service is consumed by a subscriber.
2. A communication path through a chain to an endpoint.
3. An entry point to the web services gateway that carries requests and responses between web services and the gateway.
1. A basic unit of the classification hierarchy used in the Type Designer. There are three classes: item, group, and category.
2. In object-oriented design or programming, a model or template that can be used to create objects with a common definition and common properties, operations, and behavior. An object is an instance of a class.
1. 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.
2. A diagram that shows the exchange of messages between two or more participants in a BPMN model.
1. In Eclipse, one or more plug-ins that work together to deliver a discrete set of functions.
2. A reusable object or program that performs a specific function and works with other components and applications.
1. A Service Component Architecture (SCA) element that contains components, services, references, and wires that connect them.
2. A group of related data elements used in EDI transactions.
1. A test of a situation or state that must be in place for a specific action to occur.
2. In a business state machine, an expression that guards the transition and allows transition to the next state only when and if the incoming operation evaluates to 'True'. Otherwise, the current state is maintained.
1. In Java EE, a standard extension mechanism for containers to provide connectivity to enterprise information systems (EISs). A connector consists of a resource adapter and application development tools (Sun). See also container.
2. A servlet that provides a portlet access to external sources of content, for example, a news feed from a website of a local television station.
1. An entity that provides life-cycle management, security, deployment, and runtime services to components. (Sun) See also resource adapter, connector.
2. An item that can contain other items. Tags that are added to a container inherit the position of the container.
1. A mechanism that bridges a point in a process flow between two or more process instances.
2. A record used with business processes and state machines to allow two partners to initialize a transaction, temporarily suspend an activity, and then recognize each other again when that activity resumes.
3. The relationship, captured in a correlation expression, that describes how an incoming event is matched with one or more monitoring context instances to which it will be delivered.
1. In JSP programming, an action described in a portable manner by a tag library descriptor and a collection of Java classes and imported into a JSP page by a taglib directive. (Sun)
2. A Java or non-Java process definition that you can define as a part of a health policy action plan.
1. A portion of data in a data stream that can be recognized as belonging to a specific type.
2. Any object (such as tables, views, indexes, functions, triggers, and packages) that can be created or manipulated using SQL statements. See also business object.
3. An object that provides information about required activities. Data objects can represent one object or a collection of objects.
1. The means by which an application accesses data from a database.
2. A repository of data (for example, a DB2 database) to which the runtime server can connect and retrieve data in order to enhance the event being processed.
3. 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.
1. A place (such as a database system, file, or directory) where data is stored.
2. A data structure where documents are kept in their parsed form.
1. A gateway within a business process where the sequence flow can take one of several alternative paths.
2. A gateway that routes an input to one of several alternative outgoing paths, depending on its condition. A decision is like a question that determines the exact set of activities during the execution of a process. Questions might include: What type of order? Or How will the order be shipped?
1. To place files or install software into an operational environment. In Java Platform, Enterprise Edition (Java EE), this involves creating a deployment descriptor suitable to the type of application that is being deployed.
2. To transfer assets from a local development environment into an operational, or runtime, environment.
1. The directory where the published server configuration and web application are located on the machine where the application server is installed.
2. The directory containing the subdirectories and resource files created during customization.
1. The name that uniquely identifies an entry in a directory. A distinguished name is made up of attribute:value pairs, separated by commas.
2. 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.
1. In markup languages, a basic unit consisting of a start tag, end tag, associated attributes and their values, and any text that is contained between the two.
2. A component of a document, such as an EDI, XML, or ROD record. An element can be a simple element or a compound element.
3. In Java development tools, a generic term that can refer to packages, classes, types, interfaces, methods, or fields.
1. A JCA application or other client consumer of an event from the enterprise information system.
2. The system that is the origin or destination of a session.
1. The process of entering and saving user or user group information in a portal.
2. An entitlement for an organization to subscribe to a business service.
1. In markup languages such as XML, a collection of characters that can be referenced as a unit, for example to incorporate often-repeated text or special characters within a document.
2. A simple Java class that represents a row in a database table or entry in a map.
1. A combination of header, trailer, and control segments that define the start and end of an individual EDI message. Each envelope in EDI data begins with a particular segment and ends with a particular segment.
2. A control structure containing documents.
1. A change to a state, such as the completion or failure of an operation, business process, or human task, that can trigger a subsequent action, such as persisting the event data to a data repository or invoking another business process.
2. An occurrence of significance to a task or system. Events can include completion or failure of an operation, a user action, or the change in state of a process. See also resource model, receiver, alert, message.
3. A change to data in an enterprise information system (EIS) that is processed by the adapter and used to deliver business objects from the EIS to the endpoints (applications) that need to be notified of the change.
1. A container for inbound events that enables the user to group events without the overhead of creating a new monitoring context. Event groups are purely a visual construct and are not represented in the monitor model.
2. A set of criteria that is applied to events to identify a subset of those events. The criteria include constraints expressions that define the filter conditions.
1. An event that occurs during the performance of the process that causes a diversion from the normal flow of the process. Exceptions can be generated by intermediate events, such as time, error, or message.
2. A condition or event that cannot be handled by a normal process.
1. A file created during the development process for inbound operations that contains the configuration settings for inbound processing.
2. The file containing data that has been exported.
1. A statement about data objects. Expressions are a combination of literals, object names, operators, functions, and map names. Component rules are expressions that evaluate to either TRUE or FALSE. Map rules are expressions that evaluate to data to produce the desired output.
2. An SQL or XQuery operand or a collection of SQL or XQuery operators and operands that yields a single value.
1. An element or function not included in the standard language.
2. In Eclipse, the mechanism that a plug-in uses to extend the platform. See also extension point.
3. A class of objects designated by a specific term or concept; denotation.
1. Business logic that is applied to the content of an event to determine whether the event matches certain criteria.
2. A device or program that separates data, signals, or material in accordance with specified criteria. See also servlet filtering.
1. 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.
2. An object of the business process model that helps connect components in the workflow.
1. A process element that makes copies of its input and forwards them by several processing paths in parallel.
2. 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.
1. A middleware component that bridges Internet and intranet environments during web service invocations.
2. See destination.
3. An element that is used to control the divergence and convergence of sequence flow paths in a process and in a choreography.
4. An integration pattern that provides format-independent boundary functions that apply to all incoming messages.
5. An element that controls the splitting and recombining of paths in a process flow.
1. Pertaining to an element that is available to any process in the workspace. A global element appears in the project tree and can be used in multiple processes. Tasks, processes, repositories, and services can be either global (referenced by any process in the project) or local (specific to a single process). See also local.
2. Pertaining to information available to more than one program or subroutine. See also local.
1. A collection of users who can share access authorities for protected resources.
2. In places, two or more people who are grouped for membership in a place.
3. A set of elements that is associated with the same category.
4. A set of related documents within an interchange. An interchange can contain zero to many groups.
5. A complex data object that consists of components. A group type is represented by a green dot next to the type name in the type tree.
1. The ability of IT services to withstand all outages and continue providing processing capability according to some predefined service level. Covered outages include both planned events, such as maintenance and backups, and unplanned events, such as software failures, hardware failures, power failures, and disasters.
2. Pertaining to a clustered system that is reconfigured when node or daemon failures occur, so that workloads can be redistributed to the remaining nodes in the cluster.
1. In performance profiling, a machine that owns processes that are being profiled. See also server.
2. A computer that is connected to a network and that provides an access point to that network. The host can be a client, a server, or both a client and server simultaneously. See also server, client.
1. In Internet communication, the name given to a computer. The host name might be a fully qualified domain name such as mycomputer.city.company.com, or it might be a specific subname such as mycomputer.
2. The network name for a network adapter on a physical machine in which the node is installed.
1. See HTTP over SSL.
1. In the 3270 terminal services development tool, a field on a screen definition that uniquely identifies the state of the screen. Users can choose which fields will be identifiers when creating recognition profiles.
2. The name of an item in a program written in the Java language.
1. The point at which an SCA module accesses an external service, (a service outside the SCA module) as if it was local. An import defines interactions between the SCA module and the service provider. An import has a binding and one or more interfaces.
2. A development artifact that imports a service that is external to a module. See also import file.
1. A dialog between a terminal and a message processing program using IMS conversational processing facilities. See also conversational processing.
2. In IMS Connector for Java, the dialog between a Java client program and a message processing program.
1. The point where a service message from a source enters the request flow.
2. A message flow node that represents a source of messages for a message flow or subflow.
1. A set of servers that share a common runtime database, plus their corresponding brokers and queue managers.
2. An active process element, for example, the performance of a process.
3. A specific occurrence of an object that belongs to a class. See also object.
1. An entity within a location that can be equipped with tags and whose positions can therefore be tracked, such as an asset or person.
2. A simple data object that does not consist of other objects. An item type is represented by a blue dot next to the type name in the type tree.
1. A tool that parses the declarations and documentation comments in a set of source files and produces a set of HTML pages describing the classes, inner classes, interfaces, constructors, methods, and fields. (Sun)
2. Pertaining to the tool that parses the declarations and documentation comments in a set of source files and produces a set of HTML pages describing the classes, inner classes, interfaces, constructors, methods, and fields.
1. A process element that recombines and synchronizes parallel processing paths after a decision or fork. A join waits for input to arrive at each of its incoming branches before permitting the process to continue.
2. 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.
3. The configuration on an incoming link that determines the behavior of the link.
4. An SQL relational operation in which data can be retrieved from two tables, typically based on a join condition specifying join columns.
1. A cryptographic mathematical value that is used to digitally sign, verify, encrypt, or decrypt a message. See also private key, public key.
2. Information that characterizes and uniquely identifies the real-world entity that is being tracked by a monitoring context.
1. A project that is used for the development, version management, and organization of shared resources. Only a subset of the artifact types can be created and stored in a library, such as business objects and interfaces. See also project.
2. A collection of model elements, including business items, processes, tasks, resources, and organizations.
1. An authentication framework that allows single sign-on across a set of web servers that fall within an Internet domain.
2. A protocol that uses cryptography to support security in a distributed environment.
1. Pertaining to a device, file, or system that is accessed directly from a user system, without the use of a communication line. See also remote.
2. Pertaining to an element that is available only in its own process. See also global.
1. A physical space that is being monitored. A location can contain many areas. See also area.
2. A particular occurrence or example of a location definition. If there is a location definition called USA Call Center, an example of a location would be Toledo Call Center.
1. A file that defines the transformation between sources and targets.
2. 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.
3. A data structure that maps keys to values.
1. The process of transforming data from one format to another.
2. The act of developing and maintaining a map.
3. The relationship between fields in different abstractions of event and action objects.
1. 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.
2. A process element that recombines multiple processing paths, typically after a decision. A merge brings several alternative paths together.
1. An object that depicts the contents of a communication between two participants. A message is transmitted through a message flow and has an identity that can be used for alternative branching of a process through the event-based exclusive gateway.
2. A set of data that is passed from one application to another. Messages must have a structure and format that is agreed by the sending and receiving applications. See also category.
1. A connecting object that shows the flow of messages between two collaborating participants. A message flow is represented by a dashed line.
2. A sequence of processing steps that execute in the broker when an input message is received. Message flows are defined in the workbench by including a number of message flow nodes, each of which represents a set of actions that define a processing step. The connections in the flow determine which processing steps are carried out, in which order, and under which conditions. See also subflow, mediation flow.
1. In Java EE programming, a software unit that consists of one or more components of the same container type and one deployment descriptor of that type. Examples include EJB, Web, and application client modules. (Sun) See also project.
2. A software artifact that is used for developing, managing versions, organizing resources, and deploying to the runtime environment.
3. A program unit that is discrete and identifiable with respect to compiling, combining with other units, and loading.
1. A facility of the integration test client that listens for requests and responses that flow over the component wires or exports in the modules of a test configuration.
2. In performance profiling, to collect data about an application from the running agents that are associated with that application.
1. The fundamental shapes that make up a diagram.
2. In XML, the smallest unit of valid, complete structure in a document.
3. A logical grouping of managed servers. See also managed node.
4. Any item on a tree control, including a simple element, compound element, mapping command, comment, or group node.
1. An occurrence within a process that can trigger an action. Notifications can be used to model conditions of interest to be transmitted from a sender to a (typically unknown) set of interested parties (the receivers).
2. A message that contains the event descriptions that are sent to managed resources, Web services and other resources.
1. An abstract representation of the fields in an event or action definition.
2. In object-oriented design or programming, a concrete realization (instance) of a class that consists of data and the operations associated with that data. An object contains the instance data that is defined by the class, but the class owns the operations that are associated with the data.
1. To assemble components into modules and modules into enterprise applications.
2. In Java programming, a group of types. Packages are declared with the package keyword. (Sun)
3. The wrapper around the document content that defines the format used to transmit a document over the Internet, for example, RNIF, AS1, and AS2.
1. 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.
2. A member of a portal place who can visit and use the place. By default, all portal users are participants in public places. See also place designer, place manager.
1. A route that the flow can take through the activities in a process. There may be several alternative paths.
2. The route through a file system to a specific file.
1. A characteristic of data that is maintained across session boundaries, or of an object that continues to exist after the execution of the program or process that created it, typically in nonvolatile storage such as a database system.
2. In Java EE, the protocol for transferring the state of an entity bean between its instance variables and an underlying database. (Sun)
1. A graphical container that represents the different business entities or roles that participate in a process.
2. The graphical representation of a participant in a collaboration.
1. In the Internet suite of protocols, a specific logical connector between the Transmission Control Protocol (TCP) or the User Datagram Protocol (UDP) and a higher level protocol or application.
2. 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.
1. In a relational database, a key that uniquely identifies one row of a database table. See also constraint, foreign key.
2. An object that uniquely identifies an entity bean of a particular type.
1. In XSD, a business object attribute that defines an anonymous complex type instead of referencing a named complex type.
2. 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.
1. A sequence or flow of activities in an organization with the objective of carrying out work. In BPMN, a process is depicted as a graph of flow elements, which are a set of activities, events, gateways, and sequence flow paths that adhere to BPMN execution semantics.
2. A progressively continuing procedure consisting of a series of controlled activities that are systematically directed toward a particular result or end.
3. The sequence of documents or messages to be exchanged between the Community Managers and participants to run a business transaction.
1. 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.
2. 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.
1. In object-oriented programming, pertaining to a class member that is accessible to all classes.
2. In the Java programming language, pertains to a method or variable that can be accessed by elements residing in other classes. (Sun)
1. To make a Web site public, for example by putting files in a path known to the HTTP server.
2. 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.
1. A reusable request for information about one or more model elements
2. A request for information from a database that is based on specific conditions: for example, a request for a list of all customers in a customer table whose balances are greater than USD1000.
1. The condition that exists when all intended references from data in one column of a table to data in another column of the same or a different table are valid.
2. In Extensible Markup Language (XML) tools, the condition that exists when all references to items in the XML schema editor or DTD editor are automatically cleaned up when the schema is detected or renamed.
1. The process of maintaining a defined set of data in more than one location. Replication involves copying designated changes for one location (a source) to another (a target) and synchronizing the data in both locations.
2. The process of copying objects from one node in a cluster to one or more other nodes in the cluster, which makes the objects on all the systems identical.
1. A person, piece of equipment, or material that is used to perform an activity.
2. A facility of a computing system or operating system required by a job, task, or running program. Resources include main storage, input/output devices, the processing unit, data sets, files, libraries, folders, application servers, and control or processing programs.
3. A discrete asset, for example application suites, applications, business services, interfaces, endpoints, and business events.
1. 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.
2. Map input and output data sources that are used to retrieve and route data. Resource adapters provide access to databases, files, messaging systems, and other data sources and targets. Each adapter includes a set of adapter commands that can be used to customize its operation.
1. In a relationship, a role determines the function and participation of entities. Roles capture structure and constraint requirements on participating entities and their manner of participation. For example, in an employment relationship, the roles are employer and employee.
2. 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.
3. A logical group of principals that provides a set of permissions. Access to operations is controlled by granting access to a role.
4. 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.
5. A set of permissions or access rights.
6. A description of a function to be carried out by an individual or bulk resource, and the qualifications required to fulfill the function. In simulation and analysis, the term role is also used to refer to the qualified resources.
1. The criteria or circumstances that are defined to trigger an event. For example, rules can be triggered during entry to or exit from a zone and can be specified for a tag ID, class, or group.
2. A condition that must be satisfied when a business activity is being performed.
3. See interaction block.
1. In Web services, a property that identifies the lifetime of the object serving the invocation request.
2. A specification of the boundary within which system resources can be used.
1. In service-oriented architecture, a unit of work accomplished by an interaction between computing devices.
2. A component that accepts as input a message, and processes the message. For example, a service translates its payload into a different format, or routes it to one of several output queues. Most services are implemented as message flows or primitives.
1. A series of requests to a servlet originating from the same user at the same browser.
2. A logical or virtual connection between two stations, software programs, or devices on a network that allows the two elements to communicate and exchange data for the duration of the session. See also transaction.
3. In Java EE, an object used by a servlet to track user interaction with a Web application across multiple HTTP requests.
1. A catalog service or container server that is managed from the operating system that starts and stops the server process.
2. A fully operational server that is managed independently of all other servers, using its own administrative console.
1. A session bean that is a collection of operations. The server can optimize resources by reusing bean instances on every method call.
2. A session bean with no conversational state. All instances of a stateless bean are identical. (Sun) See also session bean, stateful session bean.
1. An item that contains identifying information about a person or device. Tags enable tracking and monitoring of assets within locations, areas, and zones.
2. In UN/EDIFACT EDI Standards, the segment identifier. In export and import, a code that is assigned to each field in the database and used to identify the field in the export file. Such export files are known as tagged files.
1. The destination for an action or operation.
2. A value that a Key Performance Indicator (KPI) should achieve, such as "300" or "5 days."
3. See receiver.
1. A unit of work to be accomplished by a device or process.
2. The basic building blocks in a model. Each task performs a function. Visually, a task represents the lowest level of work that can be portrayed in a process. See also activity.
3. An atomic activity that is included within a process. A task is used when the work in the process is not broken down to a finer level of process model detail. Generally, an end-user, an application, or both perform the task. A task object is the same shape as the subprocess, which is a rectangle that has rounded corners.
1. A marker used to track the current state of a process instance during a simulation run.
2. A particular message or bit pattern that signifies permission or temporary control to transmit over a network.
1. A subprocess that represents a set of coordinated activities that are carried out by independent, loosely coupled systems in accordance with a contractually defined business relationship. This coordination leads to an agreed, consistent, and verifiable outcome across all participants.
2. A process in which all of the data modifications that are made during a transaction are either committed together as a unit or rolled back as a unit.
1. To convert a document from one form to another, such as using a purchase order formatted as an XML document to create the same purchase order formatted as an EDI document. See also translate.
2. Programming logic that converts data from one format into another format.
1. A mechanism that detects an occurrence and can cause additional processing in response.
2. In database technology, a program that is automatically called whenever a specified action is performed on a specific table or view.
1. In Java programming, a class or interface.
2. The definition of a data object or set of data objects that is graphically represented in a type tree in the Type Designer.
3. In a WSDL document, an element that contains data type definitions using some type system (such as XSD).
1. See universal character set.
2. See Uniform Communication Standard.
1. A unique address that is used to identify content on the web, such as a page of text, a video or sound clip, a still or animated image, or a program. The most common form of URI is the web page address, which is a particular form or subset of URI called a Uniform Resource Locator (URL). A URI typically describes how to access the resource, the computer that contains the resource, and the name of the resource (a file name) on the computer. See also Uniform Resource Name.
2. A compact string of characters for identifying an abstract or physical resource.
1. A self-contained, self-describing modular application that can be published, discovered, and invoked over a network using standard network protocols. Typically, XML is used to tag the data, SOAP is used to transfer the data, WSDL is used for describing the services available, and UDDI is used for listing what services are available. See also SOAP, Universal Description, Discovery, and Integration, Web Services Description Language.
2. An application that performs specific tasks and is accessible through open protocols such as HTTP and SOAP.
1. A connector used to pass control and data from a component or an export to a target.
2. To connect two or more components or cooperative portlets so that they work together. In an application, wiring identifies target services; for portlets changes in the source portlet automatically update the target portlets.
1. A temporary repository of configuration information that administrative clients use.
2. A directory on disk that contains all project files, as well as information such as preferences.
3. In Eclipse, the collection of projects and other resources that the user is currently developing in the workbench. Metadata about these resources resides in a directory on the file system; the resources might reside in the same directory.
1. An object that encapsulates and delegates to another object to alter its interface or behavior in some way. (Sun)
2. An alternate and supported interface that hides unsupported data types required by a server object behind a thin intermediate server object.
1. See XML Schema Infoset Model.
2. See XML Schema Definition Language.
1. See Extensible Stylesheet Language Transformation.
2. See XSL Transformation.
1. A logical section within an area that can span multiple subareas. Zones are the units on which rules can be performed and defined. The counts and statistics for a tag are calculated when the tag enters or leaves a zone.
2. A function that enables rules-based shard placement to improve grid availability by placing shards across different data centers, whether on different floors or even in different buildings or geographies.