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.
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.
Here's what happens when an end user clicks a presentation link on the myAccess Links page:
|Presentation Builder Overview|
|Starting and Stopping Presentation Builder Runtime Service|
|Setting the Presentation Builder Runtime Service Location|
|Changing the MCS Server Information|
|Configuring Run-time Services|
|Configuring Run-time Event Logging|
|Monitoring Application Activity, Overview|