Alfresco Software Inc. has announced the available of download of Alfresco Community 2.1. The release is designed with Web Script technology that provides access to enterprise content, metadata, user interface components, and queries using a URL interface. Utilizing new Web 2.0 integration techniques, Web Scripts can enable web sites, portals, blogs, applications, and Microsoft Office to access or mashup enterprise content without integration tools and complex programming. The designed scripting capabilities allow the development of mashups by using web technologies that enable scalability. Alfresco Community 2.1 has been designed to deliver access to content from the user’s tool of choice (Office, portal, website or Web 2.0 property as simply as accessing a URL.) The product provides access and mashup of internal and external content (without requiring complex .Net or Java programming); and scalability through proven web-oriented and REST architecture.
Alfresco Community 2.1 offers the following new capabilities: Native Office Integration --building on the ability to view the Alfresco repository as a shared drive through the existing CIFS capability, Alfresco 2.1 offers full document management from within the Office environment, as well as MySpaces, MyDocuments, MyTasks, and MyWebForms panes. This is in addition to content services such as check-in/check-out, version control, auditing, workflow and PDF generation; Enterprise Portal Integration--Liferay and JBoss portal JSR-168 Web Script access to MySpaces, MyDocuments, MyTasks MyWebForms; Enterprise Content Publishing into Blogs – WordPress and TypePad; Web 2.0 User Interface – Fisheye Drilldown, AutoPreview, Cross Platform Dashlets with Personalization.
These capabilities are available due to the next generation web-oriented architecture delivered through Web Scripts, which are the foundation of simple cross platform access, mashups, and web scalability. A web-oriented architecture simpler than a service oriented architecture because: URL access vs. SOAP; Lightweight scripting vs.Net or Java programming; mashup of internal and external vs. internal services only; Common Web Standards – OpenSearch, URL, JSON, RSS, ATOM vs. Proprietary API’s. Enterprise Edition 2.1, which will include service and support, is expected later this year.