Webdynpro content administrator

Hi All,
I am able to access Webdynpro content administrator  & webdynpro content through the 50000 port only. but we have IIS sitting infront of it on port 80. when i try to access the webdynpro content or content administrator through http://host/<webdynrocontent admin content URL>  it gives page connot be displayed page. is there anyway to access webdynpro content OR webdynpro content adminstrator the with no port specified in the URL.

First thank you very much for help. Yes. we found that IIS is not allowing /webdynpro and blocking this URL's. we got it working after configuring the IIS.
From this it is clear that all webdynpro Iviews are URL iviews? Am i correct in understanding this?

Similar Messages

  • Jco destiantions are with greyed status in webdynpro content administrator

    Hi All
    In webdynpro content administrator of BI System all the jco destinations are displatyed with greyed status,even i tried to create new destination with any name the message comes use another destination,it is already used in sld.the connection to sld is working fine.i am using the user as j2ee_admin.
    kindly help me out.
    Regards
    Pranav

    Hi Pranav
    If the SLD is working fine then you need to check the below thing :-
    1. Check the SLD Data Supplier in the Visual Administrator and update the correct information and test it.
    2. Update Host and service file for server in the server system for jco destinations visibility.
    Refer to [System Landscape Directory Process and JCo Configuration|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c0c1d495-048e-2b10-babd-924a136f56b5?quicklink=index&overridelayout=true]
    Hope it will helps.
    Best Regards, Arun Jaiswal

  • Unable to start WebDynpro Content Administrator.....

    Hello All,
            I am trying access webDynpro Content Administrator from ContentAdmin-> webDynpro but I am getting message
    <b>Missing Permissiones</b>
    <b>You do not have the needed permissions to start the Web Dynpro Content Administrator.
    Please contact your System Administrator.</b>
    I have assigned "Administrator , Super Admin & Content Admin" roles to administrator but still i am not able to view the contents of content admin.
    Pls help !
    awaiting reply !
    thanks,
    Smita

    Hello
    You need the LCR roles. Assign the roles in the Portal:
    LcrAdministrator
    LcrUser
    If you cant find the roles, you need to perform the postinstallation for SLD. It is pretty easy. Or you can import this:
    [role]
    rid=LcrClassWriter
    action=sap.com_com.sap.lcr.LcrClassWriter
    [role]
    rid=LcrAdministrator
    action=sap.com_com.sap.lcr.LcrAdministrator
    group=SAP_SLD_ADMINISTRATOR
    [role]
    rid=LcrInstanceWriterLD
    action=sap.com_com.sap.lcr.LcrInstanceWriterLD
    group=SAP_SLD_DEVELOPER;SAP_SLD_CONFIGURATOR
    [role]
    rid=LcrUser
    action=sap.com_com.sap.lcr.LcrUser
    user=J2EE_ADMIN
    group=SAP_SLD_GUEST
    [role]
    rid=LcrInstanceWriterCR
    action=sap.com_com.sap.lcr.LcrInstanceWriterCR
    [role]
    rid=LcrSupport
    action=sap.com_com.sap.lcr.LcrSupport
    group=SAP_SLD_SUPPORT
    [role]
    rid=LcrInstanceWriterAll
    action=sap.com_com.sap.lcr.LcrInstanceWriterAll
    group=SAP_SLD_ORGANIZER
    [role]
    rid=LcrInstanceWriterNR
    action=sap.com_com.sap.lcr.LcrInstanceWriterNR
    group=SAP_SLD_CONFIGURATOR
    Best Regards
    Kristoffer Engh

  • WebDynpro Content Administration

    Hi,
    My requirement is that I have to give WebDynpro Content Administration Page access to one of my developer. But I dont want him to Get Content/System/User Admin Role. I cleared all his roles and attached his ID to Administrator GROUP. It gave him access to Content/System/User  Admin Roles. Can I just give him priviliges to access only the Page of WebDynpro Content Administration.
    Any work around option for this.
    Regards,
    Murali.

    Hi Praveen,
    Thanks for ur Inputs.
    I have created a Role WD_DEV and attached the standard workset. For this Role, I went to the Permissions and gave
    Administrator, SAP_JAVA_NWADMIN_CENTRAL, SAP_JAVA_NWADMIN_LOCAL, super_admin_role, user_admin_role and the <b>userID</b> all Full Control access.
    My user is abel to logon and see this role. But when he access this page it says ' You do not have the needed permissions to start the Web Dynpro Content Administrator.
    Please contact your System Administrator. '
    I didnt create any group. Instead attached all permissions straight away to this role and attached this role to my user.
    Did I go wrong anywhere ?
    Regards,
    Murali.

  • Application cannot be started for WebDynpro Content Administrator

    <b></b>
    Hello Dear Friends,
    It's very Urgebt for me Plz....,
    We are on EP6.0 SP14 and implementing  ESS using WebDynpro for this we uploaded patch ESS & XSS Components
    firsttime in EP6.0 SP9 after we upgraded to SP14 here we faced some problems and undeployed the deployed components ESS&XSS the undeployment is sucessfully done after we are trying to logon into WebDynpro Content Administrator its giving the following Error Messgage.
    <b>
    SAP J2EE Engine/6.40
    503   Service Unavailable
    Application cannot be started.
    Details: 
    com.sap.engine.services.deploy.container.ExceptionInfo: Container metamodelrepository is not active at the moment and it is not possible to startApp sap.com/com.sap.security.core.admin.</b>
    Could u plz help me on this issue..,
    Thanks in advance and waiting for reply...........
    Sreedhar G

    Hi,
    check the status of J2EE engine.
    Check if it works after restarting J2EE engine.
    Regards,
    Ashutosh

  • Unable to see deployed component in webdynpro content administrator

    Hi,
    I created a DC under sap.com domain in one of the tracks and was able to checkin and activate that deploy that successfully,
    When i looked at the deployment log and activation log it says component is successfully deployed.
    I looked in the DTR and CBS and I could see the deployed component
    But when i look at the deployed components in Webdynpro content administrator under sap.com it is not showing the DC which i created and deployed.
    What is the wrong with the deployment
    Please let me know what is the solution
    Points will be awarded for sure
    Bala

    Hi,
    1. Did you try searching through content administrator->web dynpro->'Search' tab for the relevant object?
    2. It seems that the runtime system you are looking at is configured with the "Disable automatic deployment" option in the CMS. Pls check the status.
    3. If it so, you can start manual deployment as follows:
    a. Start the deployment servlet using http://<CBS_host>:<port>/TCS/Deployer
    b. In the "Buildrequests in queue" list, select the "buildspace name" for which you want to start the deployment and enter this name in the Buildspace field.
    c. Select "Submit".
    This will perform the deployment action.
    Regards
    Srinivasan T

  • Portal User needs permissions to start the WebDynpro Content Administrator

    Hi All,
      We are on EP6 SP13 (SR1 installation) with ECC5 as backend.
    We have a user(<b>j2ee_adm_qep</b>) as a default portal administrator.
    When i see <b>Content Administrator >> Webdynpro >></b> i get the webdynpro content administrator screen.. <b>:)</b>
    I have created another portal admin user (<b>myadmin</b>) and gave him all the roles that <b>'j2ee_adm_qep'</b> has..
    Also, Even in the backend ECC system.. Su01 transaction.. i have given
         >>>>> ROLES >>> SAP_J2EE_ADMIN
         >>>>> PROFILES >>> SAP_ALL
    But, when i login as '<i>myadmin</i>' and see the <b>Content Administrator >> Webdynpro >></b> i get the following message:
    Missing Permission
    You do not have the needed permissions to start the Web Dynpro Content Administrator.
    Please contact your System Administrator.
    I want to see the '<b>webdynpro content administrator screen</b>' when i login as '<i>myadmin</i>' too..! '<i>myadmin</i>' should have every permission as <i>'j2ee_adm_qep'</i>.
    Please help me in this regard.. This is kind of urgent.
    Would be grateful for any input.
    Regards,
    SK.

    Hi,
    A user in SAP EP has two types of access "roles", J2EE groups and SAP EP roles. Here you are missing the J2EE group administrator (backend roles in ECC system are not needed).
    The easiest way to change this is to go to user admin -> groups, search for Administrators and add the myadmin user to this group (alternatively use the security provider service of visual admin).
    Dagfinn

  • Webdynpro content administrator-- Start Assigned SLD  results in Error.

    Hi,
    I am using Netweaver 7.1 CE. I have configured SLD and started,and it is running. Now I went to crearte JCO destinations. When I tried to Start Assigned SLD  it is giving  a error. When I checked the Check SLD Connection  a pop up is comming and in it Hostname: *blank, port:+-1+, user: +blank,url:null://null:-1/sld*+
    Help in solving this issue I need to do a start assigned SLD. I am attaching the error details
    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).
    For further information about the Web Dynpro error page, error analysis and a description of well-known error situations, see SAP note 1113811.
    Root Cause
    The initial exception that caused the request to fail, was:
       java.net.MalformedURLException: The protocol is not allowed
        at com.sap.security.core.server.csi.URLChecker._isValid(URLChecker.java:334)
        at com.sap.security.core.server.csi.URLChecker.isValid(URLChecker.java:775)
        at com.sap.tc.webdynpro.serverimpl.core.url.AbstractURLGenerator.checkURL(AbstractURLGenerator.java:773)
        at com.sap.tc.webdynpro.services.sal.url.core.URLGeneratorInternal.checkURL(URLGeneratorInternal.java:404)
        at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createNonModalExternalWindow(ClientComponent.java:1034)
        ... 66 more
    Detailed Error Information
    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Invalid URL=null://null:-1/sld. See nested exception for details. Please check whether the URL contains query parameters which are not allowed for security reasons. See SAP note 864842 for more details.
      at com.sap.tc.webdynpro.serverimpl.core.url.AbstractURLGenerator.checkURL(AbstractURLGenerator.java:785)
      at com.sap.tc.webdynpro.services.sal.url.core.URLGeneratorInternal.checkURL(URLGeneratorInternal.java:404)
      at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createNonModalExternalWindow(ClientComponent.java:1034)
      at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createExternalWindow(ClientComponent.java:1009)
      at com.sap.tc.webdynpro.tools.explorer.StartView.onActionStartAssignedSLD(StartView.java:283)
      at com.sap.tc.webdynpro.tools.explorer.wdp.InternalStartView.wdInvokeEventHandler(InternalStartView.java:265)
      at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:131)
      at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:72)
      at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.doHandleActionEvent(ProcessingEventPhase.java:156)
      at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.execute(ProcessingEventPhase.java:91)
      at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequestPartly(WindowPhaseModel.java:161)
      at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doProcessRequest(WindowPhaseModel.java:109)
      at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:96)
      at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:469)
      at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:52)
      at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doExecute(ClientApplication.java:1431)
      at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doProcessing(ClientApplication.java:1251)
      at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToApplicationDoProcessing(AbstractExecutionContextDispatcher.java:158)
      at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForAppProcessing.doService(DispatchHandlerForAppProcessing.java:35)
      at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:116)
      at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:93)
      at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToApplicationDoProcessing(ExecutionContextDispatcher.java:114)
      at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:81)
      at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:507)
      at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:527)
      at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessingStandalone(ApplicationSession.java:458)
      at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:249)
      at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:699)
      at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:231)
      at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:231)
      at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToRequestManager(AbstractExecutionContextDispatcher.java:205)
      at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForRequestManager.doService(DispatchHandlerForRequestManager.java:38)
      at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:116)
      at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:93)
      at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToRequestManager(ExecutionContextDispatcher.java:140)
      at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:93)
      at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:105)
      at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
      at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doPost(AbstractDispatcherServlet.java:61)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
      at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:66)
      at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:32)
      at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:431)
      at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:289)
      at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
      at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:376)
      at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:85)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
      at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:160)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
      at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67)
      at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
      at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
      at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
      at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
      at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
      at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
      at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
      at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:309)
      at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:222)
      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:152)
      at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)
    Caused by: java.net.MalformedURLException: The protocol is not allowed
      at com.sap.security.core.server.csi.URLChecker._isValid(URLChecker.java:334)
      at com.sap.security.core.server.csi.URLChecker.isValid(URLChecker.java:775)
      at com.sap.tc.webdynpro.serverimpl.core.url.AbstractURLGenerator.checkURL(AbstractURLGenerator.java:773)
    Thanks & Regards
    Muhammed Nishad J

    Hi,
    By default on CE SLD is not available. Please go through this to configure SLD
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/20c58fff-0c62-2b10-4381-9ac4d920a8cc
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c09527da-39a7-2b10-9f99-c6a007e516a5
    Regards
    Ayyapparaj

  • New JCo names are not listing in WB Content Administrator

    Dear Friends,
    I have deployed my WebDynpro application on a landscape where the production system got 4 server services running.
    Initially the WD application was using the existing JCo connections.  But on the latest deploy I have to use new JCo connections and I made changes.
    Problem is, these new JCo connection names are not appearing in WebDynpro Content Administrator and still it displays old JCo connections.
    This problem exists with global WD Content Admin. URL as well as with individual server url, except in one server instance where JCos yet to be created.
    But when I execute the application with global URL, it is working fine.
    Intent is to create and use my new JCo connections for the application which are not listing in WB Content Admin.
    Is it require to restart the server services? 
    Is it possible to solve this problem without restarting the services?
    Is there any other way to resolve this problem?
    Thanks in advance.
    Lakshmikantha

    Sorry I can't approach to restart the j2ee service at this movement.
    And the application got new JCo name at it's JCO refrences.
    Infact the application is working fine with new JCos on development and quality systems.
    Problem exists only on production system where it got 4 server instances.
    Any hope without restarting services?

  • JCO connection in content administrator

    Hi All,
    I am doing a webdynpro Java application to call an RFC via webdynprpo java. After doing all the things. we created a
    JCO connection in content administrator. When we chose the Choose the JCO Connections tab, Two destinations named WD_FLIGHTLIST_MODELDATA_DEST and
    WD_FLIGHTLIST_RFC_METADATA_DEST are shown in this view and both of them have the status disabled. And the create button is also disabled. So we are not able to have a jco connection. What is this so? How can we bring the status enabled? What has to be done for this? Can anyone please provide solution for this?
    Regards,
    Divya

    Hi Divya,
    Are you logged in with Admin rights. try assigning the user to the ADMINISTRATOR group and then check whether it works or not .
    Did you configured SLD?..check the SLD connection is sucessful then only you can create JCO connection.
    Check this link for webdynpro content administrator:
    [Here|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3d7db2e5-0601-0010-4a88-9f3498f8142f] and [Here|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3103eb90-0201-0010-71af-be6f4a6f61d1]
    Regards, Suresh KB

  • Wrong information when select " Check SLD connetion" in Webdynpro Content

    Hi All,
    When I go to Webdynpro Content Administrator, select the button " Check SLD connection" and a new window come up with the details of where the SLD is running.
    I noticed the details are incorrect, i.e. port 54200 instead of 50700. I have check in the SLD service Visual administrator and it has correct information of hostname and port number ...
    Can you please help to point out where/how did it pick up this information?

    Hi Vincent,
    I dont think your sld is configured and running.
    1. since you said the port number is wrong you have to correct the settings in the first place.
    2. secondly you need to check the link which will be in the format http://host address:portnumber/sld and configure the sld there and then check if its up and running.
    these steps would be mentioned clealy in the guide may be in the post installation activities please check that and keep us updated.
    Regards,
    Nitin

  • Remove applications from content administrator

    Hi,
    I have some applications on the WebAS that should be removed.
    I*ve undeployed all applications with the SDM.
    But the Applications are still grey marked available in the WEbDynpro content administrator and it shows some error because of that.
    Is there any way to remove the Applications also from the Content Admin?
    Thanks and best regards,
    Dennis

    Hi,
    I first have undeployed with the visual admin, after that I saw that they are still available in the sdm. So I undeployed them there also.
    I have restarted the J2ee Engine twice. Maybe I will try to restart the whole windows server...

  • Deployed Webdynpro content

    Hi All,
       i have created one webdynpro iview using NWDS and i deployed through sdm.
       After that i checked under webdynpro--> content administrator and i found the deployed content. Now if i want to find the deployed webdynpro ivew in portal under portal content where i have to find out?
    Thanks and Regards,
    Phanikumar

    Hey Phani,
    You will have to create a JAVA Web Dynpro Iview.
    Please go through this <a href="http://help.sap.com/saphelp_nw70/helpdata/en/11/0d653f0c9fa075e10000000a114084/content.htm">documentation</a>
    Cheers!!
    AShutosh

  • Content administration - webdynpro

    Hi,
    am new to Web dynpro development. so i created a simple helloworld application and am trying to integrate in SAP enterprise portals.. in the documentation, it is mentioned to create a system if the host where the WD applciatin resides is a different machine and specify it as SAP_local_system if it resides on the same system where EP is running.I chose sap_local_system.
    my queries are:
    a) in this scenarion, is SSO really need to be implemented, as it is running on the same WAS as SAP EP?
    b)what can we do in content administration --> webdynpro tab at all?
    c) what does SLD has to do with WD applications?
    please help me.
    regards

    Hi Yogi,
    As far as I know, you only need SSO and SLD for WD apps if they're on different servers and if you're fetching data from R/3 or from some other system. For example, take a look at the pre-requisites to deploying a WD sample application from a tutorial list the following (this WD application is connecting to R/3):
    Prerequisites
    You have made sure that the relevant SAP basis system, which you will be accessing
    remotely to retrieve the flight data, is currently available and contains flight data.
    You have made sure that the SAP J2EE Engine has been launched.
    To do this, refer to Starting and Stopping the SAP J2EE Engine .
    You have checked that the configuration settings for the J2EE server and for the SDM
    server are entered correctly in the Developer Studio.
    To check the server settings, choose the menu path Window ¨ Preferences ¨ SAP
    J2EE Engine.
    The connection parameters for the used SLD are defined in the J2EE Visual
    Administrator.
    The following resource may come in handy:
    http://help.sap.com/saphelp_nw04/helpdata/en/c7/071940a65ec442e10000000a1550b0/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/7e/c82c42be6fde2ce10000000a1550b0/frameset.htm

  • 500 Internal Server Error - Web Dynpro Content Administrator

    500 Internal Server Error - Web Dynpro Content Administrator  
    Any help would be really appreciated...
    I was trying to create/Maintain JCo destions on Web Dynpro Content Administrator caught up with the 500 Internal Server Error
    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).
    For further information about the Web Dynpro error page, error analysis and a description of well-known error situations, see SAP note 1113811.
    Root Cause
    The initial exception that caused the request to fail, was:
    java.lang.NullPointerException
    at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:869)
    at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractSystemLandscapeFactory$1.checkStatus(AbstractSystemLandscapeFactory.java:310)
    at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:483)
    at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.updateJCOClientStatus(JCOConnectionsDetails.java:534)
    at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.addJCOClientToList(JCOConnectionsDetails.java:750)
    ... 73 more

    Possible Reasons:
    1. Some fields for the backend system used to setup the JCO destination are not updated properly (i.e.
    empty) in SLD.
    2. Ensure that the SLD is setup properly. Click on the u201CTest Connectionu201D to check that the SLD is up and running.
    Check section "NullPointerException in the trace when maintaining JCO destinations" in below SDN document:
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f3f93ee7-0c01-0010-2593-d7c28b5377c2 (Adaptive RFC- Troubleshooting Guide)
    Edited by: Anagha Jawalekar on Jun 25, 2009 9:11 AM

Maybe you are looking for