ECF/Servers

ECF Generic Server

ECF is currently using the Equinox Servlet Incubator to run and support the example collab application running on the 'ECF generic' provider.

Connecting to the ECF Generic Server

1. Download and install the ECF SDK.
2. Right-click on a project within your workspace.
3. Choose 'ECF' -> 'Connect Project...' from the popup menu.
4. Select the 'ECF generic' provider from the list.
5. Use ecftcp://ecf.eclipse.org:3282/server as the connect URI.
6. Choose a nickname and then select the 'OK' button.

Starting the ECF Server in an Eclipse Workspace

1. In this context, we'll assume that you're trying to do some development with ECF and have checked out the latest sources from CVS. If you have not already done so, you can go to the development resources and pick up the team project set files.
2. Once you've got your workspace setup, open up the org.eclipse.ecf.provider project and wait for it to build completely if you have not already.
3. You should now click on the dropdown arrow of the green 'Run' button and then click on 'Run...'.
4. In the 'Java Application' tree node, expand it and then find the 'ECF Server Application' launch configuration.
5. Click on the 'Run' button on the bottom right-hand corner and your workstation will not become an 'ECF generic' server!

Setting up an ECF Server with the Equinox Servlet Incubator

1. Follow instructions for setting up the Equinox Servlet Incubator. Note the location of the <appserverhome>/webapps/bridge/WEB-INF/platform/plugins directory.
2. NOTE: ECF server requires some of the bundles that come from the Equinox core (containing org.eclipse.core.runtime packages and and others). See Equinox download page for these bundles.
3. Download ECF plugins: ECF 0.9.6 or ECF Download Page
   1. Copy the ECF plugins into the <appserverhome>/webapps/bridge/WEB-INF/platform/plugins directory created above.
4. Edit the conf/server.xml in org.eclipse.ecf.server plugin (temporarily (0.9.6) you will need to unjar this plugin, edit the server.xml as described below and either re-jar it or create a directory for it...we'll get this fixed in subsequent releases. I've setup bug 172724 to track this). The default content for server.xml is:

   <server>
     <!--
       <connector protocol="ecftcp"  hostname="localhost" port="3282" timeout="30000">
   	<group name="server"/>
       </connector>
   	-->
   </server>
   

   Notice that this default connector is commented out. You should create connectors like this (from ecf.eclipse.org):

   <server>
      <connector protocol="ecftcp"  hostname="localhost" port="3282" timeout="30000">
              <group name="server"/>
              <group name="se"/>
      </connector>
   </server>
   

   This sets up two groups, with URLs:

   ecftcp://ecf.eclipse.org:3282/server and ecftcp://ecf.eclipse.org:3282/se

   You can add as many groups as you want for a given connector.

5. Start the org.eclipse.ecf.server bundle. This can be done via the server console (with 'start org.eclipse.ecf.server') or can be setup to start automatically via the <appserverhome>webapps/bridge/WEB-INF/platform/configuration/config.ini file.