Appendix: Droplets-related Registry Keys
 


Below is a table listing Droplets Platform-related Registry Keys that are created upon Droplet SDK installation. This table excludes Java-related registry keys, which are outlined in Java Support.

Registry Key Parameters / Default Values Purpose
HKEY_LOCAL_MACHINE\SOFTWARE\ Droplet\DropletServer\Logs

"LogDir"
"c:\Program Files\Droplet\Logs"

"SystemLogDir"
"system"


"AccessLogDir"

"access"

The location within which platform log folders (both system and access) will be written. Can be absolute or relative to Droplets directory root.

Location (within LogDir) within which Droplets Platform system logs are generated. Can be absolute or relative to Logdir.

Location (within LogDir) within which Droplets Platform access logs are generated. Can be absolute or relative to Logdir.

HKEY_LOCAL_MACHINE\SOFTWARE\ Droplet\DropletServer (Default)  

HKEY_LOCAL_MACHINE\SOFTWARE\ Droplet\DropletServer\Apps

(Default)  
HKEY_LOCAL_MACHINE\SOFTWARE\ Droplet\DropletServer\Apps\
<default>

"ForgotPasswordUrl"
"yourhostname\forgot"

 

 


"RegisterUrl"
"yourhostname\register"

 

 


"UserManager"
"DropletUserManagerFixture.dll" (C++)

"Apps\JavaAppHost.dll"
(Java)

"ForgotPasswordUrl" indicates the URL which will be opened in the user's Web browser when they click the "Forgot Password" button on the start-up authentication window.

"RegisterUrl" indicates the URL which will be opened in the user's Web browser when they click the "Forgot Password" button on the start-up authentication window.

"UserManager" When using a C++ User Manager, this identifies the DLL file to use for authentication, and the Fixture file is used when user authentication is not in use by any hosted applications. You should use DropletUserManagerDB.dll instead if your applications require user authentication. When using a Java User Manager, it must be set as indicated to the left.

HKEY_LOCAL_MACHINE\SOFTWARE\ Droplet\DropletServer\Apps\ UserManagerDb

"ConnectionString" "system\manager@oracle_sid"

 


"PWlookup_StoredProcName"
"asp.password_lookup_proc"

 

"PWlookup_ArrayLength"
"128"

 

"PWlookup_ReturnsHexEncodedString"
"false"

ConnectionString: Authentication database connection string indicating the location where the Droplets Server should call the authentication database.

StoredProcName: The name of the stored procedure to call for passwords (e.g. asp.password_lookup_proc). The stored procedure needs to take two array arguments, representing input (username) and output (password) respectively.

ArrayLength: This is the length to use for the two array arguments that represent input (username) and output (password) respectively. It must be a positive number; if not, a default of 128 will be used.

ReturnsHexEncodedString: Boolean parameter that informs the Droplets Server as to whether or not the password returned by your database is a hex encoded string (a string of ASCII letters that equals the hex representation in bytes of the numbers).

HKEY_LOCAL_MACHINE\SOFTWARE\ Droplet\DropletServer\Apps\ UserManagerJava

"Class"

The fully qualified class name of your Java User Manager. Use the forward slash ("/") as the package delimiter, not the period ("/").
HKEY_LOCAL_MACHINE\SOFTWARE\ Droplet\DropletServer\
BinaryFileStream
"Directory"
"Droplet\Sessions"
Directory where individual session information is stored

HKEY_LOCAL_MACHINE\SOFTWARE\ Droplet\DropletServer\ EventQueue

"MaximumThreads" = "10"

 


"ProcessingThreads" = "10"

 



"QueueThreshold" = "150"

These settings relate to how the Droplets Server handles events. Client-side (and asynchronous) events are placed in a queue for processing by threads on the Droplets Server.

MaximumThreads indicates the maximum number of Server threads that can ever be created to handle events in the queue.


ProcessingThreads indicates the number of Server threads that are created on start-up to handle events


QueueThreshold indicates the number of events that must be stored in the queue (without any threads being processed) before the Server will create an additional thread.

HKEY_LOCAL_MACHINE\SOFTWARE\ Droplet\DropletServer\Java "ignore-unrecognized" = "true"
"JVM" = "JDK location"
"jvm-options" (blank by default)
"log-jvm-message" = "true"
"stderr-file" = "dropletsdk1.0.0\java\stderr.txt"
"stdout-file" = "dropletsdk1.0.0\java\stdout.txt"
See Java registry key table for info on these
HKEY_LOCAL_MACHINE\SOFTWARE\ Droplet\DropletServer\JavaApps "ClassPath0"
"dropletsdk1.0.0\java\Api\lib\
dropletapi.jar"
Indicates the location of your Droplets Java API
HKEY_LOCAL_MACHINE\SOFTWARE\ Droplet\DropletServer\Network "Port"
"8194"
The port through which Client and Server communicate
HKEY_LOCAL_MACHINE\SOFTWARE\ Droplet\DropletServer\
SessionManager
"MaxPollSeconds" = "1500"


"MaxTimeToSerialize" = "3"
Number of seconds between Server polls

Maximum time in milliseconds to serialization

 


Return to Droplets SDK documentation home.