WDPortalNavigation in a https portal environment

[Former Member]

Hi experts!

I have the following requirement/problem: in my WD Java application, I need to navigate, i.e., open an external window of another application (outside Portal) and I'm using WDPortalNavigation.navigateAbsolute() method to do this.

My WD Java application is running in a https environment (https://myhost.com/irj/portal) and I need to navigate to a https URL also.

The problem occours when the redirection page opens, it opens with this URL: http://myhost.com/irj/portalapps/com.sap.portal.navigation.toplevel/html/child.html and I get a page not found error, wich is correct because http://myhost.com does not exist!!!

Any idea where I can "say" to WDPortalNavigation to use https instead of http in the redirection page???

Please Help.

Thank you.

Osvaldo Silva

[siarhei_pisarenka3 · Accepted solution]

Hi Osvaldo Silva

Instead of Portal Navigation use the following in the case:

IWDWindow win = wdComponentAPI.getWindowManager().createNonModalExternalWindow(java.lang.String URL, java.lang.String title);
win.show();

BR, Sergei

[Former Member · Accepted solution]

Hi Siarhei, and thanks for your reply.

I've also tried that aproach and I got a runtime "Invalid URL" error.

Any other sugestion?

Thanks.

Osvaldo Silva

[Former Member]

Hi,

I understand you are trying open an iview within in the portal using wdportalnavigation.You do not need to specify http or https anywhere .It should the same as shown in the address bar of parent portal page.

Ashok

[Former Member]

Hi Ashok and thanks for your reply.

I'm trying to open a URL from another application running outside SAP Portal which uses https protocol. The parent application is a WD Java running in a https environment.

Thanks.

Osvaldo Silva

[Former Member]

Problem solved!!!

Went back to the first aproach and used wdComponentAPI.getWindowManager().createNonModalExternalWindow() method.

The problem was that the URL which came from an iview parameter was wrong: " https://...."; instead of "https://...." There was a leading whitespace preciding the URL.

To all that replied to this thread, thanks.

Osvaldo Silva.