I am trying to register the current Liferay EE trial license provided by Liferay, but i keep getting corrupt license error.
Currently liferay is providing license for version 7.0 DE,But i want trial development license for 6.2 EE. I also tried sending an email to liferay sales.
Is there any solution for it?
You'll need to contact Liferay, which you already did, since the 6.2 EE portal subscription won't be actively sold anymore. 6.2 EE is almost 3 years old now and will have one year premium support left over. So depending on your project you'll need to make the right choice and act fast if 6.2 EE is needed (I thought subscription sales of 6.2 are ending in september 2016).
Related
I would like to ask a question about wether or not I should do the migration to Liferay 6.2.
Me and my team are working since 4 month on a portal quite big developed with Liferay 6.1 (CE edition) and now, since the project publication date is still 4-5 month ahead (so I do have time), I was wondering if doing the migration to 6.2 now is a good choice.
I already tried the new version and I must say I am impressed about the new features and since now I haven't find any bugs.
Anyone had any experience on developing portlet/themes on Liferay 6.2? Is is worth it to do the migration now or shall I wait for the next ga2 release?
Any suggestion is very welcome.
Thanks
Depends mostly on the kind of work you've done on that portal. Even slight upgrades in Liferay, can have major differences in the source code. If this affects the work you've done, it will affect the upgrade too. For example, things will get difficult to update if :
You have developed custom portlets, as they will need recompilation for the new runtime
Developed Portlets that use ServiceBuilder might need more work than just a recompilation
Using Hooks (even simple jsp hooks) might need re-writing. ext hooks will almost certainly need to, and it can become a major pain
On, the other hand, if most of your work had to do with light theming and content management, it could become an relatively easy and painless upgrade.
In any case, make sure to keep a backup of your Liferay Database, because once you upgrade, there is no way to downgrade back to the initial version.
As you're using CE, my recommendation is to upgrade as soon as possible. Reason is that there are no more updates for 6.1, now that 6.2 is out. If you're going live in 5 months, you'd be on a version that's unsupported for half a year at the date of publication.
The alternative is to go to EE, which is supported for ~5 years from release, e.g. you'll have several years of support in front of you. However, as Liferay is paying my salary, note that I might be biased...
Of course, being unsupported "by Liferay" does not mean that you won't be able to fix any bugs or issues, but you'll have to do this on your own, and sooner or later you should upgrade anyway... If you're not yet live, I'm recommending to do it sooner.
Liferay 6.2 does not (yet) support as many marketplace apps as Liferay 6.1. Also Liferay 6.2 CE has bugs, and patches are available only to EE subscribers; this forced us to use Liferay 6.1 CE instead of 6.2 CE.
You will have issues if you are using the Vaadin framework under Liferay.
Liferay 6.2 CE does not support Vaadin out of the box ... it is delivered with Vaadin 6.8, but it is broken - your portlet code will break.
You would have to consider moving to Vaadin 7.1 at best ... and that is a non-trivial code migration as many items have been deprecated between 6.8 and 7.
I went that route and the learning curve was unexpectedly steep.
One of our customers have Lotus Notes version 5.0.9. They wanted to check if it's possible to create an android mobile application to connect to the backend for documents workflow.
Couldn't find much resources about this scenario for this version. I believe Domino is already available on that version - so is Xpages a viable solution for that scenario? Thanks.
XPages requires at least Domino 8.5.x (and preferably Domino 9.0 which is the latest IBM Domino release). So you need to upgrade the Domino server if you want to use XPages.
FYI: Notes 5 was released in 1999 (see the history of IBM Notes on wikipedia).
XPages are available since IBM Notes Version 8.5. The term "Domino" stands for the IBM Notes server. So if your customer has Notes version 5.0.9 they probably have Domino version 5.0.9 too (although one can mix Notes and Domino versions).
Therefore XPages are no option for your, apart from the fact you could install a second Domino sever with version 9.0 just to host the xpages.
If they are on R5 what are they using for a workflow engine? If they are using a database designed from Approval.ntf (I think R5 was the last time it was shipped with the product) then it is a very old and very difficult to maintain &/or modify. If so then they probably need to take a deep breath and upgrade and re-design. Can probably cobble something together to make it work but really question the wisdom of doing that.
Our company is developing e-portal solutions for the government in Vietnam. We are using Liferay Community Edition. We are considering switching to Enterprise Edition.
From a programmer's perspective, is there something LP EE can do that LP CE cannot (performance, security, functionality, etc.)? We would like to hear from the experiences of programmers who have worked with both LP CE and EE before.
Thank you so much.
Linh
In addition to what the others already mentioned, Liferay EE is supported for ~5 years after release, while you won't get upgrades for major CE versions once the next release is out - so you need to upgrade less often. Support includes patches for problems that you discover (on a service level) as well as cumulative fixpacks, typically more often than on CE.
For clustering - especially for bigger clusters - there are some additional clustering options in EE that optimize the cluster communication in order to scale better.
Liferay Sync can synchronize multiple document libraries on EE, compared to a single document library in CE
Liferay Developer Studio, the commercial extension of eclipse, works with more application servers - especially the "big iron" servers while the CE/Open Source version Liferay IDE works with the open source appservers/servletcontainers.
Plus, you're supporting further development of the product directly.
That being said, however you decide, please get involved in the Liferay community and help to make the product even better
That is no prommical question, but I can say that EE get early bugfixes and EE is altogether robustly that CE.
Also, Liferay Portal EE has access to EE only marketplace applications, such as:
Kaleo Workflow Designer
Kaleo Workflow Forms
Auditing portlet
Reporting portlet
There may be more EE only applications but that is all I can think of right now.
I'm learning Liferay Portal Systems Development 2012 by Jonas X. Yuan. I tried to run sample code knowledge-base-portlet of chapter 3, but so many errors show up, like social-equity doesn't exist, viewJSP is not defined in java file etc., did anybody run it successfully on liferay 6.1.1? thanks
Not sure if he's using Liferay's standard knowledgebase plugin that you can find on the marketplace (source is available there or on github). It seems that the book is for 6.0 (couldn't find the information on the website, but it's released in January 2012), and it seems that knowledgebase is accessing deprecated APIs. Social Equity in Liferay 6.0 is called Social Activity in Liferay 6.1.
Is there a best practice for versioning SharePoint features?
Our SharePoint product gets a release every 3-6 months, and we need a way of clearly differentiating between the new version and the old version. We also need to support simultaneous installations of the new and old feature so that clients may test the new stuff before deploying it.
Versioning Features is not supported in Sharepoint 2007. In Sharepoint 2010 you can Version Features like you normally would version assemblies.
See the following post for more details: Feature Versioning and Upgrades in SharePoint 2010
Here is a excellent webcast by Jeremy Thake on feature versiong and upgrade :
http://sharepointdevwiki.com/display/SPPodCasts/2010/06/22/SPWebCast+019+-+Deep+dive+into+feature+versioning+and+upgrade+support+in+SharePoint+2010
Check out chapters 8 and 9 of our free SharePoint development guidelines. We have been using this strategy successfully for the last few years in both SP2007 and SP2010.