/build/static/layout/Breadcrumb_cap_w.png

Setting permissions on Registry with radia Tool

Hi,

I am packaging Application with Radia Tool and I am facing Problem with the application is for Test User/Normal User it requires Write access to the registry.
Found out the registry and created a New package but now the problem is setting up the permissions with tool. I have included the Tool and Registry into a New Package and tried calling the SETACL tool through ZCREATE. But I am not able to include the Command in Zcreate since the length is exceeding the allowed.

Please suggest a Solution!

Thanks In Advance,
Vna

0 Comments   [ + ] Show comments

Answers (4)

Posted by: staples 17 years ago
Senior Purple Belt
0
Just create a rexx script or batch file to do you command. (put that in the zcreate).

rex
cmd1='cmd /c setacl.exe .....'
address cmd cmd1

batch
setacl.exe ......

Just make sure you path out setacl.exe
Posted by: turbokitty 17 years ago
6th Degree Black Belt
0
You should consider extending the length of your ZCREATE line. This can be done by editing the class. Make sure you don't do this in production via the GUI or a ZUPDATE will run on all your packages. It can be done through the command line, call support to get a command that suits your environment.

A rex will work as well, as will a call to SETACL in an MSI transform but you'll eventually have to address your short ZCREATE. It can be quite a pain.
Posted by: staples 17 years ago
Senior Purple Belt
0
but to change it on the service, means you need to edit the default instance. If you do that all services will be flaged as updated and every service will trigger a updated..... a lot of traffic.

You can use zedmans command but you still have services possible out of sync. If you do change do it over a long weekend and schedule as many connects to occur off hours.

fun. I say just write a rex and have the path be less that the 50 default characters.
Posted by: turbokitty 17 years ago
6th Degree Black Belt
0
It can be done via Zedmams without triggering the update flag on your services. I've done it twice in two different environments.
I agree a quick fix is to use REX, but it's a PITA in my opinion to have to do that constantly.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