The Schema Options sheet of the Extract dialog is displayed when you have specified your extract options and you select the Schema Options sheet, to enable you to specify the parts of the schema that are to be extracted.
An example of the Schema Options sheet is shown in the following image.
When you extract multiple schemas to a file, the schema options apply to all of the schemas that you extract to the file.
To specify your schema options
In the Global Constants group box, select the global constants that are to be extracted. For a full extract (the Extract All option was selected on the Extract Options sheet), all global constants in the schema are extracted by default. For a selective extract, only the global constants that are used in your methods are extracted by default.
Select the Extract All option button if you want all global constants in the schema to be extracted. Select the None option button if you do not want any global constants to be extracted.
In the Translatable Strings/User Formats group box, select the translatable strings and user formats that are to be extracted.
For a full extract (the Extract All option was selected on the Extract Options sheet), all translatable strings and user formats in the schema are extracted by default. For a selective extract, only the translatable strings and user formats that are used in the schema are extracted by default.
Select the Extract All option button if you want all translatable strings and user formats extracted. Select the None option button if you do not want any to be extracted.
In the External Functions group box, select the external functions that are to be extracted.
For a full extract (the Extract All option was selected in the Extract Options sheet), all external functions in the schema are extracted by default. For a selective extract, only the external functions that are used in your methods are extracted by default.
Select the Extract All option button if you want all external functions extracted. Select the None option button if you do not want any to be extracted.
Check the Encrypt Sources check box if you want to encrypt the JADE method source code in your extract file. By default, extracted source code is not encrypted; that is, this check box is unchecked.
Source encryption provides security when you release schema extract files, as the source code is not easily visible (for example, when you deploy an application to a third-party). For details, see "Encrypting Schema Source Files", later in this chapter.
Ensure that you extract the encrypted schema to a location different from that of your source schema. If you subsequently load the encrypted schema (for example, for testing purposes), your method source code is lost if you load it into the same database that contains your original source files, as they are not saved during the decryption process.
As schema and form definition files are treated as binary files, if the File Transfer Protocol (FTP) is used to transfer schema and forms definition files between machines, you must ensure that the transfer is done in binary mode (rather than ASCII) to prevent the removal of carriage return characters, particularly when schemas are encrypted.
Check the Extract Skins check box if you want to extract JADE skins defined for runtime applications. By default, skins are not extracted; that is, this check box is unchecked.
Skins are stored in a global collection that is available to all runtime applications in all systems in your JADE database. When you extract skins, all skins in the JADE database defined for runtime applications are extracted to your form and data definition (.ddb
For more details, see "
If patch control is disabled and you do not want to create a command file, uncheck the Create Command File check box. If patch versioning:
Was never used in the system, this check box is disabled and not checked.
Has been used but is now disabled, this check box is enabled and checked.
Is enabled, this check box is checked but you can uncheck it to stop the creation of command files, if required.
If you do not want a JADE Control File (.jcf) created during all extract processes that you perform, check the Unset Schema Extract option 'Create Command File' check box. This check box, which is unchecked by default, controls whether the Create Command File check box on the Schema Options sheet of the Extract dialog is initially set or unset by turning off the .jcf file creation. The Create Command File check box is checked by default; that is, a .jcf file is created.
The command file, shown in the example in the following image, is created with a suffix of .jcf (JADE command file) in the location of the schema and forms definition files.
This file contains a header section, followed by a separate line for each command to be processed.
As the extracted commands are a guide only, you should check the commands before you make the JADE command file available to load into a deployed application by using the batch Schema Load utility. For details, see "
The command file automatically extracts only deleted classes and properties, renamed classes and properties, and moved classes.
If you set the AbortOnError command in the file to True, processing of the command file is aborted when the first error is encountered in the file during the batch schema load process.
When patch control is disabled, the command file contains header information only and you must enter the commands manually.
If you selected the Use Parameter File option button from the Extract Options group box, click the Parameters sheet. If you selected the Selective Extract option button from the Extract Options group box, click the Selective sheet.
Alternatively, click the OK button to confirm your selections, the Applications sheet to select your applications for extraction, or the Cancel button to abandon your selections.
