on 08-27-2007 7:06 PM
Hi Frndz...
Am learning DTR that how to work with it in NWDI this is very rget in my office..so that i found a PDF in SDN thas very fine but i hav some doubts...u can also c that PDF
in this PDF in the Requirements and Dependencies he mentioned some
· Defined Product and software components in the SLD
· Created a track for the Software component in CMS.
actually wht r s/w components and wht is track and how to create.
and also in the page no:7 DEVELOPMENT CONFIGURATION WIZARD..itz showing some application names ... how they exists ???...shall we need to configure those before..if that is the case kindly xplain how make that
this is vvvvvvvvvvvvvv urgent for me plz make this clear ASAP...
THANKS & REGARDS
K.Rajesh Kumar
Hi Rajesh,
Check the link below.
Perfect example to try.
Regards,
Rekha Malavathu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Rejesh
for creating track
http://help.sap.com/saphelp_nw70/helpdata/en/1e/086440bdd39a0ae10000000a155106/frameset.htm
Software component
Software components (SCs) combine development components (DCs) into larger units for delivery and deployment.
Every top-level component must be assigned to exactly one software component.
Child components always belong to the same software component as their parent.
The assignment of DCs to SCs is not static and may change over time.
SCs cannot be nested into each other.
Use
SCs do not control the visibility of their assigned development components.
Therefore, SCs are not considered to adhere to the black box principle like DCs.
SCs do not define public parts: all assigned components are automatically defined as public.
SCs can depend on each other and use each other, similarly to DCs.
Since SCs do not have development objects of their own, they define dependencies exclusively for the components assigned to them.
A DC can use another DC from a different SC only if its own SC defines an appropriate dependency.
DCs can restrict from being used by certain SCs by defining access control lists (ACLs).
SCs may thus be used to effectively implement software layers.
SCs have globally unique names, which are structured according to the rules for DC names. You must define the name when you create the software component; the name cannot be changed later. Names of software components usually consist of a vendor ID and only one segment, such as sap.com/crm.
Tracks define the transport route for the objects to be transported.
Hope it helps
Regards
Pratyush
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
81 | |
9 | |
9 | |
7 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.