Overview

The SDK (C/C++) supplies a dataIn/dataOut commarea mechanism for unformatted binary data exchange between an application and a TIBCO Object Service Broker rule. A rule called via the SDK (C/C++) can use all the TIBCO Object Service Broker facilities except the text-presentation DISPLAY statement. To facilitate commarea binary data exchange between an application and a rule, developers can use TIBCO Object Service Broker MAP tables to process data in the dataIn commarea and to return data back to the application through the dataOut commarea.

Remote Communication

The SDK (C/C++) is a remote interface that communicates with TIBCO Object Service Broker. TIBCO Object Service Broker on all platforms supports this interface in the same way. User applications can communicate with different TIBCO Object Service Broker installations on different platforms with no change to their code. They use the SDK (C/C++) whenever they want to control a session in another computer or in another work space on the same z/OS computer.

How Can It Be Used?

With the SDK (C/C++), you write an application to manage a TIBCO Object Service Broker session using a set of subroutines to an external program. Using the SDK (C/C++) functions, you can code in whichever programming language you prefer. To make the services of TIBCO Object Service Broker available to your program, you write specific routines that make use of the SDK (C/C++) and that exert complete control over TIBCO Object Service Broker sessions. Refer to Sample Application Using the SDK (C/C++).

Compiling and Linking

The SDK (C/C++) presents its interface to the client in an executable module (oscli.dll on Windows, and liboscli.so on Solaris) that exposes its entry points. To use the interface, an application links to the executable according to application platform and environment rules. On Windows, the oscli.lib import library is provided to link to oscli.dll. The format of the entry points is supplied in the oscli.h C header file.

Thread Safety

The SDK (C/C++) client is not thread safe at a session level. In other words, when two threads try to issue an SDK (C/C++) cliProc call on the same session area, the behavior of the second client is unpredictable.

Constants

To facilitate application development, oscli.h contains the following preprocessor definitions:


CLI_MAXRULEEXPRLEN	The maximum length of a rules call string. For more information, refer to CALLRULE – Call a Rule. The value is 514.
CLI_MAXENDMSGLEN	The maximum length of a rules end message. For more information, refer to GETENDMSG – Retrieve a Rules End Message and to the ENDMSG shareable tool. The value is 148.