Development of EPiServer solutions often occur on a development machine and then need to be migrated across to a depoyment machine. This section describes how this process relates to the topic map information and the EPiServer Module related configuration.
We do not cover the entire EPiServer project migration process as this is something covered by EPiServer. What we describe is the steps that are needed to ensure that the topic map, once migrated, continues to work correctly.
As with any complex data operation it is suggested that all TMCore and EPiServer data is backed up before carrying out this operation.
|1.||Ensure that EPiServer, TMCore and the EPiServer module are correctly installed on the deployment machine.|
|2.||When migrating the EPiServer data it is of course important to ensure that all the page types and any dynamic properties are moved across as well as the page data itself. Using the standard EPiServer Data Export is sufficient for this.|
|3.||Migrating the Topic Map from one TMCore database to another is best done by performing an XTM export and then an XTM Import. This can be done via the TMCore TMEditor web application or the TMCore command-line tools.|
|4.||Once the EPiServer data and the topic map have been migrated it is necessary to run the consistency checker tool to ensure that all local page IDs correspond to the topic that represents them in the topic map. Failure to do this will result in the PageId occurrence on all page topics being incorrect. This will manifest itself as errors in the OneHop and TwoHop controls.|
An alternative to doing an EPiServer export and import, and a XTM import and export, is to move the entire database onto the deployment server. In this case the consistency checker does not need to be run as all of the EPiServer page ID's remain the same.