Installation and Configuration Guide

10.4 HotFix 3

Back Next

Improving Performance of Bulk Data Import

When you import a file in a workflow-enabled environment, the workflow triggers the approval process in parallel. The parallel processing of workflow might affect the performance of the import process when you import more than 5000 records with child records. To improve the performance of the import process in a workflow-enabled environment, you can now set a wait time for the workflow process to trigger. Based on the wait time, the workflow process gets triggered and avoids parallel processing.

Go to the following directory:

<MDM installation directory>/app/tsr/config/

In a text editor, open the

s360-portal-workflow-config.xml

file.

Update the following properties and save the file:

Property	Description
<property name="portal.fileImport.wait">P0Y0M0DT2H0M0S</property>	Optional. Wait time for the workflow to trigger after the import process starts. For example, if the wait time is 2 hours 30 minutes, then the workflow triggers after 2 hours 30 minutes after the import process starts. You can specify the wait time in the following format: P<n>Y<n>M<n>DT<n>H<n>M<n>S P - Indicates portal. Y - Indicates number of years. M - Indicates number of months. D - Indicates number of days. T - Indicates time. H - Number of hours. M - Number of minutes. S - Number of seconds. For example, the value P0Y0M0DT2H30M0S indicates 2 hours and 30 minutes. Ensure that you set the portal.fileImport property to Y for the wait time to be considered. Default is 2 hours. Informatica recommends to use 1 hour 30 minutes for 5000 records and 2 hours 30 minutes for 10000 records.
<property name"portal.fileImport">Y</property>	Indicates whether to enable wait time for the workflow to trigger. Set to Y to enable the wait time. The wait time improves the performance of import process when you import more than 5000 records. Use this option during the file import or initial data load process. After the data load is complete, change the value from Y to N . Default is N .

Property

Description

Optional. Wait time for the workflow to trigger after the import process starts. For example, if the wait time is 2 hours 30 minutes, then the workflow triggers after 2 hours 30 minutes after the import process starts.

You can specify the wait time in the following format:

P<n>Y<n>M<n>DT<n>H<n>M<n>S

P - Indicates portal.

Y - Indicates number of years.

M - Indicates number of months.

D - Indicates number of days.

T - Indicates time.

H - Number of hours.

M - Number of minutes.

S - Number of seconds.

For example, the value

P0Y0M0DT2H30M0S

indicates 2 hours and 30 minutes.

Ensure that you set the

portal.fileImport

property to

for the wait time to be considered.

Default is 2 hours.

Informatica recommends to use 1 hour 30 minutes for 5000 records and 2 hours 30 minutes for 10000 records.

Indicates whether to enable wait time for the workflow to trigger. Set to

to enable the wait time. The wait time improves the performance of import process when you import more than 5000 records.

Use this option during the file import or initial data load process. After the data load is complete, change the value from

Default is

After you make changes to the properties, run one of the following redeploy scripts to view the changes:

On UNIX.

redeploy.sh

On Windows.

redeploy.bat

Alternatively, you can log in to the ActiveVOS console, navigate to the

Catalog

Resources

Other

section to update the properties in the

s360-portal-workflow-config.xml

file.

Go to the following directory:

<MDM installation directory>/hub/server/resources

In a text editor, open the

cmxserver.properties

file.

Update the following properties and save the file:

Property	Description
cmx.server.be-import.task-limit	Specifies the maximum number of records users can import for the task approval workflow to trigger. Set cmx.server.be-import.task-limit=10000 for users to import up to 10000 records and the task approval workflow to trigger. If a user attempts to import more than 10000 records, the task approval workflow does not trigger and displays an error.
cmx.server.find-replace.task-limit	Specifies the maximum number of replaced records that trigger the task approval workflow. Set cmx.server.find-replace.task-limit=1000 for users to replace up to 1000 records and the task approval workflow to trigger. If a user attempts to import more than 1000 records, the task approval workflow does not trigger and displays an error.