Installing ECM Developer
The ECM Developer plugin uses Java 6, so first make sure that your Eclipse is running with this version. The plugin is tested with the recent versions of Helios, Galileo and Ganymede.The plugin uses the Java API based on the WSI protocol to access the FileNet P8 system. Because the Java API is not distributed with this plugin, using this plug-in requires access to the Java API. Therefore installing this plugin is a little bit more complicated than a basic plugin install.
Before you install this plugin you have to make sure that you have the Content Engine Client files available on your local machine. There a two ways to obtain these files:
- The Content Engine Client files are located in a folder named CE_API in the FileNet installation folder on the Application Engine server. You can copy this folder to your local machine.
- If you don't have access to this folder the Content Engine Client files can also be installed using the Content Engine Client installer.
The ECM Developer plugin can be installed using the Eclipse update site http://www.ecmdeveloper.com/update or downloaded from the project download site. Refer to documentation of your Eclipse version how to install plugins. Make sure that you select the correct version of the plugin depending on the version of the FileNet Content Engine you are using. You can only select one version, both versions within the same Eclipse instance will not work!
After the plug-in is installed do not restart Eclipse immediately. For the plug-in to work properly first the Content Engine Client files must be made available within the Eclipse environment. First navigate to the plugins folder of your eclipse installation. The installation of the ECM Developer plug-in created a folder called com.ecmdeveloper.plugin.lib_1.2.0 (for Content Engine 4.5.1 and beyond) or com.ecmdeveloper.plugin.lib_1.1.0 (For Content Engine 4.5). This folder already contains some files. Now the content of the CE_API folder must copied to this folder. After this the installation is completed and Eclipse must be restarted.
See the getting started page for details about how to proceed from here.