Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Accepted Solutions
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.
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.
