Added: portals/site/jetspeed/jetspeed-2.3/src/site/xdoc/guide-migration.xml URL: http://svn.apache.org/viewvc/portals/site/jetspeed/jetspeed-2.3/src/site/xdoc/guide-migration.xml?rev=1691449&view=auto ============================================================================== --- portals/site/jetspeed/jetspeed-2.3/src/site/xdoc/guide-migration.xml (added) +++ portals/site/jetspeed/jetspeed-2.3/src/site/xdoc/guide-migration.xml Thu Jul 16 21:01:09 2015 @@ -0,0 +1,949 @@ +<?xml version="1.0"?> +<!-- + Licensed to the Apache Software Foundation (ASF) under one or more + contributor license agreements. See the NOTICE file distributed with + this work for additional information regarding copyright ownership. + The ASF licenses this file to You under the Apache License, Version 2.0 + (the "License"); you may not use this file except in compliance with + the License. You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. +--> +<document> + <properties> + <title>Migration Guide</title> + <subtitle>Migration Guide</subtitle> + <authors> + <person name="David Sean Taylor" email="[email protected]" /> + <person name="Ate Douma" email="[email protected]" /> + <person name="Randy Watler" email="[email protected]" /> + </authors> + </properties> + <body> + <section name="Data Migration from Jetspeed 2.2.2 to 2.3.0"> + <p> + No data migration is necessary from version 2.2.2 to 2.3.0. + </p> + </section> + + <section name="Data Migration from Jetspeed 2.2.1 to 2.2.2"> + <p>The following tables describe database schema changes from version 2.2.1 to version 2.2.2.</p> + <p>Note: besides the below modifications, there are a few renames of index and foreign key names + for naming consistency reasons only, which can be ignored and are not mentioned in the below tables either.</p> + + <subsection name="Dropped Foreign Keys (and their Indexes)"> + <table> + <tr> + <th>Table</th> + <th>Foreign Key</th> + </tr> + <tr> + <td>CUSTOM_PORTLET_MODE</td> + <td>FK_CUSTOM_PORTLET_MODE_1</td> + </tr> + <tr> + <td>CUSTOM_WINDOW_STATE</td> + <td>FK_CUSTOM_WINDOW_STATE_1</td> + </tr> + <tr> + <td>EVENT_DEFINITION</td> + <td>FK_EVENT_DEFINITION_1</td> + </tr> + <tr> + <td>PA_METADATA_FIELDS</td> + <td>FK_PA_METADATA_FIELDS_1</td> + </tr> + <tr> + <td>PD_METADATA_FIELDS</td> + <td>FK_PD_METADATA_FIELDS_1</td> + </tr> + <tr> + <td>SECURITY_ROLE</td> + <td>FK_SECURITY_ROLE_REF_1</td> + </tr> + <tr> + <td>USER_ATTRIBUTE</td> + <td>FK_USER_ATTRIBUTE_1</td> + </tr> + <tr> + <td>USER_ATTRIBUTE_REF</td> + <td>FK_USER_ATTRIBUTE_REF_1</td> + </tr> + </table> + </subsection> + <subsection name="Dropped Indexes"> + <table> + <tr> + <th>Table</th> + <th>Index</th> + </tr> + <tr> + <td>PROFILE_PAGE_ASSOC</td> + <td>UN_PROFILE_PAGE_1</td> + </tr> + </table> + </subsection> + <subsection name="Added Columns"> + <table> + <tr> + <th>Table</th> + <th>Column</th> + <th>Type</th> + <th>Required</th> + </tr> + <tr> + <td>PORTLET_DEFINITION</td> + <td>CLONE_PARENT</td> + <td>VARCHAR(80)</td> + <td>false</td> + </tr> + </table> + </subsection> + <subsection name="Added Indexes"> + <table> + <tr> + <th>Table</th> + <th>Index</th> + <th>Unique</th> + <th>Column(s)</th> + </tr> + <tr> + <td>FOLDER_MENU</td> + <td>IX_FOLDER_MENU_2</td> + <td>non unique</td> + <td>FOLDER_ID</td> + </tr> + <tr> + <td>PAGE_MENU</td> + <td>IX_PAGE_MENU_2</td> + <td>non unique</td> + <td>PAGE_ID</td> + </tr> + <tr> + <td>PRINCIPAL_PERMISSION</td> + <td>IX_PRINCIPAL_PERMISSION_2</td> + <td>non unique</td> + <td>PRINICIPAL_ID</td> + </tr> + <tr> + <td>RULE_CRITERION</td> + <td>IX_RULE_CRITERION_0</td> + <td>non unique</td> + <td>RULE_ID</td> + </tr> + </table> + </subsection> + <subsection name="Added Primary Keys"> + <table> + <tr> + <th>Table</th> + <th>Column(s)</th> + </tr> + <tr> + <td>CLIENT_TO_CAPABILITY</td> + <td>CLIENT_ID, CAPABILITY_ID</td> + </tr> + <tr> + <td>CLIENT_TO_MIMETYPE</td> + <td>CLIENT_ID, MIMETYPE_ID</td> + </tr> + <tr> + <td>MEDIATYPE_TO_CAPABILITY</td> + <td>MEDIATYPE_ID, CAPABILITY_ID</td> + </tr> + <tr> + <td>MEDIATYPE_TO_MIMETYPE</td> + <td>MEDIATYPE_ID, MIMETYPE_ID</td> + </tr> + <tr> + <td>PROFILE_PAGE_ASSOC</td> + <td>LOCATOR_HASH, PAGE_ID</td> + </tr> + </table> + </subsection> + <subsection name="Example SQL migration script from 2.2.1 to 2.2.2"> + <p> + Here is an example of a SQL migration script for a MySQL database: + <source><![CDATA[ +ALTER TABLE CUSTOM_PORTLET_MODE DROP FOREIGN KEY FK_CUSTOM_PORTLET_MODE_1; +ALTER TABLE CUSTOM_WINDOW_STATE DROP FOREIGN KEY FK_CUSTOM_WINDOW_STATE_1; +ALTER TABLE EVENT_DEFINITION DROP FOREIGN KEY FK_EVENT_DEFINITION_1; +ALTER TABLE PA_METADATA_FIELDS DROP FOREIGN KEY FK_PA_METADATA_FIELDS_1; +ALTER TABLE PD_METADATA_FIELDS DROP FOREIGN KEY FK_PD_METADATA_FIELDS_1; +ALTER TABLE SECURITY_ROLE DROP FOREIGN KEY FK_SECURITY_ROLE_REF_1; +ALTER TABLE USER_ATTRIBUTE DROP FOREIGN KEY FK_USER_ATTRIBUTE_1; +ALTER TABLE USER_ATTRIBUTE_REF DROP FOREIGN KEY FK_USER_ATTRIBUTE_REF_1; + +ALTER TABLE CUSTOM_PORTLET_MODE DROP INDEX FK_CUSTOM_PORTLET_MODE_1; +ALTER TABLE CUSTOM_WINDOW_STATE DROP INDEX FK_CUSTOM_WINDOW_STATE_1; +ALTER TABLE EVENT_DEFINITION DROP INDEX FK_EVENT_DEFINITION_1; +ALTER TABLE PA_METADATA_FIELDS DROP INDEX FK_PA_METADATA_FIELDS_1; +ALTER TABLE PD_METADATA_FIELDS DROP INDEX FK_PD_METADATA_FIELDS_1; +ALTER TABLE SECURITY_ROLE DROP INDEX FK_SECURITY_ROLE_REF_1; +ALTER TABLE USER_ATTRIBUTE DROP INDEX FK_USER_ATTRIBUTE_1; +ALTER TABLE USER_ATTRIBUTE_REF DROP INDEX FK_USER_ATTRIBUTE_REF_1; + +ALTER TABLE PROFILE_PAGE_ASSOC DROP INDEX UN_PROFILE_PAGE_1; + +ALTER TABLE PORTLET_DEFINITION ADD COLUMN CLONE_PARENT VARCHAR(80); + +CREATE INDEX IX_FOLDER_MENU_2 ON FOLDER_MENU ( FOLDER_ID ); +CREATE INDEX IX_PAGE_MENU_2 ON PAGE_MENU ( PAGE_ID ); +CREATE INDEX IX_PRINICIPAL_PERMISSION_2 ON PRINCIPAL_PERMISSION ( PRINCIPAL_ID ); +CREATE INDEX IX_RULE_CRITERION_0 ON RULE_CRITERION ( RULE_ID ); + +ALTER TABLE CLIENT_TO_CAPABILITY ADD PRIMARY KEY (CLIENT_ID, CAPABILITY_ID); +ALTER TABLE CLIENT_TO_MIMETYPE ADD PRIMARY KEY (CLIENT_ID, MIMETYPE_ID); +ALTER TABLE MEDIATYPE_TO_CAPABILITY ADD PRIMARY KEY (MEDIATYPE_ID, CAPABILITY_ID); +ALTER TABLE MEDIATYPE_TO_MIMETYPE ADD PRIMARY KEY (MEDIATYPE_ID, MIMETYPE_ID); +ALTER TABLE PROFILE_PAGE_ASSOC ADD PRIMARY KEY (LOCATOR_HASH, PAGE_ID ); + ]]></source> + </p> + </subsection> + </section> + <section name="Data Migrating from Jetspeed 2.1.3/2.1.4 to 2.2.1"> + <p> + Extensive schema changes were made between the 2.1 and 2.2 versions related to the Portlet API 2.0 Standard + implementation, the Pluto 2.0 integration, and the refactoring of the security and SSO components. Here + is a summary of the table modifications that were made: + </p> + <table> + <tr><th>Registry and Preferences Table Name</th><th>Modification</th></tr> + <tr><td>CUSTOM_PORTLET_MODE</td><td>columns changed</td></tr> + <tr><td>CUSTOM_WINDOW_STATE</td><td>columns changed</td></tr> + <tr><td>EVENT_ALIAS</td><td>new table</td></tr> + <tr><td>EVENT_DEFINITION</td><td>new table</td></tr> + <tr><td>FILTERED_PORTLET</td><td>new table</td></tr> + <tr><td>FILTER_LIFECYCLE</td><td>new table</td></tr> + <tr><td>FILTER_MAPPING</td><td>new table</td></tr> + <tr><td>LANGUAGE</td><td>columns changed</td></tr> + <tr><td>LOCALE_ENCODING_MAPPING</td><td>new table</td></tr> + <tr><td>LOCALIZED_DESCRIPTION</td><td>columns changed</td></tr> + <tr><td>LOCALIZED_DISPLAY_NAME</td><td>columns changed</td></tr> + <tr><td>NAMED_PARAMETER</td><td>new table</td></tr> + <tr><td>PARAMETER</td><td>columns changed</td></tr> + <tr><td>PARAMETER_ALIAS</td><td>new table</td></tr> + <tr><td>PA_SECURITY_CONSTRAINT</td><td>new table</td></tr> + <tr><td>PORTLET_APPLICATION</td><td>columns changed</td></tr> + <tr><td>PORTLET_CONTENT_TYPE</td><td>deleted</td></tr> + <tr><td>PORTLET_DEFINITION</td><td>columns changed</td></tr> + <tr><td>PORTLET_ENTITY</td><td>deleted</td></tr> + <tr><td>PORTLET_FILTER</td><td>new table</td></tr> + <tr><td>PORTLET_LISTENER</td><td>new table</td></tr> + <tr><td>PORTLET_PREFERENCE</td><td>new table</td></tr> + <tr><td>PORTLET_PREFERENCE_VALUE</td><td>new table</td></tr> + <tr><td>PORTLET_SUPPORTS</td><td>new table</td></tr> + <tr><td>PREFS_NODE</td><td>deleted</td></tr> + <tr><td>PREFS_PROPERTY_VALUE</td><td>deleted</td></tr> + <tr><td>PROCESSING_EVENT</td><td>new table</td></tr> + <tr><td>PUBLIC_PARAMETER</td><td>new table</td></tr> + <tr><td>PUBLISHING_EVENT</td><td>new table</td></tr> + <tr><td>RUNTIME_OPTION</td><td>new table</td></tr> + <tr><td>RUNTIME_VALUE</td><td>new table</td></tr> + <tr><td>SECURED_PORTLET</td><td>new table</td></tr> + <tr><td>SECURITY_ROLE</td><td>columns and constraints changed</td></tr> + <tr><td>USER_ATTRIBUTE</td><td>columns changed</td></tr> + <tr><td>WEB_APPLICATION</td><td>deleted</td></tr> + </table> + <p/> + <table> + <tr><th>Security and SSO Table Name</th><th>Modification</th></tr> + <tr><td>SECURITY_ATTRIBUTE</td><td>new table</td></tr> + <tr><td>SECURITY_CREDENTIAL</td><td>columns changed</td></tr> + <tr><td>SECURITY_DOMAIN</td><td>new table</td></tr> + <tr><td>SECURITY_GROUP_ROLE</td><td>deleted</td></tr> + <tr><td>SECURITY_PERMISSION</td><td> columns and constraints changed</td></tr> + <tr><td>SECURITY_PRINCIPAL</td><td>columns and constraints changed</td></tr> + <tr><td>SECURITY_PRINCIPAL_ASSOC</td><td>new table</td></tr> + <tr><td>SECURITY_USER_GROUP</td><td>deleted</td></tr> + <tr><td>SECURITY_USER_ROLE</td><td>deleted</td></tr> + <tr><td>SSO_COOKIE</td><td>deleted</td></tr> + <tr><td>SSO_COOKIE_TO_REMOTE</td><td>deleted</td></tr> + <tr><td>SSO_PRINCIPAL_TO_REMOTE</td><td>deleted</td></tr> + <tr><td>SSO_SITE</td><td>columns and constraints changed</td></tr> + <tr><td>SSO_SITE_TO_PRINCIPALS</td><td>deleted</td></tr> + <tr><td>SSO_SITE_TO_REMOTE</td><td>deleted</td></tr> + </table> + <p/> + <table> + <tr><th>Statisitics Table Name</th><th>Modification</th></tr> + <tr><td>ADMIN_ACTIVITY</td><td>column sizes changed</td></tr> + <tr><td>USER_ACTIVITY</td><td>column sizes changed</td></tr> + </table> + <p> + Given the extensive modifications made between these releases, migration is best performed using an ETL + approach. To support this outside of the Jetspeed portal build and runtime environments, export, + initialization, and import functionality have been integrated into the Jetspeed installer. The installer + can be downloaded as a binary and, together with a JDBC driver, can be used to migrate from 2.1.3/2.1.4 + to 2.2.1. + </p> + <p> + Documentation for ETL migration using the Jetspeed installer can be found here: <a href="guide-etl-migration.html">ETL Migration Guide</a>. + Note that migration of Derby databases using the installer is not currently supported. + </p> + </section> + <section name="Data Migrating from Jetspeed 2.1.3 to 2.1.4"> + <p>The following tables describe database schema changes from version 2.1.3 to version 2.1.4. + </p> + <subsection name="Constraint removed"> + <table> + <tr> + <th>Table</th> + <th>column(s)</th> + <th>2.1.3</th> + <th>2.1.4</th> + </tr> + <tr> + <td>PARAMETER</td> + <td>PARAMETER_VALUE</td> + <td>Required</td> + <td>Not required</td> + </tr> + </table> + <p> + Here is an example of the SQL migration scripts for the MySQL database: + <source><![CDATA[ALTER TABLE 'PARAMETER` MODIFY COLUMN `PARAMETER_VALUE` DEFAULT NULL;]]></source> + </p> + </subsection> + </section> + <section name="Data Migrating from Jetspeed 2.1.2 to 2.1.3"> + <p>The following tables describe database schema changes from version 2.1.3 to version 2.1.2. + </p> + <subsection name="Added Indexes"> + <table> + <tr> + <th>Table</th> + <th>Index</th> + <th>type</th> + <th>column(s)</th> + </tr> + <tr> + <td>PREFS_NODE</td> + <td>IX_PREFS_NODE_1</td> + <td>non unique</td> + <td>PARENT_NODE_ID</td> + </tr> + <tr> + <td>PREFS_NODE</td> + <td>IX_PREFS_NODE_2</td> + <td>non unique</td> + <td>FULL_PATH</td> + </tr> + <tr> + <td>PREFS_PROPERTY_VALUE</td> + <td>IX_FKPPV_1</td> + <td>non unique</td> + <td>NODE_ID</td> + </tr> + + </table> + </subsection> + <subsection name="Foreign Key Altering"> + <table> + <tr> + <th>Table</th> + <th>Name</th> + <th>Column(s)</th> + <th>Referencing table</th> + <th>Referencing column(s)</th> + <th>2.1.2</th> + <th>2.1.3</th> + </tr> + <tr> + <td>PREFS_NODE</td> + <td>FK_PREFS_NODE_1</td> + <td>PARENT_NODE_ID</td> + <td>PREFS_NODE</td> + <td>NODE_ID</td> + <td>(not casade delete)</td> + <td>CASCADE DELETE</td> + </tr> + <tr> + <td>PREFS_PROPERTY_VALUE</td> + <td>(not named)</td> + <td>NODE_ID</td> + <td>PREFS_NODE</td> + <td>NODE_ID</td> + <td>(not casade delete)</td> + <td>CASCADE DELETE</td> + </tr> + </table> + <p> + Here is an example of the SQL migration scripts for the MySQL database: + <source><![CDATA[ +CREATE INDEX IX_PREFS_NODE_1 ON PREFS_NODE (PARENT_NODE_ID); +CREATE INDEX IX_PREFS_NODE_2 ON PREFS_NODE (FULL_PATH); +CREATE INDEX IX_FKPPV_1 ON PREFS_PROPERTY_VALUE (NODE_ID); + +ALTER TABLE PREFS_NODE ADD CONSTRAINT FK_PREFS_NODE_1 FOREIGN KEY (PARENT_NODE_ID) REFERENCES PREFS_NODE (NODE_ID) ON DELETE CASCADE; +ALTER TABLE PREFS_PROPERTY_VALUE ADD CONSTRAINT FK_PREFS_PROPERTY_VALUE_1 FOREIGN KEY (NODE_ID) REFERENCES PREFS_NODE (NODE_ID) ON DELETE CASCADE; + ]]></source> + </p> + <p> + Here is an example of the SQL migration scripts for the MySQL database: + <source><![CDATA[ +CREATE INDEX IX_PREFS_NODE_1 ON PREFS_NODE (PARENT_NODE_ID); +CREATE INDEX IX_PREFS_NODE_2 ON PREFS_NODE (FULL_PATH); +CREATE INDEX IX_FKPPV_1 ON PREFS_PROPERTY_VALUE (NODE_ID); + +ALTER TABLE PREFS_NODE ADD CONSTRAINT FK_PREFS_NODE_1 FOREIGN KEY (PARENT_NODE_ID) REFERENCES PREFS_NODE (NODE_ID) ON DELETE CASCADE; +ALTER TABLE PREFS_PROPERTY_VALUE ADD CONSTRAINT FK_PREFS_PROPERTY_VALUE_1 FOREIGN KEY (NODE_ID) REFERENCES PREFS_NODE (NODE_ID) ON DELETE CASCADE; + ]]></source> + </p> + </subsection> + </section> + <section name="Data Migrating from Jetspeed 2.1 to 2.1.2"> + <p>The following tables describe database schema changes from version 2.1 to version 2.1.2. + </p> + <subsection name="Added Tables"> + <table> + <tr> + <th>Table</th> + </tr> + <tr> + <td>ADMIN_ACTIVITY</td> + </tr> + <tr> + <td>USER_ACTIVITY</td> + </tr> + </table> + </subsection> + </section> + <section name="Configuration Migrating from Jetspeed 2.0 to 2.1"> + <p>The following items describe important functional changes in Jetspeed 2.1 + </p> + <subsection name="Portlet API Caching"> + <p>Version 2.1 is the first Jetspeed version to support Portlet API Caching. In 2.0 the expiration-cache was set to -1 (infinity time) + for all layouts in the file WEB-INF\apps\jetspeed-layouts\WEB-INF\portlet.xml. When upgrading to version 2.1 or greater from 2.0, you will need + to update your database to disable portlet caching on the Jetspeed layouts. Updating the layouts can be achieved by either redeploying the jetspeed-layouts portlet application, + or by updating your database as shown below (assuming the APPLICATION_ID value is 2) for the jetspeed-layouts application. +<source><![CDATA[ +UPDATE PORTLET_DEFINITION P SET EXPIRATION_CACHE = 0 WHERE P.APPLICATION_ID = 2 +]]></source> + </p> + </subsection> + <subsection name="Portlet Preferences"> + <p>Portlet Preferences are now by default user specific on all pages. In Jetspeed 2.0, for shared pages, the Portlet Preferences were shared as well.</p> + <p>To retain most of the old Jetspeed 2.0 behavior, allowing an administrator to still set/modify <i>initial</i> Preferences for other users,<br/> + modify the following setting in the registry.xml spring assembly configuration for the portletEntityAccessImpl component: + <source> +<!-- + All preferences were shared. With JS2-449, preferences are now + stored 'per user'. The username is stored in the preferences FULL_PATH + To turn on mergeSharedPreferences configure this property to true + This will NOT turn off per user prefs, + but instead merge with them, where user prefs override. + boolean +--> +<constructor-arg type="boolean"> +<value>false</value> +</constructor-arg> + </source> + As is commented in the assembly configuration also, setting <i>mergeSharedPreferences</i> to <i>true</i> will <i>NOT</i> turn off per user Preferences.<br/> + Once a user sets its own Preference values (if allowed), those will override the shared Preference values.<br/> + See for further information: <a href="http://issues.apache.org/jira/browse/JS2-449" target="_blank">JS2-449</a> + </p> + </subsection> + </section> + <section name="Data Migrating from Jetspeed 2.0 to 2.1"> + <p>The following tables describe database schema changes from version 2.0 to version 2.1. + </p> + <subsection name="Added Tables"> + <table> + <tr> + <th>Table</th> + </tr> + <tr> + <td>CUSTOM_PORTLET_MODE</td> + </tr> + <tr> + <td>CUSTOM_WINDOW_STATE</td> + </tr> + </table> + </subsection> + <subsection name="Column Altering"> + <table> + <tr> + <th>Table</th> + <th>Column</th> + <th>2.0</th> + <th>2.1</th> + </tr> + <tr> + <td>PORTLET_STATISTICS</td> + <td>ELAPSED_TIME</td> + <td>INTEGER</td> + <td>BIGINT</td> + </tr> + <tr> + <td>PAGE_STATISTICS</td> + <td>ELAPSED_TIME</td> + <td>INTEGER</td> + <td>BIGINT</td> + </tr> + <tr> + <td>USER_STATISTICS</td> + <td>ELAPSED_TIME</td> + <td>INTEGER</td> + <td>BIGINT</td> + </tr> + <tr> + <td>FOLDER</td> + <td>SKIN</td> + <td></td> + <td>NEW: VARCHAR(80)</td> + </tr> + <tr> + <td>FOLDER</td> + <td>DEFAULT_LAYOUT_DECORATOR</td> + <td></td> + <td>NEW: VARCHAR(80)</td> + </tr> + <tr> + <td>FOLDER</td> + <td>DEFAULT_PORTLET_DECORATOR</td> + <td></td> + <td>NEW: VARCHAR(80)</td> + </tr> + <tr> + <td>FRAGMENT</td> + <td>STATE</td> + <td>VARCHAR(40)</td> + <td>VARCHAR(10)</td> + </tr> + <tr> + <td>FRAGMENT</td> + <td>PMODE</td> + <td></td> + <td>NEW: VARCHAR(10)</td> + </tr> + <tr> + <td>FRAGMENT</td> + <td>LAYOUT_X</td> + <td></td> + <td>NEW: REAL</td> + </tr> + <tr> + <td>FRAGMENT</td> + <td>LAYOUT_Y</td> + <td></td> + <td>NEW: REAL</td> + </tr> + <tr> + <td>FRAGMENT</td> + <td>LAYOUT_Z</td> + <td></td> + <td>NEW: REAL</td> + </tr> + <tr> + <td>FRAGMENT</td> + <td>LAYOUT_WIDTH</td> + <td></td> + <td>NEW: REAL</td> + </tr> + <tr> + <td>FRAGMENT</td> + <td>LAYOUT_HEIGHT</td> + <td></td> + <td>NEW: REAL</td> + </tr> + <tr> + <td>LINK</td> + <td>SKIN</td> + <td></td> + <td>NEW: VARCHAR(80)</td> + </tr> + <tr> + <td>PORTLET_DEFINITION</td> + <td>SECURITY_REF</td> + <td></td> + <td>NEW: VARCHAR(40)</td> + </tr> + <tr> + <td>PORTLET_DEFINITION</td> + <td>SECURITY_REF</td> + <td></td> + <td>NEW: VARCHAR(40)</td> + </tr> + <tr> + <td>PORTLET_APPLICATION</td> + <td>SECURITY_REF</td> + <td></td> + <td>NEW: VARCHAR(40)</td> + </tr> + <tr> + <td>SSO_COOKIE</td> + <td>COOKIE</td> + <td>VARCHAR(250)</td> + <td>VARCHAR(1024)</td> + </tr> + </table> + </subsection> + <subsection name="Index Altering"> + <table> + <tr> + <th>Table</th> + <th>Index</th> + <th>2.0</th> + <th>2.1</th> + </tr> + <tr> + <td>FOLDER_MENU</td> + <td>UN_FOLDER_MENU_1</td> + <td>unique</td> + <td>(non unique) index</td> + </tr> + <tr> + <td>PAGE_MENU</td> + <td>UN_PAGE_MENU_1</td> + <td>unique</td> + <td>(non unique) index</td> + </tr> + <tr> + <td>FRAGMENT</td> + <td>UN_FRAGMENT_1</td> + <td>unique</td> + <td>(non unique) index</td> + </tr> + + </table> + </subsection> + <subsection name="Foreign Key Altering"> + <table> + <tr> + <th>Table</th> + <th>Column</th> + <th>2.0</th> + <th>2.1</th> + </tr> + <tr> + <td>FOLDER</td> + <td>(FK constraint)</td> + <td>(not named)</td> + <td>named FK constraint "FK_FOLDER_1"</td> + </tr> + <tr> + <td>FOLDER_METADATA</td> + <td>(FK constraint)</td> + <td>(not named)</td> + <td>named FK constraint "FK_FOLDER_METADATA_1"</td> + </tr> + <tr> + <td>FOLDER_CONSTRAINT</td> + <td>(FK constraint)</td> + <td>(not named)</td> + <td>named FK constraint "FK_FOLDER_CONSTRAINT_1"</td> + </tr> + <tr> + <td>FOLDER_CONSTRAINTS_REF</td> + <td>(FK constraint)</td> + <td>(not named)</td> + <td>named FK constraint "FK_FOLDER_CONSTRAINT_REF_1"</td> + </tr> + <tr> + <td>FOLDER_ORDER</td> + <td>(FK constraint)</td> + <td>(not named)</td> + <td>named FK constraint "FK_FOLDER_ORDER_1"</td> + </tr> + <tr> + <td>FOLDER_MENU</td> + <td>(FK constraint)</td> + <td>(not named)</td> + <td>named FK constraint "FK_FOLDER_MENU_1"</td> + </tr> + <tr> + <td>FOLDER_MENU</td> + <td>(FK constraint)</td> + <td>(not named)</td> + <td>named FK constraint "FK_FOLDER_MENU_2"</td> + </tr> + <tr> + <td>FOLDER_MENU_METADATA</td> + <td>(FK constraint)</td> + <td>(not named)</td> + <td>named FK constraint "FK_FOLDER_MENU_METADATA_1"</td> + </tr> + <tr> + <td>PAGE</td> + <td>(FK constraint)</td> + <td>(not named)</td> + <td>named FK constraint "FK_PAGE_1"</td> + </tr> + <tr> + <td>PAGE_METADATA</td> + <td>(FK constraint)</td> + <td>(not named)</td> + <td>named FK constraint "FK_PAGE_METADATA_1"</td> + </tr> + <tr> + <td>PAGE_CONSTRAINT</td> + <td>(FK constraint)</td> + <td>(not named)</td> + <td>named FK constraint "FK_PAGE_CONSTRAINT_1"</td> + </tr> + <tr> + <td>PAGE_CONSTRAINT_REF</td> + <td>(FK constraint)</td> + <td>(not named)</td> + <td>named FK constraint "FK_PAGE_CONSTRAINTS_REF_1"</td> + </tr> + <tr> + <td>PAGE_MENU</td> + <td>(FK constraint)</td> + <td>(not named)</td> + <td>named FK constraint "FK_PAGE_MENU_1"</td> + </tr> + <tr> + <td>PAGE_MENU</td> + <td>(FK constraint)</td> + <td>(not named)</td> + <td>named FK constraint "PM_M_FK_PAGE_ID_PAGE"</td> + </tr> + <tr> + <td>PAGE_MENU_METADATA</td> + <td>(FK constraint)</td> + <td>(not named)</td> + <td>named FK constraint "FK_PAGE_MENU_METADATA_1"</td> + </tr> + <tr> + <td>FRAGMENT</td> + <td>(FK constraint)</td> + <td>(not named)</td> + <td>named FK constraint "FK_FRAGMENT_1"</td> + </tr> + <tr> + <td>FRAGMENT</td> + <td>(FK constraint)</td> + <td>(not named)</td> + <td>named FK constraint "FK_FRAGMENT_2"</td> + </tr> + <tr> + <td>FRAGMENT_CONSTRAINT</td> + <td>(FK constraint)</td> + <td>(not named)</td> + <td>named FK constraint "FK_FRAGMENT_CONSTRAINT_1"</td> + </tr> + <tr> + <td>FRAGMENT_CONSTRAINT_REF</td> + <td>(FK constraint)</td> + <td>(not named)</td> + <td>named FK constraint "FK_FRAGMENT_CONSTRAINT_REF_1"</td> + </tr> + <tr> + <td>FRAGMENT_PREF</td> + <td>(FK constraint)</td> + <td>(not named)</td> + <td>named FK constraint "FK_FRAGMENT_PREF_1"</td> + </tr> + <tr> + <td>FRAGMENT_PREF_VALUE</td> + <td>(FK constraint)</td> + <td>(not named)</td> + <td>named FK constraint "FK_FRAGMENT_PREF_VALUE_1"</td> + </tr> + <tr> + <td>LINK</td> + <td>(FK constraint)</td> + <td>(not named)</td> + <td>named FK constraint "FK_LINK_1"</td> + </tr> + <tr> + <td>LINK_METADATA</td> + <td>(FK constraint)</td> + <td>(not named)</td> + <td>named FK constraint "FK_LINK_METADATA_1"</td> + </tr> + <tr> + <td>LINK_CONSTRAINT</td> + <td>(FK constraint)</td> + <td>(not named)</td> + <td>named FK constraint "FK_LINK_CONSTRAINT_1"</td> + </tr> + <tr> + <td>LINK_CONSTRAINT_REF</td> + <td>(FK constraint)</td> + <td>(not named)</td> + <td>named FK constraint "FK_LINK_CONSTRAINT_REF_1"</td> + </tr> + <tr> + <td>PAGE_SECURITY</td> + <td>(FK constraint)</td> + <td>(not named)</td> + <td>named FK constraint "FK_PAGE_SECURITY_1"</td> + </tr> + <tr> + <td>PAGE_SEC_CONSTRAINTS_DEF</td> + <td>(FK constraint)</td> + <td>(not named)</td> + <td>named FK constraint "FK_PAGE_SEC_CONSTRAINTS_DEF_1"</td> + </tr> + <tr> + <td>PAGE_SEC_CONSTRAINT_DEF</td> + <td>(FK constraint)</td> + <td>(not named)</td> + <td>named FK constraint "FK_PAGE_SEC_CONSTRAINT_DEF_1"</td> + </tr> + <tr> + <td>PAGE_SEC_CONSTRAINTS_REF</td> + <td>(FK constraint)</td> + <td>(not named)</td> + <td>named FK constraint "FK_PAGE_SEC_CONSTRAINTS_REF_1"</td> + </tr> + <tr> + <td>PAGE_SEC_CONSTRAINT_REF</td> + <td>(FK constraint)</td> + <td>(not named)</td> + <td>named FK constraint "FK_PAGE_SEC_CONSTRAINT_REF_1"</td> + </tr> + <tr> + <td>RULE_CRITERION</td> + <td>(FK constraint)</td> + <td>(not named)</td> + <td>named FK constraint "FK_RULE_CRITERION_1"</td> + </tr> + <tr> + <td>PREFS_NODE</td> + <td>(FK constraint)</td> + <td>(not named)</td> + <td>named FK constraint "FK_PREFS_NODE_1"</td> + </tr> + <tr> + <td>PA_METADATA_FIELDS</td> + <td>(FK constraint)</td> + <td>(not named)</td> + <td>named FK constraint "FK_PA_METADATA_FIELDS_1"</td> + </tr> + <tr> + <td>PD_METADATA_FIELDS</td> + <td>(FK constraint)</td> + <td>(not named)</td> + <td>named FK constraint "FK_PD_METADATA_FIELDS_1"</td> + </tr> + <tr> + <td>USER_ATTRIBUTE_REF</td> + <td>(FK constraint)</td> + <td>(not named)</td> + <td>named FK constraint "FK_USER_ATTRIBUTE_REF_1"</td> + </tr> + <tr> + <td>USER_ATTRIBUTE</td> + <td>(FK constraint)</td> + <td>(not named)</td> + <td>named FK constraint "FK_USER_ATTRIBUTE_1"</td> + </tr> + <tr> + <td>PRINCIPAL_PERMISSION</td> + <td>(FK constraint)</td> + <td>(not named)</td> + <td>named FK constraint "FK_PRINCIPAL_PERMISSION_1"</td> + </tr> + <tr> + <td>PRINCIPAL_PERMISSION</td> + <td>(FK constraint)</td> + <td>(not named)</td> + <td>named FK constraint "FK_PRINCIPAL_PERMISSION_2"</td> + </tr> + <tr> + <td>SECURITY_CREDENTIAL</td> + <td>(FK constraint)</td> + <td>(not named)</td> + <td>named FK constraint "FK_SECURITY_CREDENTIAL_1"</td> + </tr> + <tr> + <td>SSO_SITE_TO_PRINCIPALS</td> + <td>(FK constraint)</td> + <td>(not named)</td> + <td>named FK constraint "SSO_SITE_TO_PRINC_FK1"</td> + </tr> + <tr> + <td>SSO_SITE_TO_PRINCIPALS</td> + <td>(FK constraint)</td> + <td>(not named)</td> + <td>named FK constraint "SSO_SITE_TO_PRINC_FK2"</td> + </tr> + <tr> + <td>SSO_PRINCIPAL_TO_REMOTE</td> + <td>(FK constraint)</td> + <td>(not named)</td> + <td>named FK constraint "FK_SSO_PRINCIPAL_TO_REMOTE_1"</td> + </tr> + <tr> + <td>SSO_PRINCIPAL_TO_REMOTE</td> + <td>(FK constraint)</td> + <td>(not named)</td> + <td>named FK constraint "FK_SSO_PRINCIPAL_TO_REMOTE_2"</td> + </tr> + <tr> + <td>SSO_SITE_TO_REMOTE</td> + <td>(FK constraint)</td> + <td>(not named)</td> + <td>named FK constraint "FK_SSO_SITE_TO_REMOTE_1"</td> + </tr> + <tr> + <td>SSO_SITE_TO_REMOTE</td> + <td>(FK constraint)</td> + <td>(not named)</td> + <td>named FK constraint "FK_SSO_SITE_TO_REMOTE_2"</td> + </tr> + <tr> + <td>SSO_COOKIE_TO_REMOTE</td> + <td>(FK constraint)</td> + <td>(not named)</td> + <td>named FK constraint "FK_SSO_COOKIE_TO_REMOTE_1"</td> + </tr> + <tr> + <td>SSO_COOKIE_TO_REMOTE</td> + <td>(FK constraint)</td> + <td>(not named)</td> + <td>named FK constraint "FK_SSO_COOKIE_TO_REMOTE_2"</td> + </tr> + <tr> + <td>SECURITY_USER_ROLE</td> + <td>(FK constraint)</td> + <td>(not named)</td> + <td>named FK constraint "FK_SECURITY_USER_ROLE_1"</td> + </tr> + <tr> + <td>SECURITY_USER_ROLE</td> + <td>(FK constraint)</td> + <td>(not named)</td> + <td>named FK constraint "FK_SECURITY_USER_ROLE_2"</td> + </tr> + <tr> + <td>SECURITY_USER_GROUP</td> + <td>(FK constraint)</td> + <td>(not named)</td> + <td>named FK constraint "FK_SECURITY_USER_GROUP_1"</td> + </tr> + <tr> + <td>SECURITY_USER_GROUP</td> + <td>(FK constraint)</td> + <td>(not named)</td> + <td>named FK constraint "FK_SECURITY_USER_GROUP_2"</td> + </tr> + <tr> + <td>SECURITY_GROUP_ROLE</td> + <td>(FK constraint)</td> + <td>(not named)</td> + <td>named FK constraint "FK_SECURITY_GROUP_ROLE_1"</td> + </tr> + <tr> + <td>SECURITY_GROUP_ROLE</td> + <td>(FK constraint)</td> + <td>(not named)</td> + <td>named FK constraint "FK_SECURITY_GROUP_ROLE_2"</td> + </tr> + </table> + </subsection> + + </section> + </body> +</document> +
Added: portals/site/jetspeed/jetspeed-2.3/src/site/xdoc/how-to-help.xml URL: http://svn.apache.org/viewvc/portals/site/jetspeed/jetspeed-2.3/src/site/xdoc/how-to-help.xml?rev=1691449&view=auto ============================================================================== --- portals/site/jetspeed/jetspeed-2.3/src/site/xdoc/how-to-help.xml (added) +++ portals/site/jetspeed/jetspeed-2.3/src/site/xdoc/how-to-help.xml Thu Jul 16 21:01:09 2015 @@ -0,0 +1,79 @@ +<?xml version="1.0"?> +<!-- + Licensed to the Apache Software Foundation (ASF) under one or more + contributor license agreements. See the NOTICE file distributed with + this work for additional information regarding copyright ownership. + The ASF licenses this file to You under the Apache License, Version 2.0 + (the "License"); you may not use this file except in compliance with + the License. You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. +--> +<document> + <properties> + <title>How to Help?</title> + <subtitle>How to Help?</subtitle> + <authors> + <person name="David Le Strat" email="[email protected]" /> + </authors> + </properties> + <body> + <section name="How to Help?"> + <subsection name="Simple Things I Can Do to Help"> + <p> + There are many ways to help with Jetspeed-2 as with most open source projects: + <ul> + <li>Subscribe to the <a href="mail-lists.html">user mailing list</a> and help answer questions from the community. + In open source a thriving community makes the project successful. Don't be shy to ask basic questions, we have all + been there.</li> + <li>Report bugs and issues that you encounter in <a href="http://issues.apache.org/jira/secure/BrowseProject.jspa?id=10492">Jetspeed-2 bug tracking system</a>. + Prior to reporting a bug, make sure to discuss the issue on the <a href="mail-lists.html">user mailing list</a> or even the + <a href="mail-lists.html">developer mailing list</a>.</li> + <li>When you encounter an issue, you may be compelled to fix it. We encourage this as this makes for a vibrant + community. Once you have a fix, <a href="devguide/patches.html">submit a patch</a> on the reporting issue.</li> + </ul> + </p> + </subsection> + <subsection name="Why Should I Get Involved?"> + <p> + There are many reasons why you want to help, just a few strong points: + <ul> + <li>If you help others solve there issues, they will most likely help you when you run into some problems.</li> + <li>By contributing patches, you can influence the prioritization of functionality and get your changes incorporated.</li> + <li>By reporting issues, you help Jetspeed-2 become a stronger project and improve its quality overall.</li> + <li>You will meet and get to know great people as well as share and learn best practices which will help you on + your project.</li> + </ul> + We are looking forward to have you part of our community! + </p> + </subsection> + <subsection name="How do I Join the Project?"> + <p> + Projects at Apache operate under a <a href="http://www.apache.org/foundation/how-it-works.html#meritocracy">meritocracy</a>. + To become a committer, you first need to demonstrate your committment. The best way to do so is to start contributing patch, + participate in the community and make your interest known. It takes time and willingness to help and contribute! This may + seem a bit intimidating at first, but the community will always help people who show interest and committment. + </p> + </subsection> + <subection name="Other Resources for Help"> + <p> + Here are some useful links for other resources for help. + <ul> + <li><a href="http://portals.apache.org/development/code-standards.html">Portals project coding standards</a>.</li> + <li><a href="http://portals.apache.org/development/documentation.html">Portals project documentation standards</a>.</li> + <li><a href="http://www.apache.org/foundation/how-it-works.html">How does the Apache Software Foundation work</a>?</li> + <li><a href="http://people.apache.org/~coar/mlists.html#portals.apache.org">Portals mailing lists statistics</a>. This can be helpful + to help you decide which mailing list to subscribe to.</li> + </ul> + </p> + </subection> + </section> + </body> +</document> + Added: portals/site/jetspeed/jetspeed-2.3/src/site/xdoc/index.xml URL: http://svn.apache.org/viewvc/portals/site/jetspeed/jetspeed-2.3/src/site/xdoc/index.xml?rev=1691449&view=auto ============================================================================== --- portals/site/jetspeed/jetspeed-2.3/src/site/xdoc/index.xml (added) +++ portals/site/jetspeed/jetspeed-2.3/src/site/xdoc/index.xml Thu Jul 16 21:01:09 2015 @@ -0,0 +1,157 @@ +<?xml version="1.0"?> +<!-- + Licensed to the Apache Software Foundation (ASF) under one or more + contributor license agreements. See the NOTICE file distributed with + this work for additional information regarding copyright ownership. + The ASF licenses this file to You under the Apache License, Version 2.0 + (the "License"); you may not use this file except in compliance with + the License. You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. +--> +<document> + <properties> + <title>Jetspeed 2 Home Page</title> + <subtitle>Welcome to Jetspeed 2</subtitle> + <authors> + <person name="David Sean Taylor" email="[email protected]" /> + <person name="David Le Strat" email="[email protected]" /> + </authors> + </properties> + <body> + <section name="Welcome to Jetspeed-2"> + <div id="downloadbox"> + <h5>Get Jetspeed 2.2.2</h5> + <p> + <a href="download.html"> + <img valign="top" src="images/folder-open.gif" + border="0" alt="" title="download" /> + Download + </a> + Jetspeed 2.2.2 + <small>(94MB)</small> + </p> + <ul> + <li> + <a href="getting-started.html#Requirements"> + System Requirements + </a> + </li> + <li> + <a + href="getting-started-installer.html"> + Installation Instructions + </a> + </li> + <li> + <a href="release-notes.html">Release Notes</a> + </li> + <li> + <a href="features.html">Features</a> + </li> + <li> + <a href="guide-migration.html"> + Migrating Guide + </a> + </li> + <li> + <a href="demo.html"> + Live demo! + </a> + </li> + </ul> + </div> + <p> +Jetspeed is an Open Portal Platform and Enterprise Information Portal, written entirely in open source under the Apache license in Java and XML and based on open standards. +All access to the portal is managed through a robust portal security policy. Within a Jetspeed portal, individual portlets can be aggregated to create a page. Each portlet is an independent application with +Jetspeed acting as the central hub making information from multiple sources available in an easy to use manner. + </p> +<p> +Jetspeed has been fully conformant to the +<a href="http://www.jcp.org/en/jsr/detail?id=286">Java Portlet 2.0 Standard</a> since release 2.2.0 in May 2009. +All releases prior, such as the 2.1.x releases, are conformant to the first Java Portlet Specification, + <a href="http://www.jcp.org/en/jsr/detail?id=168">the Java Portlet 1.0 Standard</a>. +</p> + <p> +A portal based on Jetspeed can make applications, database information and other data sources available to end-users through a single web site. +Jetspeed provides a security infrastructure so that the information and functions made available to each user can be customized on basis of the + user or a role that the user has. The user can access the portal via a web browser, WAP-phone, pager or any other device supported by the servlet engine. + </p> + <p> + +The Jetspeed enterprise portal integrates dynamic information, people, and processes across organization boundaries. This content is aggregated using portlets from diverse sources. +Portlets are just mini-web applications, or web-components. Jetspeed always provides secured access to the portlets. A short overview of Jetspeed <a href="features.html" >features</a>: +<ul> +<li>*New* 2.2.2 Portlet Cloning: allow site editors to quickly create new portlet variants based on modified preference and other descriptor settings</li> +<li>*New* 2.2.2 Admin roles security restriction on admin roles maintenance</li> +<li>*New* 2.2.1 JetUI AJAX Customization Engine with Dockable Toolbox, Drag and Drop, New Navigations</li> +<li>Secure Access - Security based on standards, ACLs, Open ID, CAS</li> +<li>Single Point of Entry (SSO, Federated) </li> +<li>Enterprise Integration - (EAI, integration points)</li> +<li>Personalization - (customizers, skins) </li> +<li>Dynamic Web Components - (portlets based on standards)</li> +<li>Scaleable, Component Architecture featuring multi-threading</li> +</ul> +</p> + <subsection name="Jetspeed-2 Status"> +<p> +The latest version of Jetspeed is 2.2.2, released October 10, 2011. Version 2.2.2 is primarily a maintenance and bugfix release. +See the <a href='features.html'>Features</a> page for a complete description of the Jetspeed 2.2.2 release. + </p> + </subsection> + + <subsection name="Jetspeed Documentation"> + <p> + Most of Jetspeed's documentation is in the form of guides. Depending on your role at the portal, you may want to read one of these guides: + <ul> + <li> + <a href="usersguide/index.html"> + Users Guide + </a> + </li> + <li> + <a href="adminguide/index.html"> + Administration Guide + </a> + </li> + <li> + <a href="deployguide/index.html"> + Deployment and Configuration Guide + </a> + </li> + <li> + <a href="buildguide/index.html"> + Build Guide + </a> + </li> + <li> + <a href="devguide/index.html"> + Developers Guide + </a> + </li> + </ul> + </p> + </subsection> + <subsection name="Jetspeed Tutorials"> + <p> + A great place to learn how to use Jetspeed is with the Tutorials: + <ul> + <li> + <a href="tutorial/index.html"> + Custom Jetspeed Build Tutorial with Maven-2 + </a> + </li> + </ul> + </p> + </subsection> + + + </section> + </body> +</document>
