Overview: Configuring the Run-time Environment

For most environments, configuration will consist only of installing the run-time component, Presentation Builder Runtime Service. This component handles all communication between your custom application and the host (or hosts) to which it connects. During installation, you configure the run-time by specifying the location of your Management & Control Services (MCS) server. End users may connect to MCS to get a list of presentations available to them, and to download the Presentation Renderer, but all host-to-client communication goes through Presentation Builder Runtime Service.

For typical installations of Presentation Builder, the default configuration will work well. However, for alternative installations, you may want to modify the way you configure the Presentation Builder Runtime Service. The flexibility to change your configuration is provided through a property file that you can easily edit.

How the Runtime Service Works

Installing Presentation Builder Runtime Service adds a servlet engine called HTTP Engine and sets it to run automatically. In the diagram below, the end user's screen is shown with the myAccess Links frame on the left, and a presentation running in the right frame.

Run-time diagram

Here's what happens when an end user clicks a presentation link on the myAccess Links page:

  1. Clicking the link on the myAccess Links page sends a request to MCS for the address of Presentation Builder Runtime Service.
  2. MCS sends the server name or IP address of Presentation Builder Runtime Service to the client.
  3. The client sends a request for the application to Presentation Builder Runtime Service.
  4. Presentation Builder Runtime Service checks with MCS to ensure that the client is authenticated.
  5. Presentation Builder Runtime Service gets the application from MCS (this occurs only when the number of clients of an application goes from zero to one, or if the application has been updated and republished).
  6. Presentation Builder Runtime Service sends the application's UI to the client (where it is cached).
  7. Now, MCS is out of the picture, and all host-to-client communication occurs through Presentation Builder Runtime Service.
Related Topics
Bullet Presentation Builder Overview
Bullet Starting and Stopping Presentation Builder Runtime Service
Bullet Setting the Presentation Builder Runtime Service Location
Bullet Changing the MCS Server Information
Bullet Configuring Run-time Services
Bullet Configuring Run-time Event Logging
Bullet Monitoring Application Activity, Overview