The EPC file is an .ini file that contains key/value pairs of configuration data. The values conform to the following standards:
The EPC file can include the following licensing key/value pairs: LICENSE_SERVER_TYPE=dsls|flex DSLS_LICENSE_CONFIG=[complete_path_to_]\DSLicSrv.txt FLEX_LICENSE_CONFIG=@flexServer1 ACADEMIC_TYPE=teaching|research|none COMPUTER_LOCATION=CityStateCountry FLEX_TYPE=auto|concurrent|token The EPC file can include the following sections: [EstablishedProducts] [Tosca] [fe-safe] [Abaqus] Tosca, fe-safe, and Abaqus can all use the configuration from the generic [EstablishedProducts] section. Each product can also use the configuration from its own section. Entries in the individual product section take precedence over entries in the generic section. Example 1: The EPC file contains only the generic configuration section. All products use flexServer1 because there is no product-specific configuration. [EstablishedProducts] LICENSE_SERVER_TYPE=flex FLEX_LICENSE_CONFIG=@flexServer1 Example 2: In a later release, a new license server for Tosca is added. You can update the EPC file from Example 1 as shown below. fe-safe, and Abaqus continue to use flexServer1 because there is no product-specific configuration for them, but Tosca now uses flexServer2. [EstablishedProducts] LICENSE_SERVER_TYPE=flex FLEX_LICENSE_CONFIG=@flexServer1 [Tosca] FLEX_LICENSE_CONFIG=@flexServer2 You can override the values in the EPC file. For more information about other licensing / configuration options, see: for Abaqus: for Tosca: for fe-safe: the Program Directory. (See http://media.3ds.com/support/progdir). |