Services implementing the testbed API are automatically loaded if the fully qualified classname is checked below and the jar file containing the relevant classes is uploaded below. Optionally, you may upload configuration files (plain text) which will be stored under the configs subdirectory of the working directory of the edge peers. In these files, the following special variables are automatically replaced:
| __IP__ | IP address of the edge peer |
| __EXTERNAL_IP__ | external IP address of the edge peer (or the same as __IP__ if this is already a public address) |
| __JXTA_PORT__ | the port used for JXTA |
| __PUBWEB_PORT__ | the port used for PUB-Web |
| __ABSOLUTE_PATH__ | absolute path name (may contain spaces!) of the working directory (with trailing (back-)slash) |
| __ABSOLUTE_PATH_ESC__ | the same as __ABSOLUTE_PATH__ but with double backslashes on Windows Systems |
| __JAVA__ | path (may contain spaces!) of the java executable |
| __JAVA_ESC__ | the same as __JAVA__ but with double backslashes on Windows Systems |
| __L1_CACHE__ | L1 cache size in kB |
| __L2_CACHE__ | L2 cache size in kB |
Finally, you may upload arbitrary other files, such as, e.g., JNI native libraries. These files will not be modified and are stored in the libs subdirectory.
Beside the configs and the libs subdirectories, the subdirectories .jxta, tmp, and var are the only subdirectories where you can read / modify / delete files.
Note: Once you've completed your service configuration and file uploads, it's necessary to restart your testbed partition.