Part of the assembly solution we created for Endeca was the Liferay Portal Framework. The assembly of this component was integral in that it provided the following: • A forum portlet with subscription and user management down to the thread level. • Robust user management • LDAP integration • AJAX based UI for improved user experience and performance • Ability to add your own custom modules and manage these A couple of items that didn’t meet our requirements where the blog portlet, user registration, user profile, and the Alfresco portlet integration. All of these items had functional requirements that required us to extend the functionality that was already provided within Liferay in order for it to work within the enterprise at Endeca. Blogs – The blog portlet provided by Liferay was basic and was at the time of our assembly not sufficient for the Endeca Developer Network. The team identified this early on and choose a java based blogging solution to integrate in time for the Beta launch of EDeN. The solution chosen turned out to have some limitations for the team supporting the blog application, mainly the end users were more comfortable with the user interaction of the more popular WordPress, and a php based solution. This solution had not been an option originally since the desire was to try and keep a pure java technology stack. The team then switched the blogging solution and created the user experience that made the solution work within the php/java mixed environment and the Liferay portal framework. User Registration – The user registration process for Liferay was not used so that Endeca could leverage a current registration mechanism already in place. The team stood up an LDAP server and created a process to migrate existing support site users from the Salesforce accounts they already had. This meant users that already had active support accounts could immediately gain access to the EDeN and manage that account without needing to reregister. Upon launch of the EDeN the team expanded this functionality from a batch update to communicating directly through the Salesforce API which made this experience completely seamless to the end user. User Profile – The user profile section of Liferay was expanded to include attributes that were valuable to Endeca and their end users of the system. This included their experience on Endeca products, a bio section, the user’s contributions to the community and the ability to share information that they wish to with the broader community. Alfresco – The standard Alfresco portlet available when performing this assembly was pretty basic, allowing the user to manage content within the portlet. This was not a requirement for this assembly solution. The team created portlets which allowed each content type to display attributes of the content and gave the user the ability to rate and comment on this content within Alfresco itself. Now Endeca has the ability to add content types within Alfresco and immediately make available the rating and commenting functionality that was provided by this assembly. Along the way Liferay and Optaros communicated what was being created and developed and shared these experiences so that we could better leverage these within the product roadmap that Liferay was currently executing against. This type of collaboration gives all parties the best possible solution both near and long term and is the core of the open source, solution assembly methodology that Optaros differentiates us against others in the marketplace.