You can use the Solution Process properties of a system's Solution cell to control where you run the solution. You can choose from the update options listed here; the defaults for these options are determined by the settings specified in the Solution Process preferences under > .
Note: If solve jobs will be submitted to a remote cluster, note that the license preferences set for your local machine (the RSM Client) may not be the same as the license preferences set for the cluster. In this case, the cluster license preferences will be used for all jobs.
Run in Foreground - Solutions are run within the current ANSYS Workbench session. This option is appropriate for quick-running solutions that fit within the resources of your workstation. This option is also the most robust as it is not possible to make changes that impact the current solution. When a solution is executing in the foreground, you cannot change or save the project, but you can interrupt or stop the solution.
Note: For Polyflow and CFX component or analysis systems, you can switch an update in progress on the local machine to background mode by right-clicking the Solution cell and selecting Switch Active Solution to Background.
Run in Background - Runs the solution in the background on the local machine. This option is appropriate for solutions that fit within the resources of your workstation but will take longer to execute. When a solution runs in the background, the cell enters the Pending state and you can interact with the project to exit ANSYS Workbench or work with other parts of the project. If you make changes to the project that are upstream of the updating cell, then the cell will not be in an up-to-date state when the solution completes.
Note: If you choose the Run in Background option for multiple solution components or for one solution component with multiple design points, your project and design point updates will run multiple instances of the solver at the same time. If you are using the Share single license between applications when possible option in the license preferences, only one of the solver runs will succeed. The others will fail because they cannot access the single license. There are two workarounds for this problem:
Change the license preference to be Use a separate license for each application. This preference will allocate one license for each running solver.
Instead of using the Run in Background option, use the Submit to Remote Solve Manager option and select the Local RSM queue. This is provided that a basic ANSYS RSM Cluster (ARC) has been configured to restrict the number of cores that can be used for a job. For more information, see Configuring an ANSYS RSM Cluster (ARC) and Setting the Maximum Number of Cores to be Used on an Execution Node in the RSM User's Guide.
Note: For Mechanical APDL, the Download Distributed Files property is not available and will not appear in the General Property table during foreground and background updates.
Use application default- (Mechanical application only). Uses the solver settings specified in the Mechanical application.
Submit to Remote Solve Manager- Runs the solution in the background by submitting the solution to Remote Solve Manager (RSM). This option is used primarily for long-running solutions that do not fit within your workstation's resources. Through submission to RSM, the solution can be executed on remote computing resources. RSM can also submit jobs to the local machine to allow the queuing of solutions on your workstation. When a solution is submitted to RSM, the Solution cell enters the Pending state, similar to the Run in Background option.
Important: When design points are configured to be updated via RSM, the Solution cell cannot also be updated via RSM. If you have configured design points to be updated via RSM or an EKM Portal, change the Solution cell update settings by setting the Update Option Solution Process property to Run in Foreground. For further information about tutorials and documentation on the ANSYS Customer Portal, go to http://support.ansys.com/docinfo. Note that the update of both the Solution cell and design points via an EKM Portal is not supported. If both are submitted to the Portal, the Solution cell update will automatically switch to Run in Foreground when the design points are being updated through the Portal.
Submit to Portal- Submits the solution to an EKM Portal for execution on remote computing resources. This option is used primarily for long-running solutions that do not fit within your workstation's resources, and enables you to monitor the solution remotely using the EKM web application on any computer or mobile device. EKM integrates with Remote Solve Manger (RSM), which is configured to integrate with a cluster. A scheduling system on the cluster submit host determines how jobs are queued and distributed to compute resources for execution.
Note: The Submit to Portal option is available for CFX, Fluent, Polyflow, Mechanical APDL, and Mechanical component updates. For Mechanical component updates, the Submit to Portal option is available only if the Mechanical APDL solver is selected.
To use the Submit to Remote Solve Manager option, configure RSM using the instructions in the Remote Solve Manager User’s Guide. For details see RSM Installation and Startup and RSM Configuration. For tutorials featuring step-by-step instructions on configuring RSM for direct job submission from Workbench, go to the Tutorials & Training Materials page of the ANSYS Customer Portal. For further information about tutorials and documentation on the ANSYS Customer Portal, go to http://support.ansys.com/docinfo.
To use the Submit to Portal option, configure RSM using the instructions in the EKM Administration Guide. For details see Integrating EKM with Remote Solve Manager (RSM). You must also create a connection to an EKM Portal in Workbench. For information about the installation, configuration or features of EKM, see the Engineering Knowledge Manager documentation.
If you choose Submit to Remote Solve Manager, you also have the following options, which are populated from or must use the settings from your existing RSM configuration:

