Broken Dc's in CBS

[Former Member]

Hi All,

I am using CE7.1. I faced a problem while creating projects locally. When i checked in CBS, in my track , all the DC's are shown

as broken DC's. How to fix this.

Could anyone help me in resolving this?

Thanks!

Swarnaprakash

[Former Member · Accepted solution]

Hi Swarnaprakash,

Please check the log-files using the Requests link in your CBS-view. They give more information about the request and associated build.

Are you sure all necessary sofware components are added to your track and imported in de development track?

Hope this helps.

Regards,

Alain

[Former Member · Accepted solution]

Hi Alain,

'cccc.com/dc/xxxx_search_ssss_screen' DC of 'cccc.com_XXXX_1_0_1' compartment USES 'sap.com/tc/bl/logging/api' DC,

does not exist [public-part: api] AS Build-Time Dependency

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

This is one of the info in the log. There are lot of errors like this and all the errors are same except this

line 'sap.com/tc/bl/logging/api' " is changing.

I dont have the code in my NWDS. I am able to import the track but not able to create projects due to broekn dc's. Can I fix this problem.

Thanks!

Swarnaprakash

[Former Member · Accepted solution]

Swarnaprakash,

It sounds to me you are using "Projects Dependencies" to other DC-projects in your build path of the DC project. Do not use these "Project Dependencies": all necessary jars's and/or other DC's should be included in your DC-project using the "USed DCs" settings in the DC Metadata. (Local build-paths are NOT stored in NWDI!)

As for the 'sap.com/tc/bl/logging/api', this is a Public Part in the SAP_JEE sca. Make sure this sca is imported in your development track and it is visible in the Active DCs view of the development perspective of your NWDS.

You can check this by checking the .classpath file in your DC project: all entries should refer to jars under the "Development Configurations Root Folder".

The .classpath should NOT be under NWDI-control: it will be generated using the DC Metadata of your DC during DC-Build.

Hope this helps.

Rgards,

Alain.

[Former Member · Accepted solution]

Hi Alain,

As you suggest,

"You can check this by checking the .classpath file in your DC project: all entries should refer to jars under the "Development Configurations Root Folder".

Are you saying that , I should check the classpath file in local Dc project.

I dont have any of the DC's now in local ,since I am getting error while creating projects locally after importing the track from SLD.

Am I getting errors due to broken DC's or does broken DC's impacts while creating projects locally.?Please advise . I am new to NWDS.

Thanks!

Swarnaprakash

[shreyas_pandya · Accepted solution]

Dear Swarnaprakash,

Also go through the following thread on how to add missing build time dependencies, step-by-step guide

Let us know about your findings.

Regards,

Shreyas Pandya

[ErvinSzolke]

Hi Swarnaprakash,

did you manage to resolve the issue? If yes, could you please be so kind to mark the thread as answered? Else feel free to ask.

Thank you for your time!

Best Regards,

Ervin

[Former Member]

Hi Ervin/Shreyas,

I have 2 queries

1) Can I copy the whole content from my present track to a new track? Since I am new to NWDI i thought I can do by this way.

and if i do that correctly and successful , then i can use that track itself ( possible?).

2) Also I tried to export the SCA. I selected my track and clicked export SCA button. It listed out all my SCs.

My project SC -- Usage is DEVELOPED &&& package type is AS ARCHIVE

Other standard SCs-- Usage is REQUIRED &&& package type is AS CHECKED IN

willl I be able to take the archive of my project and if in case I need, can I revert with this archive?

Expecting your suggestion.

Thanks!

Swarnaprakash

[shreyas_pandya]

Hi Swarnaprakash,

for your first query,

1) Yes, there is a facility available in CMS for copying your existing track.

2) Goto CMS >> Landscape Configurator >> select your Track >> goto Track Data.

3) Here, you'll find one button named "Save As..."

4) This operation will make a copy of your track.

5) And this new track you can import into your Developer studio for any modifications.

for your 2nd query,

1) you can export the Assembled .SCA file from the assembly view and deploy it on the target run-time system.

2) But, you can't retrieve all your source code back, even if you import the same same .SCA file into into developer studio using the import SC option.

3) After importing the SC you can only deploy the DC contained inside but you can't create the project structure out of it.

4) As those DC are in the form of Active Archives.

Regards,

Shreyas Pandya

[ErvinSzolke]

Hi,

if the SC has no build time dependency then it is not even showing up on the check-in tab. If this is the case, then of course it makes sense what Shreyas referred to. I did not check the issue in detail. One thing is sure, if the DCs of a dependent SC is not visible in the NWDS, then it is not part of the buildspace (not imported in CMS).

Cheers,

Ervin

[ErvinSzolke]

Hi Swarnaprakash,

as mentioned earlier, this happens if the SCs in question (sap_buildt, sap-jee, etc. the SCs which you are missing) haven't been imported into the buildspace. This is the reason why they are not showing up in NWDS, since there's no place to sync these DCs from... due to the reason again that their import most likely did not take place.

Please go to the CBS webui, select the track (...._D) and after you click on it, you'll get into the "Compartment" view. There look up the SC SAP_BUILDT for instance, and check the "Total DCs" column. You will see there the number 0. If so, this is the reason. You need to achieve that in that column you can see a number higher than 0 (for SAP_BUILDT in this example) and you can fix the problem by going into the CMS webui, onto the "Development" tab and import the SAP_BUILDT sitting in the import queue with status "Waiting for import". Other reason can be of course that the status is already "Import failed". This case you need to check the "Details..." button to find out why the import was not succesful. As soon as you can achieve that the DCs are imported, you need to :

- remove the Development Configuration on client side in your NWDS

- stop NWDS

- start up again NWDS

- reimport the Development Configuration.

Best Regards,

Ervin

[shreyas_pandya]

Hi Swarnaprakash,

Please consider Ervin's inputs, they are highly useful.

Ervin, we are really grateful to have an expert like you in NWDI.

Regards,

Shreyas Pandya

[shreyas_pandya]

Dear swarnaprakash,

Please let me know under which CBS buildspace DCs are broken,

Is it the Development_Buildspace or the Consolidation_Buildspace of your track?

Your DC becomes broken in the CBS buildspace, if you have forcefully activated your activities (using "Activate even if Build Fails" option checked during activation).

CASE1: If the broken DCs are found under Development_Buildspace OR Both then...

you can follow the following steps to resolve

1) Checkout the same DC from the DTR make it consistent first (i.e. the DCs must go through a successful local DC build operation before Checking-In)

2) After successful local build operation, Check-In and then Activate the DC.

3) After activation check the Development_Buildspace once again.

4) If the status of the DC looks fine, then you can release the activities from Transport view of NWDS and later import into consolidation runtime system.

4) If the build space is still having broken DCs, then i recommend you to build the entire SC from the CBS Web UI, and check it once again.

CASE 2: If the broken DCs are found under Consolidation_Buildspace only then...

Please check whether you have released all the pending activities from the Transport View of NWDS as well as successfully imported those activities into consolidation runtime systems from CMS Web UI or not?

Hope this will help you.

Regards,

Shreyas Pandya

[Former Member]

Hi Shreyas,

I dont have the code in local, so I wont be able to check in or activate.

At first I imported the track from DTR and tried to create projects locally and I got lot of errors. So I checked the CBS, there in development_buildspace , it shown as broken DC's. All my DC's were broken.

As you suggested

I go into CBS view and selected my track--> selected my SC in the compartment . There is a option for build. When I clicked that it asking to select variant. In that the build variant is default and required for activation is Null ( showing a hyphen).

Is it rite? Can I go ahead in buliding the SC? or is there anything should come in that build variant dialogue box. Please advise.

Thanks!

Swarnaprakash

[shreyas_pandya]

Dear Swarnaprakash,

As per the error Log detail that you have provided previously, it looks like.

The DC "sap.com/tc/bl/logging/api" which is present under the SC called "ENGFACADE" is not defined as a build time dependency for your Track SC.

Also, you have mentioned that...

There are lot of errors like this and all the errors are same except this line 'sap.com/tc/bl/logging/api" is changing.

This means that you need to make a list of all those DCs and then, you will have to find out under which SC each DC belongs.

Similar to how i have explained about *"sap.com/tc/bl/logging/api" DC belongs to *"ENGFACADE" SC.

To find out under which SC a DC resides, you can follow the below mentioned procedure.

1) Open the Development Infrastructure perspective in your Developer studio.

2) Expand the "MyComponent" SC inside you Local Developments.

3) select any Test DC present in the list

4) Open the Dependencies Tab and click on Add button.

5) Now here, you can type the DC name that you are looking for E.g. "tc/bl/logging/api"

6) After adding it mouse over it and find out The containing SC Name.

This way, once you know the list of all the SCs required, you can add all those SCs as build time dependencies for your main Track SC in SLD.

After the Update the CMS and modify the track by removing the Track SC from the Track and adding it back again.

And then Check-In the newly added dependencies and import them into Development and Consolidation system of your track from CMS Transport Studio.

I hope, that helps.

Let us know about your findings.

Regards,

Shreyas Pandya

[Former Member]

Hi Shreyas,

Thanks a lot for your detailed suggestion. I will try and let you know. But, in the meanwhile, as you suggested I am tying to bulid the SC.

I go into CBS view and selected my track--> selected my SC in the compartment . There is a option for build. When I clicked that it asking to select variant. A dialogue box pops up.In that the build variant column is default and required for activation column is Null ( showing a hyphen).

Is it rite? Can I go ahead in buliding the SC? or is there anything should come in that build variant dialogue box. Please advise.

Thanks!

Swarnaprakash

[Former Member]

Hi Swarnaprakash,

There is no harm done, when you press the build button.

If you did not add any variants yourself, you'll only have the "Default" variant.

The build will succeed when your code has no compilation errors AND all used DC's form other (standard SAP) SC's are imported in the workspace i.e. your track.

In the CBS you should see (besides your own SC) all othe SC's you SC is depending on. Make sure all "lights" are green for these SC's.

Hope this helps a litle more.

Regards,

Alain

[shreyas_pandya]

Dear Swarnaprakash,

Alan is absolutely correct.

if there is no build variant defined, then it will consider the default build variant.

When you trigger the SC build operation, it will build all the DCs present inside that SC.

If the build is successful, then it means that your development_buildspace will become consistent and must display the build status of all the DCs as green.

Regards,

Shreyas Pandya

[pramod_gopisetty1]

Hi,

Did you check the reply from Ervin, just go through his message it should solve the issue.

As mentioned by Ervin if the import is not executed then you will get the error.

First thing to make sure when working with NWDI is to have all the Dependents components are deployed properly. Then comes the build part.

To resolve that check if the request are hanging in TCS Deployer, if so Trigger deployment manually to make sure the Broken DC's are updated and deployed properly.

And at times the CBS service is stopped in Visual Admin, check that and start the service to process the requests.

To navigate to TCS Deployer go to link : http://<hostname>:<port number>/TCS/Deployer

Check for the Track and see if the requests are queued up, and then trigger the deployment manually.

This should solve the issue.

Cheers-

Pramod

Edited by: Pramod on Jan 25, 2011 10:37 AM

[shreyas_pandya]

Hi swarnaprakash,

Did you manage to resolve the issue?

Please share your findings.

Regards,

Shreyas Pandya

[Former Member]

Hi Shreyas & All,

When I expand by track which is in my NWDS , I am able to see the DCs which is under my proj SC. But when I expand the standard SCs( like SAP-JEE, SAP_BUIDT) none of the SCs is having their respective DCS. it happened for all the SCs. So I have asked my BASIS person to add the standard DCs to their respective SCs to the track. Hope my analysis is correct.

Please share your suggestions and please advise if anything or any steps I need to do on this.

Thanks!

Swarnaprakash

[shreyas_pandya]

Dear Swarnaprakash,

Your SC is missing the build time dependencies.

Kindly follow the below mentioned steps to resolve the issue...

1) Open the following URL to access NWDI web interface

