upgrading CF with FusionReactor already installed

[booster94]

This may be a simple question, but I'm running CF8 Standard on several
servers and I plan to upgrade to CF9 on those same servers. Do I have
to do anything with FusionReactor during that process? I know with a
CF upgrade it actually keep the old version of CF and installs the new
CF version in parellel and you then have to go back and uninstall the
old CF version. I'm never done this process since I added
FusionReactor into the mix and I wasn't sure how that factored into
the upgrade process. I am running FR 3.5.1 so I have CF9 covered if
there are no other issues.

[Darren Pywell]

Hi,

You'll have to install FusionReactor into the ColdFusion 9 those
servers that you upgrade. The easiest way is to run the installer
again, and after the license screen, select the "Install a new
Instance", click Next and then pick the CF9 installation (after you've
performed the CF9 upgrade/install).

If you want FusionReactor to use the same port as you currently use in
(default is 8088), then you will have to change the port (in the
FusionReactor Administrator for the CF9 instance) after you've
uninstalled the CF8 installation, so the that port isn't in use.

Hope that helps,
Darren

[booster94]

Seems easy enough, but I'm glad I asked, as I'm not sure I would have
figure that out on my own.

Thanks for the info.

> > there are no other issues.- Hide quoted text -
>
> - Show quoted text -

[Dan Corrigan]

I finally actually tried this (upgrading to CF9 with FusionReactor already
installed) and for the most part it worked but I can't get the old instances
(the ones monitoring CF8) to delete. I tried this on 3 different servers I
upgraded to CF9 and I got the new instance to install through instance
manager just fine, but on that same screen the "minus" button next to the
instance is grayed out. I tried removing the instance before uninstalling
CF8 and then when that didn't work I hoped it would automatically disappear
once CF8 was uninstalled. Neither happened on any of the 3 servers I
upgraded so I can't few up port 8088. The new instances are on 8089 and I'm
stuck at this point. It seems like this should be easy and I should just be
able to remove the instance in instance manager, but in all cases its grayed
out.

Am I missing something?

Hi,

Hope that helps,
Darren

--

You received this message because you are subscribed to the Google Groups
"FusionReactor" group.
To post to this group, send email to fusion...@googlegroups.com.
To unsubscribe from this group, send email to
fusionreacto...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/fusionreactor?hl=en.

[Bernd Donath [FusionReactor Team]]

Dan,

After you have installed CF9 run the FusionReactor Setup again and
choose 'Install a new Instance'. Choose a free port number overwriting
the default value shown in the dialog (which is typically used by the
FR instance already installed on CF8).
When you now open the Instance Manager page of your new FR instance on
CF9 the instance installed in the CF8 server cannot be deleted.
To change this so that the value can be deleted again stop the CF9
server and open the reactor.conf file of its FusionReactor instance
with an editor. This file is typically located in the directory

C:\FusionReactor\instance\coldfusion.cfmx9.<your-hostname>\conf

Search for the line defining the property 'instancemanager.instances'
and add the name of the FR instance of your CF8 server.

Example:

instancemanager.instances=coldfusion.cfmx9.<your-hostname>

has to be changed to

instancemanager.instances=coldfusion.cfmx9.<your-hostname>|
coldfusion.cfmx8.<your-hostname>

Note: values are separator with a '|' character.

Restart CF9 and open the Instance Manager page one more time. You can
now delete the FR instance.
If you want to change the port of your FR instance open the
FusionReactor Settings page, enter the new value for the 'Web Server
Port' parameter under the 'FusionReactor Internal Web Server' section
and restart the CF9 server again. You might want to update the port
number of your FR shortcut on the Desktop.

Related information is available here:
http://groups.google.com/group/fusionreactor/browse_thread/thread/de0c8fe0d1422de1

Hope this helped,
Bernd

[Dan Corrigan]

Bernd,

Thanks for the info. I'll have to wait for another maintenance period to
actually try it. I figured there was some config file I could change to
make it work, I just wasn't sure which one or what to change.

Why does this happen? It this a glitch or expected behavior? This seems
like it should be an easy thing to do within instance manager without having
to jump though these hoops to make it work.

Dan

----- Original Message -----
From: "Bernd Donath [FusionReactor Team]" <bernd_...@intergral.com>
To: "FusionReactor" <fusion...@googlegroups.com>
Sent: Monday, January 18, 2010 5:32 PM
Subject: Re: FusionReactor Group: Re: upgrading CF with FusionReactor
already installed

--------------------------------------------------------------------------------

[Bernd Donath [FusionReactor Team]]

Dan,

FusionReactor Setup has (currently) no logic built-in that detects if
a CF8 server has been updated to CF9. If you have FR installed on CF8
and then install CF9 you have both servers installed in parallel (with
the settings of the CF8 server migrated to the CF9 server done by the
CF9 Setup). FusionReactor does handle this new server the same way as
any other target server on the machine and allows you to install a new
instance on the CF9 server either by running the Setup again or by
using the InstanceManager page of the FR instance on your CF8 server.
This implies that you cannot delete any already existing instances
from the new FR instance on your CF9 server. In
http://groups.google.com/group/fusionreactor/browse_thread/thread/de0c8fe0d1422de1
you can read about the rules how instances are handled.

Dan, if you think it would be a useful feature to treat the CF8->CF9
case in a special way (e.g. to allow to delete the CF8 instance from
the CF9 instance please do let us know and will see what we can do to
make this possible.

Regards,
Bernd

> >http://groups.google.com/group/fusionreactor/browse_thread/thread/de0...

[charlie arehart]

Just want to share an observation, whether to help someone reading this now
or in the future (since this mailing list is indexed by search engines).

I was trying to wrap a datasource today on 64-bit CF on Windows 7, which was
using windows authentication to connect to the DB (SQL Server in my case,
but this may be an issue with other DBMSs as well.)

Anyway, I got an error and the issue is indeed covered by an existing
FusionReactor technote
(http://www.fusion-reactor.com/support/kb/FRS-217.cfm), but it doesn't (for
now) specifically reference this error message (as it was written a while
ago).

The error I got was:

Connection verification failed for data source: [dsnname]
java.sql.SQLException: NTLM (type-2) Authentication was requested
but the required DDJDBCx64Auth04.dll was not found on the path specified by
the java.library.path system property.
The root cause was that: java.sql.SQLException: NTLM (type-2)
Authentication was requested but the required DDJDBCx64Auth04.dll was not
found on the path specified by the java.library.path system property.

As the FR technote indicates, for now there is no solution, but there are
some workarounds offered.

Hope that may help someone.

/charlie

[booster94]

Okay i finally had my maintenance period and I made the changes Bernd
recommended.

I had mixed results in the sense that it worked, but their seems to be
a one hang up. I successful was able to remove the CF8 instance, and
I went to the setting page and changed the CF9 instance back to
default port 8080.

Now here is the catch...on the "instances" page my CF9 instance is
still showing port 8089, even though FR is functioning as expected on
port 8080 (and does not function on port 8089). I think (but I'm
not sure) that this is the cause of another issue...when I go to
Enterprise Dashboard my CF9 instance is there, but is in red and
showing CONN (connection failure). I suspect that it is still looking
for the instance on port 8089 and of course doesn't find it.

I assume this is another conf file change somewhere. Any idea on what
else would need to change?

-Dan

> >http://groups.google.com/group/fusionreactor/browse_thread/thread/de0...
>
> > Hope this helped,
> > Bernd
>

> ---------------------------------------------------------------------------­-----

>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "FusionReactor" group.
> > To post to this group, send email to fusion...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > fusionreacto...@googlegroups.com.
> > For more options, visit this group at

> >http://groups.google.com/group/fusionreactor?hl=en.- Hide quoted text -

[charlie arehart]

Dan, quick sanity check: are you saying you have tried changing it in the
"manager servers" page of the Enterprise section (on the left of the FR
interface)?

I know you've been around the block a few times since trying to deal with
this issue back in January. My suggestion may seem obvious, but I wanted to
make sure that this one thing had been considered. I realize as well that I
may simply not be recalling some aspect of a previous email you'd written
here, which would explain why that could not be the solution. No offense
intended. Just trying to help.

/charlie

> -----Original Message-----
> From: fusion...@googlegroups.com
> [mailto:fusion...@googlegroups.com] On Behalf Of booster94
> Sent: Monday, February 15, 2010 11:50 AM
> To: FusionReactor
> Subject: Re: FusionReactor Group: Re: upgrading CF with FusionReactor
> already installed
>

[Dan Corrigan]

Charlie,

You were right, I didn't realize you there was another place to change that.
I was tried to make the edit under "instances" but there is no "edit" option
at that point.

So now my problem is just a visual one. Everything works, but under
"instances" its still showing my CF9 instance as being on port 8089 instead
of 8088, even though now everything is definitely up an running on port
8088.

It just a potential point of confusion down the road (and even now) as it
had made me think this was causing this issue you replied to, when in fact
that fix was something else entirely.

Thanks for the seemingly obvious tip.

Dan

[charlie arehart]

Happy to help. Thanks for the update.