Cant see available tracks for adding a SC

[Former Member]

Dear all,

I would like to add another SC (KMC-BC) to one of the tracks of our customer. To be able to do that I navigated to CMS of the NWDI, but unfortunately Im not able to see any of 3 tracks configured by the customer and usable through NWDS.

To able to add an component to a track, I need to jump to the Transport Studio, marked on the screenshot. This is probably not possible, if no of the configured tracks are visible. Am I doing anything wrong? Thanks you in advance,

cheers

[former_member189220 · Accepted solution]

Hello Lawrence,

The tracks are configured and SCs are added to track in Landscape Configurator (not in Transport Studio).

What the screenshot displays is that there are no tracks configured on this CMS. Are you sure you have connected to the correct CMS?

In NWDS - Development Infrastructure, when you select the configuration track, usually a pop-up login appears. You might compare the URLs from there whith those on the screenshot.

Last but not least, if any changes in a development track are needed (adding, deleting SC), it is recommended to be done in SLD and after that the SC to be re-imported in CMS.

Regards

Milen

[Former Member · Accepted solution]

 The tracks are configured and SCs are added to track in Landscape Configurator (not in Transport Studio).

You mean this here?

What the screenshot displays is that there are no tracks configured on this CMS. Are you sure you have connected to the correct CMS?

I guess it should be right, since we are able to see available DTR stuff, activities etc.

In NWDS - Development Infrastructure, when you select the configuration track, usually a pop-up login appears. You might compare the URLs from there whith those on the screenshot.

You are right, the URL appears in the logon popup in the NWDS. In case of our customer there are 2 URL's, means 2 machines are involved. Milen, are there any how-to's or SAP documentation on this task? We didnt tryed this on our own till now, and have found only:

http://santy.wdfiles.com/local--files/web-dynpro/NWDI_Getting_Started.pdf

This seems to be wrong? Thank you for your help

cheers

[junwu · Accepted solution]

1. go to sld to add the dependency for your sc

2. landscape configurator to sync the content from sld

it is very strange your system is not showing any track........

[Former Member · Accepted solution]

Jun Wu wrote:

1. go to sld to add the dependency for your sc
2. landscape configurator to sync the content from sld

it is very strange your system is not showing any track........

Unfortunately I have no idea how to do it, never tryed this on my own before, but since the NWDI admin is on holidays.... If I jump to sld I see this:

Do you know how to proceed here to add a SC to one of the tracks? Or is there any documentation on this? Thanks,

cheers

[former_member189220 · Accepted solution]

Hello Lawrence,

When you are in SLD you have to select Software Components.

After that filer to the name of SC where you would like to add the dependency.

You might refer to point 4.3 of this guide for some directions:

http://scn.sap.com/docs/DOC-16207

Regards,

Milen

[Former Member · Accepted solution]

Guys, thank you very much for your friendly support. Indeed, I have some Problems with this approach:

1.)even if I try to add the dependency like showed in the document. First of all I need to define a dependency for a custom DC, not for a SC. I have find the right SC, but I cant see or choose any DC or maintain its dependencies. Nevertheless, even if I try to do it the button "Define Prerequisite Software Component Versions" is grayed off, I cant click on it. Im also not able to find an "Edit" Mode button or anything similar to enable it

2.)But lets assume it works and I can maintain the dependencies on that way. This is in fact not my goal. The BASIS admin who maintain the NWDI for my customer was able to provide the DC directly in the track list of NWDS, like:

So the developers dont need the Web UI of the SLD, rather they should be able to define the dependencies for single DC's directly in the NWDS using Dev Infrastructure perspective:

