Use this configuration option to choose the PC program that starts PC commands. Starting with Profound UI Version 5, Fix Pack 13.0, this configuration option overrides pui["use pc listener"] and pui["pc listener mode"].
The option expects string values:
- "listener_m2" - Profound UI uses the PC Command Listener in Mode 2, which makes the listener work on HTTPS (SSL) pages as well as HTTP pages. The listener port must also be setup. Set this value when Profound is running on the secure HTTP protocol and the listener is the preferred mode.
- "listener_m2s" - Same as "listener_m2", except the server will attempt to sign the command using public key cryptography to ensure that PC commands come from a trusted source. Keys must be configured on the server and PC Listener client.
- "listener_m1" - Profound UI uses the PC Command Listener. The listener port must also be setup. (A value of "listener" is an alias for "listener_m1".)
- "listener_m1s" - Same as "listener_m1", except the server will attempt to sign the command using public key cryptography to ensure that PC commands come from a trusted source. Keys must be configured on the server and PC Listener client.
- "launcher" - Profound UI uses the PC Command Launcher, which works in HTTPS pages and on browsers running in Terminal Services sessions. This mode does not support commands waiting (*WAIT).
- "applet" - Profound UI attempts to use the PC Integration Java Applet. See PC Integration API. This option will likely not work in modern browsers.
If pui["pc command mode"] is not specified, Profound UI uses the pui["use pc listener"] option. If pui["use pc listener"] is also not specified, Profound UI attempts to use the Integration Applet.
See PC Integration API.
This option may also be configured in Genie Admin.
Example:
| Code Block |
|---|
pui["pc command mode"] = "launcher"; |
Where do you save this configuration option? Here.