SALT only supports the Oracle Tuxedo Request/Response communication patterns for outbound service calls. An Oracle Tuxedo application can request the SALT proxy service using the following communication Oracle Tuxedo ATMIs:

• tpcall(3c) / tpacall(3c) / tpgetreply(3c)

  These basic ATMI functions can be called with an Oracle Tuxedo typed buffer as the input parameter. The return of the call also carries an Oracle Tuxedo typed buffer. All these buffers conform to the converted outside Web service interface. tpacall/tpgetreply are not related to SOAP async communication.

• tpgetcallinfo(3c)/tpsecallinfo(3c)

  tpgetcallinfo() retrieves HTTP headers associated with an application buffer using the GWWS gateway in FML32 format; tpsetcallinfo() performs the reverse (i.e., attach FML32 formatted HTTP headers to an application buffer to be sent to a remote HTTP (possibly SOAP) server).

• tpforward(3c)

  Oracle Tuxedo server applications can use this function to forward an Oracle Tuxedo request to a specified SALT proxy service. The response buffer is sent directly to the client application response queue as if it is a traditional native Oracle Tuxedo service.

• TMQFORWARD enabled queue-based communication.

  Oracle Tuxedo system server TMQFORWARD can accept queued requests, and sends them to SALT proxy services that have the same name as the queue.

For more information, see Oracle Tuxedo ATMI C Functions and File Formats, Data Descriptions, MIBs, and System Processes Reference

SALT does not support the following Oracle Tuxedo communication patterns:

• Conversational communication
• Event-based communication