Dynamic proxy for URLs drill down on RTF templates

Youssef_B_82

Summary

Dynamic proxy for URLs drill down on RTF templates

Content

Hi,

I use this tag to retrieve my current server in order to have a dynamic host on my URL links on the RTF templates to create drill downs.

I simply add <?param@begin:CURRENT_SERVER_URL?> on my templates and format the URL hyperlink as shown in the example below.

For example:

{$CURRENT_SERVER_URL}VisionMerchandisingReports/pmsi0020-product_inventory_stock_status/01-Department/ppsi0020-product_inventory_stock_status.xdo?_xpf=&_xpt=0&_xdo=%2FVisionMerchandisingReports%2Fpmsi0020-product_inventory_stock_status%2F01-Department%2Fppsi0020-product_inventory_stock_status.xdo&_xmode=&_paramsp_bu={//P_BU}&_paramsp_site=*&_xt=Dept%20Inventory%20-%20Site&_xf=pdf

That way my links works perfectly fine

Except, on some environment the reports goes through a proxy and the URL on my templates doesn't work.(Please see image below)

So my question is there any way to have a dynamic proxy? Similar to how we have dynamic server with the CURRENT_SERVER_URL function.

Thanks

Youssef

timdexter

Hi Youssef

You would need to log an enhancement request via support for this.

By 'proxy', do you mean a load balancer that sits in front of the BIP server?If that is what you mean, why is the balancer not doing the redirect on its own to the appropriate server?

Or do you mean an HTTP proxy that traffic is redirected through and the report is failing to show (it appears to be working in your screen shot?)

Tim

Youssef_B_82

The workaround sounds good.

Thanks Tim

Youssef_B_82

Hi Tim,

On the screen-shot we see the link as I hover over it but when I click on it I get an error.

To answer your question, it's a reverse proxy which traffic redirect though.

Regards

Youssef

timdexter

Ahhh I see now.

It would require an enhancement request to create a proxy variable for the server that could be accessed out of the box in your templates. For that you need to log an SR with support who will log the enhancement for you. There are a couple of workaround I can think of

1. Create a table in the db to hold the proxy server information. Then create a query in the data model to retrieve this value (and any other values you might want to store.) The value will then be available in the data model and thus in the template for reference to create the URL. When you move reports to a new environment, either copy the table or create a permanent connection to a DB that has the table in the data models.

2. You can create a 'variable' to hold the proxy server value in a sub template (google XSL template variables.) This can then be called by all of your layout templates and the value referenced to build the URL. When you move to a new environment, just update the sub template value.

3. If you are hooked to an LDAP server for security. You can create attributes that are accessible by the data model - see more here: https://docs.oracle.com/middleware/12212/bip/BIPDM/GUID-2A6E4B9B-ABCD-4CF0-A458-59B89F2443A1.htm#BIPDM224

I hope these help

Tim