1 of 1 people found this helpful
I assume you are talking about three physical appservers each running atleast one CONFIG server .
Have you tried explicitly passing the authentication profile to blcli to connect to a particular appserver.
I will have three profiles pointing to three servers, and use the one I am interested in getting the details.
When you use the Console, and do NSH here, you already get authentication for the server by making a connection and I beleive in you case you are being connected to first appserver, and you always get the details of that.
Try using this, I have not tested this myself, but I think it should work.
So I would need to use blcred to change profiles and would need to provide a password. Yes?
Try running this from command line first , there u will have to use blcred and password , see if it works the way I m thinking.
Yes that case works but i'm hoping for a solution that does not require me to use passwords in the script or use of the user_info.dat file. If it can be done in the Console via Configuration/Infrastructure Management/.../ClientConnectionService w/o re-authenticating then I would have thought it was possible from BLCLI.
In the gui, if you do the ‘generate support data’ from the configuration menu, and also a similar command in the blcli ‘Support’ namespace, I believe you can generate what you want.
The blcli will always require authentication. if you run it as part of a job, the blcli will pickup creds from the context of the job, but the authentication is still happening.