You first need to define an authentication method for the environment(s) you want to use. The way to achieve this is describe in the GUI guide Have a look here to set up authentication in console mode.

The actual delegation of the task is noted by the keyword on followed by a defined Environment:

val env = LocalEnvironment(10)

val t1 = EmptyTask()
val t2 = EmptyTask()
val t3 = EmptyTask()

val mole = t1 -- (t2 on env) -- t3

You do not need to install anything or perform any kind of configuration on the target execution environment for OpenMOLE to work. It reuses the infrastructure in place. You will however be required to provide the authentication information in order for OpenMOLE to access the remote environment. At this point, just specify the credentials you're using to login to this environment outside of OpenMOLE. Voila! That's all you need to do to use your environment through OpenMOLE. In case you face authentication problems when targeting an environment through SSH, please refer to the corresponding entry in the FAQ.

When no specific environment is specified for a task, or a group of tasks, they will be executed sequentially on your local machine.

The use of a batch environment is generally not suited for short tasks (less than a 1 minute for a cluster, or less than 1 hour for a grid). In case your tasks are short you can group several executions. To group the execution by 100 in each job submitted to the environment, use the keyword by:

val mole = explo -< (t1 on env by 100)

Multiple environments are available to delegate your workload, depending the kind of resources you have on disposal.

The Multi-thread permits to execute the tasks concurrently on your machine, the SSH one to execute tasks on remote server through SSH. You can also access a wide variety of clusters like PBS/Torque, SGE, Slurm, Condor, or OAR. You can also use EGI to execute tasks on the EGI grid, or the Ad-hoc Desktop Grid to distribute your workflows on a set of desktop/laptop computers.