General Configuration

OverwriteConfigFile Setting

The OverwriteConfigFile setting determines whether the configuration file (pdmsyscfg.xml) will be replaced by the default version provided with Altair installations (for example, HyperWorks or Inspire).

Options

  • true: automatically replaces the current configuration file with the default version during application startup.

    Use case: when deploying updates or applying a standardized configuration across multiple environments.

    Note: The default configuration file shipped with the installation has this value set to true.
  • false: preserves your existing configuration and prevents it from being overwritten.

    Best for: customized local setups where preservation of settings is critical.

Additional Notes

  • When copied to the your home directory, the OverwriteConfigFile value is automatically set to false to avoid unintentional overwrites.
  • A backup file named pdmsyscfg.xml.XXX (where XXX is the HyperMesh version) will be created in the same directory for rollback purposes.
  • Caution: Set the OverwriteConfigFile option to true only if you're certain the updated configuration is compatible with your current environment and custom settings.

ResourceBundle: Locale Encoding Configuration

The ResourceBundle section is used to define character encoding schemes for different locale codes. This ensures proper handling of localized characters during file processing.

Behavior

  • If no specific mapping is provided for a given locale, the system defaults to UTF-8 encoding.
  • This is especially useful when working with international datasets or regional Teamcenter/Windchill instances.

Configuration Format

To specify a locale-to-encoding mapping, use the following structure:

<ResourceBundle>
  <Encoding name="ISO-8859-1">
    <Value>it_IT</Value>
  </Encoding>
</ResourceBundle>
  • Encoding name: the name of the character set (for example, ISO-8859-1, UTF-16, and so on).
  • <Value>: the locale code to which the encoding should apply (for example, it_IT for Italian).

Usage Example

To use ISO-8859-1 for Italian (Italy):
<Encoding name="ISO-8859-1">
  <Value>it_IT</Value>
</Encoding>

Instructions

  • Add one or more <Encoding> blocks within the <ResourceBundle> section.
  • Each block must:
    • Include a name attribute for the encoding type.
    • Include at least one <Value> element listing the corresponding locale code(s).

Template Placeholder

The default configuration includes a placeholder block:

<Encoding name="ISO-8859-1">
  <Value></Value> <!-- Insert your locale code here, e.g., en_US, fr_FR -->
</Encoding>

Simply populate the <Value> element with your desired locale code.

CommonActionThreads: Background Task Configuration

The CommonActionThreads section configures background threads used by Altair Inspire to support asynchronous operations such as revision checks.

General Notes

  • All XML element and attribute names are case sensitive. You must ensure consistent casing when editing.
  • These threads run automatically in the background and enhance the user experience by validating part states.
CheckLatestPartRevision
This element enables a background process that checks whether the downloaded part in the current session is the most recent available revision.
Attributes
timeout (required)
Defines the delay before triggering the API call.
Is measured in milliseconds.
Example: timeout="120000" waits for 2 minutes (120,000 ms).
Values
true
Enables the thread.
An API call will check if the part revision is up to date.
false
Disables the feature.
No automatic revision validation will occur.
Example
<CheckLatestPartRevision timeout="60000">true</CheckLatestPartRevision>
This configuration enables the revision check with a one-minute delay.