Skip to main content
J
john_glynn
Inspiring
January 4, 2011
Answered

Flash Builder 4 and CF9 - configuration

  • January 4, 2011
  • 1 reply
  • 1452 views

I am new to Flash Builder but not to CF.  I am able to test everything just fine locally using tutorials such as this: http://www.eonflex.com/?p=276 & http://www.youtube.com/watch?v=mUy740fjILI.  But how do I configure FB to work with real data on my server?  I do not see a place to plug Flash Builder into my server so I can reference CFCs there as well as data in SQL.

Thanks for taking the time to read this! No doubt I am missing something obvious...

John 

This topic has been closed for replies.
Correct answer sir_teddy-HuPLRX

I don't think you really want to be developing on production data, because crazy things do happen and you might lose or destroy your data by accident. Personally i like to have 3 places. 1st being my machine where i develop and test, 2nd a place where my test group can go on and test out new features etc... etc... 3rd the actual production server where the site/app gets published to when all of the testing is done. as far as cfcs and data go you only really need to worry about the logical path and the datasources on the CF servers.

for example:

server 1(dev):

physical path: c:\intepub\wwwroot\mycfcs\

logical path in cf admin: /flexServices

datasource name: exampledatasource

database server: SERVER1

database: MyTestData

server 2(prod):

physical path: c:\some\different\path\

logical path in cf admin: /flexServices (same as before)

datasource name: exampledatasource (same name )

database server: SERVER1

database: MySuperProductionDatabase ( have to keep the same structure )

So now you can access all of your data by just using the flexServices mapping. When you hit the Run button in FB it will go to your localhost and when you publish it; it will go to the production data. This way you dont have to risk losing or damaging anything.

1 reply

S
sir_teddy-HuPLRX
Inspiring
January 4, 2011

Publish the Flash Builder project. If you have access to the production server through a network drive or something like that you can publish it directly or if you use ftp or something different then you just upload it. If your coldfusion mappings and the paths to the cfcs are the same you should be good to go.

J
john_glynnAuthor
Inspiring
January 4, 2011

Hey Sir_teddy,

Thanks for the reply!  That is largely the issue.  The mappings on the production server are different.  I suppose I could rename my local drives and directories to match, but it would be great to point directly to these remote CFCs locally.  That is how it is done in the flash authoring tool, which is where I am coming from.  In flash you were able to open a gateyway to any server you had access to.  Is this not supported in FB4?

Thanks again!

John

S
sir_teddy-HuPLRXCorrect answer
Inspiring
January 5, 2011

I don't think you really want to be developing on production data, because crazy things do happen and you might lose or destroy your data by accident. Personally i like to have 3 places. 1st being my machine where i develop and test, 2nd a place where my test group can go on and test out new features etc... etc... 3rd the actual production server where the site/app gets published to when all of the testing is done. as far as cfcs and data go you only really need to worry about the logical path and the datasources on the CF servers.

for example:

server 1(dev):

physical path: c:\intepub\wwwroot\mycfcs\

logical path in cf admin: /flexServices

datasource name: exampledatasource

database server: SERVER1

database: MyTestData

server 2(prod):

physical path: c:\some\different\path\

logical path in cf admin: /flexServices (same as before)

datasource name: exampledatasource (same name )

database server: SERVER1

database: MySuperProductionDatabase ( have to keep the same structure )

So now you can access all of your data by just using the flexServices mapping. When you hit the Run button in FB it will go to your localhost and when you publish it; it will go to the production data. This way you dont have to risk losing or damaging anything.

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices