It is not required to run the export task on a dedicated server, but you should consider it if you expect to export a large amount of data. The export task is efficient at transferring data from Identity Manager to the warehouse, and will consume as much CPU as possible during the export operation. If you do not use a dedicated server, you should restrict the server from handling interactive traffic, because the response time will degrade dramatically during a large export.
From the Data Exporter Configuration page, click the Edit link that is in the Warehouse Task Configuration section.
Select an option from the Startup Mode drop-down menu to determine whether the warehouse task starts automatically when Identity Manager starts. Selecting Disabled means the task must be started manually.
Check the Run As Me check box to cause the Exporter task to run under the your administrative account.
Select the servers that the task can run on. You may specify multiple servers, but only one warehouse task can run at any given time. If the server executing the task is stopped, the scheduler automatically restarts the task on another server from the list (if available).
Specify the number of records read from the queue into a memory buffer before writing in the Queue read block size field. The default value for this field is good for most exports. Increase this value if the Identity Manager repository server is slow compared to the warehouse server.
Specify the number of records written to the warehouse in a single transaction in the Queue write block size field.
Specify the number of Identity Manager threads to use for reading queued records in the Queue drain Thread Count field. Increase this number if the queue table has a large number of records of different types. Decrease this number if the queue table has few data types.
Click Save to save your configuration changes and return to the Data Exporter Configuration page.