NWDI Track defination for E-Commerce (crm)

[Former Member]

Hi ,

we need to set up newtrack for our e-commerce system in NWDI .In the document it says ..

1)

"Copy original Software Component from SAP-SHRAPP to CUSTCRMPRJ

• Change Context Root

• Exclude SAP-SHRAPP from deployment "

Q:What does it mean?

2) during the track defination we have added follwoing components :

CUSTCRMPRJ 5.0 sourceand archive

SAP-SHRAPP 5.0 source selected flag for excluded from deployment

SAP-SHRWEB 5.0 sorce& archive

Q:Should we set exclude from deployement falg for SAP-SHRWEB 5.0 also?

If I follow according to the document , its overwriting this component on development runtime system..

Could anybody explain me what is issue ?am i missing some configuration steps ?

or should we set flag exclude from deployment for all standard sap components ? is that recomended by sap ?

Thanks

Tagore

[Former Member]

you should be ableto fetch while adding SC'S .if you are not able get them , that means system does not find in its sld .You can update sld CIM models and check .

[Former Member]

Hi... how did u upload the CUSTCRMPRJ 5.0 package... where can i find this ???

[Former Member]

1)

"Copy original Software Component from SAP-SHRAPP to CUSTCRMPRJ

• Change Context Root

• Exclude SAP-SHRAPP from deployment "

- This is to create your DCs based on the CUSTCRMPRJ instead of the SAP-SHRAPP.

Following describes the reason for it;

In order to be able to compare the SAP standard web applications with the extended applications, it makes

sense to have two deployments. The first one is the one delivered by SAP, the second one contains project

specific extensions. This chapter describes how to set up such an application.

) during the track defination we have added follwoing components :

CUSTCRMPRJ 5.0 sourceand archive

SAP-SHRAPP 5.0 source selected flag for excluded from deployment

SAP-SHRWEB 5.0 sorce& archive

Q:Should we set exclude from deployement falg for SAP-SHRWEB 5.0 also?

A: No, this is where you would modify JSPs and other java components so it needs to be deployed after the enhancements, refer to pg. 141 ~ 142.