Uniface Anywhere User access

Hi
How do you set up Anywhere Servers being able to use only one common Uniface runtime installation.

Anywhere with several Uniface runtimes
UnifaceApp1ForUsergroupA           D:\\shares\\UsergroupA\\ Uniface\\bin\\Uniface.exe  
UnifaceApp2ForUsergroupB          D:\\shares\\UsergroupB\\ Uniface\\bin\\Uniface.exe
UnifaceApp3ForUsergroupC          D:\\shares\\UsergroupC\\ Uniface\\bin\\Uniface.exe

As Anywhere relies on the host's operating system to provide the security necessary to run applications, the user can see those start-icons which they may access. 
In Anywhere the application is defined in this kind of window. Putting the same Uniface-path in Location-field puts access to every user for any Uniface-program.

I would like to install so that Uniface runtime may be installed only once, but the users in different usergroups would see only their own start-icons. Is there an easy way to do this?  

Anywhere
UnifaceApp1ForUsergroupA           D:\\shares\\Common\\ Uniface\\bin\\Uniface.exe  
UnifaceApp2ForUsergroupB          D:\\shares\\Common\\ Uniface\\bin\\Uniface.exe
UnifaceApp3ForUsergroupC          D:\\shares\\Common\\ Uniface\\bin\\Uniface.exe

Regards RogerW

Thanks Iain ,

I have no experience of sh.exe, but that could work.
I suppose you can't do the same with CMD.EXE or PowerShell.exe, perhaps too windows integrated...
I have to do some testing...
What advantages do you get by the exe you use today? Do you want to sell it? :-)
Perhaps one could do something by cloning Uniface.exe. But that could give you some really bad problems patching Uniface versions etc.

Regards RogerW.

Hi
How do you set up Anywhere Servers being able to use only one common Uniface runtime installation.

Anywhere with several Uniface runtimes
UnifaceApp1ForUsergroupA           D:\\shares\\UsergroupA\\ Uniface\\bin\\Uniface.exe  
UnifaceApp2ForUsergroupB          D:\\shares\\UsergroupB\\ Uniface\\bin\\Uniface.exe
UnifaceApp3ForUsergroupC          D:\\shares\\UsergroupC\\ Uniface\\bin\\Uniface.exe

As Anywhere relies on the host's operating system to provide the security necessary to run applications, the user can see those start-icons which they may access. 
In Anywhere the application is defined in this kind of window. Putting the same Uniface-path in Location-field puts access to every user for any Uniface-program.

I would like to install so that Uniface runtime may be installed only once, but the users in different usergroups would see only their own start-icons. Is there an easy way to do this?  

Anywhere
UnifaceApp1ForUsergroupA           D:\\shares\\Common\\ Uniface\\bin\\Uniface.exe  
UnifaceApp2ForUsergroupB          D:\\shares\\Common\\ Uniface\\bin\\Uniface.exe
UnifaceApp3ForUsergroupC          D:\\shares\\Common\\ Uniface\\bin\\Uniface.exe

Regards RogerW

Session users do NOT see published Executables if they do NOT have the rights to start them.

You just can copy the uniface.exe and rename it to something_else.exe in the same uniface\\common\\bin directory.
Now you can select the copied exe and set the rights on it to use only by the users you want.
Within Uniface Anywhere you can just  change the uniface.exe for the copied one.

This will NOT show any executables they do NOT have the rights to it.

Thanks Nico for your input,
the problem with this, as I understand it, is that the Uniface.exe could change as you patch your Uniface.
Then you would have to reproduce the renamed Uniface.exe files after each update of your Uniface.
This could of course be done with a bat-file, if you remember to edit the bat file as your users/usergroups change on the Anywhere server.

Regards RogerW

Thanks Iain ,

I have no experience of sh.exe, but that could work.
I suppose you can't do the same with CMD.EXE or PowerShell.exe, perhaps too windows integrated...
I have to do some testing...
What advantages do you get by the exe you use today? Do you want to sell it? :-)
Perhaps one could do something by cloning Uniface.exe. But that could give you some really bad problems patching Uniface versions etc.

Regards RogerW.

Our exe checks the asn file for a logical, which points to a folder path on the server.  Files in several folders within this are then checked with files on the client and copied out if they are older/don't exist. 
Some (batch files and powershell files) are executed if they are newer.
This allows us to release patches (.uar files) on the server, and change the asn to include them, as well as running 'tidy up' scripts to remove old patches etc. 
As these are copied before uniface starts, files can be updated as they are not (yet) locked and the asn files changed before the system loads them. 
It's probably got our folder structure/install paths too hard coded to be sold 'as is', but I can probably release the source as a base for your own work if you wish. 

Regards,
Iain

Interesting, actually we have had problems with slow Uniface loading as we usually keep Uniface and Uniface-applications on a shared server-drive, ie. this is the situation not using Anywhere.
However, you probably don't use any automatic copying/updating of files using the Anywhere server? 

Regards RogerW