Rich Sezov

Author
+ Follow
since Dec 13, 2006
Merit badge: grant badges
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
1
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Rich Sezov

You might want to try getting the User out of the ThemeDisplay or ServiceContext objects instead. That always works for me.

--Rich
12 years ago
Hi Yolande,

This all, of course, depends on how your LDAP directory is configured. If you're running LDAP unsecured (i.e., the ldap:// protocol), passwords are in the clear. If you're running LDAP secured (ldaps://), passwords are encrypted.

Instructions for connecting Liferay in a secure way to LDAP are in Liferay's documentation here, and it uses Active Directory as the example:

http://www.liferay.com/documentation/liferay-portal/6.0/administration/-/ai/global-server-settin-4

Hope this helps!

--Rich
12 years ago
Hi,

Liferay has many ways it can be tuned. It's hard to say exactly what might have affected your particular installations. From a code standpoint, if you're deploying Liferay into a situation where performance is key, out of the gate, EE will perform faster than CE. Liferay implements new features, puts them into CE, gives them bug fixes, and then performance optimizes them for EE. So generally, every new CE release gets the performance optimizations from the previous release, but not the ones for the current release.

I did a presentation on this several Liferay symposiums back; I'll give you the main points from that presentation:

1. Adjust the server's thread pool and JDBC connection pool. You have to use a profiler and tune to the right number.

2. Turn off unused servlet filters. This can be done through the portal-ext.properties file.

3. Tune your JVM parameters. Again, you need a profiler for this.

4. Tune Liferay's cache. If your site makes heavy use of CMS objects, but not so much wiki objects, you will want to tune the CMS cache appropriately.

5. Change the Lucene index writer interval. If you're doing mostly reads, make it low. If you're doing mostly writes make it high.

6. If search is a big part of your site, offload it with Solr, and use the Solr plugin.

7. Optimize the counter increment (counter.increment in portal-ext.properties). Set it to a higher number to reduce database calls.

8. Use a CDN for static content (cdn.host).

9. If you can't use a CDN, use a web server to serve your static resources. This is done via three steps: 1) set theme.virtual.path to your Apache root, 2) Set the <virtual-path> property in your theme, and 3) Set your server proxy to exclude from the proxy the path to the theme.

10. Use Liferay's tag libraries for your code. They already include optimizations, such as the auto-creation of CSS/JS sprites for your images.

11. Use a Read-writer database. This is one database optimized for reads, and one database optimized for writes. Properties are jdbc.read.* and jdbc.write.*.

12. Use Liferay's sharding support.

Hope this helps!

--Rich
12 years ago
Yes, there are several ways.

1. You can create the site on one portal, then export the configuration into a LAR file, then import it into another portal server.

2. You can use Liferay's remote staging facility to push pages from a staging server to the production server.

3. You can write a hook that programmatically creates the site (the 7cogs-hook which ships with Liferay CE is a good example of this).

Hope this helps!

--Rich
12 years ago
Hi Jay,

My advice would be to look at Liferay's reporting portlets, which are based on Jasper. There are also portlets provided by Pentaho which you might have some success with. I think Liferay's reporting portlets may be EE only, so to get access to them, you'd have to contact a Liferay sales representative and get an evaluation license.

Hope this helps!

--Rich
12 years ago
Hi Yolande,

Liferay gives you various methods of connecting to LDAP. Of course, the preferred method is BIND, which Liferay defaults to, and in that case, Liferay doesn't have to store the LDAP password in the database. For binding, encryption is provided by the com.sun.crypto.provider.SunJCE class. If you elect to use the password-compare method, Liferay offers many different algorithms you can choose:

ldap.auth.password.encryption.algorithm=BCRYPT
ldap.auth.password.encryption.algorithm=MD2
ldap.auth.password.encryption.algorithm=MD5
ldap.auth.password.encryption.algorithm=NONE
ldap.auth.password.encryption.algorithm=SHA
ldap.auth.password.encryption.algorithm=SHA-256
ldap.auth.password.encryption.algorithm=SHA-384
ldap.auth.password.encryption.algorithm=SSHA
ldap.auth.password.encryption.algorithm=UFC-CRYPT

Hope this helps!

--Rich
12 years ago
It's really hard to know; it could be a caching issue; a session management issue (i.e., sessions aren't getting destroyed when users log out); or an issue with the code in the application itself. Can you post any more details about your application?

