ektron esync manual

File Name:ektron esync manual.pdf
Size:4405 KB
Type:PDF, ePub, eBook, fb2, mobi, txt, doc, rtf, djvu
Category:Book
Uploaded20 May 2019, 16:36 PM
InterfaceEnglish
Rating4.6/5 from 586 votes
StatusAVAILABLE
Last checked8 Minutes ago!

ektron esync manual

From single sites, global multi-sites, and server farms, eSync provides scalable, geo-synchronization capabilities that let you easily update exactly what you want, when you want to update it. Also, your updates can take place on the safe side of your firewall before being moved to the live site. Within complex IT infrastructures, eSync can synchronize content, asset an external file, such as a Microsoft Word document or image, stored in one of these Ektron siteroot folders: assets, privateassets, uploadedfiles and uploadedimages. An asset can be managed like native Ektron content.With its intelligent synchronization technology, eSync securely moves selected content bidirectionally: Web 2.0 sites have a wealth of user-generated content and membership information which can be synchronized back to the development side of the firewall. To track changes to Ektron data between syncs, eSync creates a c:\sync folder structure that mirrors your site’s Windows folder structure. This structure is created on each server when sync relationships are first established. No Ektron files reside in the \sync folders. Instead, each folder has four.sync files that monitor changes to Ektron files in the corresponding folder. Adjusting Relationship Settings explains how to sync content dependencies. You also can schedule time-sensitive events. The version that isn’t posted is saved in a history log (along with other previous versions), letting you track changes or restore if necessary. As your developers change the site, their updates can by synchronized to the staging and production servers.The originating server is 1, the first server with which it establishes a relationship is 2, and so on. The server number is stored in the c:\sync\serverinfo XX.xml file. Examples are content (see illustration), folders, menus, users, and so on. This prevents collisions when synchronizing between servers.http://www.dostrojar.sk/UserFiles/daikin-vrv-system-design-manual.xml

For example, since membership users created on a production server have a different ID number range from those created on the staging server, eSync does not overwrite them. An Ektron base installation file (for example, cms400Base9x.exe ). Use to install a second site with which to sync your current site. Ektron licenses that support Enterprise or Professional with eSync on every server being synchronized. Matching security certificates on every server being synchronized. See also: Managing eSync Security Certificates.See also: Defining Roles.The screen lets you establish a sync relationship between 2 websites, then specify any number of sync profile a collection of eSync information to be reused, such as: files to be synched, direction, source and destination databases, and schedule.Alternatively, you can sync content or folders. See also: Synchronizing Content and Folders. You can only initiate a sync from a server inside the firewall because an outside server does not know the address of servers inside the firewall. However, your staging server can push to and pull from a production server. This is not configurable. Each server has a database and one site. See also: Initializing a New Site. Developers can use it to create new features and modify existing ones. When they are done, they can sync changes to the staging server, where they can be verified before being moved to production. Servers, One Staging, One Production Server An asset can be managed like native Ektron content.Another profile syncs the staging server’s Workarea files with the production site server. The preproduction server can be used for review and testing of changes before they are moved to production. As an alternative, you could have a separate server for each production database, with all sites on one production server. After the servers are synchronized, one is the staging server, the one on which content is created or updated, then published.http://riolisboa.com/images/ul_files/qFryJ9kR0LdX.xml

Another server, production, hosts your live website. This is because paths to images, XSLT Extensible Stylesheet Language Transformations files, and so on, refer to a site and its folders. If the names do not match, the links break. Afterward, use eSync to periodically sync updated content, folders, users, menus, and so on. See also: Installing Ektron. Check the radio button next to Generate Certificates. Click Generate. Do not install one site to a physical folder relative to the root folder and the other site to a virtual directory. Right click and choose Run As Administrator. Right click and choose Run as Administrator. The security configurator screen appears. —Image— Next, use eSync to upload your Ektron site from the local to the remote server. After the you complete the initial and template syncs explained in this chapter, the 2 sites are mirror images of each other. Do not install one site to a physical folder relative to the root folder and the other site to a virtual directory. In this part, you generate security certificates on the local server, then copy them to the remote. If you completed that screen, skip steps 2 through 6. Right click and choose Run As Administrator. Right click and choose Run as Administrator. Name the folder local security certificate.The Security Configurator screen does this. Right click and choose Run As Administrator. Right click and choose Run as Administrator. To accomplish this, repeat the steps in Part 2: Generate and Copy Security Certificates, but this time, treat the remote server as the local server and vice versa. This screen appears. —Image— The remote server appears in the Choose Certificate field. A screen appears, showing both servers. The screen indicates that the database will be uploaded from your local server to the remote server. A screen tracks the progress. —Image— An asset can be managed like native Ektron content.In both cases, you use a tool other than eSync for the initial copy.

