Setting Permissions for a Specific Job

You can set access permission for particular jobs stored in a SIMULIA Execution Engine database.

Alternatively, if all your job permissions will be the same for every job, you can set the job permission values prior to execution. For more information, see Setting Default Permissions.

  1. Open the Job Database interface as described in Accessing the Job Database Interface.
  2. Select a job from the Job List.
  3. Do one of the following:

    • Click the on the right side of the Job Database interface.

    • Right-click the job, and click Edit Job ACL.

    • Click Load Job to load the job into the gateway and do one of the following:

      1. Click the arrow next to the Run button toolbar, and select Configure and Run Model or Configure and Run Component.
      2. From the Run menu, select Configure and Run Model or Configure and Run Component.

  4. Click Set Job Permissions.

    Note: This button is available only if you are connected to a SIMULIA Execution Engine.

    The Job Permissions dialog box appears.

  5. Click Add to create a new permission.

    The mouse cursor appears in the Managed Name field.

  6. In the Managed Name column, enter the user name or group name whose permissions you are setting.
  7. Click the Permission field, and select the type of permission:
    OptionDescription
    ALTER Select this option to give the user or group full access to the job, including the ability to edit the job’s permissions. The user or group can view the details of the job, load the job into the Runtime Gateway and watch it run, and view any results generated by the job. The user or group can also pause, resume, and stop the job while it is running, and they can delete the job and all its results at any time.
    MODIFY Select this option to give the user or group all the accessibility granted with the ALTER option, with the exception of editing the permissions.
    READ Select this option to allow the user or group to only view the job’s simulation process flow and execute it. No parameter access is allowed.
    NONE Select this option to give the user or group no access to the published object or job. In addition, any model that references this object cannot be used.
  8. Click the Represents field, and select if the name specified in the Managed Name column represents an individual user or a predefined group:
    OptionDescription
    USER Select this option to specify a particular user name for the permission you are defining. You can add the user name in the Managed Name column as described in Step 6.
    GROUP Select this option to specify a group of users to share the permission you are defining, instead of creating a permission for each user. You can add the group name in the Managed Name column as described in Step 6.
  9. Click All other users to set permissions (ALTER, MODIFY, READ, or NONE as described above) for all other users (except for those defined explicitly).

    You can also specify that there is no default option for other users (in which case a system default is applied).

  10. Repeat Step 5 through Step 8 for any additional user permissions you want to define.
  11. Arrange the listed users, as desired.

    You can use the Up or Down buttons to move a user up or down in the list. The selected user’s settings move up or down one line. The order of your list is important because a user name may appear in one or more groups (the GROUP option) as well as by itself. Therefore, it is possible for a user to be assigned more than one permission for the same job. If a user has multiple permissions, Isight uses the permission closest to the top of the list to determine the user’s actual permission for the job.

    You can use the Delete button to remove a user from the list.

  12. Click OK.

    Isight saves the permission settings.