Accessing the SSSP application

On-demand scenario

In an on-demand scenario, a request sent to the SSSP application retrieves all Ad-hoc-enabled document definitions from the runtime repository. The document definitions are then listed in a user interface in the hosting application.

In the user interface, an end-user selects one of the document definitions and a data source. For example, a file with customer data including customer name, customer address and reference name. The document definition and the data source are included in an HTTP POST request that is sent to the SSSP application. A new Message is created in the Message storage in the runtime repository and a Message ID is returned.

The Message ID will be used later, when accessing the corresponding document in Ad Hoc Correspondence.

Batch scenario

In a batch scenario, the SSSP application is accessed from the Ad Hoc or the Reviewer application. The URL to the SSSP application is set in the property files for the applications, see Customizing the applications.

No further configuration to access the SSSP application is required for the batch scenario.

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. These document definitions will not be classified as Batch or Batch and Ad Hoc document definitions, and will therefore not be available for management or editing in Composition Center.

Related topics

See the programming guide for the REST Service API included in the OpenText StreamServe web service SDK (Software Development Kit) for information on how to:

•	Retrieve Ad-hoc-enabled document definitions from the runtime repository and list them in the user interface of the hosting system.

•	Develop the HTTP POST request that triggers the creation of a Message in the Message storage based on a selected document definition and a selected data source.