Uniface Deployment Archive - Files

Hi Unifacers,

one of my Uniface project is including some external files, either text and binary files; I have included them into a project deployment archive to be distributed. This functionality is already available into current deployment archive functionality:
- Binary files are saved into deployment archive within "fil" subdir
- Text files are saved into deployment archive within "txt" subdir
Now I have found one issues:
All these files are configuration files related to this project and are organized in a subtree starting from base project directory. This project was initially setup 2 years ago and it was positioned on a machine in a certain position into file system.
Now the same project was restored to be reviewed into another machine in another position of the files system; all references to external files into UARCHITEM are broken!

The reason is UDE is saving for these files their FULL PATH NAME into table UARCHITEM, I feel because being its primary key. As of today in U9.7.05.024 I did not find any way to save a relative filename: there is a checkbox available (Qualify source name) but also unchecking it always the full path file name is saved because the filename cannot be manually edited.

My question:
Shouldn't UDE require to developer to define UNIQUE original filenames either full path names or path names relative to current directory?

Any suggestion?
Gianni

Hi Gianni,

I just had a little experiment with 9604 with Select Files Form:

uncheck Qualify Source file names
check Qualify target file names
but leave target folder (which is editable) empty

"Define Development Archive" shows only the pure filename as ObjectName

The generated UAR looks OK for me because under the root we find "txt and "uar" subdirectory

HIH, Uli

P.S:

so it may take only a little SQL magic to change the PKs for the existing Archives

Hi Unifacers,

one of my Uniface project is including some external files, either text and binary files; I have included them into a project deployment archive to be distributed. This functionality is already available into current deployment archive functionality:
- Binary files are saved into deployment archive within "fil" subdir
- Text files are saved into deployment archive within "txt" subdir
Now I have found one issues:
All these files are configuration files related to this project and are organized in a subtree starting from base project directory. This project was initially setup 2 years ago and it was positioned on a machine in a certain position into file system.
Now the same project was restored to be reviewed into another machine in another position of the files system; all references to external files into UARCHITEM are broken!

The reason is UDE is saving for these files their FULL PATH NAME into table UARCHITEM, I feel because being its primary key. As of today in U9.7.05.024 I did not find any way to save a relative filename: there is a checkbox available (Qualify source name) but also unchecking it always the full path file name is saved because the filename cannot be manually edited.

My question:
Shouldn't UDE require to developer to define UNIQUE original filenames either full path names or path names relative to current directory?

Any suggestion?
Gianni

Hi Gianni,

I just had a little experiment with 9604 with Select Files Form:

uncheck Qualify Source file names
check Qualify target file names
but leave target folder (which is editable) empty

"Define Development Archive" shows only the pure filename as ObjectName

The generated UAR looks OK for me because under the root we find "txt and "uar" subdirectory

HIH, Uli

P.S:

so it may take only a little SQL magic to change the PKs for the existing Archives

Hi Gianni,

I just had a little experiment with 9604 with Select Files Form:

uncheck Qualify Source file names
check Qualify target file names
but leave target folder (which is editable) empty

"Define Development Archive" shows only the pure filename as ObjectName

The generated UAR looks OK for me because under the root we find "txt and "uar" subdirectory

HIH, Uli

P.S:

so it may take only a little SQL magic to change the PKs for the existing Archives

Hi Unifacers,

one of my Uniface project is including some external files, either text and binary files; I have included them into a project deployment archive to be distributed. This functionality is already available into current deployment archive functionality:
- Binary files are saved into deployment archive within "fil" subdir
- Text files are saved into deployment archive within "txt" subdir
Now I have found one issues:
All these files are configuration files related to this project and are organized in a subtree starting from base project directory. This project was initially setup 2 years ago and it was positioned on a machine in a certain position into file system.
Now the same project was restored to be reviewed into another machine in another position of the files system; all references to external files into UARCHITEM are broken!

The reason is UDE is saving for these files their FULL PATH NAME into table UARCHITEM, I feel because being its primary key. As of today in U9.7.05.024 I did not find any way to save a relative filename: there is a checkbox available (Qualify source name) but also unchecking it always the full path file name is saved because the filename cannot be manually edited.

My question:
Shouldn't UDE require to developer to define UNIQUE original filenames either full path names or path names relative to current directory?

Any suggestion?
Gianni

To REPAIR this situation without artistic SQL tricks we edit the export file:

1. Export the archive(s)
2. Delete the archive(s) in Uniface (as we change the primary keys)
3. To remove the hardcoded path to the working directory, use an Editor on the export file replacing
   '<DAT name="U_OBJNAME">C:\\drive_g\\!drive_!m4l\\umeFASTory\\umeFASTory_TDD-9604\\work\\' with '<DAT name="U_OBJNAME">'
4. Import the exported Archive back to Uniface
5. create the archive output now with relative positioning

This should be able to handle even the subtrees Gianni has mentioned as we cut only the leading part of the full path which is a constant to all PKs

Its a fast and easy way to transform from fullpath to relative path while benefit from all the support of IDE.

PLUS you can maintain the archive using the standard way which is the fastest one and finally apply the transformation routine again which works on the new records only.

Hi Gianni,

Have you had a look at the mklink command in Dos?

Knut

Hi Unifacers,

one of my Uniface project is including some external files, either text and binary files; I have included them into a project deployment archive to be distributed. This functionality is already available into current deployment archive functionality:
- Binary files are saved into deployment archive within "fil" subdir
- Text files are saved into deployment archive within "txt" subdir
Now I have found one issues:
All these files are configuration files related to this project and are organized in a subtree starting from base project directory. This project was initially setup 2 years ago and it was positioned on a machine in a certain position into file system.
Now the same project was restored to be reviewed into another machine in another position of the files system; all references to external files into UARCHITEM are broken!

The reason is UDE is saving for these files their FULL PATH NAME into table UARCHITEM, I feel because being its primary key. As of today in U9.7.05.024 I did not find any way to save a relative filename: there is a checkbox available (Qualify source name) but also unchecking it always the full path file name is saved because the filename cannot be manually edited.

My question:
Shouldn't UDE require to developer to define UNIQUE original filenames either full path names or path names relative to current directory?

Any suggestion?
Gianni

Hi Unifacers,

one of my Uniface project is including some external files, either text and binary files; I have included them into a project deployment archive to be distributed. This functionality is already available into current deployment archive functionality:
- Binary files are saved into deployment archive within "fil" subdir
- Text files are saved into deployment archive within "txt" subdir
Now I have found one issues:
All these files are configuration files related to this project and are organized in a subtree starting from base project directory. This project was initially setup 2 years ago and it was positioned on a machine in a certain position into file system.
Now the same project was restored to be reviewed into another machine in another position of the files system; all references to external files into UARCHITEM are broken!

The reason is UDE is saving for these files their FULL PATH NAME into table UARCHITEM, I feel because being its primary key. As of today in U9.7.05.024 I did not find any way to save a relative filename: there is a checkbox available (Qualify source name) but also unchecking it always the full path file name is saved because the filename cannot be manually edited.

My question:
Shouldn't UDE require to developer to define UNIQUE original filenames either full path names or path names relative to current directory?

Any suggestion?
Gianni

And finally there is a proposal for a "all uniface" solution in 9.6.04

entry do_fill_x_workdir
x_workdir = $ldir()
end ; do_fill_x_workdir

entry do_retrieve
clear/e "UARCHITEM"
U_OBJNAME = $concat(X_WORKDIR,"·*")
retrieve/e "UARCHITEM"
end ; do_retrieve

entry do_transform
$1 = ""
setocc "UARCHITEM",1
while ($dbocc > 0)
putlistitems/occ $2 ,"UARCHITEM"
putitem $1,-1,$2
remocc "UARCHITEM",1
endwhile
message/info $1
while ($1 != "")
   getitem $2, $1, 1
   delitem $1, 1
   creocc "UARCHITEM",-1
   getlistitems/occ $2, "UARCHITEM"
   U_OBJNAME = $replace(U_OBJNAME,1,X_WORKDIR,"")
endwhile
end ; do_transform

entry do_save
macro "^store"
end ; do_save

; NOTE: to break the readonly UARCHITEM put a WRITE/DELETE in the triggers

The benefit of U9 is that GOLD chars have this "central dot" prefix so you should be able to just copy&paste