Restrictions

IPM is not available as a secure daemon (with TLS communication). Secure daemons use TLS to protect communication on TCP links between daemon and client. Since the client transports of IPM are within the same process as their daemon, this level of protection is unnecessary.

For platform support, see the TIBCO Rendezvous® Readme file.

IPM does not support a browser administration interface through http or https. A browser interface would allow external viewers to affect performance. In a situation where data latency is critical, such external interference must be prohibited.

Several advisory messages are not available in IPM. Design (or modify) your application programs accordingly.

RVD.* advisories report on the TCP connection between daemon and client. When the daemon is within the client process, client transport connections are not relevant, so these advisories do not occur.

Similarly, CLIENT.FASTPRODUCER and CLIENT.SLOWCONSUMER advisories report on the status of inter-process queues (IPQ) between daemon and client. When the daemon is within the application process, communication does not use IPQs, so these advisories do not occur. Monitoring DATALOSS advisories is an alternative way to check for correct operation of producers and consumers.