How the SSSP application is accessed

Figure 6

Accessing the SSSP application in an on-demand scenario

How it works

1	In a user interface in the hosting system, an end-user opens a list. A request is sent to the runtime repository via the SSSP application and the service gateway. All available Ad-hoc-enabled document definitions are returned and presented in the list.

2	In the user interface, the end-user then 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.

3	An HTTP POST request, including the document definition ID and the data source, is sent to the SSSP application. The request is passed via the service gateway to the runtime repository.

4	In the Message storage in the runtime repository, a paused Message is created from the document definition ID and the data source. The Message is associated with a Message ID.

5	The Message ID is returned to the hosting system via the service gateway and the SSSP application. The Message ID is then used when accessing the corresponding document in Ad Hoc Correspondence. See Accessing Ad Hoc Correspondence.