In Configuration Manager, select File > Migrate Legacy Data.
Last updated on
Apr 27, 2021
|
Also applies to RoboHelp Server 10, RoboHelp Server 11
You can migrate context data from Adobe RoboHelp Server 10 to Adobe RoboHelp Server 11.
While migrating, the following data is impacted:
- Published RoboHelp projects
- Information about areas
- Information about users and groups
- User or group permissions on areas
- Usage data and statistics for reports
Note:
Usage data for RoboHelp projects is migrated only if you choose to migrate the corresponding projects.
Note:
While migrating RoboHelp Server 10 analytics data, operating system and browser data is not migrated to RoboHelp Server 11.
Note that Oracle and Microsoft SQL Server databases are not replicated during migration. Instead, the schema for these databases is updated, such that it becomes compatible with RoboHelp Server 10. Once the database schema has been updated, the database can no longer be used with the previous RoboHelp Server versions.
During migration, you can choose the contexts whose data you want to migrate to RoboHelp Server 11. For example, you can choose to migrate data for production contexts while not migrating the data for transient or test contexts.
Note:
You can migrate data for only RoboHelp Server 10 contexts to RoboHelp Server 11. Migration from earlier RoboHelp Server versions is not supported. Also, if you are migrating data from MS Access, then you must have MS Access runtime libraries installed on the machine where RoboHelp Server 11 is deployed.
Follow the steps given below to migrate data from RoboHelp Server 10 to RoboHelp Server 11:
-
RoboHelp Server Migration settings RoboHelp Server Migration settings -
Browse and select the RoboHelp Server 10 installation path. Specify a network path if RoboHelp Server 10 is installed on a machine different from the machine on which you’re installing RoboHelp Server 11.
-
In the Contexts area, select one or more contexts to migrate.
Note:The existing contexts in RoboHelp Server 10 are displayed in the existing RoboHelp Server 10 Contexts box. If you choose to migrate a context with the same name as an existing context, all data in the existing RoboHelp Server 10 context is overwritten.
-
Specify the following Database details:
- Database URL - The URL of the database to which the content is to be migrated
- Database Username - The Username required to log into the database
- Database Password - The Password required to log into the database
- JDBC Driver Class - The JDBC Driver class
- JDBC Driver Path - The JDBC Driver path
-
Specify the following Migration Settings:
- Migrate All Projects - Migrate all RoboHelp projects published to the selected context
- Migrate Usage Data - Migrate project usage data and statistics along with the projects
- Migrate All Users or Groups And Their Permissions - Migrate information about users or groups and their permissions
-
Specify the Server URL in the format http://<server-name>:<port-number>/<context-name>/server.
-
Click Start Migration.
Note:If the migration of one or more contexts fails, RoboHelp Server continues migrating the other contexts that you selected in Step 3.
-
Review the Migration Log. When migration is complete, click OK.
Note:If RoboHelp Server 10 is installed on a machine different from the machine on which you are installing RoboHelp Server 11, re-create the settings for Oracle or Microsoft SQL Server database management systems.
-
Close the Configuration Manager window. RoboHelp Server automatically restarts the Tomcat service.
For migration from RoboHelp Server 9 to 10, see Migrate context data from RoboHelp Server 9 to RoboHelp Server 10.