Preview only show first 10 pages with watermark. For full document please download

How To Configure A 6.7 Publishing Hub

   EMBED

Share

Transcript

August 27, 2010 How to Configure a 6.7 Publishing Hub How to Configure a 6.7 Publishing Hub Introduction The purpose of this document is to outline the steps necessary to install and configure a Percussion CM System 6.7 Publishing Hub. Once a Publishing Hub is configured, all scheduled publishing tasks should be run on the Publishing Hub machine. Going forward, any manual publishing jobs should only be started from the Publishing Hub and all content contribution should only occur on the System Master instance. Content Contributors should not log in to the Publishing Hub. IMPORTANT: A new license is required in order to legally utilize a Publishing Hub. Please contact Percussion Sales < http://www.percussion.com/about/company-information/contact/> if you need a Publishing Hub License but don’t already have one. Assumptions This document assumes that you are using Percussion CM System version 6.7. Steps to Implement Steps to implement go here. 1. 2. 3. 4. Installing the Percussion CMSystem Publishing Hub Backup the installation.properties and sys_license.xml files Clone Production System Master and Redeploy it on the New Host Configure the Publishing Hub Installing the Percussion CMSystem Publishing Hub 1. Download and perform a fresh installation of Percussion CM System on your desired Publishing Hub Windows Server host machine: a. Create a blank database in either MSSQL or ORACLE NOTE: This is a temporary database and will be deleted later. b. Create an installation directory for your 6.7 Publishing Hub e.g. mkdir C:\Percussion\CMSystem\PubHub () 1 Introduction | Percussion Software, Inc. August 27, 2010 How to Configure a 6.7 Publishing Hub c. During Installation be sure to choose the “Publishing Hub” option in the Server Type step of the installation, and make sure to use the provided publishing hub license. Backup the installation.properties and sys_license.xml files 1. Once installation has completed successfully, drop the new database and backup the following files somewhere outside of the newly installed CM System Publishing Hub installation folder: • • C:\Percussion\CMSystem\PubHub\rxconfig\Installer\installation.properties C:\Percussion\CMSystem\PubHub\rxconfig\Server\sys_license.xml 2. Delete everything under the PubHubRoot directory C:\Percussion\CMSystem\PubHub\ Clone Production System Master and Redeploy it on the New Host 1. Take a clone of your Production System Master filesystem directory (a.k.a. “Rhythmyx tree”) a. Shutdown Rhythmyx b. Make a ZIP or TAR.GZ of the System Master root directory 2. Extract the compressed System Master clone as a sibling to the new PubHubRoot directory. C:\Percussion\CMSystem\Rhythmyx\ 2 Steps to Implement | Percussion Software, Inc. August 27, 2010 How to Configure a 6.7 Publishing Hub 3. Once extraction is complete, move extracted files into the target PubHubRoot directory a. Move everything from C:\Percussion\CMSystem\Rhythmyx\ to C:\Percussion\CMSystem\PubHub\ 4. Modify the necessary paths and port #’s to reflect the new configuration on the new host. Please use either the “Rx_6x_How_to_Move_a_Rhythmyx_6.7_Environment.pdf“ or “Rx_6x_How_to_Move_a_Rx_6x_Env_without_RhythmyxServerPropertiesEditor_GUI.pdf“ for details about how to do that. NOTE: The two files that should not be changed are the rx-ds.xml and the serverbeans.xml. These are the files that point to the database, which must be the same database as the System Master. Configure the Publishing Hub 1. Open \rxconfig\Server\config.xml in a text editor. 2. Search for "serverType" and change the value of the parameter from "System Master" to "Publishing Hub", 3. Search for "PSXSearchConfig" and change the "fullTextSearchEnabled" parameter to "no". 4. Save the file. 5. Open \rxconfig\Server\server.properties in a text editor. 6. Search for "ServerType" and change the value for the parameter from "System Master" to "Publishing Hub". 7. Save the file. 8. Copy the two files from step 1 of “Backup the installation.properties and sys_license.xml files” into the newly extracted Production System Master tree in the same locations as the source files and overwrite the extracted files with the backup files. 9. Remove any automated publishing scripts or scheduled tasks from the System Master machine and add them to the new Publishing Hub machine. 3 Steps to Implement | Percussion Software, Inc. August 27, 2010 How to Configure a 6.7 Publishing Hub IMPORTANT: The System Master filesystem and the Publishing Hub filesystem must be in sync at ALL times! Any patch installed to the System Master MUST be installed on the Publishing Hub. Any system object modification or manual system file changes made to the System Master must also be made to the Publishing Hub. Failure to maintain this process will result in unknown results and possibly corrupt your database. Backups of both environments should be taken on a regular basis. If in the event of filesystem corruption on the System Master, you must recover the System Master tree from a backup, and the Publishing Hub tree should also be recovered from a backup on the same date and time, or recreated using the backup of the System Master tree. Similarly, if in the event of filesystem corruption on the Publishing Hub, you can either recover from a backup, or recreate the Publishing Hub using a clone of the System Master following the steps in this document. 4 Steps to Implement | Percussion Software, Inc.