on 11-10-2009 2:35 PM
Hi Everyone,
When I test the webdispatcher I can connect to J2ee systems without a problem but not to any of the abap urls.
On the j2ee side I test it with
http://sapsp1ci20:8022/index.html
On th abap side I test it with
http://sapsp1ci20:8022/sap/public/ping?sap-client=200
I get a response that the service is not available although it is activated in SICF. I also get this for the standard webgui and anyotehr url I would expect to work.
1. I have installed the sap webdispatcher (relno 7000, patchlevel 0, patchno 229) for NW 7.00 on with a J2EE patch 17.
2. I have configured the ms/http_port to 8021 in the ABAP profile and set the is/HTTP/default_root_hdl = abap.
3. The following ICM services are active icr_groups, icr_urlprefix, logon_groups, urlprefix
4. The sapwebdisp.pfl was generated using the -bootsstrap option an is as follows:
Profile generated by sapwebdisp bootstrap
unique instance number
SAPSYSTEM = 22
add default directory settings
DIR_EXECUTABLE = /usr/sap/SP1/webdisp
DIR_INSTANCE = /usr/sap/SP1/webdisp
Accessibility of Message Servers
rdisp/mshost = sapsp1ci20
ms/http_port = 8021
SAP Web Dispatcher Parameter
wdisp/auto_refresh = 120
wdisp/max_servers = 100
wdisp/shm_attach_mode = 6
configuration for large scenario
icm/max_conn = 16384
icm/max_sockets = 16384
icm/req_queue_len = 6000
icm/min_threads = 100
icm/max_threads = 250
mpi/total_size_MB = 500
mpi/max_pipes = 21000
#maximum number of concurrent connections to one server
wdisp/HTTP/max_pooled_con = 2000
wdisp/HTTPS/max_pooled_con = 2000
SAP Web Dispatcher Ports
icm/server_port_0 = PROT=HTTP,PORT=8022
icm/server_port_1 =
SAP Web Dispatcher Web Administration
icm/HTTP/admin_0 = PREFIX=/sap/wdisp/admin,DOCROOT=./admin,AUTHFILE=icmauth.txt
Has anyone else experienced this issue before.
I have read OSS notes: 1101010, 1068501, 1048692, 1068501 and does not appear to be relevant for my patch level.
Best Regards
Michael
I had removed teh parameter ms/http_port = 8021 from my DEFAULT profile and all worked. thanks for all the responses.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Michael,
What is the product you are using ?
For an ABAP+JAVA instance you should have two profiles. i.e one is the central instance profile and other is the SCS instance profile.
There is a parameter ms/server_port_0 = PROT=HTTP,PORT=81$$ in the profile.
SCS instance stands for Java and DEVEBMGS profile will point to ABAP.
Check the DVEBMGS instance number. If its 00 then your ms/http_port on the web dispatcher should point 8100.
Check the above parameter and revert.
Cheers..,
Raghu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Michael,
I hope your abap message service port is not 8021. It is 8020.
Change the ms/http_port in the web dispatcher profile to 8020 and then give a try.
Cheers...,
Raghu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Raghu,
thank you very much for the response.
I updated the ms/http_port in the abap and the sapwebdisp.pfl and I still get the same error.
Should I be updating the table twpurlsvr with the information as well?
Which logfiles can I use on the ABAP side to trace the error? Or should I just increase th sapgwe trace level and keep an eye on that?
kind regards
User | Count |
---|---|
89 | |
10 | |
9 | |
9 | |
9 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.