Create a TimeXtender Classic package

A TimeXtender Classic package runs an execution package from a TimeXtender Classic repository. It lets a Classic estate be orchestrated, and migrated, from the same place as everything else.

Prerequisites

• A TimeXtender Classic 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

The fields follow a chain: Gateway > Repository > Project > Execution package. Each field loads the next, and each has a refresh button. The editor describes them as follows.

• Execution connection. The gateway that runs the package. Timextender Cloud runs it without an on-premises gateway.
• Repository. The Timextender repository reachable through the selected gateway.
• Project. The project within the selected repository.
• Execution package. The execution package to run from the selected project.

This type can run in TimeXtender Cloud. A gateway is needed when the repository sits on your network and is not reachable from the cloud, which is the usual case for an on-premises SQL Server holding a TimeXtender Classic repository.

Create the package

1. Go to Orchestration > Packages and select Create.
2. Select Timextender Classic from the Timextender area, then select Create.
3. Enter a name for the package.
4. Select the gateway, or TimeXtender Cloud, under Execution connection.
5. Select the Repository.
6. Select the Project, then the Execution package. Each loads from the selection above it.
7. Select Save. The package is saved as a Draft.

Best practices

• Choose the gateway that can reach the repository. The repository list is fetched through the gateway, so an empty list usually points to the gateway rather than to the credentials.
• Name the package for the execution package it runs, plus the environment if you have more than one repository. "Load the Classic sales warehouse" reads better in a schedule than a bare project name.
• Use one package per execution package. The point of orchestrating these is seeing which one failed.
• Select again after a rename. The package stores the reference it was configured with, so renaming the project or execution package in TimeXtender Classic means reopening the package and selecting again 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 selecting a repository. The repository connection resolved, but the credentials cannot read the project metadata. Select the refresh buttons, then 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 TimeXtender Classic what that execution package 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

This editor is shared with Jet Analytics. Both render the same fields and the same chain of gateway, repository, project and execution package, so the mechanics are identical.

Related articles

• Packages overview
• Create a Jet Analytics package, which uses the same editor