Migrating to New Versions of Presto
Migrating from 2.7 or earlier versions of Presto to 3.1 uses the new migrate command with some manual migration techniques for extensions to Presto and custom Mashlets. To migrate from version 3.0 to 3.1, see Migrating the Presto Repository from 3.0 to 3.1.
 | in migration topics, the Mashup Server and Presto Repository for your existing version is called the migration source. The Mashup Server and Presto Repository that you are migrating to is called the migration target. |
Migrate Existing Presto Data to 2.7.0. You can only migrate from version 2.7.0 to version 3.1. If you are working with an earlier version of Presto, migrate from that version to 2.7.0 before migrating to 3.1.
Install the new release of Presto. See Installing Presto for instructions.
If you install this release on the same host as your existing Presto version, install the new version in a separate instance of Tomcat and configure the new version with different port numbers.
Then complete configuration for this migration target, including:
If needed, deploy Presto in another application server. See Deploying Presto in Other Application Servers for links to application server deployment topics.
If needed, move the Presto Repository to a database other than the default. See Moving the Presto Repository to a Robust Database Solution for instructions.
Complete any configuration needed to access the Mashup Server.
This may include configuring Presto for a proxy server, configuring Presto to use your LDAP Directory, configuring logging and so on. See User Configuration and Administration and Mashup Server Configuration for links to other configuration tasks you may need to complete.
Complete Preliminary Metadata in the Migration Target. This includes:
Drivers and Datasources: if you have database services in your migration source, you must add the same JDBC drivers and define the same datasources that are used by these services in the migration target before you use the migrate command.
See Managing Data Sources and Drivers for instructions on both these steps.
Local WSDL Files: in some cases, WSDL web services require a local copy of their WSDLs in order to successfully register them. If you have WSDL web services in your source that refer to local WSDL files, you may need to copy these WSDL files to a path that is identical for the migration target to the path used in your migration source.
Custom Extensions: you may have other custom extensions in your migration source that must be manually added to the migration target. This includes things such as EMML macros, custom XPath functions, custom certificate validation classes, or Java and JRuby code used in mashups.
Many of these extensions will not cause problems during migration, but will prevent mashups from running successfully or prevent users from being successfully authenticated. See Migrating Extensions to Presto for details on these tasks.
Migrate Services, Mashups and Basic Mashlets with the migrate command. This tool automates migrating all services, all mashups and basic Mashlets.
Start the Mashup Server for both the migration source and the migration target. For the migration target, see Starting and Stopping the Presto Mashup Server for instructions.
Open a terminal or command window and move to the target-presto-install/prestocli/bin folder.
If you have configured Presto to use your LDAP Directory as the User Repository, enter this command:
migrate presto27 -l sourceURL -u sourceUsername -w sourcePassword -m targetURL -v targetUsername -x targetPassword
To get a log file showing the progress of the migration, add the -p option to this command. This logs the progress and error messages, if any, from the command in the target-presto-install/prestocli/bin/migration.log file.
If you are using the default User Repository, enter this command:
migrate presto27 -l sourceURL -u sourceUsername -w sourcePassword -m targetURL -v targetUsername -x targetPassword -j
The -j option also migrates user and group (or role) data from the source User Repository. You may also need to manually assign built-in user groups in the migration target once users are migrated to grant access to users to work in Presto Hub and register or create artifacts. See Authorization Policies and Permissions for more information.
To get a log file showing the progress of the migration, add the -p option. This logs the progress and error messages, if any, from the command in the target-presto-install/prestocli/bin/migration.log file.
For more information on syntax and troubleshooting, see the Migrate Command topic.
Migrate Custom Mashlets to Apps manually. See Migrating Custom Mashlets to Custom Apps for instructions.