![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
This example simulates the Synchronous communication paradigm that is supported by the adapter Request-Response service. The Tuxedo service, based on the DEPTID that it receives from the invoking client (the Request-Response service in this case), returns the EMPID, EMPNAME and DEPTID corresponding to that DEPTID.
1. Loading Field ID Dynamically at run-time — The Field ID for FML32 fields are loaded dynamically from the corresponding field tables at runtime.
2. Loading the Field ID stored in the repository — The Field IDs for FML32 fields are read from the corresponding header files and stored in the repository.
2. TIBCO ActiveMatrix BusinessWorks reads the input data and sends the request. The TIBCO ActiveMatrix BusinessWorks process, rpc gets triggered. The file poller in the process reads the data and forwards it to the Request-Response Invocation service in the process which publishes the data.
3.
5.
7. Files provided with this example are given in the next table. The files are located in the following locations:
Project zip that contains the adapter request-response configuration and the TIBCO ActiveMatrix BusinessWorks process. This file (instead of a database) contains the data that will be used by the server service. Contains commands required to get the Tuxedo service running on Windows (Sets the required environment variables, creates executables, loads the ubbconfig file and boots the Tuxedo service) Contains commands required to get the Tuxedo service running on UNIX (Sets the required environment variables, creates executables, loads the ubbconfig file and boots the Tuxedo service). This script should be run in a k-shell. ubbconfig file Tuxedo field table file containing the FML32 definition for the request buffer.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |