Skip to main content
To homepage To homepage
SUBMITTED

Remove release number from the names of Timextender services in TimeXtender Data Integration

Related products:TimeXtender Data Integration
  • May 8, 2024
  • 2 replies
  • 21 views
anders.e.jonsson
Contributor
Forum|alt.badge.img+1

Hi,

Would it be possible to remove the release number from the names of the Timxtender Windows services.
It would it would help if the name to remain the same when using monitoring systems. For example OP5.
The release number can still be in the description.
There is no reason to have more than the latest version installed, right? Because you can still only run one version of each service on one server. And once you've upgraded, you can't go back.
So existing services would be replaced with the new version during installation.

BR
Anders

Anders

2 replies

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

Hi,

Windows Service names must be unique - as upgrading TimeXtender means installing a new service next to the existing one instead of removing the existing and adding new, that is impossible. The Name is also not user changeable (without some risky changes anyhow) whereas DisplayName and Description are. I would therefore see if you can set your monitoring system to use those fields or if it uses the registry to look for the Left(x) characters and Startup Type to determine the service to monitor.

You can just change the DisplayName through the commandline if you want to keep some kind of consistency across versions.

I have many versions of TimeXtender Classic and TimeXtender Data Integration installed on single VMs I use for testing, I would not want to have to use the registry and/or commandline to start a service or trust user-changeable fields.

    anders.e.jonsson
    Contributor
    Forum|alt.badge.img+1

    Hi Rory,

    My suggestion was only intended for TimeXtender Data Integration, and windows services often keep their names when they are updated.
    But I like your alternatives, and will see where they can be used.

    BR
    Anders

    Anders
    Terms and ConditionsAccessibility statement