Client-side integration focuses on the embedding the document production process in the flow of the BA Client. The exact way in which it can be achieved highly depends on the nature of the client application. In general, the following occurs:

• The BA Client requests the BA Server to prepare a Master Template run. This results in the creation of a session defining the Master Template run. The BA Server will responds with a URL, which contains the session identifier as a query string parameter.

• The BA Client opens this URL in a separate browser, in an iframe on a web page or in a browser component. This triggers an interactive Master Template run.

• As soon as the end user completes the Master Template run, the modelend page of the KCM ComposerUI application is opened. The particular implementation of this page determines what happens next. For example:

  • Opening the result document, so the end user can edit it.

  • Calling a service on KCM Core for further processing of the document. This can be done in combination with any of the other options.

  • Redirection to a page in the business application, putting the business application back in control, if the business application is web-based.

  • Redirection to a page with a specific name. The BA Client can detect that the Master Template run is finished, if the business application is a Windows application and the URL is loaded inside a browser control.

  • Simply closing the browser, if the URL is loaded inside a separate browser window.