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)

Similar Messages

Financial Reporting batch runs without being scheduled when services restart

Hi,
hopefully someone may have come across this before:
I set up a scheduled batch yesterday (workspace 11.1.1.1.3) pointing at a batch of 2 large reports. As part of the testing I ran it at a scheduled time during the day and it worked perfectly. However the following morning it ran the batch again even though there was nothing in the scheduler (and I checked the scheduled job and it still said last run time 14:29 the previous day). However the snapshots that it produces had been updated overnight. One thing to add is that we shutdown all the Hyperion Services (to allow for a system backup) and they had just come up when the reports ran (could see the batch request in the FR log). Is there a way of stopping this from happening i.e. some setting/config I need to change?
Thanks,
J.

Refer :
http://download.oracle.com/docs/cd/E12825_01/epm.111/fr_user/ch15s05s02.html
for more details about command line scheduling

How to write a time triggered portal service/ schedule a portal service

Hi,
Can some one please provide me with some info/url about how to a create a time triggered portal service i.e., scheduling portal service.
Any help will be greatly appreciated.
Thanks & Regards,
Sudhir

Hi,
see my reply to your post in PortalDevelopment area:
<a href="https://www.sdn.sap.com/irj/sdn/thread?threadID=249185&tstart=0">https://www.sdn.sap.com/irj/sdn/thread?threadID=249185&tstart=0</a>
Romano

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 .......

How to schedule a service to run before network goes down

Hi
I wrote a new smf service and added it to the repository.
When running with "stop" (when the system goes down) it sends an alert to another machine.
My question is :
How can I schedule that service to run just before network services go down?
another question, how can I schedule another service to run just BEFORE system is getting down?
Many Thanks
--me2unix

Dependencies appear to be really written and tested on the boot side, but they should work properly going down as well.
My first assumption is that you'd make a dependency on the network for your service. So it should be started after the network starts, and will wait for your service to quit before trying to shut down the network.
Now this would only apply to normal shutdowns. Also, there are mulitple services on the box that have network affects. You may need to read through several to understand their purpose and interaction to pick the correct one for your use. Probably the milestone/network will be the best choice.
Darren

How do I run a weblogic platform portal 8.1 on a weblogic server 7.0 service pack 4?

Hello.
How do I run a weblogic platform portal 8.1 on a weblogic server 7.0 service
pack 4?
Is that a supported configuration? any problems / Issues ?
Weblogic Integrator

Why the hell do you want to do that ? ? ?
just run it on 8.1, if you need to get info from the 7.0 server just get it.
8.1 is a whole new framework, what you suggest a hack that is probably not supported.
nerdi
"Integrator" <[email protected]> wrote:
>
Hello.
How do I run a weblogic platform portal 8.1 on a weblogic server 7.0
service
pack 4?
Is that a supported configuration? any problems / Issues ?
Weblogic Integrator

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

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

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

Scheduling SSIS packages to run using SQL Server Agent Service

The job failed. The Job was invoked by Schedule 11 (run package). The last step to run was step 1 (Execute Package)". how do i resolve this?

Most probable causes: the developer runs the package in BI studio, it works. The job is deployed and runs in a schedule.
the sql job agent does not have same rights as the developer.
the test in BI studio was doen in 32-bit mode , the job by default ran in 64-bit mode. some oledb-odbc drivers may not work.
Jan D'Hondt - SQL server BI development

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

SyncToy 2.1 Can't Find NAS Folder When Run From Task Scheduler

I'm using SyncToy 2.1 to keep two WIN7 computers and a Synology DS414j NAS drive in sync. I have several folder pairs configured, some between the two PC's and three between one PC and the NAS drive. I have a task set up for automatic syncing. The problem
is SyncToy can't find the destination folders on the NAS drive if it's run from Task Scheduler. If I run SyncToy manually, everything works fine. I've even tried opening the command prompt and running the exact same program Task Scheduler is running (SyncToyCmd.exe
-R), and it works perfectly. But when Task Scheduler runs the task, it fails to find the NAS folders with the following error message:
SYNC: 08/21/2014 14:12:26:140: *** Failed to execute folder pair Downloads to NAS. Could not locate folder \\DISKSTATION\Downloads\.
I've been looking for days for a solution and have not found anyone with this problem. Any ideas?

Hi Texxxas,
Apparently the problem is not with SyncToy, it is with Task Scheduler. If you have had Task Scheduler work for you in the past, then I don't have an answer for that. I have never been able to get Task Scheduler to work correctly with SyncToy and a NAS drive.
I have found that for some reason it works with USB external HDD's but will not work with a network connected hard drive. The same bug exists in Win8.1 as well. However, I have since found a third party task scheduler that works perfectly with SyncToy and
my NAS drive. It is called System Scheduler by Splinterware. The free version only works when you are logged in but they have a paid version that runs as a service and will execute without being logged in. This has solved my problem.

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

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

Explicit running of a scheduled portal service.

Similar Messages

Maybe you are looking for