on 2016 Apr 21 9:31 AM
Hi,
Could you please assist on SAP webdynpro application URL masking.
We are trying to mask the sap OEP server webdynpro url i.e
"http://bpoerav4.<domain>:8060/sap/bc/gui/sap/its/webgui?sap-client=400",
In the above, bpoerav4 = is the sapOER server host name and 8060 = is the server port number ( 8000 is standard and 60 is the instance number of one of the dialog application server)
But as per the Network policy the server host name and IP address of the host will not be allowed to be accessed from customer location so we are trying to mask the above url with
"http://sapoer.<domain>:8500/sap/bc/gui/sap/its/webgui?sap-client=400".
The configuration we have did at SAP Webdispatcher and its profile as attached.
Here we are able to initially login to OER server with "http://sapoer.<domain>:8500/sap/bc/gui/sap/its/webgui?sap-client=400" mask url and can
able to hit any of the sap transaction codes but when we try to open any of the webdynpro's, its opening in a new window with sap OER hostname and Ip address of the host server with below url
"http://bpoerav4.<domain>:8060/sap/bc/gui/sap/its/webgui?sap-client=400", which is not allowed to be accessed at customer location due to Network security policy.
Thanks.
Abdul
Hi Abdul,
I recommend you going through the following Wiki page.
Even though the wiki resides in a BSP space, it can be used for ITS (WEBGUI) too.
You will find important information about how to use the HTTPURLLOC table.
Kind regards,
Cris
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Abdul,
Could you please give one example of calling a transaction code via WEBGUI (SAPGUI for HTML) that triggers a new window (and calls the backend hostname/port information, and not the Web Dispatcher one)?
It seems that the HTTPURLLOC table does not contain the correct values yet.
Thank you,
Cris
PS: Web Dynpro ABAP is another SAP technology - WEBGUI is not Web Dynpro ABAP.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Abdul,
The Web Dispatcher profile is missing.
Anyway, you can try maintaining the HTTPURLLOC table (click here for details).
Regards,
Isaías
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Isaias Freitas,
Thanks for the update.
Before sharing the SAP Webdispatcher profile , let me update you the user flow from customer end and also our
SAP system OEP ( OER- Object Event Repository) is in cluster i.e
Noda A: DB ( Database) with DB2 on HP-Unix
Node B: ASCS ( Message and Enque services ) + PAS ( Primary application server) on HP-Unix
And 4 Dialog instances on HP-Unix
User Flow from customer location to SAP servers:
User - > Firewall1 - > Hardware Load Balancer - > DMZ Layer ( SAP Webdispatcher Installed and configured and its profile as shared ) - > Firewall2 -> MZ Layer SAP server ( SAP OER).
SAP Web dispatcher profile:
SAPSYSTEMNAME = WD3
SAPGLOBALHOST = BPAPSRUWMV04
SAPSYSTEM = 00
INSTANCE_NAME = W00
DIR_CT_RUN = $(DIR_EXE_ROOT)\$(OS_UNICODE)\NTAMD64
DIR_EXECUTABLE = $(DIR_CT_RUN)
DIR_PROFILE = $(DIR_INSTALL)\profile
_PF = $(DIR_PROFILE)\WD3_W00_BPAPSRUWMV04
SETENV_00 = PATH=$(DIR_EXECUTABLE);%PATH%
#-----------------------------------------------------------------------
# Configuration for medium scenario
#-----------------------------------------------------------------------
icm/max_conn = 500
icm/max_sockets = 1024
icm/req_queue_len = 500
icm/min_threads = 10
icm/max_threads = 50
mpi/total_size_MB = 80
#icm/HTTP/logging_0 = PREFIX=/, LOGFILE=LOGFILE=access_log-%d-%m-%y_%h:%t:%s
#icm/HTTP/logging_client_0 = PREFIX=/, LOGFILE=access_log_client-%d-%m-%y_%h:%t:%s
#-----------------------------------------------------------------------
# SAP Web Dispatcher Ports
#-----------------------------------------------------------------------
##-----OER Port binding-----#####
icm/server_port_0 = PROT=HTTP, PORT=8500
##-----WD Admin port binding------####
icm/server_port_2 = PROT=HTTP, PORT=8350
icm/HTTP/admin_0 = PREFIX=/sap/admin,DOCROOT=$(DIR_DATA)$(DIR_SEP)icmandir,AUTHFILE=$(icm/authfile),PORT=8350
wdisp/system_conflict_resolution = 2
##----------------------------------------------------------------------
wdisp/system_0 = SID=OEP, MSHOST=ascsoep.<Domain>, MSPORT=8135, SRCSRV=*:8500
wdisp/system_0 = SID=OEP, MSHOST=ascsoep.<Domain>, MSPORT=8135, SRCURL=/sap/
icm/HTTP/redirect_0 = PREFIX=/, FROMPROT=HTTP, FOR=ascsoep.<Domain>:8135, TO=/sap/*, PROT=HTTP HOST=sapoer.<Domain>, PORT=8500
#-----------------------------------------------------------------------
# Start webdispatcher
#-----------------------------------------------------------------------
_WD = $(DIR_EXECUTABLE)\sapwebdisp$(FT_EXE)
Start_Program_00 = local $(_WD) pf=$(_PF)
SETENV_01 = SECUDIR=$(DIR_INSTANCE)/sec
#icm/HTTP/mod_0 = PREFIX=/, FILE=D:\usr\sap\WD2\SYS\profile\mod_rules.txt
wdisp/auto_refresh = 120
wdisp/max_servers = 100
#is/HTTP/default_root_hdl = j2ee
#wdisp/system_conflict_resolution = 0
#icm/HTTP/redirect_0 = PREFIX=/, TO=/irj/portal
##----------------------------------------------------------------------
So please help us in resolving this SAP Webdynpro URL masking.
Thanks.
Hello Abdul,
Have you tried maintaining the HTTPURLLOC table?
You would have to use the external hostname ("sapoer.<domain>") and the external port (8500) used by the end users to reach the "firewall1".
Regards,
Isaías
Dear Isaias Freitas,
In table HTTPURLLOC there were no entries so we have created below two entries in each of the client- 000 and 400
MANDT 000
SORT KEY 0001
PROTOCOL HTTP
APPLICATN */SAP/*
FOR DOMAIN <Domain Name>
HOST SAPOER
PORT 8500
MANDT 000
SORT KEY 0002
PROTOCOL HTTPS
APPLICATN */SAP/*
FOR DOMAIN <Domain Name>
HOST SAPOER
PORT 8500
MANDT 400
SORT KEY 0001
PROTOCOL HTTP
APPLICATN */SAP/*
FOR DOMAIN <Domain Name>
HOST SAPOER
PORT 8500
MANDT 400
SORT KEY 0001
PROTOCOL HTTPS
APPLICATN */SAP/*
FOR DOMAIN <Domain Name>
HOST SAPOER
PORT 8500
After this again we tried but the same issue and its not working. Please let me know if we did wrong in entries.
Thanks.
Abdul Mubeen
Dear Abdul,
Please perform the following adjustments on all four entries:
Maybe this SCN post can help you as well.
Regards,
Isaías
Dear Isaías,
Thanks for the time but still the same issue.
Below are the entiries maintained
MANDT 000
SORT KEY 0001
PROTOCOL HTTP
APPLICATN /SAP/*
FOR DOMAIN
HOST SAPOER.<Domain Name>
PORT 8500
MANDT 000
SORT KEY 0002
PROTOCOL HTTPS
APPLICATN /SAP/*
FOR DOMAIN
HOST SAPOER.<Domain Name>
PORT 8500
MANDT 400
SORT KEY 0003
PROTOCOL HTTP
APPLICATN /SAP/*
FOR DOMAIN
HOST SAPOER.<Domain Name>
PORT 8500
MANDT 400
SORT KEY 0004
PROTOCOL HTTPS
APPLICATN /SAP/*
FOR DOMAIN
HOST SAPOER.<Domain Name>
PORT 8500
The issue is same as webdynpro opening with SAP server names not with sapoer.<Domain Name>....
Thanks.
Abdul Mubeen
User | Count |
---|---|
66 | |
8 | |
8 | |
6 | |
6 | |
6 | |
6 | |
6 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.