Question & Answer
Question
Large Workflow mappings may exceed the maximum parameters allowed by default in WebSphere 7.0.0.23 and newer releases. How can this be fixed for WAS Liberty Profile opposed to a used WAS Full profile?
Cause
SYMPTOM: Will show up when:
When adding a new Smart Section
Adding an equivalent section to the form
Creating a new workflow to map data into this Smart Section
Editing map section
After clicking "Clear All" and mapping the required data
Then clicking "OK"
The edit map window does not close but just refreshes with a 'null' message at the top. The defined mapping is not saved.
****************************************************************
COM.IBM.WS.WEBCONTAINER.MAXPARAMPERREQUEST property for WebSphere Liberty Profile may be required to be set to UNLIMITED on IBM TRIRIGA servers for handling large Workflow mapping
Starting with WebSphere 7.0.0.23, a new Web Container property was introduced called: com.ibm.ws.webcontainer.maxParamPerRequest.
This setting defaults to 10000. See the WebSphere Web container custom properties technote for more details.
The default setting may prevent large workflow mappings from saving due to the restriction on the parameters. Whereas this applied mainly to a FULL WebSphere profile, from WAS 8.5.x you can now also use a different WAS profile, namely WAS Liberty Profile.
Answer
For WAS Liberty profile you can use the following solution to get around this problem:
In your server.xml (<TRIRIGA install>/wlp/usr/server/tririgaServer dir) add the following part:
<webContainer deferServletLoad="false" maxParamPerRequest="-1"/>
Related Information
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21962614