Prepare the initial Eclipse SDK package
The DITA CMS plug-ins are installed on a version of the Eclipse SDK framework that is customized for DITA CMS.
To determine what goes into your initial package, you need to answer the following questions:
- Will Kerberos authentication be used on your Windows deployments?
- For workstations and virtual machines, what deployment option will you use for
- Dropins only, and include them in your initial package?
- An update site only?
- A hybrid option, where the initial package contains dropins but other plug-ins are provided with an update site?
The following table describes what you need to include into your initial package, depending on your answers:
|Configuration step||Workstation/Virtual machine||Server farm|
|Dropins only||Update site||Hybrid||Dropins|
|Download the Eclipse SDK||X||X||X||X|
|Package the Java Runtime Environment (JRE) version 1.7||X||X||X||X|
|Edit the eclipse.ini file||X||X||X||X|
|(Optional) Configure the initial working environment for DITA CMS Eclipse clients||X||X||X||X|
|(Optional) Include the DITA CMS plug-ins and Oxygen XML Editor/Author as dropins||X||X||X|
|(Optional) Deploy the plug-ins using an update site||X||X|
|(Optional) Enable Kerberos security||(X)||(X)||(X)||(X)|
|(Optional) Configure the DITA CMS client in a remote solution||X|
|Finalize the package||X||X||X||X|
You need to create a package for every platform supported, for example:
- Windows 32-bit
- Windows 64-bit
- Linux 32-bit
- Linux 64-bit
Also, if you plan to deploy your plug-ins using dropins, you need to create two packages per platform supported, as follows:
- A regular user package
- A CMS administrator package
For example, if you plan to install the DITA CMS using dropins and your deployment supports Linux 64-bit and Windows 64-bit, you would need to create the following four packages:
- Linux 64-bit for regular users
- Linux 64-bit for CMS administrators
- Windows 64-bit for regular users
- Windows 64-bit for CMS administrators