smaSimulationCentral.properties

Some Process Composer properties are configured in a file named smaSimulationCentral.properties.

The smaSimulationCentral.properties file is located in the following directories after the Process Composer installer has run:

collaboration_server_dir/STAGING/ematrix/properties/
collaboration_server_dir/managed/properties/

After you have run the ENOVIA WAR utility and deployed Process Composer on your J2EE application server, the properties file will be located in this directory:

appserver_dir/application_name/WEB-INF/classes/

This copy of the smaSimulationCentral.properties file is the one used at runtime by Process Composer.

Modifications to the file in the collaboration_server_dir/STAGING/ematrix/properties/ directory affect all subsequent deployments of Process Composer. Modifications to the file in the appserver_dir/application_name/WEB-INF/classes/ directory affect only the deployment on the associated J2EE application server; these modifications will be overwritten if Process Composer is redeployed to this application server.

Modifications to the copy of the file in collaboration_server_dir/managed/properties/ are used during MQL execution if you are running the MQL command from collaboration_server_dir (but not if you run the MQL command from studio_dir).

The settings in the smaSimulationCentral.properties file should be suitable for most applications. However, you may want to modify certain attributes of Process Composer, including:

  • The simulation categories that are available in Process Composer (see About Categories in the Process Composer User's Guide).
  • The default simulation categories that are created in a new simulation or simulation activity (see Creating a Blank Simulation Process and Creating a Blank Simulation Activity in the Process Composer User's Guide).
  • The icons used for various simulation entities throughout Process Composer.
  • The available options for export and import rules (see About Rules in the Process Composer User's Guide).
  • The search behavior (see Searching in Process Composer in the Process Composer User's Guide), including search box headings, default search parameters, and the types of items that can be returned by a search; enabling searchability for content from other ENOVIA applications or custom business types allows you to locate these items and reference them in Process Composer.
  • The states for which Process Composer tracks the status of entities in impact graphs (see About Impact Graphs in the Process Composer User's Guide). By default, entities in a Simulation or Simulation Activity that is in the Proposed state do not appear out of date in the impact graph, even if you modify them; you can change the states for which this behavior applies.
  • The rate at which the Remarks column in the structure navigator is updated (see The Process Composer Explorer in the Process Composer User's Guide).

  • Allow users to export/import parameters and execution attributes to/from an XML file in the working directory when an activity executes. Set the following property to true to allow this type of importing or exporting of legacy data:

    smaSimulationCentral.ExecutionOptions.showLegacyImportExport = true
    For more details, see Parameters and Execution and The Format of the Execution Attributes XML File.

  • How objects can be exported from the 3DSpace database. The following property lists connectors that the user can choose for VPM data export:

    smaSimulationCentral.VPM.Export.Connectors = V5 Export, 3DXML Export

    You can define a new PLM batch connector (interactively in Process Composer), then add the new connector's name to the comma-separated list in this property. After this connector is configured, a user can choose it in the Export Method field of an export rule and can select the connector to execute the export rule.

    See About Accessing 3DSpace Data in the Process Composer User's Guide.

  • You can also export ENOVIA database objects from any of the ENOVIA Central applications, for example parts from Engineering BOM Management or requirements from Traceable Requirements Management. You can also export ENOVIA PLM parameters (but not Process Composer parameters).

    You can export any Central object, provided you specify the type and relationship key values in the following two properties:

    smaSimulationCentral.Range.ExportBO.Type =
smaSimulationCentral.Range.ExportBO.Relationship =

    All types and relationships from ENOVIA Engineering BOM Management and ENOVIA Traceable Requirements Management are included in these property definitions by default:

    smaSimulationCentral.Range.ExportBO.Type = Requirement,Part,Customer Requirement,Part Family,Derived Requirement
smaSimulationCentral.Range.ExportBO.Relationship = Sub Requirement,Part Family Member

    For any other Central objects that you want to export, you must add the corresponding key values to the comma-separated lists for the two property definitions above.

    To enable export of any documents other than the Reference Document type, you must add the appropriate key value(s) to the following property:

    smaSimulationCentral.Range.ExportBO.DOCUMENTRelationship =

More information about configuring these and other attributes is provided in the smaSimulationCentral.properties file.