Encrypting Schema Source Files
The schema extract and load facilities provide hooks that enable you to encrypt the Jade method source code in your schema extract files so that you can release schema extract files without making their source code easily visible.
These encryption hooks enable you to incorporate data encryption algorithms of your choice, to make it difficult for anyone to view your method source code. For example, you may want to encrypt your source code before releasing a schema containing Jade applications for a third‑party.
Jade provides a default encryption algorithm that is used if you do not specify an encryption library and you check the Encrypt Sources check box in the Extract dialog Schema Options sheet. You can specify an encryption library of your choice, by using the
As schema and forms 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 and the failure of the schema load process, particularly when schemas are encrypted.
For details about the encryption hook library parameter, see "
