Highlighted

CF-8 to CF-2016 migration issue (still need old server (cf8) to run the application)

New Here ,
Apr 08, 2019

Copy link to clipboard

Copied

We have migrated our application from Cf-8 to Cf-2016 (enterprise edition). With lot of difficulties, we managed to do the migration. We manually did all the settings and mappings from old version to new. We haven't done much on IIS side assuming it will automatically host the new CF version there and overwrite old CF8 mappings.  Now my test server has both CF8 and CF2016 present. I just stopped the cf8 services.

Now what's happening is - I need to start both the services (CF-8 and CF-2016) to run my application. If I only start CF-2016, then application doesn't run. It's weird.

Can someone help here pls?

Screen shot from IIS:

Views

168

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

CF-8 to CF-2016 migration issue (still need old server (cf8) to run the application)

New Here ,
Apr 08, 2019

Copy link to clipboard

Copied

We have migrated our application from Cf-8 to Cf-2016 (enterprise edition). With lot of difficulties, we managed to do the migration. We manually did all the settings and mappings from old version to new. We haven't done much on IIS side assuming it will automatically host the new CF version there and overwrite old CF8 mappings.  Now my test server has both CF8 and CF2016 present. I just stopped the cf8 services.

Now what's happening is - I need to start both the services (CF-8 and CF-2016) to run my application. If I only start CF-2016, then application doesn't run. It's weird.

Can someone help here pls?

Screen shot from IIS:

Views

169

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Apr 08, 2019 0
LEGEND ,
Apr 08, 2019

Copy link to clipboard

Copied

Honestly, CF8 > CF2016 is a _huge_ jump, and you're looking at tags/attributes/functions that have been deprecated or altered.  I mean, just going from CF8 to CF10 is a pretty big jump, and you're attempting to go way past that.  Not to mention the addition of oWasp ESAPI in CF10, increasing security.  You're probably looking at some re-writes.

But that's hardly the whole enchilada.  It probably does have to do with connectors.  Did you run wsconfig after the CF2016 install?  If you did, then the CF8 shouldn't even work, it should all be on CF2016.

HTH,

^ _ ^

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 08, 2019 0