Configuring Launch Pages to Handle Context-Switching
You must configure the Openspace or Workspace launch page(s) to handle the different format of the URL that results from context-switching.
The load balancer may use context-switching (for example, to allow dynamic routing of endpoints) in the URL that it uses to access Openspace or Workspace.
For example:
loadbalancer:port/context/openspace
If multiple contexts are used, for example:
loadbalancer:port/context1/context2/openspace
Openspace and Workspace cannot by default resolve the URL properly to load the TIBCO Forms runtime and display a form.
To correct this, you must edit the appropriate Openspace or Workspace HTML launch page(s) to account for the different format of the URL.
Procedure
Example
If the URL used to access Openspace from the load balancer is:
loadbalancer:port/context1/context2/openspace
change the entry in the launch page to:
<script type="text/javascript" language="javascript" src="../../bpmresources/formsclient/formsclient.nocache.js"> </script>
loadbalancer:port/BPMclient
or
loadbalancer:port/context/BPMclient
For example, if the URL used to access Openspace from the load balancer is:
loadbalancer:port/openspace
or
loadbalancer:port/openspace.html
or
loadbalancer:port/context1/openspace.html
no additional configuration of launch pages is required.