Modified: portals/site-live/jetspeed-2/features.html URL: http://svn.apache.org/viewvc/portals/site-live/jetspeed-2/features.html?rev=1901428&r1=1901427&r2=1901428&view=diff ============================================================================== --- portals/site-live/jetspeed-2/features.html (original) +++ portals/site-live/jetspeed-2/features.html Tue May 31 02:15:08 2022 @@ -42,7 +42,7 @@ <div class="xleft"> - Last Published: 9 May 2016 + Last Published: 26 May 2022 </div> <div class="xright"> <a href="http://portals.apache.org/applications/"; class="externalLink">Applications</a> | @@ -253,257 +253,257 @@ </div> <div id="bodyColumn"> <div id="contentBox"> - <subtitle></subtitle><authors><person name="David Le Strat" email="[email protected]"><person name="Marky Goldstein" email="[email protected]"><person name="David Sean Taylor" email="[email protected]"></authors><div class="section"><h2><a name="Features"></a>Features</h2> + <subtitle></subtitle><authors><person name="David Le Strat" email="[email protected]"><person name="Marky Goldstein" email="[email protected]"><person name="David Sean Taylor" email="[email protected]"></authors><div class="section"><h2><a name="Features"></a>Features</h2> <p> The Apache Portals Jetspeed Team is pleased to present the Jetspeed-2 Open Source Enterprise Portal. This open source project has matured past several releases, and has been fully-compliant with the Portlet Specification 1.0 (JSR-168) since version 2.0. Jetspeed-2 passes the TCK (Test Compatibility Kit) suite and is fully CERTIFIED to the Java Portlet Standard. - </p> + </p> <p>Jetspeed is fully-compliant with the Portlet Specification 2.0 (JSR-286), pasing the Portlet 2.0 TCK (Test Compatibility Kit) suite and is fully CERTIFIED to the Java Portlet Standard. - </p> -<div class="section"><h3><a name="New_Features_for_2.3.1"></a>New Features for 2.3.1</h3> + </p> +<div class="section"><h3><a name="New_Features_for_2.3.1"></a>New Features for 2.3.1</h3> <p> - Overview of new features in version <a href="http://portals.apache.org/jetspeed-2/release-notes.html"; class="externalLink">2.3.1</a>: - <ul><li>[<a href="http://portals.apache.org/jetspeed-2/security-reports.html"; class="externalLink">Security Patches</a>] - Important Security Issues found by Apache Security Team - </li> + Overview of new features in version <a class="externalLink" href="http://portals.apache.org/jetspeed-2/release-notes.html";>2.3.1</a>: + <ul><li>[<a class="externalLink" href="http://portals.apache.org/jetspeed-2/security-reports.html";>Security Patches</a>] - Important Security Issues found by Apache Security Team + </li> <li>Improved Session based Portlet Preferences - </li> + </li> <li>Detached Portlets are now available in the Portal Pipeline - </li> + </li> <li>A Search input field is now shown on all decorators. A new Search Page with search results has been added. Currently only Registry and light documentation are indexed. - </li> + </li> <li>Improvements to the User Manager portlets: Filter By Groups, Email fields added. - </li> -<li>Improved Responsive Decorators</li> + </li> +<li>Improved Responsive Decorators</li> <li>Improved CSS in Site Manager and Constraints portlets - </li> -</ul> -</p> -</div> -<div class="section"><h3><a name="New_Features_for_2.3.0"></a>New Features for 2.3.0</h3> + </li> +</ul> +</p> +</div> +<div class="section"><h3><a name="New_Features_for_2.3.0"></a>New Features for 2.3.0</h3> <p> - Overview of new features in version <a href="http://portals.apache.org/jetspeed-2/release-notes-2.3.0.html"; class="externalLink">2.3.0</a>: - <ul><li>AutoRefresh - portlets can now be configured to auto-refresh themselves in the jetspeed-portlet.xml deployment descriptor</li> -<li>Responsive Decorators and Layouts - a new set of responsive decorators and layouts have been introduced to work with mobile and full web devices</li> -<li>New Responsive Profiler Admin Portlet</li> -<li>New WebContent 2 Framework for IFrames and Secure rendering of remote content</li> -<li>Jetspeed API now fully supports Java generics</li> -<li>Support Tomcat7 out of box as default application server</li> -<li>New User Browser supporting large user data sets</li> -<li>Added support for Anding PSML Security constraints</li> -<li>Upgrading all JAR dependencies to latest versions</li> -<li>Set default compiler to Java 1.7</li> -<li>Improved Portlet Preferences and Security Caching</li> -<li>Upgrade Jetspeed to Servlet Spec 3.0</li> -<li>Upgrade Jetspeed to Portlet Spec 2.1.0</li> -</ul> -</p> -</div> -<div class="section"><h3><a name="New_Features_for_2.2.2"></a>New Features for 2.2.2</h3> + Overview of new features in version <a class="externalLink" href="http://portals.apache.org/jetspeed-2/release-notes-2.3.0.html";>2.3.0</a>: + <ul><li>AutoRefresh - portlets can now be configured to auto-refresh themselves in the jetspeed-portlet.xml deployment descriptor</li> +<li>Responsive Decorators and Layouts - a new set of responsive decorators and layouts have been introduced to work with mobile and full web devices</li> +<li>New Responsive Profiler Admin Portlet</li> +<li>New WebContent 2 Framework for IFrames and Secure rendering of remote content</li> +<li>Jetspeed API now fully supports Java generics</li> +<li>Support Tomcat7 out of box as default application server</li> +<li>New User Browser supporting large user data sets</li> +<li>Added support for Anding PSML Security constraints</li> +<li>Upgrading all JAR dependencies to latest versions</li> +<li>Set default compiler to Java 1.7</li> +<li>Improved Portlet Preferences and Security Caching</li> +<li>Upgrade Jetspeed to Servlet Spec 3.0</li> +<li>Upgrade Jetspeed to Portlet Spec 2.1.0</li> +</ul> +</p> +</div> +<div class="section"><h3><a name="New_Features_for_2.2.2"></a>New Features for 2.2.2</h3> <p> Overview of new features in version 2.2.2: - <ul><li>Many JetUI improvements, see also <a href="http://portals.apache.org/jetspeed-2/deployguide/guide-jetui.html"; class="externalLink">Intoduction to JetUI</a></li> -<li>Portlet Cloning: allow site editors to quickly create new portlet variants based on modified preference and other descriptor settings: <a href="http://issues.apache.org/jira/browse/JS2-1232"; class="externalLink">JS2-1232</a></li> -<li>Support for bulk migration of DBPSML based installations from 2.1.X to 2.2.X: <a href="http://issues.apache.org/jira/browse/JS2-1127"; class="externalLink">JS2-1127</a></li> -<li>Admin roles security restriction on admin roles maintenance: <a href="http://issues.apache.org/jira/browse/JS2-915"; class="externalLink">JS2-915</a></li> -<li>Enforced portlet level security constraints checking at render time through custom jetspeed-portlet.xml metadata: <a href="http://issues.apache.org/jira/browse/JS2-1262"; class="externalLink">JS2-1262</a></li> -<li>Apache Solr based portlet search engine: <a href="http://issues.apache.org/jira/browse/JS2-1246"; class="externalLink">JS2-1246</a></li> -</ul> -</p> -</div> -<div class="section"><h3><a name="New_Features_for_2.2.1"></a>New Features for 2.2.1</h3> + <ul><li>Many JetUI improvements, see also <a class="externalLink" href="http://portals.apache.org/jetspeed-2/deployguide/guide-jetui.html";>Intoduction to JetUI</a></li> +<li>Portlet Cloning: allow site editors to quickly create new portlet variants based on modified preference and other descriptor settings: <a class="externalLink" href="http://issues.apache.org/jira/browse/JS2-1232";>JS2-1232</a></li> +<li>Support for bulk migration of DBPSML based installations from 2.1.X to 2.2.X: <a class="externalLink" href="http://issues.apache.org/jira/browse/JS2-1127";>JS2-1127</a></li> +<li>Admin roles security restriction on admin roles maintenance: <a class="externalLink" href="http://issues.apache.org/jira/browse/JS2-915";>JS2-915</a></li> +<li>Enforced portlet level security constraints checking at render time through custom jetspeed-portlet.xml metadata: <a class="externalLink" href="http://issues.apache.org/jira/browse/JS2-1262";>JS2-1262</a></li> +<li>Apache Solr based portlet search engine: <a class="externalLink" href="http://issues.apache.org/jira/browse/JS2-1246";>JS2-1246</a></li> +</ul> +</p> +</div> +<div class="section"><h3><a name="New_Features_for_2.2.1"></a>New Features for 2.2.1</h3> <p> Overview of new features in version 2.2.1: - <ul><li>Jetui Client Side Customization Engine</li> -<li>Drag and Drop Support of portlets</li> -<li>Jetspeed Toolbox dockable portlet selector, layout selector, and skin selector</li> -<li>Dockable Jetspeed Navigator to navigate over spaces, maintenance over pages, folders, links</li> -<li>Jetspeed Spaces, secured areas of the portal site for workgroups and projects</li> -<li>JAX RS Services for Portal Customization and Registry manipulations</li> -<li>Open ID Support</li> -<li>Preview Portlet Mode from Jetspeed Toolbox</li> -<li>Improved LDAP synchronization, authentication, and maintenance of LDAP credentials</li> -<li>CAS Authentication</li> -<li>Dynamic PSML - dynamically overlay external site maps such as other web sites or content repositories onto the Jetspeed site map to dynamically navigate of external content within portal</li> -<li>PSML Templates - templacized, secured pages that overlay over URL addressable pages to merge template-portlets such as toolbox and navigator into a single page</li> -<li>Fragment References - also known as Portlet Instances - allow for referencing preconfigured portlets with preferences from a standard page</li> -<li>Improved Portlet API 2.0 Support and Compliance</li> -<li>Improved Installer to support two kinds of installations (min, demo)</li> -<li>New User Manager supporting true paging over large user databases</li> -</ul> -</p> -</div> -<div class="section"><h3><a name="New_Features_for_2.2.0"></a>New Features for 2.2.0</h3> + <ul><li>Jetui Client Side Customization Engine</li> +<li>Drag and Drop Support of portlets</li> +<li>Jetspeed Toolbox dockable portlet selector, layout selector, and skin selector</li> +<li>Dockable Jetspeed Navigator to navigate over spaces, maintenance over pages, folders, links</li> +<li>Jetspeed Spaces, secured areas of the portal site for workgroups and projects</li> +<li>JAX RS Services for Portal Customization and Registry manipulations</li> +<li>Open ID Support</li> +<li>Preview Portlet Mode from Jetspeed Toolbox</li> +<li>Improved LDAP synchronization, authentication, and maintenance of LDAP credentials</li> +<li>CAS Authentication</li> +<li>Dynamic PSML - dynamically overlay external site maps such as other web sites or content repositories onto the Jetspeed site map to dynamically navigate of external content within portal</li> +<li>PSML Templates - templacized, secured pages that overlay over URL addressable pages to merge template-portlets such as toolbox and navigator into a single page</li> +<li>Fragment References - also known as Portlet Instances - allow for referencing preconfigured portlets with preferences from a standard page</li> +<li>Improved Portlet API 2.0 Support and Compliance</li> +<li>Improved Installer to support two kinds of installations (min, demo)</li> +<li>New User Manager supporting true paging over large user databases</li> +</ul> +</p> +</div> +<div class="section"><h3><a name="New_Features_for_2.2.0"></a>New Features for 2.2.0</h3> <p> Overview of new features in version 2.2.0: - <ul><li>Portlet API 2.0 Support and Compliance</li> -<li>Inter-Portlet Communication via Events</li> -<li>New High Speed Preferences Database Storage</li> -<li>New Extensible Security Model with LDAP Synchronization</li> -<li>Improved Documentation including 5 New Guides (Users Guide, Admin Guide, Developers Guide, Build Guide, Deploy Guide)</li> -<li>New Improved Administrative Portlets</li> -<li>New Skins</li> -<li>New Maven-2 Custom Build</li> -<li>Improved integration support for popular web development frameworks like Wicket, Spring MVC, and JSF</li> -<li>EAR deployment on Websphere 6.1</li> -</ul> -</p> -</div> -<div class="section"><h3><a name="Standardized"></a>Standardized</h3> -<ul><li>Fully compliant with Java Portlet API Standard 2.0 (JSR 286)</li> -<li>Fully compliant with Java Portlet API Standard 1.0 (JSR 168)</li> -<li>Passed JSR-168 TCK Compatibility Test Suite</li> -<li>Passed JSR-286 TCK Compatibility Test Suite</li> -<li>J2EE Security based on JAAS Standard, JAAS DB Portal Security Policy</li> -<li>LDAP Support for User Authentication</li> -<li>Implements and fully Supports Portlet Events and other standardized inter-portlet communication features of the Portlet API 2.0</li> -</ul> -</div> -<div class="section"><h3><a name="Portal_Engine_Features"></a>Portal Engine Features</h3> -<ul><li>The Jetspeed Portal - Server-Side Parallel JSR-168/286 Portlet Rendering Engine</li> -<li>The Jetspeed Desktop - Web 2.0 Client-Side JSR-168/286 Portlet Rendering Engine</li> -<li>Full Support for JSR-168/286 Portlet Caching and per portlet cache configuration</li> -<li>Portlet Timeout Tracking with mimimal render time limits</li> -<li>Portlet Service Manager for automated removal of slow or dead portlets.</li> -<li>Parallel rendering on Websphere 6.1</li> -<li>New Fast Preferences Engine with version 2.2.0</li> -</ul> -</div> -<div class="section"><h3><a name="Customization_Features"></a>Customization Features</h3> -<ul><li>Portal Page Customizer</li> -<li>Desktop Page Customizer</li> -<li>Nested Fragment Customization</li> -<li>Drag and drop moving of portlets</li> -<li>Resizing of desktop portlet windows</li> -<li>Portlet Selector with Portlet Categorizations, Full-Text Search of Portlets</li> -<li>Customizable Themes (Skins)</li> -</ul> -</div> -<div class="section"><h3><a name="Security"></a>Security</h3> -<ul><li>New Extensible Security Model with version 2.2.0</li> -<li>Portlet-level Security checks based on Security Constraints or Security Permissions</li> -<li>Declarative Security Constraints and JAAS Database Security Policy</li> -<li>Fully swappable Security Constraint or Security Permission support</li> -<li>Jetspeed SSO (Single Sign-on)</li> -<li>Delegation of Security</li> -<li>Administrative actions logged to Audit Activity database</li> -<li>LDAP Synchronization</li> -</ul> -</div> -<div class="section"><h3><a name="Distributed_Cluster_Support"></a>Distributed Cluster Support</h3> -<ul><li>Jetspeed Distributed Cluster - support for distributed deployments of the portal on multiple application server platforms</li> -<li>Distributed Cache for portal components including preferences, registry and portlet entities.</li> -<li>Distributed invalidation of portlet cache</li> -</ul> -</div> -<div class="section"><h3><a name="Foundation_Component_Architecture"></a>Foundation Component Architecture</h3> -<ul><li>Spring-based Components and Scalable Architecture</li> -<li>Configurable Pipeline Request Processor</li> -<li>Auto Deployment of Portlet Applications</li> -<li>Jetspeed Component Java API</li> -<li>Jetspeed AJAX XML API</li> + <ul><li>Portlet API 2.0 Support and Compliance</li> +<li>Inter-Portlet Communication via Events</li> +<li>New High Speed Preferences Database Storage</li> +<li>New Extensible Security Model with LDAP Synchronization</li> +<li>Improved Documentation including 5 New Guides (Users Guide, Admin Guide, Developers Guide, Build Guide, Deploy Guide)</li> +<li>New Improved Administrative Portlets</li> +<li>New Skins</li> +<li>New Maven-2 Custom Build</li> +<li>Improved integration support for popular web development frameworks like Wicket, Spring MVC, and JSF</li> +<li>EAR deployment on Websphere 6.1</li> +</ul> +</p> +</div> +<div class="section"><h3><a name="Standardized"></a>Standardized</h3> +<ul><li>Fully compliant with Java Portlet API Standard 2.0 (JSR 286)</li> +<li>Fully compliant with Java Portlet API Standard 1.0 (JSR 168)</li> +<li>Passed JSR-168 TCK Compatibility Test Suite</li> +<li>Passed JSR-286 TCK Compatibility Test Suite</li> +<li>J2EE Security based on JAAS Standard, JAAS DB Portal Security Policy</li> +<li>LDAP Support for User Authentication</li> +<li>Implements and fully Supports Portlet Events and other standardized inter-portlet communication features of the Portlet API 2.0</li> +</ul> +</div> +<div class="section"><h3><a name="Portal_Engine_Features"></a>Portal Engine Features</h3> +<ul><li>The Jetspeed Portal - Server-Side Parallel JSR-168/286 Portlet Rendering Engine</li> +<li>The Jetspeed Desktop - Web 2.0 Client-Side JSR-168/286 Portlet Rendering Engine</li> +<li>Full Support for JSR-168/286 Portlet Caching and per portlet cache configuration</li> +<li>Portlet Timeout Tracking with mimimal render time limits</li> +<li>Portlet Service Manager for automated removal of slow or dead portlets.</li> +<li>Parallel rendering on Websphere 6.1</li> +<li>New Fast Preferences Engine with version 2.2.0</li> +</ul> +</div> +<div class="section"><h3><a name="Customization_Features"></a>Customization Features</h3> +<ul><li>Portal Page Customizer</li> +<li>Desktop Page Customizer</li> +<li>Nested Fragment Customization</li> +<li>Drag and drop moving of portlets</li> +<li>Resizing of desktop portlet windows</li> +<li>Portlet Selector with Portlet Categorizations, Full-Text Search of Portlets</li> +<li>Customizable Themes (Skins)</li> +</ul> +</div> +<div class="section"><h3><a name="Security"></a>Security</h3> +<ul><li>New Extensible Security Model with version 2.2.0</li> +<li>Portlet-level Security checks based on Security Constraints or Security Permissions</li> +<li>Declarative Security Constraints and JAAS Database Security Policy</li> +<li>Fully swappable Security Constraint or Security Permission support</li> +<li>Jetspeed SSO (Single Sign-on)</li> +<li>Delegation of Security</li> +<li>Administrative actions logged to Audit Activity database</li> +<li>LDAP Synchronization</li> +</ul> +</div> +<div class="section"><h3><a name="Distributed_Cluster_Support"></a>Distributed Cluster Support</h3> +<ul><li>Jetspeed Distributed Cluster - support for distributed deployments of the portal on multiple application server platforms</li> +<li>Distributed Cache for portal components including preferences, registry and portlet entities.</li> +<li>Distributed invalidation of portlet cache</li> +</ul> +</div> +<div class="section"><h3><a name="Foundation_Component_Architecture"></a>Foundation Component Architecture</h3> +<ul><li>Spring-based Components and Scalable Architecture</li> +<li>Configurable Pipeline Request Processor</li> +<li>Auto Deployment of Portlet Applications</li> +<li>Jetspeed Component Java API</li> +<li>Jetspeed AJAX XML API</li> <li>PSML: Extended Portlet Site Markup Language - <ul><li>Database Persistent</li> -<li>Content Management Facilities</li> -<li>Security Constraints</li> -</ul> -</li> -<li>Full security maintenance using LDAP is now supported for many LDAP providers</li> -</ul> -</div> -<div class="section"><h3><a name="Portal_Core_Features"></a>Portal Core Features</h3> -<ul><li>Runtime Portlet API Standard Role-based Security</li> -<li>Portal Content Management and Navigations: Pages, Menus, Folders, Links</li> -<li>PSML Folder CMS Navigations, Menus, Links</li> -<li>Rules-based Profiler for page and resource location</li> -<li>Role-based Aggregation of Visible Pages</li> -<li>Integrates with most popular databases including Derby, MySQL, MS SQL, Postgres, Oracle, DB2</li> -<li>Client independent capability engine (html, xhtml, wml,vml)</li> -<li>Support for Pocket PC</li> -<li>Internationalization: Localized Portal Resources in 12 Languages</li> -<li>Statistics Logging Engine</li> -<li>Portlet Registry</li> -<li>Full Text Search of Portlet Resources with Lucene</li> -<li>User Registration</li> -<li>Forgotten Password</li> -<li>Rich Login and Password Configuration Management</li> -</ul> -</div> -<div class="section"><h3><a name="Administrative_Portlets"></a>Administrative Portlets</h3> -<ul><li>User, Role, Group, Password, and Profile Management</li> -<li>Portal Site Manager</li> -<li>Remote Portal Application Deployer (RPAD) - hot deploy portlet applications from remote locations on the Web</li> -<li>JSR 168 Generic User Attributes Editor</li> -<li>JSR 168 Preferences Editor</li> -<li>SSO Manager</li> -<li>Permission Management (JAAS Security)</li> -<li>Security Constraints Management</li> -<li>Portlet Application and Lifecycle Management</li> -<li>Profiler Administration</li> -<li>Statistics Reports</li> -<li>Portlet Out of Service Manager</li> -<li>PSML and XML Import / Export Admin Portlet</li> -<li>Cache Manager</li> -</ul> -</div> -<div class="section"><h3><a name="Web_Framework_Support_and_Sample_Portlets"></a>Web Framework Support and Sample Portlets</h3> -<ul><li>Bridges to other Web Frameworks: Wicket, JSF, Groovy, Struts, PHP, Perl, Velocity</li> + <ul><li>Database Persistent</li> +<li>Content Management Facilities</li> +<li>Security Constraints</li> +</ul> +</li> +<li>Full security maintenance using LDAP is now supported for many LDAP providers</li> +</ul> +</div> +<div class="section"><h3><a name="Portal_Core_Features"></a>Portal Core Features</h3> +<ul><li>Runtime Portlet API Standard Role-based Security</li> +<li>Portal Content Management and Navigations: Pages, Menus, Folders, Links</li> +<li>PSML Folder CMS Navigations, Menus, Links</li> +<li>Rules-based Profiler for page and resource location</li> +<li>Role-based Aggregation of Visible Pages</li> +<li>Integrates with most popular databases including Derby, MySQL, MS SQL, Postgres, Oracle, DB2</li> +<li>Client independent capability engine (html, xhtml, wml,vml)</li> +<li>Support for Pocket PC</li> +<li>Internationalization: Localized Portal Resources in 12 Languages</li> +<li>Statistics Logging Engine</li> +<li>Portlet Registry</li> +<li>Full Text Search of Portlet Resources with Lucene</li> +<li>User Registration</li> +<li>Forgotten Password</li> +<li>Rich Login and Password Configuration Management</li> +</ul> +</div> +<div class="section"><h3><a name="Administrative_Portlets"></a>Administrative Portlets</h3> +<ul><li>User, Role, Group, Password, and Profile Management</li> +<li>Portal Site Manager</li> +<li>Remote Portal Application Deployer (RPAD) - hot deploy portlet applications from remote locations on the Web</li> +<li>JSR 168 Generic User Attributes Editor</li> +<li>JSR 168 Preferences Editor</li> +<li>SSO Manager</li> +<li>Permission Management (JAAS Security)</li> +<li>Security Constraints Management</li> +<li>Portlet Application and Lifecycle Management</li> +<li>Profiler Administration</li> +<li>Statistics Reports</li> +<li>Portlet Out of Service Manager</li> +<li>PSML and XML Import / Export Admin Portlet</li> +<li>Cache Manager</li> +</ul> +</div> +<div class="section"><h3><a name="Web_Framework_Support_and_Sample_Portlets"></a>Web Framework Support and Sample Portlets</h3> +<ul><li>Bridges to other Web Frameworks: Wicket, JSF, Groovy, Struts, PHP, Perl, Velocity</li> <li>Sample Portlets: - <ul><li>RSS, IFrame, Calendar XSLT, Struts Petstore, Bookmark, Database Browser</li> -<li>Integration with Display Tags, Spring MVC</li> -</ul> -</li> -</ul> -</div> -<div class="section"><h3><a name="Data_Migration_Features"></a>Data Migration Features</h3> -<ul><li>XML Import/Export Utility for all Jetspeed database data to support data migration over versions</li> -<li>All initial portal data seeded with XML</li> -<li>XML Schemas for all XML content</li> -</ul> -</div> -<div class="section"><h3><a name="Portal_Design_Features"></a>Portal Design Features</h3> -<ul><li>Deployment Jetspeed Portlet and Page Skins (Decorators) CSS Components</li> -<li>Configurable CSS Page Layouts</li> -<li>Easy to Use Velocity Macro Language for Skin and Layout Components</li> -</ul> -</div> -<div class="section"><h3><a name="Development_Tools"></a>Development Tools</h3> -<ul><li>Ant-based Installer</li> -<li>Tutorial</li> -<li>Automated Maven-2 Build</li> -<li>Jetspeed-2 Maven Plugin for Custom Portal Development</li> -<li>Maven-2 Profiles and Archetypes</li> -<li>AutoDeployment of Portlet Applications, Portal Resources</li> -<li>Deployment Tools</li> -<li>Plugin Goals integrated with Auto Deployment Feature</li> -<li>XML Schemas for PSML, jetspeed-portlet.xml, and Jetspeed XML (seed data)</li> -<li>Fully compatible and tested with Wicket, JSF and Spring MVC</li> -</ul> -</div> -<div class="section"><h3><a name="Extended_JSR-168286_Features"></a>Extended JSR-168/286 Features</h3> -<ul><li>Custom Portlet Modes and Window States: <b>Edit Defaults, Configure, Print, About</b></li> -<li>Custom Window States: <b>Solo</b></li> -<li>Dynamically hide Portlets at request time</li> -<li>Maximize on Edit Defaults or Edit modes option</li> -<li>Preliminary Portlet API 2.0 ResourceURL support providing full response control for JSR-168 based portlets</li> -</ul> -</div> -<div class="section"><h3><a name="Other_Features"></a>Other Features</h3> -<ul><li>Installation choice of either Demo Portal or Minimal Starter Portal</li> -<li>In-depth Jetspeed 2 Tutorial</li> -<li>Documentation Guides: Users Guide, Admin Guide, Developers Guide, Build Guide, Deploy Guide</li> -</ul> -</div> -<div class="section"><h3><a name="Application_Servers_Supported"></a>Application Servers Supported</h3> -<ul><li>Tomcat 6</li> -<li>Jetty</li> -<li>Websphere 6.0</li> -<li>Geronimo</li> -<li>JBoss</li> -<li>Weblogic</li> -</ul> -</div> -</div> + <ul><li>RSS, IFrame, Calendar XSLT, Struts Petstore, Bookmark, Database Browser</li> +<li>Integration with Display Tags, Spring MVC</li> +</ul> +</li> +</ul> +</div> +<div class="section"><h3><a name="Data_Migration_Features"></a>Data Migration Features</h3> +<ul><li>XML Import/Export Utility for all Jetspeed database data to support data migration over versions</li> +<li>All initial portal data seeded with XML</li> +<li>XML Schemas for all XML content</li> +</ul> +</div> +<div class="section"><h3><a name="Portal_Design_Features"></a>Portal Design Features</h3> +<ul><li>Deployment Jetspeed Portlet and Page Skins (Decorators) CSS Components</li> +<li>Configurable CSS Page Layouts</li> +<li>Easy to Use Velocity Macro Language for Skin and Layout Components</li> +</ul> +</div> +<div class="section"><h3><a name="Development_Tools"></a>Development Tools</h3> +<ul><li>Ant-based Installer</li> +<li>Tutorial</li> +<li>Automated Maven-2 Build</li> +<li>Jetspeed-2 Maven Plugin for Custom Portal Development</li> +<li>Maven-2 Profiles and Archetypes</li> +<li>AutoDeployment of Portlet Applications, Portal Resources</li> +<li>Deployment Tools</li> +<li>Plugin Goals integrated with Auto Deployment Feature</li> +<li>XML Schemas for PSML, jetspeed-portlet.xml, and Jetspeed XML (seed data)</li> +<li>Fully compatible and tested with Wicket, JSF and Spring MVC</li> +</ul> +</div> +<div class="section"><h3><a name="Extended_JSR-168286_Features"></a>Extended JSR-168/286 Features</h3> +<ul><li>Custom Portlet Modes and Window States: <b>Edit Defaults, Configure, Print, About</b></li> +<li>Custom Window States: <b>Solo</b></li> +<li>Dynamically hide Portlets at request time</li> +<li>Maximize on Edit Defaults or Edit modes option</li> +<li>Preliminary Portlet API 2.0 ResourceURL support providing full response control for JSR-168 based portlets</li> +</ul> +</div> +<div class="section"><h3><a name="Other_Features"></a>Other Features</h3> +<ul><li>Installation choice of either Demo Portal or Minimal Starter Portal</li> +<li>In-depth Jetspeed 2 Tutorial</li> +<li>Documentation Guides: Users Guide, Admin Guide, Developers Guide, Build Guide, Deploy Guide</li> +</ul> +</div> +<div class="section"><h3><a name="Application_Servers_Supported"></a>Application Servers Supported</h3> +<ul><li>Tomcat 6</li> +<li>Jetty</li> +<li>Websphere 6.0</li> +<li>Geronimo</li> +<li>JBoss</li> +<li>Weblogic</li> +</ul> +</div> +</div> </div> </div> @@ -512,7 +512,7 @@ </div> <div id="footer"> <div class="xright">© - 2004-2016 + 2004-2022 Apache Software Foundation
Modified: portals/site-live/jetspeed-2/getting-started-installer.html URL: http://svn.apache.org/viewvc/portals/site-live/jetspeed-2/getting-started-installer.html?rev=1901428&r1=1901427&r2=1901428&view=diff ============================================================================== --- portals/site-live/jetspeed-2/getting-started-installer.html (original) +++ portals/site-live/jetspeed-2/getting-started-installer.html Tue May 31 02:15:08 2022 @@ -44,7 +44,7 @@ <div class="xleft"> - Last Published: 9 May 2016 + Last Published: 26 May 2022 </div> <div class="xright"> <a href="http://portals.apache.org/applications/"; class="externalLink">Applications</a> | @@ -255,49 +255,49 @@ </div> <div id="bodyColumn"> <div id="contentBox"> - <subtitle></subtitle><authors><person name="David Le Strat" email="[email protected]"><person name="David Taylor" email="[email protected]"></authors><div class="section"><h2><a name="Jetspeed_2_Installer"></a>Jetspeed 2 Installer</h2> -<div class="section"><h3><a name="Getting_Started_with_the_Installer"></a>Getting Started with the Installer</h3> + <subtitle></subtitle><authors><person name="David Le Strat" email="[email protected]"><person name="David Taylor" email="[email protected]"></authors><div class="section"><h2><a name="Jetspeed_2_Installer"></a>Jetspeed 2 Installer</h2> +<div class="section"><h3><a name="Getting_Started_with_the_Installer"></a>Getting Started with the Installer</h3> <p> With version 2.2.1+, there is now only one installer (previous releases had two installers). From the installation program, you can choose either the demo or minimal installation. The demo option is best for seeing more features, capabilities, and demo portlet applications. The minimal option could be useful for basing your own custom-portal distribution upon, or just seeing the basic feature set of Jetspeed. - <ol type="1"><li>Minimal Installer Option - only contains a Jetspeed Portal and the Jetspeed Administrative Portlets, with a minimal Site map and set of users</li> + <ol type="1"><li>Minimal Installer Option - only contains a Jetspeed Portal and the Jetspeed Administrative Portlets, with a minimal Site map and set of users</li> <li>Full or Demo Option - contains a Jetspeed Portal, the Jetspeed Administrative Portlets, a full demo Site Map, 10 users. Additionally, there several portlet applications including an RSS application, a Database Browser application, a Web Content application, and a set of demo portlets including Google Maps, weather portlets, and lots of programming examples to get you started. - </li> -</ol> -<p>The installer contains both options, and can be downloaded here:</p> -<br /> -<br /> -<a href="http://www.apache.org/dyn/closer.cgi/portals/jetspeed-2/binaries/jetspeed-installer-2.3.1.jar"; class="externalLink">Jetspeed Installer</a><br /> -<br /> -</p> + </li> +</ol> +<p>The installer contains both options, and can be downloaded here:</p> +<br /> +<br /> +<a class="externalLink" href="http://www.apache.org/dyn/closer.cgi/portals/jetspeed-2/binaries/jetspeed-installer-2.3.1.jar";>Jetspeed Installer</a><br /> +<br /> +</p> <p> To run the installer: - </p> + </p> <div class="source"><pre> java -jar jetspeed-installer-2.3.1.jar - </pre> -</div> + </pre> +</div> <p> - The installer is capable of running on headless (i.e. no gui) machines, and will detect so automatically.<br /> + The installer is capable of running on headless (i.e. no gui) machines, and will detect so automatically.<br /> To force the installer in text mode manually, pass in the <b><i>text</i></b> parameter: - </p> + </p> <div class="source"><pre> java -jar jetspeed-installer-2.3.1.jar text - </pre> -</div> + </pre> +</div> <p> After starting the installer and advancing through the splash and license pages, select the <code>Install Jetspeed Portal</code> installer operation and continue. The installer will then prompt for information required for the installation process. Documentation for the other installer operations used primarily for ETL migration can be found here: <a href="guide-etl-migration.html">ETL Migration Guide</a>. - </p> -</div> -<div class="section"><h3><a name="Database_Selection"></a>Database Selection</h3> + </p> +</div> +<div class="section"><h3><a name="Database_Selection"></a>Database Selection</h3> <p> The installer will ask you to choose a database for storing the Jetspeed database. We provide a default Derby database for demo systems. The Derby database runs in embedded mode inside the Jetspeed/Tomcat JVM. All other databases require additional configuration. @@ -305,110 +305,110 @@ java -jar jetspeed-installer-2.3.1.jar t For some databases this <i>area</i> is called a <i>catalog</i>, others call it a <i>schema</i>, while others call it a <i>database</i>. Consult your database documentation for details on how to create a catalog or schema to hold the Jetspeed tables. Additionally, you may need to create a database user to access the Jetspeed tables. Often it is required to grant access to the schemas (catalogs) for the given user. - </p> + </p> <p>Jetspeed supported database list: - <ul><li>DB2</li> -<li>Derby (default)</li> -<li>MS SQL</li> -<li>My SQL</li> -<li>PostgreSQL</li> -<li>Oracle (9i or higher)</li> -<li>SapDB</li> -<li>Manual database setup </li> -</ul> -</p> + <ul><li>DB2</li> +<li>Derby (default)</li> +<li>MS SQL</li> +<li>My SQL</li> +<li>PostgreSQL</li> +<li>Oracle (9i or higher)</li> +<li>SapDB</li> +<li>Manual database setup </li> +</ul> +</p> <p>If you choose the manual database setup, then the database scripts will not be run and you will need to configure the database manually after the installation. All database scripts are provided in the installation under the <i>database</i> directory. For your specific database, look for the corresponding directory name. During installation, you will be prompted for the following fields after chosing your database types (except for Derby): - <ul><li>A username</li> -<li>A password</li> -<li>A JDBC connection string</li> -<li>A JDBC driver name</li> -<li>The location of a valid JDBC driver. The installer will copy this driver to the installed location in Tomcat.</li> -</ul> + <ul><li>A username</li> +<li>A password</li> +<li>A JDBC connection string</li> +<li>A JDBC driver name</li> +<li>The location of a valid JDBC driver. The installer will copy this driver to the installed location in Tomcat.</li> +</ul> The connections strings are only partially completed in the well-known format of the particular databaes. Please take care to complete the values in your connection string for your database. The driver name should be the right driver class for your database at the time of the making of this installation. Please ensure that a newer driver is not required for your database. Note also that the location of the JDBC driver must be selected. We have not provided the file system path to the jar file but only the likely file name. You may want to check and see if newer versions of the driver are available. - </p> + </p> <p> Once you have entered all of your parameters, the installer will test the database connection before proceeding. If the connection fails, please go back to the connection configuration setup and provide the correct parameters. If you choose to continue, the database scripts will not be run and you will need to configure the database manually after the installation. Once the installer verifies the database connection, you are ready to proceed with installation process. - </p> + </p> <p> - Please take note of the location where you are installing on your file system.<br /> + Please take note of the location where you are installing on your file system.<br /> Also, on a Windows platform make sure to use a location path without spaces, e.g. <i>NOT</i> under C:\Program Files. - </p> -</div> -<div class="section"><h3><a name="Starting_Jetspeed-2"></a>Starting Jetspeed-2</h3> + </p> +</div> +<div class="section"><h3><a name="Starting_Jetspeed-2"></a>Starting Jetspeed-2</h3> <p> Once you have completed a successful install, you are ready to start the Jetspeed Portal. - On linux, here is an example where you have installed to the default location:<br /> + On linux, here is an example where you have installed to the default location:<br /> Note that the setting of CATALINA_OPTS is optional in the following examples. (See <a href="#Note_on_Permanent_Generation_Size_of_Your_JVM">Note on Permanent Generation Size of Your JVM</a> for detail.) - </p> + </p> <div class="source"><pre> $ cd ~/jetspeed-2.3.1/bin $ export CATALINA_OPTS="-Xmx512m -XX:MaxPermSize=128m" $ ./startup.sh - </pre> -</div> + </pre> +</div> <p> On windows, here is an example where you have installed to the default location: - </p> + </p> <div class="source"><pre> > cd C:\Apache\Jetspeed-2.3.1\bin > set CATALINA_OPTS="-Xmx512m -XX:MaxPermSize=128m" > startup.bat - </pre> -</div> + </pre> +</div> <p> The very first invocation of the portal requires anywhere from 10 seconds to 30 seconds for initial startup and final installation. After starting the server, start up a web browser - and navigate to <a href="http://localhost:8080/jetspeed/portal"; class="externalLink">http://localhost:8080/jetspeed/portal</a></p> -</div> -<div class="section"><h3><a name="Note_on_Permanent_Generation_Size_of_Your_JVM"></a>Note on Permanent Generation Size of Your JVM</h3> + and navigate to <a class="externalLink" href="http://localhost:8080/jetspeed/portal";>http://localhost:8080/jetspeed/portal</a></p> +</div> +<div class="section"><h3><a name="Note_on_Permanent_Generation_Size_of_Your_JVM"></a>Note on Permanent Generation Size of Your JVM</h3> <p><em>Note:</em> You may need to increase the permanent generation size of your JVM when there are a lot of Servlets, JSP's or when script portlets are used, in order to avoid <CODE>OutOfMemoryError</CODE> errors. By default, it is 64MB. Increasing it to be <CODE>-XX:MaxPermSize=128m</CODE> might be a good start. - Please see <a href="http://wiki.apache.org/tomcat/FAQ/Memory"; class="externalLink">http://wiki.apache.org/tomcat/FAQ/Memory</a> for detail. - </p> -</div> -<div class="section"><h3><a name="Login_to_Jetspeed-2"></a>Login to Jetspeed-2</h3> + Please see <a class="externalLink" href="http://wiki.apache.org/tomcat/FAQ/Memory";>http://wiki.apache.org/tomcat/FAQ/Memory</a> for detail. + </p> +</div> +<div class="section"><h3><a name="Login_to_Jetspeed-2"></a>Login to Jetspeed-2</h3> <p> All preconfigured users have the same password as username (for example the <i>admin</i> user has the password <i>admin</i>) If you installed with the Minimal option on installation, one test account are available: - </p> + </p> <div class="source"><pre> admin -- System administrator, super user - </pre> -</div> + </pre> +</div> <p> If you installed with the Demo option upon installation, several additional test accounts are available: - </p> + </p> <div class="source"><pre> admin -- System administrator, super user debbie -- example user with the developer role in the engineering group manny -- example user with the devmgr role in the engineering group, also demonstrates a delegated security manager, can manage users with the "dev" (developer) role, see home page of this user bill -- example user with the executive role in the finance and marketing groups martha -- example user with the marketing role in the marketing group - </pre> -</div> -</div> -<div class="section"><h3><a name="Changing_the_Database"></a>Changing the Database</h3> + </pre> +</div> +</div> +<div class="section"><h3><a name="Changing_the_Database"></a>Changing the Database</h3> <p> After running the installation, you can manually reinitialize the database or even switch to another database. To do so, we provide an Ant script found under the <i>database</i> directory of your installed Jetspeed portal. The database configuration is defined in the <i>database.properties</i> file. To reinitialize or change the database, go to the database directory and edit the database.properties file, save it, and then run <b><i>ant</i></b>. - </p> + </p> <p>Here is a sample database configuration file: - </p> + </p> <div class="source"><pre> ; Jetspeed Enterprise Portal 2.1 Database setup configuration ; db.type supported values: db2, derby, mssql, mysql, oracle, postgres, sapdb @@ -418,14 +418,14 @@ db.username=j2 db.password=abracadabra jdbc.url=jdbc:mysql://localhost:3306/prod-2 jdbc.driver.class=com.mysql.jdbc.Driver - </pre> -</div> + </pre> +</div> <p>If you are configuring a database for the first time after choosing Manual database setup in the installer, or want to try out - a different type of database, make sure to copy the specific JDBC driver for the database to the Tomcat shared/lib folder <i>before</i> running ant.<br /> + a different type of database, make sure to copy the specific JDBC driver for the database to the Tomcat shared/lib folder <i>before</i> running ant.<br /> - Note: for Derby, the needed driver is already placed there or available from the database/lib directory of your installed Jetspeed portal.</p> -</div> -</div> + Note: for Derby, the needed driver is already placed there or available from the database/lib directory of your installed Jetspeed portal.</p> +</div> +</div> </div> </div> @@ -434,7 +434,7 @@ jdbc.driver.class=com.mysql.jdbc.Driver </div> <div id="footer"> <div class="xright">© - 2004-2016 + 2004-2022 Apache Software Foundation Modified: portals/site-live/jetspeed-2/getting-started.html URL: http://svn.apache.org/viewvc/portals/site-live/jetspeed-2/getting-started.html?rev=1901428&r1=1901427&r2=1901428&view=diff ============================================================================== --- portals/site-live/jetspeed-2/getting-started.html (original) +++ portals/site-live/jetspeed-2/getting-started.html Tue May 31 02:15:08 2022 @@ -42,7 +42,7 @@ <div class="xleft"> - Last Published: 9 May 2016 + Last Published: 26 May 2022 </div> <div class="xright"> <a href="http://portals.apache.org/applications/"; class="externalLink">Applications</a> | @@ -253,146 +253,146 @@ </div> <div id="bodyColumn"> <div id="contentBox"> - <subtitle></subtitle><authors><person name="David Sean Taylor" email="[email protected]"></authors><div class="section"><h2><a name="Requirements"></a>Requirements</h2> + <subtitle></subtitle><authors><person name="David Sean Taylor" email="[email protected]"></authors><div class="section"><h2><a name="Requirements"></a>Requirements</h2> <p> System Requirements to Run Jetspeed 2.3.1: - <ul><li>Java 1.7 or higher installed</li> + <ul><li>Java 1.7 or higher installed</li> <li>a database is optional, the Jetspeed installer comes with a built-in database (Derby). For production system recommend providing your own maintained database - Supported Databases: (MySQL, Oracle, Postgres, DB2, Sybase, SQL Server, Derby, HSQL)</li> -<li>100 MB free disk space</li> -</ul> -</p> -<p><a href="#cb1">System Requirements to Build and Develop with Jetspeed 2.3.1</a></p> -</div> -<div class="section"><h2><a name="Where_do_I_start"></a>Where do I start?</h2> + Supported Databases: (MySQL, Oracle, Postgres, DB2, Sybase, SQL Server, Derby, HSQL)</li> +<li>100 MB free disk space</li> +</ul> +</p> +<p><a href="#cb1">System Requirements to Build and Develop with Jetspeed 2.3.1</a></p> +</div> +<div class="section"><h2><a name="Where_do_I_start"></a>Where do I start?</h2> <p>Where you start depends on what you plan on doing with Jetspeed. Its always best to start by reading the documentation guides. There are several guides provided: - </p> + </p> <ul><li><a href="usersguide/index.html"> Users Guide - </a></li> + </a></li> <li><a href="adminguide/index.html"> Administrators Guide - </a></li> + </a></li> <li><a href="deployguide/index.html"> Deployment and Configuration Guide - </a></li> + </a></li> <li><a href="devguide/index.html"> Developers Guide - </a></li> + </a></li> <li><a href="buildguide/index.html"> Build Guide - </a></li> -</ul> + </a></li> +</ul> <p> For those of you in more of a hurry to get started, you have the choice of installing Jetspeed from a binary release or doing more indepth open source development by working with the - source code.</p> + source code.</p> <p>If you want to modify the core functionality of Jetspeed or contribute to the development of Jetspeed, you need to work with the source code. If you are interested in building your first custom enterprise portal, try the custom build. We recommend trying an Evaluation (demo, download) to get started. Eventually you will want to move on to Building a Custom Portal. Advanced users will want to learn how to build from source. - </p> -<ul><li><a href="#Evaluating">Evaluation</a></li> -<li><a href="#cb1">Building a Custom Portal</a></li> -<li><a href="#bfs1">Building Jetspeed from Source</a></li> -</ul> -</div> -<div class="section"><h2><a name="Evaluating"></a>Evaluating</h2> + </p> +<ul><li><a href="#Evaluating">Evaluation</a></li> +<li><a href="#cb1">Building a Custom Portal</a></li> +<li><a href="#bfs1">Building Jetspeed from Source</a></li> +</ul> +</div> +<div class="section"><h2><a name="Evaluating"></a>Evaluating</h2> <p> If you are evaluating Jetspeed, best to download the latest distribution or try running Jetspeed from the demo site: - <ul><li><a href="download.html">Download Jetspeed</a></li> -<li><a href="demo.html">Jetspeed Online Demos</a></li> -</ul> -</p> -<p><b>Download Requirements</b> - The requirements for the downloadable distribution are: Java 1.5 or higher, enough memory to run Tomcat with several web apps (the demo comes with Tomcat embedded in the installer)</p> -<p><b>Online Demo Requirements</b> - The requirements for the online demos are minimal: just a web browser</p> -</div> -<div id="cb1"><div class="section"><h2><a name="Custom_Build"></a>Custom Build</h2> + <ul><li><a href="download.html">Download Jetspeed</a></li> +<li><a href="demo.html">Jetspeed Online Demos</a></li> +</ul> +</p> +<p><b>Download Requirements</b> - The requirements for the downloadable distribution are: Java 1.5 or higher, enough memory to run Tomcat with several web apps (the demo comes with Tomcat embedded in the installer)</p> +<p><b>Online Demo Requirements</b> - The requirements for the online demos are minimal: just a web browser</p> +</div> +<div id="cb1"><div class="section"><h2><a name="Custom_Build"></a>Custom Build</h2> <p> When starting a new Jetspeed portal project, we strongly recommend that you create a custom portal project, and do not edit the Jetspeed-2 source and resources directly. A custom build allows you to create and maintain a Jetspeed Portal's lifecycle. With a custom build, you have a reproducible procedure for maintaining your portal across future versions. When we say custom, we mean customizing Jetspeed for your needs. Everyone has custom requirements. Custom build procedures formalize the steps required to create a custom portal. Although Jetspeed can be customized online using the portal customization features. Still, having a reproducible build is valuable as it enables you to store artifacts in a source code repository and maintain the life-cycle of this source. -</p> +</p> <p> Custom Jetspeed builds for version 2.3.1 are built with Maven-3 only. (The Maven-1 custom build is no longer supported.) Building Jetspeed from source is not necessary for most projects. -</p> -<div class="section"><h3><a name="Maven_Custom_Build"></a>Maven Custom Build</h3> +</p> +<div class="section"><h3><a name="Maven_Custom_Build"></a>Maven Custom Build</h3> <p>The Maven Custom Build is based on a Maven plugin. To get started with the Maven plugin, see the documentation here: -<ul><li><a href="buildguide/maven-2-build.html">Maven Jetspeed Build Getting Started</a></li> -<li><a href="buildguide/jetspeed-archetype.html">Maven Jetspeed Archetype</a></li> -</ul> -</p> -</div> -<div class="section"><h3><a name="Requirements_for_Custom_Builds"></a>Requirements for Custom Builds</h3> +<ul><li><a href="buildguide/maven-2-build.html">Maven Jetspeed Build Getting Started</a></li> +<li><a href="buildguide/jetspeed-archetype.html">Maven Jetspeed Archetype</a></li> +</ul> +</p> +</div> +<div class="section"><h3><a name="Requirements_for_Custom_Builds"></a>Requirements for Custom Builds</h3> <p> General requirements for custom builds: -</p> -<ul><li>Java 7</li> -<li>Maven 3.3.1</li> +</p> +<ul><li>Java 7</li> +<li>Maven 3.3.1</li> <li> Servlet 3.0 (or higher) Engine: - <ul><li><a href="deployguide/guide-tomcat.html">Tomcat 7</a></li> -<li><a href="deployguide/deploying-jetspeed-to-websphere.html">Websphere 6.0</a></li> -</ul> + <ul><li><a href="deployguide/guide-tomcat.html">Tomcat 7</a></li> +<li><a href="deployguide/deploying-jetspeed-to-websphere.html">Websphere 6.0</a></li> +</ul> Jetspeed 2 portals can be run under any servlet container supporting the 2.4 specification or greater. However we don't have documentation listed for all servers. Contributions welcome! - </li> + </li> <li>A Database Jetspeed's security model requires a database to authorize users and to retain the user information. Jetspeed security should work with any JDBC 2.0 compliant driver. The following databases are tested: - <ul><li>Derby</li> -<li>HSQLDB - Hypersonic SQL</li> -<li>MySQL</li> -<li>Oracle</li> -<li>Postgres</li> -<li>DB2</li> -<li>Sybase</li> -<li>SQL Server</li> -</ul> + <ul><li>Derby</li> +<li>HSQLDB - Hypersonic SQL</li> +<li>MySQL</li> +<li>Oracle</li> +<li>Postgres</li> +<li>DB2</li> +<li>Sybase</li> +<li>SQL Server</li> +</ul> <p> Jetspeed is distributed with the Derby database configured as the default. - </p> + </p> <p> The database configuration will be setup during the custom build process based on your property settings. See the appropriate build guide for details.. If you are not going to use the default Derby database, you need to select another database during your build configuration. - </p> -</li> -</ul> -</div> -</div> -<div id="bfs1"><div class="section"><h2><a name="Building_from_Source"></a>Building from Source</h2> + </p> +</li> +</ul> +</div> +</div> +<div id="bfs1"><div class="section"><h2><a name="Building_from_Source"></a>Building from Source</h2> <p> Building from Source is covered in the Developer guide. We build Jetspeed with Maven-2. - </p> -<div class="section"><h3><a name="Building_from_Source_with_Maven-2"></a>Building from Source with Maven-2</h3> -<p>The best place to start using Jetspeed, as a Developer, is to go to the developers guide documentation:</p> -<p><a href="devguide/index.html">Jetspeed Developers Guide</a></p> -<p>For general build information, also see the Jetspeed Build Guide:</p> + </p> +<div class="section"><h3><a name="Building_from_Source_with_Maven-2"></a>Building from Source with Maven-2</h3> +<p>The best place to start using Jetspeed, as a Developer, is to go to the developers guide documentation:</p> +<p><a href="devguide/index.html">Jetspeed Developers Guide</a></p> +<p>For general build information, also see the Jetspeed Build Guide:</p> <ul><li><a href="buildguide/index.html"> Building and developing Jetspeed-2 using Maven-2 - </a></li> + </a></li> <li><a href="buildguide/maven-2-build.html"> Building jetspeed from Source - </a></li> + </a></li> <li><a href="buildguide/jetspeed-maven-plugins.html"> Jetspeed Maven-2 Plugin Guide - </a></li> -</ul> -</div> -</div> + </a></li> +</ul> +</div> +</div> </div> </div> @@ -401,7 +401,7 @@ General requirements for custom builds: </div> <div id="footer"> <div class="xright">© - 2004-2016 + 2004-2022 Apache Software Foundation Modified: portals/site-live/jetspeed-2/guide-etl-migration.html URL: http://svn.apache.org/viewvc/portals/site-live/jetspeed-2/guide-etl-migration.html?rev=1901428&r1=1901427&r2=1901428&view=diff ============================================================================== --- portals/site-live/jetspeed-2/guide-etl-migration.html (original) +++ portals/site-live/jetspeed-2/guide-etl-migration.html Tue May 31 02:15:08 2022 @@ -42,7 +42,7 @@ <div class="xleft"> - Last Published: 9 May 2016 + Last Published: 26 May 2022 </div> <div class="xright"> <a href="http://portals.apache.org/applications/"; class="externalLink">Applications</a> | @@ -253,146 +253,146 @@ </div> <div id="bodyColumn"> <div id="contentBox"> - <subtitle></subtitle><authors><person name="Randy Watler" email="[email protected]"></authors><div class="section"><h2><a name="ETL_Migration_Using_Jetspeed_2.1.32.1.4_2.2.1_and_2.3._Installers"></a>ETL Migration Using Jetspeed 2.1.3/2.1.4+, 2.2.1+ and 2.3.+ Installers</h2> + <subtitle></subtitle><authors><person name="Randy Watler" email="[email protected]"></authors><div class="section"><h2><a name="ETL_Migration_Using_Jetspeed_2.1.32.1.4_2.2.1_and_2.3._Installers"></a>ETL Migration Using Jetspeed 2.1.3/2.1.4+, 2.2.1+ and 2.3.+ Installers</h2> <p> To facilitate ETL based migration or data manipulation strategies, the Jetspeed installer includes the ability to export, initialize, and import a Jetspeed database. In addition to basic portal data, these operations also will include database PSML and user preferences stored in the Jetspeed database. The installer does not require a Jetspeed portal build or runtime environment to execute these operations. - </p> + </p> <p> The binary installer can be obtained from the download page, (<a href="download.html">Download</a>), both the minimal and demo installers include the neccessary data operations. In addition to the installer, the appropriate JDBC driver for the installation and access to the database will be required. - </p> -</div> -<div class="section"><h2><a name="Exporting_a_Jetspeed_database"></a>Exporting a Jetspeed database</h2> + </p> +</div> +<div class="section"><h2><a name="Exporting_a_Jetspeed_database"></a>Exporting a Jetspeed database</h2> <p> The first step in migrating a database is to export its contents into a file based representation. It is best to perform this step on quiescent or shutdown portal instance. Once the binary installer for the existing Jetspeed release and JDBC drivers have been gathered, invoke the installer using the following shell command: - </p> + </p> <div class="source"><pre> java -jar <Jetspeed installer JAR file> - </pre> -</div> + </pre> +</div> <p> To run the installer in the console without a GUI, append the <code>text</code> argument to the shell command: - </p> + </p> <div class="source"><pre> java -jar <Jetspeed installer JAR file> text - </pre> -</div> + </pre> +</div> <p> After starting the installer and advancing through the splash and license pages, select the <code>Export Jetspeed Portal Database</code> installer operation and continue. The installer will then prompt for the following information: - </p> -<table class="bodyTable"><tr class="a"><th>Installer Prompt</th> -<th>Description</th> -</tr> -<tr class="b"><td><code>Export data files location</code></td> + </p> +<table class="bodyTable"><tr class="a"><th>Installer Prompt</th> +<th>Description</th> +</tr> +<tr class="b"><td><code>Export data files location</code></td> <td> Select a new directory where the export is to write the database XML files. Existing files and directories in the selected directory will be removed when the export operation is complete. - </td> -</tr> -<tr class="a"><td><code>Temporary installation location</code></td> + </td> +</tr> +<tr class="a"><td><code>Temporary installation location</code></td> <td> If the default temporary location is not vaild, select a new temporary directory where the installer Jetspeed instance can be unpacked, (it is removed after the installation is complete). - </td> -</tr> -<tr class="b"><td><code>JVM memory size</code></td> + </td> +</tr> +<tr class="b"><td><code>JVM memory size</code></td> <td> Export operations can consume a large chunk of memory as the database is traversed. Enter a larger JVM maximum memory size in megabytes as necessary for the installer Jetspeed instance invocation. - </td> -</tr> -<tr class="a"><td><code>Database selection</code></td> + </td> +</tr> +<tr class="a"><td><code>Database selection</code></td> <td> Select the current portal database type. DB2, MSSQL, MySql, PostgreSQL, Oracle, and SapDB are supported. Note that Derby is not currently supported. - </td> -</tr> -<tr class="b"><td><code>Database connection parameters</code></td> + </td> +</tr> +<tr class="b"><td><code>Database connection parameters</code></td> <td> Enter or validate the current portal database user, password, connection string, driver class, and driver JAR archive file. - </td> -</tr> -</table> + </td> +</tr> +</table> <p> After configuring the export operation, the installer will test the database connection before proceeding to the confirmation page. Continue the installation process as instructed. When it has finished, be sure to review the <code>Show Details</code> tab to ensure the export has completed as expected. The following files should appear in the export data files location specified during the installation: - <ul><li><code>j2-data.xml</code> file</li> -<li><code>j2-prefs-data.xml</code> file, (2.1.X installers only)</li> -<li><code>pages</code> directory, (if database Page Manager enabled)</li> -</ul> + <ul><li><code>j2-data.xml</code> file</li> +<li><code>j2-prefs-data.xml</code> file, (2.1.X installers only)</li> +<li><code>pages</code> directory, (if database Page Manager enabled)</li> +</ul> If the installation fails or errors occur in the detail output, the export has probably failed. - </p> -</div> -<div class="section"><h2><a name="Editing_the_Jetspeed_database_Exported_XML_Files"></a>Editing the Jetspeed database Exported XML Files</h2> + </p> +</div> +<div class="section"><h2><a name="Editing_the_Jetspeed_database_Exported_XML_Files"></a>Editing the Jetspeed database Exported XML Files</h2> <p> Exported Jetspeed database XML files can be edited, provided the original format and all dependencies are maintained. The formats and files that make up a release do change between releases, so care must be taken to keep the syntax and files consistent with the export release version. No editing should be required to migrate between dataabase vendors. - </p> + </p> <p> Multiple imports can be performed in an additive fashion to merge slices of data cut from individual exports. However, individual objects in the data model are replaced with new versions loaded during the latest import; merging does not take place at the object level. Bulk edits may also be performed to modify data during migration to complement the portal upgrades if desired. - </p> -</div> -<div class="section"><h2><a name="Initializing_a_Jetspeed_database"></a>Initializing a Jetspeed database</h2> + </p> +</div> +<div class="section"><h2><a name="Initializing_a_Jetspeed_database"></a>Initializing a Jetspeed database</h2> <p> Full exports are designed to be imported into an empty Jetspeed database. Creating databases is left to the datbase administrator, but the loading of the Jetspeed database schema can also be accompished using the Jetspeed installer. Databases that contain instances of older Jetspeed portal schemas should be cleaned by dropping all Jetspeed tables prior to reinitialization by the installer. <b>All information within the database will be removed when the Jetspeed database is - initialized.</b></p> + initialized.</b></p> <p> To initialize a new database, the installer should be obtained and started for the target Jetspeed release version as documented above for the export operation, except the <code>Initialize Jetspeed Portal Database</code> operation must be selected. The installer will then prompt for the following information: - </p> -<table class="bodyTable"><tr class="a"><th>Installer Prompt</th> -<th>Description</th> -</tr> -<tr class="b"><td><code>Temporary installation location</code></td> + </p> +<table class="bodyTable"><tr class="a"><th>Installer Prompt</th> +<th>Description</th> +</tr> +<tr class="b"><td><code>Temporary installation location</code></td> <td> If the default temporary location is not vaild, select a new temporary directory where the installer Jetspeed instance can be unpacked, (it is removed after the installation is complete). - </td> -</tr> -<tr class="a"><td><code>Database selection</code></td> + </td> +</tr> +<tr class="a"><td><code>Database selection</code></td> <td> Select the current portal database type. DB2, MSSQL, MySql, PostgreSQL, Oracle, and SapDB are supported. Note that Derby is not currently supported. - </td> -</tr> -<tr class="b"><td><code>Database connection parameters</code></td> + </td> +</tr> +<tr class="b"><td><code>Database connection parameters</code></td> <td> Enter or validate the current portal database user, password, connection string, driver class, and driver JAR archive file. - </td> -</tr> -</table> + </td> +</tr> +</table> <p> After configuring the initialization operation, the installer will test the database connection before proceeding to the confirmation page. Continue the installation process as instructed to @@ -401,9 +401,9 @@ the detail output, the initialization has probably failed. This normally indicates that the database was not clean before the initialization was attempted or sufficient permissions were not granted to the specified database user. - </p> -</div> -<div class="section"><h2><a name="Importing_a_Jetspeed_database"></a>Importing a Jetspeed database</h2> + </p> +</div> +<div class="section"><h2><a name="Importing_a_Jetspeed_database"></a>Importing a Jetspeed database</h2> <p> Previously exported Jetspeed database XML files can be reloaded using the installer import operation. Full exports are normally loaded into empty databases, but multiple imports can be used @@ -411,63 +411,63 @@ information contained within the export or the export files themselves. Individual objects in the XML data files are fully replaced upon load; object instance merging is not supported by import. <b>All data objects imported to the database will replace any existing objects in the Jetspeed - database on import.</b></p> + database on import.</b></p> <p> The installer will expect the following files to appear in the import data files location directory specified during the installation: - <ul><li><code>j2-data.xml</code> file</li> -<li><code>j2-prefs-data.xml</code> file, (2.1.X exports only)</li> -<li><code>pages</code> directory, (assumes Page Manager to be enabled)</li> -</ul> + <ul><li><code>j2-data.xml</code> file</li> +<li><code>j2-prefs-data.xml</code> file, (2.1.X exports only)</li> +<li><code>pages</code> directory, (assumes Page Manager to be enabled)</li> +</ul> All other files in the import data files location directory will be ignored. - </p> + </p> <p> Jetspeed database import operations should only be attempted on a shutdown portal instance; imports on a running portal may lead to unexpected results and is not supported. If the import is to merge with data already loaded in the database, performing a full backup before the import is highly recommended. - </p> + </p> <p> To import an existing database export file set, the installer should be obtained and started for the target Jetspeed release version as documented above. The <code>Import Jetspeed Portal Database</code> operation must be selected. The installer will then prompt for the following information: - </p> -<table class="bodyTable"><tr class="a"><th>Installer Prompt</th> -<th>Description</th> -</tr> -<tr class="b"><td><code>Import data files location</code></td> + </p> +<table class="bodyTable"><tr class="a"><th>Installer Prompt</th> +<th>Description</th> +</tr> +<tr class="b"><td><code>Import data files location</code></td> <td> Select an existing directory that contains the exported Jetspeed database XML files. - </td> -</tr> -<tr class="a"><td><code>Temporary installation location</code></td> + </td> +</tr> +<tr class="a"><td><code>Temporary installation location</code></td> <td> If the default temporary location is not vaild, select a new temporary directory where the installer Jetspeed instance can be unpacked, (it is removed after the installation is complete). - </td> -</tr> -<tr class="b"><td><code>JVM memory size</code></td> + </td> +</tr> +<tr class="b"><td><code>JVM memory size</code></td> <td> Import operations can consume a large chunk of memory as the database is loaded. Enter a larger JVM maximum memory size in megabytes as necessary for the installer Jetspeed instance invocation. - </td> -</tr> -<tr class="a"><td><code>Database selection</code></td> + </td> +</tr> +<tr class="a"><td><code>Database selection</code></td> <td> Select the target portal database type. DB2, MSSQL, MySql, PostgreSQL, Oracle, and SapDB are supported. Note that Derby is not currently supported. - </td> -</tr> -<tr class="b"><td><code>Database connection parameters</code></td> + </td> +</tr> +<tr class="b"><td><code>Database connection parameters</code></td> <td> Enter or validate the target portal database user, password, connection string, driver class, and driver JAR archive file. - </td> -</tr> -</table> + </td> +</tr> +</table> <p> After configuring the import operation, the installer will test the database connection before proceeding to the confirmation page. Continue the installation process as instructed. When it @@ -477,8 +477,8 @@ again from a clean or known database backup state. Problems are normally caused by data incompatabilities/overlap between multiple import data slices or insufficient database permissions granted to the specified database user. - </p> -</div> + </p> +</div> </div> </div> @@ -487,7 +487,7 @@ </div> <div id="footer"> <div class="xright">© - 2004-2016 + 2004-2022 Apache Software Foundation
