cancel
Showing results for 
Search instead for 
Did you mean: 

alteryx server Knowledge Base

Definitive answers from Server experts.
 You are using an unsupported browser for translation. Please switch to another browser.

This is the second article in a series on Alteryx Server backup and recovery. You can find Part 1 at:   Alteryx Server Backup & Recovery Part 1: Best Practices   As long as a backup of the Mongo database is available, you can get Alteryx Server back up and running. Luckily, backing up the embedded MongoDB is pretty simple, and can be done with a few console commands. I would recommend creating a batch file or script to perform the process. Doing so will allow you to schedule the backup using Windows Task Scheduler. The actual steps to perform a MongoDB backup are covered in detail in the online help under the server configuration section or at this direct link. I will also outline the steps below for completeness.   To create a backup of the MongoDB:   Stop AlteryxService. Execute the following command to save a backup of the database in the specified folder:   alteryxservice emongodump=<path to backup location> Restart AlteryxService   You can easily script this to a batch file with a few simple console commands. Keep in mind that paths may vary on your server, but it should look something like this.   Example:     "C:\Program Files\Alteryx\bin\AlteryxService.exe" stop "C:\Program Files\Alteryx\bin\AlteryxService.exe" emongodump=Z:\Path\MongoBackup "C:\Program Files\Alteryx\bin\AlteryxService.exe" start     You can add additional features, such as logging and date/time stamps, to the backups.  As an example of additional useful features to include with your backups, I have included the code for a batch script I created that adds the following information: logging with date/time stamping, a backup that is also date/time stamped, automated archival of the backup, copying the archive to a network location, and cleanup of the temp files.   Once you have a batch file or other script to perform your backups, you need to test the script to ensure it works properly. Once testing is done, the next step is to schedule the backup. The easiest way to do this is to use Windows Task Scheduler. To create a scheduled task on Windows 2012 Server, follow these steps:   Create a scheduled task:   Open Task Scheduler and click on “Create Task”   On the General tab, enter “Name”, “Description”, select “Run whether user is logged in or not", and select "Run with highest privileges"   On the Triggers tab, click “New”   A dialogue box will appear. Define the schedule (daily, weekly, etc...) on which you want the backup to run and click “OK”   On the Actions tab click “New”   On the dialogue window, make sure “Start a Program” is selected and click “Browse”. Select the batch file you created and click “Open”. Then click “OK”.   Click “OK” on the Create Task window to finalize the creation of the backup task.   Now that you have successfully implemented backup procedures and scheduled a task to automate the backups, it is time to discuss database restoration from a backup. The good news is that restoring the database is just as simple as backing it up. Assuming that 1) the server is functioning, 2) Alteryx Server is installed, and 3) you have a valid backup available, you can follow these simple steps outlined below.   To restore a backup of the MongoDB:   Stop AlteryxService Execute the following command to restore the backup:   alteryxservice emongorestore=<path to backup location>,<path to restore to>   Restart AlteryxService   This simplicity and same focus on command line statements means that we can also script recovery. However, since recovery actions are much less frequent, it probably isn't necessary. Instead, you would just connect to the server, open a command prompt and, following our backup example above, execute the following commands:   Example:     "C:\Program Files\Alteryx\bin\AlteryxService.exe" stop "C:\Program Files\Alteryx\bin\AlteryxService.exe" emongorestore=Z:\Path\MongoBackup,C:\ProgramData\Alteryx\Service\Persistence\MongoDB "C:\Program Files\Alteryx\bin\AlteryxService.exe" start     For Alteryx Server we also recommend backing up the controller token and some settings files. While the server can be recovered without these files. Having a backup of them can expedite the recovery process, and they will also ensure you will be able to decrypt any sensitive data in the database. The settings files we recommend backing up are:   C:\ProgramData\Alteryx\RuntimeSettings.xml C:\ProgramData\Alteryx\Engine\SystemAlias.xml C:\ProgramData\Alteryx\Engine\SystemConnections.xml   Again, please keep in mind the exact paths may vary depending on the server configuration and where the backup is located. This example also assumes the backup isn't compressed/archived. If you are using a backup script that archives the backup and copies it to network storage, you will need to copy the backup file to the server and decompress the archive before running the recovery commands above.     Below is the code for my sample batch script:   ::----------------------------------------------------------------------------- :: :: AlteryxServer Backup Script v.2.0 - 10/26/18 :: Created By: Kevin Powney :: :: Service start and stop checks adapted from example code by Eric Falsken :: ::----------------------------------------------------------------------------- @echo off ::----------------------------------------------------------------------------- :: Set variables for Log, Temp, Network, and Application Paths :: :: Please update these values as appropriate for your environment. Note :: that spaces should be avoided in the LogDir, TempDir, and NetworkDir paths. :: The trailing slash is also required for these paths. ::----------------------------------------------------------------------------- SET LogDir=C:\ProgramData\Alteryx\BackupLog\ SET TempDir=C:\Temp\ SET NetworkDir=\\ServerName\SharePath\ SET AlteryxService="C:\Program Files\Alteryx\bin\AlteryxService.exe" SET ZipUtil="C:\Program Files\7-Zip\7z.exe" :: Set the maximium time to wait for the service to start or stop in whole seconds. Default value is 2 hours. SET MaxServiceWait=7200 ::----------------------------------------------------------------------------- :: Set Date/Time to a usable format and create log ::----------------------------------------------------------------------------- FOR /f %%a IN ('WMIC OS GET LocalDateTime ^| FIND "."') DO SET DTS=%%a SET DateTime=%DTS:~0,4%%DTS:~4,2%%DTS:~6,2%_%DTS:~8,2%%DTS:~10,2%%DTS:~12,2% echo %date% %time%: Starting backup process > %LogDir%BackupLog%datetime%.log echo. >> %LogDir%BackupLog%datetime%.log ::----------------------------------------------------------------------------- :: Stop Alteryx Service ::----------------------------------------------------------------------------- echo %date% %time%: Stopping Alteryx Service >> %LogDir%BackupLog%datetime%.log echo. >> %LogDir%BackupLog%datetime%.log SET COUNT=0 :StopInitState SC query AlteryxService | FIND "STATE" | FIND "RUNNING" >> %LogDir%BackupLog%datetime%.log IF errorlevel 0 IF NOT errorlevel 1 GOTO StopService SC query AlteryxService | FIND "STATE" | FIND "STOPPED" >> %LogDir%BackupLog%datetime%.log IF errorlevel 0 IF NOT errorlevel 1 GOTO StopedService SC query AlteryxService | FIND "STATE" | FIND "PAUSED" >> %LogDir%BackupLog%datetime%.log IF errorlevel 0 IF NOT errorlevel 1 GOTO SystemError echo Service State is changing, waiting for service to resolve its state before making changes >> %LogDir%BackupLog%datetime%.log SC query AlteryxService | Find "STATE" timeout /t 1 /nobreak >NUL SET /A COUNT=%COUNT%+1 IF "%COUNT%" == "%MaxServiceWait%" GOTO SystemError GOTO StopInitState :StopService SET COUNT=0 SC stop AlteryxService >> %LogDir%BackupLog%datetime%.log GOTO StoppingService :StopServiceDelay echo Waiting for AlteryService to stop >> %LogDir%BackupLog%datetime%.log timeout /t 1 /nobreak >NUL SET /A COUNT=%COUNT%+1 IF "%COUNT%" == "%MaxServiceWait%" GOTO SystemError :StoppingService SC query AlteryxService | FIND "STATE" | FIND "STOPPED" >> %LogDir%BackupLog%datetime%.log IF errorlevel 1 GOTO StopServiceDelay :StopedService echo AlteryService is stopped >> %LogDir%BackupLog%datetime%.log ::----------------------------------------------------------------------------- :: Backup MongoDB to local temp directory. ::----------------------------------------------------------------------------- echo %date% %time%: Starting MongoDB Backup >> %LogDir%BackupLog%datetime%.log echo. >> %LogDir%BackupLog%datetime%.log %AlteryxService% emongodump=%TempDir%ServerBackup_%datetime%\Mongo >> %LogDir%BackupLog%datetime%.log ::----------------------------------------------------------------------------- :: Backup Config files to local temp directory. ::----------------------------------------------------------------------------- echo. >> %LogDir%BackupLog%datetime%.log echo %date% %time%: Backing up settings, connections, and aliases >> %LogDir%BackupLog%datetime%.log echo. >> %LogDir%BackupLog%datetime%.log copy %ProgramData%\Alteryx\RuntimeSettings.xml %TempDir%ServerBackup_%datetime%\RuntimeSettings.xml >> %LogDir%BackupLog%datetime%.log copy %ProgramData%\Alteryx\Engine\SystemAlias.xml %TempDir%ServerBackup_%datetime%\SystemAlias.xml copy %ProgramData%\Alteryx\Engine\SystemConnections.xml %TempDir%ServerBackup_%datetime%\SystemConnections.xml %AlteryxService% getserversecret > %TempDir%ServerBackup_%datetime%\ControllerToken.txt ::----------------------------------------------------------------------------- :: Restart Alteryx Service ::----------------------------------------------------------------------------- echo %date% %time%: Restarting Alteryx Service >> %LogDir%BackupLog%datetime%.log echo. >> %LogDir%BackupLog%datetime%.log SET COUNT=0 :StartInitState SC query AlteryxService | FIND "STATE" | FIND "STOPPED" >> %LogDir%BackupLog%datetime%.log IF errorlevel 0 IF NOT errorlevel 1 GOTO StartService SC query AlteryxService | FIND "STATE" | FIND "RUNNING" >> %LogDir%BackupLog%datetime%.log IF errorlevel 0 IF NOT errorlevel 1 GOTO StartedService SC query AlteryxService | FIND "STATE" | FIND "PAUSED" >> %LogDir%BackupLog%datetime%.log IF errorlevel 0 IF NOT errorlevel 1 GOTO SystemError echo Service State is changing, waiting for service to resolve its state before making changes >> %LogDir%BackupLog%datetime%.log SC query AlteryxService | Find "STATE" timeout /t 1 /nobreak >NUL SET /A COUNT=%COUNT%+1 IF "%COUNT%" == "%MaxServiceWait%" GOTO SystemError GOTO StartInitState :StartService SET COUNT=0 SC start AlteryxService >> %LogDir%BackupLog%datetime%.log GOTO StartingService :StartServiceDelay echo Waiting for AlteryxService to start >> %LogDir%BackupLog%datetime%.log timeout /t 1 /nobreak >NUL SET /A COUNT=%COUNT%+1 IF "%COUNT%" == "%MaxServiceWait%" GOTO SystemError :StartingService SC query AlteryxService | FIND "STATE" | FIND "RUNNING" >> %LogDir%BackupLog%datetime%.log IF errorlevel 1 GOTO StartServiceDelay :StartedService echo AlteryxService is started >> %LogDir%BackupLog%datetime%.log ::----------------------------------------------------------------------------- :: This section compresses the backup to a single zip archive :: :: Please note the command below requires 7-Zip to be installed on the server. :: You can download 7-Zip from http://www.7-zip.org/ or change the command to :: use the zip utility of your choice as defined in the variable above. ::----------------------------------------------------------------------------- echo %date% %time%: Archiving backup >> %LogDir%BackupLog%datetime%.log %ZipUtil% a %TempDir%ServerBackup_%datetime%.7z %TempDir%ServerBackup_%datetime% >> %LogDir%BackupLog%datetime%.log ::----------------------------------------------------------------------------- :: Move zip archive to network storage location and cleanup local files ::----------------------------------------------------------------------------- echo. >> %LogDir%BackupLog%datetime%.log echo %date% %time%: Moving archive to network storage >> %LogDir%BackupLog%datetime%.log echo. >> %LogDir%BackupLog%datetime%.log copy %TempDir%ServerBackup_%datetime%.7z %NetworkDir%ServerBackup_%datetime%.7z >> %LogDir%BackupLog%datetime%.log del %TempDir%ServerBackup_%datetime%.7z >> %LogDir%BackupLog%datetime%.log rmdir /S /Q %TempDir%ServerBackup_%datetime% >> %LogDir%BackupLog%datetime%.log ::----------------------------------------------------------------------------- :: Done ::----------------------------------------------------------------------------- echo. >> %LogDir%BackupLog%datetime%.log echo %date% %time%: Backup process completed >> %LogDir%BackupLog%datetime%.log GOTO :EOF :SystemError echo Error starting or stopping service. Service is not accessible, is offline, or did not respond to the start or stop request within the designated time frame. >> %LogDir%BackupLog%datetime%.log
View full article
Scheduling in the Gallery is now available! A few clicks and your published workflow is running when you want it to.
View full article
How to check what's using the port and steps for changing some services' default port!
View full article
I had a user recently ask about having an app on their Gallery run, produce an output, and have a second workflow send an email with the output from the app. There are a couple of ways to accomplish this, but I came up with an idea that I thought would be useful to share with the Community as they may find this feature useful for many situations.   The idea was to make it simple for the user so that they didn't have to use a chained app. The user just wanted the second workflow to run, but not put the Email tool on the Server. The solution is to use the Events > Run Command in the Workflow Configuration to schedule the email workflow after the app is run.   To accomplish the task, you can use a command line option that will add a specified workflow to the scheduler queue.   Scheduling a workflow via the Command Line:   The Run Command is in the Events tab; click on your Alteryx canvas and in the Workflow Configuration window select Events > Add > Run Command:     Run Event When: to "After Run"   Command: C:\Program Files\Alteryx\bin\AlteryxService.exe (This may not be exactly where your company has the AlteryxService.exe saved. Please check with your Server Admin.)   Command Argument [Optional]: addtoqueue=C:\location\of\workflow\to\schedule.yxmd,Server name,Controller Token,true   Example:   C:\Program Files\Alteryx\bin\AlteryxService.exe addtoqueue=C:\Temp\simpleoutput.yxmd,dib-ps-tst-12,3EA75D9170E4956DC3583C23224BA0898A98376D,true   Where to find Server name:On the machine the holds the server - Windows Start>Control Panel>System>Computer Name   Where to find the Controller Token: Open your Alteryx System setting on the Server and click Next until you reach the General screen under the Controller section. Click View to see the Controller Token and copy the token.                         Once the first workflow is run, the Scheduler will queue up the scheduled workflow and run the workflow on the Scheduler immediately.   Hopefully, this will give you some creative ideas to use this operation!
View full article
How to Clean Up Duplicate Workflows In the Gallery
View full article
The  Alteryx License Server  is an implementation of our technology partner  Flexera Software ’s  Local License Server , and allows for the deployment of a local license server within an organizations’ internal network. This allows for a smoother and more secure deployment of Alteryx products, especially behind proxies and firewalls.
View full article
Logs and files can be hard to find if you’ve never had to deal with them before.  This Alteryx Analytic Application will help gather most of the common logs and environmental files Support requests in one fell swoop!
View full article
In developing workflows our users need to push workflows to server or scheduler that contain database connections.  This is a common source of errors if not configured properly.
View full article
You've downloaded Alteryx and you want to activate it, but it asks you for information you don't have. What do you do now? Don't panic!  
View full article
This is Part 2 of the Alteryx Gallery Series - The Gallery Series only refers to the Alteryx Server where you can host your Private Alteryx Gallery. This Article with refer to 'Alteryx Gallery' as a privately hosted Gallery on the Alteryx Server.  Part 1 Alteryx Gallery Series - The Lay of the Land 101: Gallery Admin Edition Part 3 Alteryx Gallery Series: App Publishing & Version Control 101 - Alteryx Community  Part 4 Alteryx Gallery Series: How to make the most of your Alteryx Gallery – Use Cases   Each section of the user interface is outlined and described below:   Often utilizing and navigating the Private Alteryx Gallery for the first time (or even for veterans) can be difficult. This article aims to make this process simpler by giving a step-by-step guide on where to find the main areas of the Alteryx Gallery, as well as those hidden features.     Finding the Alteryx Gallery The URL is typically the ServerMachineName(or IP)/Gallery unless another domain has been defined. **** Speak to your IT or Alteryx Server Contact to find URL address. If it is an internal server, the user will need to be logged into your organization’s VPN before accessing the Gallery.   Accessing the Gallery User visits the Gallery on their own: Depending on your pre-defined user authentication setting, the user may be granted access to the Gallery the first time he or she visits the URL. If your Gallery utilizes Windows Authentication, a Gallery Account is automatically created when a new user visits the site. If your Gallery utilizes Built-In Authentication, the new user may create their own Account profile by “Joining” the Gallery from the Gallery home page.   Gallery Admin invites user to the Gallery: The Gallery Administrator may invite users to join the Gallery. This allows the Administrator to set up all of the users specific privileges before that user views the site. If your Gallery utilizes Windows Authentication, the admin would enable “No Access”. You will receive no notification from Gallery once you have registered. If your Gallery utilizes Built-In Authentication, the admin would disable the “Sign-Up Form” (Link to gallery admin page). The user will receive an invitation email and be asked to validate their account.   Lay of the Land: Everyday Gallery User “HOME is where the heart is” When you create a workflow, macro or app in the Alteryx Designer and upload in to the Alteryx Gallery you can CHOOSE to share your workflow to the Public Gallery (Home). You will need to be a Data Artisan to publish to the Alteryx Gallery (Link Permissions page). Users with access to your Gallery URL may access the Public Gallery section. External users cannot view and run workflows in the Public Gallery unless they have been invited by an Admin and have network rights to access the Gallery website. Example Users often upload proof of concepts or demo applications to the Alteryx Gallery which other users can use for reference.   Public Gallery section that have been tagged (after publishing) with a specific keyword set by the Gallery Administrator.   “The last of the thirteen DISTRICTS of Panem” Districts are Alteryx workflows shared in the Public Gallery section that have been tagged (after publishing) with a specific keyword set by the Gallery Administrator.   Example Districts are used for housing macros which are used within different internal departments.     “Welcome to my Private Studio” A user will ONLY receive their own Private Studio if their user permission level (set by the Alteryx Gallery Admin at sign up or before) are designated an Data Artisan User. This will allow them to publish Alteryx workflows from their Desktop Designer. By default, a Data Artisan will only see the workflows they have published themselves in the Private Studio section. To see content created by other Data Artisans, a workflow may be shared in the Public Gallery or via a Collection or Studio.     "Brand new Insights" New feature added in the Alteryx Server 2018.2 allowing you publish interactive charting directly into a web browser This dashboarding features offers users the ability to filter and drill down into Analytical Insights   “You’re the chosen one, welcome to my Collection” Collections are a means for ensuring only specific users may access workflows to which they are assigned. Collections are managed by users NOT by the Gallery Administrator. Collections are tied to one Private Studio only. A user must have their own (paid) Private Studio OR be a member of another Private Studio in order to run workflows shared via a Collection. Data Artisans can invite Users to a collection through the users tab inside of the collection. These Users will have to sign up to the Alteryx Gallery or be users in the same domain as the Alteryx Gallery is hosted on. You can have Multiple Admins for collections     “Let’s see these Workflow Results” Gallery Users may view the results/output of their own previous workflow executions. You can never see the results of other user’s executions via the Gallery.       'Let's automate that for you' - Scheduler In Alteryx 11.0 the gallery Admin can allow users to schedule directly from the Alteryx Gallery.  You can click on the scheduler tab and schedule your workflow by choosing the workflow and frequency you wish to run the schedule on. You then get visibility to your schedules only, and have the ability to edit the schedule and remove the schedule from being run.    Best,   Jordan Barker Solutions Consultant 
View full article
This is   Part 1   of the Alteryx Gallery Series - The Gallery Series only refers to the Alteryx Server where you can host your Private Alteryx Gallery. This Article with refer to 'Alteryx Gallery' as a privately hosted Gallery on the Alteryx Server.  Part 2 Alteryx Gallery Series - The Lay of the Land 101: User Edition  Part 3 Alteryx Gallery Series: App Publishing & Version Control 101 - Alteryx Community  Part 4 Alteryx Gallery Series: How to make the most of your Alteryx Gallery – Use Cases   The Lay of the Land 101: Gallery Admin Edition   The Gallery Admin is the Godfather of a Alteryx Gallery. The Admin is less involved with the workflow content of the site and more involved with management of users and their overall experience on the Gallery. This article will help the Gallery Admin navigate the Admin settings within the Private Alteryx Gallery.    Each section of the Admin interface is outlined and described below:   Subscriptions A   Subscription is another name for a Studio. A Studio allows Alteryx Designer users to publish and share workflows privately within their organization.  Each user that creates a Gallery account is automatically given their own subscription which can become a Private Studio if the   user permission level is designated an Artisan. As a Gallery Admin you will have to make this user an Artisan, take a look at the ‘users’ section below which details how to do this. Each Studio includes a limited number of artisans and members – assigned by the Gallery Admin. Once a subscription has been created, it can be deactivated but not deleted. Gallery Admins are the only ones with permissions to create subscriptions.    Subscription Management Permission levels     Creating and adding users to Private Studios To create a studio (subscription) click on ‘subscription tab’ and click on ‘Add New Subscription’. You will now have the ability to create a studio (subscription) Subscription Screen     This will be the subscription screen below:       Gallery Admin can create studios as well as manage the users and workflows assigned to them. There are numerous options when creating a Subscription or Studio: Private Studio Name: The name for the studio, which displays at the top of the page when the user clicks “Private Studio” on the left menu of the Gallery page. Contact Name: The person who owns and manages the studio. Subscription Type Free: Artisans and Members who are part of the studio can run workflows in the Public Gallery Paid: Artisans who are part of the studio can publish and run workflows in that studio and Members can run workflows Artist Seats: The number of Artisan seats available in the studio. Artisans can publish, run, and share workflows. Member Passes: The number of Member seats available in the studio. Members can run workflows in studios for which they have been assigned. Expiration Date: The date the Paid subscription expires. When a paid subscription expires it is downgraded to a Free subscription. API Enabled: Access to the Private Server Gallery API is enabled by default. The Gallery API supports the ability to authenticate, list apps, run apps, and retrieve app results using an API Key and Secret which are accessible via Gallery Settings.  Users Disable user sign-ups: Limits who can sign up for your Gallery. Forces users to be “invited” to join the Gallery. Allow anyone to run public workflows without singing in: If this option is selected, anyone with access to your Gallery URL may run workflows that are available on the Home Page.  This is how to add a user to a studio (Subscription). You need to take the subscription key from the ‘subscription’ section (above screenshot) and add this into the studio key within the User profile below.     When a user now publishes from there Alteryx Designer to the Alteryx Gallery they will see the studio name they are associated with. This is linked by the same subscription and studio key. Users can only be part of one Studio at a time.    Gallery Users Gallery Admins can add users directly to the Gallery or they can send an email inviting user to log in and add themselves via the Join now form on the main page of the Gallery. User permissions are managed in the users profile (or in “Permissions” if using Windows Auth) as well as in their assigned studio. The new user is added to the Users page. The users name, email (for Built-In Auth), and name of their studio display in the user box as well as icons that represent their permissions. When using Built-In Authentication, the Gallery Admin can designate the permission level of users before they sign up to Alteryx Gallery on the users tab   Built-in Permissions Screen (Users permission level for the whole Alteryx Gallery)     Windows Auth Permissions screen (Users permission level for the whole Alteryx Gallery)   Gallery Admins can manage user permissions in the Permissions page when using Windows Authentication only. A default permission level (No Access, Viewer, Artisan, Curator) can be set for any new or existing user who joins the Gallery. Admin Tip:   Set the default permission to No Access or Viewer if Content Security is of chief concern. This will require users to be invited to run workflows on the Gallery Once a user has been created, it can be deactivated but not deleted.   Workflows Gallery Admins can add workflows, apps, and macros to the Gallery and manage their icon, description, Run Mode settings, and exemptions. Admins can also create “tags” and associate them to workflows so searches within the Gallery return better results.   Run Mode: Determines the level that workflows are permitted to run in the Gallery. Workflows that contain certain tools or access may need to be blocked. The default Run Mode is selected when the server is configured. Unrestricted: Any workflow can be run. Semi-Safe: Workflows using Run Command, Download, Email, “R”, or Events will be blocked. Safe: Workflows using above tools or accessing/storing data on non-local drives will be blocked. Requires Private Data: Indicates if the workflow requires licensed data to run. Private Data Exemption: An exemption can be given to a workflow with private data so that it can be run.   Districts Gallery Admins can create new districts and modify the district name, description, and icon image. Once the District has been created, it will be displayed below the “Home Page” menu option on the Gallery.   Data Connections   This tab within the Gallery Admin section is only available for Alteryx Server Version 11.0 and above This tab will give you the option to pre-define credentials that can be sent down to designer users This will help when managing access and Alias creation on both Designer & Server DSN-less connections will run straight away. DSN connections will need to be set up on the location machine and server machine   Workflow Credentials Set workflow credentials which can be use when running a workflow from the server. These will also appear in the designer when uploading/scheduling a workflow Click on 'change; and you get the following options Use Default Credentials This will use the server service account details to run workflows if nothing has been set in the 'Run As' section of the Server System Settings Require User Credentials When running the application from the Alteryx Gallery the users will have to enter in credentials    Allow users to set options for credentials option The best practice would be to ask users for their credentials so they can only access the data they have privileges for within your internal IT environment.  The interface will look like the screenshot below. When uploading an App from your Alteryx Designer (File>>Save as>>>My Company's Gallery) you can click on 'Workflow Options' & 'Set Workflow Credentials'.    This will give the user three options    'User is not required to specify credentials' - The application/workflow will run as the default Alteryx Server user account (Run As settings in system settings on server config).  'Always run this workflow with these credentials' - The user can enter the credentials at this point, however preset credentials can be added within the Alteryx Gallery Admin section ("Workflow Credentials")   Jobs This is where you can give users permission to schedule workflows they upload to the Alteryx Gallery. This will allow all artisans to schedule workflows.         Notifications The server can send email notifications for various events. The SMTP server information is entered when the server is configured. Gallery Admins can manage the types of notifications and the message text. Admin Tip: Disable notifications so your users don't get spammed by the Gallery.   Customize your Alteryx Gallery! Banner Ads can be added to be displayed below the search bar on the Home page. Uploaded Files can be added to the site to which Gallery Users can access via Links. You have the ability to change the Gallery Name, Logo and Color Scheme within the web Browser. This is often used to house FAQs, Help & Links Add link to your Page or URL in the Header or Footers.   If you have any outstanding questions please reach out to our Alteryx Support   Best,   Jordan Barker Solutions Consultant
View full article
Credentials are how we control who has access to what on a computer or a network. Credentials are a way to prevent people from touching data or folders or content they aren’t supposed to. This article goes over the different options for setting credentials on a private gallery. 
View full article
SAML (Security Assertion Markup Language) is a standardized way for exchanging authentication and authorization credentials between different parties. The most common use for SAML is in web browser single sign ons. Starting in 2018.2, Alteryx Server supports SAML. So far, SAML in Alteryx Server has been specifically validated on two providers; Ping One and Okta. In this article we will review how to configure SAML on your Alteryx Server for  Okta.
View full article
SAML (Security Assertion Markup Language) is a standardized way for exchanging authentication and authorization credentials between different parties. The most common use for SAML is in web browser single sign ons. Starting in 2018.2, Alteryx Server supports SAML. So far, SAML in Alteryx Server has been specifically validated on two providers; Ping One and Okta. In this article we will review how to configure SAML on your Alteryx Server for   PingOne.
View full article
Alteryx Server provides a fully scalable architecture that allows an organization to scale Alteryx to automate data analytics, tackle bigger projects, process larger datasets and put self-service data analytics into the hands of more decision makers. From scaling Worker nodes to Gallery nodes to the MongoDB persistence layer, Alteryx Server allows organizations to efficiently manage their automated and self-service data analytics needs.
View full article
One common reason why the Alteryx Service appears stuck in the 'Stopping' state is when the service is trying to stop but the AlteryxEngineCmd.exe process is running. In other words, a workflow is running. The Alteryx Service cannot be stopped when a workflow is running due to a schedule or a Gallery run.
View full article
You will not be able to use this functionality on the Alteryx Server at this time. As of 10.6.8 and higher either the 'Allow Local Logon' or 'Logon as a Batch Job' permission is required for the Run As user and/or any Gallery Credentials.
View full article
How do I differentiate between workflows which are not uploaded to gallery and those that are present in the gallery?
View full article
If a quick/straight forward solution is not available, you may be asked to provide screenshots, files, and/or error logs that our Server/Gallery Support requires to help troubleshoot your issue.
View full article
If a quick/straight forward solution is not available, you may be asked to provide screenshots, files, and/or error logs that our Server/Gallery Support requires to help troubleshoot your issue.
View full article