Chapter 1. Upgrading 2.0 - 2.2 - JBoss Portal 2.2 Reference Guide 英文版参考指南文档

To describe the changes made to the deployment descriptors, we have made available an example that you can download here: HelloWorld Portlet . After this helloworldportlet.ear is deployed, you should be able to access the new portal page by pointing your browser to http://localhost:8080/portal/portal/default/HelloWorld .

All portal, page, and portlet instance deployment is now handled by one file: *-object.xml. You no longer need the *-portal.xml, *-pages.xml, and *-instances.xml found in JBoss Portal 2.0. For our example we make available helloworld-object.xml located under helloworldportlet.war/WEB-INF/ , and it looks like this:

               
                <?xml version="1.0" encoding="UTF-8"?>
                <deployments>
                <deployment>
                <if-exists>overwrite</if-exists>
                <parent-ref>default</parent-ref>
                <properties/>
                <page>
                <page-name>Hello World</page-name>
                <properties/>
                <window>
                <window-name>HelloWorldPortletWindow</window-name>
                <instance-ref>HelloWorldPortletInstance</instance-ref>
                <region>center</region>
                <height>0</height>
                </window>
                </page>
                </deployment>
                <deployment>
                <if-exists>overwrite</if-exists>
                <instance>
                <instance-name>HelloWorldPortletInstance</instance-name>
                <component-ref>helloworld.HelloWorldPortlet</component-ref>
                </instance>
                </deployment>
                </deployments>
                
            

A deployment file can be composed of a set of <deployments>. In our example file, above, we are defining a page, placing the HelloWorldPortlet as a window on that page, and creating an instance of that portlet. You can then use the Management Portlet (bundled with JBoss Portal) to modify the instances of this portlet, reposition it, and so on...

Since the underlying layer of the CMS has changed, it will be necessary for users migrating from 2.0 to move their content, so the following steps describe how to perform this operation.

JBoss Portal v2.0 had native WebDAV support, allowing a user to connect to the content repository via the Operating System, given the proper credentials. You will use this method to extract the content, zip it in an archive, and upload it to the new CMS.

Database schema differs slightly between portal 2.0.0 and 2.0.1 versions. Some new talbes were added for new functionality. There were few columns removed or type changed also.

From 2.0.1 RC2 version portal performs schema update try during startup/deployment. Hibernate SchemaUpdate hbm2ddl tool is able to add new tables or new columns. What it doesn't do is removing unnessesary columns or column sql-type changes.

Besides of that, it is always good to back up your data as this behaviour might depends on different RDBMS versions.

In portal 2.0.1 there are some changes in db schema related to Forums Portlet

For eg. columns such as:

are now not used. These are retrieved using Hibernate collections storing capabilities.

Column:

had wrong SQL type. It was 'varchar(255)' in 2.0.0 and it is 'text' in 2.0.1.

After upgrading portal to 2.0.1, schema should be updated automaticly and all new nessesary tables/columns created. If this process fail the schema will be dropped/created. Remember to backup your data before doing migration!

After successfull update beware of the fact that you will have:

To deal with second issue we must change jbp_forums_posts-->jbp_text column type. It's very simple to do in MySQL RDBMS:

               ALTER TABLE jbp_forums_posts CHANGE jbp_text jbp_text text
            

In Postgres it will be:

               ALTER TABLE portal.jbp_forums_posts ALTER jbp_text TYPE text;
            

This will change column type.

Check in your RDBMS docs if such ALTER TABLE SQL statement works. If not you should probably recreate jbp_forums_posts table with proper SELECT/INSERT statement.