Drill down functionality is not working for the public user

[citynerd]

Hi,  we have two report sites (urls) set up for the external and internal users. They do access the same reports through the proxy server. The problem I am having with the  set up of the drill down reports is, that the Drilldown functionality does not work for external users.  When they try to drill down to the details of the report from master report,  they get rerouted back to the internal URL which is not accessible to external users thereby disabling external users' ability to drill down on the reports.

Could someone shed some light whether this could be a problem with the proxy server or how the report was set up?

[Grim]

This is very dependent on how everything is configured. It could be any number of things. I suggest using Fiddler and Wireshark to trace the request from the external machine. Should help you diagnose the problem.

[aba.aguiar]

Hi,

We are having the same issue here.

We have the following architecture here:
1 Gateway
2 Dispatchers

External users come in from a different domain.

A Cognos contractor gave us the following options below. I am not quite happy with them because there is a drawback for each of them.

1. Configure One dispatcher  as the Primary dispatcher with a Gateway URI pointing to a URI accessible to our internal users. The second dispatcher would have the Gateway URI pointing to a URI accessible to external users, something like https://www.pagename.com.au:443/ibmcognos/cgi-bin/cognos_module instead of  https://servername.com.au:443/ibmcognos/cgi-bin/cognos_module .
And route all requests for external users to the second dispatcher. This allows load balancing and failover for internal users but not for external users.  Another problem could be a small likelihood of drill-through failure for internal users.

2. Configure as above and apply routing rules for both internal and external users. This disables load balancing and failover but overcomes drill through issues from PDFs.

3. Move Cognos from one domain to another. This would mean that traffic is not changing domains, failover/load balancing would be intact and both server could be identically configured with the same gateway URI. There may be some problems with that but I can't tell what.

4. Disable drill through from PDF across all cognos reports. This can't be done as a configuration option. Using hiding or variables to show/hide pages/columns.
_____________________________________________________________________________________________________

Now would one know any other option? It is possible that there are other options that could be applied in other parts of the technology stack (webserver, router, proxy, etc) ,  but they are beyond my knowledge/capabilities.

[aba.aguiar]

Hi,  we have two report sites (urls) set up for the external and internal users. They do access the same reports through the proxy server. The problem I am having with the  set up of the drill down reports is, that the Drilldown functionality does not work for external users.  When they try to drill down to the details of the report from master report,  they get rerouted back to the internal URL which is not accessible to external users thereby disabling external users' ability to drill down on the reports.

Could someone shed some light whether this could be a problem with the proxy server or how the report was set up?

Hey there, could you solve this issue? Could you please share it with us?
I would really appreciate it thanks!

Anderson

[MFGF]

Hey there, could you solve this issue? Could you please share it with us?
I would really appreciate it thanks!

Anderson

Hi,

Did you investigate Grim's suggestion (above) in tracing the request? It seems like a good starting point to me.

MF.