Import large files and images


Overview

Importing large files into IBM WCM can have a negative impact on performance. We can adjust several settings to ensure better performance.


Max file size

To set the maximum size of files that can be created...

To remove any limit on file size...

When setting the size, also make sure the system has sufficient disk space to support the setting. `


Disk space requirements:

When importing files, a temporary directory is used to store the files during the upload process. If the size of the uploaded files exceeds the available disk space for the temporary directory, the import operation fails.

When uploading large files, ensure that there is sufficient disk space to accommodate the import. The location of the temporary directory is specified by the property...

.in...


Import large files

  1. Log in to the administrative console for IBM WAS, go to...

    .and set...

    resource.maxUploadSize Specify a value in megabytes corresponding to the size of the largest file that you want to allow to be imported. For example, if you do not want to allow files larger than 34 MB to be imported, set value to 34. IBM recommends this value not exceed 100 MB. You cannot upload files larger than 512 MB.
    resourceserver.maxCacheObjectSize Specify a value of 300 KB or less.
    transaction.sync.remove property Specify a value of true.

  2. Go to...

      Servers | Server Types | WebSphere application servers | portal_server | Server infrastructure | Administration | Custom Properties

    protocol_http_large_data_inbound_buffer Specify the maximum file size in bytes. Should correspond to the value you set for the resource.maxUploadSize property in the WCM WCMConfigService service.

    The property uses bytes. So if you specified a value of 34 MB for the resource.maxUploadSize property, specify a value of 35651584 bytes for...

      protocol_http_large_data_inbound_buffer

  3. Go to...

      Resources | JDBC | Data sources | datasource_name | Custom properties

    .and set...

    fullyMaterializeLobData false

  4. Click...

      Resource | JDBC | Data sources | datasource_name | Connection pool properties

  5. Increase the maximum number of database collections allowed for the application server by increasing the value of the Maximum connections field to a value greater than the default 50 connections.

  6. If you are working with files larger than 100 MB, increase the web containers transaction timeout setting.

    Go to...

      Servers | Server Types | WebSphere application servers | portal_server | Container Services | Transaction service

  7. Increase the value of...

    .from the default setting of 120 seconds.

  8. Increase the maximum number of threads allowed in the thread pool used by the web container.

      Servers | Server Types | WebSphere application servers | portal_server | Thread pools | WebContainer

  9. Set the value of the Maximum Size field to 100 threads.

  10. If you are using IBM HTTP Server v7. increase the connection timeout value for connections to the application.

    1. Click...

        Servers | Server Types | web servers | web_server | plug-in properties | Custom properties | New

    2. In the name field, enter ServerIOTimeout.

    3. In the value field, enter the timeout value in seconds.

        The default value is 60 seconds. However, when working with large files, this default value is typically insufficient and can cause a false server error response to be sent, which in turn causes the portal to reissue the request. Specify a timeout value that is long enough to allow a failing request to receive a response, or enter -1 for an unlimited timeout value.

  11. Click Save to save configuration changes.

  12. Restart the portal for the settings to take effect.

  13. If the portal's policy cache manager indicates that a number of web container threads are hung, set the property...

      cacheinstance.com.ibm.wps.policy.services.PolicyCacheManager.lifetime

    .in the WP CacheManagerService service to a value of -1. This setting reduces the database connections and load times and helps prevent threads from hanging.


Parent

Configure a web content authoring environment


Previous


Set service configuration properties


+

Search Tips   |   Advanced Search