1. Select the RBPM Provisioning and Security tab.

2. Select Delegation and Proxy from the left navigation menu.

   The user interface displays the Delegation and Proxy page. To configure the service, you need to make some changes in the Delegation and Proxy Service Settings box.

   

3. Check the Allow All Requests option if you want to display the All option in the Resource Search Criteria drop-down list for the Team Delegate Assignments action. When the All option is available, a delegate assignment can be defined that applies to all resource categories.

4. Define the retention period for delegate, proxy, and availability assignments:

   Field	Description
   Retention time for Delegation assignments	Specifies the number of minutes to retain delegate assignments in the directory after they have expired. The default is 0, which indicates that the assignments will be removed after the expiration time has been reached.
   Retention time for Proxy assignments	Specifies the number of minutes to retain proxy assignments in the directory after they have expired. The default is 0, which indicates that the assignments will be removed after the expiration time has been reached.
   Retention time for Availability settings	Specifies the number of minutes to retain availability settings in the directory after they have expired. The default is 0, which indicates that the assignments will be removed after the expiration time has been reached.

5. Select the e-mail templates you want to use for delegation, proxy, and availability notifications:

   Field	Description
   Delegation notification template	Specifies the language-independent name for the template to use for delegation e-mail notifications. After the template name has been specified, the notification engine can determine which language-specific template to use at runtime. For details on creating and editing e-mail templates, see Section 17.4, Working with E-Mail Templates.
   Proxy notification template	Specifies the language-independent name for the template to use for proxy e-mail notifications. After the template name has been specified, the notification engine can determine which language-specific template to use at runtime. For details on creating and editing e-mail templates, see Section 17.4, Working with E-Mail Templates.
   Availability notification template	Specifies the language-independent name for the template to use for availability e-mail notifications. After the template name has been specified, the notification engine can determine which language-specific template to use at runtime. For details on creating and editing e-mail templates, see Section 17.4, Working with E-Mail Templates.

1. Select the RBPM Provisioning and Security tab.

2. In the Provisioning Configuration group of actions, select Delegation and Proxy from the left navigation menu.

   The user interface displays the Delegation and Proxy page. To schedule synchronization and cleanup, you need to make some changes in the Synchronization and Cleanup Service box.

   

3. To specify how often you want to activate the synchronization service, type the activation interval (in minutes) in the Synchronization Service Activation Interval field. The default value is 0, which means that the service is not activated.

   When the synchronization service runs, any modifications (or deletions) made to delegate assignments are synchronized with the corresponding availability settings for the user.

4. To specify how often you want to activate the cleanup service, select Cleanup Service Activation Interval, then type the activation interval (in minutes). Alternatively, select Cleanup Date and use the calendar tool to specify the date when you want to activate the service. The default value is 0, which means that the service is not activated.

   If no cleanup date is specified, the date is set to null. If no cleanup interval is specified, the interval is set to 0. When a cleanup date is specified, the interval is set to be 0. When an interval value other than 0 is specified, the date is set to null. If you check the cleanup interval option without putting in a number (the default is 0), the interface will show the original cleanup date after you submit the page, just as if you had not performed a submit.

   When the cleanup service runs, all obsolete proxy and delegate assignments are removed from the system.

1. On the Provisioning UI Display Settings page, scroll down to the General Display Settings section of the page.

   

2. Modify any of the following settings, and click Save.

   Setting	Description
   Default number of results displayed per page	Specifies the default number of rows to display in lists shown on the Roles and Resources tab. When a user initiates a query on any of the pages listed above, the User Application caches the data obtained by the query, and returns the number of rows specified for this setting to the browser. Each time the user requests to see the next page, another set of rows is returned from the cache. The default value for this setting is 25.
   Options for number of results displayed per page (use spaces to separate values)	Allows you to specify additional values that the user can select to override the default number of rows displayed on the My Roles, View Request Status, Browse Role Catalog, and Manage Role Relationships pages. The list of values you type must be separated by spaces. Note that the number specified in the Default number of results displayed per page control is always included in the list of values for the user to select. The default value for this setting is 5 10 50 100 500. NOTE:This setting also applies to the Team Tasks page on the Work Dashboard tab and to the Object Selector. The default number of rows displayed on the Team Tasks page and in the Object Selector, however, is not controlled by the Default number of results displayed per page setting. The default number of rows for team tasks is set at 5, and the default number of rows for the Object Selector is set at 10.
   Threshold for browser-based sorting and filtering	Specifies the maximum amount of memory (expressed in rows) for the client browser to use for sorting and filtering. If you specify a very high value, client-side sorting and filtering will be very fast, but an excessive amount of memory might be used on the client. If you specify a very low value, the client-side memory usage might be low, but sorting and filtering might also be too slow. This setting applies only if the size of the result set is less than or equal to the threshold value. If the size of the result set is larger than the threshold value specified, sorting and filtering operations are performed on the server. The default value for this setting is 1000.
   Novell Identity Manager Reporting Module URL	The Uniform Resource Locator (URL) for the Identity Reporting Module. Once the URL has been defined, a user can log in as a Report Administrator, and see the Access Reporting Tool button on the Work Dashboard. When the user clicks this button, the URL defined here is used to open the reporting module in a new window. If the reporting module is running on the same server and port as the User Application, you only need to enter the WAR context name prefixed with a slash [/]. Otherwise, you need to specify the full URL, including the server and port.

