Highlighted
Absent Member.
Absent Member.
3332 views

Save Quality center workflow script using OTA API

Hi

 

We hadel 150 project and would liek to take the backup of each project's customization / workflow code using VB script with OTA API. Any pointer would be helpfull for us

0 Likes
6 Replies
Highlighted
Absent Member.. Absent Member..
Absent Member..

If your running qc 10 or earlier, then the workflow scripts can be found in the repository for each project under a folder called "scripts":

There exists 1 VBScript workflow file per feature. Those are:

Login/Logout (common.tds)
Defects module (defects.tds)
Manual Test Execution (manrun.tds)
Test Requirements module (req.tds)
Test Lab module (testlab.tds)
Test Plan module (testplan.tds)
Robert Barcikowski
Senior Technical Specialist
0 Likes
Highlighted
Established Member..
Established Member..

What about beyond ALM/QC version 10? The biggest issue is project’s smart file repository which becomes an inaccessible to the humans for an accessing to the scripts for the customized automated backup. So far, HP hasn’t yet demonstrated for the backup scripts by using OTA client’s object method because there aren’t any methods existed in OTA client object.

0 Likes
Highlighted
New Member..
New Member..

You can use an ftp client to download the script files. Add in site administration a parameter of "FTP_PORT" with a port number (21 or 2121 typically). Then, any administrator can peruse, download and upload script folder - open ftp client and put in <QC server address>:<FTP_PORT value>/ , you will then be prompted for credentials (use admin user/password). 

0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

The source question here is if it is possible to save or get workflow scripts by OTA API.

 

I know that in QC 10 it was saved in temp folder, or it was saved in repository folder on the server.

In ALM 11 and higher it is no longer saved in temp file (localy) on client site. And there is used Smart repository so you can get the workflows scripts by FTP from the server site.

 

But I do not have access to the server repository. So i need to get access the workflow scripta by OTA API. The main reason is that when I do something by OTA API the workflow scripts are not run. So I want to run some specific parts from workflow scripts when I connect by OTA API.

 

Do you know how to do it?

0 Likes
Highlighted
Established Member..
Established Member..

Hello Vladimir,

 

Did you manage to access repository files via OTA API ? I am extremely interested in the reponse.

 

This is not exactly the same problem. What i am trying to do is create a project report from Sprinter execution, but in order to do that i would need to access the sprinter execution logs stored in the repository and recreate steps.

So having access to repository file is mandatory.

 

Thanks in advance for your response .

 

Best regards,

Cédric Mabileau.

0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

I think it is another question.

 

I did not find any answer for my or for this original question. There is no possibility to read workflow script by OTA API. The only solution I think about it. To run the batch on application server that will download script and save it to the database. Then I can use OTA API to read it. But it is not online.

 

Your quesiont is about files of sprinter executions or sprinter tests. I think this should be acceasable by OTA API directly. Try to search OTA API. Try to find out how to download the repository file by OTA API it is possible.

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.