Set up Tosca Distributed Execution without AOS | HTTPS

This chapter describes how to install and set up Tosca Distributed Execution without AOS (Automation Object Service) with HTTPS.

For information on other setup options, see the chapters below. All chapters include the necessary set-up steps for Unattended Execution or a proxy server.

Before you start

If you haven't yet, check out the following chapters:

Setup process

The subsequent chapters describe each setup step in detail. They are listed in the order that Tricentis recommends for your setup process.

Install DEX Server

The Tosca Distribution (DEX) Server is part of the Tosca Server.

To install the DEX Server, you need to install Tosca Server on the machine where you want the DEX Server.

For information on how to install Tosca Server, see chapter "Install Tosca Server".

Set up the DEX Server via Installer

If you install Tosca Server via Installer, you need to perform the following steps to set up the DEX Server:

  1. Make sure to select the relevant server feature(s):

    Distribution Server

  2. To specify an HTTPS binding, select HTTPS on the Tricentis Tosca shared Settings screen.

  3. Finish the Tosca Server installation.

  4. Set up the HTTPS binding for Tosca Server and its features as described in see chapter "Use Tosca Server with an HTTPS binding".

    • Define a certificate in the IIS Manager.

    • Adapt the SSL settings.

    • Start the Tosca Server website.

  5. Start the Tricentis Service Configuration.

  6. Populate the field Certificate Thumbprint in the following tab(s):

    • Tricentis Tosca Server Landing Page

Set up the DEX Server in unattended mode

If you install Tosca Server in unattended mode, you need to perform the following steps to set up the DEX Server:

  1. Make sure to select the relevant server feature(s):

    _4DEXServer and _5TestEventMonitor

  2. To specify an HTTPS binding, add the MSI command USE_HTTPS=1.

  3. Finish the Tosca Server installation.

  4. Set up the HTTPS binding for Tosca Server and its features as described in see chapter "Use Tosca Server with an HTTPS binding".

    • Define a certificate in the IIS Manager.

    • Adapt the SSL settings.

    • Start the Tosca Server website.

  5. Start the Tricentis Service Configuration.

  6. Populate the field Certificate Thumbprint in the following tab(s):

    • Tricentis Tosca Server Landing Page

Install Tosca Commander

You need to install the full Tosca Commander client on all machines on which you want to create TestEvents and trigger their execution.

For information on how to install Tosca Commander, see chapter "Install Tricentis Tosca".

Install Agents

The Agent installation is part of the Tricentis Tosca installation.

To install an Agent, you need to install Tricentis Tosca on every machine that should act as an Agent.

During the installation, you can select one of the following Agent types:

  • An Execution Agent, which can execute TestCases created with Engines 3.0.

  • A full client installation of Tosca Commander. These Agents can execute TestCases created with Engines 3.0 and Classic engines.

To install an Agent, follow the steps below:

  1. Start the installation of Tricentis Tosca.

  2. On the Type screen of the Tricentis Tosca installer, select your Agent type:

    • To install an Execution Agent, select Execution Agent.

    • To install the full client, select Tosca Commander.

Select an Agent type in the Tricentis Tosca installer

  1. Follow the instructions of the Tricentis Tosca installer to complete the installation.

Connect the Agents

Next, enable communication between the Agent and the DEX Server. You need to do this on every Agent machine.

To establish the connection, follow the steps below:

  1. On the Agent machine, open the ToscaDistributionAgent.exe.config file. By default, this file is located at %TRICENTIS_DEX_AGENT_HOME%.

  2. In the system.ServiceModel section, perform the following actions:

    • Change the security mode to Transport.

    • Enter the endpoint address of the DEX Server:

      https://<server IP address or host name>:<port>/DistributionServerService/CommunicationService.svc

      If you use an IPv6 address, the server address has to contain the IP address instead of the host name.

<system.serviceModel>

<bindings>

<basicHttpBinding>

<binding name="BasicHttpBinding_ICommunicationService" sendTimeout="Infinite" maxBufferPoolSize="2147483647" maxBufferSize="2147483647" maxReceivedMessageSize="2147483647">

<readerQuotas maxDepth="2147483647" maxStringContentLength="2147483647" maxArrayLength="2147483647" maxBytesPerRead="2147483647" maxNameTableCharCount="2147483647"></readerQuotas>

<security mode="Transport"></security>

</binding>

</basicHttpBinding>

</bindings>

<client>

<endpoint address="https://localhost:80/DistributionServerService/CommunicationService.svc"

binding="basicHttpBinding" bindingConfiguration="BasicHttpBinding_ICommunicationService"

contract="CommunicationServiceReference.ICommunicationService"

name="BasicHttpBinding_ICommunicationService" />

</client>

</system.serviceModel>

  1. If you use a self-signed certificate, enter the following code within the Configuration tags:

<system.net>

<settings>

<servicePointManager checkCertificateName="false" checkCertificateRevocationList="false" />

