Concepts and glossary > Glossary

Glossary
 
A Document (capital D) is a grouping of documents per customer number, delivery address, etc.. The scope of the Document is specified using a Document trigger.
An Event defines how to identify documents in the input job, which parts of an input document to extract, and how to create a Message.
When you export a Project, you create an export file (*.export) that includes all the configuration files needed by the StreamServer application. The export file includes the configuration files for all Platform layers defined in the Project.
The generic Platform layer (also referred to as logical layer) includes settings that must be the same in all target environments.
A stream of data, with a distinct beginning and end, received via an input connector, and processed by the StreamServer.
A tree structure of tagged fields and blocks used internally by the StreamServer when transforming input documents into output documents.
Process for output data sent to a MesageIN Event. The MessageOUT Process makes it possible to extend the processing chain over multiple StreamServers.
An output job is equivalent to a file, created by the StreamServer, and delivered via an output connector to a target application (printer, fax, etc.). The scope of the output job is set by the output mode, and in some scenarios by using script functions (e.g. SetDestPath).
The output mode specifies how to group documents before they are delivered via the output connector to the target application.
In output mode Document, the output is delivered as Documents. This means the output connector waits until the Document is complete before it delivers the output.
In output mode Job, the output connector waits until the whole Runtime job is finished before it delivers the output.
In output mode Process, the output connector delivers the output as it arrives from a Process. This means each output document is delivered separately.
The Platform represents the StreamServer application to which the Project is deployed, and contains the environment settings for that StreamServer application.
A Process defines which fields and blocks in a Message to use, and how to organize the fields and blocks in the output documents.
Each Process type has its own Process tool (PageOUT, StreamOUT, XMLOUT, etc.) where the Process is configured.
The configuration used by a StreamServer application to collect, transform, and deliver data. In Design Center, you create and configure the Project. Then you export the Project, and deploy it to the appropriate StreamServer application.
All external files that you refer to when you configure a Project must be available to the Project as resources. A resource in this context is a file with an embedded source file.
StreamServer application
The StreamServer can run several StreamServer applications, where each StreamServer application is dedicated to a specific Design Center Project.
 
OpenText StreamServe 5.6 Updated: 2013-03-01