SAP Web Dispatcher Backend Issues

[Former Member]

I have 1 web dispatcher with 2 names/alias

webdisp1.com

webdisp2.com

My applications are SAP SMP & windows IIS which is hosting a website to our sap mobile app. Each has a name/alias

App1.com & App2.com respectively

I have 2 servers with 3 pairs of applications.

1) SAP SMP = App1.com:8083/Admin installed to server1 + server2

2) Windows IIS = App1.com:443 installed to server1 + server2

3) Windows IIS =App2.com:443 installed to server1 + server2

note that app1 has 2 ports.

note that app2 and app3 are same ports.

Now, what I want for web dispatcher are the following

if I connect to webdisp1.com:8083/Admin, it will redirect to  App1.com:8083/Admin

if I connect to webdisp1.com:443, it will redirect to App1.com:443

if I connect to webdisp2.com:443, it will redirect to App2.com:443

So far I had all links working. Except that App2.com:8083/Admin exists. which supposedly should not.

Below is my profile

icm/server_port_1 = PROT=HTTPS,PORT=8083

icm/server_port_3 = PROT=HTTPS,PORT=443

wdisp/system_1 = SID=SMP, EXTSRV=https://server1:8083;https://server2:8083, SRCSRV=*:8083, SRCURL=/, STICKY=true

wdisp/system_1 = SID=SMP, EXTSRV=https://server1:443;https://server2:443, SRCSRV=*:443, SRCURL=/, STICKY=true

[isaias_freitas · Accepted solution]

Hello,

You have to tune your system selection criteria.

This WIKI page can help.

Web Dispatcher for Multiple Systems - Understanding and Examples - Application Server Infrastructure...

Regards,

Isaías

[Former Member · Accepted solution]

Hello Isaias,

Thank you for the help.

The link you gave did help me for a while. But I am encountering an issue where I cannot proceed after I login. The screen just refreshes.

Example: https://server1:8083

I cannot login because maybe I cannot proceed to https://server1:8083/Admin/something/something.

There is probably an incomplete setup in the web dispatcher.

Here is my new profile

wdisp/system_3 = SID=SMP, EXTSRV=https://server1:8083;https://server2:8083, SRCVHOST  =App2:8083

wdisp/system_3 = SID=HCL, EXTSRV=https://server1:443;https://server2:443, SRCVHOST  =App1:443

wdisp/system_4 = SID=CLT, EXTSRV=https://server1:443;https://server2:443, SRCVHOST  =App2.com:443

putting a * at the end did not help.

Regards,

Paolo

[isaias_freitas · Accepted solution]

Hello Paolo,

Are all the SMP, HCL and CLT systems non-SAP systems? I see that you are using the EXTSRV argument. This is to be used when the backend is not an SAP ABAP/Java/dual-stack system.

In addition, you have "wdisp/system_3" defined twice.

And what is "app2", "app1" and "app2.com"? Are these virtual hostnames / DNS aliases that point to the Web Dispatcher server?

Regards,

Isaías

[Former Member · Accepted solution]

Hello Isaias,

SMP is SAP Mobile Platform

HCL & CLT are non sap systems. Those are websites which are hosted using IIS of windows server.

app1 & app2 are DNS aliases

app1 port 8083 is the SAP Mobile Platform Admin Cockpit

app1 port 443 is one of the non sap websites I did with IIS

As you can see they are using the same DNS alias, only different port

app2 port 443 is another non sap website I did with IIS. Also, take note that I reused the port 443. Using a different DNS alias..

Also please take note that app1.com and app2.com aliases are pointed to the web dispatcher. However, I also reused them in my app servers which can only be accessed/pointed/redirected by the web dispatcher.

I hope I am making myself clear.

Thank you!

Paolo

[isaias_freitas · Accepted solution]

Hello Paolo,

Also please take note that app1.com and app2.com aliases are pointed to the web dispatcher. However, I also reused them in my app servers which can only be accessed/pointed/redirected by the web dispatcher.

So, any end user that tries to access "app1.com" and "app2.com" will reach the Web Dispatcher.

Is this correct?

What do you mean by "reused them in my app servers"? You should not have "app1.com" pointing to different places. This might cause issues.

The solution is not clear yet, because it seems we do not have the correct profile parameters that are in place.

Please make a copy of the Web Dispatcher profile. Then, edit this copy and change the hostnames only. And make consistent changes (example: if you replace myapp.com by app1.com, do not replace any hostname other than myapp.com by app1.com).

After the hostnames have been sanitized, attach the complete profile to this thread (there is an option to attach files to the thread).

Regards,

Isaías

[Former Member · Accepted solution]

Hello Isaias,

When I was trying to edit my profile, I figured that I need to explain to you my landscape which took me over an hour writing  in notepad.. But then I suddenly realized that I maybe I should trying fixing and eliminating the issue more .

And then I discovered something

My sap web dispatcher has 3 DNS aliases.

one of which is the web dispatcher URL for administration = webdisp1.com:44300

I guess I dont need to explain why are there 2 more. but lets name them = webdisp2.com:8083 + webdisp3.com:443

So when I was trying to connect to my application - SAP Mobile Platform Admin Cockpit via webdisp2.com:8083/Admin, I tried mixing the URLs.

I tried webdisp1.com:8083/Admin & webdisp3.com:8083/Admin are going to the same SAP Mobile platform Admin Cockpit. Which should not be the case.

So to finalize my issue, any DNS alias of the web dispatcher goes into the SAP Mobile Platform Admin Cockpit using port 8083/Admin.

There is also one instance that I fixed that issue, however, I cannot login into SAP SMP Admin Cockpit. It seems that the browser just refreshes itself when Iog my credentials.

Attached is my whole edited profile specific for this issue.

But I am pasting my wdisp here as well

wdisp/system_1 = SID=SMP, EXTSRV=https://server1.net:8083;https://server2.net:8083, SRCSRV=*:8083, SRCURL=/, STICKY=true

I tried changing the * in SRCSRV but I think Im doing it wrong.

Thanks!

Paolo

for scn.txt.zip

[isaias_freitas · Accepted solution]

Hello Paolo,

Thank you for the clarification .

The correct URL to access the Web Dispatcher administration is "/sap/wdisp/admin" .

At the profile you have attached, the SMP system is defined twice, and no system other than SMP is defined...

In addition, the system selection criteria in use does not take into account the DNS alias, just the port used to reach the Web Dispatcher.

So, basically all requests will be sent to the SMP system...

Regards,

Isaías

[Former Member · Accepted solution]

Hi Isaias,

Isaias Freitas wrote:

The correct URL to access the Web Dispatcher administration is "/sap/wdisp/admin" .

Thanks for the clarification haha..

At the profile you have attached, the SMP system is defined twice, and no system other than SMP is defined...

You may have seen SAP SMP twice because I am using 4443 port on the other one. That just made me realize that I can combine them, am I correct?

In addition, the system selection criteria in use does not take into account the DNS alias, just the port used to reach the Web Dispatcher.


So, basically all requests will be sent to the SMP system...

Regards,
Isaías

.This is what I am trying to figure. and I am not sure what I am doing wrong.

So do I change this one:

wdisp/system_1 = SID=SMP, EXTSRV=https://server1.net:8083;https://server2.net:8083, SRCSRV=*:8083, SRCURL=/, STICKY=true

to this?:

wdisp/system_1 = SID=SMP, EXTSRV=https://server1.net:8083;https://server2.net:8083, SRCSRV=webdisp2.com:8083/Admin, SRCURL=/, STICKY=true

Cause I actually already did and it still same result.

Is there a parameter where I can deactivate a specific URL?

Thanks

[Former Member]

I solved by just making the correct parameter from the wiki link you gave me in your first post

I switched SRCSRV to SRCHOST and declared the DNS/alias.

Thanks a lot!