Running a Job for an App - Teradata AppCenter

Teradata® AppCenter User Guide

Product
Teradata AppCenter
Release Number
2.0
Published
September 2020
Language
English (United States)
Last Update
2020-09-28
dita:mapPath
zzv1586527506119.ditamap
dita:ditavalPath
ft:empty
dita:id
B035-1111
Product Category
Analytical Ecosystem
"" User, Administrator

When you run a job for an app that runs once or on schedule, AppCenter prompts you to select the system to query, a Teradata Database, Teradata Vantage, or Aster Database system. The root user must first create a system that you specify when executing a job for this app type.

When required settings are completed, you can run the job for your app. You can run as many jobs as you want for apps that run once or on schedule. You can run only one job at a time for apps that run until stopped.

If email is configured, AppCenter sends you notification about job status.

For apps that run until stopped, you can open the app URL once the app is running.

  1. Select "" > Develop, then select the app.
  2. Select Select Start, then complete the settings with the following considerations:
    Setting Considerations
    System For apps that run once or on schedule:
    • If the administrator assigned a service account to this app, AppCenter automatically selects the Use service account with default system option and you do not need to enter credentials. You can clear the Use service account with default system selection and use a the same system with different credentials or a different system.
    • If the administrator did not assign a service account to this app, enter the system credentials.
    • If you select a Teradata system for which the root user assigned JWT as the Default Login Type when they created the system, AppCenter automatically selects Current Session for Authentication, and uses your current AppCenter login credentials. You can alternatively select Database or Corporate Login for authentication instead. This applies to Teradata systems only.
    Parameters (Optional)
    • If you did not add parameters when you created the app, skip this step.
    • AppCenter automatically hides Docker container image parameters not relevant to the job.
    • If you added required parameters when you created the app, select the associated settings.
    • If you selected Hidden for a parameter when you created the app, AppCenter hides that parameter when running the job.
    • If you added optional parameters when you created this app, select the associated settings or clear the parameters.
    • If you selected Upload as the parameter type when you created this app, click Browse.
    • For apps that run once or on schedule, if you selected the option Allow user to select multiple values from this query when you created this app, you can select the parameters you want to use for this query.
    • You can replace the default parameter text up to 5000 characters maximum.
    • For apps that run once or on schedule, AppCenter supports multibyte characters in job parameter names and values.
    Schedule (Optional) For apps that run once or on schedule:
    • If you select a schedule option and run the job, you cannot change the schedule later.
    • By default, AppCenter terminates the schedule if a job fails. Before running the job, you can clear the slider for Terminate schedule if a job fails to continue running the scheduled job, even if it fails.
    • AppCenter shows selected schedule options in Execution History.
    • The AppCenter UI provides the following time schedule options:
      • 30 Minutes
      • Hour
      • Day
      • Week
      • Month
      • Year

      You can use Jobs in the App Service API for more granular interval options.

    Title and description (Optional) For apps that run once or on schedule:
    • Title (name) and description are optional.
    • You can include both a name and description, only a name, or only a description.
    • If you add a name, AppCenter uses that as the job name in Execution History and in the AppCenter Overview.
    • If you add a description, AppCenter includes that under the job name in Execution History.
  3. [Optional] For job status, including any job parameters used, error messages, and links to results where applicable, select Execution History.