Deployment

TSC believes a deployment plan is essential. The migration from a non-production server to a production server is an important part of the deployment process. This plan must document the configuration needs, data sources, mappings (including CFC mappings), FCS settings and directories, and CFMX administration settings. This plan must be able to be tested to see if all aspects of the deployment were processed. The deployment plan must be repeatable and give the facility to roll back to a previous version automatically. This rollback scenario is supported by the backing up of code source files, the database, and the FCS directory.

Physical security as well as data security should also be addressed within the deployment plan. A system may be able to withstand an electronic attack, but if someone were to gain physical access to the system, then it may be of little help. Alternatively, the system could be physically inaccessible from unauthorized users, but a hacker may be able to compromise the system through electronic means.

The production environment's physical location was part of Silicon Coast's premises.

The deployment plan is outlined in Table IV-4.2.

Table IV-4.2. Deployment Plan

Task	Description	Completed	Tested	Authorized	Rollback
Install application	The production server requires Flash Communication Server (FCS) and ColdFusion MX to be installed.
FCS application directory	A directory under the FCS commServer directory called chat needs to be created.
CFMX mappings	The CFMX mapping of the CFC component directory au needs to be created.
CFMX data source	The data source of Type ODBC needs to be created and pointed to the chat.mdb file.
File copying	The CFC, CFML, and .fla files need to be copied to the relevant directories.

It appears that Silicon Coast will accept the system with the modified user interface it has requested. TSC has issued an invoice for the completed project and deployed the system on the production environment.