Flex Server Setup
Flex requires that cross domain files be used for all connections below is some basic ways of setting up Universal Messaging to server these files.
NHP connection setup
Following these steps will set up a realm server with a demo Flex app connecting via NHP
Create a test channel with a channel name of flex.
See the section Channel Administration in the Enterprise Manager documentation for details of creating a channel.
Set the ACL permissions on your channel so that you can publish and consume from it.
See the section Channel Entitlements in the Enterprise Manager documentation for details of managing channel ACLs.
Set up an HTTP Interface.
See the section Creating Interfaces in the Enterprise Manager documentation for details of adding an interface to a realm.
Set up a file plugin on this interface to serve the flex application.
See the section File Plugin in the Enterprise Manager documentation for details of managing file plugins.
Add a cross domain policy to the root file directory of the interface serving the swf (only required if different from the interface the swf connects to).
Implement a basic Flex client.
NSP connection setup
Following these steps will set up a realm server with a demo flex app connecting via NSP
Create a test channel with a channel name of flex.
See the section Channel Administration in the Enterprise Manager documentation for details of creating a channel.
Set the ACL permissions on your channel so that you can publish and consume from it.
See the section Channel Entitlements in the Enterprise Manager documentation for details of managing channel ACLs.
Set up a socket interface on port 843 and enable the socket policy server on it.
See the section Creating Interfaces in the Enterprise Manager documentation for details of adding an interface to a realm.
Add a socket cross domain policy to the data directories htdocs.
Implement a basic Flex client.