A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
| |
Access Control Lists (ACLs) |
A table that tells a computer operating system which access rights each user has to a particular system object, such as a directory or individual file. Each object has a security attribute that identifies its access control list. The list has an entry for each system user with access privileges. The most common privileges include the ability to read a file (or all the files in a directory), to write to the file or files, and to execute the file (if it is an executable file, or program). |
Alert |
The sending of information to designated users to indicate that some user action is required; also called a notification. |
API |
Application program interface. An API is the specific method prescribed by a computer operating system or by another application program by which a programmer writing an application program can make requests of the operating system or another application. An API can be contrasted with a graphical user interface or a command interface (both of which are direct user interfaces) as interfaces to an operating system or a program. |
Archive |
A set of data that has been saved in order to preserve a history of events or actions taken. |
Audit trail |
The recording to persistent storage of all significant actions taken by the system to complete a transaction; also known as logging. |
Auditing |
The ability to query, view, and report on logged information. |
BRANCH |
A flow step that executes a specified step based on the value of a variable in the pipeline. |
Breakpoint |
A feature used when testing and debugging to indicate a point in a flow service where you want processing to stop. Breakpoints can help you isolate a section of code or examine data values at a particular point in the execution path. |
The portion of the webMethods Integration Server that performs the caching of service results. Caching can greatly improve throughput when many clients are requesting the same service with identical inputs. | |
Call stack |
A feature used when testing and debugging that identifies which service generated the error and lists its antecedents. The call stack is LIFO-based. That is, the top entry in the stack identifies the last (i.e., most recent) service invoked. The bottom entry identifies first service that was invoked in a nested series. |
Client classes |
webMethods client classes are the thin client classes for Java, C/C++, and COM (Visual Basic, etc.) that enable secure, guaranteed messaging between partner applications across corporate firewalls. webMethods Client Classes communicate via XML-PRC over HTTP. |
COM |
Microsoft's framework for developing and supporting program component objects. It is aimed at providing similar capabilities to those defined in CORBA (Common Object Request Broker Architecture), a framework for the interoperation of distributed objects in a network that is supported by other major companies in the computer industry. Whereas Microsoft's OLE provides services for the compound document that users see on their display, COM provides the underlying services of interface negotiation, life cycle management (determining when an object can be removed from a system), licensing, and event services (putting one object into service as the result of an event that has happened to another object). COM includes COM+, DCOM, and ActiveX interfaces and programming tools. |
Commerce XML (cXML) |
cXML is a set of lightweight XML DTDs based on the World Wide Web Consortium's XML standard, with the W3Cs associated request/response processes. cXML provides an infrastructure that will streamline the process of digitally exchanging catalog content and transactions in a secure manner. |
Complex type definitions |
A datatype definition in an XML Schema that describes the structure and content for an element. A complex type definition can contain element declarations, attribute declarations, and element references. |
Constraining facets |
Constraints that limit the permitted values of a variable. The constraining facets you can use depend on the content constraints applied to the variable. Constraining facets and content constraints are applied to variables for validation purposes. |
Content constraints |
Validation constraints that describe the types of data and possible values for a variables. For each content constraint, you can also specify constraining facets to limit the possible values for the variables. You can apply a content type that corresponds to one of the simple types built-in to XML or to a simple type defined in an XML Schema definition. |
Content Manager |
The portion of the webMethods Integration Server that is responsible for decoding client requests and encoding data that is returned to clients. |
Context Manager |
The portion of the webMethods Integration Server that allows the server to process multiple, concurrent requests using a single copy of the service in memory. |
CORBA |
Common Object Request Broker Architecture. |
Cross-reference |
The substituting of one piece of information for another to ensure the final data meets the definition of data to be provided to the end point; also called a look-up. For example, your company uses a catalog item with a tag named Color. Your supplier/partner refers to the same attribute as CLR. A cross-reference is defined that translates the data from CLR to Color. |
Data Transformation |
The changes made to variables and variable contents to resolve name, structure, and value discrepancies. |
Data types |
A classification of a type of information. Each data type supported by the webMethods Integration Server corresponds to a Java data type and has an associated icon. |
Dependent |
An element that uses a selected element. For example, suppose that the flow ServiceA invokes the built-in service pub.web:loadDocument. ServiceA uses the pub.web:loadDocument service; therefore, flow ServiceA is a dependent of pub.web:loadDocument. |
Dimensionality |
The number of arrays to which a variable belongs. For example, the dimensionality of of a single String is 0, that of a String List or Record List is 1, and that of a String Table is 2. A String that is a child of a Record List has a path dimension of 1. |
Document Object Model (DOM) |
An addressing system for accessing information within documents. |
Document Type Definition (DTD) |
Defines the SGML syntax dialect tags that are used to mark up a document. Tags within the HTML DTD are limited to the HTML standard; however, XML is a meta-language that can define new DTDs as needed. For example, XML can be used to describe a part in inventory with customized tags and/or attributes such as "Part Name", "SKU", and "Quantity." |
Electronic Data Interchange (EDI) |
A system of syntax and semantics for the electronic exchange of business documents between trading partners. EDI has been in development and use for over 30 years by major corporations, first in North America and subsequently across the world. The syntax is not based on any existing Internet or Web syntax, because it predates both. |
Event |
A specific action that the Event Manager recognizes and an event handler can react to. Event types include audit events, exception events, guaranteed delivery events, and replication events. |
Event handler |
A service that you write to perform some action when a particular event occurs. An event handler can be any type of service-a flow service or a Java service. Event handlers subscribe to the events that they want to be notified of. Use the Event Manager to subscribe an event handler to an event. |
EXIT |
A flow step that exits an entire flow service or a single flow step. |
Explicitly mapped variables |
Pipeline variables and service variables you manually map to each other. Explicit mapping accomplishes the name and structure transformations necessary for a flow service. The Pipeline Editor connects explicitly mapped variables with a black link. |
EXtensible Stylesheet Language (XSL) |
A language for expressing stylesheets that defines how to present XML. Given a class of structured documents or data files in XML, designers use XSL to express their intentions about how that structured content should be presented; that is, how the source content should be styled, presented, and paginated onto some presentation medium such as a window in a Web browser or a set of physical pages in a book. |
Flow control step |
The term used to collectively refer to the group of flow operations that provide conditional processing capabilities and allow you to build looping, branching, and retry structures in a flow service. Examples of flow-control steps include LOOP, BRANCH, REPEAT, and SEQUENCE. |
Flow step |
The basic unit of work within a flow service. Flow steps are expressed in webMethods flow language and are interpreted and executed by the webMethods Integration Server at run time. Examples of flow steps include INVOKE, LOOP, and MAP. |
A service that is written in webMethods flow language. A flow service invokes other services and directs the flow of data among them. A flow service can optionally include flow control steps that perform looping, branching, and retry processing. | |
Hypertext Markup Language (HTML) |
The language that defines a simple, fixed type of document with markup designed for standard features such as headings, paragraphs, lists, and illustrations, with some limited provision for multimedia. |
Hypertext Transfer Protocol (HTTP) |
The protocol used to access hypertext and hypermedia information. |
Hypertext Transfer Protocol/Security (HTTP/S) |
The secure version of the Hypertext Transfer Protocol (HTTP). |
IData object |
An IData object is the collection of name/value pairs on which a service operates. An IData object can contain any number of elements of any valid Java objects, including additional IData objects and IDataCodable objects. |
IDE |
Integrated Development Environment. |
Implicitly mapped variables |
Pipeline variables and service variables the Pipeline Editor automatically maps to each other. The Pipeline Editor automatically maps variables whose names are the same and data types are compatible. The Pipeline Editor connects implicitly mapped variables with a gray link. The Pipeline Editor does not display implicit maps if a MAP step is selected in the flow pane. |
Input/Output Validation |
The process of verifying the inputs and/or outputs of a service by validating the inputs and/or outputs against the signature of the service. |
Integration module (IM) |
An add-on Package that provides enhanced functionality. In earlier versions of the webMethods Integration Server, this term referred to services that were written in programming languages such as Java, C/C++, or Visual Basic. |
Integration server |
Integration servers link e-commerce servers, application servers, ERP systems, and legacy data sources over the Internet. |
INVOKE |
A flow step that executes a specified service. |
Java service |
A service that is written in Java. |
Java Naming and Directory Interface (JNDI) |
An API that provides naming and directory functionality to applications written in the Java programming language. The JNDI is defined to be independent of any specific directory service implementation. Thus, a variety of directoriesnew, emerging, and already deployed onescan be accessed in a common way. |
Lightweight Directory Access Protocol (LDAP) |
The emerging de-facto standard for communicating with existing infrastructures that control and manage access to phone numbers, locations, passwords, access privileges, and anything else relevant to each directory entry. |
Link |
In the Pipeline Editor, the line connecting to variables mapped to each other. If the variables are implicitly mapped, the link is gray. If the variables are explicitly mapped, the link is black. If properties have been set for the link (either an applied condition or an index value), the link is blue. |
Logging |
The recording to persistent storage of all significant actions taken by the system to complete a transaction; also known as the audit trail. |
LOOP |
A flow step that executes a set of steps once for each element in a specified array. |
MAP |
A flow step that performs specified editing operations on the pipeline; for example adding variables to or dropping variables from the pipeline. |
Middleware |
Software that connects two otherwise separate applications. |
Name Transformation |
A data transformation in which the value and position of a variable in the record structure remains the same, but the name of the variable changes. |
Network Information Service (NIS) |
A directory service available on the Solaris operating system that is used to store system-related information such as that relating to machines, networks, printers, and users. |
Notification |
The sending of information to designated users to indicate that some user action is required; also called an alert. |
A process used to copy a package from one webMethods Integration Server and install it on another. Also referred to as publishing. | |
Partner profile |
A set of information about trading partners that helps determine how and why the partners work together; it also helps companies with many partners to distinguish between partners. |
Partners |
Companies that do business with one another. |
Pipeline |
The general term used to refer to the data structure in which input and output values are maintained for a flow service at run time. The pipeline starts with the input to the flow service and collects inputs and outputs from subsequent services in the flow. When a service in the flow executes, it has access to all data in the pipeline. |
Pipeline Editor |
The facility you use to inspect the pipeline and route input and output between services in a flow. |
Pipeline reference |
A transformer or pipeline modifier (Map, Drop, or Set Value) involving a variable in a record reference. For example, if ServiceA declares a record reference to PORecord as a variable in its input signature, and ServiceA maps a variable from PORecord to a new variable in the pipeline, then that mapping is a pipeline reference. |
Pipeline Validation |
The process of verifying the structure and content of the pipeline by validating it against a record. |
Primitive type |
The data type of the variable when all dimensionality is removed. For example, the primitive type for a String List or a String Table would be String. |
Protocol Manager |
The portion of the webMethods Integration Server that incoming requests for services. The webMethods Integration Server architecture is extensible and supports a number of simultaneous protocols including HTTP, SAP RFC, FTP, etc. |
Purging |
The removal of data stored at defined intervals via user action or scheduled job. Purging can be to another file or further storage, or it could complete a deletion. |
Record Validation |
The process of verifying the structure and content of an individual record in the pipeline by validating it against a record. |
Reference |
A element that is used by a selected element. For example, suppose that the flow service ServiceA invokes the services pub.web:loadDocument, ProcessPO, and SubmitPO, and declares a Record Reference to PORecord as part of its input signature. The services pub.web:loadDocument, ProcessPO, and SubmitPO, and the record reference PORecord are used by ServiceA; therefore, they are references of ServiceA. |
REPEAT |
A flow step that re-executes a set of steps up to a specified number of times based on the successful or non-successful completion of the set. |
Replication service |
A service that the webMethods Integration Server automatically executes when it prepares to replicate a package. Replication services provide a way for a package to persist state or configuration information so that these are available when the published package is activated on the remote server. |
Routing signature |
The routing-related fields in a document header (sender, receiver, document type, etc.) that a specific partner management implementation cares about. |
schema |
The blueprint or model document that you validate an XML document against. The schema defines what can and cannot be contained in the XML documents it is validated against. |
Secure Sockets Layer (SSL) |
A program layer created by Netscape for managing the security of message transmissions in a network. Netscape's idea is that the programming for keeping your messages confidential ought to be contained in a program layer between an application (such as your Web browser or HTTP) and the Internet's TCP/IP layers. The "sockets" part of the term refers to the sockets method of passing data back and forth between a client and a server program in a network or between program layers in the same computer. Netscape's SSL uses the public-and-private key encryption system from RSA, which also includes the use of a digital certificate. |
Security Manager |
The portion of the webMethods Integration Server that provides security measures for:
Authentication. The Integration Server authenticates all client connections by either a user ID and a password, or through the use of a digital certificate, and the server authenticates itself to other clients or remote webMethods Integration Servers by use of its own digital certificate.
Authorization. The server uses Access Control Lists (ACLs) to define what users (or groups of users) are authorizedor deniedaccess to a service or a folder that includes a collection of services. Data Privacy uses the Secure Socket Layer protocol (SSL) to secure both inbound and outbound requests. SSL libraries are embedded in the webMethods Integration Server and in the webMethods Client libraries. |
SEQUENCE |
A flow step that groups a set of steps into a series. The sequence step is implicit in most cases where a group of flow steps are listed one after another; however, it may be used explicitly to override default operating parameters. |
Service |
A procedure (a single unit of work) that you create using Developer and execute on the webMethods Integration Server. A service might be an entire application, but more likely it is part of a larger application. A service can be written in a language such as Java, C/C++, or Visual basic. Multiple services can be collected into a single service, called a flow service, with Developer. |
Shutdown service |
A service that the webMethods Integration Server automatically executes when it unloads a package from memory. Shutdown services are useful for executing clean-up tasks such as closing files and purging temporary data. You can also use them to capture work-in-progress or state information before a package unloads. |
Signature |
A term that is often used to refer to the set of variables (names and data types) that a service takes as input and produces as output. For example, the signature of a service that generates an authorization code for a credit card might consist of two string inputs (AcctNumber and ExpirationDate) and one string output (AuthCode). Within Developer, a services signature is referred to as its Input/Output specifications, or simply its specification. |
Simple types |
A datatype definition in an XML Schema that describes or limits the values for an element. Simple type defintions cannot have element content and cannot carry attributes. |
Specification |
A formal description of a services inputs and outputs that you create when you build a service. By including a specification, you make the input and output requirements of your service known to other developers who may want to use that service in a flow. It also enables a services inputs and outputs to be recognized by Developer so they can be mapped with values in the pipeline. |
Standard Generalized Markup Language (SGML) |
A standard formatting language that enables a publisher to create a single document source that can be displayed or printed in a variety of ways. SGML is a large, complex formatting language that is not especially suited to the Web. HTML and XML are simplified versions of SGML that are specifically designed to support Web applications. |
Startup service |
A service that the webMethods Integration Server automatically executes when it loads a package into memory. Startup services are useful for generating initialization files or assessing and preparing the environment before the server loads a package. |
Structural Constraints
|
In pipeline validation, structural constraints specify the existence and structure of variables at run time. In XML validation, structural constraints describe the structure and sequence of elements in the XML document. |
Structural Transformation |
A data transformation in which the value of the variable remains the same, but the data type or position of the variable in the record structure changes. |
Transformer |
A service you insert into a MAP step to accomplish a value transformation. Any service can be inserted as a transformer. By inserting transformers into a MAP step, you can accomplish your end-to-end mapping in a single view. |
Validation |
The process of verifying the structure and/or content of an object by matching it against a model or blueprint. If the object does not conform to the model or blue print, it is invalid. See also Input/Output Validation, Pipeline Validation, Record Validation, and XML Validation. |
Value Transformation
|
A data transformation in which the name and position of the variable remain the same, but the data contained in the variable changes. (For example, you can change the format of a date, concatenate two strings, or add the values of two variables together.) |
Values object |
In earlier versions of the webMethods Integration Server (prior to 3.5), the universal container that services use to receive input from and deliver output to programs that invoke it. The Values object is an ordered hash table that contains the individual data elements upon which a service operates. It can contain any number of elements of any valid Java data type, including additional Values objects. |
webMethods Developer |
A development environment for creating, maintaining, publishing and testing services. |
webMethods Integration Server |
A secure, high-performance deployment environment that allows the automated exchange of data between applications, Web sites, and other data sources. |
WebTap Service |
A feature of the webMethods Integration Server that provides control of an end-users browser experience while allowing services to intercept and modify data that passes through the webMethods Integration Server. Web tap "triggers" can intercept Web transactions and substitute local logic and/or pages for what would otherwise be performed by the third-party site. |
WQL |
webMethods Query Language (formerly, WOM). A language used to retrieve information from an HTML or XML document. See also, XQL. |
XML |
EXtensible Markup Language, a uniform method for describing and exchanging data that is flexible, extensible, and easy to implement. It is a simplified dialect of the Standard Generalized Markup Language (SGML). |
XML/EDI |
EDI semantics in XML syntax. The international EDI community is transitioning from EDIFACT EDI to XML. |
XML-Encoded Remote Procedure Call (XML-RPC) |
Allows XML DTDs to describe both the inputs and outputs to a service, and also the message format for the data that is sent to and returned from the webMethods Integration server. XML-RPC is implemented on top of standard Web protocols, specifically HTTP, SSL, and X.509, and is used for thin clients to access the webMethods Integration Server. |
XML Schema |
A model or description of the structure of an XML document. XML Schema is defined in the W3C's XML Schema Working Group Working Draft published on May 6, 1999. In the webMethods Integration Server, you can create schemas from XML Schema definitions. See also, schema. |
The process of verifying the structure and content of an XML document by making sure the document conforms to a schema. See also, schema. | |
XQL |
XML Query Language. A language used to retrieve information from an XML document. See also, WQL. |