Loading Encrypted Schema Source Files

When loading a schema extract file containing encrypted source code, the following occurs.

  1. JADE looks in the SchemaEncryptionHookLibrary parameter in the [JadeSecurity] section of the JADE initialization file for the name of your user-defined encryption library. JADE uses a default decryption algorithm if you do not supply your own library.

  2. JADE attempts to load the encryption library by calling LoadLibrary and gets the address of your predefined decryption hook routine by calling GetProcAddress. An error is raised if the library cannot be located.

  3. The compiler passes the encrypted source to your specified decryption routine, which restores the source code to its original form.

  4. The method source code is compiled.

To retain confidentiality, the source code is not saved by the load process. If the load process therefore detects errors when compiling method source, only the error code and message are displayed. The developer of your JADE application must then make the appropriate modification to the source, before providing you with a new schema file.

For details about overriding patch versioning in incoming schemas, see "Specifying Advanced Load Options", earlier in this chapter.