Can I manage this somehow?`

Thanks,

cheers

[former_member189220 · Accepted solution]

Hello Lawrence,

The scenario which Jun & me was relating is if you use CMS.

However, from your screenshots, it seems to me you use CM Services. This is because the name of the track in the NWDS is without "_dev" or "_con" (just "TPZ").

In such scenario you have to refer to this guides:
How To... Configure CM Services in SAP NetWeaver 7.3 and Up
https://scn.sap.com/docs/DOC-51948

Adding SC dependencies is explained in chapter
7.1.2 Configuring the Development Configuration

DCs are created in NWDS. This process is not related to whether you use CMS or CM Services.
About how to create Development Component please refer to
Creating a Development Component (DC)
https://help.sap.com/saphelp_nwce72/helpdata/en/49/0850a9716a40a8e10000000a421937/content.htm

DC could be referenced (define a dependency) only to other DC. This is done in NWDS as you have pointed already.

SC could be referenced only to SC. This is done in NWDI.

It is not possible to define a dependency of a DC directly to other SC only. You have to select a DC (part of the SC) to which your DC you want to depend.

In your screenshot you have to select 1st the SC and after that the DC to which to define a dependency.

----------------------------------------------------------------

For exaple if you have to define a dependecy

of the DC supapps/navtable

to

SC ENGFACADE - you select ENGFACADE and from the tree you select DC to which you create dependecy. In the end there will be created a dependency between

SCs: PORTAL-APPS <> ENGFACADE (this on SC level)

DCs: between supapps/navtable and the other DC.

Of course when you define the DC dependency in NWDS, later you will have to make sure you have SC dependency define in CM Services as well.

Regards

Milen

[Former Member · Accepted solution]

Hi Milen,

In such scenario you have to refer to this guides:
How To... Configure CM Services in SAP NetWeaver 7.3 and Up
https://scn.sap.com/docs/DOC-51948
Adding SC dependencies is explained in chapter 
7.1.2 Configuring the Development Configuration

Thanks, I didnt saw this document, but saw this possibility while my investigations and tryed it already, it doesnt work. I have added KMC-BC on this manner:

However, this doesnt help. Admittedly Im able to see it afterwards on the track, but it doesnt contain any DC's and accordingly it doesnt make sense to reference to it, since it want help on build errrors for appropriate classes. This look rather to me, like its supposed to create custom SC's instead binding SAP Standard stuff:

What I need is a "blue" SC including all DC's like other SAP standard stuff, KMC-WPC e.g.

Did I misunderstood anything?

 DCs are created in NWDS. This process is not related to whether you use CMS or CM Services. 
About how to create Development Component please refer to 
Creating a Development Component (DC)
https://help.sap.com/saphelp_nwce72/helpdata/en/49/0850a9716a40a8e10000000a421937/content.htm


DC could be referenced (define a dependency) only to other DC. This is done in NWDS as you have pointed already.
SC could be referenced only to SC. This is done in NWDI.
It is not possible to define a dependency of a DC directly to other SC only. You have to select a DC (part of the SC) to which your DC you want to depend.

In your screenshot you have to select 1st the SC and after that the DC to which to define a dependency.
----------------------------------------------------------------
For exaple if you have to define a dependecy
of the DC supapps/navtable
to
SC ENGFACADE - you select ENGFACADE and from the tree you select DC to which you create dependecy. In the end there will be created a dependency between
SCs: PORTAL-APPS <> ENGFACADE (this on SC level)
DCs: between supapps/navtable and the other DC.

Of course when you define the DC dependency in NWDS, later you will have to make sure you have SC dependency define in CM Services as well.


Regards
Milen

All this works well for us, particularly referencing to SAP standard DC's, thank you for clarification.

cheers

[Former Member · Accepted solution]

Could it be I need to do an import of KMC-BC, like mentioned in the 7.1.3 of the document you have pointed me to? Thanks,

cheers

[former_member189220 · Accepted solution]

Hi Lawrence,

How have you configured KMC-BC to be part of your track.

KMC-BC is property of SAP and is not provided with sources. However most probably you have configured it as 'To Be Developed'.

Would you please refer to the solution in this tread

http://scn.sap.com/thread/3735239

Please let me know how you have configured KMC-BC in the track. Please provide screenshots about the track configuration in CM Services.

Regards

Milen

[Former Member · Accepted solution]

How have you configured KMC-BC to be part of your track.

Like mentioned in the document you have pointed me to... I clicked to "edit" -> "add sc", searched for KMC-BC and was able to see the stuff I showed on the first picture I showed in my last post... Have I missed something?`

KMC-BC is property of SAP and is not provided with sources.

We are clear about that, I also saw included classes are not documented, probably of this reason. But a colleague of my needs several classes out of this SC resp included DC's, so we cant avoid the use of KMC-BC

.
However most probably you have configured it as 'To Be Developed'.
Would you please refer to the solution in this tread
http://scn.sap.com/thread/3735239

I have done so already while taking the SC in, it doesnt solve the problem of missing dependencies:

Please provide screenshots about the track configuration in CM Services.

This looks quite ok for me:

Thanks,

cheers

[former_member189220 · Accepted solution]

Hi Lawrence,

I would like to elaborate...

1.

... But a colleague of my needs several classes out of this SC resp included DC's, so we cant avoid the use of KMC-BC ...

