cancel
Showing results for 
Search instead for 
Did you mean: 

Webdynpro ABAP from enterprise portal

Former Member
0 Kudos
489

Hi,

We have an portal which can be accessed from internet through webdispatcher. Now we have developed certain Webdynpro ABAP based based application in (R3). The WD ABAP iviews are been created on portal. But we are not able to access this application when portal is opened from internet.

The R3 is not available on internet. So how can we manage these thing so that Webdynpro ABAP can be accessed from internet?

Accepted Solutions (1)

Accepted Solutions (1)

former_member201257
Active Contributor
0 Kudos

Well you will need to some how provide http connectivity to the backend system from the internet. You may choose to use a web dispatcher or a reverse proxy according to your requirements. The idea is not to expose the real server name directly and instead use a proxy host name.

Starting Netweaver 7.2, I believe you can use the same webdispatcher for multiple systems (use same webdispatcher for both portal and the backend system).

You will then need to adjust the System Object properties Web AS host name and port from System Administration of your portal.

If your Webdynpro ABAP application will be producing any absolute URLs, you may also need to configure the table HTTPURLLOC in your backend system.

Check this power point

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/24396589-0a01-0010-3c8c-ab2e3acf6...

Thanks,

Shanti

Former Member
0 Kudos

Hi Shanti,

We do have webdispatcher through which are able to access portal. But i want to understand that whether do we need some public IP for R3 system also. Like for our SAP portal we have public IP and we have registered a domain name for it.

Now from this SAP portal i need to access ABAP webdynpro. The problem is while accessing this application from internet through portal it is not working, since it tries to search for ABAP webdynpro URL. So want to understand if we can by pass this URL internally through SAP portal to ABAP webdynpro.

Regards,

Jigar Oza

Former Member
0 Kudos

Hi,

To add more information :

Current scenario which is working fine:

Browser ---> Webdispatcher (abc.companyname.com) --> SAP Portal(portal.companyname.com:50000)

Required :

Browser --->

Webdispatcher (abc.companyname.com) -->

SAP Portal ABAP Webdynpro iview (portal.companyname.com:50000) -->

ABAP(r3prd.comp.com:8000)

So how we can redirect request coming from internet to SAP portal and from SAP portal to ABAP(R3)

Regards,

Jigar Oza

Former Member
0 Kudos

Hi,

Yes, you need a public IP and a FQDN published on the Internet for your R/3 system. A portal does NOT provide any reverse proxy functionality. It just integrates visually the iviews and manages authentication and authorisations.

Regards,

Olivier

Former Member
0 Kudos

So how we can redirect request coming from internet to SAP portal and from SAP portal to ABAP(R3)

You need a reverse proxy for your R/3 system in the DMZ. If you use web dispatcher release 7.2, you can use the same web dispatcher for both the portal and R/3.

Then you need to configure the R/3 URLs in the portal to use the R/3 reverse proxy.

Regards,

Olivier

Former Member
0 Kudos

Thanks Shanti and Olivier.

Yor replies were very helpful.

I will still keep this thread as un-answered if still others has experts advice on this or more information please provide.

Regards,

Jigar Oza

Former Member
0 Kudos

Hi Jigar,

when using Webdispatcher (abc.companyname.com),,what is the protocol you are using,,,http or https to call the portal,,, if you are using https and you have configured WAS parameter of system object to http than it will not work or shows popups,,,secondly try to activate https in R3 system and check the scenario,,,,Its strange to know that portal is mainly used in internet environment and when u access web dynpro abap from internet through portal,it should work,,,as example,,say you have some work list items in UWL,,,say leave request or something else,,,those are items configured in backend side,,,try to test those things,,when you click on one of the item ,is it working or not from internet,,,

Former Member
0 Kudos

First of all let me clear few misconceptions created from above replies.

1. You dont need public IP address for your R/3. All you need is R/3 should be accessible to webdispatcher.

2. While opening ABAP Webdynpro/ITS iviews through portal, its not portal which is trying to communicate with backend. Its the browser who does this. You can see this through http trace at browser.

It is due to 2 that your ABAP webdynpro are blocked. Bcoz no one will open R/3 to internet. Probably its blocked at firewall. Its a security issue.

For ABAP WD,

Browser > Webdispatcher > R/3.

This is how it is designed.

This is very common problem and you will find many discussions in sdn regarding this.

You can either convince your security team that R/3(ICF) should not be blocked. For which they would never agree.

Another option could be create a virtual host at R/3 and create webdynpro services(ICF services) in this virtual host and specify this virtual host in your webdispatcher.

Another expensive option could be create a Webdynpro runtime engine(WEB AS ABAP) where webdynpro applications should run and they do an RFC call with R/3. I am sure security ppl would love this.

It becomes Browser > Webdispatcher > WD runtime >(through RFC) R/3.

Thanks,

Nag

Former Member
0 Kudos

Hi Nag,

As you said all i need is R3 should be accessible to Web dispatcher. Well in that case i do have webdispatcher for which R3 is accessible.

Since browser communicates directly with R3, How can browser resolve this R3(ABAP webdynpro) application URL from internet until and unless it does have some public IP. There needs to be something that can resolve webdispatcher from internet which would send request to R3,

I am aware of configuration for accessing R3 from webdispatcher. But confusion is can i use my current portal webdispatcher which would forward R3 application URL request without getting any new public IP for my R3 system

Also please provide the SDN suggestion links on this, since i have found very few on this.

Within intranet there is no problem, but the problem is from internet.

Regards,

Jigar Oza

Former Member
0 Kudos

Hi Jigar,

As in intranet, it is working fine for you, problem is only from internet, practically portal is used to access through internet, there is no need to provide special ip for R3, kindly make the host entry in you load balancer, from where it is beeing called,,,i.e

browser>load balancer (Dispatcher)> portal--> R3.

Portal would be having host entry of R3, and load balancer would be having host entry of portal, kindly provide host entry to load balancer for R3 also...

Regards

Biren

Former Member
0 Kudos

Jigar,

When browser tries to access webdynpro if webdispatcher is configured to talk to R/3, it will not use R/3 Url.

eg: your webdispatcher is webdisp.domain.com

For a webdynpro /sap/bc/webdynpro/test

When you open this webdynpro application in an iview from portal, request sent from browser will be

https://webdisp.domain.com/sap/bc/webdynpro/test

Webdispatcher receives this request and simply forwards to your r/3. So it is converted to something like

https://yourr3.internal.com/sap/bc/webdynpro/test

As it is your webdispatcher doing this, all you need is webdispatcher configured to talk to R/3

If this is not happening, webdispatcher config should have a problem.

BTW can you see http trace at browser and let us know which url is being hit for webdynpro acess? R/3 or webdispatcher?

Thanks,

Nag

hofmann
Active Contributor
0 Kudos

Since browser communicates directly with R3

As soon as you start using a reverse proxy as a single point of entry the browser will communicate with this reverse proxy only and not with your portal, ABAP or any other system.

Please close the question as this answer was already asked and solved before.

br,

Tobias

Answers (1)

Answers (1)

Former Member
0 Kudos