Configuring SIMULIA Execution Engine Stations for Run-As on Windows

To configure a Windows-based station to use the Run-As security feature, you need to update the station’s properties file, set permissions on the station’s temporary directory, and update the system rights for the users that will be executing on the station.

Note: This procedure must be performed on each system that will run a SIMULIA Execution Engine station.

  1. Perform one of the following steps, based on your security arrangement:
    • If you plan on using the same security domain for the SIMULIA Execution Engine station as specified for a Windows-based SIMULIA Execution Engine, proceed to step 5. This SIMULIA Execution Engine setting is described in Configuring the SIMULIA Execution Engine for Run-As.

    • If you plan on using a different security domain as specified for a Windows-based SIMULIA Execution Engine, proceed to step 2.

    • If you are connecting to a Linux-based SIMULIA Execution Engine, proceed to step 2.

  2. Edit the <see_install_dir>\config\station.properties file and remove the leading # character from the following setting:

    #fiper.security.station.domain
    

  3. Enter the appropriate Windows domain by replacing the DEV string with your Windows domain name. Do not replace the entire line.

    The SIMULIA Execution Engine station will now use this domain to authenticate users’ credentials instead of the domain specified in the acs.properties file.

  4. Save and close the station.properties file.
  5. Grant read, write, execute, create folders, and create files access (or full access) on the SIMULIA Execution Engine station temporary directory to all users that may submit jobs. This temporary directory is specified in the station.properties file. For more information on locating this setting in the station.properties file, see About File System Security With Run-As.

    The steps necessary for granting this access to the SIMULIA Execution Engine station temporary directory differ slightly across Windows operating systems and may require special access rights. For more information, contact your local system administrator.

    This step must be performed on all systems that will be running SIMULIA Execution Engine stations.

  6. Locate the system user rights as described below (based on your operating system):
    • Windows Server 2003: Navigate to Start / Administrative Tools / Local Security Policy; and from the Local Security Settings dialog box, access the User Rights Assignment settings under the Local Policies option.

    • Windows Server 2008: Navigate to Start / Control Panel / System and Maintenance / Administrative Tools / Local Security Policy; and from the Local Security Policy dialog box, access the User Rights Assignment settings under the Local Policies option.

    • Windows 7: Navigate to Start / Control Panel / System and Security / Administrative Tools / Local Security Policy; and from the Local Security Policy dialog box, access the User Rights Assignment settings under the Local Policies option.

  7. For each user who will start a SIMULIA Execution Engine station, add the user to the local Administrators group and grant the user the privilege Replace a process level token in the Local Security Policy dialog box.

    For more detailed information on setting these user rights, contact your local system administrator.

  8. Log out and log back on to the system. This step is necessary for the privilege changes to be recognized.
  9. Repeat step 1 through step 8 for each system that will be running a SIMULIA Execution Engine station.

    Important: If the station is configured as a Windows service, the user starting the service must either be the default service account LocalService or be a member of the Administrators group who has been granted the Replace a process level token privilege. A non-administrator account will not work. For more information on these users settings and their privileges, contact your local system administrator.

  10. Stop and restart WebSphere for the associated SIMULIA Execution Engine. For more information, see Restarting WebSphere with Security Enabled.

    The Run-As configuration is complete. Your SIMULIA Execution Engine and stations will now use Run-As security.

  11. Edit UAC (User Account Controls) Settings (see Editing User Account Controls).