Data & Services - Flex Integration

Configure Flash Remoting and Flex data services integration (Legacy)

Removed: Adobe lists Flex integration, Flex remoting and BlazeDS as removed since ColdFusion 2021, and the remaining Flash and Flex jars as removed in ColdFusion 2025. This page is retained as a historical reference for teams migrating from older ColdFusion versions. Use REST APIs or WebSockets for new development.

Overview

The Flex Integration section configures Flash Remoting and Adobe Flex data services. This is a legacy feature from when Flash and Flex were prominent technologies. Modern ColdFusion applications typically use REST APIs or WebSockets instead of Flash Remoting.

Note: Adobe ended support for Flash Player in December 2020. Flex/Flash Remoting should not be used for new applications. This documentation is maintained for legacy application support only.

What the Page Configured

Flash Remoting let Flash and Flex clients call ColdFusion components over the Action Message Format (AMF) protocol. Adobe's current Administrator documentation no longer describes the Flex Integration page, so its individual settings and defaults are not listed here.

On older releases (ColdFusion 9 through 11 era), the page had an Enable Flash Remoting checkbox, and the AMF gateway was served at /flex2gateway/ through the BlazeDS MessageBrokerServlet mapping inWEB-INF/web.xml. Lockdown guidance was to clear the checkbox and also block /flex2gateway at the web server. Source: Pete Freitag, Disable Flash Remoting on ColdFusion Servers

Status: Adobe lists Flex integration, Flex remoting, BlazeDS and LCDS integration as removed since ColdFusion 2021, and the remaining Flash and Flex jars as removed in ColdFusion 2025. Adobe also lists the DataManagement and DataServicesMessaging event gateway features as removed in ColdFusion 2025. Source: Adobe deprecated features

Migration Path

If you're still using Flash Remoting or Flex, consider migrating to modern alternatives:

Recommended Alternatives

REST APIs

Purpose
Replace Flash Remoting with RESTful services
Benefits
Standard HTTP, JSON format, wide client support

Use ColdFusion REST services for modern client-server communication with any front-end framework.

WebSockets

Purpose
Real-time bi-directional communication
Use Cases
Chat, notifications, live updates

Replace BlazeDS messaging with native WebSocket support for real-time features.

JSON APIs

Purpose
Lightweight data exchange format
Benefits
Human-readable, universal support

JSON replaces AMF for data serialization with better debugging and broader client support.

Modern Frameworks

Options
React, Vue, Angular, Svelte
Benefits
Active development, large ecosystems

Replace Flex UI with modern JavaScript frameworks for rich, responsive client applications.

Migration Steps

Step-by-Step Migration Process:
  • Audit: Identify all Flash/Flex components in your application
  • Map Endpoints: Map Flash Remoting calls to REST endpoints
  • Data Conversion: Convert AMF data structures to JSON
  • Rebuild UI: Rebuild user interface using modern HTML5/JavaScript frameworks
  • Test Thoroughly: Test all functionality before decommissioning Flash components
  • Incremental Rollout: Consider phased migration with both systems running in parallel

Security Considerations

If you must maintain Flash Remoting for legacy applications:

Critical Security Measures

Security Alert: Flash Player is end-of-life and no longer receives security updates. Any Flash-based applications are inherently insecure and should be migrated as soon as possible.
If You Must Maintain Legacy Flash Applications:
  • Network Security: Restrict access to Flash Remoting endpoints using firewall rules
  • Authentication: Implement authentication and authorization for all remote CFC methods
  • Input Validation: Validate all input from Flash clients (never trust client-side validation)
  • HTTPS Only: Use HTTPS for all Flash Remoting traffic to prevent man-in-the-middle attacks
  • Monitoring: Monitor for unauthorized access attempts and unusual AMF traffic patterns
  • Patching: Keep ColdFusion patched to address any Flash-related vulnerabilities
  • Isolation: Isolate Flash-based functionality from critical systems
  • Migration Plan: Develop and execute a plan to eliminate Flash dependencies

Related Resources

Data & Services - Flex Integration | ColdFusion Administrator | CFGuide