Ektron CMS400.NET Site Replication Manual

Transcription

1 Ektron CMS400.NET Site Replication Manual Includes Quick Deploy Version 2.0, Revision 8 Ektron Inc. 542 Amherst St. Nashua, NH Tel: Fax: sales@ektron.com

3 EKTRON, INC. SOFTWARE LICENSE AGREEMENT ** READ THIS BEFORE LOADING SOFTWARE** YOUR RIGHT TO USE THE PRODUCT DELIVERED IS SUBJECT TO THE TERMS AND CONDITIONS SET OUT IN THIS LICENSE AGREEMENT. USING THIS PRODUCT SIGNIFIES YOUR AGREEMENT TO THESE TERMS. IF YOU DO NOT AGREE TO THIS SOFTWARE LICENSE AGREEMENT, DO NOT DOWNLOAD. CUSTOMER should carefully read the following terms and conditions before using the software program(s) contained herein (the Software ). Downloading and/or using the Software or copying the Software onto CUSTOMER S computer hard drive indicates CUSTOMER S acceptance of these terms and conditions. If CUSTOMER does not agree with the terms of this agreement, CUSTOMER should not download. Ektron, Inc. ( Ektron ) grants, and the CUSTOMER accepts, a nontransferable and nonexclusive License to use the Software on the following terms and conditions: 1. Right to use: The Software is licensed for use only in delivered code form. Each copy of the Software is licensed for use only on a single URL. Each license is valid for the number of seats listed below (the Basic Package ). Any use of the Software beyond the number of authorized seats contained in the Basic Package without paying additional license fees as provided herein shall cause this license to terminate. Should CUSTOMER wish to add seats beyond the seats licensed in the Basic Package, the CUSTOMER may add seats on a block basis at the then current price for additional seats (see product pages for current price). The Basic Packages are as follows: Ektron CMS300 - Licensed for ten seats (10 named users) per URL. Ektron CMS400.NET - Licensed for ten seats (10 named users) per URL. Ektron ewebeditpro - Licensed for ten seats (10 named users) per URL. Ektron ewebeditpro+xml - Licensed for ten seats (10 named users) per URL. For purposes of this section, the term seat shall mean an individual user provided access to the capabilities of the Software. The CUSTOMER may not modify, alter, reverse engineer, disassemble, or decompile the Software. This software product is licensed, not sold. 2. Duration: This License shall continue so long as CUSTOMER uses the Software in compliance with this License. Should CUSTOMER breach any of its obligations hereunder, CUSTOMER agrees to return all copies of the Software and this License upon notification and demand by Ektron. 3. Copyright: The Software (including any images, applets, photographs, animations, video, audio, music and text incorporated into the Software) as well as any accompanying written materials (the Documentation ) is owned by Ektron or its suppliers, is protected by United States copyright laws and international treaties, and contains confidential information and trade secrets. CUSTOMER agrees to protect the confidentiality of the Software and Documentation. CUSTOMER agrees that it will not provide a copy of this Software or Documentation nor divulge any proprietary information of Ektron to any person, other than its employees, without the prior consent of Ektron; CUSTOMER shall use its best efforts to see that any user of the Software licensed hereunder complies with this license. 4. Limited Warranty: Ektron warrants solely that the medium upon which the Software is delivered will be free from defects in material and workmanship under normal, proper and intended usage for a period of three (3) months from the date of receipt. Ektron does not warrant the use of the Software will be uninterrupted or error free, nor that program errors will be corrected. This limited warranty shall not apply to any error or failure resulting from (i) machine error, (ii) Customer's failure to follow operating instructions, (iii) negligence or accident, or (iv) modifications to the Software by any person or entity other than Company. In the event of a breach of warranty, Customer s sole and exclusive remedy, is repair of all or any portion of the Software. If such remedy fails of its essential purpose, Customer s sole remedy and Ektron s maximum liability shall be a refund of the paid purchase price for the defective Products only. This limited warranty is only valid if Ektron receives written notice of breach of warranty within thirty days after the warranty period expires. 5. Limitation of Warranties and Liability: THE SOFTWARE AND DOCUMENTATION ARE SOLD AS IS AND WITHOUT ANY WARRANTIES AS TO THE PERFORMANCE, MERCHANTIBILITY, DESIGN, OR OPERATION OF THE SOFTWARE. NO WARRANTY OF FITNESS FOR A PARTICULAR PURPOSE IS OFFERED. EXCEPT AS DESCRIBED IN SECTION 4, ALL WARRANTIES EXPRESS AND IMPLIED ARE HEREBY DISCLAIMED. NEITHER COMPANY NOR ITS SUPPLIERS SHALL BE LIABLE FOR ANY LOSS OF PROFITS, LOSS OF BUSINESS OR GOODWILL, LOSS OF DATA OR USE OF DATA, INTERRUPTION OF BUSINESS NOR FOR ANY OTHER INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY KIND UNDER OR ARISING OUT OF, OR IN ANY RELATED TO THIS AGREEMENT, HOWEVER, CAUSED, WHETHER FOR BREACH OF WARRANTY, BREACH OR REPUDIATION OF CONTRACT, TORT, NEGLIGENCE, OR OTHERWISE, EVEN IF COMPANY OR ITS REPRESENTATIVES HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH LOSS.

