one way would be for the nsh script job to set a property on the target server, and the deploy jobs to pass in TARGET.YOUR_PATH to the local property you created. or get rid of the local property and have your blpackage refer to TARGET.YOUR_PATH directly.

what are you trying to do where ? why do you need to set the path for a bunch of blpackages ?

Why do you want to use a local property ? if the only place you are using that is the sudoers package change what benefit does the property give you ? it means more overhead to get the value and set it.

As I have multiple projects, I want to make use of prefered options available in BL, as needed.

I agree for sudoers it's not needed, but I have similar multiple requirements where I have to push multiple files(BL packages) or a bulk jar file(s), and/or tar file(s) not to one particular path. it vary from host to host and version to version and also from platform to platform (Unix, linux, hp-ux, aix)

One is not related to other, all my requirement are entirely different individual tasks/requests. However, the common think of all requests/requirements is that PATH is not static. It vary from host to host in my environment.

if you have a bunch of different applications that could be in different places on every target, i don't know if it makes sense to track that w/ properties - that's a lot of overhead imo. for example let's say you have 10 different applications. if each application can be in a location different that the other applications on each box you would need 10 properties to track them. and then a nsh job to continually go update the right value for each of the applications. if you can't use the same property across different applications it seems kind of pointless to use a property for this. because now you have to make sure your nsh job runs before the deploy, just in case one of the paths changed. why not just put the logic to find the location in the blpackage itself ?

so it would be one thing if you had something like 'APP_ROOT' and that was the root of where all your applications were installed. but if you have sudoers and that could be in /etc, /usr/local/etc, /usr/local and then you have a webserver and that could be in /usr/local, /usr/local/apache, /opt/apache, /usr/apache and then an appserver in /opt/tomcat, /usr/local/tomcat, etc etc for each app what value does having a property get you ?