Enable the Elastic Execution Grid integration

Elastic Execution Grid is an early access feature and available as a tech preview.

Click here if you'd like to participate in the tech preview.

To integrate Tricentis Tosca and Elastic Execution Grid, an admin user must first enable the integration.

Which steps you need to perform depends on a key decision:

  • Do you want to integrate via Elastic Execution Grid Addin?

  • Do you want to integrate via Automation Object Service (AOS)?

What's the difference between integrating via Elastic Execution Grid Addin and AOS?

 

Elastic Execution Grid Addin

AOS

Where are the results?

In Elastic Execution Grid.

In Elastic Execution Grid and Tricentis Tosca.

Tricentis Tosca only gets the results of tests that you triggered in Tricentis Tosca. If you trigger tests directly in Elastic Execution Grid, Tricentis Tosca does not get results.

How does Elastic Execution Grid authenticate?

Elastic Execution Grid authenticates every user.

Only users with a valid Elastic Execution Grid user account can push tests to Elastic Execution Grid.

Elastic Execution Grid authenticates AOS.

Any user that has access to the same repository as AOS can push tests to Elastic Execution Grid.

What does Tricentis Tosca send to Elastic Execution Grid?

The local version of your tests.

Users can make changes and directly push the modified tests to Elastic Execution Grid.

The repository version of your tests.

If users make changes to the tests, they must check in their changes before they push the tests to Elastic Execution Grid.

How do I set up the integration?

See "Set up the integration via Elastic Execution Grid Addin".

See "Set up the integration via Automation Object Service".

If you want to integrate via AOS, note the following:

  • You only need to enable AOS itself for Elastic Execution Grid. You don't need a full Tosca Distributed Execution with AOS setup.

  • If you already have Tosca Distributed Execution with AOS installed, you still need to enable AOS for Elastic Execution Grid.

  • If you use Tosca Distributed Execution without AOS for on-premise execution, you can continue to do so after you enable AOS for Elastic Execution Grid.

Set up the integration via Elastic Execution Grid Addin

Ensure that you have the right environment

Elastic Execution Grid integration is only available in multi-user environments.

If you don't have multi-user workspaces yet, create them as described in chapter "Create multi-user workspaces".

Activate the integration

To activate the integration, follow the steps below:

  1. Open the ToscaCommander.exe.config file at %COMMANDER_HOME%.

  2. Set the setting ElasticExecutionGridAddinEnabled to True.

  3. Save and close the file.

You have to do so on every machine where you want to enable the integration. Tricentis recommends that you make your modifications once and then simply copy and paste the file.

Populate the integration settings

To enable communication between Tricentis Tosca and Elastic Execution Grid, populate the integration settings. You need to do so in all workspaces where you want to enable the integration.

Alternatively, you can create project settings for your repository as described in chapter "Work with project settings". You only have to do this once; project settings apply to all workspaces connected to this repository.

To enable communication between Tricentis Tosca and Elastic Execution Grid, follow the steps below:

  1. Open a workspace.

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

  3. Populate the settings as described in this chapter.

Set up the integration via Automation Object Service

Ensure that you have the right environment

Elastic Execution Grid integration is only available in multi-user environments.

If you don't have multi-user workspaces yet, create them as described in chapter "Create multi-user workspaces".

Activate the integration

To activate the integration, follow the steps below:

  1. Open the ToscaCommander.exe.config file at %COMMANDER_HOME%.

  2. Set the setting ElasticExecutionGridAddinEnabled to True.

  3. Save and close the file.

You have to do so on every machine where you want to enable the integration. Tricentis recommends that you make your modifications once and then simply copy and paste the file.

Enable Automation Object Service (AOS)

The enablement process depends on whether you already have Tosca Distributed Execution with AOS installed or not.

To enable AOS for Elastic Execution Grid, follow the steps below:

  1. Get the Client Secret, which you need in step 2.

    If you are not an Okta admin, ask your Okta admin for the Client Secret of the application Tosca Server.

    If you are an Okta admin, follow the steps below:

  2. Modify the AOS configuration in Tricentis Tosca:

To use AOS with Elastic Execution Grid, follow the steps below:

  1. Get the Client Secret. You need it to configure the Elastic Execution Grid integration settings in the Tricentis Service Configuration later on.

    If you are not an Okta admin, ask your Okta admin for the Client Secret of the application Tosca Server.

    If you are an Okta admin, follow the steps below:

  2. Ensure that you have installed all necessary components. You need Tosca Server, including the AOS-relevant server features Distribution Server and Administration Console.

    For information on how to install and configure these components for AOS and Elastic Execution Grid, see the AOS HTTP setup chapter or the AOS HTTPS setup chapter.

  3. Create an AOS workspace as described in the AOS HTTP setup chapter or the AOS HTTPS setup chapter.

  4. Ensure that you have configured the necessary Tricentis Service Discovery settings.

    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.

What's next

Now that the setup is complete, users can run tests in Elastic Execution Grid.