Pages

Sunday 8 March 2015

SaaS (Software as a service) with Liferay


 Yes, you are surprising na... why I have included SaaS over here, Its there from the first release of liferay. I am just trying too map some facts by which you can design  your liferay implementation on Saas standards.

I will not explain what is SaaS & its features you can read it from wiki.


As you know liferay is horizontal portal i.e 


Specialized website (portal) that serves as an entry point to several firms in the same industry or to the same type of suppliers. See also vertical portal.

80% of portal used to implement to fullfil the above ask ahh?

So why not make it deliverable to end user in such a way that we can sell it on subscription basis. 

With the help of example it will be easier to understand and then implement in actual real life portal.


Inkwell company got an order to deliver POS(point of sell) for a medical outlet "M.M medical store".

Now some good Architect decided to deliver it in Liferay. Since blank fresh Liferay was already there on cloud. So it will save lots of installation & setup work.

One of the solution architect decided to hire a experinced developer of POS. He can develop a POS in 20 days with using traditional spring hibernate code.

Now take his code & convert his project to Liferay portlet.

That's its


Development has ended with this. Now we will have to play with liferay configurations.

In default liferay instance create an site(organization) named as "M M medical store" on its private page deploy the war which you have developed from liferay IDE.

create a site administrator user for MM site.

Benefits & Execution of SaaS after first client 


1. You can restrict no. of user in MM site.
2. you can schedule the expire of MM site after a fixed interval of time as per subscription plan.
3. you can create new site if new client comes for same requirement.
4. you can give different look & feel for different site.
5. With single server you can server N no. of  client,
6. No need to develop and deploy code again
7. each client can get updated & bug fixes code by default.
8. Only one super administrator can control whole single type of domain.
9. you can give option to client pay as you grow.
10. you can show zero processing fess & installation in seconds to client/
.

and many more.




Keep sharing, what you learn... :)

Tuesday 13 January 2015

GenericPortlet in Liferay


As per JSR286 , Portlet Specification 2.0 we can create portlet on above of liferay that follow standard as per specification so that in near future when we want to switch Liferay portal with any other portal server like Jboss we need not to change code.