You can customize many properties as described in this section and in the Administrator Guides for each ENOVIA product. To make sure your customizations are not overwritten when you install a new version of software, you should place your custom properties in a separate file instead of editing the existing properties file. This feature works for application properties only; it does not work for string resource property files. You cannot add custom string resources to this properties file. To customize (and internationalize) string resources, see Internationalizing Business Process Services Products. In the emxSystem.properties file, ENOVIA Business Process Services and each installed application (such as Engineering Central or Library Central) has a key-value pair to define the primary properties file. In addition, you can include a key-value pair to define a custom properties file such as: emxFramework.CustomProperties.Filename=emxFrameworkCustom.properties To provide custom properties for specific applications, include those properties in the above file. The system loads the primary properties file first, then the custom properties file. If your system includes customized code and applications, the custom properties file can contain additional key-value pairs that are not included in the primary properties file. To create the custom file, copy the properties whose values you want to change to the custom file and edit as needed. The property name in the custom file must exactly match the property name in the primary properties file, including case. The file must be stored in the <STAGING>/ENOVIA_INSTALL/properties directory, and must have a different name than the properties file distributed with the software. The file must use the .properties extension without other periods in the file name, for example, ECcustom.properties. For performance reasons, you should not copy the entire primary properties file into the custom file. | |||||||