![]() |
![]() |
![]() |
![]() |
![]() |
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. Oracle SALT supports WebLogic Server and Axis for SOAP with Attachments. The default value is wls.
Note: The WSDL download URL supported by Oracle SALT 2.0 and later is different from Oracle SALT 1.1. In Oracle SALT 1.1 release, 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 Oracle 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 Oracle SALT configuration file. The following topics list deployment considerations based on different scenarios. For more information, see Configuring the GWWS Servers in the Oracle 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 Oracle SALT messages. It can be used together with other general trace categories. For example, if trace category “atmi+msg” is specified, both Oracle 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 Oracle 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 MessagesThe 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)
>Command gwstats (abbreviated as gws) can display the statistics data of GWWS server with specific instance ID or of certain service of the GWWS server. The data include the amount of successful and failed request, etc.Before wsadmin is executed, both TUXCONFIG and SALTCONFIG environment variable 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 wsadmin Sub-Commands Specifies the default -i option Check the Oracle Tuxedo service contract definition is correct in the Oracle Tuxedo Service Metadata Repository and 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 *MACHINE section of UBBCONFIG file on the computer where 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 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.The mod_tuxedo Apache module follows Apache HTTP Server and OHS administration and configuration rules. The tux_nsapi planet plug-in follows iPlanet rules administration and configuration rules.HTTP servers using mod_tuxedo or tux_nsapi utilized and implemented just like any other Oracle Tuxedo client application. The PHP/Python/Ruby handler behaves like a regular Oracle Tuxedo application server, but includes extra parameters.For more information see, Oracle SALT Installation Guide, Administering Oracle SALT at Runtime and Configuring an Oracle SALT Application., and Appendix H: Oracle SALT HTTP FML32 Buffer Format in the Oracle SALT Reference Guide.SCA ATMI servers and clients support the Oracle Tuxedo tmtrace(5)function. All traces generated from TMTRACE are logged in the ULOG file. Checking the ULOG file trace information helps to determine the cause of a failure. The Oracle Tuxedo TMTRACE facility is enabled by setting TMTRACE environmental variable, or by using the tmadmin chtr sub-command.
Note: To trace Oracle Tuxedo ATMI messages enter: export TMTRACE=atmi:ulog at the command line.
• SCACPP_LOGGING: Set to a numeric value and controls the number of trace messages produced.
• SCACPP_ULOG: Set to "yes" to send trace messages to the ULOG. If this environment variable is not set or is set to "no", then trace messages are written to standard output.
Note: These tracing facilities are only available for Oracle Tuxedo server builds using buildscaserver and SCA client builds using buildscaclient.Listing 2‑4 shows a ULOG example containing SCA runtime tracing:Listing 2‑4 SCA Runtime Tracing Information ULOG FileAn Oracle Tuxedo SCA server built with the buildscaserver utility can be monitored using the scaadmin utility. This utility shows service statistics information and helps perform maintenance through dynamic shared library loading and unloading.To reload all components hosted by the uBikeServer Oracle Tuxedo server previously built using the buildscaserver command, do the following:Enter the following at the command line to display statistics on the services offered by the uBikeServer Oracle Tuxedo server (Table 2‑4 shows the results):
Table 2‑4 pstats 0utput Service Statics Before scaadmin is executed, you must set the TUXCONFIG environment variable. Table 2‑5 lists scaadmin sub-commands.
Table 2‑5 scaadmin Sub-Commands When multiple servers share the same component library on Windows and HP systems, the shared component library cannot be reloaded. To reload a component library common to multiple servers, the "scaadmin" reload sub-command must be performed on all affected servers simultaneously.The Oracle Tuxedo SCA Java reference binding and data transformation support output to the console and to a log file. By default there are at most 10 log files, the maximum size of each file is 100000 bytes, and are located in $APPDIR with name jatmi<number>.log file. The log file names are cycled with the latest one using the number 0, and the one just before latest one uses 1 (for example. jatmi0.log is the latest log file, and jatmi9.log is the oldest log file). If the APPDIR environment variable is not set and com.oracle.jatmi.APPDIR java property is not specified, the log is placed in the current working directory.By default, the log files are overwritten each time the application starts. Many logger parameters can be fine tuned. Table 2‑6 lists tunable Java properties related to logging.
Table 2‑6 Logger Tuning Property Table APPDIR environmental variable, if APPDIR is not set uses current working directory 0 ... maximum file size supported by the system To have the Oracle Tuxedo SCA Java reference binding log in a different language, first check the supported languages that are installed. The default is English. To switch to a different language, add: "-Duser.language=<your preferred language>" to your Java command line when starting the Oracle Tuxedo SCA Java client. For example:Table 2‑6 shows an example of the log file contents.Listing 2‑5 Log File ContentsAdministering Python, Ruby, and PHP Programming Components is very similar to administering C++ programming components. The Oracle Tuxedo TMTRACE functionality, SCACPP_LOGGING and SCACPP_ULOG environment variables, and scaadmin are all available for monitoring Python, Ruby, and PHP programming components.
Note: The scaadmin command can be used to force reload Python, Ruby, or PHP scripts when their corresponding SCA component definitions have a scope="composite" attribute. For more information, see Python, Ruby, and PHP Component Programming in the Oracle SALT SCA Programming Guide.
•
•
•