NWDS 7.3 some infrastructure servers cannot be contacted

Question

Hi
When I am trying to Import the track in NWDS 7.3 I am getting the following error.
"some infrastructure servers cannot be contacted"
I am trying to Import from System Landscape Directory
and in Windows --> Preferences --> Development Infrastructure --> System Landscape Directory
When I place the URL and click on Ping
The Ping is successful
When I am trying to import a New Development Configuration by doing Import from System Landscape Directory and I can see all my tracks and everything
I can see Remote Development Configuration
But when I try to logon to Development Infrastructure it gives me the following error
"some infrastructure servers cannot be contacted"
Can some one let me know what I need to do to resolve this error.
Regards
JM

Answer 1

Hi,
I think I can explain this. Please correct me if my understanding on the problem is wrong.
1. If you save a track, then it creates the server side devconfig xml in CMS. (this includes SC dependencies, and information on Nameserver, cbs, dtr and cms urls, nothing more really)
2.In the same time it also registers in SLD, but only the name of the devconfig, and the server where CMS is located. Again, in SLD we find only the info "where is the CMS that holds the details of the devconfig".
Why is this important? Let's say you have 5 CMS servers and all of them are bound to the same SLD.
Now if you created 1 track in each of the 5 CMS servers, then in SLD you'll have 10 entries registered.
devconf1_dev -- holds data about CMS1 URL
devconf1_cons -- holds data about  CMS1 URL
devconf2_dev -- holds data about CMS2 URL
devconf2_cons -- holds data about  CMS2 URL
devconf5_dev  -- holds data about  CMS5 URL
devconf5_cons  -- holds data about  CMS5 URL
this is only one possible scenario, many other can be imagined, needless to say. Just imagine that from the above example some of the CMS servers are bound to other SLD servers.
Now what happens in NWDS?
You enter into the preferences only 1 URL that is the SLD. NWDS goes to SLD, and retrieves the LIST of development configurations, so NWDS doesn't have to know about all those 5 CMS servers, only about 1 SLD server that takes care about the rest. NWDS talks only to SLD when importing development configurations.
The thing is that the devconfig is retrieved only once (unless you explicitly import dev config again)and will be stored on the client side in a .confdef file, and as of that point no more communication takes place between NWDS and SLD, but NWDS uses the locally stored .confdef and contacts the corresponding CMS directly according to that.
If you see the error about "some infrastructure servers cannot be contacted" then I can think of 2 issues.
1-
When you import, NWDS has to list all the development configs according to the SLD devconfig list it retrieved from SLD. If CMS1-4 is up and running, but say CMS5 is down (or has any other accessing issues, e.g. its user store includes outdated nwdi communication user, etc), you receive this error.
2-
The .confdef that is used holds old data, and the server name or port has been changed in the meantime on the server side development config. This case the resolution is to reimport the development configuration after ensuring SLD holds correct data, and the servers maintained there are reachable. If the server side devconf is wrong as well, then ensure that the data on the domain data tab, track data tab are correct, and resave the track. This will recreate the server side devconf, and creates the entry in that SLD that is added on the domain data tab. After this you can go for reimporting the devconfig in NWDS, since that has to be updated too, to avoid that the outdated local .confdef is used.
Check the SLD development configuration list here:
/sld --> CIM Instances (on lower releases it is under Adminstration -- Content Maintenance) -- Design Time Configuration.(as of 730 you can refer to the tab "Associations" to see which CMS is assigned to the given devconfig).
The pinging of SLD is positive, because the SLD is reachable, but the associated CMS servers are not. This is why ping works, but still errors about non-reachable servers are reported.
I hope this helps.
Best Regards,
Ervin