Adobe Digital Enterprise Platform / Architecture
Building state-of-the-art composite content applications today requires an unprecedented openness and connectivity into the existing environment to fully leverage existing data sources and process investment. The open, standards-based Adobe® Digital Enterprise Platform (ADEP) is the next generation of enterprise content management (ECM) for designing and delivering applications that result in customer experiences that exceed expectations.
Service container
The service container provides a common runtime environment to support all solution components and associated services. It also provides an event framework that enables business events to be defined as follows:
- ADEP supports a number of event types, including asynchronous, exception, and timer events.
- Events can be raised or received within processes or linked to external events on a messaging bus through integration with Java™ Message Service (JMS).
Open content architecture
With the next generation of ECM, the ADEP composite content application platform provides a modern architecture for easily managing and deploying content as web and UXA applications through the following standard interfaces:
- Java Content Repository API 1.0 (JSR-170) and 2.0 (JSR-283)
- Content Management Interoperability Services (CMIS)
- WebDAV, including versioning, access control, and search
- Common Internet File System (CIFS) and Server Message Block (SMB) to act as network file share
- RESTful web API to build JavaScript-based content applications
- LDAP and JAAS for user provisioning
- Remoting with RMI and HTTP over DavEx
- Mounted content from third-party repositories via the native interface, for example, Microsoft SharePoint
Web-scale deployments
Recognizing that developers must be able to respond quickly to changing demands and restructuring requirements, Adobe designed ADEP with maximum deployment and development flexibility in mind. The platform offers these capabilities:
- Provides a high-performance content repository driven by a small footprint runtime using hot-join clustering to extend capacity and distribute load
- Does not rely on relational database management systems (RDBMS)
- Stores highly optimized enterprise content in virtually any format (images, documents, forms, websites, RIAs)
Content repository
Once an application is deployed, all of the information goes into the ADEP central repository, and all the systems in a single or clustered JEE system get their components from that repository. This greatly simplifies application deployment and enables many timesaving capabilities, such as:
- High level of scalability
- Form fragment libraries for reuse
- Auditing for management
- Versioning for structured development and deployment
- The ability to package related assets into groups that can be collectively archived
