Configuring the Utility's Execution Options

From the 3DX Utility editor, select the Execution tab and expand the Execution Options.

Select Run in persistent session mode to improve performance for a process iterating on the same 3DOrchestrate Station.

Performance is improved by keeping the batch file loaded between invocations of the 3DX Utility adapter for the duration of the job; for example, between runs of a DOE, optimization, or loop. Any activity that later invokes the 3DX Utility adapter will reuse the batch file that is already loaded.

Note:

If you selected the Import Simulation Results batch utility to import simulation results files and you want to use persistent session mode, you must use the following syntax to refer to the working directory when you specify the file to import: ${rundir}\MyFile.odb.

Specify the Number of standard error messages to log to minimize the volume of standard error messages that Automation Process Composer writes to the job log.

Specify the Number of standard output messages to log to minimize the volume of standard output messages that Automation Process Composer writes to the job log.

Optional: If you use Simulation tokens for licensing, select Use embedded license for simulation to run simulations from Automation Process Composer using embedded tokens only. Embedded token licensing lets you run one simulation at a time and with the maximum number of cores specified for embedded licensing for your role. For more information, see About Embedded Licensing.

You can specify the use of Simulation tokens for licensing from the Execution preferences for Simulation Process Modeling.

Enter any shareable licenses that are required to run the batch utility. Separate multiple licenses with semicolons; for example:

SMU.prd;
						DRD.prd

.

If you selected Run in persistent session mode, Automation Process Composer releases the licenses after all the iterations have completed.

Click OK to save your changes and to close the 3DX Utility editor.