You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by "Randy Watler (JIRA)" <je...@portals.apache.org> on 2010/04/24 17:27:50 UTC

[jira] Resolved: (JS2-1189) Jetspeed installer does not seed database when selecting "Initialize Jetspeed Portal Database"

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

Randy Watler resolved JS2-1189.
-------------------------------

    Resolution: Not A Problem

The initialize database installer option is not intended to seed the database. The goal of this option is to prepare the target database to import previously exported seed data. The intent was to use these data manipulation installer operations like this:

1. Export the portal configuration using either the administrative portlets or the installer's export operation.
2. Initialize the target database using the installer's initialize database operation.
3. Import the exported portal configuration using the installer.

While your workaround is fine for a default configuration, these options are primarily for ETL migration of installed portals with heavily customized/extended configurations. Using the default seed data is often not appropriate in these cases.

See http://portals.apache.org/jetspeed-2/guide-etl-migration.html for more information.

> Jetspeed installer does not seed database when selecting "Initialize Jetspeed Portal Database"
> ----------------------------------------------------------------------------------------------
>
>                 Key: JS2-1189
>                 URL: https://issues.apache.org/jira/browse/JS2-1189
>             Project: Jetspeed 2
>          Issue Type: Bug
>          Components: Installer
>    Affects Versions: 2.2.1
>            Reporter: Chad Montgomery
>            Assignee: Randy Watler
>            Priority: Minor
>
> Database is seeded correctly when using the "Install Jetspeed Portal" option but the "initialize jetspeed portal database" option did work as expected. It did drop and recreate the database but the seed script does not appear to have been run. I believe it has to do with the new demo/minimal and jetui/classic options. I am using Oracle 11g database (ojdbc6-11.2.0.1.0.jar for the driver). As a work around I have been running the installer with the "Install Jetspeed Portal" option and configuring the oracle connection there. Once the installer finishes i just blow away the installation directory. 

-- 
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-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org