The Kapow Katalyst installation contains six additional API code examples, these examples are found in
To compile the examples run the build.bat from a command prompt. This will cause six .exe files to be produced, which can be run directly.
The .exe files are relying on the
robosuite-dotnet-api.dll and the
both of which are located in the
examples directory. Both files are identical copies of the ones located in the bin folder
and are copied in here to make it easier to run the examples.
Each example program will print a small usage text when run without any arguments.
The build.bat file assumes that the C# compiler is available in the path.
The API and accompanying log4net is build targeting the .net framework 4.0 client profile. For details on the .net framework 4.0 client profile see http://msdn.microsoft.com/en-us/library/cc656912.aspx
To run the ssl example RunSslRobot.exe the RoboServer has to be configured to use ssl and the certificate has to be imported on the client machine. This guide will show you how to configure ssl using a self-signed certificate on a windows PC running a local RoboServer.
The bat file
MakeCertificates.bat included in the examples directory will create a self-signed certificate for
your .net API client. You can use
MakeCertificates.bat as follows
Start a Visual Studio Command Prompt and go do the examples directory
You will now be prompted to type the password for the certificate in this case we simply type "123"
You will now be prompted to type a hostname that the certificate. For a local RoboServer we type "localhost" It is important that this is the same hostname that you use in your client code when creating the protocol.
Now you will be prompted 3 times for the password again - type "123" in each dialog
Certificates can also be created with Keytool as described in API Client Certificates
On the RoboServer start the Settings application located in Start -> All Programs -> Kapow Katalyst
In the Settings application goto the certificates tab
Click change and select the file
When prompted for a password type "123".
the RoboServer is now fully configured and can be started using the switch
-service ssl:50443 to use the ssl configuration on port 50443
Run the command
On the Console menu, click Add/Remove Snap-in
Under Snap-in, double-click Certificates, and select to manage certificates for the Local computer and click Finish
With the certificates snap-in loaded expand the node Certificates -> Trusted root Certification Authorities and right click the Certificates node and click the menu item All tasks -> Import
This will start the Certificate Import Wizard. When prompted to pick the certificate file
API\robosuite-dotnet-api\example\server.pub.cer and complete the import
After completing these steps, both the server and client are configured to use ssl and running the example RunSslRobot.exe can be used to verify the configuration.