4 6. Miscellaneous: This License Agreement, the License granted hereunder, and the Software may not be assigned or in any way transferred without the prior written consent of Ektron. This Agreement and its performance and all claims arising from the relationship between the parties contemplated herein shall be governed by, construed and enforced in accordance with the laws of the State of New Hampshire without regard to conflict of laws principles thereof. The parties agree that any action brought in connection with this Agreement shall be maintained only in a court of competent subject matter jurisdiction located in the State of New Hampshire or in any court to which appeal therefrom may be taken. The parties hereby consent to the exclusive personal jurisdiction of such courts in the State of New Hampshire for all such purposes. The United Nations Convention on Contracts for the International Sale of Goods is specifically excluded from governing this License. If any provision of this License is to be held unenforceable, such holding will not affect the validity of the other provisions hereof. Failure of a party to enforce any provision of this Agreement shall not constitute or be construed as a waiver of such provision or of the right to enforce such provision. If you fail to comply with any term of this License, YOUR LICENSE IS AUTOMATICALLY TERMINATED. This License represents the entire understanding between the parties with respect to its subject matter. YOU ACKNOWLEDGE THAT YOU HAVE READ THIS AGREEMENT, THAT YOU UNDERSTAND THIS AGREEMENT, AND UNDERSTAND THAT BY CONTINUING THE INSTALLATION OF THE SOFTWARE, BY LOADING OR RUNNING THE SOFTWARE, OR BY PLACING OR COPYING THE SOFTWARE ONTO YOUR COMPUTER HARD DRIVE, YOU AGREE TO BE BOUND BY THIS AGREEMENT S TERMS AND CONDITIONS. YOU FURTHER AGREE THAT, EXCEPT FOR WRITTEN SEPARATE AGREEMENTS BETWEEN EKTRON AND YOU, THIS AGREEMENT IS A COMPLETE AND EXCLUSIVE STATEMENT OF THE RIGHTS AND LIABILITIES OF THE PARTIES. Copyright Ektron, Inc. All rights reserved. LA10031, Revision 1.7 Trademarks All terms in this manual that are known to be trademarks have been capitalized. Ektron, Inc. cannot attest to the accuracy of this information. Use of a term in this manual does not affect the validity of any trademark. The following trademarks might appear in Ektron manuals: Active Directory, ActiveX, Authenticode, BackOffice, ClearType, Developer Studio, FrontPage, IntelliSense, JScript, Microsoft, MS-DOS, SharePoint Visual C++, Visual C#, Visual InterDev, Visual J++, Visual J#, Visual Studio, Visual Web Developer TM, Win32, Win32s, Windows, Windows NT, Windows Server TM, Windows Server System TM, Netscape, Netscape Navigator, Mozilla TM, Firefox TM

5 Table of Contents System Requirements...1 Server Requirements...1 PC Client Requirements...2 Apple Macintosh Client Requirements...2 Site Replication and Quick Deploy...4 Comparison of Site Replication and Quick Deploy...5 Site Replication...6 Site Replication vs. the Move Site Procedure...7 Site Replication Overview...8 What Information is Synchronized... 8 What Information is Preserved... 9 Preserving Custom Settings on Production Server while during Site Replication Possible Site Replication Configurations...10 Site Replication Best Practices Prerequisites Installing the Site Replication Feature...13 Additional Steps Prior to Configuring the Site Replication Feature. 25 Updating Membership Users Preserving Database Tables Configuring the Site Replication Feature...32 Configuring the Receiving Server Configuration Screen Security Remote DB Backups Configuring the Sending Server Configuration Screen Destinations Screen Remote DB Screen Notification Screen Make Staging Screen The Site Replication Status Page Setting up a Staging Server...45 Previewing the Site Replication Process...46 Performing Site Replication...47 Viewing and Restoring a Backup of the Production Server..49 How Backup Files Are Maintained and Numbered Setting the Maximum Number of Backups Restoring a Backup Ektron CMS400.NET Site Replication Manual, Version 2.0, Revision 8 i

6 The Site Replication Configuration File...51 Hidden Elements Receive Section Send Section Backup Section Schedule Section Site Replication web.config File Using Site Replication with Multiple Sites...58 Installation Guidelines Using Site Replication with Development > Staging > Production Servers...62 Moving.aspx Templates from Development to Staging Server Moving the Database from Development to Staging Server Testing Site Replication Software...64 List of Tests Per Server The Scheduler Windows Service...69 Running the Scheduler Service from a Remote Server Troubleshooting the Scheduler Windows Service Using the Scheduler Windows Service with Multiple Sites Uninstalling the Scheduler Windows Service Troubleshooting Problems with Site Replication...71 Uninstalling Site Replication...76 Quick Deploy...78 When Not to Use Quick Deploy...78 Information Copied During Quick Deploy...79 From Staging to Production Server From Production to Staging Server Quick Deploy Prerequisites...80 Enabling Multiple Production Destinations Using Quick Deploy...83 Automatic Movement of CMS Content Using Quick Deploy Manual Movement of CMS Content Using Quick Deploy Manual Movement of Menus and Collections Using Quick Deploy. 84 Linking to Library or Content Items Moving non-content Files with Quick Deploy Quick Deploy Troubleshooting...90 Ektron CMS400.NET Site Replication Manual, Version 2.0, Revision 8 ii

