RPCEncryptionHookDLL
String (encryption-library-name)
Internal/<name>
Purpose
Use the RPCEncryptionHookDLL parameter to identify the JADE or user-supplied SSL encryption library. The types of encryption that are available are as follows.
-
RPCEncryptionHookDLL=Internal, which uses the Windows-supplied 40-bit encryption.
-
RPCEncryptionHookDLL=SSL_TLS, which enables the SSL security feature. When SSL security is enabled, the parameters whose names start with SSL (described in following subsections) are used. For details, see "
-
RPCEncryptionHookDLL=<name>, which calls a user-supplied library with the name specified in the <name> value. For details, see "
The RPC encryption library must be thread-safe; that is, it must be able to handle multiple threads calling this library simultaneously.
If RPC encryption is enabled (by setting the RPCEncryptionEnabled parameter to true), JADE attempts to load the specified library and the required entry points dynamically during initialization.
When RPC encryption is enabled, the connections to the application server are refused and an exception is raised if the dynamic load of the library or any of the required entry-points fails.
For details about the valid combinations of the RPCEncryptionEnabled parameter and RPCEncryptionHookDLL parameter on both the application server and presentation clients, see the JADE application server RPCEncryptionEnabled parameter under "Application Server Section [JadeAppServer]", earlier in this chapter.
Parameter is read when …
The application server node is next initialized; for example, when you restart the application server.
