Skip to main content
Known Participant
February 9, 2010
Question

CF 8.0.1 (64-bit) Multiserver installation upgrade to CF9.0 requires uninstall?

  • February 9, 2010
  • 1 reply
  • 2671 views

I have CF 8.0.1 installed in Multiserver configuration on 64-bit Windows 2003 Enterprise server and its running great.  However, I need to upgrade from 8.0.1 to CF 9 and thus far, each of two attempts has prompted me to uninstalled the previous installation of CF 8.0.1 before CF 9 will install, complaining that JRun is already installed and needs to be uninstalled.  This doesn't seem to me to be a very smooth upgrade path, so it makes me question if I am missing some critical step in the in-place upgrade from 8.0.1 to 9.  Anyone done this already and have advice?

Best,

Scott

    This topic has been closed for replies.

    1 reply

    ilssac
    Inspiring
    February 9, 2010

    Most of the advice I have read actaully recomends the clean insall over the inplace install.

    Using the handy-dandy ColdFusion Archive .car feature to migrate all your application settings from one to the other.

    February 10, 2010

    I haven't tried this in CF9 yet, but the following approach has worked up through CF8 for upgrading MultiServer installs.

    1)  Shutdown all CF services.

    2)  Backup all *.xml files from the "<jrunfolder>\Servers\<x>\cfusion.ear\cfusion.war\WEB-INF\cfusion\lib\*.xml" for each of your server instances and save them to a safe location.  If you have other non default directories for things like CustomTags or 3rd party java filters back them up too.

    3)  Uninstall ColdFusion, reboot.

    4)  Install CF9 MultiServer.

    5)  Create CF9 instances for each of your previous server instances.

    6)  Create a directory named cfXsettings (in  which X is the earlier version of ColdFusion) in the  cf_webapp_root/WEB-INF/cfusion/lib directory.

    7)  Copy the backed up files settings files  to the ColdFusion 8 cfusion/lib/cfXsettings directory.

    8)  Edit the ColdFusion 8  cfusion/lib/adminconfig.xml file by setting the value of the runmigrationwizard and the migratecfX (in which X is the earlier version  of ColdFusion) switch to true.

    9)  Restart the ColdFusion Services.  It helps to configure each CF server instance to run as it's own service so that you can stop each independantly.

    10)  Browse to ColdFusion Administrator to  run the migration wizard.  After you log in with the provided Admin password, it will begin importing your configuration settings.

    Repeat steps 6-10 for each CF server instance.  Leave the default/enterprise coldfusion instance unchanged unless you want all future instances to inherit your default/enterprise changes.

    The *.car method will not get everything.

    Inspiring
    February 10, 2010

    The *.car method will not get everything.


    What's an example of what it misses?

    --

    Adam