The following properties on Tosca items are required in Tosca to support the integration:

Service Account - Special Admin Level Integration User

The integration has two categories of operations in terms of permissions:

1. Typical user

2. Admin user

A Typical user operation involves creating and updating entities. An Admin user operation, however, changes group ownership on a Tosca item, and therefore requires Admin level permission in Tosca. Admin operations are operations like routing an item for approval or removing an item from an approval route – these require "locking" and "unlocking" items in Tosca.
Typical user operations use the credentials of the ALM user. (NOTE: the first Tosca operation in an ALM User session requires that the user is prompted for their password, as passwords are not programmatically available in ALM.)
For Admin operations, a special Tosca user must be defined. The implementation refers to this account as the "Service Account" and "Service Password".
These credentials must be specified in each project, in the Synchronization Policy file. The Service Password should be encrypted by the Tx3 VERA encryption utility. See above Synchronization Policy File sample.

Lock / Unlock Groups

Two Tosca groups must exist – one that has every engineer as a member, and one that only has one or two Admin users as a member. These groups enable locking and unlocking Tosca items, when ALM switches the item's Group Ownership property.
These two group names must be configured in the Synchronization Policy file so VERA knows what values to use when locking/unlocking an item.
See above Synchronization Policy File sample.

Remote Execution

To execute a Test Set, in Test Lab, click the Tosca Interface button, then click 'Run Test Set'. On the next dialog, click the 'Run' button. Progress messages are logged in the status in the "Status" pane.
A Tosca Test Set execution runs without ALM-Tosca system problems (as opposed to System Under Test problems) when the following prerequisites are met:

• Tosca & ALM are operational, configured correctly, including Tosca's DEX and REST components

• Remote Agent machines are configured properly and are operational for the intended test cases.

• A Tosca "Test Event" is defined for the associated Execution List in Tosca. Remote Execution in Tosca executes "Test Events". Test Events can be parameterized to run on specific machines.

Note that Execution takes place via "DEX", Tosca's "Distributed Execution" service, though Tosca's CIClient. The CIClient is Tosca's "Continuous Integration Client", a command-line set of executables that requests a Test Event to be remotely executed via the DEX service. This returns an XML result set for each Test Case in the Execution List.
User credentials are not needed for a CIClient request.

Known Issues

• Remoting to Tosca Server to run Commander – run Commander "As Administrator"

• Tosca Agent – must have a logged in session and that account must have access to a Tosca license.

• Tosca Cloud License, associated user must have logged into and displayed licenses in the "Tosca License Configuration" application, at least once.

• Copying linked items in Tosca – must be done by an administrator that clears integration fields

• Tosca Properties are currently editable, until an item is routing for approval or approved. Administrative procedures, and training, must be in place to ensure that ALM related properties for managing links are not updated.

• Tosca Copy operations also copy ALM link information. Either create a new Tosca entity and copy contents into it or, if the item is locked, have an Admin perform the copy operation to remove the ALM link information.