Portal Service running status

Hi,
I have deployed one portal service. After that I would like to know whether the deployed portal service is running or not.
Please let me know if any one knows.
Thanks

Dear Tatayya:
You can check your Portal Service running status in Service Configuration.
System Administration->System Configuration->Service Configuration got to your Application. Right chick and selection Administration. You can check it and Change its status.
Xiaoming Liu

Similar Messages

  • IChat server admin Service Running, status not available

    X-Serve running 10.6.8
    I noticed the other day thaat when I look at the iChat service in Server Admin, I observed the following:
    iChat service is: Running
    Start Time: Not Available
    Domain: Not Available
    Client Connections: Not Available
    The log screen says No Log Files exist
    I have seen similar screens when there was a slight lag in server admin gathering information to display on screen.  This stays this way indefinately.  The service is working as far as I can tell, IE people can log in, add each other, and chat.  A log file is in fact being used and updated (/var/jabberd/message_archive/)
    I noticed this because I was trying to autobuddy.sh, I script I use often to update when I add new users to the organization so they show up in everyones group list.  I attempted to stop the service from the command line using:
    #:serveradmin stop jabber
    #:jabber: state = RUNNING
    and was never able to stop iChat.  The system behaves the same after a reboot.  I am not sure what to do, or what the actual problem is.  The only thing besides a reboot that I tried was a permission repair from within the OS.
    In the log below I removed some user specific information because they are user names for users on my network.  This server and service is internal only.
    the console logs I have this:
    Nov 30 10:29:55 aphrodite jabberd/router[353]: message_log received a message with empty body
    Nov 30 10:30:15: --- last message repeated 2 times ---
    Nov 30 10:30:19 aphrodite jabberd/router[353]: message_log received a message with empty body
    Nov 30 10:31:05 aphrodite jabberd/router[353]: message_log received a message with empty body
    Nov 30 10:49:17 aphrodite com.mycompany.autobuddy[83710]: /usr/local/Scripts/auto_buddy.sh: line 2: /usr/sbin/jabber_autobuddy: No such file or directory
    Nov 30 11:12:34 aphrodite jabberd/c2s[354]: od_auth_check_service_membership: mbr_check_service_membership returned 2
    Nov 30 11:12:34 aphrodite jabberd/c2s[354]: od_auth_check_service_membership: no access restrictions found
    Nov 30 11:19:17 aphrodite com.mycompany.autobuddy[87010]: /usr/local/Scripts/auto_buddy.sh: line 2: /usr/sbin/jabber_autobuddy: No such file or directory
    Nov 30 11:49:17 aphrodite com.mycompany.autobuddy[90323]: /usr/local/Scripts/auto_buddy.sh: line 2: /usr/sbin/jabber_autobuddy: No such file or directory
    Nov 30 11:54:37 aphrodite jabberd/c2s[354]: od_auth_check_service_membership: checking user "jimrumrillcotaoilcom" access for service "chat"
    Nov 30 11:54:37 aphrodite jabberd/c2s[354]: od_auth_check_service_membership: mbr_check_service_membership returned 2
    Nov 30 11:54:37 aphrodite jabberd/c2s[354]: od_auth_check_service_membership: no access restrictions found
    Nov 30 12:03:14 aphrodite jabberd/c2s[354]: od_auth_check_service_membership: mbr_check_service_membership returned 2
    Nov 30 12:03:14 aphrodite jabberd/c2s[354]: od_auth_check_service_membership: no access restrictions found
    Nov 30 12:03:32 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:04:26: --- last message repeated 2 times ---
    Nov 30 12:05:25 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:06:26: --- last message repeated 1 time ---
    Nov 30 12:06:26 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:06:57: --- last message repeated 1 time ---
    Nov 30 12:07:27 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:08:28: --- last message repeated 1 time ---
    Nov 30 12:08:28 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:09:26: --- last message repeated 1 time ---
    Nov 30 12:09:29 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:09:59: --- last message repeated 1 time ---
    Nov 30 12:10:30 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:11:30: --- last message repeated 1 time ---
    Nov 30 12:11:30 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:12:00: --- last message repeated 1 time ---
    Nov 30 12:12:31 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:13:32: --- last message repeated 1 time ---
    Nov 30 12:13:32 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:14:26: --- last message repeated 1 time ---
    Nov 30 12:14:33 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:15:34: --- last message repeated 1 time ---
    Nov 30 12:15:34 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:16:35: --- last message repeated 1 time ---
    Nov 30 12:16:35 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:17:05: --- last message repeated 1 time ---
    Nov 30 12:17:36 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:18:37: --- last message repeated 1 time ---
    Nov 30 12:18:37 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:19:17: --- last message repeated 1 time ---
    Nov 30 12:19:17 aphrodite com.mycompany.autobuddy[94140]: /usr/local/Scripts/auto_buddy.sh: line 2: /usr/sbin/jabber_autobuddy: No such file or directory
    Nov 30 12:19:38 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:19:53: --- last message repeated 1 time ---
    Nov 30 12:20:39 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:20:45: --- last message repeated 1 time ---
    Nov 30 12:21:40 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:22:10: --- last message repeated 1 time ---
    Nov 30 12:22:41 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:22:47: --- last message repeated 1 time ---
    Nov 30 12:23:42 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:24:26: --- last message repeated 1 time ---
    Nov 30 12:24:43 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:25:10: --- last message repeated 1 time ---
    Nov 30 12:25:44 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:26:45: --- last message repeated 1 time ---
    Nov 30 12:26:45 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:27:16: --- last message repeated 1 time ---
    Nov 30 12:28:24 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:29:00: --- last message repeated 3 times ---
    Nov 30 12:29:00 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Any help on what might be going on or a push in a direction would be greatly appreciated.
    Thanks!

    Well I searched the forums here and I found some similar issues, however the fix's I was directed too did not resolve the problem. 
    I did notice this today after reading a post regarding the use of the .local domain name, and fixing that fixes this issue:
    When i selected my server on the left hand side of server admin, click on settings at the top (the gear) then on Network, I see:
    Ethernet 1 (eth0) IPv4 192.1.1.4 Aphrodite.local
    I am not sure where the .local is coming from.  This is an internal server and has been configured with a FQDN for 2 years now, aphrodite.cotaoil.net.  On the server, the only other place I see the .local, is in system preferences, sharing, at the top it has my fqdn, but when I click on edit, it has a local host field that says Aphrodite, with a .local greyed out after, or ghosted.
    When I use the command changeip -checkhostname I recieve:
    changeip -checkhostname
    Primary address     = 192.1.1.4
    Current HostName    = aphrodite.cotaoil.net
    The DNS hostname is not available, please repair DNS and re-run this tool.
    dirserv:success = "success"
    the hostname not available message is new (well I know at some point in the not too distant past I did not have this message) so I am not sure if an update broke this or not but basically I am not sure where to go from here.
    The DNS settings are set the same as they were when I originally set up the server.  Reviewing DNS logs, I do not see anything abnormal.
    additionally when I run scutil i get:
    aphrodite:~ root# scutil --get LocalHostName
    Aphrodite
    aphrodite:~ root# scutil --get ComputerName
    Aphrodite.cotaoil.net
    I am a little stumped as to where to go from here.  I believe based on some other posts Ive read that this may have something to do with why I cannot see any iChat status and am recieving the dreaded "detailed service status not available until network configuration completed"
    Thanks for any and all thoughts.  Currently reviewing Hoffs tutorials, but I used combined Hoff tutorials and apple server guides when originally set up the server.  Please let me know what I did wrong (besides my internal IP range)

  • Portal service listner

    Hi All
    I have created a portal service that listens for a RFC i have created. Everything was working fine until i changed the structure of the RFC. Now when i run the RFC the portal service runs correctly however the values that are passed from my bapi table to my JCO table are different. (i.e. some values are truncated and not in the correct columns.)
    I think this may have something to do with my jco meta data but i dont know how to change it. Can anyone give me some advise please?
    Many thanks
    Calvin

    Thanks for your responses. I have gone through the threads.  Need your help...
    My portalapp.xml is given below
    <?xml version="1.0" encoding="UTF-8"?>
    <application>
      <application-config>
        <property name="startup" value="true"/>
        <property name="Vendor" value="apl.com"/>
      </application-config>
      <components>
        <component name="SnowComponent">
          <component-config>
            <property name="ClassName" value="com.sap.portal.tutorial.snow.SnowComponent"/>
          </component-config>
          <component-profile/>
        </component>
      </components>
      <services>
        <service name="SnowService" >
          <service-config>
            <property name="className" value="com.sap.portal.tutorial.service.SnowService"/>
            <property name="startup" value="true"/>
          </service-config>
          <service-profile>
            <property name="MyProperty " value="true"/>
          </service-profile>
        </service>
      </services>
    </application>
    When I deploy the par with the above portalapp.xml  I am able to start the service.  I do not have any issue in starting the service.
    Now, I want to use the said service from my Portal Component - SnowComponent which is in the same appp
    what chagnes i will have to make in my portalapp.xml ?
    pls. also provide the details pertaining to accessing this service from other portal apps too :
    is it somthing related to application config ?
    <application-config>
    <property name="SharingReference" value="SnowComponent">
    <application-config>
    do i have to import jar for the following interface declartion ?
    import com.sap.portal.tutorial.service.ISnowService ;
    ISnowService snowService = (ISnowService) request.getService(ISnowService.KEY);
    i hope the above is clear.
    pls. help .......

  • Custom portal service not running ni NW 04

    Hello!
    We are about to migrate from EP6 SP2 to NW04 and I'm currently testing the results of the first test run.
    One special problem I encountered is one of my custom portal services no longer running. It did without flaws back in EP6, so something seems to have changed.
    My Service interface:
    [code]
    package com.rag.ekportal.bginfocenter.kmservice;
    @author Juergen Wahlmann
    public interface IBGFetcher extends IService {
    [/code]
    And the implementation:
    [code]
    package com.rag.ekportal.bginfocenter.kmservice;
    public class BGFetcher implements IBGFetcher, Runnable {
    [/code]
    portalapp.xml
    [code]
    <?xml version="1.0"  encoding="UTF-8"?>
         <application>
              <application-config>
              </application-config>
              <components>
                   <component name="BGViewer">
                        <component-config>
                             <property name="ClassName" value="com.rag.ekportal.bginfocenter.bgview.control.BGViewer">
                             </property>
                             <property name="SecurityZone" value="sbi-ruhr.de/ekportal/medium_safety/com.rag.ekportal/components/bgviewer">
                             </property>
                             <property name="ResourceBundleName" value="bginfocenter">
                             </property>
                             <property name="ServicesReference" value="usermanagement,knowledgemanagement,com.rag.ekportal.bginfocenter.kmservice.BGFetcher,com.sap.portal.ivs.connectorservice,landscape">
                             </property>
                        </component-config>
                        <component-profile>
                             <property name="tagLib" value="/SERVICE/htmlb/taglib/htmlb.tld">
                                  <property name="personalization" value="none">
                                  </property>
                             </property>
                             <property name="templatesfolderName" value="Vorlagen">
                             </property>
                             <property name="guidelinesfolderName" value="Richtlinien">
                             </property>
                             <property name="bgContactsfolderName" value="BG-Ansprechpartner">
                             </property>
                             <property name="ksb2folderName" value="KSB 2">
                             </property>
                             <property name="bgControllingfolderName" value="BG-Controlling">
                             </property>
                             <property name="rvURL" value="/irj/servlet/prt/portal/prtroot/pcd!3aportal_content!2fcom.fo.admin!2fcom.admin.fo.iview!2fcom.admin.iview.fo.ri!2fcom.admin.iview.ri.fo.rag!2fcom.admin.iview.ri.rag.iv.begis_0_0?numberBG=">
                             </property>
                             <property name="KmServiceUser" value="KM Service User">
                             </property>
                             <property name="systemAlias" value="BeGIS_RV_DB">
                             <property name="personalization" value="admin"/>
                             <property name="plainDescription" value="JDBC System object for DB access"/>                         
                        </property>
                        <property name="table" value="janus_contract_bg_v">
                             <property name="personalization" value="admin"/>
                             <property name="plainDescription" value="Database View for reading contracts"/>                         
                        </property>
                        <property name="table1" value="user_roles_v">
                             <property name="personalization" value="admin"/>
                             <property name="plainDescription" value="Database Table for checking user role in RV DB"/>                         
                        </property>
                        </component-profile>
                   </component>
              </components>
              <services>
                   <service name="BGFetcher">
                        <service-config>
                             <property name="className" value="com.rag.ekportal.bginfocenter.kmservice.BGFetcher">
                             </property>
                             <property name="startup" value="true">
                             </property>
                             <property name="SecurityZone" value="sbi-ruhr.de/ekportal/medium_safety/com.rag.ekportal/services/bgfetcher">
                             </property>
                        </service-config>
                        <service-profile>
                             <property name="interval" value="300000">
                             </property>
                             <property name="enable" value="false">
                                  <property name="type" value="boolean">
                                  </property>
                             </property>
                             <property name="numberofruns" value="1">
                             </property>
                             <property name="repository" value="/rag_bgm_test/Beschaffungsgruppen">
                             </property>
                             <property name="KmServiceUser" value="KM Service User">
                             </property>
                             <property name="dbServer" value="xxx">
                             </property>
                             <property name="dbUser" value="xxx">
                             </property>
                             <property name="dbPassword" value="xxx">
                             </property>
                             <property name="dbName" value="xxx">
                             </property>
                             <property name="workfolderName" value="Arbeitsordner">
                             </property>
                             <property name="teamfolderName" value="Teamordner">
                             </property>
                             <property name="contactfolderName" value="Ansprechpartner">
                             </property>
                             <property name="publicfolderName" value="u00D6ffentlicher Ordner">
                             </property>
                             <property name="deletedfolderName" value="/rag_bgm_test/Gelu00F6scht/">
                             </property>
                        </service-profile>
                   </service>
              </services>
         </application>
    [/code]
    The service didn't work after the migration, so I tried to deploy it again. This is the result:
    [code]
    Date : 01/12/2006
    Time : 13:31:37:880
    Message : [PortalServiceItem.startServices] service initialisation failed:com.rag.ekportal.bginfocenter.kmservice|BGFetcher
    [EXCEPTION]
    java.lang.NoClassDefFoundError: com/sapportals/wcm/repository/ResourceException
         at java.lang.Class.forName0(Native Method)
         at java.lang.Class.forName(Class.java:219)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.__createServiceInstance(PortalServiceItem.java:727)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.createServiceInstance(PortalServiceItem.java:613)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.startServices(PortalServiceItem.java:1042)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startLoadOnStartupServices(PortalAppBroker.java:1563)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.start(PortalAppBroker.java:1518)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.restartQueuedApplication(PortalAppBroker.java:1866)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.updateApplications(PortalAppBroker.java:1702)
         at com.sapportals.portal.prt.deployment.DeploymentManager.updateApplications(DeploymentManager.java:1754)
         at com.sap.ip.portal.admin.portalanywhere.QueryHandler.handleTopic(QueryHandler.java:152)
         at com.sapportals.portal.prt.service.notification.impl.NotificationSAPJ2EE630.executeActionHandleTopic(NotificationSAPJ2EE630.java:1141)
         at com.sapportals.portal.prt.service.notification.impl.NotificationSAPJ2EE630.notifyActionSubscribers(NotificationSAPJ2EE630.java:1089)
         at com.sapportals.portal.prt.service.notification.impl.NotificationSAPJ2EE630.receiveWait(NotificationSAPJ2EE630.java:386)
         at com.sapportals.portal.prt.service.notification.impl.NotificationSAPJ2EE630.broadcastAndWait(NotificationSAPJ2EE630.java:553)
         at com.sapportals.portal.prt.service.notification.NotificationServiceDispatcher.broadcastAndWait(NotificationServiceDispatcher.java:192)
         at com.sap.ip.portal.admin.portalanywhere.EventForwarder.sendQueryAndGetResults(EventForwarder.java:122)
         at com.sap.ip.portal.admin.portalanywhere.EventForwarder.sendQueryToAllServers(EventForwarder.java:144)
         at com.sap.ip.portal.admin.portalanywhere.EventForwarder.forwardEventToAllServers(EventForwarder.java:135)
         at com.sap.ip.portal.admin.portalanywhere.ArchiveUploader.forwardUpdateToAllServers(ArchiveUploader.java:253)
         at com.sap.ip.portal.admin.portalanywhere.ArchiveUploader.doContent(ArchiveUploader.java:235)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
         at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
         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:95)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160)
    Severity : Error
    Category : /System/Server
    Location : com.sap.portal.prt.runtime.broker
    Application : sap.com/irj
    Thread : SAPEngine_Application_Thread[impl:3]_15
    Datasource : 2390950:E:\usr\sap\PMT\JC00\j2ee\cluster\server0\log\defaultTrace.trc
    Message ID : 000C29A5B62A00400000001300000A4000040A2887A939D9
    Source Name : com.sap.portal.prt.runtime.broker
    Argument Objs : java.lang.NoClassDefFoundError: com/sapportals/wcm/repository/ResourceException
         at java.lang.Class.forName0(Native Method)
         at java.lang.Class.forName(Class.java:219)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.__createServiceInstance(PortalServiceItem.java:727)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.createServiceInstance(PortalServiceItem.java:613)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.startServices(PortalServiceItem.java:1042)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startLoadOnStartupServices(PortalAppBroker.java:1563)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.start(PortalAppBroker.java:1518)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.restartQueuedApplication(PortalAppBroker.java:1866)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.updateApplications(PortalAppBroker.java:1702)
         at com.sapportals.portal.prt.deployment.DeploymentManager.updateApplications(DeploymentManager.java:1754)
         at com.sap.ip.portal.admin.portalanywhere.QueryHandler.handleTopic(QueryHandler.java:152)
         at com.sapportals.portal.prt.service.notification.impl.NotificationSAPJ2EE630.executeActionHandleTopic(NotificationSAPJ2EE630.java:1141)
         at com.sapportals.portal.prt.service.notification.impl.NotificationSAPJ2EE630.notifyActionSubscribers(NotificationSAPJ2EE630.java:1089)
         at com.sapportals.portal.prt.service.notification.impl.NotificationSAPJ2EE630.receiveWait(NotificationSAPJ2EE630.java:386)
         at com.sapportals.portal.prt.service.notification.impl.NotificationSAPJ2EE630.broadcastAndWait(NotificationSAPJ2EE630.java:553)
         at com.sapportals.portal.prt.service.notification.NotificationServiceDispatcher.broadcastAndWait(NotificationServiceDispatcher.java:192)
         at com.sap.ip.portal.admin.portalanywhere.EventForwarder.sendQueryAndGetResults(EventForwarder.java:122)
         at com.sap.ip.portal.admin.portalanywhere.EventForwarder.sendQueryToAllServers(EventForwarder.java:144)
         at com.sap.ip.portal.admin.portalanywhere.EventForwarder.forwardEventToAllServers(EventForwarder.java:135)
         at com.sap.ip.portal.admin.portalanywhere.ArchiveUploader.forwardUpdateToAllServers(ArchiveUploader.java:253)
         at com.sap.ip.portal.admin.portalanywhere.ArchiveUploader.doContent(ArchiveUploader.java:235)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
         at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
         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:95)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160)
    Arguments : java.lang.NoClassDefFoundError: com/sapportals/wcm/repository/ResourceException
         at java.lang.Class.forName0(Native Method)
         at java.lang.Class.forName(Class.java:219)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.__createServiceInstance(PortalServiceItem.java:727)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.createServiceInstance(PortalServiceItem.java:613)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.startServices(PortalServiceItem.java:1042)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startLoadOnStartupServices(PortalAppBroker.java:1563)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.start(PortalAppBroker.java:1518)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.restartQueuedApplication(PortalAppBroker.java:1866)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.updateApplications(PortalAppBroker.java:1702)
         at com.sapportals.portal.prt.deployment.DeploymentManager.updateApplications(DeploymentManager.java:1754)
         at com.sap.ip.portal.admin.portalanywhere.QueryHandler.handleTopic(QueryHandler.java:152)
         at com.sapportals.portal.prt.service.notification.impl.NotificationSAPJ2EE630.executeActionHandleTopic(NotificationSAPJ2EE630.java:1141)
         at com.sapportals.portal.prt.service.notification.impl.NotificationSAPJ2EE630.notifyActionSubscribers(NotificationSAPJ2EE630.java:1089)
         at com.sapportals.portal.prt.service.notification.impl.NotificationSAPJ2EE630.receiveWait(NotificationSAPJ2EE630.java:386)
         at com.sapportals.portal.prt.service.notification.impl.NotificationSAPJ2EE630.broadcastAndWait(NotificationSAPJ2EE630.java:553)
         at com.sapportals.portal.prt.service.notification.NotificationServiceDispatcher.broadcastAndWait(NotificationServiceDispatcher.java:192)
         at com.sap.ip.portal.admin.portalanywhere.EventForwarder.sendQueryAndGetResults(EventForwarder.java:122)
         at com.sap.ip.portal.admin.portalanywhere.EventForwarder.sendQueryToAllServers(EventForwarder.java:144)
         at com.sap.ip.portal.admin.portalanywhere.EventForwarder.forwardEventToAllServers(EventForwarder.java:135)
         at com.sap.ip.portal.admin.portalanywhere.ArchiveUploader.forwardUpdateToAllServers(ArchiveUploader.java:253)
         at com.sap.ip.portal.admin.portalanywhere.ArchiveUploader.doContent(ArchiveUploader.java:235)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
         at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
         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:95)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160)
    Dsr Component :
    Dsr Transaction : 5f940fe0836711da887d000c29a5b62a
    Dsr User :
    Indent : 0
    Level : 0
    Message Code :
    Message Type : 1
    Relatives : /System/Server
    Resource Bundlename :
    Session : 2391
    Source : com.sap.portal.prt.runtime.broker
    ThreadObject : SAPEngine_Application_Thread[impl:3]_15
    Transaction :
    User : xxx
    [/code]
    Looks like something is wrong in the service definition (portalapp.xml) but I have no clue. Class names are spelled right, settings the same as in EP6 SP2, yet the portal engine is not able to find the implementation class of the service.
    Any ideas?
    Cheers,
      Juergen

    Hi Detlev!
    The ServiceReference definition previously was located in the application config under SP2, but didn't work either.
    Now I found the solution. A sharing reference of all non-custom services in the application config and an additional sharing reference to my custom service in the portal application's config like this:
              <application-config>
                   <property name="SharingReference" value="usermanagement,knowledgemanagement,com.sap.portal.ivs.connectorservice,landscape">
                   </property>
              </application-config>
              <components>
                   <component name="BGViewer">
                        <component-config>
                             <property name="ClassName" value="com.rag.ekportal.bginfocenter.bgview.control.BGViewer">
                             </property>
                             <property name="SecurityZone" value="sbi-ruhr.de/ekportal/medium_safety/com.rag.ekportal/components/bgviewer">
                             </property>
                             <property name="ResourceBundleName" value="bginfocenter">
                             </property>
                             <property name="SharingReference" value="com.rag.ekportal.bginfocenter.KMService.BGFetcher">
                             </property>
                        </component-config>
    Case closed, thx for you hint. I awarded points.
    Cheers,
      Jürgen
    Message was edited by: Juergen Wahlmann, solution included

  • How to check that my portal service is running

    Hi,
    Do you know some admin application in portal which show all services that are running
    I created a simple portal service and when I try to get it with this code:
       public void doContent(IPortalComponentRequest request, IPortalComponentResponse response)
        try {
          response.write("!!!BEGIN OF TEST<br/>");
          String srvID = IPCDProvider.KEY;
          IPCDProvider service = (IPCDProvider)
              PortalRuntime.getRuntimeResources().getService(srvID);
          response.write("<p>Name = " + service.getKey()); 
        } catch (Exception e) {
          // TODO: handle exception
          response.write("END WITH ERROR!!!<br/><br/>");
          response.write("ERROR:::" + e);
    I receive error : ERROR:::com.sapportals.portal.prt.service.ServiceException: Service not found: pcd.PCDProvider
    I want to check that my service is deployed and running

    Yes I saw (under System Admin -> Support -> Portal Runtime -> Application Console) that my service is started
    But I receive error when I try getService method
          String srvID = "tc.lm.ctc.cpa.pcd_sda";
          IPCDProvider service = (IPCDProvider)
              PortalRuntime.getRuntimeResources().getService(srvID);
    This is portalapp.xml of my testing application
    <?xml version="1.0" encoding="utf-8"?>
    <application alias="ShowPCDConfigData">
      <application-config>
        <property name="PrivateSharingReference" value="com.sap.portal.pcd.glservice,tc.lm.ctc.cpa.pcd_sda"/>
      </application-config>
      <components>
        <component name="Test">
          <component-config>
            <property name="ClassName" value="com.sap.tc.lm.ctc.cpa.pcd.test.Test"/>
          </component-config>
          <component-profile/>
        </component>
      </components>
      <services/>
    </application>
    This is a portalapp.xml of my portal application  that expose servise (that I am tring to get)
    <?xml version="1.0" encoding="utf-8"?>
    <application alias="PCDProviderService">
      <application-config>
        <property name="PrivateSharingReference" value="com.sap.portal.pcd.glservice"/>
      </application-config>
      <components/>
      <services>
        <service name="PCDProvider">
          <service-config>
            <property name="className" value="com.sap.lm.ctc.cpa.pcd.service.PCDProvider"/>
            <property name="startup" value="true"/>
          </service-config>
        </service>
      </services>
    </application>
    Could you help me, please

  • Explicit running of a scheduled portal service.

    Hi all, I have created a portal service that is scheduled. I have added the following to the run() method System.out.println(“Service is running”).
    In the component monitor the service indicator is green and running.
    Please, can anyone let me know how I can force this run method to run on command or how to debug this portal service. I am just trying to find out when this method is called. So I can see that it is running on the right times.
    Is it first called on load i.e. on start of the J2ee portal.  
    Thanks in advance

    Hi,
    Can you check up if this is located in the following path.
    System Administration ->Support->Portal Runtime
    Here navigate to ROOT/WEB-INF/portal/portalapps
    Open the folder with the name of the par file and check up if you can locate the jar.
    Regards,
    Harish
    (Please award points in case this helps)

  • Refer Portal service in EP7.3

    Hello all,
    step 1 : migrated  Portal service par 7.0 to 7.3 Dc  (susezp/scsusezp/dc_portalservice_ear) by using Portal Dcs under track added required code.
    step2 :migrated  portal component par 7.0 to 7.3 Dc  (susezp/scsusezp/dc_s2p_announcement_ear) by using Portal Dcs under track added required code.
    portal service DC  added under dependencies of portal component DC.
    now  i have deployed portal component getting below error :
    Caused by: com.sap.engine.services.servlets_jsp.server.deploy.impl.exceptions.WCEApplicationNotStartedException: The application [pg.com/susezp~scsusezp~dc_s2p_announcement_ear] is configured to have ALWAYS start up mode. Currently it is in STOPPED status - because of this it will not be started implicitly by the Web Container service and any internal operation that needed this application to be running will fail. The reason for STOPPED status is because the application failed to start during cluster startup. The error is: 5625350
    startApp
    2
    Application pg.com/susezp~scsusezp~dc_s2p_announcement_ear cannot be started. Reason: it has hard reference to the following resources, which are currently not available on the system: hard to SAPPORTAL/pg_portal_service_ear (public) (f=true, cl=true); .
    In order to start the application, components that provide the missing resources should be successfully deployed.
    it is showing portal service in stopped but if saw in NWA  java application  portal service is showing status as started.

    Is the reference you are using (SAPPORTAL/pg_portal_service_ear) right for sure? It looks your service has another one, since EP cant find it
    cheers

  • CCP 9.4 - Service Link Status

    Hello there,
    I recently configured CCP 9.4 on our lab.
    I was able to connect to CCP portal successfully with domain name and checked the Service Link status was green, but when i change the domain name to WORKGROUP after that i didn't get the Service Link status green and it was red.
    So, i checked on log file and i also saw error message on running Jboss server regarding to unable to connect with this error :
    " Unable to connect to 'http://abc.xyz.com:8080/Integration
    ver/ISAdminServlet?action=iseeConnectionStatus&ObjectInstId=0': java.net.UnknownHostException: abc.xyz.com01519689514078465::***Error::CommunicationsBase: Unable to connect to 'http://abc.xyz.com:8080/Integration
    ver/ISAdminServlet?action=iseeConnectionStatus&ObjectInstId=0': java.net.UnknownHostException: abc.xyz.com "
    here, abc=my hostname , xyz.com=domain name
    so, to change this "abc.xyz.com" to "abc" because now my server was under WORKGROUP, what file i need to edit. So, i will get green status of Service Link.
    I also attach the images of the error.
    I appreciate you direction.
    Regards,
    Krupesh

    Hi Lim,
    It isn't clear from you description what the problem is.  Can you contact TAC and provide the details?
    Thanks.

  • Error during startup of portal service after SPS11

    Hi Guys,
    After installation of SPS11 to our 2004s portal system we have problem with startup of our Portal service.
    Before SPS11 we had SPS9 system and everything was working correctly.
    Our service is connecting to Database during its initialization.
    This is part of our code:
    Properties p = new Properties();
    p.put("java.naming.factory.initial", "com.sap.engine.services.jndi.InitialContextFactoryImpl");
    try
         Context ctx = new InitialContext(p);
         _ds = (DataSource)ctx.lookup(POOLNAME);
         Connection conn = _ds.getConnection();
         conn.close();
         LogWriter.traceInfo(LogWrapper.trace,"Connection established.");
    } catch (NamingException ex)
    The error is:
    #1.5#000802A2BF4A00580000038200003E3000042C1F016BDC9A#1174411586934#System.err#sap.com/irj#System.err#Guest#2####a813ff20d70611dbbcd7000802a2bf4a#SAPEngine_Application_Thread[impl:3]_27##0#0#Error##Plain###com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of SABMILLER.
         at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:649)
         at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:344)
         at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:254)
         at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:271)
         at javax.naming.InitialContext.lookup(InitialContext.java:347)
         at javax.naming.InitialContext.lookup(InitialContext.java:347)
         at cz.sap.statemanagement.StateLogRetriever.<init>(StateLogRetriever.java:73)
    The probleam appears only during startup of portal!
    If you deploy service on running portal it is started without any problems.
    We tried to apply note (Note 960199 - 2-Phase Init Mechanism for Portal Services is Deprecated) but without success.
    This is modification of our portalapps.xml as described in Note.
        <service name="StatemanagementLogService">
          <service-config>
            <property name="className" value="cz.sap.statemanagement.StatemanagementLogService"/>
            <property name="startup" value="true"/>
            <property name="twophaseinit" value="always"/>
          </service-config>
    Please could you help us with this problem?
    Anyone has an idea what is wrong?
    Thanks a lot
    Ondrej

    Hi Nirmal,
    thanks you for your quick response. This is what the installer returns when I use your suggested command:
    Mar 7, 2012 2:35:56 PM [Error]: The parameter jce_policy_zip in externally supplied configuration is invalid.
    I looked up the parameters for the STARTUP:
    rootdir [guiport] [httpport] [guistart] [guimode] [config] [sid] [instanceNr]
    Thus the jce_policy_zip is not a valid parameter.
    However, after deleting the file specified I could just run STARTUP again and this worked.
    Thanks
    Marcel
    Edited by: M. Rabe on Mar 7, 2012 2:57 PM

  • Consuming a webservice from a portal service...

    Hello all,
    I am playing around with the example code for imlimenting a federated search (found in the km section) and was trying to use a webservice call to google as an example of a the federated search.
    I generated a client side portal service (from the goodle wsdl) and I am now trying to access it form the search virtual index service I wrote...
    I someone can point me in the correct direction that would be great... I was looking at the following blog Accessing an External Web Services in Portal which helped setup the webservice but I find the code used to access it does not help. For one thing I can not find the IServiceName class anywhere in the portal or j2ee javadoc or jat files.
    Cheers,
    D.

    Hi ,
    I am getting the problems while consuming the web services in portal component.
    I am not able to call the methods of web services.
    look at my code.
    IListServiceName client=
    (IListServiceName) PortalRuntime.getRuntimeResources ().getService (IListServiceName.KEY);
         GetListResponse glr= client.getList();
    frist line is working fine.
    In my web service i have a method called GetList().
    Any way i have to call that method and get the result.
    But there are other classes which are automatically generated when i consumed the web service, like      GetListResponse().
    When i try to call client.GetList(); it gives the error at run time, No error in the code but the errors are coming at run time.
    Where is the problem? other things like proxy settings, etc i have done.
    What could be the problem? Can any one suggest.
    Regards
    Bala

  • SAP Portal - Service Timeout after 30min from ERP Backend

    Hello SCN Members,
    actually i have a problem with our Enterprise Portal. We have some Employee Self Services running in SAP Portal with connection to a SAP ERP ABAP Backend. After 30 minutes of inactivity, the User click to a Service, he became a http/500, connection timeout.
    i found the errormessage in SM21 in ABAP Backend "HTTP/RFC-Session wurde nach Timeout gelöscht" (HTTP Session deleted after timeout)
    at the ABAP Backend i set the ICF Parameters to and restart the whole system (QS):
    icm/server_port[0] = PROT=HTTP, PORT=8080,TIMEOUT=28800
    icm/server_port[1] = PROT=SMTP, PORT=8025
    icm/server_port[2] = PROT=HTTPS,PORT=8083,TIMEOUT=28800
    rdisp/plugin_auto_logout       = 28800
    But the error occurs after 30min, now i have no more idea, which parameters i need to change.
    Can you help me?
    best regards,
    Stefan

    Hi Lawrence,
    thank's for your answer, at the webdispatcher are the settings as follow, but there is still a timeout after 1800 seconds of inactivity
    rdisp/plugin_auto_logout = 0
    and
    icm/server_port_0
    PROT=HTTP,HOST=sapwddev01,PORT=80,TIMEOUT=-1,PROCTIMEOUT=-1
    icm/server_port_1
    PROT=HTTPS,HOST=sapwddev01,PORT=443,TIMEOUT=-1,PROCTIMEOUT=-1

  • Invoking the Portal Service DC from Webdynpro Java DC

    Hi experts,
    I am trying to Call a dc Portal Service from within a Web Dynpro DC
    following the steps I did,
    1. Created a DC "Portal Application Standalone" project by the name "portappstd".
    2. Created a portal service inside "portappstd" dc by the name "DemoPortalService".
    3. Exposed ITestService.class in the public part.
    4 Build and deployed the DC on server!!
    Now..
    5. Created anoter DC of type WebDynPro named "demoportaldc".
    6. Added SAP_JTECHS -> epbc.prtapi._api as a "Used DC" with dependency build time and runtime
    7. Added IDemoPortalService.class from the public part of portal Service as Used DC
    8. Tried to reference the service using the following code..
         IDemoPortalService service=(IDemoPortalService)WDPortalUtils.getServiceReference(IDemoPortalService.KEY);
    9. Build and deployed the DC.
    10. When I run the application I am getting the following error
    Processing HTTP request to servlet dispatcher finished with error.
    The error is:
    application [webdynpro/dispatcher] Processing HTTP request to servlet [dispatcher] finished with error.
    The error is: com.sap.tc.webdynpro.services.sal.core.DispatcherException: Failed to start deployable object com.arteriatech/demoportaldc.
    so, please do the needfull ASAP,..
    Thanks & Regards,
      GAANEE

    Hi...
    Check the following link..
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/ba641aa6-0c01-0010-57ac-c21a4ca7b542
    Regards,
    Alamelu

  • Use of portal service in JAAS Login Module

    Is it possible to use an portal service in an JAAS Login Module?
    I've tried to use the IUserMappingService and always run in an Null Pointer Exception.
    All needed Used DC references are set and the build and the deployment of the
    login module is possible without any errors.
    Best regards,
    Thomas

    I've debuged my JAAS login modul.
    The following objects are in accessable over my context object
    {broker=broker, com.sap.portal.pcm.collaborative.ipartstemplates={}, UME=UME, com.sap.workflow.es.portal.IKMCRoomService=com.sap.workflow.es.room.KMCRoomHelper@44c944c9, comp.sap.portal.fpn.marshallersrepository={com.sapportals.portal.workset=com.sap.portal.fpn.marshal.WorksetMarshaller@7cf07cf0, com.sapportals.portal.rolefolder=com.sap.portal.fpn.marshal.RoleFolderMarshaller@489b489b, com.sapportals.portal.operationmodifier=com.sap.portal.unification.semanticlayer.marshalling.OperationModifierMarshaller@1a1b1a1b, com.sapportals.portal.businessobject=com.sap.portal.unification.semanticlayer.marshalling.BusinessObjectMarshaller@1fc71fc7, com.sapportals.portal.layout=com.sap.portal.fpn.marshal.LayoutMarshaller@454f454f, com.sapportals.portal.role=com.sap.portal.fpn.marshal.RoleMarshaller@590e590e, com.sap.portal.obn.semanticlayer.businessobject.BusinessObject=com.sap.portal.unification.semanticlayer.marshalling.BusinessObjectNYMarshaller@68af68af, com.sap.portal.obn.semanticlayer.operation.IOperation=com.sap.portal.unification.semanticlayer.marshalling.OperationNYMarshaller@4f4a4f4a, com.sap.portal.pcm.admin.PlainFolderConverter=com.sap.portal.fpn.marshal.FolderMarshaller@284a284a, com.sapportals.portal.iview=com.sap.portal.fpn.marshal.IViewMarshaller@7ba37ba3, com.sapportals.portal.page=com.sap.portal.fpn.marshal.PageMarshaller@a100a10, com.sapportals.portal.operation=com.sap.portal.unification.semanticlayer.marshalling.OperationMarshaller@ece0ece}, WP=com.sapportals.portal.prt.core.resource.MultiPropertiesResource@3b213b21, ContentCatalog=ContentCatalog, Navigation=Navigation, PCD=PCD, com.sap.portal.obn=com.sap.portal.obn, com.sap.portal.usermanagement.usermanagement=com.sapportals.portal.prt.service.usermanagement.UserManagementService@60cc60cc, ProductionMode=true, AdHocWorkflowConnector=com.sap.workflow.es.portal.WFEWorkitemProvider@30d630d6, com.sap.ip.bi=com.sap.ip.bi, com.sapportals.portal.pcm.registeredServies=com.sapportals.portal.pcm.registeredServies, UniversalWorklistService=com.sap.netweaver.bc.uwl.core.portal.UWLPortalService@57e957e9, com.sap.portal.appintegrator=com.sap.portal.appintegrator, rtmf_messaging=com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging@41af41af, com.sap.workflow.es.portal.IKMNotificationService=com.sap.workflow.es.portal.KMNotificationService@1daa1daa, com.sap.portal.pcm.collaborative.pagestemplates={}, runtime=runtime, Authenticator=com.sapportals.portal.prt.service.authenticationservice.AuthenticationService@756f756f, com.sap.workflow.es.portal.IKMAttachmentService=com.sap.workflow.es.portal.KMAttachmentService@9750975, unification=unification}
    The IUserMappingService is missing.  Any ideas?
    Best regards,
    Thomas

  • How to make use of Portal service in the web dynpro application

    hi
    I have some portal service and how to use that in the web dynpro application.
    and also what is the main diff between Portal Component and web dynpro application.
    do we required portal to run web dynpro application.
    thanks
    mmukesh

    Hi,
    >> I have some portal service and how to use that in the web dynpro application.
    Yes. U can use Portal service in webdynpro. Check the link given by subathra.
    >> and also what is the main diff between Portal Component and web dynpro application
    Portal Components are components designed to run in portal server while webdynpro application can run in J2EE WebAS.
    >> do we required portal to run web dynpro application.
    No for general cases. Just WebAS is sufficient to run webdynpro appl. But if u use portal service in ur webdynpro appl, then make sure both (portal service and webdynpro appl) run on same J2EE engine. That is mandatory.
    Regards,
    Vijai

  • IWAB0014E Unexpected exception - Exposing Portal Services as Web Services

    Hi!
    I try to expose a Portal Service as a Web Service:
    [Exposing Portal Services as Web Services |http://help.sap.com/saphelp_nw72/helpdata/en/49/e44e702784751be10000000a42189b/frameset.htm]
    While using the wizard the following exception is rising:
    IWAB0014E Unexpected exception occurred.
          java.lang.IllegalArgumentException
          at org.eclipse.wst.server.core.internal.facets.FacetUtil.getRuntime(FacetUtil.java:89)
          at org.eclipse.jst.server.core.FacetUtil.getRuntime(FacetUtil.java:59)
          at org.eclipse.jst.ws.internal.consumption.command.common.CreateFacetedProjectCommand.setFacetRuntime(CreateFacetedProjectCommand.java:283)
          at org.eclipse.jst.ws.internal.consumption.command.common.CreateFacetedProjectCommand.getFacetsToAdd(CreateFacetedProjectCommand.java:219)
          at org.eclipse.jst.ws.internal.consumption.command.common.CreateFacetedProjectCommand.execute(CreateFacetedProjectCommand.java:115)
          at org.eclipse.jst.ws.internal.creation.ui.extension.PreServiceDevelopCommand.execute(PreServiceDevelopCommand.java:191)
          at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.runCommand(CommandFragmentEngine.java:419)
          at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.visitTop(CommandFragmentEngine.java:359)
          at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.moveForwardToNextStop(CommandFragmentEngine.java:254)
          at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager$6.run(SimpleCommandEngineManager.java:294)
          at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464)
          at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372)
          at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:934)
          at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager.runForwardToNextStop(SimpleCommandEngineManager.java:264)
          at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.runForwardToNextStop(WizardPageManager.java:91)
          at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.getNextPage(WizardPageManager.java:154)
          at org.eclipse.wst.command.internal.env.ui.widgets.SimpleWizardPage.getNextPage(SimpleWizardPage.java:136)
          at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:813)
          at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:369)
          at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
          at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228)
          at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
          at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003)
          at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3823)
          at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3422)
          at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
          at org.eclipse.jface.window.Window.open(Window.java:801)
          at org.eclipse.wst.command.internal.env.ui.widgets.popup.DynamicPopupWizard.run(DynamicPopupWizard.java:130)
          at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251)
          at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:583)
          at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:500)
          at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
          at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
          at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003)
          at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3823)
          at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3422)
          at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2384)
          at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2348)
          at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2200)
          at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:495)
          at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288)
          at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:490)
          at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
          at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
          at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193)
          at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
          at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
          at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:386)
          at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
          at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
          at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
          at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
          at java.lang.reflect.Method.invoke(Method.java:597)
          at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549)
          at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
          at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
    Has anybody an idea, or can tell me another way to do for NW 7.2?
    Thanks Daniel

    Hi Ankur,
    Please go through the below link please. It may be helpful.
    Eclipse WTP Tutorials - Creating Bottom Up Web Service via Apache Axis2
    Thanks,
    Hamendra

Maybe you are looking for