Back in June we announced the Adobe Digital Enterprise Platform. The products you know - CRX and CQ5 - are now part of this platform - in fact - they are part of the foundation of this platform. Let's focus on CRX first:
The server companion for Flex
The Content Repository CRX with it's OSGi container and RESTful Web Framework Sling got extended to cover new use cases.
It has become the server companion for applications build with Adobe Flex. One example: we added support for new protocols e.g. AMF and RTMP that Flex applications uses to communicate with the server. We went as far as making sure developers using Adobe Flash Builder building applications have transparent access to data sources connected on the server e.g. a SAP system and the content repository content. We call this feature set "Data Services"
The combination of the Content Repository + Data Services and on the client side: Flex with the Client Component Framework (in short: OSGi for Flex) + a single IDE Flash Builder, is the next evolution of rapid application development. Create applications that run in browsers with the Flash Player and with Adobe AIR on desktop, mobile phones, tablets and TVs. And yes - that includes our beloved iOS devices.
We call this extended CRX version "Experience Server" - and when we talk about the feature set - we call them "Experience Services"
To learn more about building Flex applications using the Content Repository start here: .. and I'm sure you are very familiar with that already.
- You find more YouTube sessions on Flex with CRX on: http://www.youtube.com/user/ADEPDevelopers
- and check the Enterprise Platform Techies blog: https://blogs.adobe.com/eptech/
But that's not everything..
A new bridge to PDF
Wouldn't it be great to be able to do all the crazy things you can do with PDF (trust me.. it was a revelation for me) right out of your favorite Content Repository? We thought so too.
The technical solution is like that: We provide OSGi-based services to talk to the various PDF treatment services that are off-loading the bulk of the work to other servers (we call them "Document Services") - while you as a developer have a local Java API to talk to.
CQ5 is Web Experience Management
You are going to see us using the term Web Experience Management - short WEM - when talking about the CQ5 capabilities. The reason is because we are coupling the features of the Adobe Online Marketing Suite (aka Omniture) and the Adobe Creative Suite (yes Photoshop..) with CQ5 and this combination deserves a new name.
Read more about Adobe Online Marketing Suite integration on the Omniture Blog.
While we are busy finishing the bits internally - you can sign-up to get a notification when the trial version will become available. This form gets you on the list.