This is a promising session, even if Jeroen had to rename the slide from IIG Architecture to Documentum architecture in front of our eyes. As to why, first, it is Victor’s old session which was also a must attend. Second, Jeroen van Rotterdam, the Chief Architect of the IIG Division, is always a fun and entertaining presenter.

• Part 2 agenda (which I will attend and collect notes)
• Next Information Information Server
• Demo (really early prototype)
• Migration Path
• Presentation is combination of Thoughts, Architecture, Current Products, Projects, and Experiments
• Priority in 2010, D6.7, was on quality
• Priority in 2011 is Simplification, Innovation, Performance
• Simplified Deployment
• Web 2.0 UI
• Performance Improvement
• Public Cloud Architecture (Priority in 2011-2012 as this stuff supports cloud)
• Rapid App Development
• Integration Services (REST)
• Mystery announcement
• Trying to innovate across the entire stack
• Shows HA configuration diagram [Complete chaos]
• Doesn’t scale to multi-tenant public cloud architecture
• xPlore combines full-text with security model and faceted search capabilities (challenge to optimize)
• Documentum can scale, but it is complex [Nice nod to reality of large-scale implementations]
• 64-bit windows Content Server Implementation gives 4:1 reduction in Content Server count [Goodbye 1024 user limit!]
• 6.7 was a quality release, but a large number of features
• xPlore is part of the step
• Information Rights Management supports Office 2010 [Jeroen plugged IRM, so it must matter to them to some degree]
• TaskSpace has improved 508 compliance
• Xproc Integration [includes nice code sample]
• W3C standard to process XML content and generates new output
• Dynamic processing model for XML within Content Server
• Enable access to modern XML technologies, doesn’t dictate technology
• Helps leverage power of XML Store
• Requires 6.7
• Implemented DFS-style service, add-on to the Documentum stack
• Getting into fuzzier, less firm, future thoughts (Projects, not products)
• Looking to take your data model and create the REST services automatically
• Moving to a Spring-like development model with D7
• Case Management is the Application specific services versus the Core Platform Content Services
• UI Technology Demands
• Highly optimized custom user interfaces for thousand of applications
• Minimize the cost of application development
• Strong demand for web 2.0 UI technologies
• Strong demand for choice computing (mobile)
• Composite Applications:
• Application Model on top of…
• Component Library (controls…) on top of…
• Runtime Framework (ExtJs 4.0) on top of…
• Backend Services (Application and Platform Services)
• Feels that reference applications should be built within the community [Sounds a little like open source] UI and underlying apps
• vFabric (VMWare) is likely future of scalable platform
• Messaging, RabbitMQ
• Distributed Object Cache, GemFire
• Application Server: TC (Tomcat)
• Load Balancer: Apache
• Monitering (Hyperic)
• Documentum Hyperic Experiments
• Centralized control and monitoring is not easy
• Hyperic collects dictributed metrics and controls remote processes
• No coding in the stack, so can be deployed separately
• Tracks sessions among other things
• GemFire Experiments: Simplified type cache management
• Allows cache to be updated live
• Updates the disk cache faster
• Removes Session Cache
• Played with Queue Management and GemFire
• DFC Session Pooling Experiements
• DFC needs as many sessions as active users in 5 second window
• Context switch in pooling is expensive (authentication etc.)
• Defined Limit of users
• Want a smoother scaling of session resource utilitiztion
• Old: 10K getSession Calls: 6 minutes
• New: 10K get Session Calls: 8 seconds
• Moving to the Public Cloud, Big Picture
• Next Generation Architecture is the cloud
• Hybrid Cloud related announcement tomorrow
• Public Cloud Needs:
• Multi-tenancy
• Add/Remove/Disable tenants instantly
• Self-registration
• Zero marginal costs per tenant
• End-user might become micro-tenants as well
• No third party components (i.e. databases)
• Dynamic provisioning
• Guaranteed service levels
• Wide variety of SLA’s per tenant
• No downtime
• Rolling upgrades
• Rebalancing of resources
• No backup dependency, still need HA via replication [and not like Amazon did it]
• Virtualization
• Billing and metering facilities
• Three layers in stack
• Data Management layer
• Information Management fabric on top
• Business Application Components on top of fabric
• Need Management Services and Builder Applications
• Data Providers: XACML (authorization), xPlore, NGIS/xDB for Metadata, Analytics from Greenplum, Cache with GemFire (underline is more certain component & 1st focus for 2011)
• Fabric: Collaboration Services, Retention Policies, Capture Services,BPM Services, Content Intelligence Services (CIS), IRM Services, etc….Want ability to prices at each execution of a service
• Builders: Forms, processes, UI, Search, Rules, Data Sources… [See my post last week on the challenge]

Off to Rick Devenuti’s keynote. See you there.

Disclaimer

All information in this post was gathered from the presenters and presentation. It does not reflect my opinion unless clearly indicated (Italics in parenthesis). Any errors are most likely from my misunderstanding a statement or imperfectly recording the information. Updates to correct information are reflected in red, but will not be otherwise indicated.