Restart programmaticaly portal service in a cluster

Hello,
Is it possible to restart services programaticaly in a cluster environment from one iView?
Any help will be appreciate.
thanks.
Pino.

Hi,
You might be able to achive this by reverse engineering the code of com.sap.portal.runtime.system.console  (application under system admin->support which allows you to restart services)
See the following folder and decompile the java sources with JAD or similar
C:\usr\sap\<SID>JC00\j2ee\cluster\server0\src\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\com.sap.portal.runtime.system.console
Regards
Dagfinn

Similar Messages

  • How to stop and start (restart) portal services programmatically?

    Hi experts,
    I develop a portal service IMaintenanceService extending IService.
    The new service has some profile properties (start date, end end, etc.).
    I wrote another portal application MaintenanceManager which can change these profile properties.
    However, to activate the changes I have to restart the portal service.
    Does anyone know how I can restart the portal service IMaintenanceService from my portal application MaintenanceManager?
    Thanks for help.
    Edited by: Daniel Fötsch on Nov 21, 2011 8:24 AM

    please see the metalink note
    How to Start/Stop MWA Services Using Control Scripts adstrtal.sh/adstpall.sh? [ID 731320.1]
    This is how i startup and shutdown WMA
    for stopping :
    1) login to Applications tier
    2) To see if the MWA (telnet) server is running use:
    ps -ef|grep DPID
    3) cd $MWA_TOP/bin
    3) ./mwactl.sh -login sysadmin/xxxxx stop_force 10200;
    4) check the wma process from OS level
    ps -ef|grep mwa
    for starting
    1) login to Applications tier
    2) cd $MWA_TOP/bin
    3) ./mwactl.sh -login sysadmin/xxxxx start _force 10200;
    4) check the wma process from OS level
    ps -ef|grep mwa

  • Trouble creating a portal service

    Hi,
    We are trying to create a portal service with the DeveloperStudio (7.1) and are having lots of problems. We are creating the project with the "Portal Application Project" and then creating the service via "Portal Application Object".  This worked well in the old 7.0 environment.
    We can find the services via nwa and it says there that they are running but we have no indication that they have really started, because the functionality isn't be used. The logger is not being fired either.
    Checking the traces we are finding strange warnings like "Web Model Builder: WEB-INF/web.xml is not Java EE 5 compatible, because of this annotations will not be processed." or "BcaClassFinder.addResources Can not open zip fileD:\usr\sap\CE1\J00\j2ee\cluster\server0\temp\deploy\work\deploying\TestServices.ear1215787665722\META-INF\sda-dd.xml it is not a valid zip archive"
    We created another service without any code from us and we are still getting strange errors.
    We also changed the permissions for the service to "Everyone" and this still didn't help.
    Our functionality can be packed in some other sort of service - it doesn't have to a portal service. The main requirement is that the service is restarted after a server restart.
    Does anyone have a clue what the problem might be or what sort of a service might be more appropriate?
    Thanks.
    Dick

    add the user & password at the end of ur URL
    refer the following thread.
    external service configration+adding webservice with basic authentication

  • When will BRE [Backup restartable Extensions] be available in Ontap Cluster mode ?

    Hi Folks, When will BRE [Backup restartable Extensions] be available in Ontap Cluster mode. With 7-mode there is no issue, we can suspend and restart backup from the checkpoint, however with Ontap cluster mode version 8.3 I am currently running, this is not possible [I guess all versions]. If the Job is suspended in cluster mode, session ID is lost and new session  ID is generated when the backup is resumed, in other words data backup starts from begining. Is this something will be available in Onap 8.4 cluster mode ? Thanks,
    -Ashwin 

    Hi, Yeah, you are right - 8.3RC1 is older than 8.3P1.
     8.3 Releases:
     8.3RC1 ----> old release [I already tested - dump restart does not work]
     8.3RC2
     8.3
     8.3P1 -----> Customer already is on higher update and it still dosent work
     8.3P2
     8.3.1RC1 ---> Latest release
    My confusion has only increased now as far as when this BUG is fixed Or if at all fixed?
    http://mysupport.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=1472 According to this BUG, this is already fixed in all versions of 8.3. I am currently running 8.3RC1 Simulator and suspending a Job is causing NDMP session ID to end. In 7-mode: When we suspend a Job from Backup Software, NDMP session ID is not lost and when you run Backup status command, it shows -> State : RESTARTABLEThe key word is 'RESTARTABLE' which dosent seem to work in cluster mode.
    The NDMP Backup Restart Extension (BRE) interface is a proprietary extension defined in class 0x2050
    According to NDMP.org:
    NDMP_BRE_RESTART_BACKUP:
    This request is used by the backup application (DMA) to instruct the Data Server to restart a previous backup operation at a specific point in the backup stream.  Request arguments include a handle to a previously created backup context, the restart point specified as an absolute offset within the backup stream, and a file history entry corresponding to the restart point.The backup restart mechanism requires that the Data Server generate file history information and that the Data Server implementation of file history generate fh_info values as absolute byte offsets within the backup stream. The backup application determines restart points by accessing the Tape Server NDMP_MOVER_GET_STATE bytes_moved value at appropriate ‘checkpoints’ during the original backup operation. A checkpoint represents a known good point in the backup operation. BRE extensions are bydefault disabled, I enabled by setting it 'true' yet its not working. CMODE83RC1::*> ndmp extensions show
      (vserver services ndmp extensions show)Is Extension 0x2050 Enabled: true Thanks,
    -Ashwin

  • Use of synchronized keyword with portal services

    Hi,
    Can you confirm me if it is true that a portal service is a Singleton? I mean, when using an instance variable of a portal service I am able to set the value of the instance variable using one client app and get it afterwards using another client app. So we are talking about the same and only instance of the portal service, right?
    If this is true how can I synchronize the access to a portal's service method? I tried to mark
    the method syncronized (in the interface) but then I realized that this issues a compiler error because one can not mark an interface method synchronized. So can I mark the implementation class instead? That is, can I leave the interface without the synchronized keyword for the method and still mark the implementation of the method in the service class as syncronized? Does this work?
    Thanks in advance,
    Diz

    Hi,
    Portal service is not a Singleton, as the name says a service is just provider for services which does not save state between two requests/applications.
    So if you want to save state, then use some session variables to save it.
    In a cluster installation, each server node has its own portal services, so if you save state in service, then your application should save this state on all servers of the cluster.
    So you should change your approch.
    http://help.sap.com/saphelp_nw70/helpdata/en/e3/fab74247e2b611e10000000a155106/frameset.htm
    Greetings,
    Praveen Gudapati
    [Points are always welcome for helpful answers]

  • 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

  • Portal Service Fails to Start

    Hi all,
    I've developed a custom portal service based on
    the com.sap.netweaver.kmc.globalservice.zip example
    available on NWDS Help. When I deploy it, the service
    works ok but whenever I restart the J2EE instance it
    doesn't start. I've already tried to undeploy the
    application, shutdown, start, deploy and start sequence
    that I found on another discussion from who seemed to
    have the same problem but it didn't work.
    Thanks in advanced,
    Here's my portalapp.xml:
    <?xml version="1.0" encoding="utf-8"?>
    <application name="com.redcolombia.portal.km" alias="com.redcolombia.portal.km">
    <application-config>
    <property name="startup" value="true"/>
    <property name="PrivateSharingReference" value="com.sap.portal.runtime.config, com.sap.portal.runtime.config.component, usermanagement, com.sap.netweaver.bc.crt, com.sap.netweaver.bc.util, com.sap.netweaver.bc.sf, com.sap.netweaver.bc.rf, com.sap.netweaver.bc.sf.service, com.sap.netweaver.bc.rf.service, com.sap.portal.ivs.connectorservice"/>
    </application-config>
    <components/>
    <services>
    <service name="DocumentosRecientesKM">
    <service-config>
    <property name="className" value="com.redcolombia.portal.km.DocumentosRecientesKM"/>
    <property name="startup" value="true"/>
    </service-config>
    <service-profile>
    <property name="Repository" value="documents"/>
    </service-profile>
    </service>
    </services>
    </application>
    Here's the log extract from the J2EE trace file:
    #1.5#0008540656D80060000001EF00000B1000040BAEAF4AE49A#1138744800314#com.sapportals.wcm.util.logging.CatchBlockHandler#sap.com/irj#com.sapportals.wcm.util.logging.CatchBlockHandler.CatchBlockHandler#Guest#192####cfdc3ce092a411dab3400008540656d8#SAPEngine_Application_Thread[impl:3]_33##0#0#Error##Plain###[INTERNAL] com.sapportals.wcm.util.profiler.IProfiler: java.lang.ClassNotFoundException: com.sapportals.wcm.util.profiler.IProfiler
    at com.sapportals.wcm.crt.CrtClassLoaderRegistry.findClass(CrtClassLoaderRegistry.java:176)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
    at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:219)
    at com.sapportals.wcm.crt.CrtClassLoaderRegistry.forName(CrtClassLoaderRegistry.java:349)
    at com.sapportals.wcm.util.logging.CatchBlockHandler.<clinit>(CatchBlockHandler.java:61)
    at com.sapportals.wcm.repository.ResourceFactory.getInstance(ResourceFactory.java:57)
    at com.redcolombia.portal.km.DocumentosRecientesKM.register(DocumentosRecientesKM.java:202)
    at com.redcolombia.portal.km.DocumentosRecientesKM.init(DocumentosRecientesKM.java:72)
    at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstance(PortalServiceItem.java:801)
    at com.sapportals.portal.prt.core.broker.PortalServiceItem.createServiceInstance(PortalServiceItem.java:614)
    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.startNonCoreApplications(PortalAppBroker.java:1469)
    at com.sapportals.portal.prt.runtime.Portal.init(Portal.java:406)
    at com.sapportals.portal.prt.core.PortalCoreInitializer.coreInit(PortalCoreInitializer.java:54)
    at com.sapportals.portal.prt.dispatcher.PortalInitializer.<init>(PortalInitializer.java:129)
    at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:161)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:359)
    at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:42)
    at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:114)
    at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:392)
    at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.addServlet(WebComponents.java:138)
    at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:376)
    at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:110)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    #1.5#0008540656D80060000001F000000B1000040BAEAF4B3DE2#1138744800330#com.sapportals.wcm.WcmException#sap.com/irj#com.sapportals.wcm.WcmException.WcmException(118)#Guest#192####cfdc3ce092a411dab3400008540656d8#SAPEngine_Application_Thread[impl:3]_33##0#0#Error##Plain###com.sapportals.wcm.repository.runtime.CmAdapter java.lang.ClassNotFoundException: com.sapportals.wcm.repository.runtime.CmAdapter
    at com.sapportals.wcm.crt.CrtClassLoaderRegistry.findClass(CrtClassLoaderRegistry.java:176)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
    at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:219)
    at com.sapportals.wcm.crt.CrtClassLoaderRegistry.forName(CrtClassLoaderRegistry.java:349)
    at com.sapportals.wcm.repository.ResourceFactory.getInstance(ResourceFactory.java:48)
    at com.redcolombia.portal.km.DocumentosRecientesKM.register(DocumentosRecientesKM.java:202)
    at com.redcolombia.portal.km.DocumentosRecientesKM.init(DocumentosRecientesKM.java:72)
    at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstance(PortalServiceItem.java:801)
    at com.sapportals.portal.prt.core.broker.PortalServiceItem.createServiceInstance(PortalServiceItem.java:614)
    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.startNonCoreApplications(PortalAppBroker.java:1469)
    at com.sapportals.portal.prt.runtime.Portal.init(Portal.java:406)
    at com.sapportals.portal.prt.core.PortalCoreInitializer.coreInit(PortalCoreInitializer.java:54)
    at com.sapportals.portal.prt.dispatcher.PortalInitializer.<init>(PortalInitializer.java:129)
    at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:161)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:359)
    at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:42)
    at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:114)
    at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:392)
    at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.addServlet(WebComponents.java:138)
    at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:376)
    at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:110)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    #1.5#0008540656D80060000001F200000B1000040BAEAF4B988D#1138744800361#com.sap.portal.prt.runtime.broker#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#192####cfdc3ce092a411dab3400008540656d8#SAPEngine_Application_Thread[impl:3]_33##0#0#Error#1#/System/Server#Java###[PortalServiceItem.startServices] service initialisation failed:RecientesKMService|DocumentosRecientesKM
    [EXCEPTION]
    #1#com.sapportals.portal.prt.core.broker.PortalServiceInstantiationException: Could not instantiate implementation class com.redcolombia.portal.km.DocumentosRecientesKM of Portal Service RecientesKMService|DocumentosRecientesKM because: could not load the service
    at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstance(PortalServiceItem.java:820)
    at com.sapportals.portal.prt.core.broker.PortalServiceItem.createServiceInstance(PortalServiceItem.java:614)
    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.startNonCoreApplications(PortalAppBroker.java:1469)
    at com.sapportals.portal.prt.runtime.Portal.init(Portal.java:406)
    at com.sapportals.portal.prt.core.PortalCoreInitializer.coreInit(PortalCoreInitializer.java:54)
    at com.sapportals.portal.prt.dispatcher.PortalInitializer.<init>(PortalInitializer.java:129)
    at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:161)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:359)
    at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:42)
    at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:114)
    at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:392)
    at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.addServlet(WebComponents.java:138)
    at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:376)
    at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:110)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: java.lang.NullPointerException
    at com.redcolombia.portal.km.DocumentosRecientesKM.register(DocumentosRecientesKM.java:216)
    at com.redcolombia.portal.km.DocumentosRecientesKM.init(DocumentosRecientesKM.java:72)
    at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstance(PortalServiceItem.java:801)
    ... 21 more

    Hi Detlev,
    Thanks for pointing that out. I've solved that
    NullPointerException and the service comes up, however, my service fails to register as a ResourceEventReceiver so it is up but it doesn't do its job.
    In my service I try to register as an
    ResourceEventReceiver by implementing the
    IResourceEventReceiver inteface. This is what is failing
    in my service. Is there some service properties that are
    needed for this that I don't know of?
    This is my code:
    public final void register(String repositoryName) {
         if( repositoryName == null ){
              log.fatalT("Repository Property is NULL...not doing anything...");
               return;
         IManagerFactory managerFactory;
         IRepositoryManager repository=null;
         try {
           managerFactory = ResourceFactory.getInstance().getManagerFactory();
           repository = managerFactory.getRepositoryManager(repositoryName);
           IResourceEventBroker broker = repository.getEventBroker();
           if( broker == null ) return;
           boolean async = false; // register as synchronous event receiver
           broker.register(this, resourceReadEvent, IEventBroker.PRIO_MIN, async);
           log.fatalT("Registered to " + repository.getPrefix()" Prefix="repository.getPrefix());
         catch( WcmException e ) {
           //log.fatalT("exception while registering to " + repository==null?null:repository.getPrefix() + ": " + e.getMessage());
           log.fatalT("Exception while registering to repository error: "+e.getMessage());
           e.printStackTrace();
    This is the trace:
    #1.5#0008540656D80060000001EF0000066000040BB044DABFBF#1138751604169#com.sapportals.wcm.util.logging.CatchBlockHandler#sap.com/irj#com.sapportals.wcm.util.logging.CatchBlockHandler.CatchBlockHandler#Guest#192####a7c9589092b411da9b870008540656d8#SAPEngine_Application_Thread[impl:3]_25##0#0#Error##Plain###[INTERNAL] com.sapportals.wcm.util.profiler.IProfiler: java.lang.ClassNotFoundException: com.sapportals.wcm.util.profiler.IProfiler
         at com.sapportals.wcm.crt.CrtClassLoaderRegistry.findClass(CrtClassLoaderRegistry.java:176)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
         at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
         at java.lang.Class.forName0(Native Method)
         at java.lang.Class.forName(Class.java:219)
         at com.sapportals.wcm.crt.CrtClassLoaderRegistry.forName(CrtClassLoaderRegistry.java:349)
         at com.sapportals.wcm.util.logging.CatchBlockHandler.(PortalInitializer.java:129)#
    #1.5#0008540656D80060000002060000066000040BB044DB277F#1138751604200#System.err#sap.com/irj#System.err#Guest#192####a7c9589092b411da9b870008540656d8#SAPEngine_Application_Thread[impl:3]_25##0#0#Error##Plain###     at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:161)#
    #1.5#0008540656D80060000002070000066000040BB044DB27D8#1138751604200#System.err#sap.com/irj#System.err#Guest#192####a7c9589092b411da9b870008540656d8#SAPEngine_Application_Thread[impl:3]_25##0#0#Error##Plain###     at java.security.AccessController.doPrivileged(Native Method)#
    #1.5#0008540656D80060000002080000066000040BB044DB2833#1138751604200#System.err#sap.com/irj#System.err#Guest#192####a7c9589092b411da9b870008540656d8#SAPEngine_Application_Thread[impl:3]_25##0#0#Error##Plain###     at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:359)#
    #1.5#0008540656D80060000002090000066000040BB044DB288E#1138751604200#System.err#sap.com/irj#System.err#Guest#192####a7c9589092b411da9b870008540656d8#SAPEngine_Application_Thread[impl:3]_25##0#0#Error##Plain###     at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:42)#
    #1.5#0008540656D800600000020A0000066000040BB044DB28E7#1138751604200#System.err#sap.com/irj#System.err#Guest#192####a7c9589092b411da9b870008540656d8#SAPEngine_Application_Thread[impl:3]_25##0#0#Error##Plain###     at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:114)#
    #1.5#0008540656D800600000020B0000066000040BB044DB2943#1138751604200#System.err#sap.com/irj#System.err#Guest#192####a7c9589092b411da9b870008540656d8#SAPEngine_Application_Thread[impl:3]_25##0#0#Error##Plain###     at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:392)#
    #1.5#0008540656D800600000020C0000066000040BB044DB29A1#1138751604200#System.err#sap.com/irj#System.err#Guest#192####a7c9589092b411da9b870008540656d8#SAPEngine_Application_Thread[impl:3]_25##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.addServlet(WebComponents.java:138)#
    #1.5#0008540656D800600000020D0000066000040BB044DB2A0A#1138751604200#System.err#sap.com/irj#System.err#Guest#192####a7c9589092b411da9b870008540656d8#SAPEngine_Application_Thread[impl:3]_25##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:376)#
    #1.5#0008540656D800600000020E0000066000040BB044DB2A6A#1138751604200#System.err#sap.com/irj#System.err#Guest#192####a7c9589092b411da9b870008540656d8#SAPEngine_Application_Thread[impl:3]_25##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:110)#
    #1.5#0008540656D800600000020F0000066000040BB044DB2AC7#1138751604200#System.err#sap.com/irj#System.err#Guest#192####a7c9589092b411da9b870008540656d8#SAPEngine_Application_Thread[impl:3]_25##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)#
    #1.5#0008540656D80060000002100000066000040BB044DB2B20#1138751604200#System.err#sap.com/irj#System.err#Guest#192####a7c9589092b411da9b870008540656d8#SAPEngine_Application_Thread[impl:3]_25##0#0#Error##Plain###     at java.security.AccessController.doPrivileged(Native Method)#
    #1.5#0008540656D80060000002110000066000040BB044DB2B7C#1138751604200#System.err#sap.com/irj#System.err#Guest#192####a7c9589092b411da9b870008540656d8#SAPEngine_Application_Thread[impl:3]_25##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)#
    #1.5#0008540656D80060000002120000066000040BB044DB2BD7#1138751604200#System.err#sap.com/irj#System.err#Guest#192####a7c9589092b411da9b870008540656d8#SAPEngine_Application_Thread[impl:3]_25##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)#
    #1.5#0008540656D80060000002130000066000040BB044DB7D5B#1138751604231#com.redcolombia.portal.km.DocumentosRecientesKM#sap.com/irj#com.redcolombia.portal.km.DocumentosRecientesKM#Guest#192####a7c9589092b411da9b870008540656d8#SAPEngine_Application_Thread[impl:3]_25##0#0#Fatal##Plain###Initializing instance of service com.redcolombia.portal.km.DocumentosRecientesKM number 1#
    Message was edited by: Andrés Acero

  • Portal Service - java.lang.NoClassDefFoundError

    Hi all,
    I've a Web Dynpro project which uses a portal service we wrote.
    I added the service's name to the "Sharing References" of the project and the project runs.
    However, after each restart to the server I get 'java.lang.NoClassDefFoundError' for the portal service. Redeploying the service solves the problem until next restart...
    After doing a lot of checking I've came to the conclusion that the problem is in the initialization of the service in the component controller.
    The component controller has 3 methods. In each of this methods the service is called
    ISqlService sqlservice = (ISqlService)WDPortalUtils.getServiceReference(ISqlService.KEY);
    After commenting this lines and moving the initialization line to "begin others" segment the problem seems to be solved (I've done some restarts to the server and the application ran without a problem)
    My question is: if none of the methods of the controller is called on application startup then why do I get the java.lang.NoClassDefFoundError?
    Also, when does the Web Dynpro framework load the portal service? isn't it supposed to be first time the service is called?
    Regards,
    Omri

    Hi Umesh,
    Try declaring a runtime reference for the service you are using in the project properties.
    Please explore the options:
    Project properties -> WebDynpro References -> Service References & Sharing References
    For ex:In my application, i use KM functionality.Even though Ive KM jars in the classpath (as external lib DCs), I mentioned a runtime reference in "Sharing References" as PORTAL:sap.com/com.sap.km.application.
    Similarly, I remember seeing somewhere mentioning the service you're trying to access as a Service Reference in the DC properties.
    something like: PORTAL:mycompany.com/com.....MyService
    A common portal service that is used in WebDynpro DCs is URLGenerator service. Probably if you search on it, you might find a clue.
    Regards,
    Rajit Srinivas

  • What is the lifecycle of Portal Service

    Hi,
    I am thinking in building a Protal Service as a bridge to Stateful Session EBJ.
    so i have two question:
    1. what is the lifecycle of Portal Service?
       When the PRT destroy the Portal service
    2. what is the relation between Portal components and Portal Service and User.
    For example i have to two user
    that used the same Portal Component whitch used Portal Service to creat Stateful Session EJB.
    are two users useing the same ejb client?

    Hi Raja,
    a service is started with the portal startup, if the "startup" property is set to true, or, if not, a service is started on request. It can be restarted manually via the portal interface (System Administration -- System Configuration -- Service Configuration). So a service is destroyed when the portal stops or if the service is restarted manually (then the old instance gets destroyed and a new one gets created).
    A service behaves like a singleton, so you access the same instance, independent of users and components they come from; if you want to differentiate, you have to implement the differentiation by yourself.
    Hope it helps
    Detlev

  • Accessing Portal Service from web dynpro : NoClassDefFoundError

    Hello Experts,
    I tried to develop a portal service (EquiService) and a web dynpro application (wdequset) which accesses the portal service. I put my web dynpro in an IView to show it in the portal. The service is running but when I try to open the IView I always get an error. I debugged my web dynpro application and found out that I didn’t get a reference to the service (portalEquiService is always null). See the following code and have a look to my comments.
    public void wdDoInit()
        //@@begin wdDoInit()
        String key = IEquiService.KEY;
         * Here I get the right key. That’s OK so far.
    //    IEquiService portalEquiService = (IEquiService)PortalRuntime.getRuntimeResources().getService(key);
         * When I use this line to get an instance of the service, I get the following error:
         * java.lang.NoClassDefFoundError: com/sapportals/portal/prt/runtime/PortalRuntime
         * The package "com.sapportals.portal.prt.runtime.*" is imported
         IEquiService portalEquiService = (IEquiService) WDPortalUtils.getServiceReference(key);
          * I found this in the "How to Access a Portal Service Within a WebDynpro Java Application" document.
          * When I use this line, I get the following error:
          * java.lang.NoClassDefFoundError: com/company/service/equi/IEquiService
          * The package "com.company.service.equi.IEquiService" is also imported.
        wdContext.currentContextElement().setEquinummer(portalEquiService.getEquiData().getEquiNr());
        //@@end
    When I have a look to the service in the portal I see that the service is running and the following additional lines under “Dependents”:
    service: psequinr|EquiService
    SAPJ2EE::company.com/wdequset
    So the service seems to know my web dynpro application (after debugging for the first time).
    Detailed error information 1 (when I try to get the reference by PortalRuntime.getRuntimeResources().getService(key) ):
    java.lang.NoClassDefFoundError: com/sapportals/portal/prt/runtime/PortalRuntime
         at com.company.service.ServiceCust.wdDoInit(ServiceCust.java:107)
         at com.company.service.wdp.InternalServiceCust.wdDoInit(InternalServiceCust.java:112)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingCustomController.doInit(DelegatingCustomController.java:73)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getCustomControllerInternal(Component.java:436)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:374)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:403)
         at com.sap.tc.webdynpro.progmodel.context.MappedAttributeInfo.initAttributeMapping(MappedAttributeInfo.java:319)
         at com.sap.tc.webdynpro.progmodel.context.MappedAttributeInfo.init(MappedAttributeInfo.java:278)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initAttributes(NodeInfo.java:674)
         at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:238)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:659)
         at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:539)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:421)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:130)
         at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:41)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.displayToplevelComponent(ClientComponent.java:135)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:404)
         at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:618)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
         at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:251)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:48)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Detailed error information 2 (when I tryto get reference by WDPortalUtils.getServiceReference(key) ):
    java.lang.NoClassDefFoundError: com/company/service/equi/IEquiService
         at com.company.service.ServiceCust.wdDoInit(ServiceCust.java:123)
         at com.company.service.wdp.InternalServiceCust.wdDoInit(InternalServiceCust.java:112)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingCustomController.doInit(DelegatingCustomController.java:73)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getCustomControllerInternal(Component.java:436)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:374)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:403)
         at com.sap.tc.webdynpro.progmodel.context.MappedAttributeInfo.initAttributeMapping(MappedAttributeInfo.java:319)
         at com.sap.tc.webdynpro.progmodel.context.MappedAttributeInfo.init(MappedAttributeInfo.java:278)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initAttributes(NodeInfo.java:674)
         at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:238)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:659)
         at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:539)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:421)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:130)
         at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:41)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.displayToplevelComponent(ClientComponent.java:135)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:404)
         at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:618)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
         at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:251)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:48)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Hope that anybody knows what could be wrong here.
    Thanks a lot.
    Rene

    The prtapi.jar is set in the classpath:
    <classpathentry kind="lib" path="C:/Programme/SAP/JDT/eclipse/plugins/com.sap.tc.ap/comp/SAP_JTECHS/DCs/sap.com/epbc.prtapi._api/_comp/gen/default/public/default/lib/java/prtapi.jar"/>
    and when I look in the portal (System Administration -> Support -> Portal Runtime -> Application Console), select my service and press the "show" Button, I see that the service has a dependency to my web dynpro application.
    service: psequinr|EquiService
    SAPJ2EE::company.com/wdequset
    So I think that the sharing reference of the web Dynpro should be ok. Or not?

  • Custom Portal Service not displayed under Service Configuration

    Hi All,
    I am working on EP 7.0 SP8.
    SAP Portal is not displaying any custom built Portal Services under Service Configuration tab.
    I checked with the permission, and I am having the required authorization for my service.
    I am not able to find any document on making the custom service available under Service Configutation to start/stop the service.
    Please let me know any reference docs on this.
    -Thanks,
    Pavan

    Hi Pavan,
    > working on EP 7.0 SP8
    Glad to hear that you are not stuck on EP5   No, really, that is older than old... Anyhow:
    > not displaying any custom built Portal Services under Service Configuration tab
    There services are only listed if they are configurable, i.e. if they have a service profile with at least one property (compare http://help.sap.com/saphelp_nw70ehp2/helpdata/en/df/e6b74253ffda11e10000000a155106/frameset.htm). Otherwise it makes less sense to restart a service (normally this is done after changing a service profile parameter).
    Hope it helps
    Detlev

  • 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 log exceptions and imp logging info in Portal Service via ILogger?

    Hi Experts,
    I m trying to use ILogger for my application.
    Information about my application:
    I have created a Portal Service and exposed it as a Web Service which is deployed as a PAR file on to the SAP J2EE Engine.
    I need to use the Logging facility of ILogger in this Portal Service.
    I have written the following code in the Init() function of the Portal Service
    public void init(IServiceContext serviceContext)
           mm_logger = serviceContext.getLogger("com.persistent.pankaj");
    I have put the logger.xml in the logger folder of PORTAL-INF
    my logger.xml is as follows:
    <Server>
    <Logger name="testLog" loggerInterface="com.sapportals.portal.prt.logger.ILogger" locationName="com.sap.portal.testLog" pattern="%d # %20t %15s %m #" isActive="true">
    <LoggerClass className="com.sapportals.portal.prt.logger.SimpleFileLogger" level="INFO">
    <param filename="logs/com.persistent.pankaj.log" append="true">
    </param>
    </LoggerClass>
    </Logger>
    </Server>
    On deploying my portal service as a web service
    I m unable to get the logs.
    I even dont know where will i get the log file, means wat is the exact location where i can check my log results
    I m a newbie for this
    Please help me out
    Help will be rewarded n appreciated
    -pankaj

    Hi Pankaj,
    In your init method try this code to create the logger:
    ILogger logger = PortalRuntime.getLogger("testLog");
    In your logger.xml the logger name was testLog and not com.persistent.pankaj so while creating logger you should use testLog in the above code.
    By default all the logs are written to defaultTrace.log files, to check them read this:
    Portal Runtime Logs
    If you want to log in a seperate logfile then you should set a seperate log destination, which is not recommended on productive systems due to performance problems.
    Also read these to know how to set seperate log destinations:
    Netweaver Portal Log Configuration & Viewing (Part 3)
    Netweaver Portal Log Configuration & Viewing (Part 1)
    Netweaver Portal Log Configuration & Viewing (Part 2)
    Regards,
    Praveen Gudapati

  • 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

  • Get current user in portal service context

    hi guys,
    We want to implement a portal service which will check user's role from LDAP, and we need to get the current user id.
    We know for class IPortalComponentRequest, there is method getUser().getUserId(), is there any similar method for IServiceContext? or any way for us to get user id in portal service?
    regards,
    Guo Feng

    Hi Feng,
    Implement
    public String getParameter(IPortalComponentRequest arg0, String arg1)
    eg in your implementation class and add the following code.
    IUserContext userContext = arg0.getUser();
    String username = userContext.getLogonUid();
    String full_name = userContext.getDisplayName();
    HTH

Maybe you are looking for