www.http://<hostname>:<port number>/devinf

2) goto Change Management Services

3) Open System Landscape Directory

4) Click on Software Components

5) Here in the Filter give your Software Component name (WebDynpro)

6) after the serach is over select your SC in the table and the below displayed tabs goto Dependencies.

7) in the Context dropdown chose "BuildTime"

😎 click on "Define Prerequisite Software Component Versions"

7) In the Name column of the table search for the standard SC dependencies that you have mentioned in your previous reply (for e.g. SAP-JEE, SAP_BUILDT, SAP_JTECHS) and add then one by one as a dependencies.

😎 once you are done with this, go back to the 2nd step mentioned above.

9) Goto the Landscape Configurator link.

10) Chose your track inside the table on the left side.

11) goto the Domain Data option, Click on the "Change" button, and then click on "Update CMS" button (This may take some time)

12) once the CMS Update is finished, open the "Track Data" link that is beside "Domain Data"

13) Now click on the "Change" button, from the software component (SCs) table remove the WebDynpro SC, and add it back once again.

14) Save the Track Data.

15) Now goto Transport Studio, make sure your track is selected in the table

16) In the Check-In Tab select all the components displayed in the "Check-In" button.

17) Once the Check-In operation is completed all those component will now be queued up in the Development Tab,

18) In the Development Tab select all the components & click on "Import"

19) Once the Import operation is completed all those component will now be queued up in the Consolidation Tab,

20) In the Consolidation Tab select all the components & click on "Import"

21) Now come back to your NWDS and remove the configuration that you have imported previously and then again load the same configuration once again from the SLD.

This should resolve your problem...

Please revert in case the issue still persists.

Regards,

Shreyas Pandya

[shreyas_pandya]

Hi Swarnaprakash,

Did you manage to resolve the issue?

If yes, then please mark the thread as answered.

Regards,

Shreyas Pandya

[Former Member]

Hi Shreyas/Ervin,

Your suggestions are highly helpful to me. I rechecked all the standard SCs and imported into development. Previously all my dc were shown broken now it is showing 1 broken dc. I checked that DC, it is showing RED mark in compile state column.

Also, when I try to create my CAS project locally, i get the following error

Error when reading component definition from repository:Could not get component definition file from remote server. Not found : http://aaaaa:50200/dtr/ws/yyyyy/abc.com_yyyy_1_0/dev/inactive/DCs/abc.com/dc/yyyy_bapi_wrkcentre_des... (could not get folder item from DTR client for :/yyyyyy/abc.com_yyyy_1_0/dev/inactive/DCs/abc.com/dc/yyyy_bapi_wrkcentre_dest/dictionary/_comp/.dcdef)

i am able to log in to DTR and import the track. But it is showing like repository not accessible.

Please advise.

Thanks!

Swarnaprakash

[shreyas_pandya]

Hi Swarnaprakash,

.dcdef contains all the definition related to your DC.

If this file is missing that the DC cannot be loaded from DTR.

Please check in the DTR-server whether the .dcdef file of the DC that you are trying to modify is present under "_comp" folder or not?

If the .dcdef file is missing then you must check-in that file into DTR-client.

I would request you to mark the thread as answered, if all your doubts regarding broken DCs are clear,

you can open a new thread for different issues like the one you have posted in your last reply, as it will be easier to modularize the problem statements for more clarity and get the solutions faster.

Let me know about your findings.

Regards,

Shreyas Pandya

[ErvinSzolke]

Hi,

please have a look at the guide:

Understanding Broken DCs and Dirty DCs

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/30b7c94e-fc6b-2910-30b8-d34a7b51...

You can also refer to the NWDI TSG at:

http://wiki.sdn.sap.com/wiki/display/TechTSG/%28NWDI%29%28CBS%29Q0030

The error

validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED.

means usually that you haven't executed the Import on the Development (+Consolidation) tab of the Transport Studio in the CMS webui i.e. in other words the corresponding buildspace is not including yet the dependent SCs necessary for the build and so you run into broken DCs.

Best Regards,

Ervin