Any application running on a Java application server that supports the Servlet 2.2 or 2.3 specifications can use Flash Remoting to provide services to Flash clients.
Macromedia explicitly supports JRun 4.0, IBM WebSphere Application Server 4, BEA WebLogic, and Sun ONE Web Server. The Remoting gateway determines the application server platform by looking for known classes in its classpath, a list of locations in which to look for Java classes and other resources. For Sun ONE Web Server, Flash Remoting does not support Enterprise JavaBean (EJB) services. For IBM WebSphere and BEA WebLogic, Remoting supports the standard service types described later in this chapter.
Flash Remoting supports several additional features on JRun. The user credentials specified using NetConnection.setCredentials( ) are used to define the user and user role in Container-Managed Security, the J2EE standard way of authenticating and authorizing users, and for access to EJBs. Flash Remoting can be used to give Flash clients access to JRun's JMX MBeans. Finally, Flash Remoting writes its log messages using JRun's logging infrastructure.
Flash Remoting also runs correctly on numerous other J2EE application servers, including Caucho Resin, Tomcat, JBoss, ATG Dynamo, Oracle 9i AS, and HP Application Server. However, do not take this list as complete. The next section describes how to set up Flash Remoting for these and other application servers so you can try additional platforms yourself.