This documentation is for WSO2 Data Services Server 3.2.2. View documentation for the latest release.
FAQ - Data Services Server 3.2.2 - WSO2 Documentation
Skip to end of metadata
Go to start of metadata

DSS deployment

When I set up multiple WSO2 products in my environment (e.g., DSS with WSO2 ESB), should I use dedicated servers?

It is recommended to set up each product in a separate server. For example, WSO2 ESB is used for message mediation. A considerable amount of processing happens in the ESB. The DSS does data service hosting and has a different architecture layer compared to the ESB. If you deploy both the ESB and DSS in the same instance/runtime, it can negatively impact the performance of both. It also makes scaling difficult.

However, you can set up hybrid servers (i.e., installing selected DSS features on top of the ESB and vice versa) using WSO2 products without the above performance concerns. See deploying and clustering WSO2 products for more information.

Server administration and troubleshooting

How can I get a SOAP response when invoking an IN-ONLY operation?

Setting "returnRequestStatus" attribute to true in dataservice operation as shown below will return the response for IN-ONLY operations.

<operation name="operation1" returnrequeststatus="true">
<call-query href="query1">
   <with-param name="dm1" query-param="dm1"/>
   <with-param name="dm2" query-param="dm3"/>


Why does the server slow down gradually when invoking a service in transport scope?

When we have transport session scoped services (when boxcarring is enabled), if the HTTP session is not maintained, Axis2 server creates new context objects in the back-end for each request. These objects pile up and will ultimately run out of memory. Therefore, when boxcarring is enabled, the user always has to retain the session (send back the session cookie) to prevent the server slowing down and eventually running out of memory. If Axis2 client is used to send requests, set 'Options.setManagedSession(true)'.

  • No labels