ColdFusion includes the Data Management event gateway, which uses the ColdFusion Data Service Adapter to send messages to LiveCycle Data Services ES. This means that ColdFusion applications can notify a Flex application about changes in the data that is managed by the destination.
You can send messages from a ColdFusion application to a Flex application through the Data Management event gateway. This gateway type only lets you send messages from a ColdFusion application to a Flex application.
The following image shows the process in which a message is sent from the ColdFusion application to the Flex application:
If you are running LiveCycle Data Services ES on the ColdFusion server, communication between LiveCycle Data Services ES and ColdFusion does not use RMI.
If you are running LiveCycle Data Services ES remotely, to ensure that the RMI registry provides registry service for both LiveCycle Data Services ES and ColdFusion, start LiveCycle Data Services ES first, and then start ColdFusion. If you stop LiveCycle Data Services ES, you must restart LiveCycle Data Services ES, and then restart the gateway.
If you are running LiveCycle Data Services ES remotely, the RMI registry, which facilitates communication between the ColdFusion Data Service Adapter and the Data Management event gateway uses port 1099. This is the default port for Java RMI. You can change the port number by adding -Dcoldfusion.rmiport=1234, replacing 1234 with the appropriate port number, to the Java JVM arguments on both the ColdFusion server and the Flex server.
The following is a typical process for developing and deploying a ColdFusion application that communicates with a Flex application through the Data Management event gateway: