Parameter values for the ComIbmParserManager component
You can set ComIbmParserManager component properties at the integration server level.
mqsichangeproperties integrationNodeName -e integrationServerName -o ComIbmParserManager -n property_name -v property_value
Use these properties to generate activity log entries that can help to identify where the majority of parser activity is happening in a message flow. The ability to identify where such activity is happening assists in performance tuning.
You can change the following properties and values for the ComIbmParserManager component:
- -n parserWarningThreshold -v value
- This property specifies the frequency, based on the number of parsers that are created on a thread, with which IBM® App Connect Enterprise writes warning messages to the activity log. The value that you specify is the number of parsers that are created on a thread after which a warning message is written to the activity log. The value set for this property must be a positive integer, and the default value is 1000, which means that a warning message is written to the activity log every time 1000 parsers are created on a thread.
- -n fieldWarningThreshold -v value
- This property specifies the frequency, based on the number of fields that are created on a specific parser, with which IBM App Connect Enterprise writes warning messages to the activity log. The value that you specify is the number of fields that are created on a specific parser after which a warning message is written to the activity log. The value set for this property must be a positive integer, and the default value is 100000, which means that a warning message is written to the activity log every time 100,000 fields are created on a specific parser.
- -n scopeChecking -v value
-
This property specifies whether additional scope checking is performed on parsers that are reused in the message flow. Scope checking ensures that parsers are reused only when it is safe to do so. By using the Java™ API, you can reuse parsers across message groups. However, reusing a parser while it is in use by another message group can lead to an abend of the integration server process. For message flows which frequently reuse parsers, this can cause a higher memory requirement. Disabling scope checking can reduce the memory requirement by making parsers eligible for reuse earlier in the flow invocation but protection against cross-message group usage of parsers will be lost.
The value set for this property must be either true or false. The default value is true.