...
| Warning | ||
|---|---|---|
| ||
The agent that is connected to the CMR must match exactly at least one active mapping. If there is are zero or more than one matched active mappings, then agent will not be functional as the CMR is not able to deceide decide what Environment should be bounded to the agent. |
...
| Example | Description |
|---|---|
| Maps My Test Env to the agent(s) that are connected with the name MyAgent and have the IP address 192.168.0.126 as one of the network interface. |
| Maps My Test Env to the agent(s) that are connected the name that starts with MyApp. This will match for example agents with names: MyApp [Dev], MyApp Test, etc. The mappings also define that the agent is inside the 192.168.x.x sub-network. |
| Same as above, except it will match agents connected from any IP address. |
Order of agent mappings:
| Warning |
|---|
If there are more than one matching agent mappings for one agent, the first matching mapping will be used. |
You can change the order of the agent by using 
and 
.
Example:
An agent named "dvdstore" is mapped to "Custom Environment".
An agent named "blub" is mapped to "Default Environment"