Import large files and images

Because importing large files into IBM Lotus Web Content Management can have a negative impact on performance, you can adjust several settings to ensure better performance when importing files.

If you are running on a UNIX operating system, set the maximum size of files that can be created to be at least the size of the largest file you would need to upload to the content server. Run ulimit -a to view current settings. The command...

ulimit -f unlimited

...removes any limit on file size. Make sure the system has sufficient disk space to support the setting.

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...

jcr.binaryValueFileDir

...in...

profile_root/PortalServer/jcr/lib/com/ibm/icm/icm.properties

Procedure

1. Update...
   PROFILE_HOME/PortalServer/wcm/shared/app/config/wcmservices/WCMConfigService.properties

2. Ensure that the property resource.maxUploadSize is uncommented, and 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, you would specify this.

   resource.maxUploadSize=34

   IBM recommends that this value not exceed 100 MB.

3. Ensure that the property resourceserver.maxCacheObjectSize is uncommented, and specify a value of 300 KB or less.

4. Add the property transaction.sync.remove to the file, and specify a value of true.

   For example:

   transaction.sync.remove = true

5. Save changes.

6. Log in to the administrative console for IBM WAS.

7. Add the property: protocol_http_large_data_inbound_buffer

   1. Go to...

      Servers | Application Servers | portal_server | Server infrastructure | Administration | Custom Properties

   2. Click New.

   3. Enter protocol_http_large_data_inbound_buffer in the Name field.

   4. In the Value field, specify the maximum file size in bytes.

      This value should correspond to the value you set for the resource.maxUploadSize property in WCMConfigService.properties.

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

8. Verify that the fullyMaterializeLobData property value is false.

   • Go to...

     Resource | JDBC | datasource_name | Custom properties.

   • Ensure that the fullyMaterializeLobData property is set to false.

9. Increase the maximum number of database collections allowed for the appserver.

   • Go to...

     Resource | JDBC | datasource_name | Connection pool properties.

   • Increase the value of the Maximum connections field to a value greater than the default 50 connections.

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

    • Go to...

      Servers | Application Servers | portal_server | Container Services | Transaction service

    • Increase the value of the Total transaction lifetime timeout setting from the default setting of 120 seconds.

11. Increase the maximum number of threads allowed in the thread pool used by the Web container.

    • Go to...

      Servers | Application Servers | portal_server | Thread pools | WebContainer

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

12. For IBM HTTP Server Version 7, increase the connection timeout value for connections to the application.

    • Go to...

      Servers | Web servers | web_server | plug-in properties | Custom properties | New

    • In the name field, enter ServerIOTimeout.

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

      Default 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.

13. Click Save to save your configuration changes.

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

15. 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

    ...property 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 topic:

Configure a Web content authoring environment

Related tasks

Set service configuration properties