Skip to content

You may schedule any operation to be executed in the future and at regular intervals.

Steps

  1. Sign in as a user with at least the Application Administrator capability global role assignment.

  2. Go to MANAGE > Schedules in the banner.

  3. Choose an object from the repository on which you will schedule an action.

You may pick any number of like objects. The selection of operations will change accordingly.

  1. From here you may pick any of the following:

  2. Delete operation logs: Permanently deletes completed operations and their logs older than a specified number of days. You cannot delete the original import operation log of versions available in the repository. They are automatically deleted when you delete their versions. Check 'Failed only' to delete logs of failed operations or uncheck to delete logs of all operations (successful and failed). If you only need to delete the logs that belong to unused versions you only need to call "delete unused versions".

  3. Delete system log: Delete the system logs older than 7 days (number of days may be specified).

  4. Delete unused versions: Permanently deletes model versions not used (linked) in any configurations and the logs associated with them

  5. Export Analytics: Export data for usage analytics reporting.

  6. Import new version of model(s): Import new version of imported model

  7. Import new model(s) from folder: Import new versions of imported model of all file based imported models recursively located within a folder

  8. Import users from an external file: Updates the users from the conf/UserDirectory.csv. Please copy the template file from Templates directory and populate the CSV. Merges existing users, removes users not part of the file and creates new users

  9. Retain maximum versions: Retain a specified maximum number of versions including the latest version and any used versions that will never be deleted

  10. Run Database Maintenance: Run Database Maintenance

  11. Send schedule notifications: Send notifications to model watchers, workflow roles and/or mentions.

  12. Sync physical data model(s) with database: Synchronize the physical data model(s) with the database

  13. Test performance: Evaluates overall server performance and prints summary report

  14. Update default configuration versions: Update and build this configuration in order to use the latest or published version of its models

Explorer Further

Enable / Disable Schedules

  1. In addition, you may use the toggle to Enable or Disable a schedule.

When disabled, a schedule will not run even though it has a recurring time.

One may multi-select and enable or disable multiple schedules.

When hovering over the Start or End time, you may also see these times as UTC.

Log messages are printed with the Server time, which may be obtained by going to MANAGE > System.

Repository Wide Operations

Many operations simply apply to the entire repository, e.g., Test Performance. You may simply select the Repository as a whole for these operations to be available or leave it blank and the Object field will be filled with Repository.

Additional Operation Parameters

Some operations have additional parameters which may be set, e.g., Delete Unused Versions, which has a Days parameter indicating the number of days in history to NOT delete.

In this case, only those versions of object in the Demo Enterprise Architecture folder which are more than several days old will be considered for deletion.

Scheduled Task Details

You may right-click on a schedule and see the details of the object being operated on.

Example

Right-click the any schedule and select Show in Repository Manager.

Schedule Activity at a Glance

You may see the following for each scheduled task:

  • Name -- Name given when schedule was defined

  • Object -- Impacted object

  • Operation -- The operation name applied to the Object

  • Last Execution Time -- Date and time when the scheduled task was last executed.

A manual execution of the schedule will also be recorded here.

  • Last Execution Duration -- length of time for the last execution

  • Last Execution Status -- Completion status for the last execution

  • Next Start Time -- Date and time when the scheduled task will next execute.

  • Definition -- Definition given when schedule was defined.

Execution History

One may see the history of execution with this tab.

Steps

  1. Click the schedule you want to check.

  2. Go to the Execution History tab.

Example

Run Database Maintenance on Schedule

To perform periodic maintenance on the database.

Steps

  1. Sign in as a user with at least the A .

  2. Go to MANAGE > System in the banner.

  3. Run Database Maintenance

The database maintenance is a multi-step operation, including:

  • it will perform actual purge of model data

  • it will maintain the database tables and indexes

  • it will maintain the search index

The database purge of deleted models is limited to a maximum of 2 hours per database maintenance execution. Therefore, if you have not deleted / cleaned up your models for a long time, it will take several database maintenance executions to purge all deleted models.

Migrating Schedules

When upgrading to a new major release version of the software, it may be necessary to migrate the repository database and then re-index much of the metadata. In order to ensure that the indexing process can complete in a timely manner, all scheduled harvests are disabled.

Once the indexing is complete you may re-enable these schedules.