Property Files, Language Strings, and Settings

The emxSystem.properties file contains properties that apply to all applications, such as searching, file management, date management, and so on.

Each application has an additional properties file:

emxAPPLICATION_NAME.properties

where APPLICATION_NAME is the name of the specific application, such as EngineeringCentral or SupplierCentral. The application properties file contains default settings that affect that specific application. In Engineering Central, for example, you can change the properties that control how the Part Where Used page works (relationships used for searches, how many levels to expand, etc.)

Refer to the individual Administrator's Guides for information on setting properties.

Each ENOVIA product has a string properties file that contains the text displayed in the user interface and email notifications. You can edit the file to change the text.

For example, you can edit an email notification to add a company-specific proprietary statement.

The naming convention for the base resource file (English) is:

emxAPPLICATION_NAMEStringResource.properties

For example, the string resource file for Engineering Central is emxEngineeringCentralStringResource.properties. The emxFrameworkStringResource.properties and emxCommonStringResource.properties string resource files provide text for pages available to all applications, such as the login, home, or lifecycle pages.

The naming convention for all internationalized versions of the StringResource files is:

emxAPPLICATION_NAMEStringResource_LANGUAGE.properties

where LANGUAGE is the standard abbreviation for the language, such as fr for French or de for German, in lowercase.

Refer to the Administrator Guides for information on editing string properties; refer to "Localizing ENOVIA Live Collaboration" in the ENOVIA Studio Modeling Installation Guide for information on localizing the string properties.

User interface elements, such as forms and tables, can be edited using the Business Modeler application or MQL. You can perform tasks such as renaming column headings, adding or removing columns from tables, or editing a form's layout.

Refer to the Business Modeler Guide or the MQL Guide for instructions.

Using a standard path for file resources makes them easily available to the web application. The WAR Utility then ships them directly in the web application.

File resources are stored in the following location:

PLATFORM/resources/warutil/resources/

Resources that are shipped directly in the web application are accessible via the Java class path. This makes resource loading easier, as Java classes are then able to load them using:

this.getClass().getResource("resources/RESOURCE_SUB_PATH");