Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

General Question regarding Client <--> Portal <--> Backend

Hi Experts,

in continuation to

We are facing an issue with using WebDynpros for ABAP. For your better understanding, here is our Network Infrastructure in broad strokes.

Network A (Development). Consists of Clients.

Network B (Neutral). Consists of Enterprise Portal.

Network C (Production). Consists of Clients and HCM Backend.

Network A can communicate with Network B.

Network C can communicate with Network B.

Network A can NOT comminucate with Network C.

This means. Clients in Development cannot access the productive HCM Backend.

Up until now we have only had WebDynpros for JAVA in our portal. That means:

Clients from Network A Access Network B.

Clients from Network C Access Network B.

Network B Accesses Network C (HCM Backend) for Infotype information and so on.

Now we also have WebDynpro for ABAP on our Portal. Clients from Production (Network C) can access those scenarios, clients from development(Network A) can NOT. We all thought the portal communication would work like this:

Clients from Network A Access Network B.

Portal on Network B accesses Network C for WD4A-Service, does something and presents it in Portal iView.

Client from Network A Accesses Network B yet again for WD4A in iView.

We have traced the Client-Communication with firebug and came to see this is happening:

Client accesses Portal for iView and Framework.

Once this is finished the Client tries to access the HCM-Backend directly for the WD4A-Service via POST.

This can never work in our infrastructure.

First of all I'd like someone from SAP to confirm this:

WD4A-Services presented in Enterprise Portal are directly accessed from the Backend by the client. Portal is only "routing it through".

best regards, Lukas

Not what you were looking for? View more on this topic or Ask a question