2 Replies Latest reply on Jun 29, 2005 10:17 PM by Brad Jacobs

    setting properties for a job



      It looks like Job properties won't help for this, but I would be interested to know if there is a way around this.


      We are trying to use a job to provision a nim server, and we are using server properties to do this. For example, we have a server property on the nim server that says which server we are provisioning.


      The problem happens when we want to provision more than one server at a time!


      The server property gets overwritten with the new value when the second job runs, and the new value is read by the existing running job.


      The current workaround I see is to write the server properties to a file before starting the job, but I would like to know if there is a better workaround.