Lightweight portal server for developing WebSphere Portal?

I am developing portlets for IBM WebSphere Portal 6.1. However, the deployment process is very slow. Since this is my first time developing portlets, I am not very good at various portal servers. I would like to get some recommendations for a lightweight portal portal on which I can quickly deploy it for development.

+6
java websphere portal websphere-portal
source share
7 answers

Pluto is the answer!

http://portals.apache.org/pluto/

I'm very happy.:)

+5
source share

I believe that Liferey has become Sun's adopted strategy , if it has anything to do.

+3
source share

If you are using a Websphere Portal server, you can use the lazy loading of portlet applications at server startup. This will help reduce server startup time because it does not run many administrative applications.

For more information, go to this link http://www-01.ibm.com/support/docview.wss?uid=swg27015437

Hope this helps you :)

+2
source share

I am not familiar with each of their deployment characteristics, but here is a list of open source portals in Java: http://java-source.net/open-source/portals

+1
source share

I was in a similar situation a year or two ago.

The server takes a lot of time, despite this, but in fact it does not need to be restarted with minor changes. You only need to restart the server with major changes, otherwise restart or redistribute the project to the server.

However, the system was not fast until I had three ram concerts. I would recommend upgrading the workstation to support the server first. They are called workstation class systems for some reason :) Get yourself an 8 GB machine and tell your boss that you will be twice as productive :)

0
source share

I usually use hotdeployment to change Java classes and JSP pages. This is the fastest way. We shared 1 server with 5 developers using the hotdeployment classes for PortalServer / installedApps / .ear / yourportlet.war, and it worked fine. However, from time to time we had to restart the server. If you changed deployment descriptors, you still need to redeploy the WAR portlet. Make sure the reloadingEnabled parameter is set to false for the wps.war application on your development machine (reloading gets the changes).

0
source share
0
source share

All Articles