Name-server importing wrong url?

[Former Member]

Dear experts,

I am trying to import a track from NWDI so I can add development components to a software component in the track.  The problem I am having is:

I keep getting this error " Syntax of 'nibco.com/nbdc/nibcotst' is not valid : Invalid name: appropriate prefix not found; choose another name or another name server".  We haven't had this problem in the past...When I go to CMS->Landscape Configurator and click on display development configuration button I get this configuration:

The url for name-server-url property is correct: http://xxxxxxxx:xxxxx/sld/cimom

But when I import to NWDS the url get's changed:

One NWDS:

Another NWDS:

For some reason it is changing the naming server url on import to http://xxxxxx:xxxxx/sld/name and http://xxxxxxxx:xxxxx/sld.  Any help is much appreciated.

Thanks,

Bradley Sorensen

[former_member198633]

Hello Bradley,

A few hints to resolve the problem:

and

#1816503 - NWDS not identifying Vendor/Name Prefix defined in SLD

Best Regards,

Peter Tari

Message was edited by: Ervin Szolke I have corrected the note link.

[Former Member]

Hi Peter,

Thank you for your reply Peter but your links don't seem to help with my specific problem.  Your second link seems to be broken...My problem is that the development configuration xml seems to have the correct name-server url but when the configuration gets imported to NWDS the url changes.  I even tried downloading the xml manually and doing a manual import instead of importing from SLD and still have the same problem.

Thanks,

Bradley Sorensen

[ErvinSzolke]

Hi Bradley,

I did not fully read this conversation, but this is how it works in general.

1. Name server is changed in SLD.

2. Track "in CMS' webui -- Landscape Configurator" has to be re-saved in order to have the change reflected there (this is what you have done so far)

3. NWDS development config has to be re-imported on client side. Otherwise it'll consider the old configuration, since after the first sync it creates a local file called ".confdef" and works from that one.

So as a hint: if you have no open activities in your devconfig, you can even delete it from your NWDS and import it again that makes sure it uses the updated devconfig .

There is also an "Update Development Configuration" option in the context menu of the Development Config in your NWDS, but if that would not work give it a try re-importing the development config eventually in a new NWDS workspace.

I hope this helps.

Cheers,

Ervin