Table of Contents
Advertisement
DEVELOPING COLDFUSION 9 APPLICATIONS
Using External Resources
2
The ColdFusion server sends the message to the Data Management event gateway.
The Data Management event gateway and the ActionScript translator convert ColdFusion values to the appropriate
3
ActionScript 3.0 data types, and then the gateway sends the message to the ColdFusion Data Service Adapter.
The ColdFusion Data Service Adapter sends the message to the LiveCycle Data Services Message Service.
4
5
The Message Service passes the message 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, 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 port is the
default value for Java RMI. You can change the port number by adding
with the appropriate port number, to the Java JVM arguments on both the ColdFusion server and the Flex
1234
server.
Application development and deployment process
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:
Design your application.
1
2
Configure a Data Management event gateway instance.
Write your ColdFusion CFCs, CFM pages, and any other application elements.
3
Test your application using LiveCycle Data Services ES.
4
5
Make the application publicly available.
Configuring a Data Management event gateway
Although you can configure an instance of a Data Management event gateway by creating a configuration file and
specifying that file as the configuration file when you create an instance of the event gateway, you can also provide the
configuration information in the message. You provide configuration information to the Data Management event
gateway in a configuration file to do either of the following:
• Have the Data Management event gateway send messages to LiveCycle Data Services ES on a different computer.
• Use the Data Management event gateway with a specific Flex destination, and ignore any destination specified in
the message.
The Data Management event gateway configuration file is a simple Java properties file that contains the following
properties:
Property
Description
A hard-coded destination. If you specify this value, any destination information in the message is ignored.
destination
host
The host name or IP address of the LiveCycle Data Services ES server. Omit the host name if you are running
LiveCycle Data Services ES as part of ColdFusion.
The following example is a configuration file:
Last updated 8/5/2010
1234, replacing
-Dcoldfusion.rmiport=
1317
Advertisement
Table of Contents
