cancel
Showing results for 
Search instead for 
Did you mean: 

External Access to SAP Portal 7.00 using WEB Dispatcher

Hannes2
Explorer
0 Kudos

i try to give external(internet) access to our SAP Portal 7.00 (SP10).

i have configured a webdispatcher in the DMZ with connection to the portal server .

(rdisp/ms_host , ms/http_port,.......) ==> this works fine

the external name of the portal should be "xxxxxxx. leica-geosystems.com".

how can i now connect this external URL to the internal URL of the SAP Portal which is : http://xxxxxxx.lgs-net.com:50100/irj/portal?

is this possible without using the redirect service of the MS-IIS ?

many thanks for your help

hannes toefferl

Accepted Solutions (0)

Answers (2)

Answers (2)

Hannes2
Explorer
0 Kudos

hi darren

many thanks for this helpful answer , but there are some questions left :

1) if i call xxxxx.leica-geosystems.com in the web the webdispatcher routes the request forward to the j2ee of the portal and starts the j2ee-admin page (default-page) ; how can i organize , that the portal itself is started ( ... /irj/portal) ?

if i start xxxxx.leica-geosystems.com/irj/portal in the web it works fine , but i do not want this URL from internet .

2) i have done the following settings in the VA of the portal j2ee - are they correct

(Port:50100,Type:http)(Port:50101,Type:ssl)(Port:50122,Type:http)(Port:50123,Type:ssl)

and

50122=(Host:xxxxx.leica-geosystems.com,Port:80,Scheme:http,Override:true)

does this mean , that the portal is started on port 50122 if the webdispatcher sends a request from xxxxx.leica-geosystems.com:80 ? i'm sorry , but i don't understand that !

3) do you from the security point of view suggest to use first an MS-IIS redirect functionality , and then the webdispatcher to start the portal from internet.

many thanks again hannes toefferl

darren_hague
Contributor
0 Kudos

Hi Hannes,

1) I understand what you want here. It will be difficult to avoid /irj/portal for portal URLs in general, but you can set up a redirection in a top-level index.html file. To be honest, this sort of thing is much easier to configure with an Apache reverse proxy server.

2) What happens with this config is that when the portal receives a request on 50122 (via Web Dispatcher), it looks for the internal host and port on any outbound HTML and rewrites them to the external name and port, so that any links appearing in the user's browser are correctly named. Once again, this is something which would be much better configured in an Apache reverse proxy.

To summarise, what you are trying to do is just about possible in Web Dispatcher, but the right tool for the job is an Apache web server configured as a reverse proxy.

Cheers,

Darren

<a href="http://www.fortybeans.com/">blog</a>

darren_hague
Contributor
0 Kudos

Hi Hannes,

This is indeed possible. The way to do it is to set your portal to listen on two ports, one for internal and one for external. This is done in Visual Administrator, so to listen on 50100 for internal and 50122 for external go to <b>Dispatcher -> Services -> HTTP Provider</b>, set the <b>Ports</b> property to the value <i>(Port:50100,Type:http)(Port:50101,Type:ssl)(Port:50122,Type:http)</i> (i.e. add the clause <i>(Port:52422,Type:http)</i>).

Then you set the new host name to listen on the new port - set the ProxyMappings setting to <i>52422=(Host:xxxxxxx.leica-geosystems.com,Port:80,Scheme:http,Override:true)</i>

That should do the trick...

Hope this helps,

Darren

<a href="http://www.fortybeans.com/">blog</a>

Former Member
0 Kudos

Darren,

From the question here and your reply, it looks like the webdispatcher can be used to configure Portal as an external facing portal. However, do you think it's a recommended approach? As webdispatcher can not function as a full blown reverse proxy, right?

Isn't the web dispatcher only to load balance between multiple instances of the Portal?

Just wondering about security aspects,

Thanks,

Kiran

darren_hague
Contributor
0 Kudos

Kiran,

I agree that perhaps the Web Dispatcher is not the best tool for the job in this case - an Apache-based reverse proxy would be a much better idea from a security point of view.

Cheers,

Darren

<a href="http://www.fortybeans.com/">blog</a>

Former Member
0 Kudos

Hi Darren,

Do we have to update xxxxxxx.leica-geosystems.com in DNS?

Rgds,

Hapizorr

former_member304001
Active Contributor
0 Kudos

Hi,

Change the default portal URL to give the users a more user friendly URL. The following steps will show you how to modify the URL from the default port of 50000 to 80 which is the browser default. Also you will learn how to setup a redirect from the J2EE Engine so the user can find the portal without first inputting the /irj/portal to the URL.

Change the Port:

1.Switch to the J2EE Visual Administrator

2.Go to Cluster à Dispatcher à Services à HTTP Provider

3.Choose Ports

4.Change the Port number to 80 for http and 81 for ssl

5.Choos Update and Save.

Remove the irj/portal:

1.Go to Cluster à Server à Services à HTTP Provider

2.Enter /irj/portal in the Start Page text field

3.Choose Save Properties button

4.Restart the Service