Skip to Content
avatar image
Former Member

Getting error track in CBS in metadata and used DCs

Hello Experts,
  We are migrating tracks from 7.0 to 7.31 ,
We have followed the following procedure to do the same.

1)Downloaded the SC from old NWDI and imported to the new one

2)after creating a track we added the imported SC and added 7.31 relevant dependencies(

SAP_BUILDT

EP_BUildT

ENGFACADE

FRAMEWORK

WD-RUNTIME

COMP_BUILDT

ECM-CORE

ESCONF_BUILDT

ESF

MOIN_BUILDT

ENGINEAPI)

3) Added .SCA files related to these std SC in inbox folder

4)Updated CMS

5)Check in the SC (Std and Custom) till assembly

6)Now when i go to CMS and see i find  various DC to be broken and few dirty few metadata ,used DC in Red signal.

Kindly suggest where we are going wrong.

Thanks ,

Regards,

Prajakta K

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Jul 03, 2013 at 08:30 AM

    Hi Prajakta,

    the error is visible at the end of the attached text file:

    'freescale.com/TestPar_JDI' DC of 'freescale.com_INTERNAL_WDPS_1' compartment USES 'sap.com/com.sapportals.htmlb' DC, does not exist [public-part: default] AS Build-Time Dependency

    [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]: Invalidated

    Apparently your DC has a reference to a port al related DC but its SC has not been imported into the track and this is why you have broken DCs in their metadata. If it is about broken DCs and the problem is about metadata then most of the cases it is about depencency issue.

    Check again your track configuration and ensure that the corresponding SC(s) -- which includes the DCs like the one I marked with bold letters -- have been imported into the track.

    One potential SC is the EPBC and EPBC2 SCAs, but I am not a portal expert, so I am not that familiar with these SCs. If you import these and you still face the same problem, then check again the end of the request log (the one you also attached) and check what other errors are still displayed (most likely after importing the above SCs either all the errors will disappear or the amount of errors will be less), because that means there are still SCs to be imported.

    I hope this helps.

    Best Regards,

    Ervin

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Prajakta,

      can you build that DC in your NWDS locally after the migration?

      If yes, checkin the software, activate it, etc, and then check again whether you face the same error in the build log, because maybe after this you still have broken DCs, but the reason should be different.

      Best Regards,

      Ervin