To configure the administrative settings for the Tasks list on the Work Dashboard:

1. Scroll down to the Task Settings box:

   

2. To specify whether you want the Task List to be displayed when users first open the dashboard, select either the Yes or No radio button for the Expand Task List in default view of Work Dashboard option.

3. To set the default sort column for the task list, pick the column in the Task Notifications List default sort field. Indicate whether the sort order will be ascending or descending by selecting or deselecting the Descending checkbox.

   The default sort column is required in the task list display. When you select a default sort column, this column is automatically added to the User default columns list.

   To allow the user to override the default sort column and sort order, click the the Allow user to override checkbox.

4. To include a column in the task list, select it in the Available Columns list box, and drag them to the User default columns list box. To remove a column, select it in the User default columns list box and drag it to the Available Columns list box. You can select multiple columns to include or exclude by using the Ctrl or Shift key while clicking on the columns.

   To allow the user to override the column selections you’ve made, click the Allow user to override checkbox. When you click this checkbox, the user interface displays the Available columns for User override list box. Any columns you add to the Available columns for User override list box are included in the Available columns list that the user sees on the Work Dashboard. To allow the user to override the default column list, select and drag one or more columns to the Available columns for User override list box from either the User default columns list box or the Available Columns list box. When you add a column to the Available columns for User override list box, that column is automatically removed from the list box from which you dragged it.

5. To specify how the task details should be displayed when the user clicks on a task, select one of the following options:

   Option	Description
   In line with list	Displays the details within the Task Notifications list, directly under the task selected. This is the default.
   In modal dialog	Displays the details in a separate dialog box that must appears on top of the Task Notifications list. After viewing the details for a task, the user needs to close the dialog to see the list again.

6. To allow the user to claim a task automatically by simply opening the task details, select yes for the Auto-claim when opening Task Details option. When this option is set to no, the user must explicitly select Claim to claim a task.

To configure the administrative settings for the Request Status list on the Work Dashboard:

1. Scroll down to the Request Status Settings box:

   

2. To set the default sort column for the request status list, pick the column in the Request Status List default sort field. Indicate whether the sort order will be ascending or descending by selecting or deselecting the Descending checkbox.

   The default sort column is required in the request status list display. When you select a default sort column, this column is automatically added to the User default columns list.

   To allow the user to override the default sort column and sort order, click the the Allow user to override checkbox.

3. To include a column in the request status list, select it in the Available Columns list box, and drag them to the User default columns list box. To remove a column, select it in the User default columns list box and drag it to the Available Columns list box. You can select multiple columns to include or exclude by using the Ctrl or Shift key while clicking on the columns.

   To allow the user to override the column selections you’ve made, click the Allow user to override checkbox. When you click this checkbox, the user interface displays the Available columns for User override list box. Any columns you add to the Available columns for User override list box are included in the Available columns list that the user sees on the Work Dashboard. To allow the user to override the default column list, select and drag one or more columns to the Available columns for User override list box from either the User default columns list box or the Available Columns list box. When you add a column to the Available columns for User override list box, that column is automatically removed from the list box from which you dragged it.

4. To specify how the request status details should be displayed when the user clicks on one of the items requested, select one of the following options:

   Option	Description
   In line with list	Displays the details within the Request Status list, directly under the request selected. This is the default.
   In modal dialog	Displays the details in a separate dialog box that must appears on top of the Task Notifications list. After viewing the details for a task, the user needs to close the dialog to see the list again.

1. Select the Provisioning tab.

2. Select Engine and Cluster Settings from the left navigation menu.

   The user interface displays the Workflow Configuration Settings page. To configure the engine, you need to make some changes in the Workflow Engine box.

   

