change sld in nwds and cms

[Former Member]

Hi,

we have a working version of NWDI in place, i.e. we are using NWDI for transports between DEV,QA and PROD. Now we have a requirement to use a different SLD for NWDI.

1. we specify SLD url in NWDS and in "Domain" tab of "Landscape configurator" of CMS. Is it enough to just change these URL's pointing to new host of SLD.

2. how to transport the dev configs from the old SLD to new SLD system.

3. should I reimport the dev configs in my NWDS.

Did anyone encounter this situation, if so could you please guide me.

Regards

[Former Member · Accepted solution]

Do not forget to update the Name Server configuration of the DTR. This also points to an SLD.

[Former Member · Accepted solution]

I'm doing the same thing, but the change is not showing up when I re-import the development configuration in NWDS.

I changed the URL in NWDS, in the domain tab in the landscape configurator, and in the name server configuration in the DTR.

Did I miss something?

[Former Member · Accepted solution]

Hi Christopher Esser

I am facing exactly this issue.

When I import the development configuration after changing the SLD in NWDI and NWDS the development configuration is still pointing to the old SLD.

Did you find a solution to this issue?

/Jacob

[p330068 · Accepted solution]

Hi Jacob ,

Please also update SLD DataSupplier in Visual Administrator and test it...it should be successful with all three tabs.

Hope it helps,

Regards,

Arun

[Former Member]

Hi Shiva,

Whenever a track definition changes, its helpful if you do a System Restore. Please see if that helps.

Regards,

Rajit

[Former Member]

I am configuring 2004s-Sp7 NWDI ...

I have a problem in the step DEVELOP USING NWDI, when I am trying to import the development configuration.....

I am not getting the "Name Server" in build variants...

Anybody has any idea please let me know.....

Thank U in advance,

[Former Member]

1. That should be all that is required.

2. You can just do an export and then an import. When we did it we had issues with the dependancies of a custom SC not being included in the differental export so we exported the whole thing.

3. Yes because you are working with a new SLD now.