|
|
This section contains the following topics:
If the GWWS server fails to start, check the following:
Check the Tuxedo service contract configuration in the Tuxedo Service Metadata Repository.
The GWWS server requires an extra license from BEA to enable the functionality. Check to make sure it has been installed properly.
Check the GWWS server port defined in the SALT configuration file. Avoid port conflicts with other applications.
Check the GWWS instance ID to make sure the two names are consistent in UBBCONFIG and SALT configuration files.
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.
If the GWWS server is set to RESTART=Y in the UBBCONFIG file, REPLYQ=Y also must be defined.
Make sure the SALT configuration file is accessible and set correctly for the GWWS server.
In some cases, the GWWS server may reject SOAP requests. The most common causes are:
The WSDL document used by SOAP clients is out of date and some services may not be available.
When exporting a Tuxedo service with FML/VIEW buffers to a Web service, make sure the related GWWS environment variables are set with valid values. The GWWS server needs this information for the data mapping conversion.
Check the SOAP client data and make sure Tuxedo Service Metadata Repository restrictions are not violated.
Make sure the Tuxedo service you want exported as a Web service is available.
The GWWS server supports 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 command.
The reserved trace category, msg, is used to trace BEA SALT messages. It can be used together with other general trace categories. For example, if trace category "atmi+msg" is specified, both BEA SALT and Tuxedo ATMI trace messages are logged.
| Notes: | Message tracing is recommended for diagnostic treatment only. |
| Note: | The following trigger specifications are not recommended for GWWS servers: |
| Note: | abort, system, sleep |
| Note: | In any of these trigger specifications are used, GWWS servers may be unexpectedly terminated. |
For more tmtrace and trace specification information, see tmtrace(5) in the File Formats, Data Descriptions, MIBs, and System Processes Reference.
TMTRACE specification examples for BEA SALT message tracing are shown below:
Listing A-1 shows a ULOG file example containing BEA SALT tracing messages.
183632.BOX1!GWWS.4612.4540.0: TRACE:ms:A HTTP message is received, SCO index=1023
183632. BOX1!GWWS.4612.4540.0: TRACE:ms:A SOAP message is received, SCO index=1023
183632. BOX1!GWWS.4612.4540.0: TRACE:ms:Begin data transformation of request message, buffer type = STRING, SCO index=1023
183632. BOX1!GWWS.4612.4540.0: TRACE:ms:End of data transformation of request message, buffer type = STRING, SCO index=1023
183632. BOX1!GWWS.4612.840.0: TRACE:ms:Delivering a message to Tuxedo, service name =TOUPPER, SCO index=1023
183632. BOX1!GWWS.4612.840.0: TRACE:ms:Got a message from Tuxedo, SCO index=1023
183632. BOX1!GWWS.4612.4540.0: TRACE:ms:Begin data transformation of reply message, buffer type = STRING, SCO index=1023
183632. BOX1!GWWS.4612.4540.0: TRACE:ms:End of data transformation of reply message, buffer type = STRING, SCO index=1023
183632. BOX1!GWWS.4612.4540.0: TRACE:ms:Send a http message to net, SCO index=1023
A more complex log is generated by TMTRACE=msg:ulog, used in WS-ReliableMessaging communication. All the application and infrastructure messages are sent to the ULOG file.
Listing A-2 shows a ULOG file example containing WS-ReliableMessaging TMTRACE messages.
184706.BOX1!GWWS.3640.4772.0: TRACE:ms:A HTTP message is received, SCO index=1023
184706.BOX1!GWWS.3640.4772.0: TRACE:ms:A HTTP Get request is received, SCO index=1023
184706.BOX1!GWWS.3640.4772.0: TRACE:ms:Send a http message to net, SCO index=1023
184710.BOX1!GWWS.3640.4772.0: TRACE:ms:A HTTP message is received, SCO index=1022
184710.BOX1!GWWS.3640.4772.0: TRACE:ms:A SOAP message is received, SCO index=1022
184710.BOX1!GWWS.3640.4772.0: TRACE:ms:Create a new inbound sequence, ID=uuid:4F1FEE40-72CB-118C-FFFFFFC0FFFFFFA8FFFFFFEB010000-1811
184710.BOX1!GWWS.3640.4772.0: TRACE:ms:Create a new outbound sequence, ID=uuid:f7f76200-f612-11da-990d-9f37c3d14ba7
184710.BOX1!GWWS.3640.4772.0: TRACE:ms:Send CreateSequenceResponse message for sequence uuid:4F1FEE40-72CB-118C-FFFFFFC0FFFFFFA8FFFFFFEB010000-1811
184710.BOX1!GWWS.3640.4772.0: TRACE:ms:Send a http message to net, SCO index=1022
184712.BOX1!GWWS.3640.3260.0: TRACE:ms:A HTTP message is received, SCO index=1022
184712.BOX1!GWWS.3640.3260.0: TRACE:ms:A SOAP message is received, SCO index=1022
184712.BOX1!GWWS.3640.3260.0: TRACE:ms:Begin data transformation of request message, buffer type = STRING, SCO index=1022
184712.BOX1!GWWS.3640.3260.0: TRACE:ms:End of data transformation of request message, buffer type = STRING, SCO index=1022
184712.BOX1!GWWS.3640.3260.0: TRACE:ms:Received a request message in sequence uuid:4F1FEE40-72CB-118C-FFFFFFC0FFFFFFA8FFFFFFEB010000-1811
If the WSDL document does not generate correctly, or is rejected by the SOAP client toolkit, do the following:
tmwsdlgen to generate the WSDL document manually and compare with the one provided by GWWS online downloading. If the
TMETADATA 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. You can use
wsadmin->creload to dynamically reload the configuration file.
|