Platform configuration

Preview output connector configuration

When displaying documents in web applications, preview output connectors are used. If certain prerequisites are fulfilled, you can use default preview connectors, which are automatically created and selected at preview service requests. If the prerequisites are not fulfilled, you must manually create and select the preview connectors.

Message storage configuration

Paused Messages are stored in the Message storage in the runtime repository. To enable use of this storage, you must make sure that input and output queues are used in the Design Center Project.

When a final document is distributed, the corresponding Message remains in the Message storage until an expiry time has elapsed. You enable and configure the expiry time in the Platform configuration.

Ad Hoc one to many

In an Ad Hoc one to many scenario, i.e. when an Ad Hoc document is sent to several recipients, document definitions are published via the publish REST method from the user interface in the hosting application. Document definitions published via the publish REST method will have an unpublish expiry time automatically set in order to maintain an optimal runtime environment.

Document definitions used in an Ad Hoc one to many scenario are invoked exclusively from the jobsubmit REST API via the hosting application. To be able to invoke document definitions using jobsubmit the corresponding StreamServer application must be exposed as a service via a Service Request input connector.

In this section

•	Using default preview output connectors

•	Configuring preview output connectors manually

•	Configuring input and output queues

•	Configuring an expiry time for documents