|
|
This section contains the following topics:
To view the current SALT configuration, use the following wsadmin command argument:
configstats(cstat) -i InstanceID
This argument displays the current status of the SALT configuration file for the given GWWS process. It outputs the following:
To view GWWS process runtime statistics, use the following wsadmin command argument:
gwstats(gws) -i InstanceID
The gwstats argument displays runtime statistical information for GWWS processes. Option -i is required.
| Note: | The runtime statistics do not apply to work for messages in a sequence for WS-ReliableMessaging specification. |
Table 4-1 shows the resulting displayed information.
The GWWS server is a high performance gateway used between SOAP clients and the Tuxedo framework. It uses a thread-pool working model to improve performance in a multi-processor server environment. The GWWS server also provides options to control runtime behavior by setting <WSGateway> element property values in the BEA SALT configuration file. The following topics list deployment considerations based on different scenarios. For more information, see
Configuring BEA SALT in the BEA SALT Administration Guide.
The default thread pool size is 16, but in some cases this may not be enough to handle high volume loads. It is recommended to conduct a typical usage analysis in order to better estimate the proper size requirement. Usually, if the concurrent client number is large (for example, more than 500), it is suggested that you deploy the GWWS gateway on a server with at least a 4-way processor and set the thread pool size to 64.
BEA SALT provides a network timeout tuning parameter in the configuration file. The default timeout value is 300 seconds.The value can be adjusted to reduce timeout errors.
BEA SALT administrators may want to limit the buffer size sent from a client. SALT supports this by using a property value that can be set for particular GWWS instances. By default there is no limit.
BEA SALT defines the default backlog socket listen value to 20. On some systems, such as Windows, 20 may not meet the heavy load requirements. The client connection is rejected during TCP handshake.
The recommended value for Windows is based on the max concurrent TCP connections you may encounter. For example, if 80 is the peak point, you may configure the max_backlog property value to 60 in the SALT configuration file.
| Note: | The default backlog value is adequate for most systems. You do not need tune it unless you experience client connection problems during heavy loads. |
| WARNING: | A large backlog value may increase syn-blood attack risk. |
A network receive timeout property is provided in the SALT configuration file. Web service applications are also impacted by the Tuxedo BLOCKTIME parameter. Blocktime accounting begins when a message is transformed from XML to a typed buffer and delivered to the Tuxedo framework.
If no reply is received for a particular Web service client within the BLOCKTIME time frame, the GWWS server sends a SOAP fault message to the client and terminates the connection. If the GWWS server receives a delayed reply, it drops this message because the client has been disconnected.
BLOCKTIME is defined in the
UBBCONFIG file *RESOURCE section.
If one GWWS instance is bottlenecked due to network congestion, low CPU resources and so on, multiple GWWS instances can be deployed within the same SALT configuration file on distributed Tuxedo nodes.
| Note: | Even though multiple GWWS instances can provide the same logic functionality, from a client perspective, they are different Web service end points with specific TCP ports and addresses. |
|