When the SCA is delivered without SOURCE archives you might not make changes in the DCs. This is the case with KMC-BC. Only libraries (build archives) are delivered.

You might easily check this. (please copy KMC-BC SCA and change the .sca to .zip. After that you might "explore" what the SCA contains as archives. You will not see SOURCE archives.) This means that when you declare this KMC-BC as 'To Be Developed' it will be imported in the NWDS with 'yellow' and of course there will be nothing because there are no source files (only deployed archives and/or compiled, build libraries).

So if you need particular DCs form KMC-BC, then you will not be able to have them. SAP just does not provide them (due to is not open-sourced SC). I am affraid you will have to define KMC-BC in order to use its functionality.

2.

I have done so already while taking the SC in, it doesnt solve the problem of missing dependencies:

When a SCA is delivered without SOURCE archives you might not make changes in the DCs.

Firstly, a dependency between KMC-BC and other SC has to be defined in SLD. This is not different from what has been explained before.

You need to open SLD > browse to the Software Component > select tab Dependecies > in Context: Build Time > press button "Define Prerequisite Software Component Versions" > define correct KMC-BC version. All this is in SLD. The guide about CM Services does not include this because it assumes all the configuration of the dependencies is done already in SLD.

Now comes the part of the CM Services. When the SC has dependency to KMC-BC then please go the CM Services > select Development Configuration > select tab Software Component Definition > press Check SCs. This will trigger update of the defined SC dependencies for this SC between SLD <> CM Services. It has to be seen something similar to

This is due to SCs which have been 'newly' defined in SLD are not in the "older" version of the SC dependencies in CM Services. So you will have to go through this steps in order to be able to use the KMC-BC functionalies.

Once the configuration is done in SLD & CM Services, only then, you might import again the track in the NWDS. KMC-BC should be there and should be 'blue'.

If you need some more clarifications & directions, please let me know.

Regards

Milen

[junwu · Accepted solution]

1.to be developed should not be ticked.

2.sc should be imported

[Former Member · Accepted solution]

Firstly, a dependency between KMC-BC and other SC has to be defined in SLD. This is not different from what has been explained before.

Thank you guys, this was the crucial hint for me: we were missing such a definition in SLD.

From my point of view, we would never have figure this out on our own: the "wrong" order - creating a dependency first, and definition resp import of used DC afterwards doesnt makes sense (for european kind of logic ). However, I got the principle now and this worked well our, thank you for your patient support.

Milen, you are right, besides of my actually question this one (KMC-BC) doesnt contain any public parts, so adding that one doesnt solve build problems, but at least checks SC depndencies on deploy time.

cheers

[former_member189220 · Accepted solution]

Hi Lawrence,

I'm glad to hear my input has come handy.

CM Services are designed like this. Whether it is good or not - will not discuss. However I would like to try explaining why it is designed like this.

You have to have the SC dependencies defined in SLD and then you "check" whether the data in CM Services is the same. I think it does make sense because the one of the goals about System Landscape Directory (SLD) is to be a kind of catalog of all the versions of the SC available. A "source point" from where you might get the correct versions & structure of SC (developed or not). Here you define your development product. Also you might define different versions for the very same product.

This is why I alway recommend to keep (up-to-date) the data in SLD correct. (especially for SC dependencies).

CMS & CM Services are more about the transportation process itself (where to transport - between DEV-TEST-PROD; or/& what exactly to transport - for the SCs,SDAs,Activities as CM Services allows). Although, it is possible to change the track data in CMS, I do not recommend. This option has designed for very special cases and in most of the time - it is not related. However many people try change the track data in CMS (not in SLD) and of course this leads to some problems. In CM Services this is NOT possible as you have observed. I mean when you add new SC dependency directly to a specific SC, the SC (you want to become dependent) does NOT become a dependent of the other but it is dependent to the track itself. Of course this leads to error (because the SC is marked as "To be Developed", the CM Services accept it as a development SC and expects to find source files in the SC - where there are none due to it is delivered without sources):

"Error: The file ENGINEAPI08_0-10007921.SCA cannot be imported, because it does not fit to
the target configuration. Either the file does not contain any sources or archives or the configuration does not contain the software component."

This is why you have to add this dependency in SLD and then re-check (update) the track information in CM Services.

All in all, I would like to say - SLD is where the definition of the dependencies has to be done. CMS & CM Services are about the transport matter.

Due to this thread was risen against "Cant see available tracks for adding a SC" please mark some of the answers (the one who provide you a solution for this question) as "Correct". In this way the tread will become "Answered". (This is a little bit technical but for the moderator - important)

