Skip to main content
ptc-44286451-Visitor
1-Visitor
August 31, 2012
Solved

Configuration of custom Windchill applications

  • August 31, 2012
  • 3 replies
  • 2230 views

Hello,

we use WTProperties to configure our custom Windchill applications (written in Java).

If we want to change some configuration values, we have to use the "xconfmanager" to apply the changes.

This process seems unnecessarily complex.

We are looking for easier ways, such as application-level property files (java.util.Properties) located as resources on the classpath).

Are there any substantial advantages in using Windchill xconf (WTProperties) over classic Java property files?

Thank you in advance for your opinions

mp.

Best answer by JørnAHansen

PTC use xconf to modify configuration in a few other types of files than .proprety files - so I guess that's one reason for having the xconf format and tooling in the first place. Another feature of .xconf is that it allows you to split your configuration into several files and reference these from site.xconf. That's useful to split out just the differences between test, production or machines in a cluster in particular if you don't control the files in a version control system like Subversion or Git.

These features are probably less useful for your own custom code because you don't need to constantly be able to maintain you own configuration "on top of" configuration changes coming in with upgrades from PTC.

3 replies

JørnAHansen1-VisitorAnswer
1-Visitor
September 1, 2012

PTC use xconf to modify configuration in a few other types of files than .proprety files - so I guess that's one reason for having the xconf format and tooling in the first place. Another feature of .xconf is that it allows you to split your configuration into several files and reference these from site.xconf. That's useful to split out just the differences between test, production or machines in a cluster in particular if you don't control the files in a version control system like Subversion or Git.

These features are probably less useful for your own custom code because you don't need to constantly be able to maintain you own configuration "on top of" configuration changes coming in with upgrades from PTC.

ptc-44286451-VisitorAuthor
1-Visitor
September 3, 2012

Hello Jorn,

thank you for your reply, it was really helpful.

You are right, the features of xconf are rather "heavy" for our custom applications.

But it is good to know about them.

mp.

FrédéricPradier1-Visitor
1-Visitor
September 14, 2012

Using custom preferences would give you more flexibility. By this way you could have dynamic values for your properties and even different values depending on your context

Fred

Terms & ConditionsAccessibility statement