Following my article last week about migrating from JBoss Enterprise Portal Platform 5.2 to eXo Platform 4, this week’s article is about migrating from JBoss Portal Platform 6 to eXo Platform 4.
Although JBoss Portal Platform is a powerful portal, it lacks features that eXo Platform 4 offers out-of-the-box, such as content and social collaboration.
Here is how you can migrate using a Staging Extension add-on developed by eXo and freely available to the community.
Why migrate to eXo Platform 4?
Simple. eXo Platform offers a long list of out-of-the-box features: document and web content management, knowledge management, enterprise collaboration, all tied up to social features. You can read more about our social intranet capabilities on our website.
Are JBoss Portal Platform applications compatible with eXo Platform 4?
eXo Platform 4 is based on the same technical dependencies as JBoss Portal Platform 6. It provides add-ons on top of “GateIn” for advanced Enterprise Portal Features: “Document Management System“, “Content Management System“, “Social“, “Enterprise Collaboration tools“.
Applications developed under JBoss Portal Platform remain fully compatible with eXo Platform 4. It is recommended to use eXo Platform for JBoss AS 7/EAP 6 to conserve the application’s ecosystem.
How can I migrate from JBoss Portal Platform 6 to eXo Platform 4, and is it simple?
Applications based on JBoss Portal Platform 6 are compatible with eXo Platform 4, so you just have to copy the artifacts.
To copy JBoss Portal Platform 6 custom configurations, you will need a dedicated tool: https://github.com/exo-addons/staging-extension.
What are the eXo add-ons?
The eXo add-ons are extensions to the platform. They are developed by the community, for the community. The eXo add-ons enable you to add features (like chat capabilities), integrate with other technologies (like Bonita for workflows capabilities) and manipulate your portal data (like migration).
What is the “Staging Extension”?
This is an add-on that can be deployed on JBoss Portal Platform 6 and eXo Platform 4. The main goal of this add-on is to copy data and configurations from a “GateIn compliant server” (JBoss Portal Platform or eXo Platform) to another.
This is especially used to copy data from a “staging server” to a “production Server”.
How to use the “Staging extension”?
Follow installation guide provided here to deploy it on JBoss Portal Platform 6 and eXo Platform 4.
You can add the “Staging Extension Portlet” on a page or access it via SSH.
How to migrate from JBoss Portal Platform 6 to eXo Platform 4?
After deploying the “Staging Extension” on both “JBoss Portal Platform 6” (source) and “eXo Platform 4” (target), follow these instructions:
1. Start JBoss Portal Platform Server.
2. Login and add “Staging Extension Portlet” in a page with access restrictions for administrators.
3. Export “site” resource: this resource contains all portal, group and user sites and pages.
4. Export “registry” resource: this is the “Application Registry” data.
5. If you have defined new gadgets, you will have to export “gadget” resource.
6. Copy your custom applications (Portlets) and GateIn extensions in eXo Platform 4. (EAR, JAR, WAR.)
Note: if you use eXo Platform 4 Tomcat, then you only need to copy JAR inand WAR in .
7. Start eXo Platform 4 Server.
8. Login and add “Staging Extension Portlet” in a page with access restricted to administrators.
9. Import “site” resource that you have exported from JBoss Portal Platform.
10. Import “registry” resource that you have exported from JBoss Portal Platform.
11. Import “gadget” resource that you have exported from JBoss Portal Platform.
That’s all you need to do, now you can see your Portal working with eXo Platform 4. Enjoy!
As usual, you can connect to the eXo Community Forums and post a topic if you have any questions or you need more details on how it works.
And if you already have a project and wish to upgrade to eXo Platform, you canalso contact us for more details.