1. Programming Guide
  2. Using SALT Plug-Ins
  3. Programming Message Conversion Plug-ins
  4. SALT 1.1 Custom Buffer Type Conversion Plug-in Compatibility

5.2.4 SALT 1.1 Custom Buffer Type Conversion Plug-in Compatibility

SALT 1.1 Custom Buffer Type Conversion Plug-in provides a customized message conversion mechanism only for Oracle Tuxedo custom buffer types.

Table 5-2 SALT 12cR2 Message Conversion Plug-in / SALT 1.1 Custom Buffer Type Conversion Plug-in Comparison

SALT 1.1 Custom Buffer Type Plug-in SALT 12cR2 Message Conversion Plug-in
Plug-in ID is “P_CUSTOM_TYPE” Plug-in ID is “P_CUSTOM_TYPE”
Plug-in Name must be the same as the supported custom buffer type name. Plug-in Name can be any meaningful value, which is only used to distinguish from other plug-in instances.
Only supports message conversion between SOAP message payloads and Oracle Tuxedo custom buffer types. Supports message conversion between SOAP message payloads and any kind of Oracle Tuxedo buffer type.

Buffer type-level association.

Each plug-in instance must be named the same as the supported custom buffer type name. Each custom buffer type can only have one plug-in implementation.

One custom buffer type can associate with a plug-in instance, and used by all the services.

 Message-level association. Each Oracle Tuxedo service can associate plug-in instances with its input and/or output buffers respectively through the plug-in instance name.
SOAP message payload is saved as a NULL terminated string for plug-in programming. SOAP message payload is saved as a Xerces DOM Document for plug-in programming.

Note:

SALT 1.1 Custom Buffer Type Plug-in shared library cannot be used directly in SALT 12cR2. You must perform the following tasks to upgrade it to a SALT 12cR2 message conversion plug-in:
  1. Re-implement function (*soap_in_tuxedo__CUSTBUF) and (*soap_out_tuxedo__CUSTBUF) according to the SALT message conversion plug-in vtable function prototype API. The major change is that the SOAP message payload is saved as an Xerces class DOMDocument object instead of the old string value.
  2. Re-compile your functions as a shared library and configure this shared library in the SALT Deployment file so that it can be loaded by GWWS servers.

Tip:

You do not have to manually associate the upgraded message conversion plug-ins with service buffers. If a custom typed buffer is involved in the message conversion at runtime, GWWS can automatically search a message conversion plug-in that has the same name as the buffer type name if no explicit message conversion plug-in interface is configured.

Parent topic: Programming Message Conversion Plug-ins