Skip to main content
Submitted

Configuration of Scheduler Service

  • July 18, 2019
  • 3 replies
  • 1 view
J
Forum|alt.badge.img

I have done multiple Discovery Hub Installations at a number of clients and there is always one particular item that the client gets hung up on. 

Configuring the Discovery Hub Scheduler Service. 

 

Currently one has to use the TXService account and log onto the Application/Discovery Hub Server using this account and connect Discovery Hub to the project repository, which allows Discovery Hub to create the encrypted connection file under the TXService account's user folder. 

Many Clients do not allow developer access to the TXService account and it is against best practices to use a service account for development. So often times the client configures the connection to the projectrepository using their developer account and the issue of the Discovery Hub Scheduler Service's failure to start is prevalent across lots of installations. 

My request is that Discovery hub eliminates the need to explicitly log into the TXService account on the box and connect to the repository using the tool. It would be great if a developer account could manage/configure this connection via the Discovery Hub tool, but utilizing any developer account. They would merely have a configuration tab for the Service account in which TimeXtender could then generate its encrypted connection file in the correct folder structure. 

    3 replies

    S
    Forum|alt.badge.img

    Same problem here, and I expect every corporate has this. Also I strongly support the security principle that service accounts must not have the "log on locally" permission.

    And to make it worse, every minor update you have to configure all the services again :( :(

    Bear in mind, this issue has little to do with encryption. The issue is that the config file that contains the (plain text) connection string to the repository must be in the local user's appdata folder.

     

    My suggestion: put this repository config in the discovery hub's program files folder.

    This has the additional benefit of allowing us to run 2 environments side by side from one machine.

    J
    • JTreadwell
    • Community Manager
    • February 26, 2021

    Thanks for submitting your ideas! Your continued feedback on our product is very important to us.

    We will be evaluating your input for future improvements in the product.

    At the time of this posting, the current product roadmap is focused on a major evolution in foundational pieces of our software including splitting the development into ODX, MDW, Semantic Layer and User Portal. With this evolution, we will continue to see incredible innovation in the product that may exceed your expectations or make the need for this feature obsolete.

    If you have any questions or would like to discuss further, please reach out to me or the dedicated TimeXtender Solution Specialist in you region. Thanks!

     
    J

    We are facing the exact same issue. After each upgrade minor or not, it is impossible to use a service account to startup timextender in order to configure the services for the server and the scheduler, because this is version specific. We have done last weekend an upgrade to the latest version in DEV and TEST. Hours we were looking for a possibilities to do a transfer. 

    IT cannot grant admin rights to the service accounts

    Our operator accounts have sysadmin rights but not to setup the services in windows for both services. That has not been granted for users.

    The above suggestion can be a good one because i see that Steven Koppenol is facing the same kind of issue.

     

    Terms & ConditionsCookie settingsAccessibility statement