7 System Requirements System Requirements The following components are required when developing or viewing Site Replication and Quick Deploy. Server Requirements on page 1 PC Client Requirements on page 2 Apple Macintosh Client Requirements on page 2 Server Requirements Component Requirements Recommended hardware configuration Intel Pentium 4 supporting Hyper-Threading or Intel Xeon processor (with 800MHz bus) 1 GB RAM or higher RAID array for hard drives Web server operating system Microsoft Windows 2003 Server recommended (32 bit version only) Microsoft Windows 2000, XP Professional Note: XP Home does not support IIS. Web application server Microsoft.NET Framework 2.0 (required) Microsoft Active Server Pages Web server Microsoft Internet Information Server (IIS) 4.0 or higher Ektron CMS400.NET Site Replication Manual, Version 2.0, Revision 8 Revision 6 1

8 System Requirements Component Requirements Databases SQL Server 2005 SQL Server 2005 Express SQL Server 2000 (Enterprise or Standard version) PC Client Requirements Component Operating system Browsers Requirements Any IBM-PC compatible system running Windows (32 bit versions only) Suggested minimum: Pentium 166 MHz or faster with 64MB of RAM All major browsers including: Microsoft Internet Explorer 3.0 through 7.0 Netscape Navigator Version 3.0 through 7.2 Mozilla Firefox Hardware Any IBM-PC compatible system running Windows (suggested minimum requirements: Pentium 166 MHz or faster with at least 64MB of RAM) Apple Macintosh Client Requirements Component Operating system Requirements MAC OS X Ektron CMS400.NET Site Replication Manual, Version 2.0, Revision 8 Revision 6 2

9 System Requirements Component Browsers Requirements All major browsers including: Apple Safari (Recommended) Microsoft Internet Explorer Netscape Navigator Mozilla Firefox Hardware Apple Macintosh Ektron CMS400.NET Site Replication Manual, Version 2.0, Revision 8 Revision 6 3

10 and Quick Deploy Site Replication and Quick Deploy NOTE Ektron CMS400.NET s Site Replication and Quick Deploy software is an extra cost option. Please contact your Ektron sales representative for details on purchasing it. Site Replication and Quick Deploy are Ektron CMS400.NET features that move files between your staging and production servers. Site Replication moves an entire site, while Quick Deploy typically moves content to production as soon as it is published on staging. See Also: Comparison of Site Replication and Quick Deploy on page 5 Site Replication on page 6 Quick Deploy on page 78 Ektron s Site Replication/Quick Deploy Best Practices Guide ( EktronCMS400Replication pdf) Ektron CMS400.NET Site Replication Manual, Version 2.0, Revision 8 4

11 and Quick Deploy Comparison of Site Replication and Quick Deploy Feature Site Replication Quick Deploy Direction of Movement From staging to production only Two-way between staging and production What is moved Virtually everything entered in the staging server; see What Information is Synchronized on page 8 Option to send database and files or files only From staging to production: New/ updated content and files in folders set up for Quick Deploy; menus, collections, forum configuration information, users/ user groups; also, manually-selected files (e.g., templates) in Web root folder From production to staging: information collected on production server, such as content analytics, poll/survey results, membership users, content and assets inside folders set up for Quick Deploy What is not moved Content typically entered on production server; see What Information is Preserved on page 9 Files not listed above, under What is moved How triggered Go to screen and click button Automatically when one of these events occurs on staging server. - content in any folder for which Quick Deploy has been activated is updated (not necessarily published) - a Quick Deploy folder is created or its properties, permissions, or approval chain is updated - a CMS or membership user or user group is updated Manually by going to screen and clicking button Backup of earlier version available; can be rolled back if needed yes no Can preview files to be moved beforehand yes no Ektron CMS400.NET Site Replication Manual, Version 2.0, Revision 8 5

12 Feature Site Replication Quick Deploy Can review files moved afterwards yes yes Schedule to run automatically at regular interval yes no Effect on database Creates new one Synchronizes parts of the database Privileges needed Many privileges needed because it affects files and databases Uses asp.net account Site Replication WARNING! If you upgrade a staging server from version 5.2 to 7.0 but don t choose to upgrade the production server, you need to complete some steps to make the two systems compatible.this procedure is explained in Upgrading Ektron CMS400.NET > Updating a Site Replication Production Machine after Upgrading from 5.2 to 7.0 in the Ektron CMS400.NET Setup Manual. Site Replication is an automated, one-way site synchronization between a staging or test server and a production server. It lets you perfect changes on a staging server, then effortlessly copy them to the production server. In this way, your production server can easily be kept up-to-date, while at the same time be spared simple errors that typically accompany last-minute changes. (Synchronization differs from copying in that it only copies files that are new or have changed. Since most files on both servers are typically the same, synchronization is faster than copying.) Whether you ve been testing a new site template or an upgraded version of CMS400.NET, Site Replication pushes the latest information to the production server. Site Replication is especially useful when your site contains sensitive information (for example, pricing) that needs to be carefully reviewed for quality assurance before it goes live. Ektron CMS400.NET Site Replication Manual, Version 2.0, Revision 8 6

13 Before the latest data is copied to the production server, it is backed up. So, you can restore the production server to an earlier version if you ever need to. For more information about Site Replication, see these topics. Site Replication vs. the Move Site Procedure on page 7 Site Replication Overview on page 8 Possible Site Replication Configurations on page 10 Prerequisites on page 11 Installing the Site Replication Feature on page 13 Configuring the Site Replication Feature on page 32 Setting up a Staging Server on page 45 Previewing the Site Replication Process on page 46 Performing Site Replication on page 47 Viewing and Restoring a Backup of the Production Server on page 49 The Site Replication Configuration File on page 51 Using Site Replication with Multiple Sites on page 58 Using Site Replication with Development > Staging > Production Servers on page 62 Testing Site Replication Software on page 64 The Scheduler Windows Service on page 69 Troubleshooting Problems with Site Replication on page 71 Uninstalling Site Replication on page 76 Site Replication vs. the Move Site Procedure The Ektron CMS400.NET Setup Manual section Installing Ektron CMS400.NET > Moving a Site to Another Directory or Server describes a procedure for moving an ewebeditpro+xml Web site to a new folder or even a different server. You would use that procedure under the following circumstances: Ektron CMS400.NET Site Replication Manual, Version 2.0, Revision 8 7

14 The initial move of a site up to a shared server (or any other server on which you cannot run the.exe installer). Subsequently, you would use the Site Replication feature. Moving a site to a new server. For example, you purchase a new server to replace your existing one. Moving a site between two servers that are not connected by a network. Site Replication Overview First, install Site Replication software onto both servers. Next, supply configuration information for each server, such as the site directory and when replication begins. Then, begin using Site Replication to synchronize the test server with the production server. Before initiating the synchronization, a Preview button displays the changes that will occur. Once you are ready, begin the synchronization. At this point, the staging database is backed up then sent over. On the production server, that database is restored and given a new name. Production server files not on the staging server are deleted from the production server. During this time, a screen displays the real-time progress of the replication. When synchronization is complete, you can view a log of changes made. If you decide the update should not have occurred, you can restore the receiving server. You can apply security to Site Replication by restricting the IP address and user name of the machine/person who initiates the procedure. NOTE You should verify that adequate space is available for the Site Replication. The data directories are backed up before the Site Replication begins. The previous version remains, creating a sitereplication.backup/.dirbackup date time file. A new copy of the data directories is placed in the same folder and is named dirupdates date time. What Information is Synchronized Synchronized information includes: Ektron CMS400.NET Site Replication Manual, Version 2.0, Revision 8 8

15 CMS400.NET code (the CMS400Scripts directory) CMS400.NET database schema changes CMS400.NET database content CMS400.NET assets Site Replication Document Management Functionality code (the AssetManagement directory) templates (ASPX, ASP, PHP, JSP) library content (uploadedfiles and uploadedimages folders) CMS400.NET web.config file user list - However, when the user list is copied to the production server, non-administrative users permission to add content is removed. What Information is Preserved The following kinds of information are preserved on the production server, but not sent to the staging server. membership users (See Also: Updating Membership Users on page 30) user profile settings license key and URL aliasing settings content ratings data content tracking statistics forum and blog posts (including forum private messages, attachments, and thread watches) community folders and permission changes CMS400.NET form data tables - contain form/poll/survey submissions from a Web site. Also, any tasks that track form data. Web.config settings (may need to be updated manually if you use Site Replication to push an Ektron CMS400.NET upgrade that includes new web.config settings. The new settings will not exist on the production server.) Ektron CMS400.NET Site Replication Manual, Version 2.0, Revision 8 9

16 AssetManagement.config (only needs to be updated manually when upgrading if receiving server has Document Management Functionality) AssetManagementData.config (only needs to be updated manually when upgrading if receiving server has Document Management Functionality) The most recent searches table, use to generate the Search Phrase Report Optionally, a list of tables on the production machine (See Also: Preserving Database Tables on page 31) NOTE SIte Replication does not install Windows services. To do that, you must upgrade Ektron CMS400.NET software on the production server. Preserving Custom Settings on Production Server while during Site Replication You can preserve custom web.config settings on the production server when doing site replication. To do this, place the following code into the production server s web.config file, within the <appsettings> tag. The key s value is a comma-separated list of appsettings, like this. <add key="ek_replicationpreserveappsettings" value="appsetting1,appsetting2" /> This code preserves the appsetting1 and appsetting2 keys in the production server s web.config file during Site Replication. Possible Site Replication Configurations The following configurations are supported during Site Replication: CMS400.NET site and database on same server - Assign unique names to the directories. For example, use and for URLs. - You can put Site Replication on different Web sites. (It is not part of Ektron CMS400.NET. It is a standalone Web application.) Ektron CMS400.NET Site Replication Manual, Version 2.0, Revision 8 10

