Skip to main content
1-Visitor
June 20, 2017
Question

How to determine whether a filesystem folder is used as a sandbox (without project.pj)?

  • June 20, 2017
  • 1 reply
  • 4924 views

Hi all,

at the moment we're working with Integrity 10.7, but we are in the evaluation process to update to 11.0. And we are using some external tools to work with integrity, and these tools mostly are using the Java-API to Integrity.

Until now the external tools can create and use sandboxes, and for creating sandboxes they look into a choosed filesystem folder for the project.pj to determine whether this folder is already used as a sandbox. Since Integrity 10.8 the project.pj-files in the sandbox-folders are gone, and now we are searching for a new, quick solution to replace the old functionality.

Certainly we can use the API-connection to the integrity client and use the information the client is holding, but this would be much more complex than a quick look into a folder without opening a client-connection. As an idea: Is it possible to read the new database, which is holding all the sandbox information (bypassing the client)?

Thanks, Jens

1 reply

5-Regular Member
June 20, 2017

Can you not just reference the output or info returned by the "si sandboxes" command, as it will show you the currently registered sandboxes for that client?  Perhaps that's what you're already doing?

ex.

C:\>si sandboxes

c:\sandboxxes\project.pj -> c:/ALM/SAMPLE_DATA/project.pj (mchatel0l:7001)

The client-db for the project/sandbox registry is not readable outside Integrity.

JensN.1-VisitorAuthor
1-Visitor
June 21, 2017

Hi Michael,

thanks for your answer. For sure we can use "si sandboxes" over cli or a similar command over the API. But both ways require a connection at least to the client, maybe to the server. The old way to determine whether a filesystem folder is used as a sandbox or not was completely independent from any integrity connection, from any user context and very quick. Even if you are looking at a network share and you dont know, which different users had access to this share, you can see if a folder is used as a sandbox. And we still would like to have such a quick, independent way to look at this... 

kind regards, Jens

12-Amethyst
June 21, 2017

A pragmatic approch that comes to my mind would be

if the sandbox creator was doing something like:

N:\my_sandbox>si sandboxinfo > .si_sb_info

N:\my_sandbox>si projectinfo > .si_pj_info

This would even provide readable context information but its dependent on user discipline of course.

As for wishful thinking it would be nice if such tasks could be automated

by some kind of client side trigger mechanism.

(maybe 11.0 supports such a thing ? )

regards

Jürgen