Last updated on APRIL 27, 2017
Applies to:Oracle Service Architecture Leveraging Tuxedo (SALT) - Version 12.1.3 and later
Information in this document applies to any platform.
On SALT 12.1.3 version, User has COBOL copybook exposed as webservice using Tuxedo + SALT + TMA for SNA.
User is running workflow that starts with the Tuxedo server, goes to the TMA for SNA, and then into the CICS and go to DB2.
When user tested with SoapUI along with TMTRACE=ws:ulog:dye enabled the followings are logged in Tuxedo ULOG:
090106.server!GWSNAX.19975.1617527264.0: LIBGWS_CAT:9087: WARN: Input buffer is smaller than RECORD, received(197), configured RECORD length(325)
090106.server!GWWS.19969.3610546656.0: TRACE:ws:GWWS_CAT:1627: TRACE: Got a message from Tuxedo, SCO index=4094
090106.server!GWWS.19969.3563685632.0: TRACE:ws:Sending SOAP Message: <?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:tuxedo="urn:pack.COPYBook_typedef.salt11" xmlns:tx="http://www.oracle.com/tuxedo"><SOAP-ENV:Header><tx:tpurcode>0</tx:tpurcode></SOAP-ENV:Header><SOAP-ENV:Body><SOAP-ENV:Fault><faultcode>SOAP-ENV:Server</faultcode><faultstring>GWWS_CAT:1054: Internal Error: Failed to get output type from configuration.</faultstring></SOAP-ENV:Fault></SOAP-ENV:Body></SOA
If user hard coded the test data then the work-flow worked but does not actually call DB2.
If user did not hard coded the test data then the call does DB2 work, the transaction will abend with AD2U.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms