Background

Testing your content with a new version of Tableau Server is important, especially if you use advanced features, integrations, or Web Data Connectors (WDC).

Environments

What should you do if there is an issue?

If you find an issue with the new environments submit a ticket to let us know and ask it to be routed to the Analytics and Business Intelligence Group so we can take a look at it. 

Maize/Blue Upgrades

Beginning in 2024, upgrades will transition to a Maize/Blue upgrades upgrade strategy, as opposed to the traditional in-place method. This change aims to enhance the user experience by eliminating outages and reducing risks.

Content owners will need to adapt to a new process, given the alternate use of two distinct environments: Maize and Blue.

Preparation and Testing Phase

Following the non-prod environment's upgrade, the Tableau Server team will inform the user group when the system is ready for testing. Testing is crucial as this environment will be promoted to production status. Users are encouraged to explore new features and validate their content during this phase. Identifying and addressing issues at this stage will help ensure a smoother upgrade.

The Upgrade

The Maize/Blue upgrade will involve an 8-hour freeze period during which production content will be transferred. Here's what to expect during the freeze:

• • Dashboards will be available for end-user access
  • Schedules for Extracts, Subscriptions, and Flows will be disabled
  • Content can be viewed, but any data dependent on Extracts or Prep Flows will be delayed

After the content transfer and validation by the Tableau Server team, schedules will be reactivated, and tab.med.umich.edu will redirect to the new environment.

What to Test

DataConnections

It is vital to test at least one connection to each data source or database. Ensure both live connections and extracts function correctly.

Essential checks should include, but are not limited to:

• • Database Types (e.g., Oracle, SQL Server, MySQL)
  • Specific Databases (typically, common databases like HSDW or Clarity are tested, but if you use different ones, they should be verified as well)
  • ODBC Connections
  • Web Data Connectors (WDCs)

Contact the Tableau Server Team in EDIS for an updated list of IP addresses if your databases have IP address restrictions.

Extracts

Extracts Although schedules will be paused, you can manually run them by clicking the context menu (...) and selecting 'Refresh Extracts' from the context menu of a workbook or published data source.

Live Connections

Simply loading the dashboard should trigger a database connection and query execution.

Flows

Test your Prep Flows to ensure operational functionality. When outputting to a database or published datasource, be cautious to avoid overwriting existing data unintentionally. 

Customizations and Integrations 

Uncommon or bespoke elements must be thoroughly tested. This includes, but is not limited to:

• • Dashboard Extensions
  • Analytics Extensions (e.g., RServe)
  • Scripts or custom code
  • APIs
  • WDCs

Embedded Visualizations

For any Tableau Dashboards embedded within applications, websites, or SharePoint, verification against the new version is essential. 

How and Where To Test

 Utilize the non-production environment to assess dashboards and to manually refresh extracts. Explore any forthcoming features as well.

Other Non-Production Environments

On occasion, you may be directed to perform tests on devtab.med.umich.edu, particularly for diagnosing specific issues or evaluating changes.