Skip to main content
Solved

How to Store Scheduler Job Execution History into Apache Derby?


Forum|alt.badge.img

I'm working on workflows on my local machine and have set up a scheduler to trigger every 10 minutes. Each time the workflow runs, I would like to capture the following details from the job execution history, such as: Execution Date, Execution State, Executed Action ID, Details.
 

I am using Apache Derby as my database and would like to store this information there. Please let me know if there is a way to retrieve the above-mentioned details and store them in my database.

Thank you for your assistance.

Best regards,
Dhaval

Best answer by AKislyakov

Hi ​@DhavalM 

I don’t have Derby at hand, so here is example that uses Postgree SQL.

For Derby, you need to adjust

  1. ext datasource connection in wfl_db.runtimeConfig file
  1. Path and name of the dialect file in the dialectFile tag in the wfl_db.serverConfig file
View original
Did this topic help you find an answer to your question?

11 replies

Forum|alt.badge.img+2
  • Ataccamer
  • 164 replies
  • May 23, 2025

Hi ​@DhavalM 

The easiest way to achieve this is to switch Scheduler component to database persistence (Scheduler Server Component :: Ataccama ONE)
In this case all execution states will be stored to the database tables as described in Workflow and Scheduler Database Persistence Tables :: Ataccama ONE


Forum|alt.badge.img
  • Author
  • Data Pioneer
  • 7 replies
  • May 29, 2025

Hi ​@AKislyakov ,

Thank you for providing the solution to my question. I appreciate it. However, I'm still unsure how to execute it. I’ve tried several approaches, but I couldn't find a clear step that explains how to store the execution states in my database tables. If possible, could you please share more detailed instructions or a small demo workflow/plan file that demonstrates how to set this up?

Thanks in advance!

Best regards,
Dhaval


Forum|alt.badge.img+2
  • Ataccamer
  • 164 replies
  • Answer
  • June 3, 2025

Hi ​@DhavalM 

I don’t have Derby at hand, so here is example that uses Postgree SQL.

For Derby, you need to adjust

  1. ext datasource connection in wfl_db.runtimeConfig file
  1. Path and name of the dialect file in the dialectFile tag in the wfl_db.serverConfig file

Forum|alt.badge.img
  • Author
  • Data Pioneer
  • 7 replies
  • June 4, 2025

Thanks a lot, ​@AKislyakov , for taking the time to share the ZIP file. I really appreciate your effort.


Forum|alt.badge.img
  • Author
  • Data Pioneer
  • 7 replies
  • June 17, 2025

I’ve configured the server and runtime, but I’m still unclear on how to use SCHDEF_JOB_EXEC_STATE. Specifically, where am I supposed to use this command to store details about the schedule executions?


Forum|alt.badge.img+2
  • Ataccamer
  • 164 replies
  • June 17, 2025

The runtime server will create table SCHDEF_JOB_EXEC_STATE and will use it to store execution details.


Forum|alt.badge.img
  • Author
  • Data Pioneer
  • 7 replies
  • June 17, 2025

I’m unable to see the table in my DB Explorer. I’m using the default Apache Derby in the IDE, and here is the runtime config’s screenshot
 

 below is the configuration for the serverconfig as you suggested 
 


can you please guide me if this is the correct configuration?


Forum|alt.badge.img+2
  • Ataccamer
  • 164 replies
  • June 17, 2025

Configuration seems correct, do you have any schedules defined and executed? What is shown on the Job Details page (the one in the topic header)


Forum|alt.badge.img
  • Author
  • Data Pioneer
  • 7 replies
  • June 17, 2025
my scheduler file

is this what you are referring to?


Forum|alt.badge.img+2
  • Ataccamer
  • 164 replies
  • June 17, 2025

If your configuration is as shown, the data for this page should be fetched from the database. Maybe re-check connection details and try to refresh list of tables.


Forum|alt.badge.img
  • Author
  • Data Pioneer
  • 7 replies
  • June 17, 2025

I just reconnected the database, and it is working now. Thank you so much ​@AKislyakov 

 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings