OmniLaunch

Overview

OmniLaunch exists to solve the problem of having a RDP server (or other multi-client Windows desktop system)run separate instantiations of OmniScript. OmniScript uses a configuration file to determine which of the server's global ports to use, but in a multiple client system each desktop requires its own set of ports so that only the client's signature pads are available to the desktop rather than all of the signature pads on all of the clients.

OmniLaunch is an ActiveX component that runs in either Internet Explorer or Edge (Chromium-based, "Edgium") running in IE mode. If you are interested in OmniLaunch, contact our support team at support@my.scriptel.com or 844-972-7478.

Documentation

OmniScript requires two or three ports but OmniLaunch constrains it to two per instance. The application must connect to OmniScript on a port, either an http or https port. It is possible (and normal) for OmniScript to have a port assigned for each simultaneously, however OmniLaunch forces the developer to choose only one connection method for each instantiation. The other port is used for discovery. Discovery allows OmniScript instances to "see" each other and share their devices. Since this is exactly what is not desired in the multi-tenet Remote Desktop configuration, each instance gets its own discovery port.

OmniLaunch picks two unused ports at random from a range of ports. The default range is 51456-52991 (0xc900-0xceff). The range can be set or modified in the registry.

Computer\HKEY_CURRENT_USER\Software\Scriptel Corporation\OmniLaunch\portMin

Computer\HKEY_CURRENT_USER\Software\Scriptel Corporation\OmniLaunch\portMax

Create the <OBJECT> tag as shown in the example. The example shows a HEIGHT and WIDTH, but this is just for development purposes. For production it is intended that these will be set to 0 so that the control will be invisible.

See the example at https://TBA.