FAQ

  1. What is the relation/difference between JRacer, DIG client in Java and RacerManager?
  2. Is the deployment of OwlQlWebApp optional?
  3. Can I use RacerManager with another DL Reasoner?
  4. My Racer executable obviously does not support the "-p" parameter to alter the default port.
What is the relation/difference between JRacer, DIG client in Java and RacerManager?

JRacer is a java library that can be used by Java programs to communicate with a RacerPro instance.

DIG client in Java is a library that offers a lean interface to communicate with a RacerPro instance via HTTP in the DIG protocol.

RacerManager can serve as a scalable OWL-QL application server for the DL Reasoner RacerPro. It offers iterative query answering, caching and load balancing.

[top]
Is the deployment of OwlQlWebApp optional?

Yes. OwlQlWebApp is a simple client web application to demonstrate the features of RacerManager. You can develop your own client application that calls the web service RacerManager offers.

[top]
Can I use RacerManager with another DL Reasoner?

No, because RacerManager translates OWL-QL queries to the RacerPro-specific new Racer Query Language (nRQL) and it is adapted to work (e.g. communicate) with RacerPro instances.

[top]
My Racer executable obviously does not support the "-p" parameter to alter the default port.

It's a known problem that the Racer version for Windows that is currently distributed by Racer Systems is the acl version, not the lw version that is used by the dev-Team.

We are going to fix this in the next 0.2.1 version of RacerManager. Until than, you can help yourself with the following trick:

change C:\Program Files\RacerPro-1-9-0\RacerPro.exe to C:\Program Files\RacerPro-1-9-0\RacerPro.exe *--*

The "--" forces the acl version to accept the "-p" option.

[top]