17 - The Production and Staging servers can use the same relative directory. For example, root folder and root folder. CMS400.NET site and database on separate servers Three servers: Development to Staging to Production - Configure the development server as a sending server. Send to the staging server. - Configure staging server as sending server to production server. Then, add it as the receiving server for the development server. Its sending and receiving directories are the same. - Configure the production server as the receiving server for the staging server See Also: Using Site Replication with Development > Staging > Production Servers on page 62 Site Replication Best Practices Each site must have its own database. Two sites cannot share a database. You cannot use Site Replication to move files from a production to a staging server. To sync the staging and production sites, run Quick Deploy once before running Site Replication for the first time. You cannot upgrade a staging server then use Site Replication to move those change to the production server. You must run the upgrade on each server. It is important to synchronize the clock on both servers (staging and production). Prerequisites Every user who will use Site Replication must be a member of the Administrators group within Windows Microsoft Management Console. Ektron CMS400.NET Site Replication Manual, Version 2.0, Revision 8 11

18 To apply this setting to a user, follow these steps. 1. Click Start > Control Panel > Administrative Tools > Computer Management. 2. Click Local Users and Groups then the Users folder. 3. If the user does not appear in the right frame, right click the mouse and select New User... Then complete the dialog. 4. Right mouse click on the user and select Properties. 5. Click the Member Of tab. Ektron CMS400.NET Site Replication Manual, Version 2.0, Revision 8 12

19 6. If you do not see Administrators in the Member Of window, click the Add button. 7. In the Enter the object names to select field, enter Administrators. 8. Click OK twice. Installing the Site Replication Feature You must install the Site Replication feature on the staging server and all production servers. After installing on a server, you should configure it. See Also: Configuring the Site Replication Feature on page Download the Site Replication.exe file from Ektron s Web site. 2. Double click the downloaded file. 3. Follow the screen directions as they appear. Ektron CMS400.NET Site Replication Manual, Version 2.0, Revision 8 13

20 Directions Screen 1. Indicate if this is a new installation or an upgrade. If doing an upgrade, only perform steps 3 and 6 below. Ektron CMS400.NET Site Replication Manual, Version 2.0, Revision 8 14

21 Directions Screen 2. Indicate whether the server on which you are installing will be used to send or receive information. A staging server would send, while a production server would receive. Ektron CMS400.NET Site Replication Manual, Version 2.0, Revision 8 15

22 Directions Screen 3. Identify the Web site for which you are installing the Site Replication feature. If you are unsure, accept the default. 4. Select the site host from the dropdown list. Or, you can check the Enter Host Manually box and enter the path to your site host. Ektron CMS400.NET Site Replication Manual, Version 2.0, Revision 8 16

23 Directions Screen 5. Enter the directory in which Ektron CMS400.NET resides. Important! The staging and production servers must use the same directory name (for example, staging server/ MySite and production server/ MySite). If not, the content may incorrectly reference images in the uploadedfiles directory of the staging server. As a result, the production server displays broken images. Ektron CMS400.NET Site Replication Manual, Version 2.0, Revision 8 17

24 Directions Screen 6. Enter the folder to which the Site Replication files will be installed. If you are unsure, accept the default. 7. Click Yes or No to indicate if the server uses a remote database. That is, a database stored on a separate server. Ektron CMS400.NET Site Replication Manual, Version 2.0, Revision 8 18

25 Directions Screen 8. If your receiving server uses a remote database server, the Site Replication feature uses a temporary folder to store the database prior to replication. A default folder to be used for this purpose appears. You can accept the default or navigate to a different folder on the receiving server. Ektron CMS400.NET Site Replication Manual, Version 2.0, Revision 8 19

26 Directions Screen 9. On the receiving server, enter the path to your installation of the MS SQL Server Data directory. Ektron CMS400.NET Site Replication Manual, Version 2.0, Revision 8 20

27 Directions Screen 10. If you are configuring a receiving server, enter the path to your backups directory. Before new information is pushed from the staging server, production server files are backed up to this directory. See Also: Viewing and Restoring a Backup of the Production Server on page 49 Ektron CMS400.NET Site Replication Manual, Version 2.0, Revision 8 21

28 Directions Screen 11. If you are configuring a sending server, you are prompted to enter a from address. When site replication finishes, the notification uses this as the from address. Note: You can enter a to address on the configuration screen. Ektron CMS400.NET Site Replication Manual, Version 2.0, Revision 8 22

29 Directions Screen Server Field Enter the path to the server that hosts the database. If using a remote database, enter the path to the database server, not the receiving server. Username and Password Fields If using a trusted connection, leave the username and password blank. Otherwise, enter a username and password specific to the database for the receiving and sending server. Ektron CMS400.NET Site Replication Manual, Version 2.0, Revision 8 23

30 Directions Screen 12. Click the Install button to begin the installation. 13. The installation begins. When it is done, the screen on the right appears. Ektron CMS400.NET Site Replication Manual, Version 2.0, Revision 8 24

31 Additional Steps Prior to Configuring the Site Replication Feature If you are not using a trusted connection, the login user defined in the Ektron CMS400.NET web.config file needs sysadmin privileges. The login user is defined in the user tag within the web.config s <connectionstring> element. If you are using a trusted connection, the user running the replication needs sysadmin privileges. If you are using a remote database, configure the MSSQL Windows Service on the remote server to run as one of the following: - a local user whose username/password combination on the Web server matches those settings on the SQL server - a Domain user. To set up a domain user, follow these steps. 1.Open SQL Server Management Studio. 2.Right click the database engine instance. 3.Select SQL Server Configuration Manager. 4.Under the Tree tab of the SQL Server Configuration Manager screen, select SQL Server 2005 Services. Ektron CMS400.NET Site Replication Manual, Version 2.0, Revision 8 25

32 5.In the right panel, select SQL Server (MSSQLSERVER). 6.Right mouse click SQL Server (MSSQLSERVER). 7.Select Properties from the menu. Ektron CMS400.NET Site Replication Manual, Version 2.0, Revision 8 26

33 8.On the SQL Server Properties screen, click the Log On tab. 9.Select This account. 10.Click the Browse button and find a domain user who exists on both the Ektron CMS400.NET and the database server. Ektron CMS400.NET Site Replication Manual, Version 2.0, Revision 8 27

34 Give the user selected above permission to read/write to the SiteReplication.Temp directory. To do so, follow these steps. - Open Windows Explorer. - Right mouse click the c:/sitereplication.temp folder. - Select Properties. - Click Sharing then Permissions. - Assign to the user selected above permission to read and write to this directory. Ektron CMS400.NET Site Replication Manual, Version 2.0, Revision 8 28

35 If you will use to communicate the completion of the replication, SMTP must be running on the sending (staging) server s IIS. Also, the CDO objects must be installed. Mail will be sent from CMS400 Site Replication. Finally, verify that your SMTP server allows relaying from the sending machine. You may need to set the Send\ From tag in the siterepl.config file to a valid internet address. You can use the Send web services API test in replication.asmx to test the configuration. Go to IIS > Default SMTP Virtual Server > Properties > Access tab > Relay button. Make sure the following field is checked: Allow all computers which successfully authenticate to relay, regardless of the list above. Ektron CMS400.NET Site Replication Manual, Version 2.0, Revision 8 29

36 See Also: Updating Membership Users on page 30 Preserving Database Tables on page 31 Updating Membership Users Typically, membership users are site visitors who register themselves via Web pages that reside on a production server. So, you would not want membership information on the staging server to overwrite that information. However, if your staging server contains membership users that you want to move to the production server, follow these steps. You might do this on a one-time basis if, for example before your production server goes live. 1. On the production server, navigate to the folder CMS400 server/ Documents and settings/all users/application data. 2. Open the sitereplcms400replication.config file with a simple word processor, such as Notepad. Ektron CMS400.NET Site Replication Manual, Version 2.0, Revision 8 30

37 3. Set the value of PreserveMembershipUsers to False. <entry name="preservemembershipusers">false</entry> Site Replication 4. Save and close the file. The next time you run Site Replication, all membership user information on the staging server will be sent to the production server. After running the replication, you would typically change the value of PreserveMembershipUsers to True, so that subsequent replications do not affect membership users on the production server. Preserving Database Tables Some customers have a custom set of tables in the production database for tracking unique information. If your site has custom tables that you want to preserve during replication, follow these steps to instruct the site replication to do that. 1. On the production server, navigate to the folder CMS400 server/ Documents and settings/all users/application data. 2. Open the sitereplcms400replication.config file with a simple word processor, such as Notepad. 3. Within the PreserveTables entry, list the tables to be preserved during replication. <entry name="preservetables">my_custom_table_tbl</entry> NOTE If you enter more than one table, separate each with a comma. Since the tables may have foreign key relationships, list the primary key tables first. When the tables are deleted, they are deleted in reverse order, so there are no foreign key errors. When the tables are copied, it is done in forward order so the primary keys are restored before the foreign keys reference them. 4. Save and close the file. Ektron CMS400.NET Site Replication Manual, Version 2.0, Revision 8 31

38 Configuring the Site Replication Feature Site Replication To configure the Site Replication feature, enter the following into your Web browser s address field: Alternatively, follow this path from the Start menu. Start > All Programs > Ektron > Site Replication > CMS400 Site Replication The following screen appears if you chose to set up a receiving machine. The following screen appears if you chose to set up a sending machine. Ektron CMS400.NET Site Replication Manual, Version 2.0, Revision 8 32

39 This screen displays the following Site Replication information: current status the receiving directory the sending directory test configuration This screen also links to other screens that let you configure, run, and get a detailed status of the replication process. Click Configure Send to configure your staging server, and Configure Receive to configure a production server. NOTE Only configure the send page on the staging server, and the receive page on the production server. See Also: Configuring the Receiving Server on page 34 Configuring the Sending Server on page 38 The Site Replication Status Page on page 44 Testing Site Replication Software on page 64 Ektron CMS400.NET Site Replication Manual, Version 2.0, Revision 8 33

40 Configuring the Receiving Server Site Replication Use the configuration receive page to set up information about a receiving server. NOTE To return to the home screen, click Replication in the top left corner. This screen has four secondary screens, listed across the top: Configuration Screen on page 35 Security on page 36 Remote DB on page 37 Backups on page 37 The following table explains the initial screen s fields. Ektron CMS400.NET Site Replication Manual, Version 2.0, Revision 8 34

41 Configuration Screen Field Enable Receive Description Determines whether the server you are signed into can receive Site Replication information. Checked = Receive Not checked = Do not receive Receive Directory The site directory on the receiving (production) server that is updated when Site Replication occurs. For example: c:\inetpub\wwwroot\site root folder Note: If you just installed the Site Replication feature, the receiving directory you specified during installation appears. Multisite Directories MSSQL Data Directory MSSQL Log Directory Backups Directory Save Button If your configuration includes several Web sites, you must set up Site Replication for each Multisite Receive Directory. In this field, insert in a comma-separated list of all other multisite directories. (No spaces are allowed in the list.) The Site Replication feature uses this information to point each web.config file to the same database. The location of the MSSQL database directory. The default is: c:\program Files\Microsoft SQL Server\MSSQL\Data Enter the location of the MSSQL Log directory, which stores your MSSQL.ldf files. The location of the Site Replication backup files. For example: c:\sitereplication.backups The backup directory may require a large amount of space, depending on the size of your site and if you are using the Document Management Functionality. See Also: Viewing and Restoring a Backup of the Production Server on page 49 Saves the receiving (production) server information. Ektron CMS400.NET Site Replication Manual, Version 2.0, Revision 8 35

42 Security Field Valid Username Description Username used for authentication on receiving (production) server. If you are setting up a receiving server that uses a trusted connection, this user needs sysadmin access for MSSQL. Also, this value must match the Username on the Configuration Sending Server screen. Ektron recommends entering the name in this format: domain name\username. Note: You do not need to complete this field. If you do, this information provides additional security for which user can send data to this server. Valid Sender IP The IP address of the sending (staging) server, which will be synchronized with the production server you are configuring. It must be a static IP address. Note: You do not need to complete this field. If you do, this information provides additional security for which server can send data to this server. Save Button Save the receiving (production) server information. Ektron CMS400.NET Site Replication Manual, Version 2.0, Revision 8 36

43 Remote DB Field DB Server s Temp Dir Description Most databases can only back up and restore to a local drive. So if your database server is on a different machine than your CMS, both machines must share a domain/group and a user/password for directory access. Ektron recommends setting up a separate directory named SiteReplication.Temp and sharing it on the staging or production server (whichever uses the remote database server). The database server can connect to this network share via a UNC path. Note: The MSSQL service must run as a domain user to be able to access a UNC share. Receive DB Temp Dir Save Button If the receiving server uses a remote database server, enter the UNC path to the shared directory on that server. See Also: DB Server s Temp Dir on page 37 Save the receiving (production) server information. Backups Field Replication Backups Button Description Displays the number of Site Replication backups stored in the backups directory. See Also: Setting the Maximum Number of Backups on page 50 The selection box directly below this label lists all saved backups. See Also: Viewing and Restoring a Backup of the Production Server on page 49 Choose a backup from the replication backups selection box. Click Restore to replace the site on the receiving server with the selected backup. See Also: Viewing and Restoring a Backup of the Production Server on page 49 Ektron CMS400.NET Site Replication Manual, Version 2.0, Revision 8 37

44 Configuring the Sending Server Site Replication The first time you configure the sending (staging) server, follow the procedure described in Setting up a Staging Server on page 45. Later, you can use the Configure Send page modify that information. NOTE To return to the home screen, click Replication in the top left corner. This screen has these secondary screens, listed across the top: Configuration Screen on page 39 Destinations Screen on page 41 Remote DB Screen on page 42 Notification Screen on page 42 Ektron CMS400.NET Site Replication Manual, Version 2.0, Revision 8 38

45 Configuration Screen Setting up a Staging Server on page 45 The following tables explain the screens. Field Send Directory Exclude Files Delete Removed Files Send DB When Description The location of site directory on the sending server whose content will be synchronized with the production server. For example: c:\inetpub\wwwroot\site root folder If you want to exclude certain file types from the replication, enter them here. For example, you may want to exclude all PDF files. For each file type, enter an asterisk (), period(.), then the file extension. For example *.pdf. Separate each extension with a comma. During Site Replication, files that were deleted on the staging server are now labeled deleted on the production server. Check this box if you want to remove these files from the production server. Indicate if you want to copy the Ektron CMS400.NET database to the named destination servers. Your choices are: Always 1st Destination only (only copy the database to the first destination server listed above) Never Ektron CMS400.NET Site Replication Manual, Version 2.0, Revision 8 39

46 Field Schedule On Description To begin the replication as soon as you press the Send button, leave this field blank. To schedule the replication for a future date and time, click the calendar button and choose a date. To the right of the Schedule On field is a dropdown box that lets you schedule Site Replication to run on a regular basis, such as weekly. If you want to run Site Replication automatically at one of these intervals, select it. See Also: The Scheduler Windows Service on page 69 Destinations Windows Username Password Send Button The path to the replication.asmx file on every production server that will be updated by this staging server. For example: replication.asmx or You must enter the username and password needed to access that folder before pressing the Add button to add a destination folder. Username used for authentication on receiving (production) server. If you are setting up a receiving server that uses a trusted connection, this user needs sysadmin access for MSSQL. Enter the domainname\username. It must match the WS Username on the production server s Configuration Receiving Server screen. Password for the above user. Begin the Site Replication process. If you scheduled a date/time, the process is delayed until then. Ektron CMS400.NET Site Replication Manual, Version 2.0, Revision 8 40

