Few days’ back I got to know about the something called “portal-like” . wow...a new word and a new concept after Collaboration, Web2.0 and SOA in the portal space. Drilled down a little deeper I came to know that this concept make sense when it comes to mid-size enterprise ,here it goes....
Portals Implementation gives you the solution but with a huge investment of money, infrastructure, resources and support.
Mid sized Customers who wants the portal features (with less investments) now can use the “Portal-like” products to leverage the features what a portal offers. These “Portal-like“ frameworks uses the Jsp, Jsf environment as a core language to built the applications and provide the addition runtime environment (portlet container) to consume/include the portlets on top of the jsp, jsf application. These frameworks support the deployment of standard based portlets (jsr168, wsrp1.0) together with the vendor specific portlets.
End users can also be provided with “virtually” customization features that will be a part of JSF/JSP/AJAX implementation.
These products are well suited where the core application takes more functional space than the utility portlets, which is opposite in the case of actual portal implementation.
There are few pros and cons of these frameworks/tools/products -
Pros-
1) Comparatively less investment than the Portal product
2) No portal expertise required to develop “Portal-like“ application
3) Use of standard based pre-built portlets (blogs,wikis,cms,rss etc )
Cons-
1) Application can not be easily scaled to portlets in the near future :)
2) Cannot be used as Integration point with other Enterprise/legacy applications.
3) Confidence of the customer towards the solution vendors.
The Introduction of such a framework is done by Oracle with its Web Center Suite. That provides the Content Integration, Runtime Customization, Metadata Management and Communication Services (Again a new Word for me “Presence Server”)
Wednesday, February 28, 2007 |
|
"Portals" and "Portal-like"
Posted by LOKESH PANT at 5:43 PM 0 comments
Labels: Integrations, Portals, SOA
Tuesday, May 23, 2006 |
|
Enterprise Portal and Service Oriented Architecture (SOA)
Service-oriented architecture (SOA) is the talk of the enterprise fraternity. Not only the business is getting benefited but the potential of SOA is affecting the speed of application development process.
This buzzword strikes Portal technology as well. These days organizations are in the process of migrating from traditional client/server, monolithic or disparate n-tier architecture to a more loosely coupled and interoperable environment, this process is then better termed as Service-Oriented Architecture (SOA).Most of us are aware of SOA and its benefits, I wont be repeating those here but will discuss that how Portal can be used to leverage SOA.
When we talk about the underlying components of SOA i.e. Interoperability, Scalability, and
Integration, the best suite that does and support all these is an Enterprise Portal Implementation.
A Portal based on standard like JSR168 and WSRP can be the most eligible candidate for SOA. When we look at the Portal’s Infrastructure, we find that it comprises of nuts and bolts of Service Oriented Architecture.
So the next thought that comes to mind is how Portal fits in SOA?
Portlets are reusable web components which forms the core of a Portal Desktop, providing relevant and customized information.SOA’s Interoperability is achieved by deploying JSR 168 Portlet to any JSR 168 compliant Portal server. Also, a portlet can be reused in different Portal pages as well as in different containers which proves reusability aspect of SOA.
Web Services, one of the main building blocks of SOA, fits nicely with Portal as WSRP based portlets. WSRP enabled portlets, which adhere to Web services standard such as SOAP and WSDL, enables portal to easily include services from a third party into a portal page. This eases and reduces the development process and makes use of already available enabled services. WSRP provides much support for the basic pillars of SOA like SSO, Reusability, Access management, service integration with loose coupling (here I mean to say that different processes should be integrated but without the processes being dependent on each other ).
Lastly, Role based content delivery model in Collaborative Portals makes a value addition for role based SOA Implementation.
The above information perfectly fits with the Gartner’s conclusion that
“The portal can be a logical and appropriate first step toward SOA implementation because its fundamental nature lends itself to SOA approaches”
Posted by LOKESH PANT at 6:53 PM 0 comments
Labels: Collaboration, Portals, SOA, Specs
Tuesday, April 11, 2006 |
|
RedHat to acquire JBoss
The JBoss war has finally take a not so expected turn when Red Hat announced to acquire JBoss. Red Hat and JBoss have been recognized as open source leaders in their respective domains. The large and vibrant communities around Linux and JBoss prove that the open source development model creates innovative, quality software, while providing a flexible and low cost model for customers. This acquisition is expected to accelerate enterprise adoption of open source infrastructure, and broaden the entire market opportunity for existing and new Red Hat and JBoss partners who are building
value-added enterprise solutions.
RedHat have already tried its hands on middle ware front (Jonas as application server),and much of the R&D was on portal and CMS with no success. With this acquisition RedHat will get a powerful web stack and the customer will get a product with more performance ,security and the branded and well respected support with a low –price.
As far as my speculation, I don’t think that RedHat will offer any support for Windows Version, rather it may stop JBoss’s windows version, because that will effect its own Linux distribution.
Anyways “All well that ends Well” --- OpenSource to OpenSource” :)
Posted by LOKESH PANT at 8:35 PM 0 comments
Labels: Aquisitions, OpenSource
Friday, February 24, 2006 |
|
Enterprising the open source
The cloud thickens on the strategy of the open source vendors….“The enterprise fraternity” are keen on acquiring smaller rival companies with open sourced software and after acquisition, only unveil a part of the software that remained open sourced before, Then doesn’t the whole idea of open source get flouted? Another heating debate could be on the possible reasons for acquiring such firms that are open sourced. Typically, an open sourced company is learnt to be earning from the product’s maintenance, installation and support unlike, their product counterparts that derive from the licensed product copies as well. So, there seems to be a basic clash on the ideals of the two entities. Is this strategy a result of the fear in the biggies that the smaller ones could eventually overtake them as they gather more supporters for open sourced version.
A historical data on some such developments on this front that testify this:-
Oracle acquired Innobase an open source software company and a developer of transactional database technology, the software was distributed under the GNU GPL open-source license and was bundled with MySQL. Currently, it is reportedly in talks to acquire three open-source companies to expand its customer base .In return, it announced a free, low-end version of its database software thus, letting the world know about their commitment to opensource. Oracle also plans to buy Jboss Inc ,another opensource company and a leader in the application server market .
IBM last year bought Gluecode Software,which offers an application server based on apache Geronimo project. The give and take business is not new as IBM bundles with WebSphere, and it contributed an embedded database called Derby to Apache.
Bea Systems open sourced a version of its relational database mapping tool “Kodo” under an Apache license, while continues to offer BEA Kodo under a closed source license.
Sun Microsystems looked at open source community to revive itself , open sourced Solaris and JES.
At some point this may be a good deal for the customer as now they have a quality, open, and a low-priced(a bit more) product which is now backed ie supported by a branded company. So I think the product which was originally “true open source software” turns to have only source open.
My concern is that people who contribute to the open source software (apart from the employees of the open source company) is a vast community of developers, architects, designers who believe in sharing knowledge much to the relief of the smaller firms or developers that cannot afford licensed copies. However, with such moves industry wide, would this give enough leverage & credit to the people who contribute to this wealth of information or who use this information. Wouldn’t then the trend to contribute and share knowledge, then discouraged if this trend of acquiring smaller open sourced cos by the big giants continue?
Posted by LOKESH PANT at 12:04 PM 0 comments
Labels: Aquisitions, OpenSource
Thursday, February 02, 2006 |
|
Open Ajax and Collaboration
..so the big guys finally collaborate to push AJAX in the opensource community. IBM, BEA Systems Inc., Borland International Inc., Novell Inc., Oracle Corp. and Red Hat
Inc., have formed a group to contribute code and work together to promote use of AJAX., they will call it Open Ajax. This group will promote the use of Ajax tools with which developers can build rich Internet applications. The tools essentially eliminate the need to refresh a Web page every time a user enters or receives new data.
IBM is to propose its Ajax Toolkit Framework , that framework supports multiple Ajax runtime tools and can be used to develop and debug applications.
Since in the portal front the world is going collaborative and AJAXed :) ,its good to see that even the top notch vendors are implementing or moving a part of their technology to opensource.
Posted by LOKESH PANT at 11:14 AM 0 comments
Labels: Collaboration, OpenSource