Contact your system administrator to configure this trust. If this is your chosen deployment, you will have to configure the trust relationship between your Desktop users' machines and your certificate. It is possible to deploy HTTPS-enabled Atlas with a self-signed certificate. For more information about Atlas configuration, read the Atlas documentation. While it is possible to deploy Atlas without HTTPS, Tableau does not support mapping services via http. If you see a map, set this as a default via Map > Background Maps > Set as Default.Go to Map > Background Maps > Map Services.To import and set this new file as your new default, follow these steps: Once the CLI runs, you will see Atlas.tms in your Tableau Repository. tableauAtlasConfig-macos Update Tableau Defaults For Mac, this is typically found in Documents.For Windows, this is usually found in My Documents.If you do not know where your Repository is, or have trouble finding it in your filesystem: You can choose this option or provide your own fully qualified path. The CLI will auto-detect your operating system and suggest a default path for saving. You will be first prompted for the location of your Tableau Repository. This indicates the number of styles you want to combine into a single TMS. The tool accepts a single command generate, with a single option -n that accepts an integer. It is also available via the Atlas Toolkit, which is included in the standard distribution of Atlas. There CLI can be downloaded for both Mac and Windows via Releases. Server Administrators can use the tool to create a single authoritative TMS to distribute via wikis, fileshares, or their own distributed packaged installer as well as place on Server for web-editing use. Desktop users can use the tool a single time and set the new map source as a default. The CLI is intended for both Desktop users and Server Administrators. Upon opening Tableau Desktop (or Tableau Server web-editing), they will have the option to switch to the Atlas-based map style and select it as default for future workbooks.
When it completes, the Tableau user will have a valid TMS placed in their Tableau repository. The Tableau + Atlas Configuration CLI or tabAtlas automates this process using the same user workflow as a custom style. This is due to Tableau Desktop needing a URL.
This process is error-prone and when successful, hard to distribute to Desktop users. When using Mapbox Atlas (or the Tableau maps proxy), configuration requires hand-editing of TMS files. In these cases, Mapbox Atlas is a solution for providing the same vector maps within your own IT environment. This can block or impede access to Mapbox, which can cause lag (or errors) in rendering maps in Tableau.
There are common cases where your Tableau Desktop and Server installations have difficulty in accessing the open internet.
0 kommentar(er)
