
Once you have created a new portal application development component, you need to specify the dependencies to the relevant KM development components (to get access to the KM API DCs). You have to define dependencies to concrete development components (DCs) in one development configuration in order to use a source or artifact located in this DC. This situation is defined by the component model and allows you to establish better control over how the different parts of a development project are used.
Usually you do not need all the KM API DCs at the same time. Add only the DCs that your project depends on.
SAP NetWeaver Developer Studio is installed. The Development Infrastructure perspective has to be activated. If you have not yet activated this perspective, choose .
The DCs must reside in one and the same development configuration. You cannot declare dependency to DCs located in different development configurations.
To define a dependency between DCs that reside in different software components (SCs), the SC must have already established SC dependencies.
In the Development Infrastructure perspective, expand the development configuration's software SC in which the DC is located.
Open the DC in the Component Properties tab page and choose the Dependencies tab page.
Choose Add... .
In the development configuration, navigate to the tc/km/frwk DC to declare dependency.
Choose the checkbox of the tc/km/frwk DC to declare dependency . Choose Next .
Define the type of declared dependency to the selected DC. You choose the following types of dependencies:
Design Time
Dependencies between DCs can be used by special tools.
Run Time
This dependency specifies that a DC requires another DC at runtime. This means that it can be used meaningfully only if both DCs have deployable results.
Choose Finish .
SAP delivers the following API DCs for KM projects:
|
API DC |
Software Component |
Use |
|---|---|---|
|
tc/km/frwk |
KMC-CM |
Basic KM functions |
|
tc/km/nonwdui |
KMC-CM |
Non-Web Dynpro UI classes |