Service Gateway for Files provides access to import, export and VSAM files that are remote to a Data Object Broker. Other supported accesses from rules to these file types require a Data Object Broker to run on the target system or the use of distributed data.
Service Gateway for Files (z/OS) provides interfaces to import, export and VSAM files. The Gateway ensures that data is presented to and received from TIBCO Object Service Broker rules in a manner consistent with TIBCO Object Service Broker behavior.
The Service Gateway for Files SDK is provided with the Service Gateway for Files. You can use this SDK to build applications to access Adabas, Datacom, and VSAM LDS data from TIBCO Object Service Broker. Refer to
TIBCO Service Gateway for Files
SDK User’s Guide for information about using the SDK. You must add database objects to your TIBCO Object Service Broker 6.0.0 system to use the SDK. For details, refer to
Installing Remote on Separate Host.
Service Gateway for Files must run on the same system as the files that are being accessed. A Service Gateway for Files running on a supported platform can communicate freely with a Data Object Broker on the same or another platform as long as the machines are attached through communications and they are properly configured.
The table definitions for the IMP, EXP, and VSM tables contain an optional field, Server ID. If you specify a value in this field, a Service Gateway for Files will be used for the data access. This field also identifies which Service Gateway for Files to be used.
Location parameters are permitted in the table definition but they must ultimately resolve to your local Data Object Broker as your Service Gateway for Files is logged on there.