Yes, none of the Utility export* commands can use a nsh path. none of the samples list a nsh path. we can maybe make that more clear in the docs…
what you want to acheive by doing this ?
If your requirement is to save the output to any remote server then you can do as follows.
blcli_execute Utility exportDeployRun "/sampleJobGroup" "sampleJob" $JOB_ID "C/temp/sampleJobResult.csv"
cp //$hostname/C/temp/sampleJobResult.csv //remote_server/path_to_store
You can use @ - you don’t need the localhost name…
Cp //@/blah //target/foo
Or just cp /blah //target/foo
Yup thought of that (thanks for the suggestion though)... but this command is being executed from an AO blcli adapter therefore it cannot run the additional cp command via nsh.
I would suggest to the AO guys to use the AO BladeLogic/NSH adapter but we can't seem to get that working with a domain service account using domain auth. The AO documentation is lacking confirmation on whether or not Domain Auth can be used for that adapter. Only options are ADK or SRP.
i'm not sure i understand the issue - after bao dumps the file on itself, can't you pass the file name off to another command that does the nsh copy to whatever target server you want ?
I'll check with the AO team but I believe that the AO BLCLI adapter can only process blcli commands. NSH commands would fail (assumption)
There should be a nsh or script adapter… it can be another step in the flow.
yes but we cannot get the nsh adapter to work with domain auth - believe the AO team here found and reported a bug to bmc in the NSH adapter. waiting for that to be resolved
Do you have a ticket # for that ?
Sure, here you go: ISS04324189