--- schema_version: "1" id: 06577723780adbdc0a8d2e89fe8a2a64d138b2d5b320e606689deae3f1be7ea4 title: Migrate Rserve Connections from TCP to HTTP collection: tableau version: current locale: en-us portal_url: https://docs.salesforce.com/tableau/current/en-us/online/rserve_tcp_to_http.md canonical_url: https://help.tableau.com/current/online/en-us/rserve_tcp_to_http.htm source_site: help.tableau.com content_type: documentation content_hash: 12a1a31c2e19a16820a6ab3e13cef516650b839613401d3a9151c16f4fd7e0fa description: Migrate Rserve analytics extension connections from TCP to HTTP to get model calculations, the Function Explorer, and higher limits. --- [Skip to main content](#main-content) # Migrate Rserve Connections from TCP to HTTP Beginning October 2026, you can connect to Rserve over HTTP. Before October 2026, Tableau communicated with Rserve only at the transport layer (TCP). An Rserve-by-HTTP connection uses the [Analytics Extensions API](https://tableau.github.io/analytics-extensions-api/), so it has the same advantages that TabPy and other analytics extensions have in Tableau: - Access to [model calculations](https://help.tableau.com/current/pro/desktop/en-us/r_connection_manage.htm#directly-query-external-analytics-models) and the [Function Explorer](https://help.tableau.com/current/pro/desktop/en-us/r_connection_manage.htm#custom-functions-explorer-for-deployed-models). - Simple requests to your extension are up to 10 times faster. - The payload limit increases from 6 MB to 100 MB. - The request timeout increases from 30 seconds to 60 minutes. **Note**: Rserve-by-TCP doesn't have a deprecation date, but eventually Rserve will be available only over HTTP. If you migrate now, you get the benefits of Rserve-by-HTTP right away and you won't need to take action later. The migration is a one-time process: 1. [Step 1: Set up an HTTP endpoint for Rserve](#step1RserveHTTP) 2. [Step 2: Replace or update the Rserve connection](#step2RserveHTTP) - Either: - **Create a new Rserve HTTP connection**. This approach allows you to leave the existing connection alone while you create and test a new Rserve connection. You will need to edit your workbooks one by one to complete the migration. - **Edit your existing Rserve connection so it uses HTTP**. This approach is faster, but automatically updates the connection for all workbooks using it. 3. (Optional) [Step 3: Update workbook connections](#step3RserveHTTP) - If you choose to create a new Rserve HTTP connection, you will need to update any workbooks using the old connection so they use the new connection. For general information about configuring analytics extensions, see . [Configure Connections with Analytics Extensions](https://help.tableau.com/current/online/en-us/config_r_tabpy.htm). . For information about using analytics extensions in workbooks, see [Pass Expressions with Analytics Extensions](https://help.tableau.com/current/pro/desktop/en-us/r_connection_manage.htm) in the _Tableau Desktop and Web Authoring Help_. ## Impact on users Once Rserve connections are migrated to HTTP there should be little or no impact on authors and business users. The analytics experience doesn't change, other than potentially faster performance and access to the Function Explorer. Existing content will continue to work after its connection is updated. ## Step 1: Set up an HTTP endpoint for Rserve To migrate Rserve from TCP to HTTP, you replace your existing Rserve connection with one that works through the Analytics Extensions API. You can use any method, as long as it implements the Analytics Extensions API, specifically the `/info` and `/evaluate` endpoints. We recommend [RestRserve](https://restrserve.org/), which is the method described in this section. Alternatively, you can use [Posit Connect](https://docs.posit.co/connect/admin/integrations/tableau/) (previously RStudio Connect) as your R integration, but that method requires changes to existing workbooks. For an example using RestRserve, see the [Example - RestRserve](https://tableau.github.io/analytics-extensions-api/docs/ae_example_rserve.html "RestRserve example on GitHub") on the Tableau Analytics Extensions API GitHub site. ## Step 2: Replace or update the Rserve connection New Rserve connections use HTTP by default. To switch a connection between HTTP and TCP, click Use TCP or Use HTTP in the upper-right corner of the Rserve connection dialog. The option will change depending on what type of connection is configured. For default HTTP connections, the dialog looks like this: ![New Rserve HTTP Connection dialog with the Use TCP link in the upper-right corner, and fields for connection name, hostname, port, username, and password.](/tableau/current/en-us/online/en-us/Img/rserve-http-connection-dialog.png) Switch to an HTTP Rserve connection in one of two ways: - **Create a new connection**: Create a new connection with Rserve as the connection type (this will default to HTTP) while leaving your existing TCP connection in place. Using this approach you can create and test the new connection with one or more workbooks to make sure it works as expected. You then need to switch each workbook from the old connection to the new one. Once all workbooks are updated to use the new connection, you can delete the old connection. For details, see [Configure Connections with Analytics Extensions](https://help.tableau.com/current/online/en-us/config_r_tabpy.htm#configure-analytics-extensions-settings). or - **Edit the connection in place**: Edit the existing Rserve connection and change it from TCP to HTTP by clicking Use HTTP. Using this approach you can quickly update all workbooks by editing the existing Rserve connection. Once edited, any workbook using the existing connection will automatically be using the updated connection with HTTP. **Important**: Editing the connection in place immediately switches every workbook using the connection to HTTP. Because of this you should test your new HTTP endpoint using a single workbook before you edit the existing connection. ## Step 3: Update workbook connections If you created a new connection instead of editing the existing connection, after testing to ensure the new HTTP connection works, update the connection in each workbook that uses the Rserve analytics extension. You can either do this manually following the steps in in the Desktop and Web Authoring Help, or automate the process using the [Update analytics extension for workbook](https://help.tableau.com/current/api/rest_api/en-us/REST/TAG/index.html#tag/Analytics-Extensions-Settings-Methods/operation/AnalyticsExtensionsService_updateWorkbookWithConnection) API method.