Re-Engineering One of World’s Largest Digital Archive & Delivery Platform




  • Archives largest and broadest collection of E-Journals, E-Books and Digital Content
  • Has a digital archive with hundreds of terra bytes of content
  • Owns more than 40 million E-Journals and over 30,000 E-books along with thousands of digital collections
  • All major Universities and research organizations around the world subscribe to the service offered by the client

State-of-the-Art Technology

  • AOP – Using AspectJ framework for Aspect Oriented Programming
  • Dependency Injection – Using Spring modular architecture
  • Responsive UI – Using SEAM and RichFaces
  • Performance – Using EHCache
  • ORM – Using Hibernate

The increased speed and capacity of application production capabilities, and the elimination of the production backlog, allowed us to become more transparent about the state of content during the preservation process. This kind of rapid development and excellent use of resources sets a great standard for us all, and I congratulate the team, for the leadership provided to make this happen.



Client is a leading digital preservation services organization in the world, archives the largest and broadest collection of E-Journals, E-Books and other digital content (digital newspapers, images and other primary sources vital to any research) of any third-party preservation archive. This archive is used by various participating libraries as a post-cancellation access point. To deliver the archived content, a legacy web based delivery platform was built in 2006 using Open Source Technologies on top of a Documentum Repository. The archive has hundreds of terra bytes of content with over 40 million E-Journals and 30 thousand E-Books as well as numerous digital collections.

The legacy web delivery platform had numerous challenges in terms of Security, Stability, Scalability, Extensibility and Performance issues:

  • Security – As content is assembled from multiple publishers and delivered to numerous participating libraries, setting up a Security Model where access for the subscribers could be setup easily was a challenge. It took at least a couple of weeks of manual effort or in some cases much longer to setup access permissions for a new publication
  • Stability – Platform was highly unstable as systems would go down under moderate concurrent load
  • Support – Legacy environment was an extremely complex setup and codebase changes or patch updates would result in long hours of downtime
  • Performance – The response time of the web pages was very slow, decreasing the productivity of the end users (library users)
  • Scalability – The platform was unable to scale beyond the current capacity. Client had a 20% growth rate on a yearly basis and the platform was unable to meet the demand
  • Extensibility – Any changes to the existing implementation required a complex effort and wasn’t easily extensible


Docmation team worked with both business and technical teams to design and implement a flexible solution involving state-of-the-art technology stack and design principles

  • Loosely Coupled:
    • All layers coded only to interfaces and not class implementations
    • Clear abstraction between Presentation, Service and Data Layers
  • Modular: Component based architecture (Search, Identity Management, Logging, Browse)
  • Pluggable Framework: Offered ability to modify existing business rules or add new behavior without having to modify existing codebase
  • Aspect Oriented: Modularized cross-cutting concerns using Aspects (Logging, Security, Transaction Management, Exception Handling etc.)
  • Configurable: Ability to quickly configure services exposed through the framework
  • Templatized UI: Ability to present personalized views based on scoping rules
  • Scalable Application Server Farm: Setup & deploy solution on a scalable Application Server Farm


  • Reduced support costs, as the stability/uptime of the application was significantly improved eliminating the need for the a FTE support resource
  • Increased scalability as the application is developed to be cluster aware, along with Application Server Farm with multiple nodes
  • Improved productivity with the ability to configure/provision content access using the Application UI instead of the backend
  • Higher revenues with the capability of new system to accommodate large content base (>100TB)
  • The legacy system was decommissioned within a month of launch

Other Case Study