Adjusting transaction timeouts

Some of the functions (such as import/export, and comparison) might take longer than expected, depending on the size of the data to be imported. To avoid frequent timeouts, adjust the following WebSphere® Application Server settings.

Procedure

  1. In the administrative console, go to Application Servers > Open transaction service.
  2. Set the transaction timeouts as shown:
    • Runtime
      • Total transaction lifetime timeout = 0
      • Async response timeout = 0
      • Client inactivity timeout = 0
      • Maximum transaction timeout = 0
    • Configuration
      • Total transaction lifetime timeout = 0
      • Async response timeout = 0
      • Client inactivity timeout = 0
      • Maximum transaction timeout = 0
    These settings disable the timeouts. If a different setting is needed, configure it so.
  3. Start the minimum heap size of 512 MB and maximum heap size of 1024 MB for an InfoSphere® MDM Reference Data Management Hub application server instance.
    Note: If the usage pattern for the Reference Data Management hub involves multiple concurrent exporting, importing, or cloning operations for reference data set or mapping with a large amount of volume, increase the maximum heap size to over 1024 MB.
  4. Additionally, for creating a version of a large set or mapping, configure the following timeouts for web service client binding ports.
    1. Using the administrative console, browse to the enterprise applications page and click the RDMClientEAR.
    2. On the Configuration tab, click Manage Modules.
    3. On the Manage Modules tab, click RDM_JAX-WS_Client.jar.
    4. On the Configuration tab, click Web services client bindings.
    5. For the RDMService web service, click the Edit... link in the Port Information column and set the Request Timeout to 3000 seconds.