cancel
Showing results for 
Search instead for 
Did you mean: 

Can I register webdispatcher and saprouter in SLD?

Former Member
0 Kudos

We've fronted all our systems (abap or java or both) with a webdispatcher.

Is there any way to (preferrably automatic) register these webdispatchers in SLD.

Our developers are starting to use SLD as a data source for connection info,

but all our systems are firewall protected. Same question but regarding saprouter.

I would also need some way to tell applications using SLD for connection info to employ these filtering tools rather than direct connections.

Ken

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

It seems that a 7.1x saprouter will register in SLD.

Curiously a 7.20 saprouter DOESN'T rrgister in SLD... perhaps a later patch level???

Ken

bxiv
Active Contributor
0 Kudos

@Ken even though 7.20 does not register in the SLD, it is possible to have it display in the LMDB.

Have you looked here:  http://wiki.sdn.sap.com/wiki/display/SMSETUP/Managed+System+Setup+of+SAP+Router+in+SAP+Solution+Mana...

Former Member
0 Kudos

hi ken,

check this note is applicable for you

1018839 - Registering in the System Landscape Directory using sldreg

and look at the help link for the paramaters required for sap webdispatcher.

http://help.sap.com/saphelp_nw04/helpdata/en/de/89023c59698908e10000000a11402f/frameset.htm

Since the SAP Web dispatcher connects itself to the SAP message server and communicates with it via HTTP, the following parameters must be set correctly in the SAP Web dispatcher profile.

· rdisp/mshost: Host name of the machine on which the message server is running

· ms/http_port: The port on which the message server receives HTTP requests

For the message server, this port must be configured as an HTTP port, by setting parameter ms/server_port_ in the message server profile (see Message Server Parameters).

check the config again.

Jansi

Former Member
0 Kudos

This one needs some explaination!

I normally code:

rdisp/mshost = sap_backend_host

ms/http_port = 81##

This is replaced by

wdisp/system_0 = HOST=sap_backend_host, PORT=81##, SID=SAP_BACKEND_SID, NR=<sap backend instance name, eg SCS##>

Excerpt from dev_webdisp_watchdog trace file:

[Thr 47319736972384] *** WARNING => Both wdisp/system_0 and rdisp/mshost,ms/http(s)_port specified. Ignore rdisp/mshost, ms/http(s)_port. [icrxx_mt.c 1245]

[Thr 47319736972384] *** WARNING => IcmParseSubParam: unknown subparam "HOST" for parameter: HOST=sap_backend_host, PORT=81##, SID=AAA, NR=SCS## [icxxpara_mt. 429]

[Thr 47319736972384] *** WARNING => IcmParseSubParam: unknown subparam "PORT" for parameter: HOST=sap_backend_host, PORT=81##, SID=AAA, NR=SCS## [icxxpara_mt. 429]

[Thr 47319736972384] *** ERROR => no host/port set in wdisp/system_0 [icrxx_mt.c 1312]

Apparently Web Dispatcher didn't like my interpretation of the documentation. And it didn't barf where I thought it would (NR suggests NumbeR, so maybe ## but the doc says msg server instance NAME)

Note: I didn't actually code ##, rather I inserted msg server instance number.

If one gets this form of defining the backend web dispatched system working, does startsapsrv then call the backend requesting it register in SLD? I don't see any SLD connection info.

Ken

former_member191911
Contributor
0 Kudos

Hi Ken,

Did you manage to solve this issue? I'm facing exactly the same...

Kind regards,

Mark

Former Member
0 Kudos

Ken/Mark,

There is a better description of the wdisp/system_0 parameter here:

http://help.sap.com/saphelp_nw73/helpdata/en/1b/b0fd8a12344c4ca89b7a1c5d1d7310/content.htm

For example:

"the parameter wdisp/system_0 contains both optional parameters NR and SCSHOST, which identify the back-end system in the SLD, in the case of SLD registration."

Use the NR option to specify the system number of instance that contains the message server. This can be an SCS instance (AS Java), an ASCS instance (AS ABAP), or a classic central instance (DVEMGS). So it really is a number (##)

In their example: wdisp/system_0 = MSHOST=ms.external.sap.com, MSPORT=8101, SID=ERP, SRCSRV=*:*, NR=01, SCSHOST=ms.internal.sap.corp

Cheers, Bruce.

stuart_campbell
Active Contributor
0 Kudos

Hi Ken

It should be possible to register webdispatcher in the SLD as a data supplier -->

http://help.sap.com/saphelp_nwpi71/helpdata/en/51/10ce90600f4e68afd660060876162e/content.htm

Best wishes

Stuart