To be able to operate CMS Fiona's GUI on a different computer than the Content Management Server, you first require a complete installation of the same CMS version on the dedicated computer. Afterwards, the CM and the GUI need to be configured so that the GUI is able to reach the CM.
For this, first open the Trifork console on the computer where Fiona was originally
administrator as login and
Switch to the JDBC/Datasources section and click the database type you use. Write down all parameters to be found in the input mask. Later, these parameters need to be entered on the GUI machine.
Now, on both machines, make the changes to the
file as described above so that the GUI is not started on the original
machine, whereas it is started on the other machine when
start is executed.
Afterwards, the configuration files are adapted on the CM machine and then deployed to the other machines. Please proceed as described below:
server.xmlfile located in the instance-specific configuration the connection parameters
server.cm.httpPortso that the GUI can reach the CM on its machine. The CM waits for connections on the
httpHost(leave empty for all host names assigned to the machine). It can be reached on the
httpConnectHostby other CMS components.
basicConfig.propertiesfile located in the instance-specific directory
webapps/GUI/WEB-INFthe connection parameters
cmHttpPortso that the GUI can reach the CM on the
httpPortstored in the
dynamicPreviewExtensionsparameters on the CM machine. They can be found in the
gui.xmlfile located in the instance-specific configuration directory.
export.guiUrlentry in the
export.xmlsystem configuration file located in the instance-specific configuration directory of the CM machine so that the GUI on the GUI machine is connected:
instanceNamewith the actual name of the instance):