Skip to main content

Scheduling Execution Packages in TimeXtender Orchestration

  • November 13, 2024
  • 2 replies
  • 437 views
Scheduling Execution Packages in TimeXtender Orchestration
Christian Hauggaard
Community Manager
Forum|alt.badge.img+5

Note: Jobs have been deprecated. Please schedule TDI execution packages via TimeXtender Orchestration, as described in this article, rather than using jobs 

Instead of managing TimeXtender Data Integration (TDI) executions as Jobs, you can now orchestrate your Tasks and Execution Packages directly. This change eliminates redundant groupings, making setup easier and more intuitive. You’ll spend less time figuring out what to run and more time getting results. Furthermore, TimeXtender Orchestration ensures real-time command execution, when you hit Run, TimeXtender Orchestration immediately starts executions. TimeXtender Orchestration provides enhanced logging and transparency - with all log details, execution statuses, error messages, task logs available in one place.

Prerequisites

  1. Get access to TimeXtender Orchestration:
    • Go to the waffle menu in the top right corner of the TimeXtender Portal

       

    • Click Unlock Orchestration
    • Select which user should be account admin in TimeXtender Orchestration
    • Click the Unlock Orchestration button
  2. Create an API Key in the TimeXtender Portal
  3. The TimeXtender Execution Service must be running and configured to allow Orchestration to be able to run packages. See Configure the TimeXtender Execution Service for more information on how to configure the TimeXtender Execution Service. 

Schedule an Execution in TimeXtender Orchestration

Note: When requesting access to TimeXtender Orchestration as defined in Step 1 in the above prerequisites, we auto-generate an API-key for you during the creation process and auto-generate a the Data Provider in Orchestration in the creation process, which means you can jump right in. If you dont want to use that key, you can always go to TDI Portal and generate a new one!

  1. Add a TDI Data Provider in TimeXtender Orchestration using your API key:
    • Right click Data Providers under General in the Object Explorer
    • Select New... > Data Provider 
    • Provide a title and click OK
    • Click Datasource Type and select TimeXtender Data Integration
    • Paste your API key into the api key field in the connection pane, save it, click Sync with TDI…
    • Select a system to create/move tasks to and click OK
    • Refresh the object explorer
  2. Add Ingest task and Prepare/Deliver execution packages in TimeXtender Orchestration
    • Right-click Packages
    • Select New... > TimeXtender Ingest/Prepare/Deliver
    • Give the package a name
    • Select the Data Provider you created in Step 1 above
    • Save the package
    • Manually run the package to test it by clicking the Run button and then Run Task
  3. Schedule the execution by using a Schedule Group. For more information, see Schedule Objects
    • Right-click Schedule Groups in the Object Explorer and select New... > Schedule Group
    • Drag the TimeXtender Ingest/Prepare/Deliver packages into the Schedule Group
    • Select whether they should run in Sequence or Parallel
    • Setup the schedule for the execution in the bottom Trigger pane and click Save

Execution History

To view all execution log details:
  1. Open TimeXtender Orchestration
  2. Navigate to General > Audit History in the Object Explorer and select Execution History
  3. Click the i icon, on the right-hand side of the relevant package, to see execution details and all the information from the TDI logs

Seamless Navigation

Moving between TDI and TimeXtender Orchestration is now a breeze. You’ll find a handy button in TDI that opens TimeXtender Orchestration directly. Easily located, right next to XPilot

Note: The TimeXtender Orchestration navigation button is displayed if TimeXtender Data Integration and TimeXtender Orchestration are installed on the same machine.

Parallel Executions of Execution Packages

Parallel Execution of Non-Dependent Execution Packages within the same instance

If you are working with multiple non-dependent packages (i.e. packages that do not contain the same objects), these can be execute in parallel by setting up concurrent packages. To configure execution packages to run concurrently, edit your execution package and go to the Concurrent packages tab and select which packages can run concurrently.

Parallel Execution of Execution Packages in different Prepare instances

You can execute execution packages in different Prepare instances in parallel, simply drag the TimeXtender Prepare packages into the schedule group and ensure the Parallel property is set to Parallel.

 

Parallel Execution of Execution Packages in different Deliver instances

You can execute execution packages in different Deliver instances in parallel, simply drag the TimeXtender Deliver packages into the schedule group and ensure the Parallel property is set to Parallel.

Note: This requires setting the Max degree of Deliver instance parallelism. This setting determines how many deliver instances can be executed at the same time (i.e. in parallel) by the execution service. You can also setup multiple VMs each with an execution service, and use each execution service to execute a specific deliver instance(s).

Troubleshooting

For troubleshooting issues related to scheduled TDI executions in TimeXtender Orchestration, please see: 

 

Did this topic help you find an answer to your question?

2 replies

rvgfox
Problem Solver
Forum|alt.badge.img+4
  • Problem Solver
  • 222 replies
  • November 13, 2024

@Christian Hauggaard I’m using Exmon tu run my TX Jobs.

I’m using the version:

I need the jobs execution in parallel.

How can start to use it?

Where is the new version of Exmon?

I’ve several Jobs in TX created in Exmon as packages. All the jobs really are Execution Packages in TX.

How to use the new funcionality?


Christian Hauggaard
Community Manager
Forum|alt.badge.img+5

Hi ​@rvgfox I have created a support ticket for your questions above


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