Universal Messaging 10.1 | Developer Guide | Enterprise APIs | Enterprise Developer's Guide for Java | Message Queues | Event Fragmentation
Event Fragmentation
Universal Messaging is capable of sending large messages. The maximum message size is given by the configuration parameter MaxBufferSize. For a description of this parameter, see the section Realm Configuration in the description of the Enterprise Manager in the Universal Messaging Administration Guide.
However, to get the best performance out of the system, it is important to consider how the data for such events is sent. In some cases, it might be better to compress or fragment the message rather than increasing MaxBufferSize.
If you want to send a large file, you could first compress the file before attaching it to an nConsumeEvent as a byte array. It takes time to compress data but as long as the data compresses well, you may find that the by reducing the network utilization, your system operates more efficiently.
Another option is to fragment the data. To fragment the data you need to convert to a byte array as before, but split the byte array and send multiple nConsumeEvent requests rather than one. By doing this, the events are handled completely separately by the server, so there are some things to consider; for example, this approach will not work if you are using a queue with multiple consumers.