Our client (who is running Arc+ as trial now) cannot connect two instances with the same name (“tm1”) from two different servers. They are on prem. We followed the instructions and used pulseinstance parameter in settings.yml. We have tried setting usepulseinstances to true and false, but no result. If we comment out one of the two connections, Arc+ connects to the other one. With both, Arc+ doesn’t show anything. Are we missing another setting we need to update?
Hi @ssarvartdinova,
What is the version of Arc you are using?
With later versions if Arc, they should be pulled from Pulse already. Otherwise, server groups should be the way to go with this.
Grouping TM1 servers and instances in Arc
cc: @aeremenko, @harvey
Cheers,
Paul
Just to expand on @plim’s answer, you can think of Server Groups as equivalent to Pulse’s Environments.
Setting the usepulseinstances property you mentioned to true instructs Arc to synchronize your Server Groups with your configured Pulse instances automatically. Using this configuration avoids the need for configuring a separate server-groups.yml file.
Just note there is a known bug connecting to IBM Cloud with usepulseinstances = true so YMMV in that scenario. We are currently working on that issue as a matter of priority as we speak.
The customer reported that they were able to find a workaround. When running Arc on Dev:
- specify an “adminhost” (localhost) that would automatically bring dev “tm1” instance in Arc
- specify a “connection” for Prod “tm1” instance with an alias “prod-tm1” (and remove connection to dev)
We don’t have access to their servers to try other suggestions at the moment.