Skip to main content
To homepage To homepage
Solved

Will upgrading the ODX service change the ODX repository?

  • February 26, 2025
  • 6 replies
  • 42 views
L
Participant
Forum|alt.badge.img

Hello TimeXtender Support,

We are looking to upgrade the ODX server at the customer. Currently the ODX service is installed on the PROD server. We first want to install the new version of the ODX service on the DEV, basically run a sandbox project to ensure everything is running fine and then upgrade the ODX service on PROD.

Now, I've been told by Rory that there is a change that running a newer version of the ODX service will impact the metadata in the ODX repository in a way that is irreversible. I want to make sure that we can first try the new version of the ODX service in the DEV environment without impacting the ODX repository, so we can go back to the previous situation if anything problematic pops up and don't impact PROD.

My question is: can we safely install a sandbox version of the ODX service on the DEV server and have it call home without irreversibly changing our ODX repository between these two versions?

ODX Service 20.10.37
>
ODX Service 20.10.57

Hilsen,

Luuk Bouman

Best answer by Christian Hauggaard

Hi ​@luuk.bouman 

Please see the following here https://legacysupport.timextender.com/hc/en-us/articles/210439583-Download-TimeXtender-20-10

“

WARNING

Starting from ODX Server version 20.10.53, this version will remove the need for the local "backlog" component of the application metadata repository.

This upgrade cannot be rolled back.

Before proceeding with the upgrade from a previous version, you must ensure your local backlog is fully synchronized with the cloud-based repository metadata, or you could lose saved progress in your ODX. To do this, follow the below instructions:

For Each ODX Service Project and each ODX Service:

  1. Open your TimeXtender client and right-click the ODX Service, and choose 'Shut down ODX Service'.
  2. At the bottom you will have the Last synchronization timestamp.
    - If the timestamp is current (i.e. representing the last time you made a change in your solution) your repository is in sync, so no need for further action.
    - If the timestamp is a while back in time and you are not sure that it is synchronized, you can force a synchronize by doing a minor change like adding a dummy task or edit a data source. Then wait a few minutes and check the Last synchronization timestamp again.
     - You can also double check the Windows Event Viewer and check for error messages to ensure you do not have any synchronization issues.
  3. When you are confident the backlog is synchronized you should shut down the ODX service and you are ready to upgrade.

If you encounter any issues or have questions, please reach out to us at support@timextender.com and be sure to include your Portal ID found at: https://portal.timextender.com/admin

”

View original
Did this topic help you find an answer to your question?

6 replies

Christian Hauggaard
Community Manager
Forum|alt.badge.img+5

Hi ​@luuk.bouman 

Please see the following here https://legacysupport.timextender.com/hc/en-us/articles/210439583-Download-TimeXtender-20-10

“

WARNING

Starting from ODX Server version 20.10.53, this version will remove the need for the local "backlog" component of the application metadata repository.

This upgrade cannot be rolled back.

Before proceeding with the upgrade from a previous version, you must ensure your local backlog is fully synchronized with the cloud-based repository metadata, or you could lose saved progress in your ODX. To do this, follow the below instructions:

For Each ODX Service Project and each ODX Service:

  1. Open your TimeXtender client and right-click the ODX Service, and choose 'Shut down ODX Service'.
  2. At the bottom you will have the Last synchronization timestamp.
    - If the timestamp is current (i.e. representing the last time you made a change in your solution) your repository is in sync, so no need for further action.
    - If the timestamp is a while back in time and you are not sure that it is synchronized, you can force a synchronize by doing a minor change like adding a dummy task or edit a data source. Then wait a few minutes and check the Last synchronization timestamp again.
     - You can also double check the Windows Event Viewer and check for error messages to ensure you do not have any synchronization issues.
  3. When you are confident the backlog is synchronized you should shut down the ODX service and you are ready to upgrade.

If you encounter any issues or have questions, please reach out to us at support@timextender.com and be sure to include your Portal ID found at: https://portal.timextender.com/admin

”

L
Participant
Forum|alt.badge.img
  • luuk.bouman
  • Author
  • Participant
  • 17 replies
  • February 26, 2025

Hi Christian,

Thank you for the quick reply. Just to be completely sure on my side:

If we install ODX service 20.10.53 or higher on the DEV server, this will remove the local backlog component. This then means that we will no longer be able to use the ODX service 20.10.37 installed on the PROD server. 

Is this correct?

Christian Hauggaard
Community Manager
Forum|alt.badge.img+5

Hi ​@luuk.bouman 

I have forwarded your question to the product team and will get back to you as soon as I have an update

 

L
Participant
Forum|alt.badge.img
  • luuk.bouman
  • Author
  • Participant
  • 17 replies
  • February 26, 2025

Thanks Christian,

 

Could you take along in this request the opposite side as well, so:

 

If we install ODX service 20.10.52 on the DEV server, this will not impact the ODX repository. This then means that we will be able to use the ODX service 20.10.37 installed on the PROD server. 

 

Is this correct?

L
Participant
Forum|alt.badge.img
  • luuk.bouman
  • Author
  • Participant
  • 17 replies
  • March 4, 2025

Hi Christian,

 

Did you get an answer from the team?

 

Regards

Christian Hauggaard
Community Manager
Forum|alt.badge.img+5

​@luuk.bouman I have created a support ticket for this

L
1 person likes this
  • L
    luuk.bouman

Reply


Most helpful members this week

Terms and ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings