Defining Software Component Dependencies

To be able to develop Visual Composer models in a software component, you need to set a number of dependencies to other required software components. After you set the dependencies, you need to check in and import the required software components inside the track you are using for your development.

Prerequisites

The NWDI server administrator who is configuring the track has authorization to access the System Landscape Directory (SLD) and the Change Management Service (CMS).
A track for the Visual Composer model development has been created.

The SLD being used contains the following software components:

Software Component Name	Layer
ENGFACADE	Framework
EP_BUILDT	Framework
FRAMEWORK	Framework
SAP_BUILDT	Framework
VCBASE	Framework
VTP_BUILDT	Framework
WD-RUNTIME	Framework
BI-WDALV	Framework
CORE-TOOLS	Framework
BI_UDI	Framework
EP-BASIS-API	Framework
ESF	Framework
ENGINEAPI	Framework
VCFRAMEWORK	Framework
VCFREESTYLEKIT	Framework
WDEXTENSIONS	Framework

In addition to the software components listed in the previous table, the software components to be used for storing the Visual Composer models must have been defined in the SLD. More information: Creating and Removing Third-Party Software Components

Procedure

Define the software component dependencies listed in the following table. If these dependencies do not exist in the system, you can define them by editing the XML file of the software component (by clicking View/Edit XML in the Required Software Components table). The Dependency XML Content column of the following table shows the content to add to the XML file if needed.

More information: Defining and Removing Software Dependencies

Software Component	Software Component Name	Layer	Dependent On	Dependency XML Content
J2EE ENGINE FACADE	ENGFACADE	Framework	None
EP BUILD TOOL	EP_BUILDT	Framework	SAP_BUILDT	<dependencies> <used-compartment>sap.com_SAP_BUILDT_1</used-compartment> </dependencies> <build-variants> <build-variant name="default" required-for-activation="yes"> <variant-mappings> <variant-mapping used-compartment="sap.com_SAP_BUILDT_1" used-variant-name="default"/> </variant-mappings> </build-variant> </build-variants>
JAVA FRAMEWORK OFFLINE	FRAMEWORK	Framework	None
DI BUILD TOOL	SAP_BUILDT	Framework	None
VISUAL COMPOSER BASE	VCBASE	Framework	None
VISUAL_PATTERN BUILD TOOL	VTP_BUILDT	Framework	SAP_BUILDT EP_BUILDT	<dependencies> <used-compartment>sap.com_SAP_BUILDT_1</used-compartment> <used-compartment>sap.com_EP_BUILDT_1</used-compartment> </dependencies> <build-variants> <build-variant name="default" required-for-activation="yes"> <variant-mappings> <variant-mapping used-compartment="sap.com_SAP_BUILDT_1" used-variant-name="default"/> <variant-mapping used-compartment="sap.com_EP_BUILDT_1" used-variant-name="default"/> </variant-mappings> </build-variant> </build-variants>
WEB DYNPRO RUNTIME	WD-RUNTIME	Framework	None
BI WEBDYNPRO ALV	BI-WDALV	Framework	None
J2EE ENGINE CORE TOOLS	CORE-TOOLS	Framework	None
BI UNIVERSAL DATA INTEGRATION	BI_UDI	Framework	None
PORTAL BASIS API	EP-BASIS-API	Framework	None
ES FRAMEWORK	ESF	Framework	None
ENGINEAPI	ENGINEAPI	Framework	None
VISUAL COMPOSER FRAMEWORK	VCFRAMEWORK	Framework	None
VC FREESTYLE KIT	VCFREESTYLEKIT	Framework	None
WEB DYNPRO EXTENSIONS	WDEXTENSIONS	Framework	None

Check in the SCAs of the software components listed in the previous table and import them to the track.
More information:
- Checking In Software Component Archives
- Imports
Note
When new SAP NetWeaver patches are installed, you also need to reimport the SCAs to update the track used for Visual Composer development.

End of the note.