Missing product instance "SAP Web Dispatcher" in product "CRM 7.0 / NW7.01"

[Former Member]

Hi to everbody!

We implement a new CRM 7.0 / NW7.01 landscape which should be monitored and administrated centrally with the SolMan. The installation includes a SAP Web Dispatcher.

All system are SLD registered and can be maintained in TA SMSY, even the Web Dispatcher as technical System. So far so good.

Now I like to add the technical system WDP (the web dispatcher) to the productive product system CRM. Unfortunately there is no product instance "SAP Web Dispatcher" available when the product system has the product version "CRM 7.0 / NW7.01".

Without the assignment to a product system I'm not able to do the SolMan Diagnostics Setup Wizard and the ISAgent installation for the Web Dispatcher WDP.

Does anybody have an idea or solution? Do I have to add the product instance "SAP Web Dispatcher" manually?

Have a nice day!

Sascha

[Former Member]

Hello again!

Sometimes it's a good idea to follow a different and tricky way to reech the aim. So I did.

The idea was to assign the technical system WDP to a product system with a different product version then "CRM 7.0 / NW7.01", for example a Netweaver 7.0 with EHP1 in TA SMSY. How wonders the WDP is now on the list of Java systems which could be setup with Diagnostics Wizard.

After entering some configurations, like port, URL, instance number, the setup was successfull and all available informations are shown in wily Workstation.

The last step was to remove the technical system WDP from the product system.

At least I'm very interested in an official way to assign a technical system with type Web Dispatcher to a product system with product version "CMR 7.0 / NW7.01".

Have a nice day!

Sascha

[Private_Member_19084]

Hello Sascha,

I have a similar requirement now.

Which product version did you apply, the one from CRM?

Kind regards

[Miguel_Ariño]

Hello,

It looks like the SAP Web Dispatcher was considered not to be part of CRM, but only of Netweaver . SAP Web Dispatcher has no dependencies to any CRM components, so this is likely why it was not added in order to limit complexity of product definitions. 

Why is this? Well, if we add all possible product instances to every product, PPMS would become totally unmanageable. Only direct dependencies are added, and this is not such a case.

Best regards,

Miguel Ariño