Include Optimizing the XSLT Mediator parameters in WSO2 MI Documentation

Description

When dealing with XML data streams in MI the data is initially stored in a fixed-size buffer. If this buffer overflows which means if the message chunk exceeds a configured threshold (synapse.temp_data.chunk.size) then the data is moved to a temporary file and saved as a tmp_xxxxxxx.dat file in the tmp directory.

Hence to minimise the number of temp files getting generated we can optimise the threshold limits according to the message size through the below properties.

synapse.temp_data.chunk.size
synapse.temp_data.chunk.threshold

Since these parameters decide when to write to the file system when the message size is large and improve the performance of the XSLT mediator by allowing the use of more memory when processing large messages with the XSLT mediator hence it would be difficult to identify these parameters by only referring to the WSO2 MI documentation because Optimizing the XSLT Mediator to perform better for large message sizes is not documentation in the Micro Integrator[1] as we documented in Enterprise Integrator[2].

Therefore can we include the "Optimizing the XSLT Mediator" information with the above parameters default value with information to tune in WSO2 MI documentation as well?

[1] https://apim.docs.wso2.com/en/4.1.0/reference/mediators/xslt-mediator/
[2] https://wso2docs.atlassian.net/wiki/spaces/EI660/pages/6520995/Message+Transformations

We need to evaluate other set of tuning documents we find in EI docs. If they are relevent we have to include those too.

Describe the problem(s)

A detailed description of the purpose of this improvement.

Describe your solution(s)

A detailed description of how this improvement will solve the problem described above.

Related issue(s) (optional)

Any related issues such as sub tasks and issues reported in other repositories (e.g., component repositories), similar problems, etc.

Suggested label(s) (optional)

Optional comma-separated list of suggested labels. Non committers can’t assign labels to issues, and thereby, this will help issue creators who are not a committer to suggest possible labels.

Suggested assignee(s) (optional)

Optional comma-separated list of suggested team members who should attend the issue. Non committers can’t assign issues to assignees, and thereby, this will help issue creators who are not a committer to suggest possible assignees.

Start by comparing the WSO2 MI XSLT Mediator documentation at the linked page with the referenced Enterprise Integrator Message Transformations documentation. Identify the XSLT optimization guidance and defaults for synapse.temp_data.chunk.size and synapse.temp_data.chunk.threshold, then evaluate whether other EI tuning guidance is relevant. Done means the applicable content is added to the MI documentation.