From then on, use eSync to sync your servers. For example, if the original database is backed up from staging and restored on production, the license key in the database may be for the Staging.abc.com domain. But, on the production server, you need a production domain key, such as abc.com. See also: License Keys. To copy asset files between servers quickly: The Add Synchronization Profile screen appears. —Image— When it is complete, Synchronization is Complete appears. You can use the template profile a collection of eSync information to be reused, such as: files to be synched, direction, source and destination databases, and schedule.Consider that your production server and use it to initialize the staging and development servers. The sync can only be run between Development and Staging or Staging and Production. Do not install one site to a physical folder relative to root and the other sites to virtual directories. In an eSync relationship, every server needs a security certificate from every other server. If you completed that screen, skip steps 2 through 4. Right click and choose Run as Administrator. Name the folder Prod security certificates.The Security Configurator screen does this. Right click and choose Run As Administrator. The security configurator screen appears. To do this, begin at Step 6 and follow all steps. Wherever the instructions mention a staging server, substitute the development server. If you completed that screen, skip steps 2 through 4. Right click and choose Run as Administrator. Name it staging security certificates.The Security Configurator screen does this. Right click and choose Run As Administrator. Where the instructions mention a production server, substitute the development server. If you completed that screen, skip steps 2 through 4. Right click and choose Run as Administrator. Name the folder Dev security certificates.The Security Configurator screen does this. Right click and choose Run As Administrator.

Right click and choose Run as Administrator. To do this, begin at Step 6 and follow all steps. Wherever the instructions mention a staging server, substitute the production server. The View All Synchronization Configurations screen appears. —Image— That screen appears. —Image— A new screen appears showing the production server's database. —Image— A screen tracks progress. —Image— The Add Synchronization Profile screen appears. A screen tracks the sync’s progress. —Image— You can reuse the template sync profile in the future. The View All Synchronization Configurations screen appears. —Image— After you connect to the staging server, a new screen appears showing its database. —Image— A screen tracks the sync’s progress. —Image— The Add Synchronization Profile screen appears. A screen tracks the sync’s progress. —Image— You can reuse the profile to sync templates in the future. After you enter specifications once, select the profile to sync again using the same details. A profile contains the following information: This section explains how to modify those profiles and create new ones. To create a profile for See also: Setting up a Profile to Sync Workarea Files. See also: Setting up a Profile to Sync Template and Bin Files. This is because, when 2 templates have the same name, the most recently-modified one overwrites the other. To avoid this, rename the only template installed with the min site (login.aspx) before performing the initial template sync. You should also rename login.aspx’s supporting files, such as login.aspx.vb. See also: Setting Up eSync. See also: Synchronizing a Package. The Add Synchronization Profile screen appears. To define a Scope, continue through the steps. To define a Local Package, see Synchronizing a Package. After selecting the package, you still choose a Synchronization Direction, Conflict Resolution Policy, and a Schedule. The following list describes the database scope filter checkboxes.

Database scope filters Use these checkboxes to choose groups of database tables. If you have a license to eCommerce, you will continue to receive support, but if you need to upgrade, contact your account manager for options.Lets users on the destination server review content changes (edited, published, and so on). ASP.NET —Microsoft.NET ASP provider Search —tables to support search functionality: Using Synonym Sets Providing Suggested Results Including External Files in Your Search Custom —Custom tables (if defined) See also: Synchronizing Custom SQL Database Tables. Notification —Notification activities See also: Sending Notifications to a Community. User Generated Content —Content created by membership users and other site visitors. For example: A membership user logs in and creates a new account A site visitor rates content Community members reply to forum questions and blog posts A Community member creates a community folder Whenever user-generated content is synchronized, the profile of the user who created the content is also synchronized. User-generated content is a subset of CMS Core, so you would not choose both for the same sync. But you may select user-generated content with any other scope. When you set up a sync profile for user-generated content, you typically choose Bidirectional as the direction. In this case, if a membership user updates his or her profile on the production server, eSync copies the changes to staging. On the other hand, if your administrator changes that information on staging, the next eSync copies it from staging to production.Your choices are: Bidirectional —Changed data on either server is updated on the other. See also: Choosing a Bidirectional Sync. Upload —database is copied from the local server (the one to which you signed on) to the remote server (specified at the Remote Site field above). Items on the remote server are overwritten. Download —database is copied from remote to local server.

