JACK® applications consist of a collection of autonomous agents that take input from the environment and communicate with other agents. This provides system builders with a very powerful form of encapsulation. Each agent is defined in terms of its goals, knowledge and social capability, and is then left to perform its function autonomously within the environment it is embedded in.
This is a very effective way of building applications for dynamic and complex environments – each agent is responsible for pursuing its own goals, reacting to events and communicating with other agents in the system. There is no need to explicitly program the interactions of the whole application, rather, the interactions emerge as a by-product of the individual goals and capabilities of the constituent agents.
JACK is a mature, cross-platform environment for building, running and integrating commercial-grade multi-agent systems. It is built on a sound logical foundation: BDI (Beliefs/Desires/Intentions). BDI is an intuitive and powerful abstraction that allows developers to manage the complexity of the problem. In JACK, agents are defined in terms of their beliefs (what they know and what they know how to do), their desires (what goals they would like to achieve), and their intentions (the goals they are currently committed to achieving).
Entirely written in Java™, JACK is highly portable and runs on anything from PDAs to high-end, multi-CPU servers. Its Java foundation means that JACK can run with multiple threads across multiple CPUs, has platform-independent GUIs, and is easily integrated with third-party libraries.
Yes, you need a Java Development kit or equivalent installed on your computer. A Java runtime by itself is not enough.
JACK® documentation is provided as part of the JACK Documentation package. This package is separate from JACK itself. Once installed, the documents (in PDF and HTML format) are in the doc subdirectory. You can access the JACK documentation from the Help menu of the JDE.
There should also be a link in the automatically installed menu or shortcuts. If not, point your browser at the file doc/jackdocs.html in the place where you installed JACK and it will guide you to all the available documentation.
The JACK® installation comes complete with a set of examples in the sub-directory examples.
You can also look under the Help menu in the JACK Development Environment (JDE).
Yes. Look under the Help menu.
Within a single JVM, all JACK® agents are (normally) executed by just one thread. JACK includes a time-based scheduler, which ensures that all agents get a slice of execution. On top of that, each JACK agent can have many tasks pending at the same time so each agent can specify its own task manager. This provides the task execution policy for that agent. The default is for the agent to stay committed to a task as long as possible.
Each JACK plan is transformed by the compiler into steps in a finite state machine which can be executed by an agent's task manager. The executing thread may leave the plan (task) and come back to it later, and then continue progressing the plan (task) later.
Thus, JACK has only one thread. Plus an additional one for receiving messages.
In many applications, the code within an agent is "java interface code", which may be invoked by threads other than the JACK scheduling thread. (The message receiving thread is an example of such a thread).
There are three possible reasons for this.
Before contacting us, please check to ensure one of these reasons is not the cause.
Some versions of the JACK® compiler had trouble telling apart Java files that were automatically generated by JACK from user-provided Java files. This lead to many name clashes due to duplicate declarations. Newer versions of the compiler should be ok but if in doubt, clean it out!
This happens when any plan step of a reasoning method (e.g. body()) takes an unreasonably long time to complete (about half a second). It usually means that something is calling out to Java code and not coming back, normally a bug with your code. Individual plan steps must execute quickly. In any case, the JACK® kernel leaves that thread alone since it is taking too long and starts a new one to handle other plans. If the original one ever comes back then all is ok. If not, then the agent mentioned is hung. Often this is harmless but it might indicate a bug in your code. There are several ways you can include a lengthy computation within a plan step should the need arise. One quite flexible way is to use an Action cursor (aos.jack.util.cursor.Action). See the JACK Agent Manual for details.
If the process is using a lot of CPU, then you may simply be stuck in an infinite loop. Otherwise, there may be nothing to do because JACK® is just waiting around for an event to process. There are tracing options described in the JACK Agent Manual which may be of use.
This is a Java installation problem rather than a JACK® one. It sounds like your old Java xxx runtime or JDK has become stuck in the registry. Possibly the previous Java that was installed did not get uninstalled properly and now there are incompatible Java components mentioned in the registry.
Although tedious, we suggest the following:
The JACK® compiler needs to be able to locate your java compiler, javac. The message indicates that the java compiler can't be found. You need to have installed a JDK (Java Development Kit) and you need to add the bin directory of wherever your JDK is installed to the PATH environment variable. Unfortunately, the Java installer may not do this for you. Under Windows 2000/XP, you can do this from the Control Panel, under System, in the Environment tab. Under Windows 95/98 etc. you would need to edit C:\AUTOEXEC.BAT.
To test this, open a Command Prompt window and type javac and see if the command is found. If found, it should complain about being called without any java file arguments. If it is not found, then there is still a problem. You may need to log out or reboot after setting the PATH variable.
One other potential problem is if your PATH environment variable has quotes in it. If so, the JDE may not be able to compile your programs. Edit the PATH as described above, and remove any quotes.
If you requested an evaluation copy of JACK® then your email address is required for us to send you a password to enable you to install JACK and use it for the duration of your evaluation period. We do not use any information provided by you for any other external purpose and any information provided by you is treated with the utmost confidence.
JACK® applications never exit on their own. The JACK kernel is always waiting for an event to process. If you want the application to exit, you should call System.exit(0) explicitly when required. However, calling System.exit in this way stops everything immediately. If JACK was still processing, you may get unexpected results.