Few questions regarding SAP Dependencies when creating new SC

[Former Member]

Hello,

When creating new Software Component one must always add these dependencies:

SAP J2EE ENGINE <Release>

SAP BUILD TOOL <Release>

SAP JAVA TECH SERVICES <Release>

I have few questions regarding that:

1. In my system I have JDI BUILD TOOL instead of SAP BUILD TOOL and when I import it everything is working OK. Am I doing something wrong here and why can't I see SAP BUILD TOOL?

2. When I filter for SAP J2EE ENGINE and SAP JAVA TECH SERVICES I have two options: 6.40 and 7.00 but when I filter for JDI BUILD TOOL I only have 6.40. What does it mean and why don't I have JDI BUILD TOOL 7.00 as well? After all, I always upgraded the JDI as a whole.

3. When I choose these three objects do they must all be at the same version?

4. What happen when later SAP will upgrade these SCs? Will I need to go over each SC I have created and manually define the new dependencies for it?

Thank you in advance,

Roy

[Former Member]

In short:

6.40 = NW2004

7.00 = NW2004s

SAP BUILD TOOL = JDI BUILD TOOL, it just got renamed in NW2004s.

The versions of these SC's must correspond with the versions of your target runtime systems.

Note that in NW2004s there is also an EP_BUILDT, which you need to add a dependency for (and import it into the track(s)) if you want to perform Enterprise Portal developments.

You need to upgrade your development tracks if you intend to upgrade the connected runtime systems. If this involves an upgrade from NW2004 to NW2004s you must indeed change the Usage dependencies in the SLD. In this case I would actually recommend to define a new version of your own SC's (with dependencies to the 7.00 SC's) and develop these in new tracks.

Message was edited by: Pascal Willemsen

[Former Member]

Hello Pascal,

Thank you for the answer.

Could you please explain me how do I define a new version of my own SC's ? Does it created automatically when I create new track for this SC and complete the track's lifecycle?

Regards,

Roy

[Former Member]

No, it's the same procedure as creating a brand new SC with the only difference that you have to create a new SC in the SLD with the exact same name as the previous one, but with a different version number.

You should read <a href="/people/manohar.sreekanth/blog/2005/09/21/best-practicesjdi-branching-patterns-use-cases">this weblog by Manohar Sreekanth</a> for more info.