Adobe AIR integration includes all the features from the Flex Integration section (Flex Remoting, Flex Data Management, Messaging), however the client project configuration is slightly different. The reason for the difference in the configuration is that WebORB assumes by default that the Flex clients will use the relative endpoint URL to communicate with the server. In case with AIR, the relative URL is not applicable, since the client is not loaded from the server. For remoting and data management, AIR clients can communicate with WebORB using either the HTTP-based AMF protocol or the RTMP protocol via a dedicated socket. It is also quite common to deploy AIR applications in combination with the standalone WebORB server running on the same computer as the AIR client. The standalone server does not require a web server and can provide AIR application access to the resources of the local operating system or a database, however, it is not required that the standalone server runs on the same computer as the AIR client.
AIR clients can communicate with a Java backend using the Flex Remoting API, however, it is important that the remoting URL used by the client application is absolute. There are several classes on the client-side responsible for client/server communication, but in most cases, the applications use only the RemoteObject class. An instance of RemoteObject may reference a destination which, if specified, comes from a configuration file referenced at the compile time. A destination is linked to a channel, and channel has an associated endpoint URL. The diagram below illustrates the relationship between these concepts:
For information about configuring AIR client to use remoting or WebORB Data Management see the links below: