Относительный путь в go_url

IFedoseev

Добрый день!

Я столкнулся с проблемой при использовании механизма go_url для организации переходов между связанными отчетами в Oracle BI (версия 11.1.1.7).

Отчеты разрабатываются на тестовом контуре, при переносе на прод ссылки приходится перебивать (имя сервера).

Есть ли возможность указывать относительный путь в строке ссылки?

Пример:

http://server:9704/analytics/saw.dll?Dashboard&PortalPath=@{1}&Page=@{2}&Action=@{3}

Gianni Ceresa

Hi,

would be better if you post in English ... As it's an international forum English is the official language to make sure we all understand each other (more or less )

IFedoseev

Hi,

I faced with a problem in GO_URL feature while creating Oracle BI report's links  (Oracle BI 11.1.1.7).

Is it possible to use related url in url string to avoid manual editing that string after change environment from test to prod?

Example:

http://server1:9704/analytics/saw.dll?Dashboard&PortalPath=@{1}&Page=@{2}&Action=@{3}

http://server2:9704/analytics/saw.dll?Dashboard&PortalPath=@{1}&Page=@{2}&Action=@{3}

I want something like this:

/saw.dll?Dashboard&PortalPath=@{1}&Page=@{2}&Action=@{3}

But it doesn't work. Please, help.

Andrew Fomin.

Here is the doc, that solves your issue: https://docs.oracle.com/cd/E21764_01/bi.1111/e16364/actions.htm#BIEIT1671

You need to define an alias in the

<Oracle Middleware Home>\user_projects\domains\bifoundation_domain\config\fmwconfig\biinstances\coreapplication\ActionFrameworkConfig.xml

Something like this:

Server1

<aliases>
<location-alias>
<alias>biserver</alias>
<actual>http://server1:9704/analytics</actual>
</location-alias>
</aliases>

Server2

<location-alias>
<alias>biserver</alias>
<actual>http://server2:9704/analytics</actual>
</location-alias>
</aliases>

Restart managed server.

And now you can create go URLs:

@[biserver]/saw.dll?Dashboard&PortalPath=@{1}&Page=@{2}&Action=@{3}

But I wonder why do you use go URLs instead of Navigate to BI content?

IFedoseev

Andrei, Thank you!

I'l try it and then mark your answer as correct.

I use it because of flexibility.

For example, I need to send some value [rep1.field1] to the filter of another report [rep2.field2].

Field 1 and Field 2 are different fields from subject area (or even from different subject areas).