--Rich
12 years ago
Yes; at this point I believe Sumit is correct. It has, however, been proven to work on Amazon's cloud service.

--Rich
12 years ago
Hello Raja,

Certainly it is possible to migrate from Sharepoint to Liferay. Liferay has all the collaboration apps that you need in order to make users more effective than they would be on Sharepoint. Liferay 6.1, which is due to come out this fall, will also add the Dynamic Data Lists feature, and it will be fully integrated with Liferay's workflow. It's in the last stages of Alpha right now, and there should be a beta release of this within the next month. I'd encourage you to try that out when it comes out so you can see how it works.

The book has a case study, but it's not a migration case study. We build a site from scratch over the course of the book.

--Rich
12 years ago
Hi Michael,

To answer your questions:

1. The book is all about Liferay development. The purpose of the book is to show developers how to use Liferay as a platform for their web sites.

2. Since the book focuses on Liferay and its many APIs, there wasn't space for integration topics, as I wanted to make sure I covered as much Liferay functionality as possible. But if there's good demand, and the book is a success, I may be able to tackle some of those topics in a 2nd edition.

3. There aren't specific product comparisons in the book; I sort of thought that was the job of salespeople and not me. I'm just a technology guy, and like to write about the technology.

Thanks!

--Rich
12 years ago
Hi Evelyn,

It's hard to answer your question without further details; it sounds like a JavaScript bug in whatever theme you're using (hope it's not the default), or maybe a cache issue with the web browser. What version of Liferay are you using? Can you log in as the 2nd user and then reload the page and see if that fixes it?

--Rich
12 years ago
Hi Mark,

Yes; this book has been designed to take somebody who knows Java web development and turn them into a Liferay developer.

In fact, during development of the book, Manning thought I was going too slow and had me move some material into appendixes in order to get going with development faster. So some background information about portlets and IDEs and such now appears in appendices.

I wanted to cover several frameworks in the book (Spring, JSF, etc.), but I wasn't able to get to that material, and so I stuck with Liferay's MVCPortlet framework. This is really nice and easy to use, because it uses conventions rather than XML config files or annotations. So once you learn the conventions, you know how it works, and then everything works in the same pattern.

Hope this helps!

--Rich
12 years ago
Hi there,

Liferay is much, much more than Tiles. While Tiles is a templating engine which helps with web applications and static web sites (and has been used with Struts for a long time), Liferay is both a complete product and a development platform. I like to call it an engine that runs web sites. Liferay out of the box is a content management system (complete with both local and remote staging, as well as content structures and templates), a collaborative suite (message boards, wikis, blogs), and a social network. On top of the platform, you can build any kind of site you like. It's very powerful.

The book does talk about why Liferay is better than other platforms out there. In fact, that stuff is in the first chapter, which you can download for free.

The nice thing about Liferay for architects is how freeing it is. You don't have to worry about user management anymore; Liferay handles user account management beautifully. And if you already have that in place, Liferay can connect to LDAP directories and integrates nicely with single sign-on. And it's server and database-agnostic, so you can use it with all the major app servers, from Tomcat to WebSphere, and all the major databases, from MySQL to Oracle. You can stick with the infrastructure standards you have and still use Liferay, which is probably one of the most attractive things about it to an architect who has to figure out where in the infrastructure it will fit and how it will be used.

I encourage you to download it and give it a try!

--Rich
12 years ago
Thanks; it's great to be here! The book is actually called Liferay in Action, but in Depth works too.
12 years ago