Missing Name Server-Configuration in imported Development Configuration

[Former Member]

Hello,

we have several tracks in different Development Configuration Paths. Importing a Development Configuration from the first path, the DevConf correctly specifies the SLD Name Server. However importing another track from an other path, the DevConf has no Name Server, instead the Component Properties in the NetWeaver Development Studios show "- - - -" instead.

Are there any track-specific configurations to get the Name Server Configuration applied to the DevConf?

Thanks

[ErvinSzolke · Accepted solution]

Hello Kai,

I don't think this is the solution. See the picture, I assume this was also the symptom you faced (see attached screenshot DevConfimportstatus.JPG).

For this the answer is:

If you save a track in CMS WebUI, then the development configuration will be created/upated. In NWDS you'll see on the status screen the URLs exactly in the form in which you have specified them inside the track configuration (You can check the Development Configuration at: CMS webui -- Landscape Configurator -- check the tab "Build Variants" and there you have a button to display the configuration). DTR and CBS specific URLs are taken from the "Track Data" tab, CMS is taken as you have entered it on the "Domain Data" tab and last but not least u2013 our main concern is this symptom --, the nameserver will ll be taken from the SLD (See "CIM Server URL" at Nameserversetup.JPG I attached. This is from 640 times, but the setup is the same on higher releases). Notice, SLD is part of the development process, but not part of the NWDI itself. The NWDS's preferences has no influence on this status screen at development configuration import.

Here comes a problem: customer creates a track, and forgets to specify the nameserver in SLD. At this point the track can be saved without problems, but attempting a development configuration import into NWDS results the phenomenon, that the nameserver URL is empty on the status screen (see attachment DevConfimportstatus.JPG). The solution is of course to create/update the missing nameserver specification in SLD, and then resave the track, to update this information in its development configuration.

I hope this helps.

Best Regards,

Ervin

[Former Member · Accepted solution]

Thank you for your reply Ervin. Unfortunately your image-links are broken.

I have double-checked the build-variant XML-File and I wonder where the SLD Name-Server is explicitly stated. My Configuration is attached at the bottom, with all <sc-compartment> ommited. Nevertheless, I am aware that the configuration is collected from Track-Configuration and the Name-Server from the SLD, which are and were both configured. It really seems NWDS was not able to pick up the proper Name-Server since the Track-Configuration had an invalid configuration-path. With other tracks the Name-Server worked like a charm.

Looking forward to non-broken images, thank you very much for helping to clarify this issue!

Kai

<?xml version="1.0" encoding="UTF-8"?>
<configuration caption="CAFTEST_dev" cms-url="http://innsapli6:50000" config-version="0000000040" document-type-version="1.0" is-local="no" name="NDI_CAFTEST_D" name-server-url="http://innsapli6:50000" sl-location="NDI_CAFTEST_D" sld-url="http://innsapli6:50000" xsi:schemaLocation="http://xml.sap.com/2002/11/DevelopmentConfiguration confdef.xsd" xmlns="http://xml.sap.com/2002/11/DevelopmentConfiguration" xmlns:IDX="urn:sap.com:DevelopmentConfiguration:1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<config-description>CAF Sandbox_dev</config-description>
<build-server><a href="http://innsapli6.inndom.intern:50000" TARGET="test_blank">http://innsapli6.inndom.intern:50000</a></build-server>
<properties>
<NOTIFY_TCS xmlns="http://xml.sap.com/2003/07/DevelopmentConfiguration/Transport-Controller">true</NOTIFY_TCS>
<SDM_URL xmlns="http://xml.sap.com/2003/07/DevelopmentConfiguration/Transport-Controller"><a href="http://dummySDMURL:50018" TARGET="test_blank">http://dummySDMURL:50018</a></SDM_URL>
<TCS_SERVLET xmlns="http://xml.sap.com/2003/07/DevelopmentConfiguration/Transport-Controller"><a href="http://innsapli6.inndom.intern:50000/TCS/Deployer" TARGET="test_blank">http://innsapli6.inndom.intern:50000/TCS/Deployer</a></TCS_SERVLET>
<TRANS_D xmlns="http://xml.sap.com/2003/07/DevelopmentConfiguration/Transport-Controller">/usr/sap/trans/EPS/in/CMSinnsapli6NDI</TRANS_D>
</properties>
<sc-compartments> ... </sc-compartments>
</configuration>

[ErvinSzolke]

Hello Kai,

I am wondering why the images are broken. Anyway, I upload them again.

Regarding the development configuration:

If you have no nameserver maintained in the landscape, then of course the development configuration is not including this information either, and since you import as per the server side development config when you import in NWDS, the development config import will not have this information either.

In my case, one of my development configuration looks this way

(only the beginning part of it. Notice the section name-server-url😞

<?xml version="1.0" encoding="UTF-8" ?> 
<configuration xmlns="http://xml.sap.com/2002/11/DevelopmentConfiguration" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xml.sap.com/2002/11/DevelopmentConfiguration confdef.xsd" name="ERP_CAFDEV_D" 
document-type-version="1.0" caption="CAF Development_dev" config-version="0000000323" 
sl-location="ERP_CAFDEV_D" cms-url="http://nwbud01.test-bud.sap.corp:50000" 
name-server-url="http://nwbud02.test-bud.sap.corp:50000/sld/cimom" is-local="no" xmlns:IDX="urn:sap.com:DevelopmentConfiguration:1.0">
<config-description>CAF Development_dev</config-description> 
<build-server><a href="http://nwbud01:50000" TARGET="test_blank">http://nwbud01:50000</a></build-server> 
<sc-compartments>

Best Regards,

Ervin

[Former Member]

Thank you for your reply Ervin

the images are broken again I think the Jive-Forum has some issues with that...

I rechecked my posted XML and it also correctly states the name-server-url. Besides that, the Name-Server is of course correctly configured and is recognized by NWDS with most Tracks. Only one track with the trailing slash in the Configuration Path had the issue, that the name-server was not recognized by NWDS. This seems to be a bug.

Thank you very much for keeping up.

Kai

BTW, we are using NW CE 7.2 and the corresponding NW 7.2 NWDI

Edited by: Kai Meder on Nov 23, 2010 2:01 PM

[Former Member]

NWDS will only use the name server if a Development Configuration Path for the track in NWDI CMS is specified.

Additionally the specified DevConf Path must not end in a slash!

/test    OK

/test/   FAIL

solved