AccAD crontab jobs (scheduled tasks) - explained

/etc/crontab
run-parts
01 * * * * root run-parts /etc/cron.hourly          <-- every HH:01
02 4 * * * root run-parts /etc/cron.daily          <-- every 04:02am
22 4 * * 0 root run-parts /etc/cron.weekly     <--  every Sunday 04:22am
42 4 1 * * root run-parts /etc/cron.monthly     <--  every 1st of month 04:42am
* * * * root run-parts /etc/cron.minutely          <--  every minute
/etc/cron.daily:
-rwxr-xr-x  1 root root  167 Feb  2 12:47 slot-0
/etc/cron.hourly:
-r-xr-xr-x  1 root root  626 Feb  1 12:30 vl_clean_cores
-rwxr-xr-x  1 root root  383 Feb  1 12:30 vl-ntp-update
/etc/cron.minutely:
-rwxr-xr-x  1 root root  153 Feb  1 11:38 accad_monitor.sh
-rwxr-xr-x  1 root root  515 Feb  1 12:30 vl-write-maxdb.pl
/etc/cron.weekly:
-rwxr-xr-x  1 root root  767 Feb  1 12:30 vl-slot-restart

Similar Messages

  • ASE 15.7 Job Scheduler won´t start again

    Hi,
    we encoutered the following problem in our ECC6.0 / EHP5 on ASE 15.7 PL 122 System:
    DBACockpit / Collector Configuration shows the warning "The ASE-Job Scheduler is not active". The log SID_JSAGENT shows the following entries:
    00:11704:12104:2014/09/01 08:00:35.78 jamain  Opening jsagent connection.
    00:11704:12104:2014/09/01 08:00:35.78 jamain  Agent will listen on <IP>
    00:11704:12104:2014/09/01 08:00:35.78 jamain  SYB_JSAGENT waiting for connection
    00:11704:12104:2014/09/01 08:00:36.72 jamain  Job Scheduler Agent connected with Job Scheduler Task on port 4903
    00:11704:12104:2014/09/01 08:00:36.72 jamain  Initializing SYB_JSAGENT
    00:11704:12104:2014/09/01 08:00:36.72 jamain  Allocating list resources.
    00:11704:12104:2014/09/01 08:00:36.72 jamain  Allocating queue resources.
    00:11704:12104:2014/09/01 08:00:36.72 jamain  Allocating thread resources.
    00:11704:12104:2014/09/01 08:00:36.72 jamain  Initializing connection pool.
    00:11704:12104:2014/09/01 08:00:36.99 jamain  Client message: ct_connect(): user api layer: external error: The connection failed because of invalid or missing external configuration data.
    00:11704:12104:2014/09/01 08:00:36.99 jamain  ct_connect() failed.
    00:11704:12104:2014/09/01 08:00:36.99 jamain  jsj_AddConxs: jsd_MakeConnection() failed for user jstask to server SID
    00:11704:12104:2014/09/01 08:00:36.99 jamain  jsj_CreateConxPool: jsj_AddConxs() failed
    00:11704:12104:2014/09/01 08:00:36.99 jamain  Initialization failed initializing connection pool
    00:11704:12104:2014/09/01 08:00:36.99 jamain  Jsagent failed to handle INIT message.
    00:11704:12104:2014/09/01 08:00:36.99 jamain  JS Agent aborting. Cancel all running jobs.
    00:11704:12104:2014/09/01 08:00:36.99 jamain  Job Processing failed.
    00:11704:12104:2014/09/01 08:00:36.99 jamain  JS Agent exiting.
    Restarting the scheduler on ISQL doesn´t seem to work. Any ideas?
    Many thanks & greetings
    Vierengel Stefan

    Hi,
    thank you. Problem was solved by performing the following steps
    1.     deleting the following file: DRIVE:\sybase\SID\OCS-15_0\ini\ocs.cfg
    2.     Stop / Start Job Scheduler
             exec sybmgmtdb..sp_sjobcontrol '','stop_js'
            go
             exec sybmgmtdb..sp_sjobcontrol '','start_js'
            go
    3.     Refresh DBACockpit
    Greetings
    Vierengel Stefan

  • Job scheduling with J2EE on Weblogic 8.1

    Weblogic 8.1 is not J2EE 1.4 compatible
    I need to setup a job scheduling task. Has anyone done this with WL 8.1?
    What is the best way to implement functionality similar to that provided by the J2EE Timer service in J2EE 1.4 compatible servers?
    thanks very much

    Yeah, we use quartz too, but with the Spring wrappers. Works pretty nicely.
    Read up on:
    http://www.springframework.org/docs/reference/scheduling.html
    Cheers
    IV

  • Hi any one please explain background job scheduling

    Hi any one please explain background job scheduling . Good answer can be rewarded.
    Thanks

    Background jobs are pgms that are scheduled to be run in the Background without user interaction. So this can be done only for Type 1(executable) Program and not for Module-Pool Programs. Typically, a variant is defined and the pgm is run using the same.
    The transaction code is sm36 -Define Background job. Using the Start Condition tab you can define when you want the job to run (specific time or if it has to follow after a particular job is done etc.,) Using the Step tab you can assign the pgm name and variant.
    After the job is scheduled, you can check the status in sm37, along with the Job log and Spool.
    For more info:
    http://help.sap.com/saphelp_bw30b/helpdata/en/c4/3a7f87505211d189550000e829fbbd/content.htm

  • How to schedule a crontab job for a script?

    Hi,
    Can anyone help me in this?
    Actually, i want to schedule a crontab job for a script.
    the script needs to check for a file in a diectory.
    When ever a particular file in a directory is created, then i need to run that script. (creation time of file and execution time of script must be same)
    So, how can i do this?
    any suggestions?
    Thanks,
    Suman.

    crontab manual http://linux.about.com/od/commands/l/blcmdl5_crontab.htm
    if you need check files on OS, crontab is good way... to do
    Example: checking trace file older 30 days and remove (00.00 -> every days )
    file.sh:
    ........begin file......
    #!/bin/sh
    find PATH/udump -name '*.trc' -type f -mtime +30 -exec rm {} \;
    ........end file......
    $ chmod 750 file.sh
    $ mv file.sh /home/oracle/file.sh
    -- edit crontab
    $ crontab -e
    0 0 * * * /home/oracle/file.sh
    -- list crontab
    $ crontab -l
    0 0 * * * /home/oracle/file.sh
    good luck

  • Windows Server Backup scheduled task run successfully but backup do not start (not running) on Windows Server 2012

    Hi,
    A backup job has been setup on Windows Server 2012 (Platform: Win32NT; ServicePack: ; Version: 6.2.9200.0; VersionString : Microsoft Windows NT 6.2.9200.0) via Windows Backup Software UI (Local Backup 1.0).
    It is appearing as a scheduled task "\Microsoft\Windows\Backup\Microsoft-Windows-WindowsBackup" belonging to user 'nt authority\system' in task scheduler.
    The problem is that the Backup job never start despite the scheduled task running and completing successfully (when run automatically or manually)!
    Would you be able to explain why and assist in resolving that issue?
    Here is what we know:
    When the backup is run manually via the Windows Backup Software UI, it works fine.
    When the backup is run via command line (as set in schedule task) in a cmd command prompt (as local/domain 'administrator' or as 'nt authority\system' which is possible by running command prompt via 'PsExec.exe -i -s cmd'), something like "%windir%\System32\wbadmin.exe
    start backup -templateId:{f11eb3aa-74e7-4ff4-a57b-d8d567ee3f77} -quiet", it works fine.
    If you manually run the preset scheduled task while logged in as administrator, the task run and complete successfully but the backup job does not start.
    Idem if you schedule task is run automatically at scheduled time.
    The schedule task run and complete successfully but the backup job does not start.
    It is confirmed by running the following in a command prompt as 'nt authority\system':
    schtasks /run /tn "\Microsoft\Windows\Backup\Microsoft-Windows-WindowsBackup"
    SUCCESS: Attempted to run the scheduled task "\Microsoft\Windows\Backup\Microsoft-Windows-WindowsBackup".
    Despite success result, the Backup job does not start running...
    No errors or warning appears anywhere in Event Logs (Microsoft > Windows > Backup or Task Scheduler) nor in the scheduled task History tab. The schedule task complete successfully but no Backup job is run...
    If scheduled task automatically set by Windows Backup software is duplicated (copied) and set manually it runs fine as 'administrator' and as 'nt authority\system' (subject that 'nt authority\system' is added to the 'Backup Operators' AD group).
    Here is an export of the current pre-set schedule task, is there any settings that need to be changed to make it works?
    <?xml version="1.0" encoding="UTF-16"?>
    <Task version="1.4" xmlns="http://schemas.microsoft.com/windows/2004/02/mit/task">
      <RegistrationInfo>
        <Author>MYDOMAIN\SERVER1</Author>
        <SecurityDescriptor>D:AR(A;OICI;GA;;;BA)(A;OICI;GR;;;BO)</SecurityDescriptor>
      </RegistrationInfo>
      <Triggers>
        <CalendarTrigger id="Trigger 1">
          <StartBoundary>2014-07-14T21:00:00</StartBoundary>
          <Enabled>true</Enabled>
          <ScheduleByDay>
            <DaysInterval>1</DaysInterval>
          </ScheduleByDay>
        </CalendarTrigger>
      </Triggers>
      <Principals>
        <Principal id="Author">
          <UserId>S-1-5-18</UserId>
          <RunLevel>HighestAvailable</RunLevel>
        </Principal>
      </Principals>
      <Settings>
        <MultipleInstancesPolicy>Parallel</MultipleInstancesPolicy>
        <DisallowStartIfOnBatteries>true</DisallowStartIfOnBatteries>
        <StopIfGoingOnBatteries>false</StopIfGoingOnBatteries>
        <AllowHardTerminate>true</AllowHardTerminate>
        <StartWhenAvailable>true</StartWhenAvailable>
        <RunOnlyIfNetworkAvailable>false</RunOnlyIfNetworkAvailable>
        <IdleSettings>
          <StopOnIdleEnd>false</StopOnIdleEnd>
          <RestartOnIdle>false</RestartOnIdle>
        </IdleSettings>
        <AllowStartOnDemand>true</AllowStartOnDemand>
        <Enabled>true</Enabled>
        <Hidden>false</Hidden>
        <RunOnlyIfIdle>false</RunOnlyIfIdle>
        <DisallowStartOnRemoteAppSession>false</DisallowStartOnRemoteAppSession>
        <UseUnifiedSchedulingEngine>false</UseUnifiedSchedulingEngine>
        <WakeToRun>false</WakeToRun>
        <ExecutionTimeLimit>P3D</ExecutionTimeLimit>
        <Priority>7</Priority>
      </Settings>
      <Actions Context="Author">
        <Exec>
          <Command>%windir%\System32\wbadmin.exe</Command>
          <Arguments>start backup -templateId:{f11eb3aa-74e7-4ff4-a57b-d8d567ee3f77} -quiet</Arguments>
        </Exec>
      </Actions>
    </Task>
    Thank you in advance for your feedback.

    Once again, the issue is not to run the backup manually from the command line but to have it run via the scheduled task setup by the Windows Backup software.
    By default, the schedule task is to be run as NT Authority\System, and when run under this account, the backup does not start (even though account is member of Backup Operators) and job can manually be run via elevated command prompt. This is not a normal
    behavior and constitute a major bug in Windows Server 2012.
    From my understanding the NT Authority\System account is a built-in account from Windows that should by default be part of the Administrators group (built-in) even though it does not explicitly appears like it in AD by default.
    This account shall have by default Administrators rights and Backup Operators rights (via the Administrators group) without being explicitly added to those groups (http://msdn.microsoft.com/en-gb/library/windows/desktop/ms684190%28v=vs.85%29.aspx). By design
    it is supposed to be the most powerful account which has unrestricted access to all local system resources. If that is not the case (as it seems) then this would constitute a major bug in Windows Server 2012 edition.
    As said previously and as you confirmed, currently by default NT Authority\System on Windows 2012 server cannot start backup manually via an elevated command prompt unless it is manually added to Backup Operators (or Administrators) group. But wouldn't that
    constitute a bug of Windows Server 2012?
    Our server has not yet been restarted since I added NT Authority\System account to the Administrators group explicitly manually so I cannot yet confirmed it would sort the issue. Indeed it is heavily in use so cannot easily be restarted. Will confirm when
    done.
    We also have an additional problem where after a while of last reboot, part of the Exchange ECP can no longer be properly loaded in the web browser due to compilation error (compilation is done via NT Authority\System account which seems to no longer have
    sufficient right to compile .NET code). What is strange is that it works at first and then stop working at some point... I am hopeful that adding NT Authority\System to the Administrators group would sort this issue as well but once again, that shall not be
    needed!!!
    Could a Windows Server 2012 update introduced some security policy changes or else that prevent NT Authority\System to have full power?

  • Background Job Scheduling

    Hi,
      I am scheduling a report to run in background.
    In this report it is creating background jobs automatically for different company codes.
    It submits the 1st background job and waits until it finishes.
    Then 2nd job starts in background and continues with other jobs.
    At end it finishes all the jobs and closes.
    Now my problem is.
    1.       Whether is it possible for us to submit all the jobs at 1 time. And execute at same time. Ie., 1st, 2nd job will start at same time.
    2.       If possible how can we do that.
    What I have written is
    loop at companycode.
    Create job name.
    call fun 'Job_Open'.
    submit xxxx user sy-uname via job job_name numer job_count
    to sap-spool
    spool parameters l_spool_parameter
    without spool dynpro
    with companycode
    with ......
    and return.
    endloop.
    Please help ASAP, urgent.

    hi praveen,
    Job Scheduling Explained
    Definition
    Before any background processing can actually begin, background jobs must be defined and scheduled. The scheduled time for when a job runs is one part of the job’s definition. There are several ways to schedule jobs:
    From Transaction SM36 (Define Background Job)
    With the "start program in the background" option of either Transaction SA38 (ABAP: Execute Program) or Transaction SE38 (the ABAP editor)
    Through the background processing system’s own programming interface. (Many SAP applications use the internal programming interface to schedule long-running reports for background processing.)
    Through an external interface.
    Scheduling Background Jobs   
    Use
    You can define and schedule background jobs in two ways from the Job Overview:
    ·         Directly from Transaction SM36. This is best for users already familiar with background job scheduling.
    ·         The Job Scheduling Wizard. This is best for users unfamiliar with SAP background job scheduling. To use the Job Wizard, start from Transaction SM36, and either select Goto ® Wizard version or simply use the Job Wizard button.
    Procedure
           1.      Call Transaction SM36 or choose CCMS ® Jobs ® Definition.
           2.      Assign a job name. Decide on a name for the job you are defining and enter it in the Job Name field.
           3.      Set the job’s priority, or “Job Class”:
    ·         High priority:      Class A
    ·         Medium priority: Class B
    ·         Low priority: Class C
           4.      In the Target server field, indicate whether to use system load balancing.
    ·         For the system to use system load balancing to automatically select the most efficient application server to use at the moment, leave this field empty.
    ·         To use a particular application server to run the job, enter a specific target server.
           5.      If spool requests generated by this job are to be sent to someone as email, specify the email address. Choose the Spool list recipient button.
           6.      Define when the job is to start by choosing Start Condition and completing the appropriate selections. If the job is to repeat, or be periodic, check the box at the bottom of this screen.
           7.      Define the job’s steps by choosing Step, then specify the ABAP program, external command, or external program to be used for each step.
           8.      Save the fully defined job to submit it to the background processing system.
           9.      When you need to modify, reschedule, or otherwise manipulate a job after you've scheduled it the first time, you'll manage jobs from the Job Overview.
    Note: Release the job so that it can run. No job, even those scheduled for immediate processing, can run without first being released.
    Specifying Job Start Conditions
    Use
    When scheduling a background job (either from Transaction SM36, Define Background Job or CCMS ® Jobs ® Definition), you must specify conditions that will trigger the job to start.
    Procedure
    Choose the Start condition button at the top of the Define Background Job screen.
    Choose the button at the top of the Start Time screen for the type of start condition you want to use (Immediate, Date/Time, After job, After event, or At operation mode) and complete the start time definition in the screen that appears.
    For the job to repeat, check the Periodic job box at the bottom of the Start Time screen and choose the Period values button below it to define the frequency of repetition (hourly, daily, weekly, monthly, or another specific time-related period). Then choose the Save button in the Period values screen to accept the periodicity and return to the Start Time screen.
    Once you’ve completed specifying the job start conditions, choose the Save button at the bottom of the Start Time screen to return to the Define Background Job screen.
    No job can be started until it is released, including jobs scheduled to start immediately. Since releasing jobs can be done only by a system administrator from the job management screen (Transaction SM37) or by other users who have been granted the appropriate Authorizations for Background Processing, no unauthorized user can start a job without explicit permission
    Managing Jobs from the Job Overview
    Use
    The Job Overview, or Job Maintenance, screen is the single, central area for completing a wide range of tasks related to monitoring and managing jobs, including defining jobs; scheduling, rescheduling, and copying existing jobs; rescheduling and editing jobs and job steps; repeating a job; debugging an active job; reviewing information about a job; canceling a job's release status; canceling and deleting jobs; comparing the specifications of several jobs; checking the status of jobs; reviewing job logs; and releasing a job so it can run.
    Procedures
    To display the Job Overview screen, choose CCMS ® Jobs ® Maintenance or call Transaction SM37. Before entering the Job Overview screen, the system first displays the Select Background Jobs screen. You'll need to complete this Job Selection screen to define the criteria for the jobs you want to manage. Once you've selected jobs to manage, you can choose from a wide range of management tasks:
    To copy a single existing job, choose Job ® Copy.
    To reschedule or edit job steps or attributes of a single job, choose Job ® Change. A job step is an independent unit of work within a background job. Each job step can execute an ABAP or external program. Other variants or authorizations may be used for each job step. The system allows you to display ABAP programs and variants. You can scan a program for syntax errors. You can also display the authorizations for an authorized user of an ABAP job step.
    To repeat a single job, choose Job ® Repeat scheduling.
    To debug an active job, choose Job ® Capture: active job. Only a single selection is allowed. If an active job seems to be running incorrectly (e.g., running for an excessively long time), you can interrupt and analyze it in debugging mode in a background process, and then either release it again or stop it altogether.
    You will be able to capture a background job only if you are logged on to the SAP server on which the job is running. To find server information in the Job Overview, select and mark the job, then choose Job ® Job details.
    To review information about a job, choose Job ® Job details. Details displayed can include:
    current job status
    periodicity, or the repetition interval
    other jobs linked to the current job, either as previous or subsequent jobs
    defined job steps
    spool requests generated by the current job
    To cancel a job's "Released" status, select the job or jobs from the Job Overview list and choose Job ® Release -> Scheduled.
    To cancel a job from running but keep the job definition available, select the job or jobs from the Job Overview list and choose Job ® Cancel active job.
    To delete a job entirely, select the job or jobs from the Job Overview list and choose Job ® Delete. Jobs with the status of Ready or Running cannot be deleted.
    To compare the specifications of more than one job, select the jobs from the Job Overview list and choose Job ® Compare jobs.
    To check the status of jobs, select the job or jobs from the Overview Job list and choose Job ® Check status. This allows you to either change the job status back to Planned or cancel the job altogether. This is especially useful when a job has malfunctioned.
    To review job logs, select a job or jobs with the status Completed or Canceled from the Job Overview list and
    regards
    karthik
    reward me points if helpfull

  • Crontab job does not execute Export script

    Hello Dear Oracle/Linux Gurus,
    I have limited knowledge about Cron job scheduling. After reading few articles/documentation, i have scheduled an Export job with crontab.
    When i run manually script (./exportuser.sh) Then its working fine. But with crontab is doesn't trigger. Log file exist but does not contain any entry, its empty.
    I would be grateful if you could let me know where is mistake?
    Thankyou in advance.
    ----Crontab entries are below here----
    oracle@backup-oracle:~/oracle/product/10.2.0/db_1/admin/orcl/dpdump> crontab -l
    # DO NOT EDIT THIS FILE - edit the master and reinstall.
    # (/tmp/crontab.XXXXFcYToV installed on Mon Dec 5 10:26:28 2011)
    # (Cron version V5.0 -- $Id: crontab.c,v 1.12 2004/01/23 18:56:42 vixie Exp $)
    * 21 * * * /home/oracle/oracle/product/10.2.0/db_1/rdbms/scripts/exportuser.sh > /home/oracle/oracle/product/10.2.0/db_1/rdbms/scripts/log/exportuser.log
    ----exportuser.sh is below here-----
    cd /home/oracle/oracle/product/10.2.0/db_1/admin/orcl/dpdump
    find /home/oracle/oracle/product/10.2.0/db_1/admin/orcl/dpdump -ctime +7 -exec rm{} \;
    export DATE=$(date +"%d-%m-%Y")
    exp scott/tiger file=scott_md_bk_$DATE.dmp log=scott_md_bk_$DATE.log rows=yes
    gzip scot_md_bk_*

    I suggest to put the following line at the beginning of your exportuser.sh script:
    date >> /tmp/exportuser.started
    Then check the output of /tmp/exportuser.started to see if the script gets actually called. Errors are normally dispatched by email to the user running the cron task. Did you receive any? You can also check the cron log file for errors and should verify that the cron daemon is actually running, e.g. "ps -ef | grep crond". Crontasks can run as root or any user who is allowed to run cron. I'm not so much familiar with Suse, which is quite different to other Linux distros.

  • What is a Scheduled task ?

    how to write a scheduled task ? Explain me pls
    Thanks in advance
    Prakash

    In OIM you can configure jobs to run on a schedule-based time. So, for example, you can create a task to search and send an e-mail to all users who has password about to expire. You can configure this in OIM as a schedule task, then you have to provide the task parameters (if necessary) and set frequency etc.
    You can get more information about OIM in these links: http://download.oracle.com/docs/cd/E10391_01/index.htm and http://download.oracle.com/docs/cd/E10391_01/doc.910/e10363/oimadm.htm#CIADIAEJ
    Renato.

  • Scheduler task to save file to KM.

    Dear all
    I have seen the following blog for scheduler task.
    <a href="https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1515">Link to blog</a>
    But my scenario is a little bit different. I want to create a sceduler task which creates and save a file in a particular destination in KM.
    Can anybody help me in doing this?
    Regards
    Aparnna

    hi prasad,
    I am also tried the same blog  <b>"Did you know you can schedule jobs in portal using KM's Scheduler Task "</b>..
    After deploy my Par I am getting my schedular task under Knowledge Management>content Management>Globel Service-->schedular task..... But i didnt get <b>yahoofeed.xml</b> file..
    then i have checked..System Configuration >Monitoring>Knowledge Management>Component Monitor>Services-->Schedulers.. my Schedular task status is <b>startup failed</b>...
    did u get the result for ur schedular task.. if yes,, plz guide me where I did error..
    thanks and regards,
    Chinnadurai.R

  • Scheduler Tasks in KM

    Hi,
    I created a task by following this blog:
    https://www.sdn.sap.com/sdn/weblogs.sdn?blog=/pub/wlg/1515
    It doesn't seem that my job is starting up.  Where do I go to look at a log of an execution?  Do I need to stop and restart the J2EE engine in order for the scheduler jobs to start up?  (I am on NW2004)
    My steps were:
    1. Create portal application project
    2. Create the Respository Framework 7.1.5 Schduler Task wizard
    3. Put my java code in the "run" method - I did execute the same code in a standalone project to be sure it doesn't contain bugs.
    4. Created PAR file and uploaded to portal server
    5. Configured the Scheduler task as shown in the BLOG- I was not sure if I should check off a CM System- I have tried both ways and it doesn't seem to run either way.
    Any help would be appreciated.
    Thanks.

    Hi Dana,
    You can use the standalone log-viewer to view the log files. See the documentation on sap help. http://help.sap.com/saphelp_nw04/helpdata/en/47/209779bbe64a318454b64148a0c76d/frameset.htm
    The best way would be to include some tracing and logging statements in your scheduler code.
    Create a new location in your code
    private static Location logger = Location.getLocation("mylocation");
    and put some trace statements in your code
    logger.intoT("start of method");
    But you will have to create a new location in Log Configurator in the VA and set the severity level to INFO. Then in the default.trc you can filter on your location name to get the relevant traces.
    Akhilesh

  • Deployed KM Scheduler Task Does Not Appear in Global Services / Scheduler T

    Hi All,
    I've deployed a portal service and a KM scheduler task in the same DC but cannot see the scheduler task listed under System Admin -> System Config -> Knowledge Management -> Content Management -> Global Services -> Scheduler Tasks.
    The service works correctly and performs its periodic processing once on initialisation of the service, and I can see the resulting log statements to make sure it has worked.
    Both the service and the scheduler task are packed inside the same DC, which builds and deploys without any errors.
    There are no errors in the log regarding the deployment of the DC, or the scheduler task.
    There is a log statement about registering the classloader for the DC, which I assume is the statement in the IRFServiceWrapper init() that goes:
    CrtClassLoaderRegistry.addClassLoader(this.getKey(), this.getClass().getClassLoader());
    But I still dont see the task listed in Global Services -> Scheduler Tasks.
    Does anyone know what might be causing this or how to diagnose the problem further?
    Cheers,
    Steve

    Hi Srini,
    No it doesn't it just has the run method which is generated automatically.
    I have created a local Portal Application project, which is not in a DC, and this also does not have a default constructor ether but appears in the Scheduler Tasks list as soon as it is deployed.
    I also tried to create a Portal Applicaiton DC and Portal Applicaiton (Packaged as SDA) DC and despite the scheduler task being the same, both the DC tasks do not appear in the Scheduler Tasks.
    The only one I can get to work is the local Portal Application project. This is no use as we cant store this in DTR (unless someone can explain how to do this???).
    The Portal Application project packages up the RF Framework JARS inside its PAR file, but the DC and SDA projects dont, so I tried including them via an Assembly Public Part to an External Library DC, which does include the JARs in the deployment files but they still dont appear in the Scheduler Tasks.
    Has anyone out there got a working Scheduler Task in a Portal Application DC?
    Cheers,
    Steve

  • KM Scheduler Task Error on SP16

    Hi All,
    I am trying to create a KM Scheduler Task. However while starting the task it gives me this error.
    [code]Configuration Error:  Failed to load task com.wyeth.clinicaltrials.jobs.PubstratFeed[/code]
    This is the error that is shown on the component Monitor under System Administration->Monitring->Knowledege Management->Component Monitor.
    If I click on the properties under this task it throws the following nullpointerexception
    [code]java.lang.NullPointerException
            at com.sapportals.wcm.service.scheduler.SchedulerEntry.getDescription(SchedulerEntry.java:357)
            at com.sapportals.wcm.service.scheduler.crt.SchedulerEntryProxy.getDescription(SchedulerEntryProxy.java:102)
            at com.sapportals.wcm.repository.manager.crt.CrtPropertyManager.getProperties(CrtPropertyManager.java:340)
            at com.sapportals.wcm.repository.ResourceImpl.internalGetProperties(ResourceImpl.java:3620)
            at com.sapportals.wcm.repository.ResourceImpl.getProperties(ResourceImpl.java:1209)
            at com.sapportals.wcm.control.edit.PropertiesControl.initialize(PropertiesControl.java:1058)
            at com.sapportals.wdf.stack.Control.initializeImpl(Control.java:449)
            at com.sapportals.wdf.stack.Pane.initialize(Pane.java:510)
            at com.sapportals.wdf.stack.PaneStack.initialize(PaneStack.java:509)
            at com.sapportals.wdf.stack.Pane.initialize(Pane.java:504)
            at com.sapportals.wdf.stack.PaneStack.initialize(PaneStack.java:509)
            at com.sapportals.wdf.stack.Pane.initialize(Pane.java:504)
            at com.sapportals.wdf.stack.PaneStack.initialize(PaneStack.java:509)
            at com.sapportals.wdf.WdfCompositeController.doInitialization(WdfCompositeController.java:279)
            at com.sapportals.wdf.WdfCompositeController.buildComposition(WdfCompositeController.java:659)
            at com.sapportals.htmlb.AbstractCompositeComponent.preRender(AbstractCompositeComponent.java:33)
            at com.sapportals.htmlb.Container.preRender(Container.java:120)
            at com.sapportals.htmlb.Container.preRender(Container.java:120)
            at com.sapportals.htmlb.Container.preRender(Container.java:120)
            at com.sapportals.portal.htmlb.PrtContext.render(PrtContext.java:414)
            at com.sapportals.htmlb.page.DynPage.doOutput(DynPage.java:237)
            at com.sapportals.wcm.portal.component.base.KMControllerDynPage.doOutput(KMControllerDynPage.java:130)
            at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:129)
            at com.sapportals.portal.htmlb.page.PageProcessorComponent.doContent(PageProcessorComponent.java:134)
            at com.sapportals.wcm.portal.component.base.ControllerComponent.doContent(ControllerComponent.java:73)
            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:545)
            at java.security.AccessController.doPrivileged(AccessController.java:204)
            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(AccessController.java:180)
            at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
            at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)[/code]
    I am using the SP16 Developer studio to create the scheduler task. There is nothing in the scheduler task just a log message. Still this fails. Is this a bug or I am missing something here.
    I would really appreciate any help in this regards.
    Thanks
    Ankur

    Hi,
    just a guess - do you have your Description field filled in your CM configuration for task? From the trace it seems it could not read the property DESCRIPTION from the Cm configuration.
    Just check it...
    Romano

  • KM Scheduler Task in 7.4

    Hi All,
    I am working with SAP Netweaver 7.4 SP04.  I want to create KM Scheduler Task to execute some of the KM functionalities on the predefined interval.  I came across Scheduler Jobs & Tasks (Developing and Scheduling Jobs -  Using Central Development Services - SAP Library) looks different to me.
    Kindly show some light for developing KM Scheduler Task in 7.4.  Please refer the attached screenshot for your information.
    Regards,
    Venkatesh K

    Hello Venkatesh,
    could you please come back and mark your last post as the correct answer? This way it will be highlighted and appear in your first post. It's easier to find then. Thank you!
    Regards,
    Steffi.

  • Call Multiple Files From Single ColdFusion Scheduled Task

    Our host only allows us to have 5 scheduled tasks per account but we need to run cfml applications to import data for multiple sites (at least 15 processes).  What I'd like to do is combine all the 'sample requests' for all sites into ONE scheduled task that will run them one after another thus cutting back on the number of scheduled tasks needed.
    We're using ColdFusion to connect to a MySQL DB to gather all sample requests. First the app retrieves all the unflagged records from a remote db then begins looping through all the returned records. On the each loop, the app 'scrubs' the data by properly formatting phone numbers, fixing address abbreviations, etc. Next the app saves the scrubbed data to a local MS SQL table then starts the loop over on the next row. Lastly the app sends out an email saying it has completed successfully.
    What I'm trying to do is Create a New Parent App that will run as a scheduled task to do the following:
    - New Parent App Runs as Scheduled Task and calls/includes first of X sample request app files
    - New Parent App runs first sample request app as described above (which can take up to a minute to process)
    - Parent app waits until after first sample request app completes, then Parent App goes on to second sample request app, etc.
    - After all sample requests are complete New App sends completion email with date and time
    The problem I'm having is getting the scheduled task to wait for apppage1.cfm to finish before loading apppage2.cfm and so on. Can you give me a simple codeset that accomplishes this?
    I've attached a sample of the include page the needs to complete before moving on!

    Our approach is a bit more comprehensive.
    First, we (meaning my co-workers) wrote a custom tag that does something like this:
    <cftry>
    <cfinclude the template>
    <cfcatch>
    log any errors
    Then our actual scheduled job go like this:
    set a really long timeout (and none of the actual jobs can have their own timeout)
    set some variables
    use the custom tag for each job we want to run
    send mail if any errors occurred.

Maybe you are looking for