nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

passing instance name

herald10

Hi,
Is there a way to pass an instance name to a DNR script.
Environment: Open Deploy 5.6 SP1(Solaris)

Thanks in advance
H

Find more posts tagged with

Comments

ts_user

It depends on the way you are generating the deployment command line. If you are generating the instance name with each deployment, you should be able to pass the instance name as one of the parameters which is used as one of the arguments for your DNR.
example:

iwodstart depname -inst abcinstance -k dnrparam=abcinstance

The $dnrparam^ is used within the deployment configuration file as one of the arguments for the DNR script.

Hope this helps.

Thanks.

herald10

Thanks for your response.
But in the morning I gave the same solution to the client. They don't want the user to enter the instance name twice. And we are invoking the deployment from open deploy UI. Is there any other way? documented or undocumented? I checked the documentation and KB articles but couldn't find a solution.

Thanks again
H

lhdavis

You could create a custom CGI script, called from the TeamSite GUI, that simply has a textfield that accepts the instance name, and then you could programmatically generate and execute the OD command line call. You could even post the results of the command. Personally I would keep users out of the OD Admin GUI as much as possible. There's too many things they can do to screw things up. And if they don't want to have to type something twice, this is an easy solution.

Luke Davis
Open Technology Group, Inc.
luke.davis@med.va.gov

ts_user

Depending on the number of instance names you have defined, you should be able to hardcode that values within the deployment names for the DNR and have the users select the deployment names to invoke the DNR with the instance names. You can match the deployment names to be instance names so that it's not difficult for the users to remember which deployment name to call.

Thanks,
ts_user

Migrateduser

Fyi, a feature request has been filed (#54455). Please contact Tech Support (or send me a message) with your company name to get attached to the request.

Another workaround I can think of is to infer the instance name from the most recently updated log file, but that assumes there aren't other deployments happening at the same time and that the script knows where the deployment name stops and the instance name starts. (The instance name is automatically concatenated to the end of the deployment name.)

Todd Scallan
Director of Product Management
Interwoven
t: 408-530-7167
e: tscallan@interwoven.com

ts_user

I thought of same option of parsing the log files for instance name but it would also be challenging depending on the number of deployments happening at that time ( if any concurrently) and number of log files in the logs directory ( if there is no periodic cleanup).