MicroStrategy ONE
Changing the Monitoring Agent to a Communication Agent
You can change a monitoring agent to a communication agent by manually modifying the installation_list.yaml
file.
Manually modifying the installation_list.yaml
file to change the agent from a monitoring to a communication agent, or vice versa, is not recommended. Only a MicroStrategy administrator should manually modify installation_list.yaml
to correct input mistakes during installation or reconfigure the service registration agents in a cluster with manually deployed web applications.
During the installation, when selecting a multiple machine environment, the user must provide a list of communication agents. If the current machine where installation is running is not in the list, it is not configured as a communication agent. Instead, it is set as a monitoring agent only. If the Library server is manually deployed on a machine, the embedded service registration agent is configured as a monitoring agent by default.
Manually Change the Monitoring Agent to a Communication Agent
- After installation, navigate to the
MicroStrategy/Services Registration/yaml
directory. - Back up installation_list.yaml.
-
Open
installation_list.yaml
and locate the consul section.Copy---
consul:
install_path: "C:\\Program Files (x86)\\MicroStrategy\\Services Registration"
java_install_path: "C:\\Program Files (x86)\\Common Files\\MicroStrategy\\JRE\\180_192\\Win64\\bin"
retry_join:
- MachineA.corp.microstrategy.com
server: false
--- - Change the
server
value totrue
. - Add
retry_join:
in the consul section. List all communication agents' machine names in the field. See Specifying the Topology Communication Agent for more information. - Add
bootstrap_expect: <number>
in the consul section. See Specifying the Topology Communication Agent for more information.For a three communication agent cluster, the consul section looks like the following:
Copy---
consul:
install_path: "C:\\Program Files (x86)\\MicroStrategy\\Services Registration"
java_install_path: "C:\\Program Files (x86)\\Common Files\\MicroStrategy\\JRE\\180_192\\Win64\\bin"
retry_join:
- MachineA.corp.microstrategy.com
- MachineA.corp.microstrategy.com
- MachineA.corp.microstrategy.com
server: true
bootstrap_expect: 3
---For a one communication agent cluster, the consul section looks like the following:
Copy---
consul:
install_path: "C:\\Program Files (x86)\\MicroStrategy\\Services Registration"
java_install_path: "C:\\Program Files (x86)\\Common Files\\MicroStrategy\\JRE\\180_192\\Win64\\bin"
retry_join:
- MachineA.corp.microstrategy.com
server: true
bootstrap_expect: 1
---
- Modify
installation_list.yaml
on all machines in the same Services Registration cluster by including the name of this machine in theretry_join
list. Theretry_join
list andbootstrap_expect
value must be identical for all communication agents in the same consul cluster. - Stop Services Registration on all machines in the same consul cluster.
- In all the machines, navigate to the installation directory and delete
MicroStrategy/Services Registration/data
. - Restart Services Registration on all machines in the same consul cluster.
Manually Change the Communication Agent to a Monitoring Agent
- After installation, navigate to the
MicroStrategy/Services Registration/yaml
directory. - Back up
installation_list.yaml
. -
Open
installation_list.yaml
and locate the consul section.Copy---
consul:
install_path: "C:\\Program Files (x86)\\MicroStrategy\\Services Registration"
java_install_path: "C:\\Program Files (x86)\\Common Files\\MicroStrategy\\JRE\\180_192\\Win64\\bin"
retry_join:
- MachineA.corp.microstrategy.com
- MachineB.corp.microstrategy.com
- MachineC.corp.microstrategy.com
server: true
bootstrap_expect: 3
--- - Change the
server
value tofalse
. - Add
retry_join:
to the desired communication agent's FQDN. If it's an embedded Services Registration in the MicroStrategy Library deployment, only provide the FQDN of the Intelligence server machine Library connects to. - Remove
bootstrap_expect: <number>
in the consul section.For an embedded Services Registration in the MicroStrategy Library deployment, the consul section looks like the following:
Copy---
consul:
install_path: "C:\\Program Files (x86)\\MicroStrategy\\Services Registration"
java_install_path: "C:\\Program Files (x86)\\Common Files\\MicroStrategy\\JRE\\180_192\\Win64\\bin"
retry_join:
- MachineA.corp.microstrategy.com
server: false
---For a monitoring agent in a cluster of three communication agents, the consul section looks like the following:
Copy---
consul:
install_path: "C:\\Program Files (x86)\\MicroStrategy\\Services Registration"
java_install_path: "C:\\Program Files (x86)\\Common Files\\MicroStrategy\\JRE\\180_192\\Win64\\bin"
retry_join:
- MachineA.corp.microstrategy.com
- MachineB.corp.microstrategy.com
- MachineC.corp.microstrategy.com
server: false
---
- Modify
installation_list.yaml
on all machines in the same Services Registration cluster by including the name of this machine in theretry_join
list. Theretry_join
list andbootstrap_expect
value must be identical for all communication agents in the same consul cluster. - Stop Services Registration on all machines in the same consul cluster.
- In all the machines, navigate to the installation directory and delete
MicroStrategy/Services Registration/data
. - Restart Services Registration on all machines in the same consul cluster.