Corda Demobench for V1.0

Demobench is a stand-alone desktop application that allows you to easily configure and run local Corda nodes. This is helpful for training, demonstration and exploratory experiments.

Windows Installer (EXE) Max OS X Installer (DMG) Demobench is provided as an Open-source software based on the Apache 2.0 licence. Its source code can be found in Corda GitHub repo. Run Demobench Configuration node Each node must have a unique name that can be identified in the Network map service. Demobench recommends the use of node names (nodes names), the nearest city (nearest cities), and the local port numbers. The first node will be used as the network Map service, and we will also configure it as a notary node. So only notary services are available in the Services list. For subsequent nodes, you can also choose to Corda any Services that are built into it.   Click the Start node button to use your configuration to start the Corda node. Run Node Demobench loads each new node in a terminal emulator (Command Window). View Database, Launch Explorer, and the Launch Web Server button will be unavailable until the node is fully booted. Then Demobench will display a simple analysis of the node, such as the capital surplus. Now you can't do this if you want to restart a node that is already closed (the user enters "bye" in the node's command window). But the data and logs of that node still exist under the path. exit Demobench When you close the Demobench, it automatically closes all nodes and all of the explorers they loaded before exiting. Profiles You can store the configuration and Cordapps of the node currently running in Demobench into a profile file, which is a zip file containing the structure:

notary/
    node.conf
    plugins/
banka/
    node.conf
    plugins/bankb/node.conf plugins/
        Example-cordapp.jar
...

When Demobench reloads the profile, it stops all currently running nodes and then loads the new nodes. All nodes will be created with a completely new database. Note: Each profile inside the node.conf file is the Json/hocon format, so it can be extracted and edited as needed.
Demobench writes log files in the path below: Macosx/linux: $HOME/demobench/demobench.log
Windows:%userprofile%\demobench\demobench.log
Building installation filesGradle defines the task (tasks) to use Javapackager to create demobench installation files. There are three scripts under the Tools/demobench path to execute the following command: Package-demobench-exe.bat (Windows) package-demobench-dmg.sh (MacOS) Package-demobench-rpm.sh (fedora/linux) Each script runs only under the established platform and requires that the platform's installation tools be available as well. Windows:inno Setup 5+ MacOS: The packaging tools should be installed automatically. If Packager finds an available Developer ID application certificate on the keyring, along with a private key, the DMG content is also signed. (By default, the user name of the Demobench Build.gradle expected signature key is "R3cev"). You can create a certificate by generating a certificate signing Requests, and then ask your local Apple team agent to upload the certificate to the Apple Developer portal. (View details)
Attention:
-Ensure that the/usr/bin/codesign program always has access to your certificate's signature key. You may need to reboot your MAC after you have made any changes using the MacOS keychain Access application.
-On MacOS You should use a version higher than JDS 8u152 to build Demobench, because this version resolves a problem that prints a reminder message in the Command window when you start each node.
-You should use the JetBrains JDK to build DMG. Fedora/linux:rpm-build packages. You also need to define the JAVA_HOME environment variable so that it points to the same JDK that is running Gradle. The Installer will be written to the Tools/demobench/build/javapackage/bundles path and can then be installed in your system just as you would install any other application. JetBrains JDKMac users should note that the best way to build demobench is to use the JetBrains JDK to download the executable file in the Bintray center. The JDK contains a number of useful GUI fixes, and the most important thing to know is that when you use the JDK to build demobench, the terminal window will support emoji, so there will be better ANSI progress with color. It also solves some of the problems caused by hidpi rendering in Windows. The JDK does not include Javapackager, which means you still need to copy $JAVA _home/lib/ant-javafx.jar from the Oracle JDK path to the path below your jetbrains jdk. Developer AttentionTo be able to run Demobench developers every time you do not build a new installer, you can use Gradle to install locally:

$ gradlew tools:demobench:installDist
$ cd tools/demobench/build/install/demobench
$ bin/demobench

Unfortunately, Demobench's $CLASSPATH is too long for Windows shell. If so, you can still run demobench like this:

> Java-djava.util.logging.config.class=net.corda.demobench.config.loggingconfig-jar lib/demobench-$ Version.jar

However, Demobench can also be run in the IDE, depending on whether the developer has previously installed all runtime dependencies (runtime dependencies) (for example, the working directory of the current JVM) under the path corresponding to the User.dir system attribute value:

corda/
    corda.jar
    corda-webserver.jar
explorer/
    node-explorer.jar
    plugins/ Bank-of-corda.jar