Hi Community.
I'm trying to figure out the agentspacks and deployment scripts examples (https://docs.automic.com/documentation/webhelp/english/ALL/components/DOCU/24.4.0/Automic%20Automation%20Guides/Content/AWA/AdministrationPerspective/AG_AgentDeploy_UnixScript.htm) with a multiple AE servers context.
The idea is to use the "pre-configured package" download feature, as described here (https://docs.automic.com/documentation/webhelp/english/ALL/components/DOCU/24.4.0/Automic%20Automation%20Guides/Content/REST_API/AE_REST_API_Using_WorkingWithAgents.htm).
The method is clever, and i'm producing a package with ini files pre-configured with the POST method agentpacks method.
The response is parsed, so i then get an url location to download this agent pack zip file. This works fine when you have a single REST process on a single AE server.
When you have two AE engines, each of them with a REST process, and using REST_ENDPOINT with a dns entry that points on a NLB :
- the first rest call (package generation) is handled by one of the REST process (AE1 or AE2).
- the response produced contains a location with the REST_ENDPOINT (uc_system_settings) in the url (fine)
- you then use the response location parameter to actually download the package (curl, wget, whatever...) and then
- if you are lucky and the NLB forwarded the download request on the same AE that handled the package API call - the download starts.
- if the NLB forwards the request on the second AE : you get a 404 not found error.
Note that i have a customer context where the most agents won't be able directly access the AE1 or the AE2 and must go through the NLB...
Are there any specific parameter to alter this behavior ? Any advice ?
------------------------------
Lionel TUAL [Sched. integration e.]
[@ITS Integra]
------------------------------