The following describes the steps for creating a deployment application in RED.
Maximum number of objects in an application: |


| Fields | Description | |
|---|---|---|
| Output Directory | The directory to which the application files will be written. By default, this is the WhereScape program directory.
| |
| Application Identifier | The application identifier is a four-character code used to identify the application uniquely. This identifier is used in the naming of the files that are created to contain the application data. | |
| Application Version | The version is a character string that provides a version number for reference purposes. This version number is displayed when applications are being loaded and is used in the naming of the files that are created to contain the application data. As such, it must contain characters that are valid in a Windows file name | |
| Application Name | The name by which the application is known. This name is displayed during the selection of an application to load and is recorded in the metadata of the repository into which an application is loaded. It is not used, for documentation purposes. | |
| Description | This description is displayed during the selection of an application to load. It is not used at any other point, apart from documentation purposes. | |
| Previous Application | Click the Browse button next to Previous Application to choose a previously built application to use as a list of objects to include in the new application. After using a previous application as a starting point for this application, additional objects can be added or removed from the application. | |
| Pre-application load SQL | This text box enables you to enter an executed SQL statement before the application is loaded. For example, you may wish to drop the date dimension before loading the application because we have changed the primary key constraint. In such a case, you would enter 'drop table dim_date' in this field to have the table dropped before the application is loaded. | |
| Post application load SQL | This text box enables you to enter an SQL statement that is executed after the application is loaded. For example, you could execute a function to populate a table. |

|

| Options | Description |
|---|---|
| Archived Objects | This option includes all objects that have been versioned and deleted. This is the case in a development repository, where the object was removed after versioning. This is the default option. |
| Current Objects | This option includes all the currently available objects and their associated Projects or Groups. |
| All Objects | This option includes all the Current Objects plus the Archived Objects (deleted/versioned). Objects that were versioned and deleted will appear in All Objects but not under any Projects or Groups. |
| File | Purpose |
|---|---|
| App_data_XXXX_NNNNN.wst | This file contains the scripts and data required to rebuild the objects in the new metadata repository. |
| App_id_XXXX_NNNNN.wst | This control file identifies the application and its version. |
| App_obj_XXXX_NNNNN.wst | This file contains control information and each object in the application. |
| App_con_XXXX_NNNNN.wst | A list of all the connections either in the application or used by objects in the application. |
| App_map_XXXX_NNNNN.wst | A list of all the project and group mappings for the objects in the application. |
Refer to Deploying an Application for details on how to load your new application to a selected RED repository.