Solve Process Setting -- (Mechanical application only) - This setting is the solving configuration that you have defined in Mechanical.
RSM Queue - This is a queue defined in RSM that maps to a specific cluster configuration and cluster queue. Any RSM queues currently defined in RSM will appear in this drop-down list. The cluster configuration and cluster queue that are associated with the selected RSM queue are displayed under RSM Queue Details.
If a queue has been recently added in RSM and you do not see it in the list, use the Refresh Queues action at the bottom of the RSM Queue drop-down to update the queue list.
Job Name: The name that will be reported in the RSM job log. The
default name for a Workbench job is Workbench, or whatever is set
for the Default Job Name in your Workbench Options. The default name
for a Mechanical job submitted from the Mechanical application is
Mechanical. The job name provides a traceable piece of data
that administrators can use to track job submissions to a cluster (for billing purposes,
for example).
Job name overrides must adhere to the following conventions:
Can only use alphanumeric characters and ~ # % ^ , & * ' ( ) - _ + = / < >
Cannot exceed 15 characters
The first character must be one of the alphanumeric characters (a-z, A-Z, 0-9)
Download Progress Information- Specifies that the solver monitor should periodically query RSM or the EKM Portal for output files in order to display progress (where applicable). Queries begin when you initiate an action to display the solution progress (such as choosing the Display Monitors option in CFX). This option, available for Fluent and CFX systems, is enabled by default.
CFX systems have the following options:
Always Download Progress Information causes queries to RSM or the EKM Portal to begin immediately. This option is enabled by default.
Download Progress Information on Demand causes queries to RSM or the EKM Portal to begin when you initiate an action to display the solution progress (such as choosing the option in CFX).
Polyflow and ANSYS Icepak systems have the following check box:
Download Progress Information - specifies that the solver monitor should periodically query RSM or the EKM Portal for output files in order to display progress (where applicable). Queries begin when you initiate an action to display the solution progress. This option is enabled by default.
Progress Download Interval - Specifies the periodic time interval with which the solver should query RSM or the EKM Portal for output files in order to display progress. Default is 30 seconds. Setting this value to zero (0) results in continuous queries; that is, as soon as files are downloaded from the execution node, ANSYS Workbench will immediately query again. This option is available for Fluent and CFX systems.
Execution Mode - Specifies serial or parallel solver execution mode. The parallel option is available only if the selected solver supports parallel execution mode. This option may not be available with all systems. When performing a design point update via RSM or the EKM Portal with component update in the foreground, the Parameter Set properties will override the parallel-process settings in individual components. For details on updating design points, see Updating Design Points via ANSYS Remote Solve Manager or an EKM Portal.
Number of Processes - If parallel execution mode is selected, specifies the number of processes to use for the solution (must be a number greater than or equal to 2).
If you choose Submit to Portal as your Update Option, you will need to specify the following:
Portal Connection - Select the EKM Portal to which you want to submit the project. If no connections are listed, you may need to create a connection or open an existing connection.
Queue - You can select from the batch job submission queues that are currently defined in the EKM Portal.
If a project is unsaved and any cells in your project are configured to use RSM or run in the background, you must save the project or change the solution process settings of those cells to run in the foreground before you can update.
Note: The naming scheme for jobs sent to RSM is as follows:
For Mechanical jobs:
[client machine name]-[Workbench project name]-[design point name]-[Model node name (including cell ID)]-[Environment node name (including cell ID)]-[Solution node name (including cell ID)]
Example: MyWorkstation-MyProject-DP0-Model (A4)-Static Structural (B5)-Solution (B6)
For CFX/Fluent/Polyflow/Mechanical APDL jobs:
[client machine name]-[Workbench project name]-[design point name]-[System name]-[Component name (including cell ID)]
Example: MyWorkstation-MyProject-DP0-CFX-Solution (C3)
The following sections describe how to use the Solution Process settings to submit a job to RSM for each of the solvers (where applicable).