Skip to main content
To homepage To homepage
SUBMITTED

Silent install of TX (and why it is not working now)

Related products:TimeXtender Data Integration
  • October 3, 2024
  • 2 replies
  • 24 views
daniel
TimeXtender Xpert
Forum|alt.badge.img+8

Hi All,

(bigger) Organisations will have their IT department run updates or upgrades or installs e.d. trough silent installs. This is perfect for them as they can have this run on schedules or independently from the intervention of people. With this I mean that no human interaction is needed in these processes.

At the moment this cannot be done TX. When a new install or upgrade has been done you have to log in for the software (mainly the ODX) to work (again). This is a human intervention and this is unwanted.

Can we make it so that this is no longer nessicary? That service accounts can be added in the portal so that when they make a connection it goes straight trough or that you can save / back up the condig file and whenever an update / upgrade has been made the config file gets read and logging in is not required?

2 replies

rory.smith
TimeXtender Xpert
Forum|alt.badge.img+8
  • rory.smith
  • TimeXtender Xpert
  • October 3, 2024

Hi @daniel,

while certain software is amenable to unattended patching I am not sure TimeXtender is one of those.There are decisions with resultant actions that very much depend on the setup: it is sometimes required to upgrade Data Source connections and sometimes optional, for instance.

While I am sure you can patch SAP in a silent fashion, I would expect by far most organisations don't due to the complexities involved as an example.

What you can already do is push images to virtual machines, that way you only need to do the upgrade once and push to many VMs. I do this here as it allows me control but also automates as much as possible.

daniel
TimeXtender Xpert
Forum|alt.badge.img+8
  • daniel
  • Author
  • TimeXtender Xpert
  • October 3, 2024

Hi @rory.smith ,

thats exactly what happens. So there is an Image but when the VM gets build a person still needs to log in and make the software operational.

For me this is a feature for the maturity of the TX software especially with big(ger) more corporate IT departments where silent installs are the norm.

Personally I think this is a bit of a hassle especially when you can automate everything else but the process get stopped by the logging in part. It would be easier / nicer / better when TX would check its sonfig of just skip the login for the SA account.

Terms and ConditionsAccessibility statement