NWDS - Track (existing dev config) not available in the list to import

[Former Member]

Experts,

1. I have already existing four different tracks in my NWDI with all the components CMS, CBS, DTR, SLD working fine.

2. A user is assigned with appropriate roles of NWDI developer and NWDI administrator and has correct authorizations for roles and groups.

3. When this user tries to import via the 'Development Configuration Import' and remote option in the NWDS, he is able to see only two tracks in the list instead of four.

4. There are no errors, just the fact that instead of four tracks entries only two are available in the list.

What is the issue here?

Regards,

Kaushik

[ErvinSzolke · Accepted solution]

Hi Kaushik,

are you sure that you are importing from the proper SLD?

Please check the SLD URL in CMS -- Landscape Configurator -- Domaina Data tab

Now ask the developer colleague to check in the NWDS -- Window -- Preferences -- Development configuration pool settings if he specified this URL.

Is this reproducible for all the developers or only for one?

After a track is saved in CMS, it gets registered in SLD. You can check if the tracks are really available in the SLD (again in the SLD which is registered on the Domain Data tab):

http://<host>:<port>/sld --> Administation --> Content Maintenance --> Design Time Configuration

(as of CE the same settings is reachable from the main screen under the link CIM Instances).

Here you will see obviously 8 entries if you have 4 tracks, since both the dev and cons buildspaces are registered separately.

If not all of the 4 tracks would be available here, then make an attempt to resave the track in the CMS webui -- Landscape Configurator -- Track Data tab.

Thanks and Regards,

Ervin

Edited by: Ervin Szolke on Sep 29, 2011 4:32 PM

[Former Member · Accepted solution]

Hello Ervin,

Firstly, apologies for getting back to this thread after a long time.

And thank you very much for the precise steps you mentioned.

Here's my update:

1. The SLD url in Domain data tab and in the Studio are consistent/correct. - correct SLD is being used.

2. Yes this happens for all developers

3. I could see the Design Time Config under CIM instances (SLD on PI 7.1) - there are only two tracks available (4 entries - 2 each for _dev & _cons)

4. Logged into NWDI -> CMS with admin user/password.

5. Tried saving (Change -> Save) the track under CMS -> Landscape Configurator -> Track Data, but it results in error.

Exact error description is:

"Unexpected error; inform your system administrator: User not authorized. (Service call exception; nested exception is: com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (401) Unauthorized. The requested URL was:"http://<host>:<port>/CBSWebService/CBSHttpSOAP?style=rpc")"

I would try and search about this error, but please do let me know if you already know what it means.

Regards,

Kaushik

[Former Member · Accepted solution]

Just to document our experiences for future reference:

We just changed our NWDI to use a new SLD following SAP Note 1031984. Additionally, the J2EE_ADMIN user on the new SLD had a different password than the on the old SLD, so we also followed SAP Note 896427.

As the J2EE_ADMIN user needs to have the same password on the NWDI system and the SLD system, we changed its password  on our NWDI system to reflect the password of the user on the new SLD.

After entering the new password in NWDI > CMS > Landscape Directory > Tab "Domain Data" > CMS password" and saving it, the J2EE_USER got locked almost immediately, resulting in exactly the error message from above: "Unexpected error; inform your system administrator: User not authorized. (Service call exception; nested exception is: com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (401) Unauthorized. The requested URL was:"http://<host>:<port>/CBSWebService/CBSHttpSOAP?style=rpc")".

Apparently something on the NWDI still used the old password. We restart the whole NWDI server which solved this problem.

[edited formatting and added links]