Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Corona/Installation

< Corona
Revision as of 11:53, 13 November 2006 by Unnamed Poltroon (Talk) (Installation Steps)

Requirements

In order to install and run Corona it is necessary to have the following Eclipse components:

  • WebTools Platform all-in-one SDK distribution of Eclipse, v 1.5 (contains a complete Eclipse application wiht WTP, EMF, GEF and JEM frameworks) download WebTools Platform
  • Eclipse Communication Framework SDK, v 0.9 (full SDK distribution required) download ECF
  • Add-on equionox bundles download Equinox add-on bundles:
    • org.eclipse.equinox.log
    • org.eclipse.equinox.event
    • org.eclipse.equinox.http
  • Apache Axis2 jars Axis2 jars for Corona
    A number of libraries used by Corona are not yet supplied with the binary distribution because of on-going IP approval process by Eclipse Committee.

Installation Steps

Download Corona

The latest Corona distribution can be downloaded from download Corona. The distribution consists of two parts:

  1. Corona Server - enables collaboration between distributed components, handles event routing and web service calls,
  2. Corona Client - adds collaboration capabilities to Eclipse IDE tool.


Install Eclipse platform for Corona

You need to install two Eclipse instances, one for Corona Server and one for Corona Client. Let the installation directory be called <install> (it is either <installClient> or <installServer>):

  1. Unzip Web Tools Eclipse application to <install>
  2. Unzip ECF to <install>
  3. Copy add-on Equinox bundles to <install>/plugins

Install Corona

In order to install Corona server:

  • Unzip org.eclipse.corona.server-{version}.zip to <installServer>

In order to install Corona client:

  • Unzip org.eclipse.corona.client-{version}.zip to <installClient>

For both client and server:

  • Unzip 3rd party libraries file (plugins.zip) to <install> folder

Running Corona

In order to run a full Corona client-server collaboration with default collaboration context, you need to:

  1. Set CORONA_CONFIG_HOME system variable to the absolute path, in which initial project container definitions are located:
    <installServer>/plugins/org.eclipse.corona.container.config_{version}/examples
    The plugin with container definitions is supplied with both client and server distribution.
  2. Run Corona server:
    1. cd to <installServer>
    2. execute eclipse -console
  3. Run Corona client:
    1. cd to <installClient>
    2. execute eclipse -console -clean

Multi-User Collaboration

In multi-user collaboration, it is assumed that a Corona server is up and running on a host, (let the server that host Corona is called serverHost).

To enable multi-user collaboration:

  • Install Corona clients on machines expected for collaboration
  • Select Corona server
    • Choose Window -> Preferences -> Corona -> Server settings
    • Enter Corona Server URL
  • Configure ECF settings as described in

Development Environment

Configuration Basics

In order to run Corona server it is required to set container configuration directory:

  • the directory pointed by CORONA_CONFIG_HOME system variable. It contains project containers, project containers's properties and team member repositories. An exemplary configuration is located in plugin org.eclipse.corona.container.config/data

In order to run Corona client it is required to set two parameters:

  • Corona server settings, which enables to communicate with the server either locally or remotely, default settings are localhost:1080
  • CORONA_CONFIG_HOME, which enables to read team member repository from an XML file, the configuration will be changed in future versions concerning a general mechanism of authorisation and user verification.

The settings can be changed in Eclipse IDE by calling Window->Preferencec->Corona

Demo Configuration

Project container definition Team member repository

Back to the top