topic Re: Testing new node in Management & Governance

Testing new node

Pheaxx — Sat, 16 Nov 2024 04:38:57 GMT

Hi,

I got a new scheduler node, and i want to test all the data connections before this scheduler is being used to run tasks(as in, it goes into production use).

The reason I ask is because some connection are not working on this new node, while i can use the same settings and same objects, from the same machine with the same service account in SSMS without any issue.

So being able to use this new node in a kind of test mode would really help in testing in finding the cause.

Does anyone have an idea about something like this?

any other ideas are also welcome.

Regards,

Nick

Re: Testing new node

Levi_Turner — Fri, 20 Sep 2019 13:24:42 GMT

As far as I am aware there is not an obvious structured way of testing data connections. What you can do is the following:

Ensure that there are sufficient security rules for the account used here to access all data connections
Add the node into the cluster
- Enable the Proxy and Engine services
In QMC > Virtual Proxies, edit the default virtual proxy for this new node such that it load balances off only the new node's Engine
Access the new node's default virtual proxy (windows authentication)
Go into an existing app / create a new app
Navigate to the Data Load Editor
Attempt to load from every data connection

That's a pretty brute-forcey but simple way of accomplishing the task.

As an alternative, if you're familiar with the data connections, you can:

navigate to the QMC > Data Connections
Use the column selector and toggle off the tags column, add in the Connection String and type columns, like so:

From here you can make sure that things are setup for success. A rough outline of the warning signs:
- Type: folder which refer to drive paths (e.g. C:\Data). These will need to be converted to UNC paths so both nodes access a common location
- Type ODBC. Ensure that there is a DSN with the appropriate driver with the same name on the RIM
- Type OLE DB. Ensure that there are appropriate drivers if not using the core set of OLE DB providers which ship with the Windows Operating System
- Type: QvRestConnector. Ensure that the url parameter is not localhost. This will need to be converted to a machine name / FQDN which is resolvable by the RIM node.
- There are probably others but nothing else comes to mind at a first approximation

The second method obviously requires a bit of sophistication when it comes to knowing what these data sources are, etc so the first method may be easier to operationalize for many customers.

Re: Testing new node

Pheaxx — Mon, 23 Sep 2019 09:00:38 GMT

Hi @Levi_Turner

Thank you for your reply.

For your first solution, you mean adding it in the load balance section and then hitting it via the host/FQDN of that node?

Also, when you change proxy settings for a node, and you save changes, it then asks for restarting the proxy, is this only for the node in question or the whole proxy within an environment?

Regards,

Nick

Re: Testing new node

Levi_Turner — Mon, 23 Sep 2019 13:33:02 GMT

> For your first solution, you mean adding it in the load balance section and then hitting it via the host/FQDN of that node?

Yes. For example accessing https://rim1.company.com which is load balanced to RIM1's engine.

> Also, when you change proxy settings for a node, and you save changes, it then asks for restarting the proxy, is this only for the node in question or the whole proxy within an environment?

Just the proxies which are attached to the virtual proxy.

Re: Testing new node

Pheaxx — Wed, 25 Sep 2019 08:49:04 GMT

Thanks @Levi_Turner , first idea works like a charm!