When the GWWS is booted and SALT proxy services are advertised, you can create an Oracle Tuxedo application to call them. To develop a program to access SALT proxy services, do the following:

1. Check the Oracle Tuxedo Service Metadata Repository definition to see what the SALT proxy service interface is.
2. Locate the generated FML32 field table files. Modify the FML32 field table to eliminate conflicting field names and assign a valid base number for the index.

   Note:

   The wsdlcvt generated FML32 field table files are always used by GWWS. You must make sure the field name is unique at the system level. If two or more fields are associated with the same field name, change the field name. Do not forget to change Oracle Tuxedo Service Metadata Repository definition accordingly. The base number field index in the generated FML32 field table must be changed from the invalid default value to a correct number to ensure all field indexes in the table are unique at the entire system level.
3. Generate FML32 header files with mkfldhdr32(1)
4. Boot the GWWS with correct FML32 environment variable settings.
5. Write a skeleton C source file for the client to call the outbound service (refer to Oracle Tuxedo documentation and the Oracle Tuxedo Service Metadata Repository generated pseudo-code if necessary). You can use tpcall(1) or tpacall(1) for synchronous or asynchronous communication, depending on the requirement.
6. For FML32 buffers, you must add each FML32 field (conforming to the corresponding SALT proxy service input buffer details), defined in the Oracle Tuxedo Service Metadata Repository ( including FML32 field sequence and occurrence). The client source may include the generated header file to facilitate referencing the field name.
7. Get input buffer ready. You can handle the returned buffer, which should be of the type defined in Metadata.
   • Compile the source to generate executable.
   • Test the executable.