Glossary terms for B2B Integrator.

A

A2A

See application to application.
See anything to anything.

accumulator

A function that counts the occurrences of a field or generates increasing, sequential record, or line item numbers.

activity

An action designed to achieve a particular business process. An activity is performed on a set of targets on a specific schedule.

adapter

An intermediary software component that allows two other software components to communicate with one another.

Advanced File Transfer (AFT)

A centralized, dynamic file-exchange platform for secure transfer of files within and between organizations. It provides end-to-end visibility of file movement in an event-driven, process-oriented, highly scalable SOA framework.

AFT

See Advanced File Transfer.

AFT community

An organization of protocols and options that are available to member AFT partners.

AFT Partner

An individual profile that belongs to a community, with selected options within the structure of the community.

all activity

An activity that contains two or more complex child activities and executes each of them simultaneously.

American Standard Code for Information Interchange (ASCII)

A standard code used for information exchange among data processing systems, data communication systems, and associated equipment. ASCII uses a coded character set consisting of 7-bit coded characters.

anything to anything (A2A)

A data transformation from any data format to any other data format.

Applicability Statement 1 (AS1)

An EDI protocol for securely exchanging data over the Internet, by using SMTP as a transport mechanism.

Applicability Statement 2 (AS2)

An EDI protocol for securely exchanging data over the Internet, by using HTTP as a transport.

application adapter

An adapter that integrates external business applications with Sterling B2B Integrator.

application file format

See positional data format.

application server

A server program in a distributed network that provides the execution environment for an application program.

application to application (A2A)

A data transformation from the output of one application to the input of another application.

approver relationship

An association between a category manager's user profile and a specific item number or category.

AS1

See Applicability Statement 1.

AS2

See Applicability Statement 2.

ASCII

See American Standard Code for Information Interchange.

attachment

A file that is attached to an email message or other electronic document.

attribute

Descriptive information that provides important details about a module, requirement, discussion, or element.

attribute container

An item that contains the attributes of an XML element.

attribute container object

A repository that is automatically created when the first attribute of an XML element is created. Sterling B2B Integrator uses attribute container objects to contain the attributes of an XML element. Attribute containers do not have properties.

attribute object

A characteristic that specifies the information associated with a particular element.

authentication

In computer security, verification of the identity of a user or process and the construction of a data structure that contains the privileges that were granted to the user or process.

authority-signed certificate

A certificate that is signed using a key maintained by a certificate authority. Before issuing a certificate, the certificate authority evaluates a certificate requestor to determine that the requestor is the certificate holder referenced in the certificate.

B

B2B standards services: A set of services that implement interoperable Internet business sequencing protocols, such as EDIINT, SOAP, RosettaNet RNIF, and ebXML.
BAPI: See Business Application Programming Interface.
base envelope: An envelope that is used to create a new envelope with the same properties. If the base envelope is modified, all related envelopes will also change.
base href: A URL that indicates to Sterling B2B Integrator where to find image files or style sheets to use with a web template if the HTML code uses relative paths.
base identity: An identity that can be used to create a new identity.
binding: An association between a client, object, and network that shares information about the transport protocol.
BPEL: See Business Process Execution Language.
BPML: See Business Process Modeling Language.
BPML activity: A step in a business process that provides directions for how data should be handled.
BPSS: See Business Process Specification Schema.
business analyst: 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 Application Programming Interface (BAPI): A programming interface that is used to access SAP databases from with SAP or other development platforms. BAPI is used to achieve integration between the R/3 System and external applications and legacy systems.
business 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 context: A state of a business process at a particular point in a business process. The business process context is modified as the business process moves from activity to activity.
business process editor: A facility in Sterling B2B Integrator that is used to create, modify, or delete a business 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 instance: A business activity performed on a set of targets, on a specific schedule, within a business process model.
business process model: An automated business process that uses drag-and-drop technologies to link activities in a digital, graphical representation of the related task.
Business Process Modeling Language (BPML): An XML-based language that describes business processes designed by the Business Process Management Initiative (www.bpmi.org).
Business Process Specification Schema (BPSS): A specification that enables Sterling B2B Integrator to define business processes according to a trading partner agreement.
business process version: An iteration of a business process that is checked in to Sterling B2B Integrator.

C

CA: See certificate authority.
CA certificate: See certificate authority certificate.
CA-signed certificate: A certificate that is signed using a key maintained by a certificate authority. Before issuing a certificate, the certificate authority evaluates a certificate requestor to determine that the requestor is the certificate holder referenced in the certificate.
category: A set of catalog items in a number of different hierarchical and searchable groupings.
Center for the Information of Industry data format (CII data format): Data format that provides the Japanese syntax definition for EDI messages within Sterling B2B Integrator.
certificate: A digital document that binds a public key to the identity of the certificate owner, thereby enabling the certificate owner to be authenticated. A certificate is issued by a certificate authority and is digitally signed by that authority. See also certificate authority, certificate signing request.
certificate authority (CA): A trusted third-party organization or company that issues the digital certificates. The certificate authority typically verifies the identity of the individuals who are granted the unique certificate. See also certificate, Secure Sockets Layer.
certificate authority certificate (CA certificate): A digital certificate that is issued by a certificate authority. The CA verifies trusted certificates for trusted roots.
certificate signing request (CSR): An electronic message that an organization sends to a certificate authority (CA) to obtain a certificate. The request includes a public key and is signed with a private key; the CA returns the certificate after signing with its own private key. See also certificate.
character set: A list of characters (letters, numbers, and symbols such as #, $, and &) that are recognized by computer hardware and software.
choice activity: One of three types of complex BPML activities. A choice activity is used to make decisions in the business process model and runs only one of the child activities it contains. The choice activity makes it possible to model branch processing.
chunk: A group of archived business processes.
CII data format: See Center for the Information of Industry data format.
CII root element: A representation of the CII document that Sterling B2B Integrator is mapping. The CII root element is a group and can contain groups and segments.
cluster: Two or more connected copies of Sterling B2B Integrator that share a database.
code list: One or many dynamic pairs of code values that contains sender code and receiver code. Each code pair has one description and up to four additional codes relating to the pair.
code list table: A repository for lists of codes that can further define fields.
command: A statement used to initiate an action or start a service. A command consists of the command name abbreviation, and its parameters and flags if applicable.
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.
communications adapter: An adapter that performs activities that control the transmission of business process data between Sterling B2B Integrator and external applications.
community: A collection or grouping of trading partners for the purpose of achieving a common goal.
compiled map: A source map that has been compiled to provide instructions for translating from one format to another in a way that can be interpreted by the translator.
complex activity: A step in a business process that provides direction for how the next step should be executed. There are three kinds of complex activities: sequence (serial), choice (conditional), and all (parallel).
composite: A group of related data elements used in EDI transactions.
configurable service: A service that requires the specification of parameters (other than a name and description), before they are ready to be used in a business process.
constant: Data that has an unchanging, predefined value to be used in processing.
constant standard rule: A rule that enables the user to move a constant value to the specified field, indicate a qualifying relationship with another field, and map the current date or time to the specified field.
consumer: An entity that receives data from another entity.
content particle: An element type that defines a choice, sequence, or activity. A content particle can only contain one pcdata. These objects can repeat in sequence until the content particle data ends or the maximum number of times the loop is allowed to repeat is exhausted. A content particle can not be referenced by standard rules or links.
contract: An agreement that establishes the business and technology terms and conditions that two trading partners have agreed upon to conduct business transactions. A contract consists of a production profile (identifies the document sender), a consumption profile (identifies the document receiver), and business process information.
control number: An incrementing number in an EDI envelope.
CORBA: See Common Object Request Broker Architecture.
correlation: Data that enables a user to record document-specific correlation parameters generated during translation, by the correlation service, or by document tracking functions.
CSR: See certificate signing request.
cursor operation record: A record that contains instructions for the translator on moving through the result set returned by a query to a new record. Each operation record is associated with a single SQL statement record that returns a result set. The translator performs cursor operations as it encounters them while processing the map.
custom adapter: An adapter that is created by users or consultants and is not shipped with Sterling B2B Integrator. Custom adapters can integrate custom applications and legacy systems with Sterling B2B Integrator.

D

data attribute: A specific piece of descriptive information about an object (item) or organization. Examples of item data attributes include product number, product description, product price, and company name.
data definition format (DDF): An IBM format that contains an XML-formatted description of the input or output side of a map.
Data Manipulation Language: A subset of SQL statements that is used to manipulate data. Most applications primarily use DML.
Data Universal Numbering System (DUNS): A system in which internationally recognized nine-digit numbers are assigned and maintained by Dun & Bradstreet to uniquely identify worldwide businesses.
Data Universal Numbering System number (DUNS number): A unique, nine-digit company identification number issued by Dun & Bradstreet Corporation.
data visualization: A visual display of relationships in multidimensional data that enables analysis.
DBCS: See double-byte character set.
DDF: See data definition format.
dead-letter mailbox: A mailbox that stores messages that cannot be added to a particular mailbox. The primary role of this mailbox is to provide temporary data storage until the administrator can correct the problem.
decision point: An intersection in a business process that determines the next step in the business process. A decision point is much like an if/then statement, in which the answer determines the next action.
decryption: In computer security, the process of transforming encoded text or ciphertext into plaintext.
de-enveloping: The process of removing one or more envelopes from a document or a set of documents.
default envelope: A version of the document envelope that is used by Sterling B2B Integrator.
default version: A copy of a resource, such as a service configuration, saved in Sterling B2B Integrator that the system uses for processing unless otherwise specified.
delimiter: A flag that is formed by a character or a sequence of characters to group or separate items of data by marking the beginning and end of a unit of data. The delimiter is not a part of the flagged unit of data.
delivery channel: A trading partner set-up that links a document exchange record and a transport record.
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.
digest: Data that has been organized into a format that provides for quick access to each piece of data.
digital certificate: An electronic document used to identify an individual, a system, a server, a company, or some other entity, and to associate a public key with the entity. A digital certificate is issued by a certification authority and is digitally signed by that authority.
digital signature: Information that is encrypted with a private key and is appended to a message or object to assure the recipient of the authenticity and integrity of the message or object. The digital signature proves that the message or object was signed by the entity that owns, or has access to, the private key or shared-secret symmetric key.
DMZ: See demilitarized zone.
document envelope: A structure that is applied to a document to prepare it for exchange between trading partners.
document exchange record: A record that describes properties of the documents and messages passed between trading partners.
document type definition (DTD): The rules that specify the structure for a particular class of SGML or XML documents. The DTD defines the structure with elements, attributes, and notations, and it establishes constraints for how each element, attribute, and notation can be used within the particular class of documents.
double-byte character set (DBCS): A set of characters in which each character is represented by 2 bytes. These character sets are commonly used by national languages, such as Japanese and Chinese, that have more symbols than can be represented by a single byte.
DTD: See document type definition.
DUNS: See Data Universal Numbering System.
DUNS number: See Data Universal Numbering System number.

E

EAI: See enterprise application integration.
ebXML: See electronic business Extensible Markup Language.
EDIINT: See Electronic Data Interchange-Internet Integration.
EDI root element: A representation of the EDI document that Sterling B2B Integrator is mapping. At the EDI root element, delimiters and syntax records can be defined. It is a group and can contain groups and segments.
EDI service: A service that is related to the transaction processing requirements for EDI transactions, including deenveloping, enveloping, and functional acknowledgement generation.
effective change date: The date on which an approved change to an item in the pending catalog becomes valid.
e-invoice: An electronic bill for services or products provided to a customer.
EJB: See Enterprise JavaBeans.
electronic business Extensible Markup Language (ebXML): A set of specifications that enables enterprises to conduct business through the exchange of XML-based messages. ebXML is a joint initiative ofUN/CEFACT and OASIS.
Electronic Data Interchange-Internet Integration (EDIINT): A set of protocols for exchanging EDI and other business documents over the Internet. EDIINT was developed by the Internet Engineering Task Force (IETF).
element: The smallest unit in a table, array, list, set, or other structure. Examples of an element are a value in a list of values and a data field in an array.
encoding: A representation of data in a specific character set recognized by computer hardware and software.
endpoint: The origin or destination of a file transfer within Sterling B2B Integrator.
enterprise application integration (EAI): A technology that serves as the common interface between dissimilar applications using the same data and processes.
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 resource planning (ERP): The planning and management of all the resources in an enterprise.
envelope: A pair of segments that define or enclose an electronic transaction.
ERP: See enterprise resource planning.
execution control keyword: A keyword that controls the flow of execution of the defined rule. These keywords evaluate conditions and perform looping operations.
expression: In programming languages, a combination of terms and operators that can be evaluated to a single value by using the rules of precedence for the given language.
expression language: A computer language that is used in JSTL to express simple expressions. EL is based on the XPath and JavaScriptor JScript languages.
extended rule: A rule that defines complex translations and consists of declaration and statement sections.
Extensible Markup Language (XML): A standard metalanguage for defining markup languages that is based on Standard Generalized Markup Language (SGML).
extractability: A Sterling B2B Integrator Mailbox concept that determines whether a message that resides in a mailbox can be extracted from the mailbox by a business process or the Mailbox Browser interface (MBI).

F

field: In a database, a portion (as defined during the database description generation process DBDGEN) within a segment that is the smallest unit of the data that can be referred to.
file upload utility: A Web Extensions utility that can be used to define business process files that require mapping from one data format to another. By default, the utility is configured to map positional data to XML data.
fixed format: See positional data format.
functional group: One or more documents of a similar type transmitted from the same location and enclosed by functional group header and trailer segments.

G

GCI

See Global Commerce Initiative.

Global Commerce Initiative (GCI)

A voluntary body that was created in October 1999 to improve the performance of the international supply chain for consumer goods through the collaborative development and endorsement of recommended standards and important business processes.

GPM

See Graphical Process Modeler.

Graphical Process Modeler (GPM)

A stand-alone graphical interface tool that is used in Sterling B2B Integrator to create and modify business processes. The GPM converts the graphical representation of business processes to well-formed BPML (source code) and saves the effort of writing code.

group

In B2B Integration role-based security, a set of access permissions for multiple users that can be managed from a central location.
In EDI, a looping structure that contains related items, which repeat in sequence either until the translation service has processed all the data in the group or it has repeated the loop the maximum number of times allowed.

H

hard stop: A function that halts the system without waiting for a business process to finish. Hard stops may result in loss of data in unfinished processes.
human interaction: Any action taken by a human being on a business process as it executes.
human interaction service: A service that enables human interaction with business processes as they execute.

I

identity

A representation of a trading partner that describes and contains information referenced when a business process involving the trading partner is run. A trading partner can have more than one identity to represent the different ways it performs an operation.

IETF

See Internet Engineering Task Force.

inbound envelope

An EDI structure that identifies an inbound document within Sterling Integrator so that it can be sent and received by trading partners.

initiator

An AFT partner that takes the first action in a file transfer, initiating activity.

input record

A record that contains a logical group of fields that can be mapped to the output format. The input record is allowed only on the input side of the map and cannot be referenced by standard rules or links.

input service

A service that receives data from external systems.

integer

A positive or negative whole number, or zero.
See N-formatted number.

integration engine

An application that transmits business data in Sterling B2B Integrator to support data management, translation, transformation, and routing services.

interchange

The exchange of information between trading partners. Also a set of documents grouped together, such as EDI documents enclosed within an EDI envelope.

internal service

A service that runs solely inside Sterling B2B Integrator to support the general runtime environment. Although internal services accept parameters and produce results, they do not interact directly with external systems.

Internet Engineering Task Force (IETF)

The task force of the Internet Architecture Board (IAB) that is responsible for solving the short-term engineering needs of the Internet. The IETF consists of numerous working groups, each focused on a particular problem. Specifications proposed as standards typically undergo a period of development and review before they are adopted as standards.

J

Java: An object-oriented programming language for portable interpretive code that supports interaction among remote objects.
Java Cryptography Extension (JCE): A framework and implementations for encryption, key generation and key agreement, and message authentication code (MAC) algorithms.
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 EE: See Java Platform, Enterprise Edition.
Java Message Service (JMS): An application programming interface that provides Java language functions for handling messages.
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 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.
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 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.
JavaServer Pages Standard Tag Library (JSTL): A standard tag library that provides support for common, structural tasks, such as: iteration and conditionals, processing XML documents, internationalization, and database access using the Structured Query Language (SQL). (Sun)
Java virtual machine (JVM): A software implementation of a processor that runs compiled Java code (applets and applications).
Java Web Start: A tool that assists the development of client-side Java applications and enables a web server to independently distribute and update client code.
JCE: See Java Cryptography Extension.
JDBC: See Java Database Connectivity.
JMS: See Java Message Service.
join: To combine two or more business processes or subprocesses to form one business process.
JRE: See Java runtime environment.
JSP: See JavaServer Pages.
JSP container: An entity that provides lifecycle management and runtime services to the components of a web application.
JSSE: See Java Secure Socket Extension.
JSTL: See JavaServer Pages Standard Tag Library.
JSTL namespace: A unique identifier that defines the URI of the tag library and the prefix used in the tags for that specific functional area library.
JVM: See Java virtual machine.

K

key: A cryptographic mathematical value that is used to digitally sign, verify, encrypt, or decrypt a message.
key certificate: A combination of an ASCII-encoded certificate and an ASCII-encoded PKCS5 encrypted private key.
key certificate file: A file that is stored on the client system that contains an encrypted message to identify the client and enable client/server authentication during secure connections.
keyword: One of the predefined words of a programming language, artificial language, application, or command.

L

license: A legal agreement that authorizes the use of proprietary information including, but not limited to, copyrighted or patented information.
lifecycle record: A database record that contains tracking information about data processing performed by the data manager.
listener: A program that detects incoming requests and starts the associated channel.
log file: The file where the log of events is recorded.
Loop Count standard rule: A rule that enables a user to count the number of times a loop is repeated if the field is part of a loop.

M

mailbox: A storage location in a network to which messages for a user are sent.
Mailbox Browser Interface (MBI): A secure web access application that allows trading partners to interact with the Sterling B2B Integrator Mailbox.
map: A translation description that is created, modified, and compiled by the Sterling B2B Integrator Map Editor. A map is used by the Translation service to translate data from one format to another.
mapping link: A visual line that connects the fields on the input side of a map to mapped fields on the output side of a map.
MBI: See Mailbox Browser Interface.
MDN: See Message Disposition Notification.
Message Disposition Notification (MDN): A receipt document that contains the message ID and status information from the original message. See also receipt.
messaging adapter: An adapter that enables Sterling B2B Integrator to send messages to and from remote messaging queues.
MIME: See Multipurpose Internet Mail Extensions.
mined data: Data that is pulled from a business process and written to an internal database.
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

NAT: See network address translation.
network address translation (NAT): In a firewall, the conversion of secure Internet Protocol (IP) addresses to external registered addresses. This enables communications with external networks but masks the IP addresses that are used inside the firewall.
N-formatted number: A number that has an implied decimal point. For example, 2.01 is formatted as 201.
node: In communications, an end point of a communication link or a junction common to two or more links in a network. Nodes can be processors, communication controllers, cluster controllers, terminals, or workstations. Nodes can vary in routing and other functional capabilities.
nonversioned resource: A resource, such as user accounts, for which only one current copy is saved in Sterling B2B Integrator at any time. When a non-versioned resource is modified, the new data replaces the old data in the system.

O

Open Secure Shell (OpenSSH): A set of open-source programs that implement the SSH protocol.
OpenSSH: See Open Secure Shell.
operation: A business process that invokes action against a participant. When an operation is invoked, it delivers a request message and waits for a response. If a fault is communicated, the operation fails.
operation activity: An activity that invokes an action against a participant. An operation involves a synchronous request/response message exchange with a possible fault message. When an operation is invoked, it delivers a request message and waits for a response message. If a fault is communicated, the operation faults.
operator: A symbol (such as +, -, or *) that represents an operation (in this case, addition, subtraction, multiplication).
outbound envelope: An EDI structure that identifies an outbound document within Sterling Integrator so that it can be sent and received by trading partners.
output record: A record that represents UPDATE, INSERT, or DELETE SQL statements, and contains database output fields. Output record fields represent the columns Sterling B2B Integrator is updating or inserting and the key to the affected row or rows. Output records can be created on both the input and output sides of a map and cannot be referenced by standard rules or links.
output service: A service that sends data to external systems.

P

packaging record: A record that describes the organization of the message, including its header or envelope, which contains metadata identifying the messages, and its body or payload, which contains the business content of the message. A packaging record includes details about protocol-specific security, as well as envelope fields like a MIME content type or an XML namespace.
parsed character data (pcdata): A data definition that produces clear text output of character data. Because it is parsed, it does not include any markup in the output.
participant: An entity that is outside a given business process. In Sterling B2B Integrator, a participant is recognized only when it is used in an operation activity.
payload data: User content that is stored from a data transfer. Data includes overhead and user information.
pcdata: See parsed character data.
perimeter server: Communication management software that can be installed in a DMZ and manages communication flows between a perimeter network and Sterling B2B Integrator TCP-based transport adapters.
perimeter service: A service that supports multihoming and secure perimeter network traversing for Sterling B2B Integrator communication protocols.
permission: The ability to access a protected object, such as a file or directory. The number and meaning of permissions for an object are defined by the access control list.
persistence level: A level that determines the degree of detail written to the database as a business process runs. Decreasing the persistence level increases the business process performance at the cost of full tracking for each step of the business process.
polled methodology: An internal process that uses a time interval to establish when to query the queue manager for data.
positional data format: A fixed data format that uses characteristics of a file such as delimiters or record length.
positional root element: An element that represents a positional document that Sterling B2B Integrator is mapping. A positional root element is a group and can contain groups and records.
post-session rule: A rule that is executed after the translation object is completely processed and has no permanent scope.
predefined business process: A business process that is ready to use upon installation of Sterling B2B Integrator.
prefix: A unique identifier that defines the functional area that a tag belongs to. The prefix is defined in the JSTL Namespace. For example, prefix=”c” means that all tags that start with c: are part of the core functional area tag library. The c in c: is the prefix of the tag.
Present Working Directory (PWD): The directory that is currently active in a transaction.
pre-session extended rule: A rule that defines variables that have global scope. Pre-session rules are processed before the translation object is processed, and apply to every extended rule defined in the map.
pre-session rule: A rule that defines variables that have global scope (can be accessed from any other extended rule in the map). Pre-session extended rules are processed before the translation object is processed, and apply to every extended rule defined in the map.
primary document: A document that the services in a business process act on or in relation to. A primary document is usually the document passed to a business process by the initiating adapter.
private key: The secret half of a cryptographic key pair that is used with a public key algorithm. The private key is known only to its owner. Private keys are typically used to digitally sign data and to decrypt data that has been encrypted with the corresponding public key. See also public key.
process automation: The act of running each step of a business process with little or no user intervention.
process branching: A protocol that evaluates one or more rules to reach a decision and then specifies which activity to execute as a result of that decision.
process data: Data that is accumulated in an XML document about a business process during the life of the process. Activities in the process add elements to the process data and use components of the process data to complete configured processing tasks.
process element: An element that defines an activity and is the basic element of a business process model.
producer: An entity that transmits data to another entity. For example, a join thread that receives data from a scan thread is considered a consumer; in this case the scan thread is considered a producer.
profile record: A record that links a trading partner's delivery channel and packaging record to a business process.
protocol server: A computer or device on a network that is dedicated to the management of communications protocol resources.
public key: The non-secret half of a cryptographic key pair that is used with a public key algorithm. The public key is made available to everyone. Public keys are typically used to verify digital signatures and to encrypt data that can be decrypted only with the corresponding private key. See also private 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.
PWD: See Present Working Directory.

Q

qualifier: A simple element that gives another generic compound or simple element a specific meaning. Qualifiers are used in mapping single or multiple occurrences. A qualifier can also be used to denote the namespace used to interpret the second part of the name, typically referred to as the ID.
queue: A line or list of items waiting to be processed, for example, work to be performed or messages to be displayed or transmitted.

R

RDN: See relative distinguished name.
real number: See R-formatted number.
receipt: An electronic document that verifies or acknowledges a trading partner agreement. See also Message Disposition Notification.
relationship-dependent master data: Master data that concerns all terms that are communicated between trading partners, like marketing conditions, prices and discounts, and logistics agreements.
relative distinguished name (RDN): An entity that builds the CA certificate name.
Remote Procedure Call (RPC): A protocol that allows a program on a client computer to run a program on a server.
resource: 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.
resource tag: A name that is used to assign a group of resources to another group for quickly gathering an export package, such as moving a group of resources from one instance to another.
R-formatted number: A number that has an explicit decimal point and truncates trailing zeros. For example, 2.01 is formatted as 2.01.
role-based security: Security that provides access rights to certain files, business processes, web templates, and features, according to the permissions associated with the user account.
rollback segment: A function that enables a user to undo DML (data manipulation language) transactions that were performed against a database.
root element: An element that represents the document/transaction that Sterling B2B Integrator is mapping. The root element defines the characteristics of the file, such as delimiters or record length. The root element is a group and can contain groups and records.
router: In Sterling B2B Integrator, the Advanced File Transfer routing capability.
routing rule: A rule that enables Sterling B2B Integrator Mailbox to take automatic action when a message is added to a mailbox, such as notifying a business process to process the message.
RPC: See Remote Procedure Call.

S

SA: See system administrator.
scope: The range of context in a map for which a variable name, identifier, or declaration is valid or can be used.
SCP: See secure copy program.
SDK: See software development kit.
secure copy program (SCP): See secure shell/secure copy program.
Secure FTP: An FTP protocol that uses Secure Sockets Layer (SSL) protocol.
secure shell/secure copy program (SSH/SCP): A program that copies files between hosts on a network. It requests passwords or pass phrases if needed for authentication.
secure shell/Secure File Transport Protocol (SSH/SFTP): An interactive file transfer protocol that performs all operations over an encrypted SSH transport.
Secure Sockets Layer (SSL): A security protocol that provides communication privacy. With SSL, client/server applications can communicate in a way that is designed to prevent eavesdropping, tampering, and message forgery. See also certificate authority.
segment: An EDI logical unit of information. EDI segments are made up of data elements and composites. Segments are delimited; their components are separated by a delimiter.
self-signed certificate: In cryptography, a public key certificate that is signed with its own private key rather than by a certificate authority.
sequence activity: One of three types of complex BPML activities that executes a series of child activities in the order in which they are listed.
service: A set of business processes (such as web transactions) that represent business-critical functions that are made available over the internet.
service configuration: A set of runtime parameters that is specified for a particular service type.
service instance: A particular invocation of a service configuration.
service level agreement (SLA): A contract between a customer and a service provider that specifies the expectations for the level of service with respect to availability, performance, and other measurable objectives.
service-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 type: A component that contains code that is used to do work when executed in a business process.
signed security token: A token that is cryptographically endorsed by a specific authority, such as an X/509 certificate.
simple activity: In Business Process Modeling Language (BPML), a single step in a business process.
SLA: See service level agreement.
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.
soft stop: A function that halts the system after all the business processes finish running.
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.
source map: A source file that contains graphical mapping instructions for translation.
spawn: A function in which a calling process (the parent process) creates a new process called a child process. The child process inherits attributes from the parent process. A new program is specified and starts running in the child process.
split: The separation of a business process into one or more business processes or subprocesses to run simultaneously.
SQL: See Structured Query Language.
SQL root element: An element that represents the SQL data sources that Sterling B2B Integrator uses during translation. The SQL root element is a looping structure that contains groups, SQL statements, cursor operations, and input and output records that repeat in sequence until either the group data ends or the maximum number of times that the loop is allowed to repeat is exhausted. The SQL root element cannot be referenced by standard rules or links.
SSH/SCP: See secure shell/secure copy program.
SSH/SFTP: See secure shell/Secure File Transport Protocol.
SSL: See Secure Sockets Layer.
standard rule: A rule that allows access to functions necessary for mapping operations more complex than simple linking but less complex than extended rules. Standard rules are mutually exclusive (only one can be used on a particular field).
statement record: A unit of SQL that includes an SQL query (which may or may not return a result set), a command (which does not return a result set), or a stored procedure invocation (which may or may not return a result set). Each statement record is associated with a single data source.
stencil element: A labeled icon that represents services and BPML activities in the Graphic Process Modeler.
string field: A field that can contain one or more printable characters.
Structured Query Language (SQL): A standardized language for defining and manipulating data in a relational database.
subflow: A sequence of processing steps, implemented using message flow nodes, that is designed to be embedded in a message flow or in another subflow. A subflow must include at least one Input or Output node. A subflow can be executed by a broker only as part of the message flow in which it is embedded, and therefore it cannot be deployed.
subgroup: A group that is subordinate to another group. A subgroup corresponds to a nested looping structure, a loop within a loop.
subprocess: An independent process that is part of another business process.
syntax token: A data subtype that applies only to string fields and can contain one or more character ranges and single characters, such as $, Z or@.
system administrator (SA): The person who controls and manages a computer system.
system certificate: A digital certificate for which a user has the private key.
system passphrase: Encryption data that protects cryptographic keys and cannot be changed without reinitializing the database.
system service: An internal service that runs solely inside Sterling B2B Integrator without interacting with external systems.
System Variable standard rule: A rule that enables a variable to map the current date and time to the selected field.

T

tag handler: An explanation of how to process a tag when it is encountered in the processing of the JSP web template.
tag library descriptor: An XML file that describes a tag library and contains the tags in the library. Each functional area has a .tld file.
TFD: See transfer form data.
third-party certificate: A digital certificate that identifies an organization other than those preconfigured for the system.
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.
trading partner: A company, such as a manufacturer or a supplier, that agrees to exchange information using electronic data interchange, or an entity in an organization that sends and receives documents that are translated.
trading profile: A profile that describes the technology and business capabilities of the trading partner that enable the partner to engage in electronic business with other trading partners. The profile links the trading partner with business processes to exchange documents with other partners.
transaction set: The basic business document in EDI data. Transaction sets are enclosed in an envelope that separates one transaction set from another. Groups of transaction sets that are functionally related are enclosed in a functional group envelope.
transfer form data (TFD): A block of data in CII data format that consists of a tag, a length indicator, and data.
translation object: A source map that has been compiled to provide instructions for translating from one format to another in a way that can be interpreted by the translator.
translation service: A service that transforms data from one format to another using maps created with the Sterling B2B Integrator Map Editor.
translator: An engine that translates data.
transport: The process or protocol mechanism of transferring an XML message or document between parties as part of a meaningful, reliable exchange. The most common transports for web services are SOAP/HTTP, SOAP/HTTPs, and SOAP/JMS.
transport record: A record that describes the document delivery protocol. It identifies the protocol, such as HTTP, FTP, or SMTP. It also details the use of the protocol, such as HTTP configured with SSL for secure data exchange.
transport service: A service that implements interoperable Internet business sequencing protocols such as EDIINT, SOAP, RosettaNet RNIF, and ebXML.
trusted certificate: A certificate that is purchased from and issued by a Certificate Authority (CA).
trusted root: The foundation upon which chains of trust are built in certificates. Trusting a CA root means that all certificates issued by that CA can be trusted.
trusted root certificate file: A file stored in a local directory on a client system that contains a list of trusted sources. During communications connections, the client compares the server certificate to the trusted root certificate file to determine whether the server certificate was signed by a trusted source. The client can establish a secure communications connection if a trusted source signed the server certificate.
tunnelling: The process of treating a transport network as though it were a single communication link or local area network (LAN).

U

UDDI: See Universal Description, Discovery, and Integration.
Unicode: A character encoding standard that supports the interchange, processing, and display of text that is written in the common languages around the world, plus many classical and historical texts.
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.
Uniform Resource Indicator
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.
Unlimited Strength Policy File: See Java Cryptography Extension.
unsigned security token: An authentication specification used to verify the recipient of the message containing the token. Unsigned tokens often consist of login credentials supplied by the service requestor, for example, a user name token.
URI: See Uniform Resource Identifier.
user account: The login directory and other information that gives a user access to the system.
user exit: An extended rule that enables a map to temporarily exit translation and perform functions that are not normally performed during translation.
UTF-8: Unicode Transformation Format, 8-bit encoding form, which is designed for ease of use with existing ASCII-based systems. The CCSID value for data in UTF-8 format is 1208.

V

value-added tax (VAT): A transactional consumption tax charged on most public and private consumption.
variable-length-delimited data format: A data format that enables delimited files, such as comma-separated variable (CSV) files, to be mapped.
variable-length-delimited root element: A root element that represents the variable-length-delimited document that Sterling B2B Integrator is mapping. The variable-length-delimited root element is a group and can contain groups and records.
VAT: See value-added tax.
VDA: See Verband der Automobilindustrie.
Verband der Automobilindustrie (VDA): A standard developed by the German Association of the Automotive Industry to ensure the integrity of products and processes are up to German manufacturing standards.
versioned resource: A resource, such as a business process model, for which multiple copies, or versions, are saved in the system. Each time a versioned resource is modified, the system saves the data as a new version so that old versions can be reverted to as needed.
version history: A record of modifications made to a web template. Each time a web template is edited, a new version is created, but the original web template remains intact for future use.
virtual root: A function that enables an administrator to associate a user ID with a mailbox so that the user can not see the hierarchy that embeds that mailbox.

W

WAR: See web archive.
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 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.
Web Extensions: A suite of utilities and services that enable human interaction within business processes as they are executed in Sterling B2B Integrator.
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 service: 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 group: A set of services, adapters, and business processes that will be published for a specific task, and generally for a specific consumer or subset of consumers.
web services consumer: A person or system who uses the web service.
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 provider: The author and originator of the web service being offered.
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.
web template: A set of markup tags that enable business process contexts to be displayed at any point in a business process. Web templates combines client- and server-side markup tags to enhance reusability.
wire format: A universal format, independent of hardware, operating system, and programming language architecture that provides a common language to connect diverse programs.
workbench: The user interface and integrated development environment (IDE) in Eclipse and Eclipse-based tools such as IBM Rational Application Developer.
worklist: The set of data change updates that is retrieved by a recipient.
workspace: An area into which elements can be dragged to build a business process model.
WSDL: See Web Services Description Language.
WSS: See Web Services Security.
WS-Security: See Web Services Security.

X

XML: See Extensible Markup Language.
XML encoder object: A compiled map that translates data from either the input or output side of a source map into XML. EDI, positional, and variable-length delimited data formats can be compiled into XML encoder objects.
XML namespace: A collection of names, identified by a Universal Resource Identifier (URI) reference, used in XML documents as element types and attribute names. An XML namespace allows a user to include multiple XML vocabularies in a single XML document without ambiguity of names.
XML resource bundle: A group of XML properties that is bound in a package for ease of deployment. There is a separate resource bundle for each language.
XML root element: The implicit highest-level node of a parsed XML document. It may not always be possible to predict which element will be the document element of a parsed instance, but it will always have a root node that can be used for preliminary or setup processing.
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.