Change SLD url in NWDI track

[irijsdijk]

We recently moved a development PO system from server A to server B. In this process, the host name of de PO system was changed. I managed to update all references to the old system (called PODEV), except one reference in the NWDI track which still references the old SLD. I am unable to edit this track, because the old SLD no longer exists. I already tried SAP note 1031984, but the SLD url does not get updated.

Please share any thoughts on how to change the SLD here.

[Robert_Russell]

From the screenshot it looks like you are using CM Services and not CMS.

Try the SAP note for CM Services linked below. It states it is changed from the CTS+ system (usually SolMan). Update the DI_SLD_URL for the development configuration system (DI_SYSTEM=true) and take the options to update the config service.

1797220 - CM Services URL can not be changed after system copy

[irijsdijk]

Thanks, this looks very promising. Unfortunately the used SolMan system is unable to connect to the new NWDI environment. I'll have the basis guys set up a connection.

[former_member189220]

Hello Iddo,

If this is indeed true "the old SLD no longer exists", then the only way forward is to change the local hosts file (which is used in the domain name resolution process). In particular, it is necessary to temporarily reroute all connections (pointing to the old SLD) to point to the new SLD.

(f.e. by setting the IP address of the new SLD to match to the FQDN of the old SLD. In this way, you will re-route the changing request of the CM Services to the IP address of the new SLD)

If NWDI is running on Windows, you can do this via "C:\Windows\System32\drivers\etc\hosts"file. For other OS, there should be a relevant equivalent configuration setting. Please do this out of the business hours, because during this change of the hosts file is active, the network traffic will be influenced.

Regards,

[irijsdijk]

Hi Milen,

Thanks. I already tried that, but unfortunately the ports of the old and new server are not the same.

Iddo

[former_member189220]

Hello Iddo,

1.

In such case, you can create a new development configuration and continue the software logistics there. This dev. configuration (which contains the old not-existing SLD) can not be used for developing and transporting new customizations. (there is a very thin chance this to happen with NWDS which has this dev.conf. imported. Probably, it would be possible to do some limited sw development there.Yet, if a new DC is created, with new vendor, the Name Service will have to be contacted - and as we know the Name Server is a role of the SLD, as well as the name prefixes are stored in SLD)

2.

If necessary, the source code could be replicated from the "old" DTR workspace of the development configuration (where SLD can not be changed) to the "new" DTR workspace of the "newly" created development configuration (from the STMS transaction). More details in:

Replicating a Track into a Different DTR Repository

https://help.sap.com/saphelp_nw73/helpdata/en/49/101b273d9d132ee10000000a421937/content.htm

https://help.sap.com/doc/39222f18c2ab428985c7f3e041b11e26/7.5.9/en-US/49101b273d9d132ee10000000a4219...

3.

With all my respect, I do not think, it will be possible to change the SLD url from the ABAP side (STMS transaction). In the SAP KBA 1797220, this has been mentioned at first place as a fundamental requirement: "It is assumed that source and target NWDI and SLD are up and running."

Regards,