Is there any official documentation on Routing Rules precedence.

For example, I have a routing rule that sends Sales reports to Server A. I have another rule that sends Finance Users to Server B.

If a Finance user runs a Sales report, which server will they be sent to?

With my limited testing, it doesn't appear to be as simple as rule ordering. For example, if I set up rule 1 to route the Everyone role to Server A, and rule 2 as a datasource to Server B. Then running a report against the specified data source hits server B.

If it was as simple as rule orders, then everyone (and any report they run) should go to server A.

So is there some kind of precedence rules? Check to see if data source matches, if not then check roles, if not check groups?

Edited to add....

In some versions of the documentation this little nugget appears:  https://www.ibm.com/docs/el/cognos-analytics/11.2.0?topic=dr-setting-routing-rules-dispatchers

However, this isn't in all 11.2 documents.

My limited testing also implies that this isn't how it works.

------------------------------
Marc Reed
------------------------------

Hi,

I have only used the routing rules for groups.

Using only for user groups, the order on the configuration page is respected top-down.

However, there is a problem, routing rules do not work for dashboards. I've already opened a ticket and support responded to me begrudgingly, saying that it's normal behavior, despite me saying that it works for datasets and data modules. Also, it would have to work for dashboards, Cognos has always been like that anyway.

Regards,

Is there any official documentation on Routing Rules precedence.

For example, I have a routing rule that sends Sales reports to Server A. I have another rule that sends Finance Users to Server B.

If a Finance user runs a Sales report, which server will they be sent to?

With my limited testing, it doesn't appear to be as simple as rule ordering. For example, if I set up rule 1 to route the Everyone role to Server A, and rule 2 as a datasource to Server B. Then running a report against the specified data source hits server B.

If it was as simple as rule orders, then everyone (and any report they run) should go to server A.

So is there some kind of precedence rules? Check to see if data source matches, if not then check roles, if not check groups?

Edited to add....

In some versions of the documentation this little nugget appears:  https://www.ibm.com/docs/el/cognos-analytics/11.2.0?topic=dr-setting-routing-rules-dispatchers

However, this isn't in all 11.2 documents.

My limited testing also implies that this isn't how it works.

------------------------------
Marc Reed
------------------------------

Hi together,

I also know that Cognos processes routing rules top to bottom until the first routing rule applies to the scenario. 

Using the Everyone group for a routing rule on top may break the logic for rules as then no other rule would be used. Maybe Cognos is ignoring those rules? I don't know. In my setup I have two routing rules and they are processed top-down. Checked that with different scenarios. I'm on 11.1.7 FP6.

What I cannot confirm is that routing rules do not work for dashboards. In my environment they do! The different dispatchers are tied to routing rules which use user roles. I have to send all users with an Analytics Viewer license (to use dashboards) to a distinct dispatcher. Works great.

Hi,

I have only used the routing rules for groups.

Using only for user groups, the order on the configuration page is respected top-down.

However, there is a problem, routing rules do not work for dashboards. I've already opened a ticket and support responded to me begrudgingly, saying that it's normal behavior, despite me saying that it works for datasets and data modules. Also, it would have to work for dashboards, Cognos has always been like that anyway.

Regards,

Is there any official documentation on Routing Rules precedence.

For example, I have a routing rule that sends Sales reports to Server A. I have another rule that sends Finance Users to Server B.

If a Finance user runs a Sales report, which server will they be sent to?

With my limited testing, it doesn't appear to be as simple as rule ordering. For example, if I set up rule 1 to route the Everyone role to Server A, and rule 2 as a datasource to Server B. Then running a report against the specified data source hits server B.

If it was as simple as rule orders, then everyone (and any report they run) should go to server A.

So is there some kind of precedence rules? Check to see if data source matches, if not then check roles, if not check groups?

Edited to add....

In some versions of the documentation this little nugget appears:  https://www.ibm.com/docs/el/cognos-analytics/11.2.0?topic=dr-setting-routing-rules-dispatchers

However, this isn't in all 11.2 documents.

My limited testing also implies that this isn't how it works.

------------------------------
Marc Reed
------------------------------

Hi, Robert.

I'm sorry, but they don't work. I proved this to IBM support and developers.

In my case, as I have 8 servers, I'm using Cognos Gateway with Apache, loading the cognos-load-balance configuration. This can mask the effects of this issue.

In the case of the dashboard, Cognos always runs it in the dispatcher that you connected to, that is, it was directed by Apache. The behavior is the same if you access the dispatcher directly.

There is a simple test you can see this happening. You will see that the routing rule works in the report, but not in the dashboard.

- Create a blank dashboard, with any module as datasource.
- Then create a calculation with the following expression:

#sq( getConfigurationEntry ('externalDispatcher' ))#

- Drag this calculation to your dashboard and save.

