Summary

Write-Back Manager enables you to set up and configure Write-Back in a web environment and guides you through the process. Every Manager screen has a help section on the side providing the necessary information to fill each screen. This manual is a complement to that help section.

Accessing Write-Back Manager

Write-Back manager is available at https://us01.manager.writeback4t.com. To access open this URL on the browser.

Authentication on Manager

The Write-Back Manager requires an administrator account to access it. To log in, use the credentials defined through the email that the administrator received to register the administrator account.

Advanced Configuration

Configure Site

Data Storage

Write-Back stores the data submitted on datasets that persisted on your database. Write-Back works as an engine that can translate your settings and data submission into valid database commands hiding all the technical complexity behind it.

This configuration allows you to choose what is going to be the database repository that Write-Back is going to use to store its datasets. You can choose across a wide set of database technologies that include: PostgreSQL, SQL Server, Oracle, MySQL, SAP Hana, Vertica, Redshift, Snowflake, Exasol, and Google Big Query and this means you can store Wite-Back data side by side with your existing data.

Database access

Write-Back has a fixed IP that will establish communication with your database, to ensure that you have to allow external to access to the database from IP address 13.82.49.25.

It is highly recommended to create a specific database user for Write-Back to use. It should only have full access to the Write-Back schema where the datasets will be created.

Supported Databases

It is recommended to use a cloud database or ensure a compatible version.

Database	Version
MySQL	MySQL Server versions 8.0 and 5.7
PostgreSql	PostgreSql 8.2 and higher
Oracle	21c, 19c, 18c and 12.2 - TNS variable cannot be used
Snowflake	No limitations
Exasol	No limitations
Redshift	No limitations
BigQuery	No limitations
Vertica	No limitations
SAP HANA	SAP HANA 2.0 SPS 04 and later versions
SQL Server	SQL Server 2019, SQL Server 2017, SQL Server 2016, SQL Server 2014, SQL Server 2012, SQL Server 2008 R2, SQL Server 2008, SQL Server 2005, SQL Server 2000

Database Limitations

SQL Server

In the case of SQL Server, this user must be created with a default schema, as SQL Server has the requirement to always specify a schema. To add a default schema to a user, here is an example: ALTER USER XPWBTABEXT WITH default_schema = dbo; Replacing the highlighted words with the proper ones for your scenario.

Amazon Redshift

In the case of Amazon Redshift, depending on the security settings, you most likely will need to add the IP of the Tomcat server to be able to access the database. In the EC2 Console, there should be an option to manage Security Groups where the IP should be added to the inbound rules. This guide might help: https://docs.aws.amazon.com/redshift/latest/gsg/rs-gsg-authorize-cluster-access.html

Amazon Redshift

In the case of Amazon Redshift, depending on the security settings, you most likely will need to add the IP of the Tomcat server to be able to access the database. In the EC2 Console, there should be an option to manage Security Groups where the IP should be added to the inbound rules. This guide might help: https://docs.aws.amazon.com/redshift/latest/gsg/rs-gsg-authorize-cluster-access.html

Snowflake

In some cases, when using Snowflake, an error may indicate that there is an unsafe memory allocation or an out-of-bounds index. To fix this, please add JDBC_QUERY_RESULT_FORMAT=JSON in the JDBC Advanced Options.

BigQuery

In the case of BigQuery due to a lack of support for some operations on the database, there are the following limitations:
- Transactions are not supported at SQL level, so we cannot guarantee the integrity of the BigQuery database if some error happens during the action.
- Being an analytics database bear in mind the operations can take longer to be executed.

Authentication

Here you can configure the authentication methods that include:

SAML Single-Sign-On on Tableau Server, Online and Desktop
Open ID Single-Sign-On on Tableau Server, Online

For each method, you will need to complete the setup using the form available.

Before Using Write-Back

On Tableau Server

If you want to use Write-Back on Tableau Server follow the Configure Tableau Server to allow Write-Back Cloud instructions to allow it.

License Management

This is the page where you will be able to see the information about your license, such as the maximum number of users of your license, available seats, and when your subscription will end.

Apply Settings

Write-Back manager allows you to configure Write-Back but it is a separate application. It is only when you click on Apply Settings that the configuration is applied to Write-Back. The whole process is done automatically.

Any change made to the configuration needs to be applied afterward.

Using Write-Back

This section provides everything that you need to start using Write-Back on Tableau. It allows you to download the TREX file that you will need to use Write-Back in your dashboards.