Items on the local server are overwritten. Your choices are: Version on Remote Site Wins Version on Local Site Wins Effect of choosing a conflict resolution policy Effect of Choosing Conflict Resolution Policy If the synchronization direction is Bidirectional and you choose Version on Remote Site Wins, the remote version overwrites local version and you choose Version on Local Site Wins, local version overwrites remote version If the synchronization direction is Upload and you choose Version on Remote Site Wins, the remote version is retained; nothing is copied and you choose Version on Local Site Wins, the local version overwrites remote version If the synchronization direction is Download and you choose Version on Remote Site Wins, the remote version overwrites local version and you choose Version on Local Site Wins, local version is retained; nothing is copied The choices are None —Don’t set up a schedule. One Time —specify a start time and date. Hourly —specify a start minute. The profile runs every hour at this minute. Daily —specify a start time. The profile runs every day at this time. Weekly —specify a start time and weekday. The profile runs on this day every week at this time. Monthly —specify a start time and calendar day (numbers 1 through 31). After the start date, the profile runs on this day every month at this time. For example, if you enter 31, the sync will not run in February, April, June, September, and November. If you check the Exclude button, and enter widgets into the Directories field, eSync ignores them. An asset can be managed like native Ektron content.Here, you can select individual files. If you included files types, only they are available for selection. If you excluded file types or directories, they are unavailable. An asset can be managed like native Ektron content.Also, you can predict how long a sync will take, because the preview takes the same amount of time. See also: Viewing eSync Activity. So, at 10:50 a.m.

, the sync does not run. The next sync starts at 12:50 p.m. This information can be viewed and edited on the staging server. Here are some examples: So, if a membership user updates his or her profile on the production server, eSync copies the changes to staging. On the other hand, if your administrator changes that information on staging, the next eSync copies it from staging to production. The choices are: All servers in an eSync relationship must have matching, encrypted security certificates to establish an eSync relationship. You only need to install certificates on servers that host Ektron. Then, you copy the client certificate to the other servers in the relationship. The local machine’s server certificate must match a client certificate on the remote server, and vice versa. After that, any eSync activity triggers a background check, and you can only proceed if certificates match. You determine this when installing them. Check marks indicate the certificates. You can also delete all certificates for a server. You cannot remove them from the server to which you are logged in. Your server's security certificates appear. —Image— The eSync checkbox (second from the top) is only accessible if your license key contains an eSync modifier. —Image— Right click and choose Run as Administrator. —Image— Generate Certificates —Use this screen area to create security certificates that must be copied to a remote server with which you want to sync. Site Name —If more than one site is installed on this server, use the pull-down list to select the website for which you are installing security certificates. Or, click All to apply certificates to all sites on the server. Apply Remote Server Certificates —Use this screen area to apply security certificates that were copied from a remote server to your local server. See also: Step 3: Copy Local Client Certificate to Remote Server. The status field at the bottom of the screen updates as it progresses.

If you click OK more than once, you delay the certificates’ creation. The folder name is not important.After you copy the local server’s security certificates to the remote server, they need to be registered and moved to the correct folders. The Security Configurator screen does this. Right click and choose Run as Administrator. You would do this if they stop working, or you are concerned about a security breach. Right click and choose Run as Administrator. See also: Step 1: Create Security Certificates on Your Local Server. This action creates new security certificates on your server. This is explained in Step 3: Copy Local Client Certificate to Remote Server. To resolve this, see Regenerating Security Certificates. You define DXH endpoints in your site’s web.config file. error indicates that The default is 32 MB. You can change it to any size up to the amount of RAM in your eSync server. Auto detect: Try to connect using TCP. If successful, the mode is switched to direct. Otherwise, the mode is proxy. Auto detect is the default. Proxy: Use Windows Communication Foundation (WCF) service. Direct: Direct SQL Connection (direct TCP connection used instead of WCF connection) The commit occurs after the data reaches this size. The default value is false because Azure does not support encryption. You should only check this box if you are using eSync in an on-premises environment. See also: Backing up the Destination Server During an eSync. See also: Determining which Collisions are Resolved. This is because paths to images, xslt files, and so on, refer to a site and its folders. If the servers’ site and folder names do not match, the links break. See also: Managing the eSync Queue. The following topics explain eSync features that you control via the.config files. If you have a license to eCommerce, you will continue to receive support, but if you need to upgrade, contact your account manager for options. An asset can be managed like native Ektron content.

To disable eSync's asset sync: Set up your replacement tool to do that. The settings are: If PDB files are present in the EWS folder or it is a DEBUG build, this value is set to 1. Setting this value to 2 works as in version 8.5. This list determines if a content item being synchronized is an image. If true, a thumbnail is also synchronized. If this value is BLANK, no thumbnails are synchronized while synchronizing dependent images (including the file sync retry and content dependency sync). Zero (0) indicates that all dependencies are evaluated, regardless of the number of recursions necessary. If you enter a number more than zero, EWS only evaluates as far as the specified depth. Ensure that BOTH the local and remote server has enough resources to handle normal load if the number of MaxNNumberOfParallelThreads processors run at 100% CPU. If set to False, files specified in metadata are not synchronized during a content sync. Default value is True. This means that if a content's metadata or HTML references other content blocks, their dependencies are also evaluated and synchronized. Default value is True. See also: Resource Selector, Creating and Deploying a Related Content Definition. This process starts 5 minutes after the service starts. Default value is 5. Default value is 5. You should increase this value if you have an adequate CPU resources to significantly improve performance. Ensure that both the local and remote servers have enough resources to handle normal load if the number of MaxNumberOfParallelThreads processors run at 100% CPU. This is set to false by default because file hash mode can fail when the file is locked for reads. You cannot sync from a production server outside the firewall to other servers—you can only sync to this production server. To sync a profile a collection of eSync information to be reused, such as: files to be synched, direction, source and destination databases, and schedule.See also: Managing the eSync Queue.

Instead, you want to reinitialize the test server from your current Ektron server. To accomplish step 3, use the Force Initial Sync button. The button only appears when all of these conditions are present. The site is not part of a multi-site relationship. The server has only one sync server relationship. The server is the destination (that is, on the download side) of the sync server relationship. The following image illustrates the last 2 conditions. —Image— If you do and problems occur during the sync, the database is restored to its pre-backup state. You can specify the backup to occur on the initial sync only, or every time you sync. See also: Synchronizing Content and Folders, Synchronizing a Package. Before initial sync —Run backup before the initial sync only. Before each sync —Run backup before each sync. The user account that runs the Ektron Windows Service must have read and write permission to the folder. An example of folder modification is the assignment of a new metadata value. You must also run a full sync for all other sync profiles that use those tags or taxonomy a content-level categorization system that uses one-to-many relationships (such as Ronald Reagan is to Actor, Governor, and President) to create a scalable organization of content. A taxonomy lets your site visitors navigate content independent of the folder structure. categories. See also: Tagging Content, Library Items, Users, and Groups with Keywords. The sync also copies all entities on which the content is dependent, such as Select the appropriate one. —Image— See also: Managing the eSync Queue. It does not affect content in folders underneath the selected folder. See also: Synchronizing Content and Folders. A screen asks you to select a sync profile a collection of eSync information to be reused, such as: files to be synched, direction, source and destination databases, and schedule.. —Image— See also: Managing the eSync Queue.

