1. Linux

    2. Windows

    3. IIS (Unavailable)

    1. Windows SSL

    2. Linux SSL

    3. Windows SSL (IIS) - DEPRECATED

    4. Forward Proxy

    5. Reverse Proxy

    6. High Availability (Enterprise Only)

    1. Authentication Methods Overview

    2. Okta (SAML)

    3. OneLogin (SAML)

    4. Windows LDAP (IIS) - DEPRECATED

    5. Curator Users

    6. Azure AD (SAML)

    7. OneLogin (OIDC)

    8. Multifactor Authentication

    9. Signing SAML Login Requests

    10. Active Directory

    1. REST API Integration

    2. Tableau Cloud Setup

    3. Alternative URL Routing

    4. Using Postman to Test Connection

    5. Tableau Server Repository

    6. Supported Tableau Server Versions

    7. API Connections Overview

    1. Azure App Setup

    2. Service Principal Setup

    3. Curator Connection

    1. Integrating ThoughtSpot with Curator

    1. Central Dispatch Windows Deployment

    2. Central Dispatch Linux Deployment

    1. Curator Styles

    2. Homepage

    3. Titles and Toolbars

    4. Group Overrides

    1. Pages Overview

    2. Tiles

    3. Error Pages

    4. SSRS Embedding

    5. Explorer

    6. User Customized Metrics

    7. Box Embedding

    8. Forms

    9. Blogs

    1. Tutorials

    2. Search

    3. Managing Menus

    4. Menu Items

    5. Keywords

    6. Files

    7. Notices

    8. Loading Screens

    1. Embedded Tableau Server Views

    2. Thumbnails

    3. Tagged Workbooks

    4. Favorites

    5. Email Subscriptions

    6. Data Export

    7. Download Workbook

    8. Share Workbook

    9. Custom Views

    10. Pause/Resume Changes

    11. Dashboard Titles

    1. Filters

    2. Parameters

    3. Apply Button

    4. Filter Categories

    5. Hidden Sticky Filters/Parameters

    6. Specify Filter Sheet

    7. Mark Commenting

    8. URL Action Overrides (Link Target)

    9. Hidden Dashboards

    10. Replace Dashboard URLs

    11. Site Switcher

    12. Cache Filter/Parameter Options

    1. Data Manager Basics

    2. Web Data Connector (WDC)

    3. Import Data

    4. Connecting to Data Manager

    5. User Commenting

    6. Field Calculations

    1. Overview and Enabling

    2. Report Builder: Scheduled Reports Option

    3. Report Builder: Email Option

    4. Report Builder: Watermark Text

    1. Automatic License Provisioning

    2. Just-in-time (JIT) Provisioning

    3. Users and Groups

    4. Reset User's Password

    5. Username Mapping

    6. User Sync and Membership Sync Overview

    7. Custom Attributes

    1. Frontend User Permissions

    2. Password Change

    3. Password Reset

    4. Password Expiration and Complexity

    5. Bypass Link-preview Security

    1. E-mail Configuration

    2. System Notifications

    1. Force SSL

    2. Trusted Tickets

    3. Basic HTTP Authentication

    1. Import / Export

    2. Backend Users

    3. Frontend Users

    4. Updating License Key

    5. Linux: Cron Troubleshooting

    6. Filesystem Permissions

    7. Backend Administrator Password Reset

    8. Manual Restoration of Curator Backup

    9. Updating Curator Logging

    10. Third Party Cookies

    11. Troubleshooting Load Times

    12. Tableau API Debugging

    13. Curator Backup

    14. Taking a Manual Full Backup

    1. System Upgrade

    2. Disable Curator Upgrades

    3. Offline Upgrades (Airgapped)

    4. Dependency Updates

    5. Troubleshooting Upgrades

    1. Scripts

    2. Commands

    3. Subscription Routing

    1. Curator API Overview

    2. Integration

    3. Curator API

    4. Tableau API

    5. Content

    6. User API

    Windows Installer

    .htaccess file

    Dockerfile

    API Example: Creating a File (Python)

    Sample Hero Images (jpgs)

    Logging.php file

    Frontend Quickstart - Homepage

    Frontend Quickstart - Dashboard

    Backend Quickstart - Styling

    Backend Quickstart - Adding Content

    Backend Quickstart - Adding Content

    Backend Quickstart - Adding Content

    Get Started with Curator in 5 Minutes

    Setup: Central Dispatch

    Central Dispatch Linux Deployment

    1. Install Curator using Linux installer like usual.
    2. You can make a new directory called centraldispatch at /var/www and move the contents of the webroot (/var/www/html) there or you can leave it as is. The newly deployed instances will be located at /var/www/instance-name while the main Central Dispatch site remains at /var/www/html or /var/www/centraldispatch. The rest of the guide will assume /var/www/html so change all of the commands to the correct path if you chose /var/www/centraldispatch.
    3. Set up SSL for this initial instance. This blog by the great and powerful Orr will get you most of the way there (Ubuntu systems are slightly different).
    4. There should already be a default conf file that has an IncludeOptional line that points to a directory where additional vhost conf files can go. Make sure you know where the newly added vhost conf files should go:
      • Ubuntu:
        • Default conf: /etc/apache2/apache2.conf
        • Includes vhost conf files: */etc/apache2/sites-enabled/.conf**
        • Ubuntu is a little different and actually stages the conf files here before being enabled: */etc/apache2/sites-available/.conf**
      • Everything else:
        • Default conf: /etc/httpd/conf/httpd.conf
        • Includes vhost conf files: */etc/httpd/conf.d/.conf**
    5. Create database user using the worker_database_user.sql example script at /var/www/html/plugins/interworks/centraldispatch/workers directory. Tweak the password if you'd like before executing.
      • Run the sql file: mysql -u root -p curator < worker_database_user.sql
      • Enter root password
      • Test if the new user is there: mysql -u worker -p
      • Enter worker password
    6. Create directory /var/www/archives
    7. Set up worker script
      1. Copy php_worker.example.php script to php_worker.php in the /var/www/html/plugins/interworks/centraldispatch/workers directory:
        • sudo cp php_worker.example.php php_worker.php
      2. Copy vhost.template.example.conf to vhost.template.conf in the same directory.
        • sudo cp vhost.template.example.conf vhost.template.conf
      3. Make sure apache user owns everything:
        • sudo chown -R $APACHEUSER:$APACHEUSER /var/www
      4. Tweak paths as needed in php_worker.php
        1. DB_ENV_DISPATCHER uses details from step 5 above.
        2. DB_ENV_INSTANCE uses the root database details to be able to provision users as needed. Can set up dispatcher user with these permissions if you don’t want to use the root account.
        3. Modify vhost section:
          1. Directory should be set to where you determined the vhost conf files should go in step 4.
          2. Template should be set to /var/www/html/plugins/interworks/centraldispatch/workers/vhost.template.conf
        4. Modify worker section:
          1. Source_directory should be set to /var/www/html
          2. Archive_directory should be set to /var/www/archives
        5. Modify $DEFAULT_BACKEND_EMAIL as needed.
        6. Modify $LINUX_APACHE_RESTART to the relevant apache restart command for your distro.
        7. Modify $LINUX_APACHE_USER to the relevant apache user for your distro.
      5. Tweak vhost template as needed in workers directory
        1. Comment out the #apache 2.2 lines (lines 22-23) and uncomment out the #apache 2.4 lines unless using Apache 2.2.
        2. Update SSLCertificateChainFile, SSLCertificateFile, and SSLCertificateKeyFile as needed.
      6. Schedule root to run worker with the following command. Feel free to change the frequency (this one is every 15 minutes). Also, make sure to change $APACHEUSER to the relevant apache user in the chown command (this makes sure the application owns all the files even though root is making everything).
        • **(sudo crontab -l ; echo "*/15 sudo php /var/www/html/plugins/interworks/centraldispatch/workers/php_worker.php >> /dev/null 2>&1 && sudo chown -R $APACHEUSER:$APACHEUSER /var/www") | sudo crontab -**
    8. Restart apache
    9. In the Central Dispatch Curator portal’s backend, register the workers with the dispatcher at Backend > Settings > Central Dispatch > Central Dispatch Settings. Probably with these settings:
      1. Host URL: localhost
      2. Worker name: localhost (or use something more descriptive)
      3. Install Path: /var/www
    10. Attempt to deploy a new managed instance at Backend > Central Dispatch > Managed Instances.