Creating Web Dynpro Project in JDI

[Former Member]

Hi,

I'm having difficulty creating a simple Web Dynpro project in a DC in JDI. I'm trying use Scenario 2+. When I try to build the DC containing the WDP project in the DC View, I get the following error:

Apr 25, 2005 6:15:48 PM /userOut/Development Component (com.sap.ide.eclipse.component.provider.listener.DevConfListener) [Thread[ModalContext,5,main]] ERROR: hello: Build failed for meridium.com/hello(meridium.com_APPLICATION_1) in variant "default": Used component not found: sap.com/tc/bi/bp/webDynpro

In the Web Dynpro perspective of the same project, the project cannot be built until I modify the .classpath file to modify the build path to include all of the jars reference in a WDP project.

How do I identify the components that are to be used for a Web Dynpro application? Is this done in the SLD? If so, which dependencies should I assign? Are there any step-by-step examples of creating a WDP application in JDI scenario 2+?

Thanks.

Rob

[Former Member · Accepted solution]

Hi Rob,

You can find a .dcdef file under your DC directory which write the information about your DC dependency.

In your webdynpro explorer, DC MetaData -> DC Definition -> Used DCs . you can define your used DCs here.

Hope that is helpful.

Best regards

Deyang

[Former Member · Accepted solution]

Thanks for your response.

I took a look at the .dcdef file and it looks like it defines the proper DCs for a WDP project (see below). The problem seems to be that the files defined in these dependencies can't be located. The build error says "Used component not found: sap.com/tc/bi/bp/webDynpro" which is defined in the .dcdef file below. How do I specify where to find the dependent files?

<?xml version="1.0" encoding="UTF-8"?>

<development-component

xmlns="http://xml.sap.com/2002/11/DevelopmentComponent"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xsi:schemaLocation="http://xml.sap.com/2002/11/DevelopmentComponent dcdef.xsd"

version="1.0.2"

xmlns:IDX="urn:sap.com:DevelopmentComponent:1.0">

<name>hello</name>

<vendor>meridium.com</vendor>

<caption>Hello </caption>

<component-type>

<vendor>sap.com</vendor>

<type>Web Dynpro</type>

</component-type>

<properties>

<ns0:localization xmlns:ns0="http://xml.sap.com/2003/06/Localization">

<ns0:domain>CA</ns0:domain>

<ns0:originalLocale>en</ns0:originalLocale>

</ns0:localization>

</properties>

<build-plugin>

<dc-ref>

<name>tc/bi/bp/webDynpro</name>

<vendor>sap.com</vendor>

</dc-ref>

<pp-ref>webDynpro</pp-ref>

</build-plugin>

<dependencies>

<dependency>

<dc-ref>

<name>tc/cmi</name>

<vendor>sap.com</vendor>

</dc-ref>

<pp-ref>default</pp-ref>

<at-build-time/>

</dependency>

<dependency>

<dc-ref>

<name>tc/ddic/ddicruntime</name>

<vendor>sap.com</vendor>

</dc-ref>

<pp-ref>default</pp-ref>

<at-build-time/>

</dependency>

<dependency>

<dc-ref>

<name>tc/ddic/metamodel/content</name>

<vendor>sap.com</vendor>

</dc-ref>

<pp-ref>default</pp-ref>

<at-build-time/>

</dependency>

<dependency>

<dc-ref>

<name>tc/wd/webdynpro</name>

<vendor>sap.com</vendor>

</dc-ref>

<pp-ref>default</pp-ref>

<at-build-time/>

</dependency>

<dependency>

<dc-ref>

<name>tc/logging</name>

<vendor>sap.com</vendor>

</dc-ref>

<pp-ref>default</pp-ref>

<at-build-time/>

</dependency>

<dependency>

<dc-ref>

<name>tc/wdp/metamodel/content</name>

<vendor>sap.com</vendor>

</dc-ref>

<pp-ref>default</pp-ref>

<at-build-time/>

</dependency>

<dependency>

<dc-ref>

<name>com.sap.aii.proxy.framework</name>

<vendor>sap.com</vendor>

</dc-ref>

<pp-ref>default</pp-ref>

<at-build-time/>

</dependency>

<dependency>

<dc-ref>

<name>com.sap.aii.util.misc</name>

<vendor>sap.com</vendor>

</dc-ref>

<pp-ref>default</pp-ref>

<at-build-time/>

</dependency>

<dependency>

<dc-ref>

<name>com.sap.exception</name>

<vendor>sap.com</vendor>

</dc-ref>

<pp-ref>default</pp-ref>

<at-build-time/>

</dependency>

<dependency>

<dc-ref>

<name>com.sap.mw.jco</name>

<vendor>sap.com</vendor>

</dc-ref>

<pp-ref>default</pp-ref>

<at-build-time/>

</dependency>

</dependencies>

<folders>

<source-folder>META-INF</source-folder>

<source-folder>src/mimes</source-folder>

<source-folder>src/configuration</source-folder>

<package-folder>src/packages</package-folder>

</folders>

</development-component>

-r

[Former Member · Accepted solution]

Hi Ericsson,

I don't know the scenario 2+ you said. But in our porject, we also got this problem. As I know, if you open your "Local DCs" view in the netweaver developer studio, you can find your JDI. and the DC "tc/bi/bp/webDynpro" should be find under "XX_SAP_BUILDT_1" node. you can compare it with your Local Development in the same view. If there is some DCs missing in the JDI server, maybe you should contace your JDI administrator

Regards

Deyang

[Former Member · Accepted solution]

Hi,

Just before you posted your reply, I figured it out the problem. The SCs required for the build were missing from the buildspace. At some point, I must have created a new buildspace and it did not have the SCs required by CBS (SAP-JEE, SAP_BUILDT and SAP_JTECHS). I made sure these were imported in Transport Studio and it all works now.

Thanks very much for your responses - they were helpful in tracking down the problem.

-r