List of Popular Portal servers
• Liferay - Liferay deploy portlets that adhere to the Portlet API (JSR 168).Its one of the most popular and most talked upon potal server in the recent market. It has lots of portlets bundled with the portal (Mail,Workflow, Document Library, Calendar, Message Boards,Wiki, to name a few) and can be used to develop for adding your own custom portlets.The Ext environment in the portal server is used for extending the portal towith custom generated portlets and make it compatible with newer additions of incremental development.
• Exo - The eXo platform is a one of the major Open Source - JSR 168 compliant - enterprise portal built from various modules.It provides virtualization of the work space through an advanced WebOS interface.
• Pluto - Reference Implementation of the JSR168.It now supports JSR286 also. Apache Pluto is a subproject of the Apache Portals Project.
• JA-SIG uPortal - uPortal is a free, sharable portal under development by institutions of higher-education. Community tools, such as chat, forums, survey, and so on, build relationships among campus constituencies. uPortal is an open-standard effort using Java, XML, JSP and J2EE.
• ByLine - Byline is an open source (LGPL) content management, portal, and collaboration system built on top of a sophisticated web development framework. Byline includes content authoring, versioning, workflow, categorization, and lifecycle management capabilities. Byline has been used to build sophisticated content and document management systems for customers such as the APLAWS consortium, FranceTV (www.france2.fr), Deutsche Post, the United Nations, and many others. Byline has been used to power systems that have over 400GB of data, thousands of content contributors, and tens of thousands of content visitors.
• Jakarta Jetspeed 2 Enterprise Portal - Jetspeed-2 is the next-generation enterprise portal at Apache. Jetspeed-2 offers several architectural enhancements and improvements over Jetspeed 1.0. First, Jetspeed-2 is conformant to the Java Portlet Standard and provides a standard mechanism for the deployment of portlets. Second, Jetspeed-2 has matured to a more scalable architecture featuring multi-threaded functionality. Third, Jetspeed-2 is decoupled from several legacy open source projects. Fourth, Jetspeed-2 is based on a component architecture.
• JBoss Portal - JBoss Enterprise Portal Platform provides an integrated open source platform for hosting and serving a portal's web interface, aggregating, publishing, and managing its content, and personalizing its experience.
• Websynergy-project WebSynergy SB 2 is the next-generation web aggregation and presentation platform from SunTM Microsystems. This platform includes developer tools and an enterprise-grade presentation runtime based on Liferay Portal Server, GlassFishTM version 3, and MySQLTM software.
• Portals in Cocoon - The portal framework is a portal server that runs inside Cocoon - or to be more precise inside the Cocoon servlet. It contains a portlet container that is called coplet container. Coplet stands for Cocoon Portlet and is the Cocoon equivalent to portlet.Due to the highly extensible nature of Cocoon, the portal is configurable and extensible as well and provides many hooks and switches to easily adapt the portal for specific needs. As the portal is integrated in Cocoon it has the advantage that all features of Cocoon can easily be used. Cocoon is very strong in fetching data from various source and delivering it in the various output formats requested by different clients (like HTML, WML, PDF etc.).
Showing posts with label web application. Show all posts
Showing posts with label web application. Show all posts
Thursday, January 22, 2009
Monday, January 19, 2009
Portlets ....why ? (part 1)
AGENDA
• Traditional Web Application
• Shortcomings of traditional Web Application
• What is needed?
• What are Portlets? Portals?....
• The New Generation answer …..
Traditional Web Application
• The “W W W” --The world wide web ,subset of internet is responsible for information sharing.
• The Website Approach ---each application is developed separately like a website and deployed singly on a server.
• The Client Server --the usual client server architecture involves synchronous request response paradigm.
• The Users' Perspective --the user access the website ,using the browser and can work with a single website at a time.A single application to interact with.A single repository of information.
• The Developers' Perspective --separation of work and single handed workaround with no plug and play feature.A huge effort is required to maintain,re-engineer or add a new application to an existing one.
• The Business ….Market….Bottom-line -- a huge cost incurred as the project is nearly developed from scratch (or even if component reuse ).In these hard times market and bottom line are the deciding factors for the fate of the project,people and even the company.
Traditional Web Application -Drawbacks
• Lack of Personalized Matter --the content is hard to personalize,lack of personalized matter means lack of edge on the business for traditional web application.
• Segregated Approach --the development is done in separation,a foreign developer body cant collaborate and no plug and play features included,developed by an external developer.
• Difficult for technology up gradation --a technology update in an existing web application is difficult to inherit.
• Single Handed Approach --a traditional web application is developed singlehandedly by a certain community of users and are deployed on a web/application server with no specific way to incremental upgradation.
• Difficult to Maintain --as the development goes on and one it becomes very hard to maintain and at a time the entire application can collapse for a simple and difficult to trace fault.
• Difficult to Re-engineer --very difficult to re-engineer and maintain stuff.
• Separate User Management --the entire user management is separately developed and no inbuilt support is given by the web server.
We Need…..
• Personalized Matter
• Integrated Approach….
• Ease of technology Upgradation….
• Community and collaboration framework ……
• Application Repository……
• Easy to Re-engineer…….
• Painless User Management….
• Hassel Free Maintenance
What are Portlets? Portals?....
What did u understand from the above image. Look closely at the image and u can find that each and every application is associated with a portlet window which can be minimized , maximized, closed or removed form the portal page . It means that each and every portlet is a small application which can be arranged on the portal page as we like and also it has inbuilt support of personalization and user management.The entire thing is asynchronous also also conforms to web2.0.....its like magic!
a close look at the skeleton of a portal page along with portlets which show contents called fragments
The New Generation answer ….. what is the new generation answer to the drawbacks of traditional web applications its Portlets and Portals..
• Traditional Web Application
• Shortcomings of traditional Web Application
• What is needed?
• What are Portlets? Portals?....
• The New Generation answer …..
Traditional Web Application
• The “W W W” --The world wide web ,subset of internet is responsible for information sharing.
• The Website Approach ---each application is developed separately like a website and deployed singly on a server.
• The Client Server --the usual client server architecture involves synchronous request response paradigm.
• The Users' Perspective --the user access the website ,using the browser and can work with a single website at a time.A single application to interact with.A single repository of information.
• The Developers' Perspective --separation of work and single handed workaround with no plug and play feature.A huge effort is required to maintain,re-engineer or add a new application to an existing one.
• The Business ….Market….Bottom-line -- a huge cost incurred as the project is nearly developed from scratch (or even if component reuse ).In these hard times market and bottom line are the deciding factors for the fate of the project,people and even the company.
Traditional Web Application -Drawbacks
• Lack of Personalized Matter --the content is hard to personalize,lack of personalized matter means lack of edge on the business for traditional web application.
• Segregated Approach --the development is done in separation,a foreign developer body cant collaborate and no plug and play features included,developed by an external developer.
• Difficult for technology up gradation --a technology update in an existing web application is difficult to inherit.
• Single Handed Approach --a traditional web application is developed singlehandedly by a certain community of users and are deployed on a web/application server with no specific way to incremental upgradation.
• Difficult to Maintain --as the development goes on and one it becomes very hard to maintain and at a time the entire application can collapse for a simple and difficult to trace fault.
• Difficult to Re-engineer --very difficult to re-engineer and maintain stuff.
• Separate User Management --the entire user management is separately developed and no inbuilt support is given by the web server.
We Need…..
• Personalized Matter
• Integrated Approach….
• Ease of technology Upgradation….
• Community and collaboration framework ……
• Application Repository……
• Easy to Re-engineer…….
• Painless User Management….
• Hassel Free Maintenance
What are Portlets? Portals?....
What did u understand from the above image. Look closely at the image and u can find that each and every application is associated with a portlet window which can be minimized , maximized, closed or removed form the portal page . It means that each and every portlet is a small application which can be arranged on the portal page as we like and also it has inbuilt support of personalization and user management.The entire thing is asynchronous also also conforms to web2.0.....its like magic!
a close look at the skeleton of a portal page along with portlets which show contents called fragmentsThe New Generation answer ….. what is the new generation answer to the drawbacks of traditional web applications its Portlets and Portals..
Subscribe to:
Posts (Atom)