Sometimes the SLD registration via sldreg fails due to HTTP(s) error. For analyzing these issues, HTTP trace is required.
* Command line used to start sldreg:
sldreg -connectfile /<some path>/slddest.cfg -file /<some path>/sldreg.xml -logfile /<some path>/sldreg.log
Profile is not explicitly specified on cmd line using pf=<profile>
Thu Oct XX xx:xx:xx 20xx Used URL: http://<SLD host>:<SLD port>/sld/ds
Thu Oct XX xx:xx:xx 20xx Proxy is not configured.
Thu Oct XX xx:xx:xx 20xx HTTP open status: false - NI RC=0
Thu Oct XX xx:xx:xx 20xx Failed to open HTTP connection!
Make sure HTTP tracing is active (-logfile <filename> and '-httptrace' on cmd line or 'sldreg/httptrace = 1' in profile) and check sldreg_http_trace.log.
- SAP netweaver relaease independent
- SLDREG release independent
BOE, tomcat, HANA, Data Service, Kernel, ASCS, sapstartsrv, sldreg_httptrace , KBA , BC-CCM-SLD , System Landscape Directory / Component Repository , How To
About this pageThis 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.