If you face build problems, as you've mentioned, please open an additional thread by quoting the build log and adding some screenshots. I would be glad to help you with what I can.

Regards

Milen

[Former Member · Accepted solution]

Thanks Milen, this clarifies some things. The reason we found it to be build weird is as following: if I would be a NWDI admin, I wouldnt wait till people would ask me for additional SC's, but import all the available stuff instead directly while initial configuration of the tracks. Due your explanation you cant do this, unless you have defined a custom SC and appropriate dependencies. I guess its clear what I want to tell beyond, it saves unnecessary admin effort etc.

Due to this thread was risen against "Cant see available tracks for adding a SC" please mark some of the answers (the one who provide you a solution for this question) as "Correct". In this way the tread will become "Answered". (This is a little bit technical but for the moderator - important)

this is already the case as far I can see

If you face build problems, as you've mentioned, please open an additional thread by quoting the build log and adding some screenshots. I would be glad to help you with what I can

Thanks, but this should be quite clear: we need to copy appropriate JAR's to our custom lib dc's to make the "hidden" SAP stuff available. We are familiar with such problems e.g. for using PCD content, service classes etc which are neither documented nor offering public parts, but are compelling needed for development. This approach has worked well for us, thanks

cheers

[former_member189220 · Accepted solution]

Hi Lawrance,

Thank you for having assisted in the administration of this thread. Now when this is in the history, let me put some other stuff on board. (I hope it might be useful)

The development configuration (or development track) concept has been created with the purpose to "to define the developer’s view to the development infrastructure". In other words to determine (or constraint) what the developer might (or might not) use as SCs. The process it self consists of...

1. First a product is defined in the System Landscape Directory (SLD). This product consists of
software components (SCs). The dependencies between different SCs need to be defined as well.
„2. Then, tracks are created. A track consists of logical development systems for a specific release of
specific software components. In addition, required SCs are imported into the track.
„3. The developer starts the work by importing the correct development configuration. With this step,
the configuration of the local development environment is finished.

This concept is useful from the point of view that it will save resources (of the AS Java) in the import, build and deploy phases during the transport process. You might imagine what would have been if you had to transport only few SCs and on the other hand - all available SCs.

I agree with you - this puts extra tasks on your already overpilled working desk. (I might sincerely relate to that). However I would like to point out, there is still a "silver lining". You might create in advance specific products with SC dependencies in SLD for any kind of development (f.a. different configurations for BPM, CAF, VC, WebDypro or EP). Once you have done so you might re-use it in the future or slightly make the necessary changes. (if you have access to SAP notes I might provide you some for further use)

Other approach is to create one configuration with all SC dependencies defined. Then when needed just copy it and delete what is not necessary for the development. (I'm not sure how much will spare this to you)

All these actions are in SLD. After that (as I mentioned) you just have to import them in CM Services or CMS. Do not forget that you have the option to create different versions of the very same project (which somehow gives a kind of flexibility).

I hope this info might save you some other minute (and problem as well).

Regards

Milen

[Former Member · Accepted solution]

Thank you very much Milen, quite usefull information and a great roadmap. I like the placeholder-dummy approach:

Other approach is to create one configuration with all SC dependencies defined. Then when needed just copy it and delete what is not necessary for the development. (I'm not sure how much will spare this to you)

and will propagate this one

cheers

[former_member189220 · Accepted solution]

... just do not forget to do all this in SLD. The configuration between SLD and CMS/CM Services has to be the same.

Regards

Milen

[Former Member · Accepted solution]

Milen Dontcheff wrote:

... just do not forget to do all this in SLD. The configuration between SLD and CMS/CM Services has to be the same.

Regards
Milen

Thank you, this worked well as soon I knew I need to do the SLD stuff first. But Im a bit confused by one thing: with your friendly support we have imported KMC-BC. Since you mentioned it doesnt have any public parts, my expectation was to see a "blue" SC with nothing included. But:

I didnt try to reference some of them, but it seems it would work. Why Im able to see all the stuff, this shouldnt be the case? I probably missed something...

cheers

[former_member189220 · Accepted solution]

Hi Lawrence,

I wrote:

"When the SCA is delivered without SOURCE archives you might not make changes in the DCs. This is the case with KMC-BC. Only libraries (build archives) are delivered."

You do not have an access to the source of the development component (the code itself). However you do have access to the public part (which are classes - builded archive/executalbe code).

Otherwise you may not use the functionalities of the DCs (and ultimately - SCs).

Regards

Milen