Problem Analysis: Deployed Web Dynpro Application Does Not Run 

With command list_app in the Telnet box, you can display the list of all currently deployed Web Dynpro applications. In addition to the name of the application, the list contains the status of the application. If the status of an application is STOPPED, you can start the application with command start_app <application name>. If this does not work, the reason might be that the Web Dynpro application defined runtime references which cannot be accessed from the Java Engine. You see that there is a reference that cannot be accessed if you cannot start the application. You can check this by entering the command add webdynpro followed by webdynpro getrefs <application name>. The list that is displayed shows all the references that were defined by the Web Dynpro application. This list also includes the status of the references. If the status of a reference is not OK, the application cannot be started.

●      Enter the activating command add deploy, next command lss (abbreviation stands for “list services”) which provides a list of all services that are currently deployed.

●      Command lsl (abbreviation stands for “list libraries”) provides a list of the deployed libraries.

●      Command lsi (abbreviation stands for “list interfaces”) provides a list of the deployed interfaces.

You can correct the problem either by changing the definition of the references in the application, or by deploying the missing referenced components to the Java Engine.