Create a Jet Analytics package¶

A Jet Analytics package runs an execution package from a Jet Analytics repository, so a Jet estate can be scheduled and monitored alongside the rest of your data platform.

Before you start¶

• A Jet Analytics repository reachable either from Timextender Cloud or through a gateway
• An execution package already defined in that repository. This type runs execution packages; it does not create them.

The selection chain¶

Gateway → repository → project → execution package. Each field loads the next, and each has a refresh button.

The gateway that runs the package. Timextender Cloud runs it without an on-premises gateway.

The Jet Analytics repository reachable through the selected gateway.

The project within the selected repository.

The execution package to run from the selected project.

The first line is worth noticing: unlike Command Line, this type can run in Timextender Cloud. A gateway is only needed when the repository sits on your network and is not reachable from the cloud — which, for an on-premises SQL Server holding a Jet Analytics repository, it usually is not.

Steps¶

1. Create the package¶

Orchestration → Packages → Create, then Jet Analytics from the Timextender area.

2. Choose the gateway, then the repository¶

3. Choose the project, then the execution package¶

Each loads from the selection above it.

4. Save¶

Saves as a Draft.

Best practices¶

Choose the gateway that can actually reach the repository. The repository list is fetched through the gateway, so an empty list is usually the wrong gateway rather than the wrong credentials.

Name the package for the execution package it runs, plus the environment if you have more than one repository. "Load the Jet finance mart" reads better in a schedule than a bare project name.

One package per execution package. The point of orchestrating these is seeing which one failed.

Re-pick after a rename. The package stores the reference it was configured with; renaming the project or execution package in Jet Analytics means reopening and re-selecting here.

Troubleshooting¶

The repository list is empty. The selected gateway cannot reach the repository, or its credentials cannot read it. Try the other gateway, or Timextender Cloud if the repository is reachable from the internet.

The project and execution package fields stay empty after picking a repository. A known issue: the Project and Execution package fields can come back empty after the repository connection resolves. Use the refresh buttons beside each field first; if they stay empty, check the connection's permissions on the repository database.

A project exists but is not listed. The repository connection points at a different repository — commonly a Test repository rather than Production.

The package runs but the execution package did nothing. Check in Jet Analytics what that execution package actually contains; an empty or disabled package succeeds without doing work.

Reference¶

Fields¶

Validation: Please select an O&DQ Gateway, Please select a repository, Please select a project, Please select an execution package.

One editor, two types¶

Jet Analytics uses the Timextender Classic editor — the rendered fields are the package_timextenderclassic_* controls, and the chain is identical. The two types differ in which repository they read, not in how they are configured.

Related¶

• Packages overview
• Create a Timextender Classic package — the same editor