Error while building the DC and deploying it.

Question

Hi,
I have done all the while Post Installation Steps of Usage Type DI.
The SAP Link followed was :
http://help.sap.com/saphelp_nw2004s/helpdata/en/45/68d64260752a78e10000000a155106/frameset.htm
This is first time, I am configuring SAP NEWDI.
The server installed is: sap.com/SAP-JEECOR  7.01 SP4 (1000.7.01.4.0.20090417015900
which looks SAP NetWeaver 7.0 EHP1 SP4.
The DB installed is: DB2/NT64 (SQL09050)
The Java Virtual Machine details in the server is:
VM  system properties... 
Name:  Java HotSpot(TM) 64-Bit Server VM 
Vendor:  Sun Microsystems Inc. 
Version:  1.4.2_21-b03 
Now, I also installed SAP NWDS 7.01.04 which is SAP NWDS 7.0 EHP1 SP4, I think.
I did some mistakes while doing Post DI Steps.
The track and sc can be successfully imported to SAP NWDS
and I am able to build dcs on that sc.
Now, while doing the step build from Java WebDynpro perspective,
I am getting the build error.
I am pasting the errors.
Kind     Status     Priority     Description     Resource     In Folder     Location
Warning               [Warning]: Path in Classpath for file webdynproadmin.jar not found.     DJ1_DEV_Dhometestarpita~sap.com          
Warning               [Warning]: Path in Classpath for file webdynproclientserver.jar not found.     DJ1_DEV_Dhometestarpita~sap.com          
Warning               [Warning]: Path in Classpath for file webdynpromodel_dynamicrfc.jar not found.     DJ1_DEV_Dhometestarpita~sap.com          
Warning               [Warning]: Path in Classpath for file webdynpromodelimpl.jar not found.     DJ1_DEV_Dhometestarpita~sap.com          
Warning               [Warning]: Path in Classpath for file webdynproprogmodel.jar not found.     DJ1_DEV_Dhometestarpita~sap.com          
Warning               [Warning]: Path in Classpath for file webdynproruntime_designtime_coupling_api.jar not found.     DJ1_DEV_Dhometestarpita~sap.com          
Warning               [Warning]: Path in Classpath for file webdynproruntime_designtime_coupling.jar not found.     DJ1_DEV_Dhometestarpita~sap.com          
Warning               [Warning]: Path in Classpath for file webdynproruntime_repository_pmr.jar not found.     DJ1_DEV_Dhometestarpita~sap.com          
Warning               [Warning]: Path in Classpath for file webdynproruntime_repository.jar not found.     DJ1_DEV_Dhometestarpita~sap.com          
Warning               [Warning]: Path in Classpath for file webdynproservices.jar not found.     DJ1_DEV_Dhometestarpita~sap.com          
Warning               [Warning]: Path in Classpath for file SapDictionaryTypeServices.jar not found.     DJ1_DEV_Dhometestarpita~sap.com          
Warning               [Warning]: Path in Classpath for file SapDictionaryTypesRuntime.jar not found.     DJ1_DEV_Dhometestarpita~sap.com          
Warning               [Warning]: Path in Classpath for file SapMetamodelWebdynproContent.zip not found.     DJ1_DEV_Dhometestarpita~sap.com          
Warning               [Warning]: Version for file webdynproadmin.jar not found.     DJ1_DEV_Dhometestarpita~sap.com          
Warning               [Warning]: Version for file webdynproclientserver.jar not found.     DJ1_DEV_Dhometestarpita~sap.com          
Warning               [Warning]: Version for file webdynpromodel_dynamicrfc.jar not found.     DJ1_DEV_Dhometestarpita~sap.com          
Warning               [Warning]: Version for file webdynpromodelimpl.jar not found.     DJ1_DEV_Dhometestarpita~sap.com          
Warning               [Warning]: Version for file webdynproprogmodel.jar not found.     DJ1_DEV_Dhometestarpita~sap.com          
Warning               [Warning]: Version for file webdynproruntime_designtime_coupling_api.jar not found.     DJ1_DEV_Dhometestarpita~sap.com          
Warning               [Warning]: Version for file webdynproruntime_designtime_coupling.jar not found.     DJ1_DEV_Dhometestarpita~sap.com          
Warning               [Warning]: Version for file webdynproruntime_repository_pmr.jar not found.     DJ1_DEV_Dhometestarpita~sap.com          
Warning               [Warning]: Version for file webdynproruntime_repository.jar not found.     DJ1_DEV_Dhometestarpita~sap.com          
Warning               [Warning]: Version for file webdynproservices.jar not found.     DJ1_DEV_Dhometestarpita~sap.com          
Warning               [Warning]: Version for file SapDictionaryTypeServices.jar not found.     DJ1_DEV_Dhometestarpita~sap.com          
Warning               [Warning]: Version for file SapDictionaryTypesRuntime.jar not found.     DJ1_DEV_Dhometestarpita~sap.com          
Warning               [Warning]: Version for file SapMetamodelWebdynproContent.zip not found.     DJ1_DEV_Dhometestarpita~sap.com          
Error               com.sap cannot be resolved (or is not a valid type) for the field TestApplArpita.logger     TestApplArpita.java     DJ1_DEV_Dhometestarpita~sap.com/gen_wdp/packages/com/vmp/wdp     line 29
Error               com.sap cannot be resolved     TestApplArpita.java     DJ1_DEV_Dhometestarpita~sap.com/gen_wdp/packages/com/vmp/wdp     line 30
Error               com.sap cannot be resolved     TestApplArpita.java     DJ1_DEV_Dhometestarpita~sap.com/gen_wdp/packages/com/vmp/wdp     line 37
Error               com.sap cannot be resolved (or is not a valid type) for the field TestApplArpita.wdControllerAPI     TestApplArpita.java     DJ1_DEV_Dhometestarpita~sap.com/gen_wdp/packages/com/vmp/wdp     line 72
Error               com.sap cannot be resolved (or is not a valid type) for the field TestApplArpita.wdComponentAPI     TestApplArpita.java     DJ1_DEV_Dhometestarpita~sap.com/gen_wdp/packages/com/vmp/wdp     line 81
Error               wdControllerAPI cannot be resolved or is not a field     TestApplArpita.java     DJ1_DEV_Dhometestarpita~sap.com/gen_wdp/packages/com/vmp/wdp     line 87
Error               The method wdGetAPI() is undefined for the type IPrivateTestApplArpita     TestApplArpita.java     DJ1_DEV_Dhometestarpita~sap.com/gen_wdp/packages/com/vmp/wdp     line 87
Error               wdComponentAPI cannot be resolved or is not a field     TestApplArpita.java     DJ1_DEV_Dhometestarpita~sap.com/gen_wdp/packages/com/vmp/wdp     line 88
Error               The method wdGetAPI() is undefined for the type IPrivateTestApplArpita     TestApplArpita.java     DJ1_DEV_Dhometestarpita~sap.com/gen_wdp/packages/com/vmp/wdp     line 88
Error               Location cannot be resolved     InternalTestApplArpitaInterfaceView.java     DJ1_DEV_Dhometestarpita~sap.com/gen_wdp/packages/com/vmp/wdp/wdp     line 25
Error               com.sap cannot be resolved (or is not a valid type) for the field InternalTestApplArpitaInterfaceView.wdAlterEgo     InternalTestApplArpitaInterfaceView.java     DJ1_DEV_Dhometestarpita~sap.com/gen_wdp/packages/com/vmp/wdp/wdp     line 30
Error               IWDNode cannot be resolved (or is not a valid return type) for the method wdGetRootNode     InternalTestApplArpitaInterfaceView.java     DJ1_DEV_Dhometestarpita~sap.com/gen_wdp/packages/com/vmp/wdp/wdp     line 41
Error               IWDAction cannot be resolved (or is not a valid return type) for the method wdCreateAction     InternalTestApplArpitaInterfaceView.java     DJ1_DEV_Dhometestarpita~sap.com/gen_wdp/packages/com/vmp/wdp/wdp     line 51
Error               wdAlterEgo cannot be resolved     InternalTestApplArpitaInterfaceView.java     DJ1_DEV_Dhometestarpita~sap.com/gen_wdp/packages/com/vmp/wdp/wdp     line 52
Error               IWDAction cannot be resolved (or is not a valid return type) for the method wdCreateNamedAction     InternalTestApplArpitaInterfaceView.java     DJ1_DEV_Dhometestarpita~sap.com/gen_wdp/packages/com/vmp/wdp/wdp     line 61
Error               wdAlterEgo cannot be resolved     InternalTestApplArpitaInterfaceView.java     DJ1_DEV_Dhometestarpita~sap.com/gen_wdp/packages/com/vmp/wdp/wdp     line 62
Error               com.sap cannot be resolved (or is not a valid type) for the argument alterEgo of the method InternalTestApplArpitaInterfaceView     InternalTestApplArpitaInterfaceView.java     DJ1_DEV_Dhometestarpita~sap.com/gen_wdp/packages/com/vmp/wdp/wdp     line 70
Error               com.sap cannot be resolved (or is not a valid return type) for the method wdGetAPI     InternalTestApplArpitaInterfaceView.java     DJ1_DEV_Dhometestarpita~sap.com/gen_wdp/packages/com/vmp/wdp/wdp     line 78
Error               com.sap cannot be resolved     InternalTestApplArpitaInterfaceView.java     DJ1_DEV_Dhometestarpita~sap.com/gen_wdp/packages/com/vmp/wdp/wdp     line 79
Error               wdAlterEgo cannot be resolved     InternalTestApplArpitaInterfaceView.java     DJ1_DEV_Dhometestarpita~sap.com/gen_wdp/packages/com/vmp/wdp/wdp     line 79
Error               logger cannot be resolved     InternalTestApplArpitaInterfaceView.java     DJ1_DEV_Dhometestarpita~sap.com/gen_wdp/packages/com/vmp/wdp/wdp     line 86
Error               logger cannot be resolved     InternalTestApplArpitaInterfaceView.java     DJ1_DEV_Dhometestarpita~sap.com/gen_wdp/packages/com/vmp/wdp/wdp     line 87
Error               logger cannot be resolved     InternalTestApplArpitaInterfaceView.java     DJ1_DEV_Dhometestarpita~sap.com/gen_wdp/packages/com/vmp/wdp/wdp     line 94
Info               TextView DefaultTextView: UIElement does not have a label     TestApplArpitaView.wdview     DJ1_DEV_Dhometestarpita~sap.com/src/packages/com/vmp/wdp     
After that it is possible to successfully deploy the application after that,
but while running the application, I am getting runtime error.
500   Internal Server Error
SAP NetWeaver Application Server 7.00/Java AS 7.00 
Failed to process request. Please contact your system administrator.
Root Cause
The initial exception that caused the request to fail, was:
   com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to create delegate for com.vmp.appl.Test_dev_comp: no suitable constructor. (Hint: Does the generation version match the runtime version?)
    at com.sap.tc.webdynpro.progmodel.generation.ControllerHelper.createDelegate(ControllerHelper.java:103)
    at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.<init>(DelegatingComponent.java:51)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:382)
    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:756)
    ... 23 more   
Detailed Error Information
Detailed Exception Chain
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to create delegate for com.vmp.appl.Test_dev_comp: no suitable constructor. (Hint: Does the generation version match the runtime version?)
     at com.sap.tc.webdynpro.progmodel.generation.ControllerHelper.createDelegate(ControllerHelper.java:103)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.<init>(DelegatingComponent.java:51)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:382)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:756)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:291)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Now some points I need to tell about the NWDI:
In the , Post Installation Steps of Usage Type DI:
I need some points to be clarified in:
Preparing the System Landscape Directory.
1. Activate the SLD Server
While doing this step,
      1.      Open the SLD Web UI under the URL http://<server>:<port>/sld.
       2.      Open the initial page of the SLD Web UI and log on as an administrator.
       3.      On the initial page, choose Administration and in the section Server u00AE Profile.
The system displays the Parameters screen.
       4.      ChooseSection u00AEServer Settings.
       5.      Enter a reserved SAP NetWeaver namespace in the input field Object Server. Keep the preset working directory in the input field Working Directory. Select the values for persistency and write protection. Save your entries.
The object server name was localhost. I think this needed to be changed to the FQDN
of the server were the J2EE Engine is running say hclprd09.hcltech.com (or it would be the SID of the J2EE Server, that is DJ1).
The other values are now set to:
Persistence Type: Database
Working Directory: E:\usr\sap\DJ1\SYS\global\sld
Write Protection: None
Then the next step is:
Import the SAP Master Component Information.
  1.      On the SLD initial page, choose Administration and in the section Content u00AE Import.
       2.      Choose Import CR Content (this switch appears only before the content import has been executed once. By default, this is a step during installation).
The SLD server starts the import of the SAP Master Component Information. This process can take some time.
For this we have to use the file:
F:\usr\sap\DJ1\SYS\global\sld\model\CR_Content.zip
Is this step mandatory?
If I do the step will I have to recreate the users, roles, worksets and iviews again.
As some developments are already there.
So, importing the CR_Content.zip will overwrite or destroy all those roles, iviews etc.
Now, also in giving the name prefix for the development component for user kaba
has been given by me as sap.com.*
I think this is wrong as the DC is produced by my company and not by SAP.
Then I followed all other steps as written.
Give me your suggestions where I might be wrong.
Regards
Kaushik

Answer 1

Hi Neha,
Yes, till now; you are right.
The Product and sc has been created in
http://<host name>:<port>/devinf
The steps followed are written below:
1> Now Click on System Landscape Directory and create Product.
2> After entering Name, Vendor and Version for Product. Click on Create..
3> Product is created now it will ask for name of Software Unit.
4> Specify name and click on Create.
S/w Unit is created now it will ask inputs for S/w Components.
Provide all the necessary inputs for S/w Components and keep Production State as released.
Click on create.
Now select your Software Component and click on the Dependencies tab in the lower half of screen.
Select Build Time as Context and click on Define Prerequisite Software Components Versions
Now on next page search for three basic dependencies those are.
SAP J2EE ENGINE 7.00
DI BUILD TOOL 7.00
SAP JAVA TECH SERVICES 7.00
This is screen shot for SAP JAVA TECH SERVICES 7.00
Repeat the same process for the other two steps also search word will be *DI* for DI BUILD TOOL 7.0
*SAP J2e* for SAP JAVA TECH SERVICES 7.00
Domain Configuration and Track Creation
Now navigate to Landscape Configurator and click on Domain Data.
Enter all the required inputs in the screen below Click on Save and Update CMS.
Update CMS is very important step do not forget it.
Now click on Track Data and click on New.
Enter all the required inputs in the screen below
On the next page, search for your Software Component and click on ADD.
Click on Runtime Tab on the Top and Select System as per your requirement.
Enter the required Inputs and click on Save.
Now click on Transport Studio on top and select Check In now select all three Dependencies and click on Check In Button.
Now Click on Development Tab on top and Select All 3 Dependencies and Click on Import
Look at the status now it should say Import finished.
Your track is now created, configured & ready to use for development component in NWDS.
But mistake,
I should have added
SAP J2EE ENGINE 7.00
DI BUILD TOOL 7.00
SAP JAVA TECH SERVICES 7.00
Also, I removed prequisite software dependicies from SAP J2EE ENGINE.
Now what to do?
Do I need to import CIM Model Data?
Would it help?
Regards
Kaushik