Thursday, July 24, 2008

Kapow Deployment Schema

This article will explain what is Kapow Robosuite like, when it is deployed and working.

First of all the launch of robots is done in 1 of the following applications within Kapow Robosuite installation.

1. Kapow Roboserver
It is a process on linux or windows server, which working on the port, you mentioned while installation. Generally it is 50000 by default for Data Collection Edition.
2. Kapow RoboRunner
Kapow Roborunner is not represented as a process. It is launched when you want to launch robots from command line or from crontab. It is ddifferent from roboserver, because we cannot pass parameters to robots when using it. From the other side - the robots can be launched using crontab or windows scheduler, that is easing the process.

After we decide which of them to use - we create robots to make data migration for example.
Robots are made in Robomaker and are generally stored in project/library/ path within installation of robosuite. Robots need models to store some temporary calculations, data and so forth. Models are stored where the robots are, but they are created by ModelMaker application.

Launching Robots:
1. RoboClient - the most easy way. Just set up the ip address of the roboserver, path to robot and click launch.
2. RoboManager - also easy to use, but it is more powerful than roboclient, as it manages robot groups, outputs, errors, etc...
3. API - C# or java APIs for launching. You can make 3-chained calls for php or other languages.
4. Command line - in crontab, or just in console. It is only for Roborunner.


No comments: