Configuring environment execution profiles - Data360_DQ+ - Latest

Data360 DQ+ Help

Product type
Software
Portfolio
Verify
Product family
Data360
Product
Data360 DQ+
Version
Latest
Language
English
Product name
Data360 DQ+
Title
Data360 DQ+ Help
Copyright
2024
First publish date
2016
ft:lastEdition
2024-07-09
ft:lastPublication
2024-07-09T15:09:58.774265

The properties on the Execution Profile tab enable you to set execution settings that can be inherited by data views and analyses on the selected environment.

  1. From the menu at the top of the screen, select Admin > Environments.
  2. To edit an existing environment, select the environment that you want to edit from the list on the left of the screen.
  3. Select the Execution Profile tab.

In this topic:

Creating a new execution profile

  1. Click New to open the Add Execution Profile dialog.
  2. Enter a name for the new profile.
  3. Select Execution Sizing to edit the execution settings, as needed. If you need assistance with these settings, please contact Precisely Support.
    • Choose Cluster Type based on their configuration;
      1. Dedicated Cluster - These are on-demand temporary clusters created for each job and terminates after the job completes. The bootstrap time for these cluster/ jobs are largely constant, around 10 minutes on AWS, which is largely dictated by AWS resource provisioning and initialization time. It does not change much with data volume, as your data volume goes up, its percentage shrinks.
      2. Shared Cluster - This is pre-provisioned/always on cluster that accepts multiple jobs, with limited auto scaling capacity, jobs maybe queued when capacity is full with running jobs. because its pre-provisioned, the bootstrap time for shared is typically much shorter than dedicated, say 2 minutes, but can vary a great deal due to queuing when many jobs are running.
    • Selecting Configure Sharing allows you to add the following details,
      1. Step Concurrency Level - It is the number of concurrent steps (jobs) the dedicated cluster can accommodate before the job waits. The default value is 2.
      2. Shutdown Idle Timeout (Minutes) - It is the time after which if there are no new arrives to execute, the cluster shutdowns via the new EMR ability. The default time is 60 minutes and maximum time that can configured is 120 minutes.
  4. Select Execution Properties then click Yes to enable if you want to create new execution properties to include in the profile.
  5. Click Apply Changes to close the Add Execution Profile dialog.
  6. Click Save Changes.
Tip: The execution profiles that you create on this page will be available for users to select when editing the settings of an analysis or a data view.

Editing an execution profile

  1. Click the menu button to the right of the profile that you want to edit and select Edit to open the Edit Execution Profile dialog.
  2. Edit the properties as needed.
  3. Click Apply Changes to close the Edit Execution Profile dialog.
  4. Click Save Changes.
Note: If you edit an execution profile that is referenced by an analysis or a data view, you will need to navigate to the analysis or data view and manually associate it with the execution profile again. Execution profile references are not maintained if the profile is edited or deleted.

Deleting an execution profile

  1. Click the menu button to the right of the profile that you want to delete and select Delete.
  2. Click Yes, delete to confirm that you want to delete the selected profile.
  3. Click Save Changes.
Note: If you delete an execution profile that is referenced by an analysis or a data view, you will need to navigate to the analysis or data view and reconfigure the execution settings. Execution profile references are not maintained if the profile is edited or deleted.

Administering execution profiles across environments

When importing or promoting an analysis or data view that references an execution profile to a new environment, the system will check if the execution profile exists in the target environment. If the execution profile does not already exist on the target environment, a new empty execution profile is created. The new profile will have the same name as the profile in the source environment, but will not contain the configuration details.

You will need to configure the details of the new execution profile on the target environment to enable the successful execution of any imported or promoted data stages that reference the profile. For example:

  1. "Execution Profile 1" exists only on "Environment A".
  2. You have an analysis on "Environment A" which inherits the execution settings from "Execution Profile 1".
  3. You promote the analysis from "Environment A" to "Environment B".
  4. "Environment B" does not have "Execution Profile 1".
  5. As part of the promotion, the system automatically creates a new, empty, "Execution Profile 1" on "Environment B". You can check this by navigating to the Admin > Environments page, and selecting the Execution Profile tab on "Environment B".
  6. Click the menu button to the right of "Execution Profile 1" and select Edit to configure the details as needed.