SAP Knowledge Base Article - Preview

2467196 - Web Dispatcher "-checkconfig" fails when SSL is used for the metadata exchange with Application Server

Symptom

The metadata exchange of the Web Dispatcher was configured to use HTTPS with the parameters:
  wdisp/ping_protocol = https
  wdisp/group_info_protocol = https
  wdisp/url_map_protocol = https

or by setting the argument SSL_ENCRYPT=2:

wdisp/system_<X> = SID=<SID>, MSHOST=<message server hostname>, MSPORT=<message server HTTP port>, SRCURL=/, SSL_ENCRYPT=2

or:

wdisp/system_<X> = SID=<SID>, MSHOST=<message server hostname>, MSSPORT=<message server HTTPS port>, SRCURL=/, SSL_ENCRYPT=2

or by setting the argument CONFIG_PROTOCOL=https:

wdisp/system_<X> = SID=<SID>, MSHOST=<message server hostname>, MSSPORT=<message server HTTPS port>, SRCURL=/, CONFIG_PROTOCOL=https

The following error occurs when calling "sapwebdisp -checkconfig pf=<WDP profile>":

   WARNING: No active https port for group into retrieval for ABAP stack available!

Pure_ABAP.jpg

Or below error if backend system is Pure Java system:

   Checking J2EE serves with URL "/index.html":
   Checking JE22 server https://<hostname>:0...
   ERROR: Connection to server <hostname>:0 failedWARNING: checking JE22 server failed: Network error <NI><-8>

Pure_Java.jpg


Read more...

Environment

  • SAP Web Dispatcher Release 742 and above

Product

SAP NetWeaver all versions

Keywords

webdisp WDP communication SSL certificate , KBA , BC-CST-WDP , Web Dispatcher , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.