SAP-ESS 6.03 Dependencies - SAP_PRT and EC_JSTARTUP?

[Former Member]

vwe are on NWDI 7.0 sp22, our runtime system for ESS application is on

EP 7.01 SP7. We are using SAP_ESS 6.03, We are trying to build track

for ESS webdynpro components. the default dependency components for

sap_ESS 6.03 is 7.0 version of SAP_BUILDT, SAPJTECHS, SPA_JEE and

EP_BUILDT. since our runtime system is on 7.01, we added 7.01 version

of the SAP_BUILDT, SAPJTECHS, SPA_JEE and EP_BUILDT to SAP_ESS 6.03 as

its dependencies. Once we done that, we got a pop up window which says

we need to check in another 16 components to build space (like BI_BASE_S, CAF_UM, WDEXTENSIONS, etc), two of them

we can not find: SAP_PRT and EC_JSTARTUP. Did anybody have this problem before? are we supposed to add 7.01 version of SAP_BUILDT, SAP_JEE, etc as dependency to SAP_ESS 6.03? Our understanding is that those version needs to match the runtime system version, is that correct? do we really need to add all those 16 components for ESS? where can we find SAP_PRT and EC_JSTARTUP.sca file?

Thanks,

Jane Zhou

[former_member214355 · Accepted solution]

Hello Jane

I investigated the SCs

EC-JSTARTUP

SAP_PRT.

They are only used SAP internally and appear in your track configuration

only because of transitive dependencies. They are not needed for your

development. Your build should work without them.

If the build fails and the build log explicitly asks for those SCs

you need to report back to me. Because this then indicates an error

with the SAP delivery.

Thanks

Kenny

[shreyas_pandya]

Dear jane zhou,

Are you facing the same problem with the default dependency components version 7.0?

Also, there's one way by which you can find out exactly which dependencies are required.

Please follow the below mentioned procedure...

Assuming that, you have imported the ESS track in your developer studio.

1) Go to the Development Infrastructure perspective of your studio.

2) Expand your ESS Track SC and click on the first DC and open the component properties.

3) Go to dependencies; here you'll see the list of decencies.

4) Now, one by one mouse over to each of these dependent DCs and find out under which SC it is present (basically note down the Containing SC)

5) Repeat the same procedure for all the other DCs and make a unique list of the containing SCs.

6) Now that you have the unique list of containing SCs, you can add the same SCs as the build time dependencies to your ESS Track SC.

Please revert with your findings.

Regards,

Shreyas Pandya