Hi Jyoti,

You can the the increase the length of the payload by modifiying xmlmanger settings 

update the xml manger of ther service with JSON Settings 

either you can create a new xml manger specific to this service and edit the add new JSON Settings with the size limit that you would require





hope this is what yiou are looking for.

Thanks & Regards

Avianash

Hi Jyoti,

yes we can do it to specific servic . We just need to create a new xml manger specific to this service and then you can modify the settings accordingly.

Thanks

Avinash 

Hi Jyoti,

yes we can do it to specific servic . We just need to create a new xml manger specific to this service and then you can modify the settings accordingly.

Thanks

Avinash 

Hi Jyoti,

yes we can do it to specific servic . We just need to create a new xml manger specific to this service and then you can modify the settings accordingly.

Thanks

Avinash 

Hi Jyoti,

yes we can do it to specific servic . We just need to create a new xml manger specific to this service and then you can modify the settings accordingly.

Thanks

Avinash 

Hi Jyoti,

yes we can do it to specific servic . We just need to create a new xml manger specific to this service and then you can modify the settings accordingly.

Thanks

Avinash 

Hi Jyoti,

yes we can do it to specific servic . We just need to create a new xml manger specific to this service and then you can modify the settings accordingly.

Thanks

Avinash 

Hi All,
There is a lot to catch up on with this thread. 

1. Although this is a DataPower forum this thread started out asking about API Connect v5 which was implemented as a MultiProtocol Gateway Service which references an XML Manager which references JSON settings.  The only place where the JSON settings is enforced in a MPGW would be on a HTTP Convert action with JSON encoding which produces a JSONx output.   APIC v5 uses this action always on the request rule for JSON requests and optionally on the response rule based upon an API property being set to true to enforce response JSON payload sizes.  If in GatewayScript, a JSON.parse(someJSONstring) doesn't use these limits as the parse is being done by the JavaScript engine which doesn't have knowledge of the DataPower JSON settings.  If any MPGW has a request or response type configured as JSON, then I believe this HTTP Convert with JSON encoding is happening "under the covers" in a similar manner as the request or response type would be configured as XML which would use the XML parser settings.  As noted, the XML Manager / JSON settings are service wide settings with no ability to customize how a particular HTTP Convert action within the service behaves, so it needs to be configured to the maximum sizes that would be allowed for all  requests coming into the service.   As for submitting RFEs, they are always welcomed and encouraged.  https://integration-development.ideas.ibm.com/?project=DPGWY for DataPower and https://integration-development.ideas.ibm.com/?project=APICONN for API Connect are links where you can submit your ideas.
2. There was a comment about manually updating the XML Manager settings and a subsequent comment about them being overwritten.  Again I assume this is an API Connect concern about updating a v5 object such as the webapi XML Manager or JSON settings object, only to have them redeployed to the default settings when you would deploy a new DataPower Gateway or upgrade  an existing one.  In this case, to allow the updated settings to be preserved in this case, you should utilize a Gateway Extension that would deploy your updated XML Manager or JSON settings upon deployment/upgrade.  The Gateway Extension can be used in a couple ways, but its simplest form is a DataPower export that would contain DataPower objects that would be deployed after the base framework has been deployed, thus you could have the webapi xml manager and json settings objects as the only two object in this zip file.  You'd associate the zip file as the Gateway Extension using the API Connect CMC.
3.  As for the most recent question, I'd add to Joseph's questions what specific error are you getting? You have the overall document size but also the value of a specific property that could also be an issue.  Also, what is meant in comment 10 by "Policy set as default"?

Hi Jyoti,

yes we can do it to specific servic . We just need to create a new xml manger specific to this service and then you can modify the settings accordingly.

Thanks

Avinash 

Hi All,
There is a lot to catch up on with this thread. 

1. Although this is a DataPower forum this thread started out asking about API Connect v5 which was implemented as a MultiProtocol Gateway Service which references an XML Manager which references JSON settings.  The only place where the JSON settings is enforced in a MPGW would be on a HTTP Convert action with JSON encoding which produces a JSONx output.   APIC v5 uses this action always on the request rule for JSON requests and optionally on the response rule based upon an API property being set to true to enforce response JSON payload sizes.  If in GatewayScript, a JSON.parse(someJSONstring) doesn't use these limits as the parse is being done by the JavaScript engine which doesn't have knowledge of the DataPower JSON settings.  If any MPGW has a request or response type configured as JSON, then I believe this HTTP Convert with JSON encoding is happening "under the covers" in a similar manner as the request or response type would be configured as XML which would use the XML parser settings.  As noted, the XML Manager / JSON settings are service wide settings with no ability to customize how a particular HTTP Convert action within the service behaves, so it needs to be configured to the maximum sizes that would be allowed for all  requests coming into the service.   As for submitting RFEs, they are always welcomed and encouraged.  https://integration-development.ideas.ibm.com/?project=DPGWY for DataPower and https://integration-development.ideas.ibm.com/?project=APICONN for API Connect are links where you can submit your ideas.
2. There was a comment about manually updating the XML Manager settings and a subsequent comment about them being overwritten.  Again I assume this is an API Connect concern about updating a v5 object such as the webapi XML Manager or JSON settings object, only to have them redeployed to the default settings when you would deploy a new DataPower Gateway or upgrade  an existing one.  In this case, to allow the updated settings to be preserved in this case, you should utilize a Gateway Extension that would deploy your updated XML Manager or JSON settings upon deployment/upgrade.  The Gateway Extension can be used in a couple ways, but its simplest form is a DataPower export that would contain DataPower objects that would be deployed after the base framework has been deployed, thus you could have the webapi xml manager and json settings objects as the only two object in this zip file.  You'd associate the zip file as the Gateway Extension using the API Connect CMC.
3.  As for the most recent question, I'd add to Joseph's questions what specific error are you getting? You have the overall document size but also the value of a specific property that could also be an issue.  Also, what is meant in comment 10 by "Policy set as default"?

Hi Jyoti,

yes we can do it to specific servic . We just need to create a new xml manger specific to this service and then you can modify the settings accordingly.

Thanks

Avinash 

Hi All,
There is a lot to catch up on with this thread. 

1. Although this is a DataPower forum this thread started out asking about API Connect v5 which was implemented as a MultiProtocol Gateway Service which references an XML Manager which references JSON settings.  The only place where the JSON settings is enforced in a MPGW would be on a HTTP Convert action with JSON encoding which produces a JSONx output.   APIC v5 uses this action always on the request rule for JSON requests and optionally on the response rule based upon an API property being set to true to enforce response JSON payload sizes.  If in GatewayScript, a JSON.parse(someJSONstring) doesn't use these limits as the parse is being done by the JavaScript engine which doesn't have knowledge of the DataPower JSON settings.  If any MPGW has a request or response type configured as JSON, then I believe this HTTP Convert with JSON encoding is happening "under the covers" in a similar manner as the request or response type would be configured as XML which would use the XML parser settings.  As noted, the XML Manager / JSON settings are service wide settings with no ability to customize how a particular HTTP Convert action within the service behaves, so it needs to be configured to the maximum sizes that would be allowed for all  requests coming into the service.   As for submitting RFEs, they are always welcomed and encouraged.  https://integration-development.ideas.ibm.com/?project=DPGWY for DataPower and https://integration-development.ideas.ibm.com/?project=APICONN for API Connect are links where you can submit your ideas.
2. There was a comment about manually updating the XML Manager settings and a subsequent comment about them being overwritten.  Again I assume this is an API Connect concern about updating a v5 object such as the webapi XML Manager or JSON settings object, only to have them redeployed to the default settings when you would deploy a new DataPower Gateway or upgrade  an existing one.  In this case, to allow the updated settings to be preserved in this case, you should utilize a Gateway Extension that would deploy your updated XML Manager or JSON settings upon deployment/upgrade.  The Gateway Extension can be used in a couple ways, but its simplest form is a DataPower export that would contain DataPower objects that would be deployed after the base framework has been deployed, thus you could have the webapi xml manager and json settings objects as the only two object in this zip file.  You'd associate the zip file as the Gateway Extension using the API Connect CMC.
3.  As for the most recent question, I'd add to Joseph's questions what specific error are you getting? You have the overall document size but also the value of a specific property that could also be an issue.  Also, what is meant in comment 10 by "Policy set as default"?

