Table of Contents

Search

  1. Preface
  2. Introduction to Informatica MDM - Supplier 360
  3. Supplier 360 Installation Overview
  4. Before You Install
  5. Installing the Supplier 360 Components
  6. After You Install
  7. Business Processes for Supplier Management
  8. Customizing Supplier 360
  9. Upgrading MDM - Supplier 360
  10. Troubleshooting

Installation and Configuration Guide

Installation and Configuration Guide

Improving Performance of Bulk Data Import

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.
  1. Go to the following directory:
    <MDM installation directory>/app/tsr/config/
  2. In a text editor, open the
    s360-portal-workflow-config.xml
    file.
  3. 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
    .
  4. 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.
  5. Go to the following directory:
    <MDM installation directory>/hub/server/resources
  6. In a text editor, open the
    cmxserver.properties
    file.
  7. 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.
  8. Restart the application server.

0 COMMENTS

We’d like to hear from you!