It should be on ALL.
One or the other way, the communication passes through All the Application Servers in the environment at some point of time.
Evidence is that we had issue in running BLCLI commands through NSH Script jobs saying invalid Proxy or AppServer URLs.
you have a couple options:
- make the job instances job+nsh proxy and config+nsh proxy. jobs running that need a proxy will point to the same instance for the proxy service and you don't need to set the proxyserviceurls. users that need the proxy will get directed to the config instance they are connected to w/o any additional config.
- setup a nsh proxy instance or add the proxy service to an existing ALL instance (you don't seem to have any all) and then on each instance that needs to know about the proxy set the proxyserviceurl to point to the nsh proxy instance.
the first option is more scaleable and it means you don't have to worry about restarts of one instance/server affecting the whole env, which you would if there was only a single nsh proxy.
im rephrasing what you have written with the first solution
1 st server 1 config 1 job
2nd sever 1 job server
3rd 1 config 1 job
4th 1 job server
now i want to have 1 NSH proxy server on 2nd server that has only 1 Job server
in this case i just create a job execution rule for a AP job which marks towards these two 2nd server which has 1 job server and one NSH proxy server where in my JOB server will have ProxyServiceURLs settings updated?
correct me if im wrong?
1st Server: 1 CONFIG+NSH_PROXY instance, 1 JOB+NSH_PROXY instance
2nd Server: 1 JOB+NSH_PROXY instance
3rd Server 1 CONFIG+NSH_PROXY instance, 1 JOB+NSH_PROXY instance
4th Server 1 JOB+NSH_PROXY instance
and you can leave the proxyserviceurls settings blank.
when you create a new instance you can select ALL or any combination of job, config, proxy.
but in my case i don't want to have NSH proxy , but im forced to have as i need AP. and i need only one NSH proxy now. so in this case let me know what can be the solution ?
i think in that case i should go with the second idea of updating on all servers?
It sounds good. But, I just wanted to confirm "instead of making it a complex configuration, we may prefer to set ProxyServiceURLs on AppServers with no harm?"
Please correct me if I am wrong.
why do you want only 1 nsh proxy? why not have it on all boxes ?
if you have only a single nsh proxy, and then point all the appservers at it you can:
- overwhelm the proxy instance w/ connections
- have a single point of failure
currently its for AP use for agent instal. will that suffice?
You don’t need a nsh proxy for the agent installer job.
- Use of an automation principal requires an NSH proxy connected to the BMC Server Automation database. NSH operations that do not pass through an NSH proxy cannot use automation principals. In addition, a "standalone" NSH proxy, that is, an NSH proxy without access to the BMC Server Automation database, cannot use automation principals because it cannot retrieve the credentials from the database.
then what is this all about?
1 of 1 people found this helpful
That’s for nsh, file deploy, etc. not for the install jobs. there’s no agent on the target for the uai job.
is there a possibility that i can convert my existing config server to config+NSH proxy?
I think you can do a ‘redeploy’ but i’m not sure if you can add the proxy services. so you might have to delete and make a new one.