Multi-site deployments

There are two recommended scenarios for a multi-site deployment.

Option 1: Using a single Content Store on a TEXTML Server

In this deployment option, shown in Figure 1, a single Content Store is installed ; it is located at the primary site (Montreal). Users at the primary site install the DITA CMS Eclipse Client on their workstations.

The users at the secondary site (New York) run the DITA CMS as follows:
  • Authors, editors, and reviewers (i.e., light users) run the DITA CMS through the DITA CMS Eclipse Client installed on their workstations. To perform transactions, the DITA CMS Eclipse Client accesses the Content Store at the primary site over the WAN. Because light users generate a small number of DITA CMS transactions, these transactions can be executed over the WAN while still providing a good response time. See Software requirements for more information about latency.
  • Information architects, localizers, and production officers (i.e., heavy users) run the DITA CMS by working with a DITA CMS Eclipse Client installed at the primary site, using a remote access solution (Citrix, Microsoft remote application, or a virtual machine). Because these users perform a large number of transactions on many objects, the DITA CMS transactions must be performed locally at the primary site for optimal performance.
Satellite users (such as users working from home or very small offices) can run the DITA CMS application in one of two ways:
  • By installing the DITA CMS Eclipse Clients on their workstations.
  • By working with a DITA CMS Eclipse Client installed at the primary site, using a remote application solution. This is the preferred solution for heavy users.
The main objective with multiple sites is to ensure that the performance and response time for users located at secondary sites (or for satellite users) is acceptable.
Note: When the WCR and Web Author Clients are started, they download an applet from their respective application (i.e., the WCR Application and Web Author Application). If poor performance is observed when users at the secondary site access the WCR or the Web Author clients, this may indicate that the WAN bandwidth isn't sufficient to handle these operations. One option is to add a WCR Application and a Web Author Application at the secondary site to handle these requests.
Figure 1. Multi-site deployment with a single Content Store Simple multi-site deployment

Option 2: Using a replicated Content Store and two TEXTML Servers

If all users at the secondary site were light users, they could all run the DITA CMS through the DITA CMS Eclipse Client, so no remote access solution would be necessary.

Another option is to replicate the Content Store at the secondary site, as shown in the following diagram.

Figure 2. Multi-site deployment with a replicated Content Store Option 2: Using replicated Content Store

In this deployment option, a primary Content Store is installed at the primary site (Montreal). Users at the primary site install the DITA CMS Eclipse Client on their workstations.

A replicated Content Store is installed at the secondary site (New York). The users at the secondary site run the DITA CMS as follows:
  • Light users still run the DITA CMS through the DITA CMS Eclipse Client installed on their workstations, as in option 1, but they now access the Content Store locally instead of over the network, which makes some of their operations faster, including:
    • Read access to the Content Store (for example, searches)
    • Generating the output
    Write operations are still performed over the WAN, so they are executed in about the same time as in option 1.
  • Heavy users still work directly with the primary Content Store for optimal performance, using remote access, since they generate too many DITA CMS transactions.

Satellite users (users working from home and London) still run the DITA CMS using a remote access solution or though a DITA CMS Eclipse Client installed locally, but they should access the Content Store located at the primary site. However, if connection to the primary site is too slow, light users can connect to the replicated Content Store located at a secondary site near their location.

Using a replicated Content Store is recommended if there are many light users at the secondary site, or if there is too much latency when light users try to perform DITA CMS transactions. Note that, even though users are spread over multiple sites, they share the same workgroup configuration.
Note: Additional IXIASOFT licenses are required for the replicated Content Store; a third-party license for the rendering software (e.g., Antenna House, RenderX) may also be required.