Ensuring Dynamic Components Are Working

Ensuring that your dynamic components are working is critical at this stage. As we pointed out earlier in the book, ColdFusion MX Components (CFC files) contain reusable code that is rather easy to maintain. Still, these components are one of the first things to test upon deployment.

This check can easily be done with Flash MX 2004 if you have installed the Flash Remoting components. To verify that the CFC is running:

  1. Open Flash MX 2004 and select Window, Services Browser to open the Service Browser panel.

  2. Click the arrow on the left of the panel to open the Service Browser Options menu.

  3. Select Add Gateway to open the Add Gateway dialog box.

  4. In the text input area of the dialog box, enter the domain name or IP address for your server, along with "/flashservices/gateway." For example, you would enter: http://www.yourdomain.com/flashservices/gateway. Click the Add Gateway button.

  5. Open the Services Options menu and select Add Service to open the Add Service dialog box.

  6. In the text input area, type the name of your CFC file. In this case, it would be the facilities file from the Oakbridge site. Click the Add Service button.

If the connection is successful, you will see a list of the methods within your CFC (such as addBooking, removeBooking, listFacilities, and so on).

Checking Database Connectivity

This is another area that should have a high degree of importance attached to it. Most providers will either provide you with an online database management utility or a domain or IP address of the database. If you have the IP address of the database management utility, you can most likely add it as a server in your database management program.

Some database management programs enable you to export the schema of your MySQL database to a file that can be imported into the new database. Check your database management utility for this, and if you do not have this feature, you will have to re-enter the table information.

Finally, make sure the username and password for your database connections?locally and remotely?match the remote server. This is why many developers make it a habit to mirror the username and password on the testing server. Again, try to keep everything as similar as possible between the testing and remote servers.