11/13/2022 0 Comments Definition if analytical sandvox![]() A group of users need to be members of both the Sandbox and Production Sites to promote content from the Sandbox site to the Production site.Otherwise the job will be “untagged” and be directed to the Sandbox Worker in the above scenario. The Job Tag must be specified when the Schedule is created, or when an on-demand job is being submitted, under the Advanced Settings panel.Users with the “Consumer” role cannot select a Job Tag. The ability to specify a Job Tag at workflow execution time is restricted to Contributors, Data Stewards, and Site Admins.A user specifying a job tag before running a workflow.An example Production Worker configuration with a “Production” Job Tag, and configured not to execute untagged jobs.Additionally, if a user submits a job and does not specify a job tag, the workflow execution would occur on the Sandbox worker where untagged jobs are allowed, and not the Production worker. This approach provides a dedicated Worker for production jobs, which prevents development and debugging jobs from tying up the job queue, which could block production jobs from being able to run. An architectural diagram of the environment is depicted above. Additionally, the Sandbox worker should also be configured to run untagged jobs. One tagged for “ Sandbox” jobs and the other tagged for “ Production” jobs. The Analytics Hub environment should include at least two Workers. Production – where all curated data assets and workflows are uploaded and scheduled.Here users can define new data connections, upload, and collaborate on new workflows and analytic apps. Sandbox – where all development and testing work takes place.This example Sandbox Strategy for Analytics Hub is to creates two Sites: Job Tags allow users to direct the execution of a particular workflow run or schedule to a specific Worker (Alteryx computing engine).All content in a Site is completely walled off from other Sites. Sites are separate and secure areas to store data files, run workflows, and collaborate with other users.Sites were introduced in Alteryx Analytics Hub at inception, Job Tags are introduced in the 2020.4 version. This sandbox strategy for Analytics Hub is based on two key concepts, Sites and Job Tags. Alteryx Analytics Hub 2020.4 has added functionality that provides for a sandbox development environment while streamlining user administration, ultimately providing easy workflow promotion from the sandbox to production. This article walks through a Sandbox strategy for Alteryx Analytics Hub, and applies to Analytics Hub version 2020.4. A recommended best practice from Alteryx is to leverage a “Sandbox” environment for developing and testing Workflows, data connections, user configurations, and other settings before publishing to a production environment. But, sandboxes can be difficult to manage … until now. Sandboxing protects an organization’s production data, programs, and other content from changes that could be damaging to mission-critical systems. For questions, please reach out to your Alteryx representative.Ī sandbox is a development and testing environment isolated from a production environment or repository. Version 21.1 and newer includes a set of Sandbox licenses for a separate Sandbox environment. NOTE: The following article applies to Analytics Hub 20.4 only. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |