Applet Development Environment

The applet development environment is intended to provide developers of applets with an environment which mimics the dCDR applications such as the android, windows, linux, and gateway applications. The development environment provides the dCDR services and mimics:

• Offline synchronization with the central iCDR server

• Clinical Decision Support systems

• Business Rules execution

• Report and dataset rendering

Rather than relying on packaged and digitally signed applet files, the applet development environment will load source code directly from your hard drive and will simulate how the dCDR will operate on your files once packaged.

Never us the SDK environment to host a production instance of the SanteDB dCDR infrastructure. Use one of the production/release environments for your needs.

Console Options

Tool: sdb-ade.exe

The command line options for this tool are:

Option	Description	Example
core	Automatically reference the org.santedb.core solution.	--core
solution	References a solution file (see: Solutions). The applet development environment will scan subdirectories of the applet for source code related to each applet package contained in the solution. It should reference the solution file.	--solution=C:\temp\my.sln
applet	Identifies applet package(s) which are being debugged. The applet parameter loads only the specified applet and may be used to side-load individual source code into the debugging environment. It should reference a directory with a manifest.xml which is being debugged.	--applet=C:\temp\app\
ref	References a pre-packaged applet either (1) installed in the SDK installation directory, or (2) found on the central SanteDB package repository.	--ref=org.santedb.core
reset	Clears the configuration for the current dCDR development environment. This option allows you to "reset" your development environment to match a fresh install of the dCDR.	--reset
name	Creates a segregated, named instance of the development environment. This allows you to maintain several configurations without resetting.	--name=MPI
assembly	If you're writing a dCDR .NET plugin and wish to have the SDK load your .NET plugin into the host context, you can specify the assembly to load here.	--assembly=MyPlugin.dll

Named Instances

When you launch the applet debugging environment with no parameters, the configuration files are stored in the %appdata%\sdbade\default directory and offline synchronization data is stored in %localappdata%\sdbade\default, this is the DEFAULT instance of your debugging environment.

However, there are times when developers are working on several environments, and several servers at once. For example, it is quite possible that a developer would want to have an environment for development, an environment for staging server access and validation.

In this case, the developer may launch their dCDR applet for development using:

> sdb-ade --ref=org.santedb.admin.sln --applet=C:\source\myapp --name=dev

When the developer needs to validate a bug/issue on a staging instance, he would simply switch configurations via:

> sdb-ade --ref=org.santedb.admin.sln --applet=C:\source\myapp --name=stage

When the developer does this, the existing configuration is applied as though he is using two different Android tablets, or gateway instances. Named instances store their data in %localappdata%\sdbade\{name} and configuration in %appdata%\sdbade\{name}.

The disconnected gateway and the www host both support named instances as well.