![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
The Execution Environment runs, or executes, the TIBCO Object Service Broker applications for the end user. It manages such things as:The Execution Environment deals with the Data Object Broker on behalf of the user or application and passes on requests for data and commands to update the database.The Execution Environment makes requests to the Data Object Broker to obtain information, processes the information, and presents it in the form of screen displays or reports. An Execution Environment can connect to only one Data Object Broker, whereas a Data Object Broker can support many Execution Environments. In short, the Execution Environment provides the user and application interface to the physical data.
• Multi-user Execution Environment accessed through the Object Integration Gateway (OIG), ostty, TIBCO Object Service Broker SDK (C/C++), or TIBCO Object Service Broker SDK (Java) clients, or via a 3270 emulator using Telnet 3270.Execution Environments require a number of parameters. System-wide defaults for each type of Execution Environment are defined during installation and each Execution Environment can specify its own defaults at startup.
• TIBCO Object Service Broker Parameters for more information about Execution Environment parameters.
• TIBCO Object Service Broker Object Integration Gateway for more information about Object Integration Gateway.
• TIBCO Object Service Broker for Open Systems External Environments for more information about the SDK (C/C++) and the SDK (Java) clients.
• TIBCO Object Service Broker for Open Systems Utilities for more information about osBatch.
• TIBCO Object Service Broker Getting Started for more information about the Telnet 3270 access.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |