Is there a problem we are trying to solve or are we just validating the setup?
You have a load balancer for traffic from ARS->BAO and NOT for traffice from BAO->ARS right?
In the third bullet item, "set fields action", are you referring to traffic from BAO->ARS?
BAO in general has no idea if the request is arriving directly via Remedy, via a load balancer and/or via a proxy server. As long as request arrives, it services the request and returns the response. If you are able to achieve this then you can safely assume the set up is correct.
In the case of BAO->ARS, do we have any devices restricting communication?
We are trying to get it to work with the load balancer
We have the load balancer in front of the cdp and hacdp.
This connects to ARS server with no loadbalancer
The set fields action is in the ARS workflow that we are using to call the AO process
There is nothing in restricting communications between BAO-ARS. We confirmed this by setting the set fields to communicate straight to the CDP server and it worked. Just doesnt like the loadbalancer.
Hope this is clear
2 of 2 people found this helpful
Seems like your proxy server setting is incorrect. IMO, this has nothing to do with BAO or ARS. I am sure the set-fields request did not even arrive at BAO.
You will need to make exclusions in your proxy settings for those internal sites; your browser will then bypass the proxy and go directly to those internal sites.
Hello @Kevin Kujawa
We are facing the same issue.
As per this community update we checked regarding Proxy, but our's is internal domain, no proxy is blocking this request. We can access the link from Browser of AR Server, but it is not connecting through Remedy Dev Studio.
We are facing same issue, Can you please share details if it is resolved already.?
I am facing same issue, while putting the WSDL URL in Remedy Dev Studio for the creating Filter in set fields/
While loading the WSDL in "Datasource" we are consuming Atrium Orchestrator WSDL and then loading asks the "Web Server" login .
Putting credentials , it shows the error
Error Connecting to BMC Atrium Orchestrator Server.
Reason: (407) Proxy Authorization required (ARERR 5262)
Please let me know if the issue is resolved, bit urgent.
Open the BAO Service URL from the browser - Is it the Grid Manager URL we are talking about here.
you can try to access Grid Manager Console or the ORCA WSDL URL.
just to be sure, the use you configured in Orchestration Configuration form has the permissions assigned on Grid to view any modules?
I am assigning "aoadmin" in AO Configuration form.
how to assign permission on grid to view any modules, i hope AOADMIN has super privileges.