Why upgrading the license after a ColdFusion Migration matters

Migrating ColdFusion to a new host, data center, or version often starts in trial or developer mode. Converting that instance to your paid Standard or Enterprise license is not just a Compliance checkbox: it unlocks production Features, removes trial limitations (for example, PDF watermarks), ensures correct CPU/core usage under your edition, and stabilizes updates and support eligibility. A clear, auditable License upgrade process reduces downtime and prevents surprises when the old server is decommissioned.

---

Prerequisites / Before You Start

• Confirm product versions and editions

  • Identify the exact ColdFusion version/build on both source and target (e.g., ColdFusion 2018, 2021, 2023).
  • Verify your serial number matches the version you’re running. Serial numbers are version-specific; a 2021 key does not activate 2023 unless you obtained an official upgrade key from Adobe.
  • Determine edition (Standard vs Enterprise) and how it maps to your Deployment (Features, cores, clustering).

• Backups, exports, and documentation

  • Export ColdFusion Administrator settings if available and appropriate.
  • Back up Configuration files from the source:
    • cfusion/lib/neo-*.xml (data sources, mail, mappings, etc.)
    • cfusion/bin/jvm.config (JVM flags)
    • cfusion/runtime/bin/wsconfig (web server connector configs)
    • cfusion/wwwroot/ and app code (if applicable)
  • Back up the target server’s initial (pre-license) snapshot in case you need to roll back.

• Dependencies and environment readiness

  • Java runtime supported by your ColdFusion version (vendor, version).
  • Web server Integration (IIS/Apache, connector version).
  • Required ColdFusion packages/modules via cfpm (PDF, ORM, S3, Image, etc.).

• Networking and activation reachability

  • Outbound HTTPS (port 443) to Adobe Licensing services for online activation.
  • If activation must be offline, have a secure machine/browser that can access Adobe’s offline activation portal and a process to move files between environments.

• Access and credentials

  • ColdFusion Administrator password on both source and target.
  • OS/service management privileges to restart ColdFusion and web servers.
  • Licensing portal access, your serial numbers, and the right to move them.

• Compliance checks and planning

  • Count the CPU cores available to the VM/host and ensure they align with your edition limits.
  • Plan a Maintenance window or low-traffic period for deactivation/activation and service restarts.
  • Document a rollback path.

• Change management

  • Ticket, approval, and timeboxed window.
  • Communication to stakeholders about potential impact.

---

Step-by-step guide to upgrading your ColdFusion license after Migration

1) Inventory your current licensing and Deployment

• Gather serial number(s), support contract details, and edition rights (Standard/Enterprise).
• Validate the target server build: ColdFusion Administrator > System Information shows version and build.
• If you upgraded versions during migration (e.g., 2018 to 2023), confirm you have an upgrade or Maintenance license for the new version. If not, contact your reseller or Adobe to obtain the correct key.

Tip: Keep a short “licensing worksheet” that notes instance names, hosts, number of cores, and the serial to be applied. This stops confusion during audits.

---

2) Prepare the target ColdFusion environment

• Apply the latest updates and Security hotfixes first:

  • ColdFusion Administrator > Updates > Check for Updates > Install.
  • Restart services if prompted.

• Ensure required packages (features) are installed using the ColdFusion Package Manager (cfpm):

  Linux

  /opt/ColdFusion/cfusion/bin/cfpm.sh list
  /opt/ColdFusion/cfusion/bin/cfpm.sh install pdfg,lucene,cfhtmltopdf

  Windows (PowerShell)

  “C:\ColdFusion\cfusion\bin\cfpm.bat” list
  “C:\ColdFusion\cfusion\bin\cfpm.bat” install s3,aws

• If you run Standard edition on a host with many cores and need to enforce core limits at the JVM layer for compliance, add an explicit processor count to jvm.config (choose a number your license permits):

  File: cfusion/bin/jvm.config

  -XX:ActiveProcessorCount=2

  After editing, restart ColdFusion.

• Verify web server connectors are properly registered (wsconfig) and that requests route to the new server.

---

3) Deactivate the license on the source server (if reusing the same serial)

Most ColdFusion licenses are not concurrent-use across multiple servers unless your contract explicitly allows it. If you are moving a license, deactivate it on the old server first.

• Online deactivation (preferred)

  • ColdFusion Administrator > Server settings > Licensing & Activation.
  • Click Deactivate or Remove Serial Number and follow prompts.
  • Ensure the server has Internet access to reach Adobe licensing endpoints.

• Offline deactivation (if no Internet access)

  • In the same Licensing & Activation page, choose Offline Deactivation.
  • Generate the deactivation request file; move it to a machine with Internet.
  • Upload it to the Adobe offline portal as instructed; obtain and apply the response file to complete deactivation.

Document completion with a timestamp and keep it for Audit purposes.

---

4) Apply the license on the target server

• Online activation via the Administrator UI

  1. Log in to ColdFusion Administrator.
  2. Navigate to Server settings > Licensing & Activation.
  3. Choose the appropriate edition (Standard/Enterprise) if prompted.
  4. Enter your serial number exactly as provided.
  5. Complete activation. If a restart is suggested, plan it promptly.

• Offline activation (no outbound Internet)

  1. On the Licensing & Activation page, choose Offline Activation.
  2. Generate the activation request file and move it to an Internet-connected machine.
  3. Use Adobe’s offline activation site to upload the request and obtain a response.
  4. Import the response file back on the ColdFusion server to finalize activation.
  5. Restart services if required.

• Notes on Automation and headless scenarios

  • For brand-new installs, you can often supply the serial during installation or via deployment tooling depending on your method (e.g., silent installers or server Automation). The exact properties and flags differ by version and installer—review Adobe’s installer documentation for your release.
  • For containers or ephemeral Infrastructure, check your image’s official documentation for supported environment variables or startup hooks to inject the license in a compliant way.
  • Avoid manually editing licensing XML files; it is unsupported and risky.

---

5) Restart ColdFusion and connected services

A Service restart often finalizes the licensing change and clears trial-related behaviors.

• Linux:

  sudo systemctl restart coldfusion
  sudo systemctl restart httpd # Apache, if applicable

• Windows (PowerShell):

  Restart-Service -Name ColdFusion* -Force
  Restart-Service -Name W3SVC -Force # IIS

If you run multi-instance (Enterprise) on the same server, restart each instance that needs the updated license state.

---

6) Validate license status and features

• Verify edition and status:
  • ColdFusion Administrator > System Information and Licensing & Activation pages should show Standard or Enterprise and the activation state as active (not Trial/Developer).
• Test features that differ by edition:
  • Clustering and multiple instances (Enterprise).
  • Enterprise features such as Distributed caching connectors or API Manager integrations (if applicable).
  • PDF generation without Watermarking.
• Confirm connectors and Scheduled tasks behave normally and logs are clean.

---

7) Clean up and finalize the migration

• Remove access to the old server or fully decommission it to prevent accidental use.
• Update inventory and CMDB with the new server’s license and edition info.
• Store your activation proof and deactivation confirmation, if available.
• Share the final state with stakeholders (ops, Security, compliance).

---

Risks, Common Issues, and How to Avoid Them

• Wrong serial for the version

  • Symptom: Activation rejected or edition mismatch.
  • Avoidance: Confirm the serial corresponds to the exact ColdFusion version. If you upgraded versions, you need an upgrade serial from Adobe.

• Internet/proxy issues during activation

  • Symptom: Online activation fails due to firewall or proxy restrictions.
  • Avoidance: Whitelist licensing endpoints, configure proxy in the OS/CF if required, or use offline activation.

• License concurrency violations

  • Symptom: Using the same serial on two production servers.
  • Avoidance: Deactivate on the source before activating on the target. Keep Audit logs of deactivation and activation.

• Standard edition running on too many cores

  • Symptom: Non-compliant deployment; unpredictable Performance.
  • Avoidance: Right-size the VM or explicitly cap CPU recognition via JVM flag (-XX:ActiveProcessorCount) and confirm licensing terms.

• Skipping post-activation restarts

  • Symptom: Trial watermarks or restrictions persist.
  • Avoidance: Restart ColdFusion and the web tier after applying the license.

• Manual file edits to licensing Configuration

  • Symptom: Corrupted config, failed startups.
  • Avoidance: Use the Administrator UI or supported activation workflows only.

• Multi-instance confusion (Enterprise)

  • Symptom: Some instances appear unlicensed.
  • Avoidance: Ensure all instances on the box reflect the licensed state; restart each instance and verify per-instance Administrator pages if needed.

---

Post-migration validation steps

• Licensing

  • Licensing & Activation shows active status.
  • Edition is correct (Standard or Enterprise).
  • No trial banners or watermarks in PDFs or documents generated after licensing.

• Performance and compliance

  • CPU/core usage matches your license rights.
  • JVM flags, Memory settings, and thread pools match your performance plan.

• Functional smoke tests

  • Data sources connect successfully.
  • Scheduled tasks run as expected.
  • ColdFusion packages (e.g., PDF, Image, S3) operate without errors.
  • Endpoints behind the web server connector respond correctly.