47 Destinations Screen Field Destinations Destination to add Windows Username Password Add Button Preview Changes Button Description A Display-only field that lists the path to the replication.asmx file on every production server that will be updated by this staging server. Enter the path to the replication.asmx file on every production server that will be updated by this staging server. For example: replication.asmx or You must enter the username and password needed to access that folder before pressing the Add button to add a destination folder. Username used for authentication on receiving (production) server. If you are setting up a receiving server that uses a trusted connection, this user needs sysadmin access for MSSQL. Enter the domainname\username. It must match the WS Username on the production server s Configuration Receiving Server screen. Password for the above user. Add a new Destination. See Also: Destinations on page 40 Before pressing this button, make sure that a valid destination appears in the Destinations field, and the username and password needed to access that folder appear in their respective fields. Preview a list of changes to take place when the Site Replication occurs. Use this feature to examine which changes are scheduled before replication begins. Before pressing this button, make sure a valid destination appears in the Destinations field, and the username and password needed to access that folder appear in their respective fields. Then, select a production server from the Destinations field. See Also: Previewing the Site Replication Process on page 46 Ektron CMS400.NET Site Replication Manual, Version 2.0, Revision 8 41

48 Remote DB Screen Field DB Server s Temp Dir Send DB Temp Dir Description Most databases can only back up and restore to a local drive. So, if your database server is on a different machine than your CMS, both machines must share a domain/group and a user/password for directory access. Ektron recommends setting up a separate directory named SiteReplication.Temp and sharing it on the site replication server. The database server can connect to this network share via a UNC path. So, if the sending server uses a remote database server, enter the site replication server s shared directory. If the sending server uses a remote database server, enter the UNC path to the shared directory on that server. Notification Screen Field Notification to Description Use this field to notify someone when the site replication is finished. Enter the address of the person you want to notify. Note: notification only works if the sending server s SMTP mail service is enabled. See Also: If you will use to communicate the completion of the replication, SMTP must be running on the sending (staging) server s IIS. on page 29 Here is an example of the resulting from a successful replication. Completed At 10/7/2005 9:50:26 AM From Address Enter the name that will appear in the s from line. Ektron CMS400.NET Site Replication Manual, Version 2.0, Revision 8 42

49 Make Staging Screen This screen helps you to set up a staging server when only a production server is currently available. The screen facilitates the setup of the staging server by copying Web site and database information from the production server to the staging server initializing the staging server with content from the production server For more information, see Setting up a Staging Server on page 45.. Field New Connection String MSSQL Data Directory MSSQL Log Directory Description Enter a connection string pointing to the new database. Enter the location of the staging server s MSSQL database directory. The default is: c:\program Files\Microsoft SQL Server\MSSQL\Data Enter the location of the staging server s MSSQL Log directory, which stores your MSSQL.ldf files. Temp Directory Windows Username Password Enter the Username used for authentication on receiving (production) server. If you are setting up a receiving server that uses a trusted connection, this user needs sysadmin access for MSSQL. Enter the domainname\username. It must match the WS Username on the production server s Configuration Receiving Server screen. Enter the password for the above user. Ektron CMS400.NET Site Replication Manual, Version 2.0, Revision 8 43

50 Field Description Click this button when you are ready to create the staging server based on the information entered on the screen. Before pressing this button, make sure you completed Setting up a Staging Server on page 45. When you click the Create Staging button, Site Replication copies the site root folder, the assetlibrary directory, and the CMS400 database form the production server to the staging server. The Site Replication Status Page The status page keeps you informed of the Site Replication process. Specifically, it lists the current status of the Site Replication. Also, If a replication is currently in progress, the page displays the percentage of completion the file currently being replicated the destination server s URL Ektron CMS400.NET Site Replication Manual, Version 2.0, Revision 8 44

51 Setting up a Staging Server Follow these directions if you are migrating from a single-server model to a two-server model, that is, a staging and production server. Your current server becomes a production server, and the new server will be a staging server. After purchasing the appropriate licensing and downloading the Site Replication software, follow these steps. WARNING! Only follow these steps to set up a sending server. After that, you can perform Site Replication by following Performing Site Replication on page Install Ektron CMS400.NET on the staging server. Set it up exactly like the production server (for example, all directories must have the same name). NOTE This procedure is described in the Ektron CMS400.NET Setup Manual. During installation, when you are asked to specify Setup Type, choose Minimal. 2. Install Site Replication software on both servers. See Installing the Site Replication Feature on page Follow the steps described in Additional Steps Prior to Configuring the Site Replication Feature on page Configure Site Replication software on the production server according to instructions in Configuring the Receiving Server on page On the sending server, enter the following into the browser address bar: 6. Click the Destinations tab. 7. In the Destinations to Add field, enter the path to the replication.asmx file on the production server. For example: or Enter only one destination. 8. Enter the username and password needed to access that folder. 9. Press the Add button. 10. Click the Configuration tab. Ektron CMS400.NET Site Replication Manual, Version 2.0, Revision 8 45