Follow

Install Discovery Hub

This document outlines how to download and install Discovery Hub. Be sure you have properly configured the Discovery Hub Prerequisites and the User Accounts and Permissions before installation. 

  1. Download Discovery Hub.
  2. When the file has been downloaded, unzip the installation package and run Setup.exe.

    Install1.PNG

    If all prerequisites have been met, you should be able to install using the .msi file in the downloaded archive. Using setup.exe is recommended, however, since it checks for the required version of the .NET Framework and installs it if necessary.
  3. On the welcome page, click Next.

    Install.PNG

  4. On the End-User License Agreement page, review the license agreement and select I accept the terms in the License Agreement if you do. Click Next.

    Install3.PNG

  5. On the Choose Setup Type page, select Typical and click Next.

    Install4.PNG

  6. On the Ready to Install page, click Install. Windows might ask you to confirm that you wish to make changes to the computer. If so, click Install the software. Wait for the installation to finish.

    Install5.PNG

  7. Once the installation is completed, click Finish to close the setup program.

    Install6.PNG

 

 

Once you have finished installation, you can launch Discovery Hub and complete the First Time Set-Up of Discovery Hub.

Was this article helpful?
3 out of 3 found this helpful

18 Comments

  • 0
    Avatar
    Thomas Idelot

    Hi, 

    Thanks for the answer, and you're right as I said it is not that complicated.

    Maybe that's more a feeling as my Deploy&Execute can take a very long time (and i don't need rollback capability as I do a snapshot before the upgrade).

    Anyway, keep up the good work, it's always nice to see your tool evolve in the right direction :)

     

     

  • 0
    Avatar
    Nicolas Cosma

    Hi Thomas,

    I have ugraded the application, but at the moment of choosing "select upgrade methode" by "web service, I had an error, with the choice local file, No problem

    Is it ok ?

  • 0
    Avatar
    Chris Shelley

    Hi Thomas,

    You are correct I have not redeployed as I was not aware that it was required post upgrade. Do i need to redeploy all elements in the repository? If so that should I feel be in the upgrade instructions.

    Also if I just redeploy will I not end up with 2 SSIS folders and duplicated packages.

    Thanks

     

    Chris

     

  • 0
    Avatar
    Thomas Lørup Duun

    Local files in the latest version (as with most versions) is OK!

     

  • 0
    Avatar
    Catherine Karimi

    Hi Thomas,

     

    This is still now showing errors even after following your instructions,

     

    Regards,

    Cate

     

  • 0
    Avatar
    Thomas Lørup Duun

    Hi Chris,

    You can change the SSIS Root folder on the Edit Project screen if you need to. When you deploy the project the new folders should be created automatically though - so I wonder if you did not deploy but just executed after the upgrade?

  • 0
    Avatar
    Thomas Lørup Duun

    Hi Chris,

    It is the deployment that translates your project into SQL Server code, so if you do not deploy, then the upgrade will not be reflected in the code being executed. And you are correct in your assumption about ending up with duplicate packages. Feel free to delete the old ones, once the upgrade is completed successfully.

    We will add the important deployment step to the instructions. Thanks for pointing our attention to it!

  • 0
    Avatar
    Thomas Lørup Duun

    Hi Jörgen,

    If the server is not connected to the internet, then you should use local files. If there is an issue with the files distributed with the release, then we have announced it on the support site. Actually version 16.4.2 is missing an upgrade file, which we have announced and released 16.4.3 in order to fix it.

    Kind regards,

    Thomas

  • 0
    Avatar
    Jörgen Peerik | Victa

    Hi Thomas,

    Thanks for the explanation.

    What about servers which don't have an internet connection. Then the server is not able to download the latest upgrade scripts and I have to click on the button 'Local Files' instead of 'Web Service'. 

    How can I make sure the upgrade is done by using the latest scripts?

     

    Greetings,

    Jörgen Peerik

  • 0
    Avatar
    Martin OLoughlin

    I am currently looking at upgrading from TX2014 to the current release. As part of the testing i have installed TX2017 on my local machine, which is working fine and has allowed me to build a functional model, i have exported a model from the live system with the idea of importing to a local environment to get a feel for the process and identify any pitfalls. 

    However i am getting an error message "the project xml for generated in TX DWA server 14.2.6 The project can not be imported." 

    Is there something that prevents an upgrade? Is there a work around, ie upgrading to tx2015-tx2016-tx2017? 

  • 0
    Avatar
    Catherine Karimi

    Hi

    I am currently installing discovery hub for the first time and while setting up the Scheduler account but it is not letting me add the account i setup to the windows security box as it is defaulting to my native domain and it does not give me an option to use a different account. 

    Regards,

     

    Cate

     

  • 0
    Avatar
    Thomas Idelot

    Hi Thomas,

    Do you have any plans on making future upgrades more easy to perform ?

    It's not that complicated but it takes a lot of time nevertheless, I would really like to be able to upgrade In Place, meaning just launch a setup, click next/next/next and be done with it ;)

  • 0
    Avatar
    Nicolas Cosma

    Thanks :)

  • 0
    Avatar
    Kes

    Er det korrekt at opsætning af Multiple Environment skal foretages igen efter opgradering til TX DWA ??

  • 0
    Avatar
    Thomas Lørup Duun

    Allow me to translate your question to English.

    Q: Is it correct that you need to reconfigure multiple environments after upgrading to TX DWA?

    A: You need to configure the new TX DWA Server Service to use the same credentials as the old server service did. Then you have to login as that user, start TX DWA, point it to that environments repository database and upgrade the repository. Then start the service, and your multiple environments are back in business.

     

  • 0
    Avatar
    Thomas Lørup Duun

    Hi Martin,

    To upgrade your 14.2.6 project you need to point TX DWA to the repository. It is not possible to upgrade using an export / import. 

    In your scenario, you could restore a backup of the repository database from the live system on your local system and then have TX DWA upgrade it. 

    If you need further assistance on this, please contact support; support@timextender.com 

     

  • 0
    Avatar
    Chris Shelley

    Do you need to update the SSIS folder options post Upgrade? Currrently I get errors where the SSIS folerd cannot eb found as it has changed names between installs:

    Was: TX2014Server\DevTest

    Now: TX DWA Server\DevTest

  • 0
    Avatar
    Thomas Lørup Duun

    Hi Thomas,

    Upgrade is launch setup, click next, next, next, finish. Then start TX DWA and if will perform an upgrade of the repository. To put the upgrade into effect you ofcourse need to deploy and execute the project. I do not see how we could make this simpler while still giving you the option to run side-by-side versions and possibility to perform rollbacks. 

Please sign in to leave a comment.