3. To change an engine setting, click the target field for the setting and type the new value. The engine settings are described below:

   Engine Setting	Description
   Email Notification (per workflow engine)	Enables or disables e-mail notifications for the entire workflow engine. Defaults to enabled.
   Web Service Activity Timeout (minute)	Specifies the default Web Service activity timeout in minutes. The default is 50 minutes.
   User Activity Timeout (hour, 0 for no timeout)	Specifies the default user activity timeout. The default is 0 days, which indicates no timeout.
   Completed Process Timeout (day)	Specifies the number of days that a completed process state is kept in the workflow database system. The default is 120 days.
   Completed Process Cleanup Interval (hour)	Specifies how often the engine checks for and removes completed processes that have been in the workflow database system for longer than the completed process timeout. The default is 12 hours.
   Pending Process Interval (second)	User activities that are executed on an engine which the process is not bound to are put into a pending state. This interval specifies how often to check for pending activities in order to continue their execution. The default is 30 seconds.
   Retry Queue Interval (minute)	Activities that fail because of suspected database connectivity issues are put on a retry queue. This interval specifies how often the engine attempts to retry these activities. The default is 15 minutes.
   Maximum Thread Pool Size	The maximum number of threads that the engine uses to execute activities. The default is 20.
   Minimum Thread Pool Size	The minimum number of threads that the engine uses to execute activities. When a thread is requested and fewer than the minimum are in the pool, a new thread will be created even if there are idle threads in the pool. The default is 10.
   Initial Thread Pool Size	Number of prestarted threads in the pool when it is created. The default is 5.
   Thread Keep Alive Time (second)	If the pool is larger than the minimum size, excess threads that have been idle for more then the keep alive time will be destroyed. The default is 5 minutes.
   Process Cache Load Factor	The load factor specifies how full the cache is allowed to get before increasing its capacity. If the number of entries in the cache exceeds the product of the load factor multiplied by the current capacity, then the capacity is increased. The default is 0.75.
   Process Cache Initial Capacity	The process cache is backed by a hash map. The capacity is the number of buckets in the hash map. The initial capacity is the number of buckets at the time the cache is created. The default is 700.
   Process Cache Maximum Capacity	Before adding a process to the cache, if the number of processes in the cache equals or exceeds the Process Cache Maximum Capacity, the cache attempts to remove the oldest inactive process from the cache. The maximum capacity is a soft limit, so the number of processes in the cache might exceed the Process Cache Maximum Capacity if there are no inactive processes (only active processes) in the cache. A good value for this setting should be less than product of the Process Cache Initial Capacity and the Process Cache Load Factor. This gives the cache a chance to remove older inactive processes from the cache before having to increase its capacity. Take the following example: Process Cache Initial Capacity = 700; Process Cache Load Factor =.75; Process Cache Maximum Capacity = 500; Number of processes in cache = 500; In this case, the number of processes in the cache that will trigger the cache to grow its capacity and perform a rehash would be 525, because the Initial capacity multiplied by the load factor is equal to 525.In this example, when there are 500 processes in the cache, the cache is approaching the point where it must increase its size and perform a rehash, which is at 525 processes. When another process is added to the cache, the engine attempts to remove the least recently used inactive process instead of letting the cache get closer to 525 processes. The default is 500.
   Maximum Engine Shutdown Timeout (minute)	The engine attempts to shutdown gracefully. When shutting down it stops queuing new activities for execution and attempts to complete any activities already queued. This timeout specifies the maximum time that the engine waits for all queued activities and threads executing activities to complete. If this time is exceeded, the engine halts processing of queued activities and attempts to stop all threads executing activities. The default is 1 minute.

1. Select the Provisioning tab.

2. Select Engine and Cluster Settings from the left navigation menu.

   The user interface displays the Workflow Configuration Settings page. To configure cluster settings, you need to make some changes in the Workflow Cluster box.

   

3. To change a cluster setting, click the target field for the setting and type the new value. The cluster settings are described below:

   Cluster Setting	Description
   Heartbeat Interval (second, minimum 60)	Specifies the interval at which the workflow engine’s heartbeat is updated. When the workflow engine starts up, it detects if its engine ID is already being used by another node in the cluster and refuses to start if the ID is in use. The User Application database maintains a list of engine IDs and engine states. If an engine crashes and is restarted, its last state in the database indicates that it is still running. The workflow engine therefore uses a heartbeat timer, which writes heartbeats at the specified interval, to determine if an engine with its ID is still running in the cluster. If it’s already running, it refuses to start. The minimum value for the heartbeat interval is 60 seconds.
   Heartbeat Factor (minimum 2)	Specifies the factor that is multiplied with the hearbeat interval to arrive at the heartbeat timeout. The timeout is the maximum elapsed time permitted between heartbeats before an engine will be considered timed out. The minimum value for the heartbeat factor is 2.