To do this, you must create the custom table on all servers.The table must have a primary key and cannot use identity columns. Create table foo3(Id int not null primary key clustered, The Manage Custom Table Configurations screen appears. Select it to sync custom tables. Advantages of a sync package include: A sync package, on the other hand, includes modifications to parent objects. So, a package can sync content and folders whether or not a parent folder’s properties were edited recently. After assembling the items into a sync package, you can sync it from development to production at any time without affecting other site files. There is no submit button. Click Save Package to save all items in a package. Use the Show drop-down to display only objects of a selected type. —Image— Use Delete () to remove items. You can also remove an item by clicking its tab and unchecking it there. If you choose a taxonomy a content-level categorization system that uses one-to-many relationships (such as Ronald Reagan is to Actor, Governor, and President) to create a scalable organization of content. A taxonomy lets your site visitors navigate content independent of the folder structure., menu, or collection a list of Ektron content links for display on a Web page., only the top-level object appears on the Package Contents tab. However, all child objects (taxonomy categories, submenus, and so on) and all assigned content, users and groups are synchronized with the package. If you have a license to eCommerce, you will continue to receive support, but if you need to upgrade, contact your account manager for options.If you select a folder, the package includes its content in all languages at the time the package sync is run. If you view a folder, its content is checked and grayed out. This indicates that the package includes the folder's content. —Image— Folder selection is not recursive. So, you must select each child folder.

Do not choose those inserted into selected content, since they are automatically included. All folder attributes (described in Content and Folders, above) apply to library folders. You cannot select categories within them. By selecting a taxonomy, you also add the following to the package all categories below it all content, users and groups assigned to the taxonomy and its categories As a taxonomy's content changes, the package automatically includes the current files.You cannot select submenus. By selecting a top-level menu, you also add to the package all of its submenus all items assigned to the menu and its submenus: content, library assets, hyperlinks, and additional submenus As a menu's content changes, the package automatically includes the current files. Folders assigned to menus are not synchronized with them. See also: Assigning a Folder or Template to a Menu.As a collection's content changes, the package automatically includes the current files. This lets you re-use the packages on other servers in your eSync relationship. Other package definitions do not include objects assigned to them (content, folders, and so on). You must verify matching folder structures on both servers before beginning a package sync. See also: Creating a Package. The Add Synchronization Profile screen appears. See also: Managing the eSync Queue. A profile is added to the queue in FIFO order (first in—first out) if a sync process is running when you try to sync a profile. The queue screen lets you So, you should carefully consider hardware resources when using the eSync queue in a hosted environment. If you want to sync a removed profile at a later time, return to the View All Synchronization Configurations screen and click Sync () again. Run the initial sync for one See also: Initializing a New Site. View information about Delete Create View and edit Sync a profile See also: Running eSync. Delete If the column contains a check mark, the sync was successful.

Ektron support can use this log to troubleshoot the problem. If you have a license to eCommerce, you will continue to receive support, but if you need to upgrade, contact your account manager for options. products If you have a license to eCommerce, you will continue to receive support, but if you need to upgrade, contact your account manager for options.To avoid confusion, eSync appends a number to the more recently-created item. For example, the Marketing folder becomes Marketing11329. This is an example of a resolved collision. If the eSync direction is download, the collision resolution information appears on the local server; if upload, it appears on the remote server; if bi-directional, it appears on both servers. If you click Resolve, the following button appears on the toolbar. Upon viewing it, you should notify appropriate content authors, who may want rename the items. You will need to use this new username the next timeTo learn about editing it, see Translating the Workarea. Unchecked items are ignored. When activity that might cause collisions occurs, you may temporarily enable checkboxes. Then, disable them again once the activity is complete. You can also use the Performance Counter to debug and monitor the EWS. If the counter's values stop changing, nothing is happening. This information can help you determine that it is safe to stop the service. Peer Server —The other server(s) in a sync relationship. A continual increase indicates a problem. This may occur if, for example, a file is locked. This number always increases, never decreases unless someone restarts the EWS Ektron Windows Service. This is incremented before change detection begins for that folder. This may occur if, for example, a file is locked This number should never be zero (0) on the destination server while a sync is running. FE Sync failure(s): Enable if you want an email notification to be sent if an FE sync failure occurs.

All completed sync(s): Enable if you want an email notification to be sent when a sync completes. Recipient email addresses: Specify the email addresses of notification recipients.Here, set the SMTP information for sending email. See Balancing the Load on Your Servers. Note that if a separate database server is outside the load balance cluster, eSync only synchronizes documents and files used by the search among the clustered servers. It does not touch the database. The following illustration shows a typical load balanced cluster. If you run a download sync on S2, you also need to run an upload sync to push the file to P2, which will then Load Balance with P1. In this example, since you changed the file on S1, if you initiate a sync from S1, it will be automatically updated on S2, P1, and P2. If Ektron is already installed on one server, install a minimum site on the others. To do this, run the Ektron base installation file (cms400Base9x.exe). See also: Installing the Ektron Base. See also: Managing eSync Security Certificates. Right click and choose Run as Administrator. See Managing eSync Security Certificates. Select the Generate Certificates radio button. Click the Generate button then click OK when the Ektron Windows Service’s warning dialog appears. This action creates security certificates for your server and applies them to all the sites on the server. Optionally, you can select a single site from the Web Site Description drop-down to install certificates to a selected site. Then, click OK when the Ektron Windows Service warning dialog appears. When you sync with the production sever, the Load Balance feature pushes those files to the other servers in the LB configuration. That is, you cannot set up a eSync relationship in a single-site environment and then later change to multi-site. You can set up a new relationship at any time. See also: Supporting Multi-Site Configurations.