Skip to main content
Question

ODX Server installed on Dev\TST server

  • November 17, 2025
  • 3 replies
  • 34 views

Hi All,

My current employer uses TimeXtender Desktop and two separate servers (dev/test + prod).

The previous administrator installed the ODX server on the dev/test server. This causes issues when a datasource is modified, as it also affects the production environment.

At my previous employer, we had an ODX server per environment: Dev ODX, Test ODX, and Prod ODX.

My question is: what does the community recommend regarding having an ODX server on the dev/test environment?
My ideas:

  • Install the ODX Server on the production environment.
  • Rename the VM.

Thanks in advance for your help and input!

Kind regards,


Tim

3 replies

Thomas Lind
Community Manager
Forum|alt.badge.img+5
  • Community Manager
  • November 19, 2025

Hi ​@Timmm 

I would usually suggest having the ODX on the prod server. We did a internal BI setup and that is what I suggested then as well.

You run more transfers on production than on development, so it makes sense to have it be on the one closes to the traffic.

To do the switch.

  1. Uninstall the ODX on DEV
  2. Install the ODX on Prod and run the config
  3. Point at the ODX on prod from DEV
  4. Point at the ODX on Prod from Prod

You don’t need to change the name of the VM, unless it is called something like DEV and runs Prod.


  • Author
  • Starter
  • November 19, 2025

Hi ​@Thomas Lind ,

Thank you for your response! Below are a few follow-up questions:

  1. Wouldn’t it be more practical to install the ODX on the Dev Server environment after the ODX Prod server has been installed?
  2. Can I already proceed with this even though an ODX is currently running on the Dev server? I think I could temporarily disable the TimeXtender ODX service on the Production server.

When installing the ODX on the production server, can I simply transfer all data sources manually? Or is there also a way to migrate data sources from ODX Dev to ODX Prod?

Thanks in advance for your answer.

Kind regards,


Tim

​​​​​​


Thomas Lind
Community Manager
Forum|alt.badge.img+5
  • Community Manager
  • November 21, 2025

Hi ​@Timmm 

I don’t know if it is more practical, but you can choose to install it wherever you want as long as the environments can connect to it.

The server that hosts the ODX will use memory and processing when running tasks. When it is done from an external server, you will see that this server uses more memory whereas the ODX server is using CPU to run them.

The environments can only connect to one ODX, it is not possible to have one for each environment, they will need to share one.

 

Regarding moving from one ODX to another, I think it should be mentioned that we do not have ODX in TimeXtender Data Integration (TDI), it is called Ingest Instances. The ODX exists in our legacy program aka v20. You can use the above sections as answers to how it would be done in v20.

So if you meant TDI, then sure, you can set up a Ingest instance for each environment. Then you would use it similar to other environments and move the data source setups from one ingest to another. It is important that the same data sources exists in both instances when you do the migrations.