How to Dynamic Map (Release Automation) Agents?

[Anon Anon]

Has anyone experience with the Dynamic Agent Mapping?

 

According to the Help dynamic mapping should be done like this:

 

To automatically map agents to the appropriate application and environment during a silent installation, configure agent.mapping.xml.

Follow these steps:

1. Create one additional input file per agent. Use the following example to create agent.mapping.xml:

   <?xml version="1.0" encoding="ISO-8859-1" ?> <agent-mapping> <application name="<APPLICATION NAME"> <environment name="<ENVIRONMENT NAME>"> <<SERVER TYPE>="Remote"/> </environment> </application> </agent-mapping> 

2. Copy or move the file to the NolioAutomationCenter/conf folder on the target agent.
   When the agent connects to the execution server, the application and environments are mapped to the agent according to agent.mapping.xml

 

This implies to me that needs to be done after installation of the Agent and before starting the Agent.

Has anyway successfully configured an Agent to be mapped to a specific Application/Environment/ServerType? For both a silent installed Agent and an already installed Agent?

The use case for this is, in our case, that we want to use Docker containers with a Agent pre-installed. The Agent should connect to a certain Application when the Docker container is started based on some parameters we can define using Docker.

[Jacky_Mahadab]

The usage of agent.mapping.xml relevant only for the first time the agent is start-up after installation (Note that I think you need to enable this option in the system settings as well, create DYNAMIC_AGENT_MAPPING_ENABLED and set it to True  and restart the RA server)

BTW when you doing silent install you can add options to map the agent to the environment ( -Vnolio.agent.mapping.application=MyAPP -Vnolio.agent.mapping.environment="Dev" -Vnolio.agent.mapping.servertype="IIS" )

In case you want to map the agents which already running or after just installation you can use SOAP call (mapInstanceToEnvironment)

Another option is to use RA actions that assign agent to environment

Thanks

Jacky

[Anon Anon]

Thanks Jacky for the reply.

I managed to find a solution, by changing the node_id of the installed agent the changes you will make in the agent.mapping.xml (which is created if you install the agent with the options) will be adopted after restarting the agent.

In a way it is replacing the agent with a new agent of course, but it is suitable for the use case we are looking into.

[Anon Anon]

Is it possible to assign multiple server types with the above command e.g -Vnolio.agent.mapping.servertype="IIS, WQ"