TIBCO Object Service Broker integrates directly with both TIBCO Enterprise Messaging Service (EMS) and TIBCO BusinessWorks. The same integration mechanisms are used regardless of whether TIBCO Object Service Broker is running on z/OS, Windows or Solaris.
These interfaces provide access to the native TIBCO Object Service Broker data store and processing environment as well as to all the external data sources available to TIBCO Object Service Broker: DB2, CA-Datacom, CA-IDMS, IMS, Adabas, Oracle, ODBC-compliant data, and sequential and VSAM data.
The interface to EMS provides a set of tools, S6BCALL and S6BFUNCTION, that TIBCO Object Service Broker rules applications running on z/OS and Open Systems can use to produce and consume messages. These messages are transported via TIBCO EMS servers which run on many platforms.
The first call to EMS by a rule initializes the environment to run EMS and loads code related to invoking EMS. The types of arguments and the return value are determined by the EMS C routine being invoked.
TIBCO Object Service Broker for z/OS External Environments and
TIBCO Object Service Broker for Open Systems External Environments about using the EMS interface.
The TIBCO BusinessWorks OSB Plug-in is supplied with TIBCO Object Service Broker. The plug-in allows you to retrieve and send TIBCO Object Service Broker data in a predefined manner so that it can take part in BusinessWorks processes.