How to access Portal URL outside of the LAN

[chinna_babu2]

Hi Experts,

Our J2EE engine is hosted on one machine and R/3 is installed on other machine (IP address is different). We have configured Web Dynpro ABAP iVIEW's and Transaction iViews in my portal. To be able to access these two iViews I have to maintain the IP addresses of both EP server and R/3 server IP's in every client host file.

Hence my client system is in LAN it is working with no issues, but we want to access the URL form out of LAN which is not possible at the moment.

Could anyone please advise me how to access the URL without maintaining the IP address in host file

and

able to access the URL out side of the LAN.

Thanks

Murthy

[chinna_babu2]

solved.

[Former Member]

Hi Narasimha,

I trying to access portal url outside of the LAN.

I did the same configuration as you mentioned.

I'm able to access the portal with host entry in end user system.

Please share  me the procedure "how to access portal from external without host file entry in end user system".

Regards.

[chinna_babu2]

Hi

Publish EP in Web Dispatcher and call URL given to the portal in Dispatcher.

Your Basis and Network guys would be able to help you with this.

Regards,

Murthy

[Former Member]

Hi Narasimha,

So far ,i published the portal in web dispatcher and the configurations are working, i'm able to access the portal in extranet IP address/DNS host name if, I maintain the host name entry in Laptop host file.

My requirement is to access the portal without maintaining any host entries in END User systenm.

As of now, I'm not having basis and Network support,I myself handing the process.

Can you give me any suggestions to proceed.

[chinna_babu2]

Hi

We have installed Web Dispatcher and maintained the IP Address of both EP and ECC. Now we are able to call the EP from outside of the LAN with the IP address of dispatcher, but when Transaction iView was being called from EP with the URL of ECC (http://<ecchost.domain>:8000/sap/bc/gui/sap/its/webgui?sap-client=100) it gives page not found error.

Can anyone suggest how to resolve it.

Thanks

Murthy

[Former Member]

Hi,

You have exposed your portal on the internet. You also need to expose your ECC system on the internet if you want the ECC transaction iviews to work. EP is NOT a reverse proxy... The browser from the internet has to be able to call the ECC URL.

EP is just used for interface integration, access control and SSO.

So you need a second web dispatcher or use web dispatcher 7.2 which is able to proxify several SAP back office systems.

Regards,

Olivier

[chinna_babu2]

Hi Oliver,

Thanks for the reply. We have published ECC also in Web Dispatcher.

We have maintained both EP and ECC IP addresses in Web Dispatcher.

URL for EP is http://portal.domain.com:50000/irj

URL for the ECC is http://ecc.domain.com:8000/sap/bc/gui/sap/its/webgui?sap-client=100

We are able to call the EP from outside of our LAN with the web dispatcher URL http://webdispather.domain.com:8888/irj (which will call the Portal), in the same way we are able to call the ECC with the web dispatcher URL http://webdispather.domain.com:5555/sap/bc/gui/sap/its/webgui?sap-client=100.

But the issue here is, when the transaction iview called, request will be passed as http://ecc.domain.com:8000/sap/bc/gui/sap/its/webgui?sap-client=100 which the request will not pass to the web dispatcher.

Could you please suggest me how to handle this.

Thanks

Murthy

[chinna_babu2]

Hi

I have maintained web dispatcher entry instead of ECC host name in Portal System. Current issue has been solved with this approach. Don't any drawback with this approach.

Thanks

Murthy

[Former Member]

Hello

Where web dispatcher entry was maintained?

In system definition in portal?  Which property?

Could you explain this in detail?

Regards

Artur

[Former Member]

Hello Murthy,

As stated by Shanti please refer to the links below for detailed information on the implementing External Facing Portals. The solution to your issue will be maintaining DNS entries for the backend as well the Portal IP addresses in your internal and external DNS servers. This will ensure that the IP addresses are not distributed to the intranet users and will save you time in maintaining the host file entries in the client machines.

The Network Team of your organization will be able to do the DNS maintenance. Typically, all intranet (LANs) users and extranet users can access via the url http:// <fqdn>:<port>/irj/portal.

In case you are exposing Portal to the internet then using a reverse proxy can be a good option.

Regards,

Pinac Bendre

[former_member201257]

The general idea is to install the portal inside your network and "expose" it through "some means" to the outside world. This will depend on your requirements, current infrastructure and you can choose from a variety of options (Reverse Proxies, Web Dispatchers, Load Balancers, Federated Portals, ... )

There are some good weblogs on SDN on the topic of External Facing portal

Implementing an External Facing Portal:

http://help.sap.com/saphelp_nw04s/helpdata/en/04/e5b7c3de384515afeafa0dab8e44e0/frameset.htm

Options and strategies to secure an Internet Facing Portal:

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

http://wiki.sdn.sap.com/wiki/display/EP/ExternalFacingPortal

http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/44a122f3-0901-0010-b09e-ed4a21441319

http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/30eb732a-2448-2a10-7aa6-8fd0849b6f20

- Shanti