Skip to Content
0

NWDI 7.5 upgrade issue - DCs not visible in NWDS

Aug 18, 2017 at 11:08 AM

242

avatar image
Former Member

Hello Everyone,

We are upgrading our NetWeaver from 7.3 to 7.5, we are facing few issues:

We have recently installed a new NWDI 7.5 system on which we need to migrate the old portal tracks from NWDI 7.3

We have followed the below steps:

1. The Functional Unit configuration UI wizard has been run to set up the domain and CMS.

2. Copied the archives of the custom SC's from old Inbox to the new inbox.

3. Created new SC's in the new SLD with same name as old SC's and assigned dependencies of newer version.

4. Created a new track for Portal on NWDI 7.5 and added these custom SC's to the track.

5. Checked-In the Custom and dependent standard SC's from Transport Studie.

6. Imported in Development Queue.

Now the issue is, when we try to access the track from NWDS, we are unable to see the Webdynpro DC's associated with those custom SC's.

Those DCs are visible in DTR but not in the track that we import in NWDS.

Could you provide a hint on which step or configuration are we missing here?

What should be the deployment method of runtime systems? Should it be SDM or deploy controller? We have selected SDM but the Web Dynpro Java application doesn't get deployed on the portal server when we check-in & import the SC's in the transport studio.

Thanks

Priyanka

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

2 Answers

Best Answer
Milen Dontcheff
Aug 21, 2017 at 02:56 PM
2

Please execute a Synchronization from the NWDS with the DTR server.

In this document

https://archive.sap.com/documents/docs/DOC-3204

in chapter 6 there is a screenshot about this.

Show 1 Share
10 |10000 characters needed characters left characters exceeded
Former Member

Thanks Milen for your helpful answer.

The issue is resolved.

The DCs were broken because while importing the SCAs from the older track, the correct SP version was not defined resulting into broken DCs. Corrected the same, imported the track and synchornized the DCs.

0
Milen Dontcheff
Aug 18, 2017 at 11:25 AM
1

1.

If the import in the CMS - Transport Studio - tab Development is successful, then after the import of the track in the NWDS it is necessary the DCs to be synchornized.

In the NWDS, only DCs in the custom SCA will be available for modification and customizations. The other DCs, from the SCA dependencies, might be refered only with the public parts.

2.

"What should be the deployment method of runtime systems? Should it be SDM or deploy controller?"

There is no SDM since NW 7.1. Hence the P4 port, configured in the CMS - RTS must be be 5xx04, where the xx is the instance number of the target deployment RTS.

3.

"We have selected SDM but the Web Dynpro Java application doesn't get deployed on the portal server when we check-in & import the SC's in the transport studio. "

This is wrong configuration. I have explained why. When you configure correctly the RTS, please review the following Trouble Shooting Guide and to cross check whether the connection test works

http://wiki.scn.sap.com/wiki/display/Java/%28NWDI%29%28CMS%29Q0002

Show 3 Share
10 |10000 characters needed characters left characters exceeded
Former Member

Hi Milen,

Thanks for your response!

1. I followed the steps recommended by you for Runtime systems in CMS and the deployment of SC's/DC's is successful. I could see the custom SCs & their correpsonding DCs in the portal server.

2. However we are still facing problem in accessing the custom DCs in NWDS 7.5. After successful import of SCs in Development tab(Transport Studio),I imported the track in DI perspective of NWDS. When i expand the tree structure of custom SC present in that track, it still doesn't show up the custom DCs.

I checked those custom SCs NWDS.jdi workspace, _comp folder is blank. Am i missing any configuration in the CMS?

I verified that those DCs are visible in both CBS and DTR.

Regards

Priyanka

0
Former Member

Hi Millen,

Those DCs were broken causing this problem. I re-imported those SCs by correcting their version. Issue is resolved.

Thanks a lot!

Priyanka

0

I'm glad to understand you've managed to resolve the impediment.

0