RSM has changed significantly in Release 18, resulting in a more simplified and efficient architecture. If you have a previous installation of RSM, here are the key changes and concepts you should know about:
RSM runs directly within ANSYS Workbench and Mechanical. No additional RSM processes are required on the client machine.
RSM no longer provides job scheduling. RSM jobs are always submitted to a
cluster, and it is the cluster that will do the job scheduling. Even a user's local
machine (localhost) can be considered a single-node ANSYS RSM
Cluster (ARC). You integrate RSM with clusters by creating cluster
configurations in RSM. Cluster configurations determine how the client
communicates with the cluster, how files are handled, and which queues are available for
job submission. See RSM Configuration.
If you are not integrating with a third-party scheduler, you can use the new ANSYS RSM Cluster (ARC) system to schedule and run jobs. When run as a single-node cluster, an ARC requires no special setup, as job scheduling and execution occur on the same node. When run as a multi-node cluster (like a commercial cluster), you will need to install master/slave cluster services on cluster nodes, and perform other configuration tasks. See ANSYS RSM Cluster (ARC) Configuration.
The RSM Setup Wizard has been removed. The new RSM Cluster Configuration application, with its built-in intelligence and wizard-like responsiveness, helps you create cluster configurations with ease.
There are no longer RSM Manager and Compute Server services. If jobs will be
submitted to a remote cluster, the RSM launcher service
(Ans.Rsm.Launcher.exe) provides a service for launching the
user proxy. There is no need to install any service on the client machine.
RSM no longer has alternate accounts. Instead, the account credentials used to
access a remote cluster are the only credentials cached with RSM. You do not need to cache
credentials when the client machine can directly submit to the cluster (in other words,
Submit Host is localhost).
For improved account security, passwords are always cached on the client machine, even if jobs will be submitted to a remote cluster. Passwords are no longer centrally cached and managed as they were in previous releases.
The Windows RSM Admins group or Linux rsmadmins group is no longer used to control a user's ability to change the RSM configuration. The ability to change RSM configuration settings is fully controlled by IT through a user's file system permissions on the configuration storage directory.
The RSM configuration application no longer provides a standalone job monitoring interface. Job monitoring is now embedded within Workbench and EKM.
For general information on the RSM R18 architecture and workflow, see How RSM Works.