Each GWWS server automatically generates a WSDL document for each deployed inbound native WSDF. The WSDL document can be downloaded from any of the HTTP/S listening endpoints via HTTP GET.Table 2‑1 lists all WSDL document download options.
Table 2‑1 WSDL Download Options Specifies the native WSDF name for the WSDL document. The specified native WSDF must be imported via inbound direction by the GWWS server. If the option is not specified, the first inbound native WSDF is used. Use this option only if you have previously defined mappolicy=raw. Specify the client toolkit used so that the proper WSDL document description for a CARRAY typed buffer MIME attachment is generated. SALT supports WebLogic Server and Axis for SOAP with Attachments. The default value is wls.
Note: The WSDL download URL supported by SALT 2.0 and later is different from the SALT 1.1 release. In SALT 1.1, one GWWS server adaptively supports both RPC/encoded and document/literal message style, both SOAP 1.1 and SOAP 1.2 version, from a given configuration file. In SALT 2.0 and later, each WSDF file associated with the GWWS server must be pre-combined with a certain SOAP version and a certain SOAP message style. So the following WSDL download options for SALT 1.1 GWWS server are deprecated in this release.
Table 2‑2 Deprecated WSDL Download Options The GWWS server is a high performance gateway used between external Web Service application and the Oracle Tuxedo application. 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 the <WSGateway> element property values in the SALT configuration file. The following topics list deployment considerations based on different scenarios. For more information, see Configuring the GWWS Servers in the SALT Configuration Guide.Property: thread_pool_sizeProperty: timeoutProperty: max_content_lengthProperty: max_backlogThe 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.
WARNING: A large backlog value may increase syn-blood attack risk.If one GWWS instance is bottlenecks due to network congestion, low CPU resources and so on, multiple GWWS instances can be deployed with the same Web Service binding on distributed Oracle Tuxedo nodes.
Note: Even though multiple GWWS instances can provide the same logic functionality, from a client perspective, they are different Web service endpoints with different HTTP/S listen ports and addresses.The GWWS server supports Oracle Tuxedo TMTRACE functionality (used to dynamically trace messages). All trace points are logged in the ULOG file. Checking the ULOG file trace information helps to evaluate GWWS server SOAP message problems. GWWS server message tracing behavior is set using the TMTRACE environment variable, or by using the tmadmin chtr sub-command.The reserved trace category, msg, is used to trace SALT messages. It can be used together with other general trace categories. For example, if trace category “atmi+msg” is specified, both SALT and Oracle Tuxedo ATMI trace messages are logged.For more tmtrace and trace specification information, see tmtrace(5) in the File Formats, Data Descriptions, MIBs, and System Processes Reference.Listing 2‑1 shows a ULOG file example containing SALT tracing messages.Listing 2‑1 TMTRACE Messages Logged By GWWS ServerA more complex log is generated by TMTRACE=msg:ulog, used in WS-ReliableMessaging communication. All the application and infrastructure messages are sent to ULOG. Listing 2‑2 shows a ULOG file example containing WS-ReliableMessaging TMTRACE messages.Listing 2‑2 WS-ReliableMessaging TMTRACE MessagesChecking the ULOG tracing information helps to evaluate GWWS server SOAP message problem status.The GWWS server can be monitored with wsadmin utility, which is a command-line tool. This tool can show the running status of GWWS.Listing 2‑3 Use wsadmin to Monitor GWWS$wsadmin
wsadmin - Copyright (c) 2005-2010 Oracle.
Portions * Copyright 1986-1997 RSA Data Security, Inc.
All Rights Reserved.
Distributed under license by Oracle.
SALT is a registered trademark.
> gwstats -i abcd
GWWS Instance : abcd
Inbound Statistics :
---------------------------------
Request Response Succ : 74
Request Response Fail : 32
Oneway Succ : 0
Oneway Fail : 0
Total Succ : 74
Total Fail : 32
Avg. Processing Time : 210.726 (ms)
Outbound Statistics :
---------------------------------
Request Response Succ : 0
Request Response Fail : 0
Oneway Succ : 0
Oneway Fail : 0
Total Succ : 0
Total Fail : 0
Avg. Processing Time : 0.000 (ms)
---------------------------------
Total request Pending : 0
Outbound request Pending : 0
Active Thread Number : 2
> gws -i out -s getTemp
GWWS Instance : out
Service : getTemp
Outboud Statistics :
---------------------------------
Request Response Succ : 333
Request Response Fail : 139
Avg. Processing Time : 143.064 (ms)
>The gwstats command (abbreviated as gws), displays the WWS server statistics data with a specific instance ID or of a certain GWWS server service of the. The data includes the amount of successful and failed request, etc.Before wsadmin is executed, both the TUXCONFIG and SALTCONFIG environment variables must be set. wsadmin supports both active mode and in-active mode, which means wsadmin is able to launch with/without booting the Oracle Tuxedo domain.Table 2‑3 lists wsadmin sub-commands.
Table 2‑3 wsadmin Sub-Commands Specifies the default -i option
• Check if the Oracle Tuxedo Service Metadata Repository Server - TMMETADATA - is booted successfully.Check the GWWS instance ID to make sure the two names defined in UBBCONFIG and SALTDEPLOY file are consistent.
• UBBCONFIG file MAXWSCLIENTS definition.Make sure that MAXWSCLIENTS is defined in theUBBCONFIG file *MACHINE section on the computer where the GWWS server is deployed.
• RESTART=Y and REPLYQ=Y parameters.
• SALTCONFIG file.Make sure the binary version SALTCONFIG file is compiled successfully and the environment variable SALTCONFIG is set correctly for the GWWS server.
• Try to use the document/literal message style and SOAP 1.1 to define native Oracle Tuxedo WSDF file. This is also the default behavior.
• Use tmwsdlgen to generate the WSDL document manually and compare it with the one downloaded by the GWWS server. If the TMMETADATA server is not started when the GWWS server booted, the GWWS server cannot obtain the correct service contract information. Therefore, the downloaded WSDL document does not contain the correct type definitions.
•
•