Command Line Bot

A tool that enables access to distrbuted UNIX systems and services from a simple messenger.

Date Posted: March 16, 2004

Overview Requirements Download FAQs Forum Reviews 1. The Java program is not able to run the Bot and complains about some classes not being found. Please check your CLASSPATH variable. It should include The IBM Sametime Java toolkit, which can be found inside the bin directory of the installation directory Xerces XML JAR libraries. On UNIX/Linux, ensure that you have exported the CLASSPATH variable using "export CLASSPATH". Back to top 2. The Bot complains of a problem with the config file syntax. Ensure that you have conformed to the rules of the XML config file as mentioned in the readme file. All tag names and attributes are case-sensitive. Also ensure that the DTD path in the Config file is correct. Back to top 3. The Bot is unable to connect to the Sametime Server and logs out. Follow the trouble-shooting steps given by the bot when it is unable to log in successfully: Check whether another instance of BOT is running, or BOT user ID used by someone else. Check messaging Server name. Check log-in User ID password. Check network connectivity on your system. Check Sametime service, or contact Sametime administration. Back to top 4. User ABC is unable to use the bot and gets an error saying "unauthorized." Any of the below is possible: User is not included in the config file. (It is possible that you have included the user but the UserName field does not exactly match the Log-in ID on the server. Refer to the installation guide for more details on how to specify the UserName.) User is included in the config file, but the Service section under it is missing. More than one service section is present for this user. (This feature is not supported yet.) Back to top 5. Bot automatically logs in to Telnet to a remote machine, but I see several extra symbols/characters in the output. Please execute "export TERM=" before running the Bot program in the same shell. Back to top 6. Why do programs such as Vi or other "screen" programs not work in the command line? As mentioned in above question, the Chat window cannot emulate a terminal. As a result, the bot also ignores the screen control characters used by "screen" or cursor programs such as Vi. However, all non-screen programs are executed perfectly. Back to top 7. Authentication has failed but I get a success message. Future releases would have authentication failure detection. Basically, ID/passwords need to be tested before they are even put into the config file. Back to top