</settings>

</system.net>

  1. If you want to use a proxy server, establish the communication between Agent and proxy. This step is only necessary if you want to use a proxy server. If not, you can skip it.

    To establish the connection, modify the settings ProxyAddress, ProxyUsername, and ProxyPassword in the userSettings section.

<userSettings>

<Tricentis.DistributionServer.Properties.Settings>

...

<setting name="ProxyAddress" serializeAs="String">

<value>https://11.1.11.11:1111</value>

</setting>

<setting name="ProxyUsername" serializeAs="String">

<value>User1</value>

</setting>

<setting name="ProxyPassword" serializeAs="String">

<value >Proxypassword</value>

</setting>

</Tricentis.DistributionServer.Properties.Settings>

</userSettings>

  1. Save and close the file.

  2. Start your Agent.

Set up Agent RDP access

To set up the Agent to allow RDP access for Unattended Execution, follow the steps below:

  1. Open the Distributed Execution Monitor.

  2. In the Agent View, click on in the row of the Agent that you want to configure. This opens the Configuration window.

  3. In the Configuration window, go to the Unattended Execution tab and perform the following actions:

    • Select Allow to open remote connections to this agent.

    • Select Use RDP connection.

    • Populate the following fields:

Field

Optional?

Description

Username

 

User name of the Windows user who runs the Agent.

Password

 

Password of the Windows user who runs the Agent.

Desktop Width

yes

Change the default width of the remote desktop in pixels. The default value is 1600.

Desktop Height

yes

Change the default height of the remote desktop in pixels. The default value is 1200.

Color Depth

yes

Change the default color depth of the remote desktop. The default value is 16.

Configure Unattended Execution

  1. Click Save and close the window.

Connect Tosca Commander

Now you need to specify the connection between Tosca Commander and the DEX Server.

You need to do this on all machines where you want to create tests and trigger executions.

Alternatively, you can create project settings. In this case, the settings apply to all workspaces connected to the repository.

To connect Tosca Commander, follow the steps below:

  1. Open Tosca Commander.

  2. Go to Project->Settings->Commander->DistributedExecution->Server.

  3. As the value of the setting EndpointAddress, enter the address of the DEX Server:

    https://<server IP address or host name>:<port>/DistributionServerService/ManagerService.svc

    If you use an IPv6 address, the server address has to contain the IP address instead of the hostname.

  4. If you want to use a proxy server, populate the value of the setting Proxy with the complete network address of the proxy server:

    https://<server IP address or host name>:<port>

  5. Go to Project->Settings->Commander->DistributedExecution->Monitor Url.

  6. As the value of the setting Url, enter the address of the machine that holds the Tosca Distributed Execution Monitor:

    https://<server IP address or hostname of the machine that holds the DEX Monitor>:<port>/Monitor/

Modify the settings

Administer licenses

You need to have a valid Tosca license on all machines where you install Tricentis Tosca:

  • Each Agent machine requires an ExecutionOnly license.

  • Each machine on which you create tests and trigger their execution needs an appropriate Tosca license. Which license you need depends on the kind of tests you create. For information on licensing options, contact Tricentis Sales.

For information on how to set up licensing on your machines, see chapter "License management".

Set up workspaces

To use Tosca Distributed Execution without AOS, you need to set up separate multi-user workspaces.

These workspaces must have access to one common repository.

  • One multi-user workspace on each machine on which you create and trigger your tests. These are your user workspaces.

  • One multi-user workspace on each Agent machine. This is the workspace the Agent uses to execute your tests.

Create user workspaces

  • If you are already working with Tricentis Tosca and have a repository and workspaces, you can skip this step.

  • If you have not yet set up your repository and workspaces, do so now (see chapter "Create multi-user workspaces"). You need one workspace on every machine where a user should create and execute tests.

Create Agent workspaces

The Agent workspace is the workspace that the Agent uses to execute your tests.

To set up an Agent workspace, follow the steps below:

  1. On the Agent machine, create a multi-user workspace. Ensure that it's connected to the common repository.

  2. Ensure that you have at least one Admin user who has all necessary access and permissions to the applications the Agent should steer during execution.

  3. On the DEX Server machine, open the Distributed Execution Monitor.

  4. Switch to the Agent View.

  5. Click on in the row of the respective Agent. This opens the Configuration window.

Open the Configuration dialog in the Distributed Execution Monitor

  1. In the Configuration window, click Workspace and populate the following fields:

Field

Description

Tosca Workspace

Absolute path to the workspace that the Agent should use for execution.

Tosca User

Name of the user to access the workspace.

Password

Password of the user.

If you use LDAP integration to manage user groups, leave the Tosca user and Password fields empty (see chapter "Synchronize users and user groups with LDAP").

Set up a workspace

  1. Click Save and close the window.

What's next

Now that you've set up Tosca Distributed Execution, you're ready to start testing! For more information, see chapter "Create and execute TestEvents".