Advanced

The Advanced tab is used to specify the behavior of attachment for the reply message. This is useful if large messages are sent and you want to write them to files instead of storing them in memory. The Advanced tab has the following fields.

Field

Description

Write to File

Checking this field specifies that incoming messages whose attachments exceed the specified threshold size should be written to a file instead of stored in memory. This allows you to accept large incoming attachments without consuming a great deal of memory. When this field is checked, the Directory and Threshold Size fields appear.

Leaving this field unchecked specifies that attachments of incoming messages should be kept in memory.

Note: Once written, the files created by using this option are not deleted automatically. You must manage the storage used by these files and delete them when they are no longer used.

Although Write to File exists for SwA and MTOM, Soap over JMS completely depends on the heap size configuration as JMS specifications do not support writing JMS messages in parts as is the case with Soap over HTTP, which can be written over wire in parts. Hence, writing large JMS messages to JMS after configuring Write to File, completely depends on the Heap size.

Directory

The directory to write attachments that are above the specified threshold. The process engine does not attempt to create the directory if the specified directory does not exist. Therefore, create the directory before starting the process engine.

Create Non-Existing Directories

When checked, all directories in the path specified in the Directory field are created, if they do not already exist.

If this field is unchecked and there are one or more directories in the specified path in the Directory field that do not exist, an exception is raised.

Threshold Size (bytes)

The maximum size (in bytes) of an incoming message attachment that can be kept in memory. Attachments larger than the specified size are written to a file in the specified directory. The file’s name is output so that subsequent activities in the process definition can access the file and read its contents.

Specifying zero (0) in this field causes all incoming messages to be saved to a file.