6 Replies Latest reply on Jan 22, 2019 6:34 AM by Juan Landaeta

    TabJolt for Server 2018.3

    Ben Bryant

      I have uploaded a new version of TabJolt which you can download here. https://github.com/tableau/tabjolt/releases


      This version includes fixes which allow it to work on versions up though 2018.3 including Linux servers. If you encounter problems or have questions please let us know in this thread. We hope to push out incremental updates in the near future.

        • 1. Re: TabJolt for Server 2018.3
          Ciara Brennan

          Thanks for sharing @ Ben!


          • 2. Re: TabJolt for Server 2018.3
            Parth Upadhyay

            Hi Ben,


            Currently I am trying to explore Tabjolt for Tableau: 2018.3 version. And I am facing a road block while installing Tabjolt.


            As suggested in the guide, I am installing tabjolt on a new EC2 windows machine(m4.xlarge) separate from actual Tableau Server.


            I am using installation guide from below:



            When I am entering “OS Login Credentials” correctly I am still getting below error.


            "Unable to log into Tableau Services Manager. Please double check that the username and password are correct"



            I am able to ping tableau server from tabjolt box successfully but i am not sure where am i going wrong.


            Any help would be greatly appreciated.



            • 3. Re: TabJolt for Server 2018.3
              Parth Upadhyay

              Also I am able to successfully connect with Tableau Server when i am entering Tableau Server Admin credentials in Step 1.


              I am able to get the proper list of Views as well in Step 2.


              It is only the last step “OS Login Credentials”  i am facing problem.

              • 4. Re: TabJolt for Server 2018.3
                Parth Upadhyay

                Latest Update -


                I was able to successfully run the Tabjolt results for the Tableau Server box.


                So this is really strange that the last step of installation (Tabjolt integration with TSM) did not complete still Tabjolt is working as expected.


                I think the issue lies Tabjolt integration with TSM in the latest version of tabjolt - TabJolt 2018.2.0 Installer

                • 5. Re: TabJolt for Server 2018.3
                  Toby Erkson

                  I hope this will clear up some confusion in the documentation.


                  For a complete list of command line parameters for the go.bat file enter the following on the command line:

                  go help


                  Currently you will get the following after a few debug error messages (ignore them) and a rather long example at the end:

                  There are two ways to run TabJolt:
                    * Run a specific test plan and upload results. 3 parameters are required: test plan, duration, and thread count.
                      go --t=testplans\InteractVizLoadTest.jmx --d=10 --c=1
                    * Only upload results. 2 parameters are required: processResultsOnly, and ResultsFolderPath
                      go --processResultsOnly=true --p=C:\Results
                  --buildVersion       --b:   The build version of server under test
                  --customParams       --z:   Custom parameters that test would need
                                              eg --z=loadMultiplier=2,replayFile=c:\replay.json
                  --description        --r:   The description of the run. Default to empty.
                  --doNotPurge         --n:   whether or not to retain the result in DB without being purged.
                                              Default to false.
                  --duration           --d:   The duration for the perf run. Time unit is seconds.
                  --emailReport        --x:   List of email recipients separated by commas (no spaces)
                  --environment        --e:   The environment which the run is hitting against. Default to empty.
                  --injector           --j:   If not specified, localhost is treated as injector. You can
                                              specify multiple injectors as a comma separated string like
                                              --j=machine1,machine2, in which case clients are equally
                                              divided between the injectors; the same testplan and
                                              configuration files are used by all injectors. If you do use
                                              this flag, jmeter engine is run only on the machines
                                              specified. If remote injector is given, it is assumed that
                                              psexec.exe is included in the PATH environment variable. If
                                              remote injector is given, the same directory structure is
                                              created on remote machine as on localhost.
                  --note                      Adding extra note to the run
                  --officialRun        --ofr: Indicating whether official run or not
                  --owner              --o:   The owner of the run. Default to the login user of the system.
                  --processResultsOnly --a:   Does not run test; only uploads results to DB. Requires --p option.
                                              Eg --a=true --p=c:\ResultsFolder\.
                  --ResultsFolderPath  --p:   Specify the path (p) where the results go
                  --rootPath:                 The location of bin, lib, config, and testplans directories.
                  --serverUrl          --u:   Specify the server url which the test case is trying to hit.
                                              It will override the value in ServerTestConfig.yml.
                  --skipSaveResult     --s:   whether or not to skip saving the result to DB.  Default to false.
                  --TestPassId         --i:   Specify the testPassId (i) which the test case run is part of
                  --testPlan           --t:   The location of the jmeter test plan (.jmx).
                  --TestplanFolder     --f:   Specify the folder (f) where all the testplans exist
                  --threadCount        --c:   The number of threads used in the perf run.
                  --twbFilePath        --y:   File path to performanceViz.twb
                  --workers            --w:   Specify the workers which are part of your server deployment


                  In it's easiest form you execute Tabjolt as so:

                  go --t=testplans\<t> --d=<d> --c=<c>


                  • <t> is the filename of the plan to use (InteractVizLoadTest.jmx, ViewInteractVizLoadTest.jmx, ViewVizLoadTest.jmx, or Replay.jmx if you will use that feature)
                  • <d> is the number of seconds to run Tabjolt
                  • <c> is the number of users - or threads - to run against the Tableau Server

                  Do not place spaces around the required equals symbols.

                  • 6. Re: TabJolt for Server 2018.3
                    Juan Landaeta

                    Hello Ben!


                    Im having this same issue attempting to install TabJolt in Tableau Server 2013.0 environment. Did u solve this issue? You could help me? im stuck in label OS Login Credentials when i have to input domain and credentials of my tsm configuration.


                    What i need to do do?TabJolt Issue Installation.PNG


                    LIKE (0) THIS HELPED ME YES