• Logs and monitoring

  • Review cfusion/logs/application.log, coldfusion-out.log, and web Server logs for errors.
  • Monitoring dashboards show normal response times and resource usage.

• Security and hardening

  • ColdFusion Lockdown Tool or equivalent hardening practices are applied.
  • Administrator access is locked down and audited.

• Documentation

  • Change records updated.
  • License serial, activation date, and server mapping recorded.

---

Reference paths and useful locations

• ColdFusion installation root:

  • Windows: C:\ColdFusion\
  • Linux: /opt/ColdFusion/

• Key directories:

  • cfusion/logs/ — application and Server logs.
  • cfusion/bin/jvm.config — JVM options.
  • cfusion/runtime/bin/wsconfig/ — web server connector configuration.
  • cfusion/lib/neo-*.xml — ColdFusion Administrator settings (do not hand-edit for licensing).

• Admin pages:

  • ColdFusion Administrator > Server Settings > Licensing & Activation
  • ColdFusion Administrator > System Information

---

Example commands and snippets

• List and install ColdFusion packages:

  Linux

  /opt/ColdFusion/cfusion/bin/cfpm.sh list
  /opt/ColdFusion/cfusion/bin/cfpm.sh install pdfg,orm

  Windows

  “C:\ColdFusion\cfusion\bin\cfpm.bat” list
  “C:\ColdFusion\cfusion\bin\cfpm.bat” install image

• Restart services (examples):

  Linux

  sudo systemctl restart coldfusion
  sudo systemctl restart httpd # or nginx

  Windows

  net stop “ColdFusion 2023 Application Server” && net start “ColdFusion 2023 Application Server”
  iisreset

• Example JVM flag to cap cores (compliance helper for Standard):

  cfusion/bin/jvm.config

  -XX:ActiveProcessorCount=2

• Quick check after activation:

  • Browse to ColdFusion Administrator > System Information and confirm:
    • Edition: Standard or Enterprise
    • Serial number present (masked) and activation status OK
    • Build and update level match your target state

---

Practical tips for special deployments

• Clusters and multi-instance setups (Enterprise)

  • Ensure the enterprise features you rely on are visible and functioning post-activation (e.g., cluster pages in the Administrator).
  • Restart and verify each instance.

• Virtualization and cloud

  • Match VM sizing (vCPU) to your license rights, or cap processors as needed.
  • Keep automation scripts parameterized for serials and edition settings, but never store keys in plaintext repo code.

• Containers

  • Use vendor-supported mechanisms to provide license and accept EULA at runtime or build-time.
  • Persist only what is necessary; do not bake secrets into images.
  • Plan for activation behavior when Scaling replicas—follow Adobe’s licensing guidance.

---

Troubleshooting Checklist

• Activation fails online:

  • Verify outbound HTTPS and proxy settings.
  • Try offline activation workflow.
  • Double-check serial formatting and version.

• Still seeing trial behavior:

  • Restart ColdFusion and web server.
  • Clear caches and retest generating new artifacts (old PDFs keep watermarks).
  • Confirm edition and activation status in the Administrator.

• License applied to wrong instance:

  • Validate the exact instance Admin URL and check its licensing page.
  • Ensure you did not mix up ports or service names on multi-instance deployments.

• Ambiguous core usage:

  • Confirm vCPU count and JVM ActiveProcessorCount setting.
  • Cross-check with OS-level tools (top, Task manager) and ColdFusion Server monitor if available.

---

FAQ

Can I reuse my old ColdFusion serial number on the new server?

Yes, but you must not run the same serial concurrently unless your license explicitly allows it. Deactivate the license on the old server first, then activate it on the new server. Keep deactivation and activation confirmations for audit.

What if the new server has no Internet access for activation?

Use the offline activation flow from the ColdFusion Administrator. You will generate a request file on the server, upload it from a machine with Internet access to Adobe’s portal, then import the response file back on the server. The same approach applies to deactivation if needed.

Do I need a new serial number if I migrate to a newer major version?

Usually yes. Serial numbers are tied to the ColdFusion version. If you have current maintenance or an upgrade entitlement, obtain the new serial number from Adobe or your reseller. Confirm Version compatibility before attempting activation.

How can I ensure Standard edition remains compliant on a high-core VM?

Either size the VM to the licensed core count or cap the JVM’s perceived processors by adding -XX:ActiveProcessorCount= to cfusion/bin/jvm.config, then restart. Always validate this approach with your licensing terms and keep documentation for audits.

Does Enterprise licensing automatically cover multiple instances on the same server?

Enterprise permits multiple ColdFusion instances on a single server, but your overall licensing must still align with Adobe’s terms (including cores). After activation, restart and verify each instance’s Administrator shows the proper edition and active status.