Creating webdynpro system

Hi,
How can I create Webdynpro system in EP6.0??
Your help is highly appreciated.....
thanks,
sriram.

Hi Sree ram,
We generally create a 'dedicated R/3 System' or any other backend system in the portal and use that system for accesing WebDynpro applications. In the created system, specify the WAS host name and the WAS protocol.
WAS hostname :<host>.<domain>:<port>
WAS protocol : http
Or if your portal is installed on the same WAS server where your WD application runs, then you can directly use the default system available - SAP_LocalSystem.
Hope this helps,
Best Regards,
Nibu.

Similar Messages

  • Error while creating Technical System

    Hi
    i am creating Technical system in SLD. I gave all inputs for host name, Instance, License correctly.
    When i press next, It is throwing this error. Do anyone have any idea about this.
    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.IllegalArgumentException: The node, node element, and attribute info MUST NOT be null
        at com.sap.tc.webdynpro.progmodel.controller.MessageManager.reportContextAttributeMessage(MessageManager.java:940)
        at com.sap.sld.wd.technicalsystem.NewABAPSystem2.onActionNext(NewABAPSystem2.java:369)
        at com.sap.sld.wd.technicalsystem.wdp.InternalNewABAPSystem2.wdInvokeEventHandler(InternalNewABAPSystem2.java:344)
        at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
        at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
        ... 27 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; InfoPath.1; .NET CLR 1.1.4322; .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.0006.20060302084208.0000 (release=NW04S_06_REL, buildtime=2006-03-04:17:33:21[UTC], changelist=10570, host=pwdfm114), build date: Sat Oct 14 19:38:14 GMT+05:30 2006
    J2EE Engine 7.00 patchlevel
    Java VM Java HotSpot(TM) Server VM, version:1.4.2_12-b03, vendor: Sun Microsystems Inc.
    Operating system Windows 2003, version: 5.2, architecture: x86
    Session & Other
    Session Locale en
    Time of Failure Sat Nov 11 14:04:06 GMT+05:30 2006 (Java Time: 1163234046750)
    Web Dynpro Code Generation Infos
    sap.com/tcsldwd~main
    SapDictionaryGenerationCore 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:18[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
    SapDictionaryGenerationTemplates 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:25[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
    SapGenerationFrameworkCore 7.0006.20050713144242.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:06[UTC], changelist=357697, host=PWDFM101.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:22:50[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCommon 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:45[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCore 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:38[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
    SapMetamodelDictionary 7.0006.20051128142655.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:15:16[UTC], changelist=378069, host=PWDFM101.wdf.sap.corp)
    SapMetamodelWebDynpro 7.0006.20051128151854.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:19:38[UTC], changelist=378109, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
    SapWebDynproGenerationCore 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:23:00[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
    sap.com/tcsldwd~landscape
    SapDictionaryGenerationCore 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:18[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
    SapDictionaryGenerationTemplates 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:25[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
    SapGenerationFrameworkCore 7.0006.20050713144242.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:06[UTC], changelist=357697, host=PWDFM101.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:22:50[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCommon 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:45[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCore 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:38[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
    SapMetamodelDictionary 7.0006.20051128142655.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:15:16[UTC], changelist=378069, host=PWDFM101.wdf.sap.corp)
    SapMetamodelWebDynpro 7.0006.20051128151854.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:19:38[UTC], changelist=378109, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
    SapWebDynproGenerationCore 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:23:00[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
    sap.com/tcwddispwda
    No information available null
    sap.com/tcsldwd~businesssystem
    SapDictionaryGenerationCore 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:18[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
    SapDictionaryGenerationTemplates 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:25[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
    SapGenerationFrameworkCore 7.0006.20050713144242.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:06[UTC], changelist=357697, host=PWDFM101.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:22:50[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCommon 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:45[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCore 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:38[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
    SapMetamodelDictionary 7.0006.20051128142655.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:15:16[UTC], changelist=378069, host=PWDFM101.wdf.sap.corp)
    SapMetamodelWebDynpro 7.0006.20051128151854.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:19:38[UTC], changelist=378109, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
    SapWebDynproGenerationCore 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:23:00[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
    sap.com/tcsldwd~technicalsystem
    SapDictionaryGenerationCore 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:18[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
    SapDictionaryGenerationTemplates 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:25[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
    SapGenerationFrameworkCore 7.0006.20050713144242.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:06[UTC], changelist=357697, host=PWDFM101.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:22:50[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCommon 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:45[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCore 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:38[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
    SapMetamodelDictionary 7.0006.20051128142655.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:15:16[UTC], changelist=378069, host=PWDFM101.wdf.sap.corp)
    SapMetamodelWebDynpro 7.0006.20051128151854.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:19:38[UTC], changelist=378109, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
    SapWebDynproGenerationCore 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:23:00[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
    sap.com/tcwdcorecomp
    No information available null
    sap.com/tcsldwd~softwarecatalog
    SapDictionaryGenerationCore 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:18[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
    SapDictionaryGenerationTemplates 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:25[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
    SapGenerationFrameworkCore 7.0006.20050713144242.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:06[UTC], changelist=357697, host=PWDFM101.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:22:50[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCommon 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:45[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCore 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:38[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
    SapMetamodelDictionary 7.0006.20051128142655.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:15:16[UTC], changelist=378069, host=PWDFM101.wdf.sap.corp)
    SapMetamodelWebDynpro 7.0006.20051128151854.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:19:38[UTC], changelist=378109, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
    SapWebDynproGenerationCore 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:23:00[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
    sap.com/tcsldwd~namereservation
    SapDictionaryGenerationCore 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:18[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
    SapDictionaryGenerationTemplates 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:25[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
    SapGenerationFrameworkCore 7.0006.20050713144242.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:06[UTC], changelist=357697, host=PWDFM101.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:22:50[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCommon 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:45[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCore 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:38[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
    SapMetamodelDictionary 7.0006.20051128142655.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:15:16[UTC], changelist=378069, host=PWDFM101.wdf.sap.corp)
    SapMetamodelWebDynpro 7.0006.20051128151854.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:19:38[UTC], changelist=378109, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
    SapWebDynproGenerationCore 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:23:00[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
    Detailed Error Information
    Detailed Exception Chain
    java.lang.IllegalArgumentException: The node, node element, and attribute info MUST NOT be null
         at com.sap.tc.webdynpro.progmodel.controller.MessageManager.reportContextAttributeMessage(MessageManager.java:940)
         at com.sap.sld.wd.technicalsystem.NewABAPSystem2.onActionNext(NewABAPSystem2.java:369)
         at com.sap.sld.wd.technicalsystem.wdp.InternalNewABAPSystem2.wdInvokeEventHandler(InternalNewABAPSystem2.java:344)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
         at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:422)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:133)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:344)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:298)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:705)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:659)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:227)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:150)
         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)
    Thanks in Advance
    Vijay Raheja

    HI Michal Krawczyk,
    Thanks for your response. i am working on XI 7.0 and when i go to SLD-> Adminitsrtion-> SLD Data Supplier. There i tried to add SLD CLient.
    It is asking me for :
    -URL of target SLD system, e.g. http://host:port/
    -User
    -Password.
    What should i give here. WHat will be port for R/3 system to which i want to connect.
    Just to add: I have already created Technical system for R/3(CLient 600). I added this through SLD only. But now it is giving error for Technical SYstem for same R/3(Clinet 812).
    Thanks,
    Vijay Raheja

  • I created webdynpro view then i want to export to sap portals using SLD CON

    hi
    every body
    i created WebDynpro views in NetWeaver dev studio
    then i want to export to sap portals i have to use
    SLED CONFIGURATION what are all step required can
    post to me and aloes step to configure in visual administrator and JCo connections
    bee

    hi
    check out this weblog for SLD configuration
    /people/sugree.phatanapherom/blog/2005/08/14/configuring-sld-in-sneak-preview-sap-netweaver-04-sneak
    or
    Do the following
    SLD (System Landscape Directory) CONFIGURATION on J2EE Server.
    http://host:j2ee_port/sld
    Enter Administrator user name and password.
    Go to Administration -> Server Settings
    Make sure that the SLD server is stopped
    Enter the following Server Parameters
    Object Server:
    <Host name of the J2EE server>
    Working Directory:
    The working directory of the System Landscape Directory.
    The standard path is "/usr/sap/<SAPSID>/SYS/global/sld"
    Click on SET.
    Select the following parameter for Persistence
    Persistence: Database
    Click on SET.
    Leave ABAP Connection Parameters Blank.
    Go back to Administration.
    Click on Data Supplier Bridge
    Configure the data supplier bridge with following parameters.
    Update local SLD (sld/active): TRUE
    RFC Gateway:
    Server : <host name of J2EE server>
    Service : <The SAP gateway service port>
    Click on SET.
    Open Administration Tool for J2EE server from following Location.
    C:\usr\sap\<SID>\JC<instance number>\j2ee\admin\go.bat
    Select Default and Click on Connect.
    Enter password for Administrator.
    Click on Connect.
    Select Cluster->Server->Services->SLD Data Supplier
    Select http setting tab page and enter following details.
    Host: <host name of J2EE server>
    Port: <Port Number of J2Ee Server>
    User: <Administrator User>
    Password: <Password for Administrator User>
    Use https? : <Check this if you want to use https>
    Trust Store: <leave default i.e. TrustedCAs>
    Click on SAVE.
    Select RFC Settings tab page and enter following details.
    Gateway Host : <host name of J2EE server>
    Gateway Service/Port: sapgw<instance number>
    Click on SAVE.
    Restart the SLD data Supplier Service.
    After the SLD is configured.
    go to the path.
    http://<hostname>:50000/webdynpro/welcome.
    go to your application.
    click on the application. on the right hand side you can see you logical systems.
    create the JCO connection going through that steps.
    Deploy you application on to portal from NWDS and run your application.
    Regards,
    Gopi

  • Created HTTP system, which iView to choose?

    Hello:
    I have created a webDynpro app that requires authentication (using the authentication default property). It now shows me the normal SAP logon and it works fine.
    Now I have deployed it into the portal and in order to avoid getting two logon screens (one for the portal and one for the iView) I've set up a new HTTP System, giving as parameters the webDynpro URL (both WEB AS and WD app are in the same box) and the fields for user and password.
    Now I do believe those parameters are ok. Now that I've created the system, gave an Alias and set User mapping, which iView should I create in order to actually use the new system?
    Thanks in advance
    Regards
    Alejandro

    Hi,
      I think u are looking for something like an <i>application integrator</i>. Using this, the user can login from portal & enter the homepage of his application directly.
    The following weblog link guides u to proceed:
    Step-By-Step Guide to implement Application Integrator
    Hope it helps.
    Regards,
    M.Subathra

  • Error while creating a system object for R3 in portal

    Hi,
    I am getting error while trying to create a system object in portal.
    Following are the details I used :
    Under WAS...
    Web AS Host Name :<XXXX>:8001
    Web AS path: /sap/bc/bsp/sap/
    Web AS protocol : http
    Under User management:
    Authentication Ticket Type : SAP Logon Ticket
    Logon Method :SAPLOGONTICKET
    User Mapping Type : admin,user
    Under Connector:
    SAP Client : <Client NO>
    SAP System ID : <System ID>
    SAP System No : <System No>
    System Type : SAP_R3
    While trying with connection test... I am getting like this:
    SAP Web AS Connection
      Test Details:
    The test consists of the following steps:
    1. Checks the validity of system ID in the system object.
    2. Checks if the system can be retrieved from the PCD.
    3. Check whether a SAP system is defined in the system object
    4. Validate the following parameters: WAS protocol; WAS host name
    5. Checks if the host name of the server can be resolved.
    6. Pings the server to see if it is alive.
    7. Pings the WAS ping service; works only if the service is activated on the ABAP WAS.
    8. Checks HTTP/S connectivity to the defined back-end application
      Results
    1. The system ID is valid
    2. The system was retrieved.
    3. The system object represents an SAP system
    4. The following parameters are valid: Web AS Protocol (http) Web AS Host Name (<FQDN server name>:8001)
    5. The host name <FQDN Server Name> was resolved successfully.
    6. The server sapdwh01 could not be pinged successfully.
    Test Connection with Connector
      Test Details:
    The test consists of the following steps:
    1. Retrieve the default alias of the system
    2. Check the connection to the backend application using the connector defined in this system object
      Results
    Retrieval of default alias successful
    Connection failed. Make sure that Single Sign-On is configured correctly
    It seems that the portal is not able to ping to R3 system. I tried to ping to R3 server from portal server by command prompt. I am able to ping. Also under SICF, I can see ping service as in activated state.
    Kindly help.
    Regards,
    Niraj
    Edited by: Niraj Kumar on Dec 11, 2008 10:41 AM

    I created a SAP Transactional iView for transaction SE80.
    Also, I tried from under System Administration -> Support -> SAP Transaction. It is not working.
    Got portal Runtime error :
    Portal Runtime Error
    An exception occurred while processing your request
    Exception id: 12:57_11/12/08_0003_2795650
    See the details for the exception ID in the log file.
    Regards,
    Niraj

  • Why do we create logical systems in ALE?

    Hi All,
            i got this question in interview.
        Why do we create logical systems in ALE?
    Thanks & Regards
    suresh

    Hi
    In addition to above .
    A logical system is used to identify an individual client in a system, for ALE communication between SAP systems. That's why you see a field for 'logical system' in the client master data in SCC4 (table T000).
    /people/udo.martens/blog/2005/09/30/one-logical-system-name-for-serveral-bpm-acknowledgements
    http://help.sap.com/saphelp_nw04/helpdata/en/b5/1d733b73a8f706e10000000a11402f/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/69/c24ca94ba111d189750000e8322d00/content.htm
    http://72.14.203.104/search?q=cache:J-uDLyT0w54J:www.topxml.com/biztalkutilities/walkthroughs/SAP%2520Configuration.pdfwhatislogicalsystems+(SAP)&hl=en&gl=in&ct=clnk&cd=5
    http://help.sap.com/saphelp_nw04/helpdata/en/78/217dc151ce11d189570000e829fbbd/content.htm
    http://help.sap.com/saphelp_nw04s/helpdata/en/d7/9c73631d6c11d2a56e0060087832f8/content.htm
    This guide is really good shows step by step procedure.
    http://72.14.203.104/search?q=cache:Xyl0zxpyEXsJ:www.sappoint.com/abap/ale.pdfLogicalsystem(ALE)&hl=en&gl=in&ct=clnk&cd=9
    for one client config
    http://www.sappro.com/downloads/OneClientDistribution.pdf#search=%22Logical%20system(ALE)%22
    Please reward for the same.

  • PI 7.11 - How to create a System Error in SXMB_MONI using a Java Mapping

    Hi
    We ve go a  Java Mapping in a File-to-HTTP Scenario. It works perfect except of one error case: if an empty source file or a source file with the wrong structure is delivered. In this case our Java Mapping forwards an empty payload to the HTTP channel. So, for PI is the mapping successful.
    I'd like to recognize this case and invoke a system error in the SXMB_MONI, so that this mapping will be stopped and our alerting concept informs the users. I know, how to recognize the case in Java but need to know how to create the System Error Status in the PI System.
    Thanks in advance
    Michael

    Hi Michael,
    Please refer here for the mapping API description:
    http://help.sap.com/javadocs/NW04S/SPS09/pi/com/sap/aii/mapping/api/package-summary.html
    You can use the StreamTransformationException exception describet there to raise an error from your Java mapping. Direct link:
    http://help.sap.com/javadocs/NW04S/SPS09/pi/com/sap/aii/mapping/api/StreamTransformationException.html
    You might also consider using the "Empty-File Handling" option in sender file CC to avoid processing empty files by PI.
    Hope this helps,
    Greg

  • How to find Installation Number in R3 to create Technical system in XI.

    Hi,
    how to find Installation Number in R3 to create Technical system in XI. can you please help me out.
    thanks
    siva.

    Hi Siva,
    Host name you can find at same location. Not sure about message server port (Basis team shall be able to provide this information)....
    However there is a very simple way fo creating technical system..
    Check out this Michals blog...its very easy
    /people/michal.krawczyk2/blog/2005/03/10/registering-a-new-technical-system-in-sld--abap-based
    Nilesh

  • Creating FRCommon system failed - in 11g Forms & Report Installation

    Dear all,
    When installing 11g Forms and Reports "*Creating FRCommon system failed - in 11g Forms & Report Installation*".
    I have successfully created the weblogic server 10.3.5 , and continued with 11g forms & reports. First Installed the forms & reports software, and i try to configure. after several steps of configuration i have failed when its place "*Creating FRCommon system failed - in 11g Forms & Report Installation*".
    What it is this Error.
    Kindly help me.
    My OS Windows
    Forms and reports 11gR2
    More info
    When i start the configuration i have chosen Forms & Reports server and Development tools in the configuration page along with OHS.
    Regards
    Hamid

    Hi experts,
    I have the same problem when I try to install oracle Fusion Middleware 11g, is it possible that I forget some steps before, or should I install required something before continue intallation?
    Best Regards.
    Karim.

  • Portal Runtime Error while creating  new system in portal content

    Hi
      Can anyone  solve my problem, i am geting error while creating new system in p ortal content
    Portal Runtime Error
    An exception occurred while processing a request for :
    iView : pcd:portal_content/com.sap.pct/admin.templates/iviews/editors/com.sap.portal.templateSelection
    Component Name : com.sap.portal.admin.templateselectionwizard.default
    com/sap/portal/iviewserver/cache/OClass.
    Exception id: 11:29_26/12/06_0014_5891950
    See the details for the exception ID in the log file

    Hi,
    Check this link for creating system object
    http://help.sap.com/bp_epv260/EP_EN/documentation/EP/N03_BB_InstallGuide_EN_US.doc
    Regards
    Arun

  • While creating Billing, system is very slow..performance issue

    Hi,
    While creating Billing, system is very slow. How can I debugg and provide the analysis where is the exact problem.
    This is showing performance issue.
    Waiting for kind response.
    Best Regards,
    Padhy
    Moderator Message : Duplicate post locked.
    Edited by: Vinod Kumar on May 12, 2011 10:59 AM

    hi,
    Chk the links
    http://help.sap.com/saphelp_nw04/helpdata/en/4a/e71f39488fee0ce10000000a114084/content.htm
    Re: How to create Secondary Index?
    How may secondary indices I can create on the ODS?
    Deletion of ODS index
    Ramesh

  • Problem in Creating a System through WEB AS

    Hi ,
         I created a System (ECC 6.0) in Portal and testing it through WEB AS.I'am able to "Test the connection for Connectors" but when coming to test WEBAS am getting an error "<b>Test Details:
    The test consists of the following steps:
    1. Check the validity of the system ID in the system object
    2. Check whether the system can be retrieved
    3. Check whether a SAP system is defined in the system object
    4. Validate the following parameters: WAS protocol; WAS host name
    5. Check HTTP/S connectivity to the defined backend application
      Results
    1. The system ID is valid
    2. Retrieval of the system was successful
    3. The system object represents an SAP system
    4. The following parameters are valid: Web AS Protocol (http) Web AS Host Name (srtplecd:8000)
    5. HTTP/S connection failed</b> "
    please help me in this.
    with regards,
    pradeep.B

    Yes i had entered everything required for WAS and when i'am doing Connection Tests through WAS am getting this error "<b>SAP Web AS Connection
      Test Details:
    The test consists of the following steps:
    1. Check the validity of the system ID in the system object
    2. Check whether the system can be retrieved
    3. Check whether a SAP system is defined in the system object
    4. Validate the following parameters: WAS protocol; WAS host name
    5. Check HTTP/S connectivity to the defined backend application
      Results
    1. The system ID is valid
    2. Retrieval of the system was successful
    3. The system object represents an SAP system
    4. The following parameters are valid: Web AS Protocol (http) Web AS Host Name (srtplecd:8000)
    5. HTTP/S connection failed</b>"

  • Error While Creating Technical System for SNC

    Hi There,
    I am trying to create technical system for SNC in SLD, I am not able to seee SNC as a s/w component/product in the list.
    when I checked the list of components in SLD, I found SNC is there under product "SCMSNC" but this product is not in the list of products.
    Please help me how I can get "SCMSNC" product in the product list.
    Thanks,
    Nishant

    Can you please explain it little bit clearly?
    I think you first create product, then SWC and then try to create Technical system.
    While you will create the Technical system, in the last step it will ask you for installed products.
    There you can specify ur product.
    Thanks,
    Hetal

  • RUNTIME ERROR WHILE CREATING NEW SYSTEM IN EP6

    Hi
    Can anyone solve my problem, i am geting error while creating new system PORTAL FOR to connect biw 3.5 system
    Portal Runtime Error
    An exception occurred while processing a request for :
    iView : pcd:portal_content/com.sap.pct/admin.templates/iviews/editors/com.sap.portal.templateSelection
    Component Name : com.sap.portal.admin.templateselectionwizard.default
    com/sap/portal/iviewserver/cache/OClass.
    Exception id: 11:29_26/12/06_0014_5891950
    See the details for the exception ID in the log file
    thanks in advance
    Rock

    hi,
    check the log file and let me the the error.
    manish

  • Error while creating SOURCE SYSTEM

    Hi All,
    I have a problem while creating Source System to a Solman syatem configured with BW content. I have configured few some source systems already in the same Solman System.The system shows the following error, previous to this i get the message a "generating connection to the source system"
    <b>Error in source system RXX_100
    Message no. RSAR502
    Diagnosis
    With Remote Function Call to system RXX_100 error Screen output without connection to user.  ccurred.
    Procedure
    Remove the cause of the error.</b>
    Kindly provide me suggestions and DOCS related to the same.
    Suitable points will be awarded for replies.
    Expecting your kind reply,
    Vineeth

    Hi ,
    In SCC4 the source client should not set as production when creating the source system connection between two systems.Please check below SAP note
    973555 - System must be open for creating/connecting source systems
    Thanks,
    Shanaka

Maybe you are looking for