Rehosting
Rehosting is the process by which data is migrated from one server to another. This section provides an example of how to move data from a monolithic environment to a split configuration, or cluster environment.
To rehost a server the following must be done:
• Before you begin, a cluster or split configuration environment must be configured.
• The Publisher must be migrated from the monolithic server, to the hosting server.
• The Publisher must be configured, by running the DeployFamily command.
• Data must be migrated from the monolithic server to the cluster or split configuration Viewers.
Before You Begin Rehosting
Before you begin this procedure ensure the following:
• There are no Servigistics InService tasks running, queued, paused, or in a failed state.
• There exists a monolithic system with data to be moved.
• There exists a previously configured cluster or split configuration server, with no data on it.
Migrating the Publisher
To migrate the Publisher from the monolithic server to the cluster or split configuration Publisher use the following procedure:
1. Copy the entire Global file system from the monolithic server to the cluster or split configuration Publisher. This directory can be found by navigating to data/Storages/Global/.
2. Copy all <FamilyName>_TR directories to the cluster or split configuration Publisher. This directory can be found by navigating to data/Storages/.
3. Export the following E3C schemas to the Publisher:
◦ TN_CM_SOURCES
◦ TN_CM_FOLDERS (first delete existing content)
◦ TN_CM_ADMIN_TREE
◦ TN_CM_FEED
◦ TN_GN_SEQUENCES
◦ SC_IDENTITY
◦ SC_REGISTRY
◦ SC_RELATIONS
4. Navigate to config/System/config/ and copy PublicationList.xml to the cluster or split configuration Publisher.
5. Navigate to config/System/config/ and copy ProfileDefinitions.xml to the cluster or split configuration Publisher.
6. Copy the following directory to the new cluster or split configuration Publisher: work/Application/ContentManger/Work/Profiles.
7. Restart the Publisher.
Configure the cluster or split configuration Publisher
Following the migration of the Publisher you must configure the cluster or split configuration Publisher by using the following procedure:
1. Bring up the new Publisher and all Viewers.
2. Run DeployFamily for all families that you copied to the Publisher.
Migrating Data to the Viewers
To migrate data to the cluster or split configuration Viewers use the following procedure:
1. On each Viewer delete all content from the Storages directory.
2. From the monolithic server copy all data from Storages/<SegNumber>/directory to the same directory on the cluster or split configuration Viewers, with the exception of the following directories, which should NOT be copied:
◦ Global
◦ *_TR
3. On each Viewer delete all content from the following Core directories.
◦ Core/{Viewer1-hostname}/coreServer-1
◦ Core/{Viewer1-hostname}/coreServer-2
4. From the monolithic server copy the following directories to the same directory on the cluster or split configuration Viewers:
◦ <Servigistics InService>/data/Titles/<segName>_<number>/Data/Cor
◦ <Servigistics InService>/<segName>_Secondary_<number>/Data/Core
5. On the CMI database delete the contents of the following tables from the monolithic server and then copy them to cluster or split configuration Viewers:
◦ TN_CM_SOURCES
◦ TN_CM_FOLDERS
◦ TN_CM_ADMIN_TREE
◦ TN_CM_FEED
6. On the E3C database delete the contents of the following tables from the monolithic server and then copy them to cluster or split configuration Viewers:
◦ TN_GN_SEQUENCE
7. Migrate the entire TitanDB and TitanDB2 databases from the monolithic server to cluster or split configuration Viewers.
8. Restart the Viewers.
9. Migrate Windchill schema from the monolithic server to cluster or split configuration Viewers.
Rehosting a Monolithic Installation on the Same Path
1. Install Servigistics InService in the same target location as the source server.
2. Backup and restore the database from the source to the target.
3. Apply all customizations.
4. Copy the InService Data folder from the source to the target server.
5. Reconfigure standalone-full.xml and db.properties to point to the target database.