- Create a list report, using the same data source as the panel.
- Create a data item with the same calculation

#sq( getConfigurationEntry ('externalDispatcher' ))#

- Drop this calculation on the report page and save.

Now let's go to the tests. Remembering that accessing through the gateway can confuse you with the results, let's access the dispatchers through their URL.

- Access the DISPATCHER_B URL (http://dispacther_b:9300/bi), using a user that should be routed to DISPATCHER_A
- Run the report many times. You will see that the execution is routed to DISPATCHER_A.
- Run the dashboard. You will see that it was executed by DISPATCHER_B, always.

Continuing the tests:

- Access the DISPATCHER_A URL (http://dispacther_a:9300/bi), using a user that should be routed to DISPATCHER_B
- Run the report many times. You will see that the execution is routed to DISPATCHER_B.
- Run the dashboard. You will see that it was run by DISPATCHER_A, always.

In summary, the behavior is as follows:

Routing rules work for the report. However, the dashboard is always executed by the dispatcher you connected to.

Hi together,

I also know that Cognos processes routing rules top to bottom until the first routing rule applies to the scenario. 

Using the Everyone group for a routing rule on top may break the logic for rules as then no other rule would be used. Maybe Cognos is ignoring those rules? I don't know. In my setup I have two routing rules and they are processed top-down. Checked that with different scenarios. I'm on 11.1.7 FP6.

What I cannot confirm is that routing rules do not work for dashboards. In my environment they do! The different dispatchers are tied to routing rules which use user roles. I have to send all users with an Analytics Viewer license (to use dashboards) to a distinct dispatcher. Works great.

Hi,

I have only used the routing rules for groups.

Using only for user groups, the order on the configuration page is respected top-down.

However, there is a problem, routing rules do not work for dashboards. I've already opened a ticket and support responded to me begrudgingly, saying that it's normal behavior, despite me saying that it works for datasets and data modules. Also, it would have to work for dashboards, Cognos has always been like that anyway.

Regards,

Is there any official documentation on Routing Rules precedence.

For example, I have a routing rule that sends Sales reports to Server A. I have another rule that sends Finance Users to Server B.

If a Finance user runs a Sales report, which server will they be sent to?

With my limited testing, it doesn't appear to be as simple as rule ordering. For example, if I set up rule 1 to route the Everyone role to Server A, and rule 2 as a datasource to Server B. Then running a report against the specified data source hits server B.

If it was as simple as rule orders, then everyone (and any report they run) should go to server A.

So is there some kind of precedence rules? Check to see if data source matches, if not then check roles, if not check groups?

Edited to add....

In some versions of the documentation this little nugget appears:  https://www.ibm.com/docs/el/cognos-analytics/11.2.0?topic=dr-setting-routing-rules-dispatchers

However, this isn't in all 11.2 documents.

My limited testing also implies that this isn't how it works.

------------------------------
Marc Reed
------------------------------

Hi Jeam,

thank you for your additional information re gateway with Apache and your testings.

I've tested the setup here with 11.1.7 like you've suggested with #sq( getConfigurationEntry ('externalDispatcher' ))# in a dashboard and I have to confirm my initial quote: it still works! I log in as regular user and dispatcher A comes up in the dashboard. When I use another special user configured to use the second dispatcher, I see exactly that dispatcher URL in the same dashboard.

So: this could be something that happens due to your usage of an Apache gateway whilst I'm using IIS. We also do not (never ever) let our users access Cognos via any direct dispatcher URL. It's always the IIS gateway. Maybe that's a reason why it works perfectly on our end.

Hi, Robert.

I'm sorry, but they don't work. I proved this to IBM support and developers.

In my case, as I have 8 servers, I'm using Cognos Gateway with Apache, loading the cognos-load-balance configuration. This can mask the effects of this issue.

In the case of the dashboard, Cognos always runs it in the dispatcher that you connected to, that is, it was directed by Apache. The behavior is the same if you access the dispatcher directly.

There is a simple test you can see this happening. You will see that the routing rule works in the report, but not in the dashboard.

- Create a blank dashboard, with any module as datasource.
- Then create a calculation with the following expression:

#sq( getConfigurationEntry ('externalDispatcher' ))#

- Drag this calculation to your dashboard and save.

- Create a list report, using the same data source as the panel.
- Create a data item with the same calculation

#sq( getConfigurationEntry ('externalDispatcher' ))#

- Drop this calculation on the report page and save.

Now let's go to the tests. Remembering that accessing through the gateway can confuse you with the results, let's access the dispatchers through their URL.

- Access the DISPATCHER_B URL (http://dispacther_b:9300/bi), using a user that should be routed to DISPATCHER_A
- Run the report many times. You will see that the execution is routed to DISPATCHER_A.
- Run the dashboard. You will see that it was executed by DISPATCHER_B, always.

Continuing the tests:

- Access the DISPATCHER_A URL (http://dispacther_a:9300/bi), using a user that should be routed to DISPATCHER_B
- Run the report many times. You will see that the execution is routed to DISPATCHER_B.
- Run the dashboard. You will see that it was run by DISPATCHER_A, always.

In summary, the behavior is as follows:

Routing rules work for the report. However, the dashboard is always executed by the dispatcher you connected to.

Hi together,

I also know that Cognos processes routing rules top to bottom until the first routing rule applies to the scenario. 

Using the Everyone group for a routing rule on top may break the logic for rules as then no other rule would be used. Maybe Cognos is ignoring those rules? I don't know. In my setup I have two routing rules and they are processed top-down. Checked that with different scenarios. I'm on 11.1.7 FP6.

What I cannot confirm is that routing rules do not work for dashboards. In my environment they do! The different dispatchers are tied to routing rules which use user roles. I have to send all users with an Analytics Viewer license (to use dashboards) to a distinct dispatcher. Works great.

Hi,

I have only used the routing rules for groups.

Using only for user groups, the order on the configuration page is respected top-down.

However, there is a problem, routing rules do not work for dashboards. I've already opened a ticket and support responded to me begrudgingly, saying that it's normal behavior, despite me saying that it works for datasets and data modules. Also, it would have to work for dashboards, Cognos has always been like that anyway.

Regards,

Is there any official documentation on Routing Rules precedence.

For example, I have a routing rule that sends Sales reports to Server A. I have another rule that sends Finance Users to Server B.

If a Finance user runs a Sales report, which server will they be sent to?

With my limited testing, it doesn't appear to be as simple as rule ordering. For example, if I set up rule 1 to route the Everyone role to Server A, and rule 2 as a datasource to Server B. Then running a report against the specified data source hits server B.

If it was as simple as rule orders, then everyone (and any report they run) should go to server A.

So is there some kind of precedence rules? Check to see if data source matches, if not then check roles, if not check groups?

Edited to add....

In some versions of the documentation this little nugget appears:  https://www.ibm.com/docs/el/cognos-analytics/11.2.0?topic=dr-setting-routing-rules-dispatchers

However, this isn't in all 11.2 documents.

My limited testing also implies that this isn't how it works.

------------------------------
Marc Reed
------------------------------

Hi, Robert!

In fact, the web server/gateway is not a problem. But as they have their balancing algorithm, they can mask it.

Did you run the tests directly accessing the dispatcher URL, without going through the gateway?

BTW, I'm in CA 11.2.1 zLinux.

Hi Jeam,

thank you for your additional information re gateway with Apache and your testings.

I've tested the setup here with 11.1.7 like you've suggested with #sq( getConfigurationEntry ('externalDispatcher' ))# in a dashboard and I have to confirm my initial quote: it still works! I log in as regular user and dispatcher A comes up in the dashboard. When I use another special user configured to use the second dispatcher, I see exactly that dispatcher URL in the same dashboard.

So: this could be something that happens due to your usage of an Apache gateway whilst I'm using IIS. We also do not (never ever) let our users access Cognos via any direct dispatcher URL. It's always the IIS gateway. Maybe that's a reason why it works perfectly on our end.

Hi, Robert.

I'm sorry, but they don't work. I proved this to IBM support and developers.

In my case, as I have 8 servers, I'm using Cognos Gateway with Apache, loading the cognos-load-balance configuration. This can mask the effects of this issue.

In the case of the dashboard, Cognos always runs it in the dispatcher that you connected to, that is, it was directed by Apache. The behavior is the same if you access the dispatcher directly.

There is a simple test you can see this happening. You will see that the routing rule works in the report, but not in the dashboard.

- Create a blank dashboard, with any module as datasource.
- Then create a calculation with the following expression:

#sq( getConfigurationEntry ('externalDispatcher' ))#

- Drag this calculation to your dashboard and save.

- Create a list report, using the same data source as the panel.
- Create a data item with the same calculation

#sq( getConfigurationEntry ('externalDispatcher' ))#

- Drop this calculation on the report page and save.

Now let's go to the tests. Remembering that accessing through the gateway can confuse you with the results, let's access the dispatchers through their URL.

- Access the DISPATCHER_B URL (http://dispacther_b:9300/bi), using a user that should be routed to DISPATCHER_A
- Run the report many times. You will see that the execution is routed to DISPATCHER_A.
- Run the dashboard. You will see that it was executed by DISPATCHER_B, always.

Continuing the tests:

- Access the DISPATCHER_A URL (http://dispacther_a:9300/bi), using a user that should be routed to DISPATCHER_B
- Run the report many times. You will see that the execution is routed to DISPATCHER_B.
- Run the dashboard. You will see that it was run by DISPATCHER_A, always.

In summary, the behavior is as follows:

Routing rules work for the report. However, the dashboard is always executed by the dispatcher you connected to.

Hi together,

I also know that Cognos processes routing rules top to bottom until the first routing rule applies to the scenario. 

Using the Everyone group for a routing rule on top may break the logic for rules as then no other rule would be used. Maybe Cognos is ignoring those rules? I don't know. In my setup I have two routing rules and they are processed top-down. Checked that with different scenarios. I'm on 11.1.7 FP6.

What I cannot confirm is that routing rules do not work for dashboards. In my environment they do! The different dispatchers are tied to routing rules which use user roles. I have to send all users with an Analytics Viewer license (to use dashboards) to a distinct dispatcher. Works great.

Hi,

I have only used the routing rules for groups.

Using only for user groups, the order on the configuration page is respected top-down.

However, there is a problem, routing rules do not work for dashboards. I've already opened a ticket and support responded to me begrudgingly, saying that it's normal behavior, despite me saying that it works for datasets and data modules. Also, it would have to work for dashboards, Cognos has always been like that anyway.

Regards,

Is there any official documentation on Routing Rules precedence.

For example, I have a routing rule that sends Sales reports to Server A. I have another rule that sends Finance Users to Server B.

If a Finance user runs a Sales report, which server will they be sent to?

With my limited testing, it doesn't appear to be as simple as rule ordering. For example, if I set up rule 1 to route the Everyone role to Server A, and rule 2 as a datasource to Server B. Then running a report against the specified data source hits server B.

If it was as simple as rule orders, then everyone (and any report they run) should go to server A.

So is there some kind of precedence rules? Check to see if data source matches, if not then check roles, if not check groups?

Edited to add....

In some versions of the documentation this little nugget appears:  https://www.ibm.com/docs/el/cognos-analytics/11.2.0?topic=dr-setting-routing-rules-dispatchers

However, this isn't in all 11.2 documents.

My limited testing also implies that this isn't how it works.

------------------------------
Marc Reed
------------------------------

Hi Jeam,

yes I also run the test directly using both dispatcher URLs. Now it depends on how I point to the dispatchers. The routing rules work with FQDN URLs only, but if I use the short ones it's always the second dispatcher which executes the queries. Have you checked on the dispatcher URLs in your browser and the ones in your Cognos Configuration? Both dispatchers run on Windows Server OS here.

Hi, Robert!

In fact, the web server/gateway is not a problem. But as they have their balancing algorithm, they can mask it.

Did you run the tests directly accessing the dispatcher URL, without going through the gateway?

BTW, I'm in CA 11.2.1 zLinux.

Hi Jeam,

thank you for your additional information re gateway with Apache and your testings.

I've tested the setup here with 11.1.7 like you've suggested with #sq( getConfigurationEntry ('externalDispatcher' ))# in a dashboard and I have to confirm my initial quote: it still works! I log in as regular user and dispatcher A comes up in the dashboard. When I use another special user configured to use the second dispatcher, I see exactly that dispatcher URL in the same dashboard.

So: this could be something that happens due to your usage of an Apache gateway whilst I'm using IIS. We also do not (never ever) let our users access Cognos via any direct dispatcher URL. It's always the IIS gateway. Maybe that's a reason why it works perfectly on our end.

Hi, Robert.

I'm sorry, but they don't work. I proved this to IBM support and developers.

In my case, as I have 8 servers, I'm using Cognos Gateway with Apache, loading the cognos-load-balance configuration. This can mask the effects of this issue.

In the case of the dashboard, Cognos always runs it in the dispatcher that you connected to, that is, it was directed by Apache. The behavior is the same if you access the dispatcher directly.

There is a simple test you can see this happening. You will see that the routing rule works in the report, but not in the dashboard.

- Create a blank dashboard, with any module as datasource.
- Then create a calculation with the following expression:

#sq( getConfigurationEntry ('externalDispatcher' ))#

- Drag this calculation to your dashboard and save.

- Create a list report, using the same data source as the panel.
- Create a data item with the same calculation

#sq( getConfigurationEntry ('externalDispatcher' ))#

- Drop this calculation on the report page and save.

Now let's go to the tests. Remembering that accessing through the gateway can confuse you with the results, let's access the dispatchers through their URL.

- Access the DISPATCHER_B URL (http://dispacther_b:9300/bi), using a user that should be routed to DISPATCHER_A
- Run the report many times. You will see that the execution is routed to DISPATCHER_A.
- Run the dashboard. You will see that it was executed by DISPATCHER_B, always.

Continuing the tests:

- Access the DISPATCHER_A URL (http://dispacther_a:9300/bi), using a user that should be routed to DISPATCHER_B
- Run the report many times. You will see that the execution is routed to DISPATCHER_B.
- Run the dashboard. You will see that it was run by DISPATCHER_A, always.

In summary, the behavior is as follows:

Routing rules work for the report. However, the dashboard is always executed by the dispatcher you connected to.

Hi together,

I also know that Cognos processes routing rules top to bottom until the first routing rule applies to the scenario. 

Using the Everyone group for a routing rule on top may break the logic for rules as then no other rule would be used. Maybe Cognos is ignoring those rules? I don't know. In my setup I have two routing rules and they are processed top-down. Checked that with different scenarios. I'm on 11.1.7 FP6.

What I cannot confirm is that routing rules do not work for dashboards. In my environment they do! The different dispatchers are tied to routing rules which use user roles. I have to send all users with an Analytics Viewer license (to use dashboards) to a distinct dispatcher. Works great.

Hi,

I have only used the routing rules for groups.

Using only for user groups, the order on the configuration page is respected top-down.

However, there is a problem, routing rules do not work for dashboards. I've already opened a ticket and support responded to me begrudgingly, saying that it's normal behavior, despite me saying that it works for datasets and data modules. Also, it would have to work for dashboards, Cognos has always been like that anyway.

Regards,

Is there any official documentation on Routing Rules precedence.

For example, I have a routing rule that sends Sales reports to Server A. I have another rule that sends Finance Users to Server B.

If a Finance user runs a Sales report, which server will they be sent to?

With my limited testing, it doesn't appear to be as simple as rule ordering. For example, if I set up rule 1 to route the Everyone role to Server A, and rule 2 as a datasource to Server B. Then running a report against the specified data source hits server B.

If it was as simple as rule orders, then everyone (and any report they run) should go to server A.

So is there some kind of precedence rules? Check to see if data source matches, if not then check roles, if not check groups?

Edited to add....

In some versions of the documentation this little nugget appears:  https://www.ibm.com/docs/el/cognos-analytics/11.2.0?topic=dr-setting-routing-rules-dispatchers

However, this isn't in all 11.2 documents.

My limited testing also implies that this isn't how it works.

------------------------------
Marc Reed
------------------------------

Hi Robert,

I'm using FQDN too, browser and Cognos Configuration. I have tested with IBM support and they see the same behavior that I'm getting.

It's strange that Cognos is differentiating the URL you enter in the browser, it shouldn't do that. Cognos should only go by its own settings.

Did you try run dashboard several times to see behavior? 

Hi Jeam,

yes I also run the test directly using both dispatcher URLs. Now it depends on how I point to the dispatchers. The routing rules work with FQDN URLs only, but if I use the short ones it's always the second dispatcher which executes the queries. Have you checked on the dispatcher URLs in your browser and the ones in your Cognos Configuration? Both dispatchers run on Windows Server OS here.

Hi, Robert!

In fact, the web server/gateway is not a problem. But as they have their balancing algorithm, they can mask it.

Did you run the tests directly accessing the dispatcher URL, without going through the gateway?

BTW, I'm in CA 11.2.1 zLinux.

Hi Jeam,

thank you for your additional information re gateway with Apache and your testings.

I've tested the setup here with 11.1.7 like you've suggested with #sq( getConfigurationEntry ('externalDispatcher' ))# in a dashboard and I have to confirm my initial quote: it still works! I log in as regular user and dispatcher A comes up in the dashboard. When I use another special user configured to use the second dispatcher, I see exactly that dispatcher URL in the same dashboard.

So: this could be something that happens due to your usage of an Apache gateway whilst I'm using IIS. We also do not (never ever) let our users access Cognos via any direct dispatcher URL. It's always the IIS gateway. Maybe that's a reason why it works perfectly on our end.

Hi, Robert.

I'm sorry, but they don't work. I proved this to IBM support and developers.

In my case, as I have 8 servers, I'm using Cognos Gateway with Apache, loading the cognos-load-balance configuration. This can mask the effects of this issue.

In the case of the dashboard, Cognos always runs it in the dispatcher that you connected to, that is, it was directed by Apache. The behavior is the same if you access the dispatcher directly.

There is a simple test you can see this happening. You will see that the routing rule works in the report, but not in the dashboard.

- Create a blank dashboard, with any module as datasource.
- Then create a calculation with the following expression:

#sq( getConfigurationEntry ('externalDispatcher' ))#

- Drag this calculation to your dashboard and save.

- Create a list report, using the same data source as the panel.
- Create a data item with the same calculation

#sq( getConfigurationEntry ('externalDispatcher' ))#

- Drop this calculation on the report page and save.

Now let's go to the tests. Remembering that accessing through the gateway can confuse you with the results, let's access the dispatchers through their URL.

- Access the DISPATCHER_B URL (http://dispacther_b:9300/bi), using a user that should be routed to DISPATCHER_A
- Run the report many times. You will see that the execution is routed to DISPATCHER_A.
- Run the dashboard. You will see that it was executed by DISPATCHER_B, always.

Continuing the tests:

- Access the DISPATCHER_A URL (http://dispacther_a:9300/bi), using a user that should be routed to DISPATCHER_B
- Run the report many times. You will see that the execution is routed to DISPATCHER_B.
- Run the dashboard. You will see that it was run by DISPATCHER_A, always.

In summary, the behavior is as follows:

Routing rules work for the report. However, the dashboard is always executed by the dispatcher you connected to.

Hi together,

I also know that Cognos processes routing rules top to bottom until the first routing rule applies to the scenario. 

Using the Everyone group for a routing rule on top may break the logic for rules as then no other rule would be used. Maybe Cognos is ignoring those rules? I don't know. In my setup I have two routing rules and they are processed top-down. Checked that with different scenarios. I'm on 11.1.7 FP6.

What I cannot confirm is that routing rules do not work for dashboards. In my environment they do! The different dispatchers are tied to routing rules which use user roles. I have to send all users with an Analytics Viewer license (to use dashboards) to a distinct dispatcher. Works great.

Hi,

I have only used the routing rules for groups.

Using only for user groups, the order on the configuration page is respected top-down.

However, there is a problem, routing rules do not work for dashboards. I've already opened a ticket and support responded to me begrudgingly, saying that it's normal behavior, despite me saying that it works for datasets and data modules. Also, it would have to work for dashboards, Cognos has always been like that anyway.

Regards,

Is there any official documentation on Routing Rules precedence.

For example, I have a routing rule that sends Sales reports to Server A. I have another rule that sends Finance Users to Server B.

If a Finance user runs a Sales report, which server will they be sent to?

With my limited testing, it doesn't appear to be as simple as rule ordering. For example, if I set up rule 1 to route the Everyone role to Server A, and rule 2 as a datasource to Server B. Then running a report against the specified data source hits server B.

If it was as simple as rule orders, then everyone (and any report they run) should go to server A.

So is there some kind of precedence rules? Check to see if data source matches, if not then check roles, if not check groups?

Edited to add....

In some versions of the documentation this little nugget appears:  https://www.ibm.com/docs/el/cognos-analytics/11.2.0?topic=dr-setting-routing-rules-dispatchers

However, this isn't in all 11.2 documents.

My limited testing also implies that this isn't how it works.

------------------------------
Marc Reed
------------------------------

Hi Jeam,

yep I reproduced the setting a few times and it repeats as described. Routing rules via IIS gateway and FQDN dispatcher seems to work properly. Sorry that I can't give you more hints about this issue but I'll keep an eye on that when we upgrade to V12.

Hi Robert,

I'm using FQDN too, browser and Cognos Configuration. I have tested with IBM support and they see the same behavior that I'm getting.

It's strange that Cognos is differentiating the URL you enter in the browser, it shouldn't do that. Cognos should only go by its own settings.

Did you try run dashboard several times to see behavior? 

Hi Jeam,

yes I also run the test directly using both dispatcher URLs. Now it depends on how I point to the dispatchers. The routing rules work with FQDN URLs only, but if I use the short ones it's always the second dispatcher which executes the queries. Have you checked on the dispatcher URLs in your browser and the ones in your Cognos Configuration? Both dispatchers run on Windows Server OS here.

Hi, Robert!

In fact, the web server/gateway is not a problem. But as they have their balancing algorithm, they can mask it.

Did you run the tests directly accessing the dispatcher URL, without going through the gateway?

BTW, I'm in CA 11.2.1 zLinux.

Hi Jeam,

thank you for your additional information re gateway with Apache and your testings.

I've tested the setup here with 11.1.7 like you've suggested with #sq( getConfigurationEntry ('externalDispatcher' ))# in a dashboard and I have to confirm my initial quote: it still works! I log in as regular user and dispatcher A comes up in the dashboard. When I use another special user configured to use the second dispatcher, I see exactly that dispatcher URL in the same dashboard.

So: this could be something that happens due to your usage of an Apache gateway whilst I'm using IIS. We also do not (never ever) let our users access Cognos via any direct dispatcher URL. It's always the IIS gateway. Maybe that's a reason why it works perfectly on our end.

Hi, Robert.

I'm sorry, but they don't work. I proved this to IBM support and developers.

In my case, as I have 8 servers, I'm using Cognos Gateway with Apache, loading the cognos-load-balance configuration. This can mask the effects of this issue.

In the case of the dashboard, Cognos always runs it in the dispatcher that you connected to, that is, it was directed by Apache. The behavior is the same if you access the dispatcher directly.

There is a simple test you can see this happening. You will see that the routing rule works in the report, but not in the dashboard.

- Create a blank dashboard, with any module as datasource.
- Then create a calculation with the following expression:

#sq( getConfigurationEntry ('externalDispatcher' ))#

- Drag this calculation to your dashboard and save.

- Create a list report, using the same data source as the panel.
- Create a data item with the same calculation

#sq( getConfigurationEntry ('externalDispatcher' ))#

- Drop this calculation on the report page and save.

Now let's go to the tests. Remembering that accessing through the gateway can confuse you with the results, let's access the dispatchers through their URL.

- Access the DISPATCHER_B URL (http://dispacther_b:9300/bi), using a user that should be routed to DISPATCHER_A
- Run the report many times. You will see that the execution is routed to DISPATCHER_A.
- Run the dashboard. You will see that it was executed by DISPATCHER_B, always.

Continuing the tests:

- Access the DISPATCHER_A URL (http://dispacther_a:9300/bi), using a user that should be routed to DISPATCHER_B
- Run the report many times. You will see that the execution is routed to DISPATCHER_B.
- Run the dashboard. You will see that it was run by DISPATCHER_A, always.

In summary, the behavior is as follows:

Routing rules work for the report. However, the dashboard is always executed by the dispatcher you connected to.

Hi together,

I also know that Cognos processes routing rules top to bottom until the first routing rule applies to the scenario. 

Using the Everyone group for a routing rule on top may break the logic for rules as then no other rule would be used. Maybe Cognos is ignoring those rules? I don't know. In my setup I have two routing rules and they are processed top-down. Checked that with different scenarios. I'm on 11.1.7 FP6.

What I cannot confirm is that routing rules do not work for dashboards. In my environment they do! The different dispatchers are tied to routing rules which use user roles. I have to send all users with an Analytics Viewer license (to use dashboards) to a distinct dispatcher. Works great.

Hi,

I have only used the routing rules for groups.

Using only for user groups, the order on the configuration page is respected top-down.

However, there is a problem, routing rules do not work for dashboards. I've already opened a ticket and support responded to me begrudgingly, saying that it's normal behavior, despite me saying that it works for datasets and data modules. Also, it would have to work for dashboards, Cognos has always been like that anyway.

Regards,

Is there any official documentation on Routing Rules precedence.

For example, I have a routing rule that sends Sales reports to Server A. I have another rule that sends Finance Users to Server B.

If a Finance user runs a Sales report, which server will they be sent to?

With my limited testing, it doesn't appear to be as simple as rule ordering. For example, if I set up rule 1 to route the Everyone role to Server A, and rule 2 as a datasource to Server B. Then running a report against the specified data source hits server B.

If it was as simple as rule orders, then everyone (and any report they run) should go to server A.

So is there some kind of precedence rules? Check to see if data source matches, if not then check roles, if not check groups?

Edited to add....

In some versions of the documentation this little nugget appears:  https://www.ibm.com/docs/el/cognos-analytics/11.2.0?topic=dr-setting-routing-rules-dispatchers

However, this isn't in all 11.2 documents.

My limited testing also implies that this isn't how it works.

------------------------------
Marc Reed
------------------------------

Is there any official documentation on Routing Rules precedence.

For example, I have a routing rule that sends Sales reports to Server A. I have another rule that sends Finance Users to Server B.

If a Finance user runs a Sales report, which server will they be sent to?

With my limited testing, it doesn't appear to be as simple as rule ordering. For example, if I set up rule 1 to route the Everyone role to Server A, and rule 2 as a datasource to Server B. Then running a report against the specified data source hits server B.

If it was as simple as rule orders, then everyone (and any report they run) should go to server A.

So is there some kind of precedence rules? Check to see if data source matches, if not then check roles, if not check groups?

Edited to add....

In some versions of the documentation this little nugget appears:  https://www.ibm.com/docs/el/cognos-analytics/11.2.0?topic=dr-setting-routing-rules-dispatchers

However, this isn't in all 11.2 documents.

My limited testing also implies that this isn't how it works.

------------------------------
Marc Reed
------------------------------

It looks that whilst IBM have incorporated Routing Sets into the the new Glass interface, they need to have a thing about the fundamentals of routing sets. The tech seems to be based on the old days of reports with a single datasource. But these days we have:

1. Dashboards with multiple data sources
2. Reports with multiple data sources 
3. User created data

Given that a report is sent to a dispatcher - what would happen if it contained a data source sent to dispatcher A and a datasource sent to dispatcher B?

To comment on my routing rule for the Everyone group...In the old world all your data would be FM packages. You would set up routing sets for these known FM packages. You could be guaranteed you would have routing rules defined for all your data. Now that users can create their own datasources (their own data modules, copies of data modules uploaded files etc), there is a potential for there to be data that isnt in a routing rule, so you could end up with reports being sent to 'round robin' servers. I want a catch all rule so that any user created data is sent to a catchall server. Hence using the everyone group.

I know that the everyone Group would be the last rule I want to be checked. Hence the question about precedence. I was testing precedence by placing this first just to see if there was any precedence rule.

I think I'll open a support call to get the official word - then I can raise a few bugs.

Is there any official documentation on Routing Rules precedence.

For example, I have a routing rule that sends Sales reports to Server A. I have another rule that sends Finance Users to Server B.

If a Finance user runs a Sales report, which server will they be sent to?

With my limited testing, it doesn't appear to be as simple as rule ordering. For example, if I set up rule 1 to route the Everyone role to Server A, and rule 2 as a datasource to Server B. Then running a report against the specified data source hits server B.

If it was as simple as rule orders, then everyone (and any report they run) should go to server A.

So is there some kind of precedence rules? Check to see if data source matches, if not then check roles, if not check groups?

Edited to add....

In some versions of the documentation this little nugget appears:  https://www.ibm.com/docs/el/cognos-analytics/11.2.0?topic=dr-setting-routing-rules-dispatchers

However, this isn't in all 11.2 documents.

My limited testing also implies that this isn't how it works.

------------------------------
Marc Reed
------------------------------

Is there any official documentation on Routing Rules precedence.

For example, I have a routing rule that sends Sales reports to Server A. I have another rule that sends Finance Users to Server B.

If a Finance user runs a Sales report, which server will they be sent to?

With my limited testing, it doesn't appear to be as simple as rule ordering. For example, if I set up rule 1 to route the Everyone role to Server A, and rule 2 as a datasource to Server B. Then running a report against the specified data source hits server B.

If it was as simple as rule orders, then everyone (and any report they run) should go to server A.

So is there some kind of precedence rules? Check to see if data source matches, if not then check roles, if not check groups?

Edited to add....

In some versions of the documentation this little nugget appears:  https://www.ibm.com/docs/el/cognos-analytics/11.2.0?topic=dr-setting-routing-rules-dispatchers

However, this isn't in all 11.2 documents.

My limited testing also implies that this isn't how it works.

------------------------------
Marc Reed
------------------------------

For anyone interested, here is the IBM reponse on routing rules...

Is there any official documentation on Routing Rules precedence.

For example, I have a routing rule that sends Sales reports to Server A. I have another rule that sends Finance Users to Server B.

If a Finance user runs a Sales report, which server will they be sent to?

With my limited testing, it doesn't appear to be as simple as rule ordering. For example, if I set up rule 1 to route the Everyone role to Server A, and rule 2 as a datasource to Server B. Then running a report against the specified data source hits server B.

If it was as simple as rule orders, then everyone (and any report they run) should go to server A.

So is there some kind of precedence rules? Check to see if data source matches, if not then check roles, if not check groups?

Edited to add....

In some versions of the documentation this little nugget appears:  https://www.ibm.com/docs/el/cognos-analytics/11.2.0?topic=dr-setting-routing-rules-dispatchers

However, this isn't in all 11.2 documents.

My limited testing also implies that this isn't how it works.

------------------------------
Marc Reed
------------------------------

For anyone interested, here is the IBM reponse on routing rules...

Is there any official documentation on Routing Rules precedence.

For example, I have a routing rule that sends Sales reports to Server A. I have another rule that sends Finance Users to Server B.

If a Finance user runs a Sales report, which server will they be sent to?

With my limited testing, it doesn't appear to be as simple as rule ordering. For example, if I set up rule 1 to route the Everyone role to Server A, and rule 2 as a datasource to Server B. Then running a report against the specified data source hits server B.

If it was as simple as rule orders, then everyone (and any report they run) should go to server A.

So is there some kind of precedence rules? Check to see if data source matches, if not then check roles, if not check groups?

Edited to add....

In some versions of the documentation this little nugget appears:  https://www.ibm.com/docs/el/cognos-analytics/11.2.0?topic=dr-setting-routing-rules-dispatchers

However, this isn't in all 11.2 documents.

My limited testing also implies that this isn't how it works.

------------------------------
Marc Reed
------------------------------

Is there any official documentation on Routing Rules precedence.

For example, I have a routing rule that sends Sales reports to Server A. I have another rule that sends Finance Users to Server B.

If a Finance user runs a Sales report, which server will they be sent to?

With my limited testing, it doesn't appear to be as simple as rule ordering. For example, if I set up rule 1 to route the Everyone role to Server A, and rule 2 as a datasource to Server B. Then running a report against the specified data source hits server B.

If it was as simple as rule orders, then everyone (and any report they run) should go to server A.

So is there some kind of precedence rules? Check to see if data source matches, if not then check roles, if not check groups?

Edited to add....

In some versions of the documentation this little nugget appears:  https://www.ibm.com/docs/el/cognos-analytics/11.2.0?topic=dr-setting-routing-rules-dispatchers

However, this isn't in all 11.2 documents.

My limited testing also implies that this isn't how it works.

------------------------------
Marc Reed
------------------------------