CAROL Usage

Quick start for CAROL users

CAROL use on the server side:

• The Server has to be a standard RMI IIOP Server (with PortableRemoteObject export and JNDI bindings).
• Set the Server jvm property by: -Djava.security.policy=${test.ext}/java.policy ... and call, inside the server, the org.objectweb.carol.util.ConfigurationRepository.init() method. You can also give an URL to init() method.
• Set the Server jvm properties by: java -Djavax.rmi.CORBA.PortableRemoteObjectClass=org.objectweb.carol.rmi.multi.MultiPRODelegate -Djava.naming.factory.initial=org.objectweb.carol.jndi.spi.MultiOrbInitialContextFactory
• The ow_carol.jar has to be visible in the server classpath.
• Each stub, for each RMI, has to be visible in the server classpath.
• The carol.properties file has to be visible in the server classpath (see below for the configuration of this file).
• A java.policy file which grants all permissions has to be visible in the server classpath (see in the conf directory of CAROL).

CAROL usage on the client side:

• The ow_carol.jar has to be visible in the client classpath.

carol.properties configuration

• This file is for multi RMI and JNDI configuration (see carol/conf/carol.properties for configuration).

CAROL Compilation and Test

Quick start for CAROL testing

CAROL Building

• Ant is needed for CAROL compilation. (1.6 version)
• In the carol directory, do an "ant dist".
• see the CAROL distribution in carol/output/dist.

CAROL Testing

• AAnt, JUnit 3.8.1 and JDK 1.4 are needed for CAROL tests.
• In the carol directory, type "ant run.tests"
• See the result in output/dist/test/report directory.