Usually you have a Sophora server (main server) in which you maintain the website content. If you want to manage additional content in a separate repository or Sophora server (additional content server - ACS), but the editors should use their DeskClient as always, this add-on fulfills that demand. Technically it works like this: the editor connects to a plugin in the main server. This plugin merges the contents of the main server and the ACS, so that in the DeskClient the content from both servers is displayed as if it was only a single server, completely transparent for the user.
The user can search, edit and publish documents of both repositories using the DeskClient and will not notice that he is modifing content from different Sophora Servers. This also includes the work with proposals.
An example would be an ACS with user-related content or user-related data that should be stored separately from the main webpage content.
To install the add-on you need to create a file named acs.properties next to your sophora.properties of the main server. The file contains the connection from the main server to the ACS:
The main server is the server a user usually connect to. The acs server is the server with the additional content that should be shown in the DeskClient of the main server.
The main server will need to login to the acs server to provide the extra content. Therefor an acs-user document must be present in the adminstation view of the main server. This document maps a Sophora role (in the main server) to a Sophora user and its credentials (in the ACS).
You choose a role of the main server and fill in the login credentials of a user in the ACS. This login will be used by the plugin for the connection to the acs server. From now on everyone with that configured role will be able to login with an acs connection.
When logging in with the Sophora DeskClient you need to change the connection URL to http://mainserverdomain:mainserverport?acs=true. After that you are able to search content from the main server and the acs server, edit and publish documents and use proposals from both servers.
Note that an ACS connection can only be established by using http(s). Connecting without ?acs=true results in a connection without the additional content.
It is also possible to run the acs server as a cluster. For that to be possible the Add-on High Availability Cluster is needed.
There are some limitations:
- Administration: To administrate the acs server you need a direct connection to the server. Currently it is not possible to administrate both servers with a single acs connection.
- Links between documents: It is currently not possible to link documents from the main server with documents from the ACS and vice versa.
- Searching documents: While searching for documents you are only able to search in the main repository or the ACS repository. A single search in the DeskClient will only yield results from one repository.
Major updates of the sophora server, especially the stagingslave with an ACS connection (?acs=true), might lead to a situation in which the stagingslave cannot connect to the ACS because of incompatible API versions. This issue can be avoided by the following update procedure:
- Update of all staging slaves
- Update of the acs server
- Update of the main server
When the staging slaves are updated, the ACS documents might not be accessible in the webapp. To reduce this time, the update of the acs server should be done just after the update of the staging slaves.