[Top] [Previous] [Next] [End of Book]

Appendix A . Operational Considerations and Compatibility

Operational Considerations

Operational considerations are permanent limitations on using a feature. The following operational considerations apply to Connect TPS:

Note: In the following discussion, a "local" application program is one that resides within the immediate BEA TUXEDO administrative region. A "remote" application program is one that resides outside the immediate BEA TUXEDO administrative region.

Connect TPS does not support conversational communication.
Connect TPS supports only non-transactional communication.
Local client programs cannot send authentication keys and identifiers to remote services.
Remote client programs cannot send authentication keys and identifiers to local services.
Local client and server programs which use the tpsprio() function set the priority at which service requests are dequeued by Connect TPS. This does not affect any prioritization on the remote system.
Local client programs cannot use the tpbroadcast() function to send unsolicited messages to remote client programs (and the reverse).
Local services cannot use the tpbroadcast() or tpnotify() functions to send messages to remote client programs (and the reverse).
When local client and server programs use the tpgprio() function to determine the priority of a remote service, the priority of a local Connect TPS Requester (TPSR) is returned.
For background information about these operational considerations, see "Limitations on the Use of Certain ATMI Functions" in Chapter 2, "Understanding How BEA Connect TPS Works".

Compatibility

There are no known compatibility issues for this release level of Connect TPS.

[Top] [Previous] [Next] [End of Book]