System Alias in Web Dynpro ?

Hello All,
I have a requirement such that in my Web Dynpro application, I need to figure out that the backend R/3 it is trying to connect to, is it a unicode or a non unicode system.
For this purpose, we maintain an additional alias name for the portal system starting with UNI_ if its a unicode box or NONUNI_ if its a non-unicode box.
Is there any other better way of storing this information.
<b>I need to know, how can we fetch all the alias names maintained for a sytem in portal using Web Dynpro APIs.</b>
Please help.
Thanks in advance,
Samta

Hi,
import com.sap.portal.pcm.system.ISystem;
import com.sap.portal.pcm.system.ISystems;
import com.sap.security.api.umap.system.DummySystemLandscapeWrapperImpl;
import com.sap.tc.webdynpro.clientserver.portal.impl.PortalUtils;
DummySystemLandscapeWrapperImpl sysLandscapeImpl = null;
PortalUtils portalUtils = null;
ISystems sys = null;
ISystem system = null;
String[] allSystems;
Enumeration allAliases = null;
String systemName = null;
String systemAlias = null;
portalUtils = new PortalUtils();
sys = (ISystems)portalUtils.getServiceReference(ISystems.KEY);
allSystems = sys.getAliases();
for (i = 0; i < allSystems.length; i++)
sysLandscapeImpl = new DummySystemLandscapeWrapperImpl
(allSystems<i>.toString());
allAliases = sysLandscapeImpl.getAllAliases();
while (allAliases.hasMoreElements())
systemAlias = allAliases.nextElement().toString();
Regards
Ayyapparaj

Similar Messages

  • How to call legacy system screen in web dynpro for java?

    Now I'm using Netweaver CE for building BPM (Business Process Management).
    In BPM system, I wana call legacy system screen(ERP, C/S , Web, etc..) in web dynpro.
    I'v already known how to call legacy system method and data.( using RMI, SOAP and RFC )
    But I don't konw how to call legacy system screen.
    If there is no way calling legacy system screen, I will have to build every screen using web dynpro.
    It's so terrible.
    So I think there is a way calling legacy system screen.
    It's just my opinion.
    If It can call legacy system screen in web dynpro, please let me know how to call it.
    Or, If there is no way calling legacy system, how solve I this problem?
    Thank you reading my question.

    I assume that with "legacy system screen" you mean ABAP Dynp sceens. Of cause it would be attractive to integrate into new BPM processes. However there is a conceptional issue: You could easily integrate them e.g. into a WebDypro using a URL to to the so-called WebGUI (the ITS that makes Dynp screens Web enabled).
    However the Dynp screen store all there state in the ABAP backend. This information is not available to to the process engine, e.g. to set the Task to completed or to use the data in Output Mapping.
    In fact you need a way to wrap the how UI transaction into a WebDynpro screen including data flow.

  • Access portal system details in Web Dynpro ???

    Hello All,
    I have a requirement such that in my Web Dynpro application, I need to figure out that the backend R/3 it is trying to connect to, is it a unicode or a non unicode system.
    For this purpose, we maintain an additional alias name for the portal system starting with UNI_ if its a unicode box or NONUNI_ if its a non-unicode box.
    Is there any other better way of storing this information.
    <b>I need to know, how can we fetch all the alias names maintained for a sytem in portal using Web Dynpro APIs.</b>
    Please help.
    Thanks in advance,
    Samta

    Hi,
    please take a look at the <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/developerareas/webdynpro?rid=/library/uuid/49f2ea90-0201-0010-ce8e-de18b94aee2d">tutorial section</a> here at SDN. This is a good starting point to learn WebDynpro.
    Regards
    Sebastian

  • How configurate a SAP System Registry in Web Dynpro ?

    Hi everybody,
    When i deploy a web dynpro application,
    i obtain the following error:
    "No default system is configured in SAP System Registry"
    In menu Window->Preferences->SAP AS Java,
    i need to register SAP instance.
    However, i don't know how to retrieve the following information of my SAP system:
    - Instance Host ?
    - Instance Number ?
    Need your help!
    Thanks
    Rodolphe

    localhost
    0

  • Connecting to R/3 System through Java Web Dynpro forms.

    Hi,
    I have a requirement in which I have to send data to R/3
    from Java Web Dynpro screens.
    I will design the Java Web Dynpro screens and write a RFC Model.
    I will write a RFC in se37 which will connect to the RFC Model.
    Before creating the RFC in se37, I will create ztables in se11.
    I will write a ABAP Report to see that all data enters the ztables.
    I need some guidance with regard to this.
    Do, the RFC Model have the access of the ECC(R/3) System.
    What are tasks to be told the Basis guy so, that RFC being called from through Java Web Dynpro?
    Please provide me some documents with regards to this scenario.
    Regards
    Neha Singh

    Hi Neha,
    The steps you provided is clear enough to connect to a R/3 system through the WD forms.
    On creating the model you need to give two inputs such as
    logical system name for model instance
    logical system name for RFC metadata
    there will be 2 default values, also you can create your own JCOs in the <servername>:<port>/devinf of the server or u can ask your basis team also.
    Before creating the JCO , the SLD (System Landscape Directory) needs to be configures, that your basis team will know.
    other than that once you create the functional module in se37 make it RFC enabled , and once you import the RFC model , you can give your ECC system user name and password and search for RFC you have created from the list of RFC.
    Regards,
    Sam Charles J.

  • System Requirement for Web-Dynpro Appraisal Application on ESS

    Hi Gurus...
    Greetings
    Our client have SAP Netweaver 7.0 without any Enhancement Pack.
    They are already using standard Web-Dynpro application of Leave Management System on ESS.
    Now, they want to use standard Web-Dynpro screens for Appraisal system on ESS.
    My Query is:  What is the minimum system requirement for using standard Web-Dynpro screens for Appraisal system on ESS ???
    I think minimum enhancement pack used for the same requirement is  EHP2.  Kindly correct me if  I am wrong.
    One more query:  From where we can see the latest Enhancement Pack applied on System  ???
    Please reply to my Queries.
    Thanks & Regards,
    PKG.....

    Hi,
    Greetings....
    How can we have our system upgraded from ECC 600 to ECC 604 (EHP4) ???
    Is it a patch level activity or upgraded activity ??
    How to achieve this, would it be having any side-effects on current system ??
    Thanks & Regards,

  • Can't connect to a SAP backend system via portal/web dynpro/JCo destination

    Scenario:
         Can't successfully set the JCo destination.. Always got a Java exception..
    Solution:
         Use the router string "/H/sapserv3/S/3296/H/", instead of
    "/H/sapserv3.wdf.sap.corp/S/3296/H/".
         This looks like a bug in portal NW2004s SP9.

    Sorry for the delay, but I was not able to get access to this system until this afternoon.  I ran the ARP command you suggested on the server, and it did return the correct IP and MAC address values for the problem workstation.
    I then ran IPCONFIG/displaydns on the server.  There was a record there for the problem workstation.  The "record name" matched the machine name correctly.  However, the "A <Host> Record" value was for the wrong IP address (192.168.1.4
    rather than the actual workstation IP of 192.168.1.7).  This could certainly explain why I am not able to RWA/RDP to the machine by name, although I can make an internal RDP connection via IP address.
    Could you please tell me what I need to do to repair this problem?  Should I run IPCONFIG/flushdns on the server?
    Thanks again for your assistance.
    John

  • Conversion from SAP R/3 system to web dynpro abap.

    hi,
        Can anybody provide me with information on what all objects can be converted from an SAP R/3 system to a web dynpro ABAP application, nd hw??.

    Hi Girish,
    I don't understand your question completely. Is your question related to the Internet Transaction Server? If it is a Web Dynpro question, I can move this thread to the Web Dynpro forum. What do you think?
    - Henning

  • How to create remote SAP j2ee web dynpro system

    I have a J2EE web dynpro on another J2EE instance than the portal.  I want to take advantage of logon tickets from Portal J2EE to this other system.   But creating the system connection in the portal, I'm not sure what system type to select.  If I choose to create an IView for J2EE Web Dynpro, it seems to assume that the app is on the portal instance.
    I could just do a straight URL type IView, but then I don't think that I could make logon tickets work with that.

    Thank you, that was helpful.
    I followed the instructions to create a system and then web dynpro iview, putting in the relevant parameters.
    Our remote webdynpro iview URL is:
    http://<host>/webdynpro/dispatcher/sap.com/<namespace>/<app>?SAPtestId=83
    SO, in the iview entry, i gave values:
    namespace: sap.com/<namespace>
    app: <app>
    parameters: SAPTestId=83
    When I preview it, I get a J2EE exception:
    Caused by: javax.naming.NoInitialContextException: Cannot instantiate class: com.sapportals.portal.prt.registry.PortalRegistryFactory [Root exception is java.lang.ClassNotFoundException: com.sapportals.portal.prt.registry.PortalRegistryFactory
    Found in negative cache

  • Web Dynpro without Java stack?

    Hello
    a simple question : Is is possible to deveop and run Web Dynpro applications on a system with no Java stack? It is a ECC 6.0 system.
    Thanks
    A.

    Hi Aleksandra, 
    Yes it is posible to develop and run Web Dynpro applications without Java Stack.
    For Web Dynpro for ABAP :- Java stack not required, you can do with SAP System T-Code - SE80 if Web Dynpro Component available in your sap system.
    For Web Dynpro for Java :- You must require Java Stack.
    Hope this will helps you.
    Thanks
    Arun Jaiswal

  • Error in opening sap web dynpro iview

    hi all,
    i am trying to open sap webdynpro iview in portal but getting the following error...
    500   Internal Server Error
      Web Dynpro Container/SAP J2EE Engine/6.40 
    Failed to process request. Please contact your system administrator.
    [Hide]
    Error Summary
    While processing the current request, an exception occured which could not be handled by the application or the framework.
    If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
    Root Cause
    The initial exception that caused the request to fail, was:
       java.lang.ClassNotFoundException: com.lti.wdp.InternalCSLs Found in negative cache -
    Loader Info -
    ClassLoader name: [local/SLAReporting_KM] Parent loader name: [Frame ClassLoader] References: common:service:http;service:servlet_jsp service:ejb common:service:iiop;service:naming;service:p4;service:ts service:jmsconnector library:jsse library:servlet common:library:IAIKSecurity;library:activation;library:mail;library:tcsecssl library:ejb20 library:j2eeca library:jms library:opensql common:library:com.sap.security.api.sda;library:com.sap.security.core.sda;library:security.class;library:webservices_lib;service:adminadapter;service:basicadmin;service:com.sap.security.core.ume.service;service:configuration;service:connector;service:dbpool;service:deploy;service:jmx;service:jmx_notification;service:keystore;service:security;service:userstore interface:resourcecontext_api interface:webservices interface:cross interface:ejbserialization sap.com/com.sap.km.application sap.com/tcwddispwda sap.com/tcwdcorecomp service:webdynpro service:sld library:tcddicddicservices library:com.sap.aii.proxy.framework library:tcgraphicsigs library:com.sap.mw.jco library:com.sap.lcr.api.cimclient library:sapxmltoolkit library:com.sap.aii.util.rb library:com.sap.util.monitor.jarm library:tcddicddicruntime library:com.sap.aii.util.xml library:tccolapi library:com.sap.aii.util.misc library:tccmi library:tccol~runtime Resources: D:\usr\sap\CX5\DVEBMGS00\j2ee\cluster\server0\apps\local\SLAReporting_KM\webdynpro\public\lib\app.jar Loading model: {parent,references,local} -
        at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:348)
        at com.sap.tc.webdynpro.progmodel.generation.ControllerHelper.createDelegate(ControllerHelper.java:65)
        at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.<init>(DelegatingView.java:41)
        at com.sap.tc.webdynpro.progmodel.view.ViewManager.createUninitializedView(ViewManager.java:638)
        at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:675)
        ... 49 more
    See full exception chain for details.
    System Environment
    Client
    Web Dynpro Client Type HTML Client
    User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 2.0.50727)
    Version null
    DOM version null
    Client Type msie6
    Client Type Profile ie6
    ActiveX enabled
    Cookies enabled
    Frames enabled
    Java Applets enabled
    JavaScript enabled
    Tables enabled
    VB Script enabled
    Server
    Web Dynpro Runtime Vendor: SAP, build ID: 7.0007.20060509173555.0000 (release=NW04S_07_REL, buildtime=2006-05-09:16:21:23[UTC], changelist=13857, host=pwdfm114), build date: Thu May 18 17:33:32 GMT+05:30 2006
    J2EE Engine 7.00 patchlevel
    Java VM Java HotSpot(TM) Server VM, version:1.4.2_09-b05, vendor: Sun Microsystems Inc.
    Operating system Windows 2003, version: 5.2, architecture: x86
    Session & Other
    Session Locale en
    Time of Failure Wed Jul 12 09:17:18 GMT+05:30 2006 (Java Time: 1152676038656)
    Web Dynpro Code Generation Infos
    sap.com/pb
    SapDictionaryGenerationCore 7.0007.20060210160356.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:25:11[UTC], changelist=388986, host=PWDFM101.wdf.sap.corp)
    SapDictionaryGenerationTemplates 7.0007.20060210160356.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:25:18[UTC], changelist=388986, host=PWDFM101.wdf.sap.corp)
    SapGenerationFrameworkCore 7.0007.20050713144242.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:14:35[UTC], changelist=357697, host=PWDFM101.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 7.0007.20060228171604.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:30:31[UTC], changelist=391800, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCommon 7.0007.20060210160857.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:15:31[UTC], changelist=388995, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCore 7.0007.20060210160857.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:15:22[UTC], changelist=388995, host=PWDFM101.wdf.sap.corp)
    SapMetamodelDictionary 7.0007.20051128142655.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:22:56[UTC], changelist=378069, host=PWDFM101.wdf.sap.corp)
    SapMetamodelWebDynpro 7.0007.20060210162212.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:27:38[UTC], changelist=389002, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 7.0007.20060316153408.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:45:50[UTC], changelist=394237, host=pwdfm101)
    SapWebDynproGenerationCore 7.0007.20060228171604.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:30:40[UTC], changelist=391800, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationTemplates 7.0007.20060316153408.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:45:50[UTC], changelist=394237, host=pwdfm101)
    sap.com/tcwddispwda
    No information available null
    sap.com/pb_api
    SapDictionaryGenerationCore 7.0007.20060210160356.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:25:11[UTC], changelist=388986, host=PWDFM101.wdf.sap.corp)
    SapDictionaryGenerationTemplates 7.0007.20060210160356.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:25:18[UTC], changelist=388986, host=PWDFM101.wdf.sap.corp)
    SapGenerationFrameworkCore 7.0007.20050713144242.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:14:35[UTC], changelist=357697, host=PWDFM101.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 7.0007.20060228171604.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:30:31[UTC], changelist=391800, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCommon 7.0007.20060210160857.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:15:31[UTC], changelist=388995, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCore 7.0007.20060210160857.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:15:22[UTC], changelist=388995, host=PWDFM101.wdf.sap.corp)
    SapMetamodelDictionary 7.0007.20051128142655.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:22:56[UTC], changelist=378069, host=PWDFM101.wdf.sap.corp)
    SapMetamodelWebDynpro 7.0007.20060210162212.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:27:38[UTC], changelist=389002, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 7.0007.20060316153408.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:45:50[UTC], changelist=394237, host=pwdfm101)
    SapWebDynproGenerationCore 7.0007.20060228171604.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:30:40[UTC], changelist=391800, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationTemplates 7.0007.20060316153408.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:45:50[UTC], changelist=394237, host=pwdfm101)
    sap.com/tcwdcorecomp
    No information available null
    Detailed Error Information
    Detailed Exception Chain
    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to create delegate for view com.lti.CSLs. (Hint: Is the corresponding DC deployed correctly? Does the DC contain the component?)
         at com.sap.tc.webdynpro.progmodel.generation.ControllerHelper.createDelegate(ControllerHelper.java:110)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.<init>(DelegatingView.java:41)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.createUninitializedView(ViewManager.java:638)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:675)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:560)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.doOpen(WebDynproWindow.java:300)
         at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.open(ApplicationWindow.java:204)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:359)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:670)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:267)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:726)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:662)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:228)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
         at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
         at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:808)
         at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:227)
         at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1278)
         at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:353)
         at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:551)
         at com.sap.portal.pb.PageBuilder.wdDoApplicationStateChange(PageBuilder.java:300)
         at com.sap.portal.pb.wdp.InternalPageBuilder.wdDoApplicationStateChange(InternalPageBuilder.java:197)
         at sun.reflect.GeneratedMethodAccessor3364.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doApplicationStateChange(DelegatingComponent.java:139)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doApplicationStateChange(ClientComponent.java:659)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doApplicationStateChange(ClientApplication.java:532)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:120)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:297)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:706)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:660)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:228)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:56)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:47)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         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:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: java.lang.ClassNotFoundException: com.lti.wdp.InternalCSLs
    Found in negative cache
    Loader Info -
    ClassLoader name: [local/SLAReporting_KM]
    Parent loader name: [Frame ClassLoader]
    References:
       common:service:http;service:servlet_jsp
       service:ejb
       common:service:iiop;service:naming;service:p4;service:ts
       service:jmsconnector
       library:jsse
       library:servlet
       common:library:IAIKSecurity;library:activation;library:mail;library:tcsecssl
       library:ejb20
       library:j2eeca
       library:jms
       library:opensql
       common:library:com.sap.security.api.sda;library:com.sap.security.core.sda;library:security.class;library:webservices_lib;service:adminadapter;service:basicadmin;service:com.sap.security.core.ume.service;service:configuration;service:connector;service:dbpool;service:deploy;service:jmx;service:jmx_notification;service:keystore;service:security;service:userstore
       interface:resourcecontext_api
       interface:webservices
       interface:cross
       interface:ejbserialization
       sap.com/com.sap.km.application
       sap.com/tcwddispwda
       sap.com/tcwdcorecomp
       service:webdynpro
       service:sld
       library:tcddicddicservices
       library:com.sap.aii.proxy.framework
       library:tcgraphicsigs
       library:com.sap.mw.jco
       library:com.sap.lcr.api.cimclient
       library:sapxmltoolkit
       library:com.sap.aii.util.rb
       library:com.sap.util.monitor.jarm
       library:tcddicddicruntime
       library:com.sap.aii.util.xml
       library:tccolapi
       library:com.sap.aii.util.misc
       library:tc~cmi
       library:tccolruntime
    Resources:
       D:\usr\sap\CX5\DVEBMGS00\j2ee\cluster\server0\apps\local\SLAReporting_KM\webdynpro\public\lib\app.jar
    Loading model: {parent,references,local}
         at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:348)
         at com.sap.tc.webdynpro.progmodel.generation.ControllerHelper.createDelegate(ControllerHelper.java:65)
         ... 52 more

    Hi there,
    Try re-deploy the application and restart the server. It will fix this problemn.
    Regards,
    Luciano

  • After applying SP21 the web dynpro is not working (WDTypeNotFoundException)

    Hi
    We have recently applied SP21 to our NW04 system.
    The patch was successfully applied. But while accessing the Web Dynpro, we are getting WDTypeNotFoundException exception.
    The Error Message is as follows :
    +500 Internal Server Error
    Web Dynpro Container/SAP J2EE Engine/6.40
    Failed to process request. Please contact your system administrator.
    Hide
    Error Summary
    While processing the current request, an exception occured which could not be handled by the application or the framework.
    If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
    Root Cause
    The initial exception that caused the request to fail, was:
    500 Internal Server Error
    Web Dynpro Container/SAP J2EE Engine/6.40
    Failed to process request. Please contact your system administrator.
    Hide
    Error Summary
    While processing the current request, an exception occured which could not be handled by the application or the framework.
    If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
    Root Cause
    The initial exception that caused the request to fail, was:
    com.sap.tc.webdynpro.services.exceptions.WDTypeNotFoundException: type jp.co.companyname.projectname.pp.fnp09.datapreparemodel.types.Ru_cnfind not found
    at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getDataType(DataTypeBroker.java:224)
    at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.init(DataAttributeInfo.java:318)
    at com.sap.tc.webdynpro.progmodel.context.NodeInfo.addAttribute(NodeInfo.java:517)
    at com.sap.tc.webdynpro.progmodel.context.NodeInfo.addAttribute(NodeInfo.java:530)
    at jp.co.companyname.projectname.pp.fnp09.main.RawMaterialView.wdDoModifyView(RawMaterialView.java:191)
    ... 28 more
    See full exception chain for details.
    System Environment
    Client
    Web Dynpro Client Type HTML Client
    User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.2; .NET CLR 1.1.4322)
    Version
    DOM version
    Client Type msie6
    Client Type Profile ie6
    ActiveX enabled
    Cookies enabled
    Frames enabled
    Java Applets enabled
    JavaScript enabled
    Tables enabled
    VB Script enabled
    Server
    Web Dynpro Runtime Vendor: SAP, Build ID: 6.4021.00.0000.20070905102710.0000 (release=630_VAL_REL, buildtime=2007-09-19:20:40:15UTC, changelist=460812, host=PWDFM026)
    J2EE Engine 6.40 patchlevel 109749.313
    Java VM Java HotSpot(TM) Server VM, version:1.4.2_13-b06, vendor: Sun Microsystems Inc.
    Operating system Windows 2003, version: 5.2, architecture: x86
    Other
    Session Locale ja
    Time of Failure Mon May 17 18:35:52 JST 2007 (Java Time: 1197884152810)
    Web Dynpro Code Generation Infos
    companyname.co.jp/pp~fnp09
    SapDictionaryGenerationCore 6.4010.00.0000.20040910101802.0000 (release=630_VAL_REL, buildtime=2004-12-09:22:23:41UTC, changelist=280522, host=PWDFM026.wdf.sap.corp) +
    If you have any ideas please let me know.
    thanks and Regards
    Raghunahth L

    Hi raghu,
    You can go to Visual administrator (/usr/sap/<SID>/JCxx/j2ee/admin--go.bat)
    Give administrator credentials..
    Cluster-Server-Services-webdynpro Runtime.
    See if it is stopped.You can see red croos,if it is stopped.If it is,
    Right click on Webdynpro Runtine and  start.
    One more option,you can give a try is start all teh srvices manually through
    telnet
    This can be done with "run' command on you system
    telnet <IP adress> telnet port
    telnet port will be http port ending with 8.
    then give administrtaor credentials.
    then go with these commands,
    jump 0
    add deploy
    list_app
    start_app-all
    Try looki in for detailed error messages in default trace and application logs.
    Loc : /usr/sap/<SID>/JCxx/j2ee/cluster/server0/log
    Regards
    Usha

  • How to execute a BI query/view from a web dynpro application?

    Hi all,
    I am trying to connect to a BI system from a Web Dynpro application. I have to execute a view/query and process the output in my application. Please guide me about how to establish the connection to the BI system from my web dynpro application and then execute the query/view.
    I have tried executing/modelling the BI query/view using Visual Composer but I get an error saying 'QueryView Instantiation failed' when I try to drag the view/query on to the design board.
    Please guide me and help me achieve this.
    Thanks & Regards,
    Kishan

    Hi Kishan,
    Define system for BI in portal and define JCo destination, then from WDJ application use can query BI.
    Create the Technical System and connect with JCO Destinations
    or
    Connecting through the BI Connecters (ex: XMLA Connecter)
    Refer below link:-
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/60f35908-ecd4-2910-6c89-e75e1054d9d1?quicklink=index&overridelayout=true
    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/60f35908-ecd4-2910-6c89-e75e1054d9d1
    In this document you will get details related to connector and other admin activity.
    Hope this may help you.
    Deepak!!!

  • Trying to run a Web Dynpro Simple Sample with no luck??

    Hi I have downloaded a Web Dynpro and BPM simple sample application from this location: The problem is after configuring the CE instance and setting everything up, when i Deploy and Run this app i get the following error displayed can some one please help?? 500 Internal Server Error SAP NetWeaver Application Server/Java AS The initial exception that caused the request to fail, was: java.net.ConnectException: Connection timed out: connect at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) ... 115 more See full exception chain for details. Failed to process request. Please contact your system administrator. While processing the current request, an exception occured which could not be handled by the application or the framework. If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file). For further information about the Web Dynpro error page, error analysis and a description of well-known error situations, see SAP note 1113811. Correction Hints Exception could be caused by the development component: tcwdwebdynpro Note: The above hints are only a guess. They are automatically derived from the exception that occurred and therefore can't be guaranteed to address the original problem in all cases. System Environment Client Web Dynpro Client Type AJAX Client User agent Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; LLY-EMA-EN; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022; InfoPath.2; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; LLY-EMA-EN; LLY-EMA-EN) Client Type msie7 Client Type Profile ie6 ActiveX enabled Java Applets enabled Accessibility mode disabled Inline CSS false Validate by rendering true Server Web Dynpro Runtime vendor: 'sap.com', name: 'tc/wd/webdynpro', location: 'SAP AG', counter: '7.2001.20091210105536.0000', change number: '79724', codeline: NW720_01_REL J2EE Engine 7.20.3710.69682.20090922144234 System ID (SID) CE1 Server Node ID |3191650|31916|Server 00 00_31916|YHP30964.ema.lilly.com/40.205.138.181|SERVER|RUNNING Java VM SAP Java Server VM, version:6.1.007, vendor: SAP AG Operating system Windows XP, version: 5.1, architecture: x86 Application Java EE Application (deployable object) ides.com/soacmpssc~salsord Web Dynpro Application CreateSalesOrderApp Request URI /webdynpro/resources/ides.com/soacmpssc~salsord/CreateSalesOrderApp Version vendor: 'ides.com', name: 'soa/cmp/ssc/salsord', location: 'localDevelopment', counter: '20100329143545', change number: 'null' Session & Other Session Locale en_GB Session Timezone Greenwich Mean Time Time of Failure Mon Mar 29 15:38:53 BST 2010 (Java Time: 1269873533200) Session User ClientUser(id=USER.PRIVATE_DATASOURCE.un:Administrator, name=Administrator) Http Session Id tCJhFjXUItrW3M0cACKdKt9MDaBiM0upJwFiszAA_SAP Client Window Id Application Session Id b2a8d9023b4011dfb81f001b7889332c Web Dynpro Code Generation Infos ides.com/soacmpssc~salsord WD web module webdynpro/resources/ides.com/soacmpssc~salsord: SapDictionaryGenerationCore 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:31:05+0000, changelist=69541, host=pwdfm222, is-central=true) WD web module webdynpro/resources/ides.com/soacmpssc~salsord: SapDictionaryGenerationTemplates 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:31:22+0000, changelist=69541, host=pwdfm222, is-central=true) WD web module webdynpro/resources/ides.com/soacmpssc~salsord: SapGenerationFrameworkCore 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:18:18+0000, changelist=63859, host=pwdfm222, is-central=true) WD web module webdynpro/resources/ides.com/soacmpssc~salsord: SapIdeWebDynproCheckLayer 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:52:50+0000, changelist=69852, host=pwdfm222, is-central=true) WD web module webdynpro/resources/ides.com/soacmpssc~salsord: SapMetamodelCommon 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:22:47+0000, changelist=69781, host=pwdfm222, is-central=true) WD web module webdynpro/resources/ides.com/soacmpssc~salsord: SapMetamodelCore 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:19:24+0000, changelist=69781, host=pwdfm222, is-central=true) WD web module webdynpro/resources/ides.com/soacmpssc~salsord: SapMetamodelDictionary 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:26:44+0000, changelist=69542, host=pwdfm222, is-central=true) WD web module webdynpro/resources/ides.com/soacmpssc~salsord: SapMetamodelWebDynpro 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:34:20+0000, changelist=69853, host=pwdfm222, is-central=true) WD web module webdynpro/resources/ides.com/soacmpssc~salsord: SapWebDynproGenerationCore 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:53:23+0000, changelist=69852, host=pwdfm222, is-central=true) WD web module webdynpro/resources/ides.com/soacmpssc~salsord: SapWebDynproGenerationTemplates 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:52:22+0000, changelist=69852, host=pwdfm222, is-central=true) WD web module webdynpro/resources/ides.com/soacmpssc~salsord: SapWebDynproRuntimeGen 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:48:47+0000, changelist=64407, host=pwdfm222, is-central=true) sap.com/tcwdapi WD web module webdynpro/resources/sap.com/tcwdapi: SapDictionaryGenerationCore 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:31:05+0000, changelist=69541, host=pwdfm222, is-central=true) WD web module webdynpro/resources/sap.com/tcwdapi: SapDictionaryGenerationTemplates 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:31:32+0000, changelist=69541, host=pwdfm222, is-central=true) WD web module webdynpro/resources/sap.com/tcwdapi: SapGenerationFrameworkCore 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:18:18+0000, changelist=63859, host=pwdfm222, is-central=true) WD web module webdynpro/resources/sap.com/tcwdapi: SapIdeWebDynproCheckLayer 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:52:50+0000, changelist=69852, host=pwdfm222, is-central=true) WD web module webdynpro/resources/sap.com/tcwdapi: SapMetamodelCommon 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:22:47+0000, changelist=69781, host=pwdfm222, is-central=true) WD web module webdynpro/resources/sap.com/tcwdapi: SapMetamodelCore 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:19:24+0000, changelist=69781, host=pwdfm222, is-central=true) WD web module webdynpro/resources/sap.com/tcwdapi: SapMetamodelDictionary 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:26:44+0000, changelist=69542, host=pwdfm222, is-central=true) WD web module webdynpro/resources/sap.com/tcwdapi: SapMetamodelWebDynpro 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:34:20+0000, changelist=69853, host=pwdfm222, is-central=true) WD web module webdynpro/resources/sap.com/tcwdapi: SapWebDynproGenerationCore 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:53:23+0000, changelist=69852, host=pwdfm222, is-central=true) WD web module webdynpro/resources/sap.com/tcwdapi: SapWebDynproGenerationTemplates 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:53:55+0000, changelist=69852, host=pwdfm222, is-central=true) WD web module webdynpro/resources/sap.com/tcwdapi: SapWebDynproRuntimeGen 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:48:47+0000, changelist=64407, host=pwdfm222, is-central=true) Detailed Error Information Detailed Exception Chain com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exception was thrown in preprocessing phase of application session b2a8d9023b4011dfb81f001b7889332c. The causing exception is nested. RID=b2a8d9003b4011dfbdb7001b7889332c at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doPreprocessing(ApplicationSession.java:606) at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:335) at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:315) at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87) at com.sap.tc.webdynpro.serverimpl.wdc.DispatcherServlet.doContent(DispatcherServlet.java:76) at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doGet(AbstractDispatcherServlet.java:55) at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152) at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:447) at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:264) at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96) at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:315) Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to create delegate for component com.ides.soa.cmp.ssc.salsord.createsalesord.CreateSalesOrd. (Hint: Is the corresponding DC deployed correctly? Does the DC contain the component?) at com.sap.tc.webdynpro.progmodel.generation.ControllerHelper.createDelegate(ControllerHelper.java:98) at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.<init>(DelegatingComponent.java:79) at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:381) at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:566) at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doPreprocessing(ClientApplication.java:1438) at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doPreprocessing(ApplicationSession.java:603) ... 43 more Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at com.sap.tc.webdynpro.progmodel.generation.ControllerHelper.createDelegate(ControllerHelper.java:71) ... 48 more Caused by: com.sap.tc.webdynpro.model.webservice.exception.WSModelRuntimeException: Exception on creation of service metadata for WS metadata destination 'ERP_META' and WS interface 'SalesOrderBasicDataByBuyerAndBasicDataQueryResponse_In'. One possible reason is that the metadata destination 'ERP_META' has not been properly configured; check configuration. at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:558) at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.readOperationsFromWSDL(WSModelInfo.java:457) at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadataInternal(WSModelInfo.java:425) at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadata(WSModelInfo.java:399) at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateModelInfo(WSModelInfo.java:334) at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateModelInfo(WSModelInfo.java:307) at com.sap.tc.webdynpro.model.webservice.gci.WSTypedModel.<init>(WSTypedModel.java:93) at com.ides.soa.cmp.ssc.salsord.findsomodel.FindSOModel.<init>(FindSOModel.java:114) at com.ides.soa.cmp.ssc.salsord.createsalesord.CreateSalesOrd.<init>(CreateSalesOrd.java:732) at com.ides.soa.cmp.ssc.salsord.createsalesord.wdp.InternalCreateSalesOrd.<init>(InternalCreateSalesOrd.java:8892) ... 53 more

    Hi Anixan
    Please update the SAP AS Java at windows >> Preference >> SAP AS Java >> Add new SAP >> Put instance Hostname like 'CE1' and Instance Number like '00'. Then please verify that is connected or not in NWDS at windows >> show view >> Others >> Server >> Servers
    **Also update the Update your server IP address and host name in host file entry at (Start > RUN > drivers > etc > host file)
    and update JAVA_HOME system enviromental variable in my computer (My computer > Priperties >> Advance >> Startup and Recovery >> Enviromental Variable >> System Variables >> Add new JAVA_HOME parameter with path for installed Java JDK)
    Please check here http://help.sap.com/saphelp_nw70/helpdata/EN/43/3976df43b33575e10000000a11466f/content.htm
    Hope it helps
    Regards
    Arun

  • Error is in example  "How to Create Online and Offline Forms in Web Dynpro"

    Hi,
    I am developing " How to Create Online and Offline Forms in Web Dynpro " in nwds 7.0. This is standard example which is available at sdn. but when i run it gives me error like "
    Failed to process request. Please contact your system administrator.
    [Hide]
    Error Summary
    While processing the current request, an exception occured which could not be handled by the application or the framework.
    If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
    Root Cause
    The initial exception that caused the request to fail, was:
       java.lang.NullPointerException
        at com.travelrequestapp.TravelRequestComView.wdDoInit(TravelRequestComView.java:97)
        at com.travelrequestapp.wdp.InternalTravelRequestComView.wdDoInit(InternalTravelRequestComView.java:133)
        at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
        at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
        at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:445)
        ... 34 more
    See full exception chain for details.
    System Environment
    Client
    Web Dynpro Client Type HTML Client
    User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)
    Version null
    DOM version null
    Client Type msie6
    Client Type Profile ie6
    ActiveX enabled
    Cookies enabled
    Frames enabled
    Java Applets enabled
    JavaScript enabled
    Tables enabled
    VB Script enabled
    Server
    Web Dynpro Runtime Vendor: SAP, build ID: 7.0009.20060804145649.0000 (release=645_VAL_REL, buildtime=2006-08-26:14:41:58[UTC], changelist=413534, host=pwdfm101), build date: Thu Feb 15 10:23:57 IST 2007
    J2EE Engine 7.00 patchlevel
    Java VM Java HotSpot(TM) Server VM, version:1.4.2_13-b06, vendor: Sun Microsystems Inc.
    Operating system Windows 2003, version: 5.2, architecture: x86
    Session & Other
    Session Locale en_US
    Time of Failure Mon Oct 29 12:13:24 IST 2007 (Java Time: 1193640204484)
    Web Dynpro Code Generation Infos
    local/TravelRequest
    SapDictionaryGenerationCore 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-14:14:59:42[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
    SapDictionaryGenerationTemplates (unknown)
    SapGenerationFrameworkCore 7.0006.20050713144242.0000 (release=645_VAL_REL, buildtime=2006-01-14:14:48:59[UTC], changelist=357697, host=PWDFM101.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-14:15:05:10[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCommon 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-14:14:49:45[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCore 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-14:14:49:38[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
    SapMetamodelDictionary 7.0006.20051128142655.0000 (release=645_VAL_REL, buildtime=2006-01-14:14:57:39[UTC], changelist=378069, host=PWDFM101.wdf.sap.corp)
    SapMetamodelWebDynpro 7.0006.20051128151854.0000 (release=645_VAL_REL, buildtime=2006-01-14:15:02:09[UTC], changelist=378109, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 7.0006.20060111154644.0000 (release=645_VAL_REL, buildtime=2006-01-14:15:18:33[UTC], changelist=384368, host=pwdfm101)
    SapWebDynproGenerationCore 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-14:15:05:21[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationTemplates 7.0006.20060111154644.0000 (release=645_VAL_REL, buildtime=2006-01-14:15:18:33[UTC], changelist=384368, host=pwdfm101)
    sap.com/tcwddispwda
    No information available null
    sap.com/tcwdcorecomp
    No information available null
    Detailed Error Information
    Detailed Exception Chain
    java.lang.NullPointerException
         at com.travelrequestapp.TravelRequestComView.wdDoInit(TravelRequestComView.java:97)
         at com.travelrequestapp.wdp.InternalTravelRequestComView.wdDoInit(InternalTravelRequestComView.java:133)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
         at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:445)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.makeVisible(ViewManager.java:793)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.performNavigation(ViewManager.java:296)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:767)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.navigate(ClientComponent.java:873)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doNavigation(WindowPhaseModel.java:498)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:144)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         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:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    So please help me to correct this error .....
    Help will be rewarded.
    Regards,
    Gurprit Bhatia

    Hi Gurprit,
    A null value is being passed at runtime. Make sure that you enter values when filling in the form.
    Also check for the cardinality of the nodes being used. You can also initiliaze your value attributes as follows:
    In wdDoInit() method:
    wdContext.currentNodeAElement.setValueA("");
    Context is as follows:
    RootNode
      |____NodeA
            |_____ValueA
    Hope it helps.

Maybe you are looking for