[ 
https://issues.apache.org/jira/browse/JS2-1127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Randy Watler resolved JS2-1127.
-------------------------------

    Fix Version/s: 2.2.1
                   2.2.0
       Resolution: Fixed

SVN commit 942663

Bulk migration database tool and installer integration.
- uses JDBC and minimal heap configuration to migrate jetspeed database 
instances.
- migration from 2.1.3, 2.1.4, 2.2.0 to 2.2.1 schemas, (including SSO and 
DBPSML data).
- converts portlet names, layout decorators, and portlet decorators as part of 
the migration.
- new stand-alone installer migration option supported: prompts for source and 
target database connection configuration.
- can convert from any supported database to another, (e.g. from MySQL to 
PostgreSQL).
- Derby migration not supported at this time in the installer front end.


> Bulk Migration from 2.1.X to 2.2.X
> ----------------------------------
>
>                 Key: JS2-1127
>                 URL: https://issues.apache.org/jira/browse/JS2-1127
>             Project: Jetspeed 2
>          Issue Type: New Feature
>          Components: Import/Export
>    Affects Versions: 2.1.3, 2.1.4, 2.2.1
>         Environment: 2.1.3-POST-RELEASE and 2.1.4 to 2.2.1 DBPSML
>            Reporter: Randy Watler
>            Assignee: Randy Watler
>             Fix For: 2.1.3, 2.1.4, 2.2.2, 2.2.1, 2.2.0
>
>
> Implement bulk data migration scripts and/or processes to migrate DBPSML 
> based installations from 2.1.X to 2.2.X. Special considerations must be given 
> to large numbers of users, user customized pages, and preferences on minimal 
> memory footprint JVM environments, (i.e. 32 bit 2G heaps).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscr...@portals.apache.org
For additional commands, e-mail: jetspeed-dev-h...@portals.apache.org

Reply via email to