Client installation overview

To install the DITA CMS Eclipse Client, you prepare the initial Eclipse SDK package and then install the plug-ins.

  • Prepare the initial Eclipse SDK package. This is done by downloading the standard Eclipse SDK and customizing it for DITA CMS.
  • Install the DITA CMS plug-ins. There are two options for installing the DITA CMS Eclipse plug-ins:
    • Through dropins: When Eclipse starts, it checks the contents of its dropins directory and loads the newest plug-ins available. To install a new plug-in or a new version of an existing plug-in, you can simply copy it to the dropins directory and it will be loaded at startup.
    • Through an update site: An update site is a URI (web site, FTP site, file server, etc.) that contains the plug-ins available for installation. Users configure their Eclipse to connect to this URI and check if a new plug-in or a new version of an existing plug-in is available. If it is, then users can install it.
You can install the DITA CMS Eclipse Client directly on user workstations or in a remote access solution (for example, a Citrix or Remote Application server or virtual machines). If you install the client on workstations or virtual machines, you can use either the dropins or update site method. If you install the client on a server farm (Citrix or Remote Application server), you must use dropins.
You can configure the DITA CMS to authenticate users. The DITA CMS supports:
  • Kerberos authentication—Kerberos is an authentication protocol, based on the concept of "tickets", that allows nodes to prove their identity to one another in a secure manner. TEXTML Server can use the Kerberos protocol to authenticate users and provide a secure connection between itself and the DITA CMS Eclipse Client. The DITA CMS supports Kerberos authentication on Windows only (for both server and client, using Active Directory).
  • Local authentication—In this scheme, TEXTML Server uses the local operating system (OS) to authenticate users. The local OS validates the username and password supplied by the user against the authentication method configured on the local OS. If a centralized user database is used (Active Directory, NIS, etc.), the local OS configuration is used to reach the centralized database.

The authentication scheme that you select will impact the initial Eclipse SDK configuration.