Execution Packages

Note: This article is intended for database administrators. Ensure the following tasks are completed by someone with the appropriate database administration privileges.

Jet Analytics Execution Service

To schedule execution packages, you must first Configure the Jet Analytics Execution Service and include the instances you want to schedule. Go to Services and verify that the Jet Analytics Execution Service is running. Right-click on the Jet Analytics Execution Service and set the Startup Type to Automatic (Delayed Start).

Execution Packages

Adding execution packages in Prepare and Deliver instances

To add an execution package to a Prepare instance, expand the instance in the Solution Explorer and open the Execution tab.

Right-click on Execution packages and select Add Execution Package.

To add an execution package to a Deliver instance, expand the Deliver instance in the Solution Explorer and open the Execution tab.

Right-click on Execution packages and select Add Execution Package.

Configuring an execution package

An execution package determines which objects in an instance will be executed and how. The configuration window differs slightly between Prepare and Deliver instances.

To configure an execution package, follow the steps below.

1. Enter a Name for the execution package.
2. On the Include/Exclude Steps tab, choose the steps to include or exclude by dragging objects from All Steps to Include Steps or Exclude Steps respectively. For example, drag the Execute Instance step to Included Steps to execute the entire instance. To exclude everything except specific steps, drag those steps to Exclude Steps. Right-click an object and click Remove Step to remove it from either list.
3. (Optional) On the Concurrent packages tab, select other packages that can execute concurrently with this one. By default, two packages from the same instance will not run simultaneously unless explicitly permitted.
   Note:

   When you set package A to execute concurrently with package B, package B is also set to execute concurrently with package A. This means you cannot use this setting to allow A to run while B is running while also preventing B from running while A is running.

4. Enter the maximum number of steps that can run in parallel in Max. Threads. The optimal number depends on server resources — too few threads result in slower execution, while too many can make the server slow or unresponsive.
5. Clear the Log Execution time and/or Log Row Count checkboxes if you do not want to log this information.
   Note:

   The Log Row Count option is only available for Prepare instances.

6. Select a setting for Managed Execution:
   • Disabled: Managed execution is off. Objects are executed in the order they appear in the tree.

     When managed execution is disabled, tables execute in the order they appear in the tree. Ensure tables are executed in a logical order to avoid errors — for example, an Order table must execute before the related Order Detail table. Tables can be reordered using drag-and-drop or Alt+Up/Down.

   • Execution Number: When more than one object is ready to execute, Jet Analytics Data Integration prioritizes objects based on their position in the tree from top to bottom.
   • Classification: Objects are prioritized by table classification in the following order: Fact Table – Large, Fact Table, Dimension Table – Large, Dimension Table. When two tables share the same classification, execution number is used as the secondary criterion.
   • Execution Time: Objects are prioritized by average execution time, with the longest-running object executing first. When two objects share the same execution time (e.g. new objects), execution number is used as the secondary criterion. This option typically results in the shortest overall execution time once execution times are known.
7. Check Merge Steps to treat all individual sub-steps of the chosen steps as one collection. This can speed up execution.
8. (Optional) In the Prioritization list, select the prioritization to apply to this execution package. See Adding a Prioritization below for more information.
9. Under Failure Handling, select the Action to take if execution fails:
   • Fail Package: When a step fails, execution stops and the package is declared failed.
   • Retry Step: When a step fails, it is retried until the maximum number of retries is reached. Enter the maximum retries for the package in Retries, the maximum retries per step in Retries per Step, and the wait time between retries in Retry delay in minutes. See Setting up retry steps for more information.
10. Under Post Execution, select a Notification on Success and a Notification on Failure. Notifications must be created before they are available in this list. See Adding a Notification below.
11. To run another package after a successful execution, select it under Run Package.
12. Click OK to add the execution package.

Adding a Notification for an Execution Package

Notifications alert specified individuals when an execution package succeeds or fails. They are most commonly configured as email alerts but can also write to the Windows Event Log.

1. On the Execution tab, right-click Notifications and click Add Notification. The Notification window appears.

   

2. Enter a Name for the notification and select the Type:

   Option	Description
   Mail	Creates an email notification.
   EventLog	Writes a notification to the Windows Event Log.
   Both	Creates both an email notification and writes to the Event Log.

3. Enter the SMTP server details under Mail Server.
   • Since October 2022, Microsoft has ended basic authentication for online SMTP servers. To work around this, provide an Application (client) ID and your company's Tenant ID. The app requires the following permissions:

     

     • The app must have Mail.Send, SMTP.Send, and User.Read permissions.
     • An admin must grant consent for all three permissions.
     • The user account used as the From Email address and Username must not have Multi-Factor Authentication enabled.
   • If using Gmail, a standard password cannot be used. Enable 2-step verification on the email account and use an App Password in the password field.
4. Enter the recipient email addresses and a Subject under Mail Recipient. The following variables can be used in the subject line:
   • %Instance% — the name of the instance
   • %Status% — the execution status (Success / Fail)
   • %ExecutionPackage% — the name of the execution package
5. Click OK.

The notification is now available for selection when creating or editing an execution package.

Adding a Prioritization to an Execution Package

Prioritizations allow you to specify which objects should be executed first during a managed execution. This is useful when, for example, only a short time window is available for data extraction, or when a specific model needs to be ready for users as early as possible.

1. On the Execution tab, right-click Prioritizations and click Add Prioritization.
2. In Name, enter a name for the prioritization.
3. Drag and drop objects from the Available Objects tree to Selected Objects to add them to the prioritized set.
4. Click an object in Selected Objects to display its execution steps under Object Settings. Select or clear individual steps under Selected steps to specify exactly which steps are prioritized — for example, prioritizing only the data transfer for a specific table.
5. Select Blocking to halt all other execution tasks until the selected steps for the selected object have completed.
6. Click OK to create the prioritization.

Adding a Usage Condition to an Execution Package

A usage condition restricts an execution package to run only when specific conditions are met. To add a usage condition, follow the steps below.

1. Right-click on the instance and select Instance Variables to add the instance variable you want to use in the condition.
2. On the Execution tab, expand Execution Packages, right-click the relevant package, and click Add Usage Condition. The Usage Condition pane appears on the right.
3. Click the variable you want to use from the list of available instance variables.
4. In the Operator list, select the operator to use.
5. In the Comparer list, select the data type to use when comparing the variable to the value.
6. In the Value box, enter the value to compare the variable against.
7. Click Add to add the usage condition.

If you attempt to manually execute a package with a usage condition that evaluates to true, a warning message will appear. The same message will be written to the log if the package is triggered by a scheduled execution.

On-Demand Ingestion

When the Data on demand option is enabled, the data source transfers data into Ingest instance storage before the Prepare instance ingests it. This works without configuring an explicit Transfer task under the data source.

1. In Jet Analytics Data Integration, right-click the data source and select Edit Data Source.
2. Click Advanced Settings.
3. Check the Data on demand box.

   

Scheduling an Execution Package

Schedule Jet Analytics execution packages using Jet Analytics Orchestration. See the Jet Analytics Orchestration documentation for scheduling instructions.