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.
Table 2‑2 Deprecated WSDL Download Options 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.A network receive timeout property is provided in the SALT configuration file. Web service applications are also impacted by the Oracle Tuxedo BLOCKTIME parameter. Blocktime accounting begins when a message is transformed from XML to a typed buffer and delivered to the Oracle 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.
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 process utilizes the TMTRACE trace functionality that is supported by the Tuxedo. The trace feature in the GWWS is used in conjunction with the TMTRACE.The trace can be enabled using the environment variables TMTRACE and GWWS_TRACE_LEVEL. The TMTRACE variable enables the trace. And the environment variable GWWS_TRACE_LEVEL controls the amount of trace that will be logged by the SALT gateway.The trace category ws is used to trace Oracle SALT messages. It can be used together with other general trace categories. For example, if trace category "atmi+ws" is specified, both Oracle SALT and Oracle Tuxedo ATMI trace messages are logged.For more information, see tmtrace(5) in the File Formats, Data Descriptions, MIBs, and System Processes Reference.GWWS_TRACE_LEVEL can be set to 100 or 200. The value '100' provides the least amount of trace information in the ULOG file. The value '200' provides the most amount of trace information.TMTRACE and GWWS_TRACE_LEVEL environment variables can be set as follows:
Note: Be aware of the amount disk space available when the GWWS_TRACE_LEVEL is set to 200 especially for large data buffers since trace will fill the ULOG file.Listing 2‑1 shows a ULOG file example containing SALT tracing messages.
Note: Listing 2‑1 TMTRACE Messages Logged By GWWS Server105106.slc04jtu!GWWS.27653.1379895040.0: TRACE:ws:SCO[4095] FSM State Transition: --OK-->FindServiceThe GWWS server can be monitored using the wsadmin utility, which is a command-line tool. This tool displays GWWS running status.Listing 2‑2 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 (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 the UBBCONFIG 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.OAM integration only supports SALT inbound request, for HTTP Basic Authentication GWWS will extract username and password and calls Tuxedo AUTHSVC to authenticate the user, OAUTHSVR will communicate with OAM to authenticate, if it is successful then GWWS will retrieve OAM session token, the session token will be passed in following service call, OAUTHSVR will use the session token to authorize.For WSSE situation, GWWS will use user credential received and authenticate with Tuxedo, before it calls Tuxedo service it will check if auth level is TPAPPAUTH and insert the session token into context and call Tuxedo service.For 11g WebGate, the OAM token cookie (OAMAuthnCookie) is not passed to downstream applications such as SALT, please specify WebGate user-defined parameter filterOAMAuthnCookie to false. For more information, see ans Setting up OAUTHSVR as the Authentication Server and Registering Managing OAM 11g Agents.Figure 2‑1 WebGate
1.
•
•