|  |
Command Line Bot
A tool that enables access to distrbuted UNIX systems and services from a simple messenger.
Date Posted: March 16, 2004
|
|
 |
 |
|
Platform requirements for Command Line Bot
Operating systems: UNIX, Linux®
Hardware:
- 256 MB RAM system
- 5 MB of free hard disk space
- Network connectivity and user account with an existing Sametime server.
Java tools:
- Java Run-time Environment 1.4.1
- Xerces XML Parser (included in many distributions of Java SDK)
- IBM Sametime® Java Toolkit 3.0 (Available for Windows® platform. Once extracted, the platform-independent Java JAR files are all that is needed. They are located in the path X:\ST30JavaToolkit\bin where X is the installation drive in Windows.)
Other: Support for multiple threads
For connecting to the bot:
- a valid user ID on a Sametime Server
- a Sametime Client, such as Lotus Sametime Client
Note: Command Line Bot was developed and tested under Linux RedHat 9.0 using IBM SDK 1.4.1; hence this is the recommended system configuration. However, since it is Java-based with open standards, other architecture and JRE versions (not lower than 1.3) should also work. Due to limitations of Java stream re-direction with native processes on Microsoft Windows, this program currently works on UNIX/Linux only.
Installation instructions for Command Line Bot
- Ensure that the above system requirements are met.
- Extract the zip file to a convenient directory. A new directory IBMCommandLineBot will be created and will contain the program files.
- Edit the CLASSPATH variable to include all the JAR libraries for
- the IBM Sametime Java toolkit, which can be found inside the bin directory of the installation directory of the toolkit
- Xerces XML JAR libraries.
- On UNIX/Linux, ensure that you "export" the CLASSPATH variable for it to take effect.
- Please see the readme file for configuration instructions.
- Once the config file is ready, run the JAR file IBMCommandLineBot.jar with the absolute path of the XML config file as the single argument. It is necessary to execute "export TERM=" prior to running the Bot so that the "TERM" environment variable is reset for the Bot program. Example commands are below:
export TERM=
java -jar "Absolute_Path_Of_IBMCommandLineBot.jar_file" "Absolite_Path_Of_Config_File"
This command will not return and it is best to run it with a & suffix and make it a background process using "bg". Its a good idea to re-direct STDOUT/STDERR to a file (see command below). Any changes made to the config file while the Bot is running would require the Bot to be restarted in order to take effect.
java -jar "Absolute_Path_Of_IBMCommandLineBot.jar_file" "Absolite_Path_Of_Config_File" > ./logfile &
|
|
 |
|
| |
|