cancel
Showing results for 
Search instead for 
Did you mean: 

Visibility of Web Dynpro Abap

Former Member
0 Kudos

Hi,

I implemented the "travel management", which recalls the EP Web Dynpro ABAP by a back end HR. Now implementing the EP in IBM WebSphere (TAM) have reported the problem invoking Web Dynpro ABAP is invoked directly the host back end. I can work around this "problem"? or is his normal behavior?

Regards.

Accepted Solutions (0)

Answers (4)

Answers (4)

former_member227283
Active Contributor
0 Kudos

Hi,

I implemented the "travel management", which recalls the EP Web Dynpro ABAP by a back end HR. Now implementing the EP in IBM WebSphere (TAM) have reported the problem invoking Web Dynpro ABAP is invoked directly the host back end.

in general scenario when you are using abap dynpro and you don't want to expose you backend system directly to user , then there is just 1 option remain i.e you have to user web proxy.

first web proxy should be used to for Portal

Second web proxy should be used for ECC backend system

When you create a system on portal, where you give neccesary input of the backend system at that time rather than backend system detail you have to give detail of the web proxy which is redirecting to ECC system.

In my landscape , i have used 2 sap webdispatcher , 1 is for portal and other is for ECC system.

Hope this clears you , any doubt pls ask.

Thanks

Anil

Former Member
0 Kudos

Hi,

we solved properly configuring 2 web seal.

Thanks to all.

Best regards.

Diego.

former_member227283
Active Contributor
0 Kudos

Hi,

When you create iview for webdynpro abap on portal, you assign the system alias to that iview.

That system alias contain the information about the backend system.

When you will click on that iview it will redirect to that system.

If you don't want to expose backend system on internet , then anyhow you have to use another reverse proxy for that.

This is a praticle scenario on which we have worked.

Thanks

Anil

Former Member
0 Kudos

Hi,

Then configured correctly our Web Seal can solve and avoid exposing the backend on the Internet.

I'll try to do as you suggested.

Best Regards.

Diego.

Former Member
0 Kudos

HI Anil Bhandary,

Can you explain better what do I do?

Best regards.

Diego.

former_member227283
Active Contributor
0 Kudos

Hi Diego,

IBM WebSphere (TAM) have reported the problem invoking Web Dynpro ABAP is invoked directly the host back end

it is a normal behaviour of Abap webdynpro through portal, portal redirect the abap dynpro to ICM of backend system.

Even you use webdispatcher it will behave like same.

If you dont want to expose backend system , then you can also use reverse proxy for backend system.

Thanks

Anil

Former Member
0 Kudos

Hi,

Yes, I integrate EP that contains iView that call on the backend WD ABAP in IBM Web Sphere.

The problem is that if I call the EP all OK, but if I call the WD ABAP these draw directly on the backend URL (http:// <hostbackend>: <port> / / WDA ...) that does not appear.

Now, Anil Bhandary writes me that is the normal behavior of WD ABAP and that if I do not want to expose the backend I use a reverse proxy. This is the only way to remedy my problem?

Regards.

former_member195896
Contributor
0 Kudos

Hi Diego,

If I understand you correctly, you are :

1) Trying to integrate IBM Web sphere with EP and then calling an ABAP Web Dynpro application via the portal iview?

2) Calling the WDA application directly?

which is it and what is the exact problem. Please provide more clarity.

cheers,

Shantanu