Tosca on Windows Server 2016
Tricentis Tosca supports a full Tosca Commander client installation on Windows Server 2016. For information on the installation process, see chapter "Set up Tricentis Tosca" and chapter "Install Tricentis Tosca".
To run Tosca Commander on your Windows Server 2016, you need to perform additional actions:
-
Mandatory actions that concern Tricentis Tosca Commander as a whole.
-
Modifications that only apply if you work with specific Tricentis Tosca Engines.
Mandatory actions
To run Tosca Commander on your Windows Server 2016, you need to perform the following, mandatory actions:
-
Create a separate License.xml for every workspace.
You need to create a separate License.xml file for every user. Otherwise, any changes you make to a common License.xml will affect other testers.
Tricentis recommends that you perform this step before you start testing.
-
Save settings and buffers to the workspace of individual testers.
If testers change settings or buffers, they need to ensure that these changes apply to their own workspace only. Otherwise, they will overwrite the settings other testers have defined for their workspaces.
Modifications for Tricentis Tosca Engines
If you work with the following Engines, you need to make some additional modifications:
-
XML Engine and XML Engine 3.0: Set a separate port for every user
-
WebService Engine and WebService Engine 3.0: Set a separate port for every user
-
PowerBuilder Engine: Set a registry key for non-admin users
|
|
Tosca Commander on Windows Server 2016 does not support Textra. This affects Optical Character Recognition (OCR) with Classic Win32 Engine and Classic Powerbuilder Engine. For more information, see chapter "Optical Character Recognition with Textra". |