This blog is moved to a permanent location.
Please visit www.contentprise.com
Thursday, August 27, 2009 |
|
Moved a step ahead
Posted by LOKESH PANT at 7:08 PM
Friday, June 19, 2009 |
|
Fatwire : Content Integration Vs Content Migration
Few days back Fatwire Software announced the launch of the Fatwire Rescue Program for Vignette and Interwoven WCM customers.
The program will enable customers of Interwoven and Vignette to upgrade to FatWire’s WCM solutions at no license cost. However, this holds good only if they engage Fatwire’s supported or so-called ‘proven' migration tools and services.
If you remember Fatwire already has a Content Integration Platform(CIP), which is a “web-services-based” content sharing tool. In this Fatwire CMS user can access content stored across the enterprise without leaving the Fatwire CMS interface (CS-Direct). CIP offers connectors to access content from Documentum, SharePoint, and Windows and Unix file systems.
So why this rescue package from Fatwire when they already have a solution in place? Here are my insights on the demarcation between the two offerings and the differences in the approach -
1. In Content Integration Platform, the source WCM/ECM sever must be up and running in order to serve the content. The only difference will be accessing the content using Fatwire console (dash/advance/insite interfaces).
[Access + Connector = Integration]
2. Fatwire rescue program is based on the expertise and past experiences of Content Migration service providers (Vamosa and Kapow). Server Instances of Teamsite or Vignette will not be required after full content migration.
[Entire data movement (Assets/Content/Templates/Workflows/Roles/Security/Users/Publishing Events) = Content Migration ]
Since there is no Fatwire connector for Vignette and Teamsite as of now, I believe this is another way of attracting the customers to move completely into Fatwire at lower cost (No license cost + No Running Instances of Teamsite or Vignette required).
Content Migration is a very risky, customers are advised that there is no fully automatic or a neat way of doing it. Manual intervention and tweaking of trusted scripts, XMLs and non-java based templates is very much required in order to do the migration. Evaluate and request for case studies or a proof of concept from the product vendor before you make a decision.
I am glad that in the midst of acquisitions in the WCM space, Fatwire is the one of the niche player who is moving a step forward by collaborating with content migration service providers like Vamosa and Kapow. I hope this move will hold well for Fatwire in WCM market space.
da75zxrjm4
.
Posted by LOKESH PANT at 6:40 PM 0 comments
Labels: Aquisitions, Architecture, ECM, Trends, WCM
Tuesday, May 26, 2009 |
|
How IBM is #1 in web portal software?
IT analyst firm Gartner, Inc., has ranked IBM as the worldwide market share leader in the Portal Products and User Interaction Tools enterprise software segment. Here is my take -
There is no question on the capabilities and functionalities of IBM WebSphere Portal V 6.1, which is well designed to collaborate the information from users, communities, corporate enterprises, and the Web. I will not discuss the cool and robust features of IBM but will list down the external factors that might have influenced the ranking-
1. Technology: Still the market share of .net is much less than java. IBM being a java based portal and is adopted by organizations who either already have java based software infrastructure or their decisive people are pro-java. I agree with Janus-
“Microsoft is known to give away SharePoint like candy, so SharePoint might indeed have less revenue. A substantial portion of SharePoint licenses remain unused.”
Yes, the Adoption of SharePoint (MOSS) is much higher than any portal in the market (07-08), and who does the marketing better than MS, but the point has still not reached where SharePoint can be ranked as #1.
2. Choice: Do customers have choice?..ummm –lets find out-
a) Opensource/Liferay: Even though Liferay is named as the Visionary portal product in Gartner’s magic quadrant, the financial industry has no confidence in this open source portal. On the other hand, IBM software is being used by the top 10 global banks.
b) Sun JES Portal: before the acquisition: The setting sun finally decided to stop the further release if its enterprise portal product (last version 7.2) and decided to contribute towards Websynergy and Webspace (Liferay-Sun combo Prj).
c) Oracle/Weblogic/Webcenter: Oracle invested huge $$$ in their Webcenter portal project but failed to market their so-called strategic portal product. Market still questions Oracle’s portal leadership. With five portal products under its belt, seems like that sale and marketing team is confused on which portal to highlight. I believe that aqualogic and weblogic are doing pretty well but not widely adopted as IBM WebSphere.
3) Leadership/Support/Cost: IBM tops the chart in terms of cost for its product, services and support. Even then, organizations opt for security, availability, collaboration and other web2.0 stuffs over the cost. It might be because IBM promises better ROI. I believe that 2011 will be a crucial year for IBM portal after the economic recession ends as most of the organizations have kept their decisions on hold for buying an expensive portal products.
There can be other reasons as well such as innovations, industry types, underlying architecture etc that might have valued customers more in buying this product.
More information about the report, features, and a case study is here-
http://www.eweek.com/c/a/Web-Services-Web-20-and-SOA/Report-IBM-Number-One-in-Portal-Software-333186/
Posted by LOKESH PANT at 4:19 PM 2 comments
Labels: Aquisitions, Collaboration, Market Share, Portals
Thursday, April 23, 2009 |
|
Another buyout. Who's next?
Another big acquisition from shopaholic giant. Finally Oracle bought Sun Microsystems.
Anyways..I'll leave other analysts to comment on hardware/storage/cloud computing and other areas. I am more interested to speculate the future of software products from Sun, example Sun Portal, Access Manager, Directory Server, and other open source projects. Here is my take in that -
Oracle already have five portals under its belt, out of with they have clearly indicated of taking Webcenter, Aqualogic and Weblogic forward.
With this buy out, Oracle might dispose Sun Portal, as this product from Sun is not doing great from last few years, even after Sun made heavy investments and revamped its portal suite during '06-07. Sun failed to generate more ROI and is now supporting only its top 100 customers.
I also fear that it might be a dead end for all open source initiatives from Sun, as Oracle has never shown any interest in the Open Source arena. This might badly affect project Websynergy and Webspace (Liferay-Sun combo Prj), NetBeans IDE, PostgresSQL etc.
I think, Liferay is becoming more vulnerable for acquisition by Oracle as Sun had an interest initially and still have few ongoing projects with Liferay.
On the greener side, Oracle will get benefited with Sun's IDM suite as Access Manager & Directory Server are widely used and now Oracle will have a reply to IBM's Tivoli suite.
Let’s wait and watch what next will come under Oracle's Business Process Management tag.
Posted by LOKESH PANT at 2:41 PM 0 comments
Labels: Aquisitions, OpenSource, Portals
Friday, February 06, 2009 |
|
All in one: ECM vendors tale
Just read Russ’s blog. It’s a nice post that made me think if there is a single ECM vendor who really managed to make their customer happy with full-fledged ECM requirements.
I think its not only mergers and acquisitions that led the large or mid size, organization to have various sub-ECM products from different vendors but it’s the piling of softwares that grows during the period. The reasons may be a not-so future oriented solution from service providers or a highly effective sale person or a customer with no or very less IT experience.
There are numerous cases where customers have enough ECM softwares and do not know what to do. E.g. I have come across with customer with Sharepoint already in place and looking for Livelink as DMS or customers with Livelink as DMS and Fatwire as WCM in place and then looking for integration.
The problem is on the other side as well. A few genuine ECM vendors really cater to “custom” ers requirements. Therefore, before going for any ECM establishment, customers should check the integration points with their existing WCM/ DMS/RM/BI etc infrastructure and at the same time ask the Service providers to show some kind of proof of concepts (POC) to validate the integrations
.
Posted by LOKESH PANT at 7:11 PM 0 comments
Friday, January 23, 2009 |
|
Interwoven to be Acquired by Autonomy
It was a mixed feeling for me when I read about Autonomy acquiring Interwoven. Yes, it is a surprise move as quoted by cmswatch, but some of the industry observers see it as a pending acquisition. Both Interwoven and Autonomy are niche and big market players in their area. Where Autonomy has a huge customer base for its Infrastructure and Intelligent Search solution, Interwoven on the other hand is a well-known ECM provider.
I think that it is more than good for Interwoven in many ways. Interwoven will have a strategic advantage of getting more customer base. A direct access to more than 20,000 Autonomy clients.
The Intelligent search from Autonomy can be embedded within Interwoven’s CMS, DMS, and Collaboration tools as Interwoven uses Vivisimo as a search engine for most of its product line, but now with Autonomy coming in, the search will eventually get impacted because Autonomy will push for Verity(Interwoven dropped Verity).
Though Autonomy has its own solutions for BPM, Search, and Record Management, it will be a challenge to manage the same offerings from Interwoven as well under the same hood.
With recession on the go, is this acquisition a fall in number of ECM player or a rise of one more CMS vendor to compete with Vignette or Fatwire WCM.
Posted by LOKESH PANT at 11:26 PM 0 comments
Labels: Aquisitions, ECM, Search, WCM
Wednesday, January 21, 2009 |
|
Let's get SharePoint Integrated
I’m currently seeing a new trend these days, it’s about portals and content management systems going above and beyond their technologies, language and platform to get integration with SharePoint. I have put my views on how Content Management Systems (Fatwire and Immediacy WCMs 6.1) are tending towards integrating with SharePoint. Now, it’s the open source portal which will come up with a similar kind of integration with SharePoint.
Integration with Sharepoint from a non-open source Java based portal is not new. IBM Websphere uses WSRP for communication with Sharepoint, while Sun Portal Server 7.2 integrates with Windows SharePoint Services (WSS) 3.0 which provides a set of portlets to get deployed over Sun portal.
Latest in this area is about open source portal Liferay 5.2 which is about to get release soon is coming up with a feature to integrate with SharePoint. The Implementation of the SharePoint protocol will allow saving documents to Liferay as if it were a SharePoint server.
Except WCM, most of the customers feel that SharePoint has more “admin” friendly document collaboration features, document categorization, roles based document access and defining document types on the fly. Altogether it provides better DMS capabilities.
As neither Fatwire nor Liferay has their own full fledge document management system. Enterprises with existing SharePoint investments and who are looking for a portal or WCM solutions can look for these connectors/portlets.
Anyways, the thought around these integration approaches is to have “seamless access” to SharePoint’s repositories without leaving the actual Interface of either portal or web CMS.
As far as cost is concerned, I am not sure if the “SharePoint integration” will be a part of Liferay Community Release or if there is any additional commercial involved in its Enterprise Edition. On the other hand Fatwire-SharePoint Integrator costs tens of thousands $$$ for each Sharepoint deployment.
I will constantly look in this area of integration and will provide more information as soon as community version of Liferay is released.
Posted by LOKESH PANT at 4:03 PM 0 comments
Labels: ECM, Integrations, OpenSource, Portals
Friday, October 17, 2008 |
|
Content Integration Platform and Content Interoperability
Few days back Fatwire Introduced Microsoft SharePoint Connector as part of its Content integration platform. This new connector enables Fatwire CMS users to seamlessly access SharePoint content to use on the web. The Content Integration platform provides web-services-based, peer-to-peer content sharing capabilities that gives CMS users access to content stored across the enterprise without ever leaving the Content Server interface, and publish it to their public sites, intranets and extranets.
“…….Using CMIS-defined HTTP calls, you will be able to do standard CRUD operations (create, read, update, delete) against any compliant repository, regardless of the underlying repository architecture “
Though there are couple of valid questions which still need to be answered around the concurrent operations across content repositories, but it seems like that various CMS vendors or specification authorities are going to use “common web services” as their technology to move forward.We will definitely look forward for the success of content integration platforms or CMIS as it’s hard to find projects that were successful where vendors
took JCR170 as their selling point, nevermind you still find sales guys talking about JSR 283 in their product presentations :-)
Posted by LOKESH PANT at 2:04 AM 0 comments
Labels: Integrations, Trends, WCM
Friday, September 12, 2008 |
|
Sun-Liferay and Project WebSynergy
After Sun-Liferay partnership early this year, Sun Microsystems has releases a stable version of a new Portal (from common code base) codename Project WebSynergy. A stable build 2 of WebSynergy is also available for download. Here are some of the new features in this release –
1. Portlet container 2.0: Complaint to JSR286 specs. Built on top of Open Portal Portlet container. Supports expiration and validation of cache, eventing and more advanced IPC.
2. JCR Compliance: Liferay Portal uses Mirage API that enables to use JCR compliant content repository, the same is incorporated in the WebSynergy release.
3. WSRP 2.0 Consumer Support : A WSRP consumer support and a new administration application is added that enables managing multiple WSRP consumers
4. Roller Blog Portlet: The Roller Blog portlet provides integration with Roller Weblogger version 4.0. Using this portlet, portal users can create and manage blogs on a Roller 4.0 server.
5. Presence: Presence Infrastructure also known as RUON has been integrated into Liferay Portal. Not really sophisticated as of now but there are plans to include more presence portlets to provide more presence-aware portal to the end user.
Its not far when a commercial release will be in the market. Surely this will be a big move from Sun’s perspective after a long time as there will be no more Sun JES Releases. This does not mean that Sun will stop shipping Access Manager and Directory Server duo. Both Access Manager and Directory Server are well known in the market and Sun will sell these products separately while relying on the Liferay community to concentrate on the portal side.
I think there is a possibility to see a connector/integration of Liferay Portal with Sun IDM stack in the near future.
Posted by LOKESH PANT at 12:48 PM 0 comments
Labels: Integrations, OpenSource, Portals
Tuesday, January 15, 2008 |
|
RFPs, Implementation Scope and Costs
It’s been quite some time that I am into responding RPFs and RFIs in Portal and Content Management space and sometimes jump onto implementation for the solution that we have provided :-) .
This post highlights issues that project delivery faces when a customer hides the information of its existing software infrastructure during pre –engagement stage.
Most of the customers do not supply enough information while releasing RFP. (for a mid-large size project it might just be a 2-3 pages of “relevant” information).
Along with RFP comes predefined “timelines” and “scope” and as usual, time-bound response is expected from vendors. In any circumstance you are paid to respond and get business for your company. You are not left with a choice, but to provide a solution based on one or two liner requirements with no information or volume of development, enhancement or migration of software/applications. Apart from solution, you have to mend your effort and cost estimations and make then inline with what was proposed to you.
Also, you must have experienced a time gap between the day you get the project and the day your SOW is signed off. What happens in this time gap? Answer is simple. You end up including another set of high level tasks that were neither part of RFP nor you have heard in your pre-engagement calls(lucky if you get this more), which slightly(as of now) adds to what you have proposed.
Few weeks later you will come to know more about customer’s existing s/w infrastructure and you are told that apart from portal development there is/are CMS/DMS/Back Office application that needs to be migrated or enhanced to latest version. Not bad so far. You start analyzing, assume few things, give better estimates and go ahead. Bad happens, if the existing CMS /DMS/Back Office application doesn’t fit in to the portal product that you proposed (Remember: it’s not your fault). Service providers end up doing all tricks to make the integrations work and customer ends up paying huge $$$ to product support and consultancy. These commercials would have been easily eliminated if right information would have given at right time.
“Right information at right time” is what makes a better response, which not only provides a better solution (considering all underlying application, their integration, SSO etc) but also reduces cost (Trust me, Indian service based s/w companies charge far less than any Product base company for their support and consultancy excluding license and training costs))
Posted by LOKESH PANT at 11:33 AM 0 comments
Labels: Architecture, Integrations, Trends
Monday, October 22, 2007 |
|
Oracle-Bea, Portals,Portals everywhere !!
Is the portal market going to see another acquisition by Oracle? Though Bea has denied the deal of $6.66 bn as “too low”, but as we know Oracle has a history of acquiring BIG companies and maintaining multiple products of same line. BEA and Oracle own two Portal products each (Aqualogic and Weblogic) and (Oracle Portal and webcenter), respectively.
If in case, the acquisition happens then in my view it will be relatively hard for Oracle to maintain and sell these portal products as Oracle is concentrating and investing huge in its webcenter suite and has a roadmap of releasing the next version i.e. Webcenter 11g very soon.With so many like products and no clear
feature demarcations of which product will cater to which type of customer its going to be a big challange for the sales team.
Looking from another perspective, Oracle surely will have business benefits with this acquisition as -
1) Oracle will eliminate a very big competitor.
2) Oracle portal is quite old and is in the edge of retirement and Oracle Webcenter is new in the portal market and is more developer centric. Oracle will revive with having aqualogic and weblogic in its main portal product stream
3) With Aqualogic and Weblogic from BEA, Oracle surely will have more and better products to sell.
4) As BEA Weblogic application server leads the middleware market and Oracle standalone application server lags far behind. Selling Bea appserver is going to add huge $$$ in Oracle’s account.
5) Oracle will also get boost to its SOA strategies, as both the companies have invested heavily on the SOA paradigm.
Apart from the above stated products, Oracle will rethink in supporting the other Bea products and suites as they may lag behind when compared to Oracle’s home grown products for example, BPEL solution and Presence Solution
Lets wait another leap that Oracle going to make and keep eye in the next quarter results.
Posted by LOKESH PANT at 4:24 PM 0 comments
Labels: Aquisitions, Integrations, Portals
Tuesday, May 29, 2007 |
|
JAX India 2007: Web2.0: What you should do?
Craig McClanahan talked on the Web2.0 at JAX India 2007.You can find more detilas about what he covered in Shishank's post. Here’s a bit of elaboration of those 10 points what Craig suggested to make the web right :-
10 - Expose Data/Logic as services
* Content is more important than presentation.
* Use REST based Services when you “Can”
* Use SOAP based Services when you “must”
9 - Incorporate External Content
* No single application or database can contain everything
* Combine available content from multiple sources
8 - Seek QOS (Quality of Service) deals from Sources
* Authentication guarantee
* Performance provisioning
* API and format compatibility
7 - Give QOS Deals to users
* External consumer will also become dependent upon your content
6 - Adopt Agile Processes
* Continuous iterative improvement model
* Incremental release every 7-14 days
5 - Test Driven Development
* Reduce release testing
* Do aggressive unit /functional testing
4 - Architect for Scalability
* Separate view, logic and persistence
* Break into layers that can be independently scaled
* Add resource as needed for bottlenecks
3 - Embrace Heterogeneity
* Data and logic as “service” insulates layers both internally and externally
* Agile Technology benefits in for fast UI fixes
2 - Reach out to Mobile Clients
* UI for Mobile devices can share existing service
1 - Enable User Provided Content
* Participating in “mashups” counts
* User like to participate not just “view”
The suggestion that Craig has provided, gives a clear perspective on how Web2.0 should be incorporated gradually within your organizations portal, CMS or website.If you read the above points again I feel that some of them directly or indirectly take you to the SOA space where we re-architect our implementations so that our applications can be “loosely coupled” and “interoperable” when used as “services”.
Posted by LOKESH PANT at 7:18 PM 0 comments
Labels: Architecture, Web2.0
Monday, April 30, 2007 |
|
Portals: Intruding the ECM space?
If Portals are the underlying technology for the presentation, aggregation, integration and SOA implementation (as every vendor talks about it ), then the Content Management System (CMS) is what feeds the portals.
Portals have been designed to integrate with CMS products as a part of their offerings. At the same time they have come up with their own version of built-in CMS.
Besides Partnering with vendors from Web Content Management (WCM) or Enterprise Content Management (ECM) arena, Portal vendors are also working successfully towards their own built-in CMS. These built-in CMS provide you the best a CMS product can offer. Journal Content Management, Document Management, Integration with MS office or Open Office, Drag and Drop of your desktop files, Workflow management, Integrated Publishing and Search.
WebSphere Portal 6.0 Integrates externally with CMS products like Interwoven Teamsite ,Documentum etc , also includes IBM Workplace Web Content Management Version 6.0 which itself carries a full fledged WCM capabilities. BEA provides the integration with Stellent, documentum and Vignette CMS products but has its own Content Management system and virtual content repository. Open source player Liferay portal 4.2 has come up with portlets for Alfresco (another open source Leader in ECM),but again it has its own "Liferay Journal" CMS which covers most of the WCM functionalities.
Sun and Bea have partnered with FatWire to provide Portal Server customers with unlimited-use licenses of FatWire Spark Portal Content Management (pCM) software at no cost.
There is a definite and clear separation of a built-in CMS and a third party CMS integration on to the portals. The choice is up to you, it all depends on what satisfies your business requirements. As for small and mid-size customers, these built-in CMS are doing the job, that too with a lot of ease and bringing in cost benefits.
CMS market has always been more mature, streamlined and more professional. On the other hand, the Portal market are not making the impact that was expected of them and was so fiercly predicted by the experts, a few years ago. The reasons could be cost, need, ease of implementation or lack of expertise with the service providers. In such a scenario are Portal vendors adding on CMS to their product feature list to stay alive?
If yes, what next? Would they continue to break ground and venture into ECM territory as they have now ventured into WCM territory?
Posted by LOKESH PANT at 4:49 PM 0 comments
Wednesday, February 28, 2007 |
|
"Portals" and "Portal-like"
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”)
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
Wednesday, January 11, 2006 |
|
An Eye on Collaborative Portals
The New Year heralds new realizations derived from the bygone year’s developments and thus, exploring options in the Collaborative portals space. The concept of Collaborative portals was an extension of the idea from commercial to business and organization’s infrastructural needs. It always was a challenge to achieve a single point of access as the teams are geographically distributed and mobile. Employees want to locate and communicate directly in the context of business processes and their day-to-day applications. They do not want to launch separate tools to chat with colleagues, participate in discussion threads or check project status.
However, the big players have their plug-in applications that adhere to no one standard and thus a technology incompatibility had erupted. Devising specifications for Java users (JSR 168) has been one move in this direction. As today’s teams are geographically distributed and mobile. To meet the expectation of being insync, organizations are providing and enhancing the capabilities that can transform the way colleagues communicate, relate with each other and perform work activities.
May it be asynchronous or synchronous, real-time based, these collaborative tools have provided a electronic workspace to allow people to share documents, project plans, calendars in the same online location. Bulletin boards and Blogs are becoming the medium to share thoughts and ideas on a particular topic on the web. Interactive Content Management System (I call it iCMS) with version control,Shared database ,email, event messaging etc are becoming the vital part of the collaborative suite.
It’s the business that benefits when -
• Employees access the right enterprise information, business process and people contributing in their areas of expertise with new ideas ,past experiences.
• Distributed expertise can respond more quickly and accurately to access consolidated
systems, reducing travel and facilitating efficient communications.
• A fast and reliable information flow can improve responsiveness, reduces coordination costs.
• Use the portal as a collaboration forum for employees and partners to work together more efficiently without regular face-to-face meetings.
Where every vendor is busy building their collaboration stacks and not concentrating on the compatibility with other Collaborative platforms,still there is no answer to the question of interoperability between different collaborative platforms in external or internal business units.
With this in mind a new category of integration software may emerge to enable interoperability among disparate enterprise collaboration platforms.
Concluding this post ,I believe that the market for collaborative portals is still promising, A trend is noted towards moving from collaboration to an "WorkField" which will incorporate collaboration, e-Learning, expertise location/identification, Interactive content management System (iCMS) and self-service applications.
Posted by LOKESH PANT at 7:56 PM 0 comments
Labels: Collaboration, Portals
Friday, December 16, 2005 |
|
Sun's Collaborative Portal Server 7
Another big hit by Sun Microsystems Inc today by announcing major enhancements to the Java Enterprise System with a new version of the Sun Java System Portal Server(version 7) that will provide developers and customers with collaborative features and identity-based content through web-based applications.
As Collaborative Portals are speedily replacing the traditional portal features and architecture, Sun was a bit late but came with enhanced and the most needed capabilities of its Portal Server which will allow the easy creation of interactive communities of users and services, building community portals populated with collaborative content including RSS feeds, blogs and wikis.
The story of Collaborative technology is not new anymore ,Interwoven’s WorkSite (Document Collaboration), IBM lotus Quickplace, EMC Documentum e-room were the first one to include the Collaborative technology in their products.
Liferay Portal server 3.6 too have and support for the collaborative content including RSS feeds, blogs and wikis, but follows the Gropus and Role Concept that works more or less the same as Community Concept
Identity-based portals and community portals, when combined with Sun's leading support of AJAX (Asynchronous JavaScript) portal containers, allow users to experience the interactive power of the Web along with the personalization and rich application interfaces traditionally associated with the desktop.
Some of the enhancements made to the Sun Java System Portal Server 7 include:
**Delegated Administration Features -> enables end users with the ability to manage page layouts, reset passwords, and allow non-technical users the ability to manage common portal functions, thus freeing up IT resources .
** Tools to Create New Communities and Community Services -- including user communities, wikis, file sharing, blog integration, and an open interface to build and expand on these services.
** Sun is also incorporating the open Java DB, a Sun supported distribution of the Apache Derby database, in the Sun Java System Portal Server 7 for use in data storage.
More information can be found at: http://www.sun.com/software/javaenterprisesystem
Posted by LOKESH PANT at 7:14 PM 0 comments
Labels: Collaboration, ECM, Integrations, Portals