Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 19 Using TIBCO Object Service Broker SDK (C/C++) : Overview of the TIBCO Object Service Broker SDK (C/C++)

Overview of the TIBCO Object Service Broker SDK (C/C++)
What Is the TIBCO Object Service Broker SDK (C/C++)?
The TIBCO Object Service Broker SDK (C/C++) is an application programming interface (API) used by an application to
The SDK (C/C++) is installed with TIBCO Object Service Broker.
How Does It Work?
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 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 z/OS, in another work space on the same computer.
How Can It Be Used?
With the SDK (C/C++), you can 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 the programming language of your choice. 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 Running
1.
For our example, we are using the following parameters:
COMMID=D364046@
NODENAME=A
2.
For our example, so that this Execution Environment connects to the Data Object Broker referenced in step #1., we use the following parameters:
TD=D364046@
MD=N364046@ /* This value is supplied in the call to the sample program */
STANDBYNUM=2
CLIMSGLENMAX=1M
3.
4.
Compile, bind and run your program using the JCL in the RCLIJCL member of the JCL data set provided with the SDK (C/C++) at installation.
Make sure that the IBM cataloged procedures CBCC, CBCB, and CBCG are accessible by this job.
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:
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.
See Also
TIBCO Object Service Broker Managing Data about MAP tables.
TIBCO Object Service Broker Programming in Rules about the rules language, writing rules, and transaction processing.
TIBCO Object Service Broker Parameters about starting sessions and session Execution Environment parameters.
TIBCO Object Service Broker Shareable Tools about the ENDMSG shareable tool.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved