The following table describes when to do the configuration tasks that are documented in this chapter:
| Configuration task | When to do it |
|---|---|
|
You must stop and restart ColdFusion MX 7 after you enable or disable security in the ColdFusion MX Administrator or change any of the Java and JVM settings, in order for your changes to take effect. You can do this at any time after you install ColdFusion MX 7. |
|
|
When moving to a production server or when the built-in web server no longer meets your needs. |
|
|
You must do this only if you must make CORBA invocations from ColdFusion MX 7. You can do this after you install ColdFusion MX 7 and before you make a CORBA call from ColdFusion MX 7. |
|
|
For security reasons, disable RDS when you move an application to the production environment. |
|
|
When running ColdFusion MX 7 Enterprise Edition in a hosted environment, you might want to disable JSP processing. |
|
|
You must do this only if you discover that the account under which ColdFusion MX 7 is running has inappropriate access rights; for example, to interact with remote data sources, other application pages, or COM objects. You can do this after you install ColdFusion MX 7 and before you deploy your application. |
|
|
You must do this only if you use a Type 4 database driver that is not included in ColdFusion MX 7. You can do this after you install ColdFusion MX 7 and before you set up the data source in the ColdFusion MX Administrator. |
For information about additional configuration tasks, see Configuring and Administering ColdFusion MX.