Hi Jyoti,

yes we can do it to specific servic . We just need to create a new xml manger specific to this service and then you can modify the settings accordingly.

Thanks

Avinash 

Hi All,
There is a lot to catch up on with this thread. 

1. Although this is a DataPower forum this thread started out asking about API Connect v5 which was implemented as a MultiProtocol Gateway Service which references an XML Manager which references JSON settings.  The only place where the JSON settings is enforced in a MPGW would be on a HTTP Convert action with JSON encoding which produces a JSONx output.   APIC v5 uses this action always on the request rule for JSON requests and optionally on the response rule based upon an API property being set to true to enforce response JSON payload sizes.  If in GatewayScript, a JSON.parse(someJSONstring) doesn't use these limits as the parse is being done by the JavaScript engine which doesn't have knowledge of the DataPower JSON settings.  If any MPGW has a request or response type configured as JSON, then I believe this HTTP Convert with JSON encoding is happening "under the covers" in a similar manner as the request or response type would be configured as XML which would use the XML parser settings.  As noted, the XML Manager / JSON settings are service wide settings with no ability to customize how a particular HTTP Convert action within the service behaves, so it needs to be configured to the maximum sizes that would be allowed for all  requests coming into the service.   As for submitting RFEs, they are always welcomed and encouraged.  https://integration-development.ideas.ibm.com/?project=DPGWY for DataPower and https://integration-development.ideas.ibm.com/?project=APICONN for API Connect are links where you can submit your ideas.
2. There was a comment about manually updating the XML Manager settings and a subsequent comment about them being overwritten.  Again I assume this is an API Connect concern about updating a v5 object such as the webapi XML Manager or JSON settings object, only to have them redeployed to the default settings when you would deploy a new DataPower Gateway or upgrade  an existing one.  In this case, to allow the updated settings to be preserved in this case, you should utilize a Gateway Extension that would deploy your updated XML Manager or JSON settings upon deployment/upgrade.  The Gateway Extension can be used in a couple ways, but its simplest form is a DataPower export that would contain DataPower objects that would be deployed after the base framework has been deployed, thus you could have the webapi xml manager and json settings objects as the only two object in this zip file.  You'd associate the zip file as the Gateway Extension using the API Connect CMC.
3.  As for the most recent question, I'd add to Joseph's questions what specific error are you getting? You have the overall document size but also the value of a specific property that could also be an issue.  Also, what is meant in comment 10 by "Policy set as default"?

Hi Jyoti,

yes we can do it to specific servic . We just need to create a new xml manger specific to this service and then you can modify the settings accordingly.

Thanks

Avinash 

Hi All,
There is a lot to catch up on with this thread. 

1. Although this is a DataPower forum this thread started out asking about API Connect v5 which was implemented as a MultiProtocol Gateway Service which references an XML Manager which references JSON settings.  The only place where the JSON settings is enforced in a MPGW would be on a HTTP Convert action with JSON encoding which produces a JSONx output.   APIC v5 uses this action always on the request rule for JSON requests and optionally on the response rule based upon an API property being set to true to enforce response JSON payload sizes.  If in GatewayScript, a JSON.parse(someJSONstring) doesn't use these limits as the parse is being done by the JavaScript engine which doesn't have knowledge of the DataPower JSON settings.  If any MPGW has a request or response type configured as JSON, then I believe this HTTP Convert with JSON encoding is happening "under the covers" in a similar manner as the request or response type would be configured as XML which would use the XML parser settings.  As noted, the XML Manager / JSON settings are service wide settings with no ability to customize how a particular HTTP Convert action within the service behaves, so it needs to be configured to the maximum sizes that would be allowed for all  requests coming into the service.   As for submitting RFEs, they are always welcomed and encouraged.  https://integration-development.ideas.ibm.com/?project=DPGWY for DataPower and https://integration-development.ideas.ibm.com/?project=APICONN for API Connect are links where you can submit your ideas.
2. There was a comment about manually updating the XML Manager settings and a subsequent comment about them being overwritten.  Again I assume this is an API Connect concern about updating a v5 object such as the webapi XML Manager or JSON settings object, only to have them redeployed to the default settings when you would deploy a new DataPower Gateway or upgrade  an existing one.  In this case, to allow the updated settings to be preserved in this case, you should utilize a Gateway Extension that would deploy your updated XML Manager or JSON settings upon deployment/upgrade.  The Gateway Extension can be used in a couple ways, but its simplest form is a DataPower export that would contain DataPower objects that would be deployed after the base framework has been deployed, thus you could have the webapi xml manager and json settings objects as the only two object in this zip file.  You'd associate the zip file as the Gateway Extension using the API Connect CMC.
3.  As for the most recent question, I'd add to Joseph's questions what specific error are you getting? You have the overall document size but also the value of a specific property that could also be an issue.  Also, what is meant in comment 10 by "Policy set as default"?

Hi Jyoti,

yes we can do it to specific servic . We just need to create a new xml manger specific to this service and then you can modify the settings accordingly.

Thanks

Avinash 

Hi All,
There is a lot to catch up on with this thread. 

1. Although this is a DataPower forum this thread started out asking about API Connect v5 which was implemented as a MultiProtocol Gateway Service which references an XML Manager which references JSON settings.  The only place where the JSON settings is enforced in a MPGW would be on a HTTP Convert action with JSON encoding which produces a JSONx output.   APIC v5 uses this action always on the request rule for JSON requests and optionally on the response rule based upon an API property being set to true to enforce response JSON payload sizes.  If in GatewayScript, a JSON.parse(someJSONstring) doesn't use these limits as the parse is being done by the JavaScript engine which doesn't have knowledge of the DataPower JSON settings.  If any MPGW has a request or response type configured as JSON, then I believe this HTTP Convert with JSON encoding is happening "under the covers" in a similar manner as the request or response type would be configured as XML which would use the XML parser settings.  As noted, the XML Manager / JSON settings are service wide settings with no ability to customize how a particular HTTP Convert action within the service behaves, so it needs to be configured to the maximum sizes that would be allowed for all  requests coming into the service.   As for submitting RFEs, they are always welcomed and encouraged.  https://integration-development.ideas.ibm.com/?project=DPGWY for DataPower and https://integration-development.ideas.ibm.com/?project=APICONN for API Connect are links where you can submit your ideas.
2. There was a comment about manually updating the XML Manager settings and a subsequent comment about them being overwritten.  Again I assume this is an API Connect concern about updating a v5 object such as the webapi XML Manager or JSON settings object, only to have them redeployed to the default settings when you would deploy a new DataPower Gateway or upgrade  an existing one.  In this case, to allow the updated settings to be preserved in this case, you should utilize a Gateway Extension that would deploy your updated XML Manager or JSON settings upon deployment/upgrade.  The Gateway Extension can be used in a couple ways, but its simplest form is a DataPower export that would contain DataPower objects that would be deployed after the base framework has been deployed, thus you could have the webapi xml manager and json settings objects as the only two object in this zip file.  You'd associate the zip file as the Gateway Extension using the API Connect CMC.
3.  As for the most recent question, I'd add to Joseph's questions what specific error are you getting? You have the overall document size but also the value of a specific property that could also be an issue.  Also, what is meant in comment 10 by "Policy set as default"?

Hi Jyoti,

yes we can do it to specific servic . We just need to create a new xml manger specific to this service and then you can modify the settings accordingly.

Thanks

Avinash