Moving a CAD assembly files to a test server after a refresh.

[pyalavarthi]

Hello all,
When we do a test system refresh from production database, we don't
copy the vault everytime. Though database and ldap are synced everytime ,
vault is not.
I am wondering if there is a way to move files only corresponding to a CAD
assembly to the test server after the database refresh. Any suggestions
/ideas will be appreciated.

Thanks,
Prathap <">http://goo.gl/LuT5>

[ddemay]

You can export an assembly through the export applet to a jar file or write
sql where its resultset/output is the sequenceid and vault folder and
filename in a csv format. You can write a quick script to copy only those
files to a staging area and move them over. For the remaining files, there
is a utility class that will write 0kb files to fill the vault with valid
files matching what is in database.

[GaryMansell]

Dave,

This is a topic that is of interest to me also...

How do you suggest using the Applet export/import as, if you export the data from the PROD System, surely you will not be able to import the same data into the TEST system as it will already exist in the DB (but not the vault)? If you were to just copy the vault files from the resulting exported jar file then I am guessing that this would not work either as the filenames will all be wrong.

Or am I missing something here?

Would you be able to expand on your SQL report method to grab an assy's vault files so that they can be manually copied and point me to the utility class and how to use it?

Thanks in advance

Gary

[jer3d1]

Consider this method:

In the Production Environment:

1. Backup the data from the production environment the same way you would save anything offline. (IE: Use backup in Pro-Engineer, export from a workspace, download from the details pages etc...)

In the Test Environment:

2. Add the documents to a workspace and check them out.


3. With the same workspace from step 2 activated in Pro-Engineer, open the files which were backed up in step 1. (File --> Open or drag and drop into Pro-E from Windows folder.)



4. Check the files in from Pro-E. You will receive a warning that there are already files in the workspace with the same name, choose to ignore this warning and continue.




All the best,
Jered

[pyalavarthi]

Thanks David.
I was able to come up with a sql script to find the actual
filenames. As you suggested I copied them manually to test server and they
worked fine. Thanks for your suggestion.


select M.wtdocumentnumber,
F.name as FolderName ,
(select PATH from FVMOUNT where ida3a5=F.ida2a2) as Path,
lower(to_char(I.UNIQUESEQUENCENUMBER,'0XXXXXXXXXXXXX')) AS FileName,
I.MODIFYSTAMPA2 AS ModificationTime
FROM FVITEM I,
FVFOLDER F,
APPLICATIONDATA A,
HOLDERTOCONTENT H,
WTDOCUMENT D,
WTDOCUMENTMASTER M
where M.WTDOCUMENTNUMBER in (*'0000029218','0000029219'*)
and M.ida2a2=D.ida3masterreference
and D.ida2a2=H.ida3a5
and H.ida3b5=A.ida2a2
and A.ida3a5=I.ida2a2
and F.IDA2A2=I.IDA3A4


Prathap <">http://goo.gl/LuT5>