What’s New in Documentum 7.3
•Download as PPTX, PDF•
3 likes•4,595 views
This document provides an overview of what's new in Documentum 7.3, including: - The introduction of stateless Documentum and application containers using Docker for continuous delivery and faster upgrades. - Enhancements to security features like SAML 2.0 single sign-on and updates to the Java Development Kit update tool. - Expanded REST APIs and support for CMIS 1.1 for improved integration and user enablement. - Optimization and automation tools aimed at reducing the effort required for patches, upgrades and overall administration.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Similar to What’s New in Documentum 7.3
Similar to What’s New in Documentum 7.3 (20)
Recently uploaded
Recently uploaded (20)
What’s New in Documentum 7.3
- 1. 1© Copyright 2016 Dell . All rights reserved. 1© Copyright 2016 Dell. All rights reserved. What’s New in Documentum 7.3 Michael Mohen, Chief Architect, DE Tara Shaw, Product Management
- 2. 2© Copyright 2016 Dell . All rights reserved. • This presentation contains “forward-looking statements” as defined under the US Federal Securities Laws. • Dell EMC makes no representation and undertakes no obligations with regard to product planning information, anticipated product characteristics, performance specifications, or anticipated release dates (collectively, “Roadmap Information”). • Roadmap Information is provided by Dell EMC as an accommodation to the recipient solely for purposes of discussion and without intending to be bound thereby, and is subject to change without notice. • Roadmap information is Dell EMC Confidential Information, and is provided under the terms, conditions and restrictions defined in the Dell EMC Non- Disclosure Agreement in place with your organization. Safe Harbor Disclaimer
- 3. Recent News • Business as usual until close: 90-120 days • Roadmaps have always been under NDA and subject to change • Momentum ECN for FAQs and ongoing communications • Follow SPARK blog for executive updates - sparkblog.emc.com “Dell EMC and OpenText are committed to supporting customers through the transition with world-class support. In addition, it’s OpenText’s intention to maintain and invest in ECD’s portfolio to protect customers’ investments in their current products and solutions.” - Mark Barrenechea, CEO & CTO, OpenText
- 4. 4© Copyright 2016 Dell . All rights reserved. Documentum Platform Services Documentum Platform* • Documentum Content Server (CS) • Documentum APIs / SDKs • Documentum Foundation Classes (DFC) • Documentum REST Services • Documentum Foundation Services (DFS) • Content Management Interoperability Services (CMIS) • Thumbnail Server • Documentum Tools • Documentum Administrator (DA) • Documentum Composer • Search and Indexing • xPlore • Content Intelligence Services (CIS) • Federated Search Services (FS2) Documentum Platform Extensions * • Branch Office Caching Services(BOCS) • High Volume Server • Content Storage Services (CSS) • Content Services for NetApp SnapLock Content Transformation Services • Media Bundle * • Documents Bundle * • Audio-Video Bundle * • XML Transformation Services * Trusted Content Services(TCS) * * - Separately licensed
- 5. 5© Copyright 2016 Dell . All rights reserved. Continuous Delivery: Stateless Containers for Fast Upgrades & Patches Trust & Security: • SAML 2.0 SSO • JDK Update Tool • Cross Forest Kerberos New User Enablement: • More REST Services • CMIS 1.1 • Better Together LEAP integrations Lower Total Cost of Ownership: • Open Source • Simship Documentum Platform 2016/2017 Key Themes
- 6. © Copyright 2016 Dell Inc.6 Patches and Upgrades #1: Alleviate Heavy Activities Optimizations • Unattended Install / Upgrade Tools • Preservation of Customizations • Dormant State for Non- Admins Best Practices • ACL clean-up • Workflow preparation • Audit File clean-up 20% Reduction in Administration Effort Scripts • Rename Docbase • Change Docbase ID • Change Install Owner
- 7. © Copyright 2016 Dell Inc.7 Making Upgrades Even Faster #2: Addressing the Root Cause of Downtime RE-INDEXING CHALLENGE NO FORCED CHANGES STATELESS DOCUMENTUM
- 8. © Copyright 2016 Dell Inc.8 Making Upgrade Easier with Application Containers #3: Uniform Portability without Disruption Docbase “BEDROCK” Docbase 7.2 Content Server 7.2 STATELESS DOCUMENTUM 7.3 APP CONTAINER
- 9. © Copyright 2016 Dell Inc.9 Containers are isolated but share OS, and bins/libraries where appropriate, for lightweight efficiency VMs Every app, every copy, every modification requires a new virtual server Containers • Original Container has no OS, so less space, resources, restart time • Copy can share bin/libs • Union filesystem can save deltas between modified containers Original Copy Modified VM Container 40% to 80% savings in hardware Docker vs. VMWare #4: Certification of Extremely Lightweight Containers
- 10. © Copyright 2016 Dell Inc.10 Docker - High Level Deployment
- 11. © Copyright 2016 Dell Inc.11 Docker Swarm
- 12. © Copyright 2016 Dell Inc.12 Docker Swarm
- 13. © Copyright 2016 Dell Inc.13 Stateless Documentum and Docker #5: Continuous Delivery to Production PRODUCTIO N BEDROC K Up to 95% savings in upgrade effort and downtime
- 14. 14© Copyright 2016 Dell . All rights reserved. Documentum Application Containers #6: Flexible Deployment Support DEVELOPER / POC INDIVIDUAL SERVICES STATELESS DOCUMENTUM
- 15. 15© Copyright 2016 Dell . All rights reserved. Planned Documentum App Containers #7: Certification Across the Solution Stack Platform Content Server & DocBroker xPlore & CIS BOCS JMS Webtop Documentum Administrator REST Services RPS D2 D2 Config D2 Client xCP BPM BPS XDA App-host Q4/2106: Linux (CentOS, Ubuntu); Oracle/PostgreSQL; Tomcat Microsoft WS2016 for post-Bedrock ALSO Best Practices for “Grown-at-Home” containers
- 16. 16© Copyright 2016 Dell . All rights reserved. Easy Migration to Containers #8: Adopt Docker when Ready Repository On Premise Content Server Hosted Content Server Content Server Content Server
- 17. © Copyright 2016 Dell Inc.17 Trust and Security • SAML 2.0 SSO • Cross Forest Kerberos • JDK Update Tool
- 18. 18© Copyright 2016 Dell . All rights reserved. Admin, Performance, TCOExperience Docker SSO Admin Console Push Config to multiCPS Preserve Config Profiles Fast Thesaurus Import Wildcard Cut-Off Feedback Search: xPlore 1.6 Pause Rebuilds per Collection ReFeed Feedback & Resume Optional Position Information Advanced Collection Routing ACL Cache Controls Fast Search within Folders Mixed Language Indexing SKOS two-way expansion Multiple Term Optimization Non Admin Reports
- 19. 19© Copyright 2016 Dell . All rights reserved. CMIS 1.1 Browser Binding (JSON) Append to Stream Bulk Property Updates
- 20. 20© Copyright 2016 Dell . All rights reserved. CMIS Comparison by Vendor http://cmissync.org/CmisCompat/
- 21. 21© Copyright 2016 Dell . All rights reserved. Documentum REST Services Saved Searches Search Templates Advanced Structured Search with Facets User Group Management User Preferences Access Control SAML 2.0 Value Assistance Lightweight SysObjects Aspects Virtual Document (read-only) Retention Workflow Transformation Collaboration Comment Services UNDER INVESTIGATIO N
- 22. 22© Copyright 2016 Dell . All rights reserved. Environmental Pressures on Content Transfer
- 23. 23© Copyright 2015 EMC Corporation. All rights reserved. Applet-Free Transfer No dependency on JRE plug-in or applets New Browser Plug-in takes place of Java Applets to interact with OS filesystem Shields web applications from future changes UCF (Webtop & DA) Native clients (D2 & xCP) D2 Goblin (Q4) | Webtop Aragorn (Q3) | DA Bedrock (Q4) | xCP Moonbow (Q3)
- 24. 24© Copyright 2016 Dell . All rights reserved. Product Downloads from Online Support
- 25. 25© Copyright 2016 Dell . All rights reserved. Online Support Matrix
- 26. © Copyright 2016 Dell Inc.26 7.2 (FEB 2015) Business Transformation Enablement • Software-defined storage and hyperscaling (ViPR & ECS) • Search, batch transactions and extensibility for REST Content Lifecycle Management • WORM data protection with retention (Data Domain Retention Lock, Isilon SmartLock) • Flexible indexing optimizations for xPlore IT Management • TOP SECRET protection for content at rest and in transit (AES-256) • Administrator-proof protection for primary application keys (RSA Lockbox) • Additional enterprise authentication updates (SHA-2, Kerberos Constrained Delegation) • Automated AEK encryption key upgrades 7.3 “BEDROCK” (Q4 2016) Business Transformation Enablement • Stateless Documentum • REST for Value Office Solutions • CMIS 1.1 Content Lifecycle Management • CTS Documents • XTS IT Management • Portable Containers via Docker • Unattended installers (No UI) • Customization preservation • Distributed authentication (SAML) • PostgreSQL, CentOS, Ubuntu • Applet-Free Transfer • JDK Update Tool • Cross Forest Kerberos • AWS, Azure VERSION GA DATE EOPS DATE EOES DATE 6.6 15 JUN 10 30 JUN 14 30 JUN 17 6.7 29 APR 11 30 APR 15 30 APR 18 6.7 SP1 13 DEC 11 30 APR 15 30 APR 18 6.7 SP2 28 FEB 13 30 APR 15 30 APR 18 7.0 21 NOV 12 30 NOV 16 30 NOV 19 7.1 11 NOV 13 30 NOV 17 30 NOV 20 7.2 09 FEB 15 28 FEB 19 28 FEB 22 Recent & 1H 2016 Next All dates in blue are past GA dates All dates in green are committed GA dates All dates in orange are targeted GA dates All items in purple are exploratory work with no targeted GA date yet. CONFIDENTIAL – INTERNAL USE ONLY. DELL EMC makes no representations or commitments, and undertakes no obligations with regard to product planning information, anticipated product characteristics, performance specifications and functionality, or anticipated release dates (collectively, “Roadmap Information”) as provided. Roadmap Information is provided by DELL EMC as a courtesy to the recipient solely for purposes of discussion and without intending to be bound, and is subject to change without notice. Business Transformation Enablement • LEAP integrations • Hybrid Bridge Content Lifecycle Management • Federal Standards • xPlore billion object benchmark IT Management • Segregated Security Roles • Independent JMS • S3 Storage Support • Cryptography-Free binaries for Russia & China • Root-free scripting • DockerHub • Windows 2016 Docker
- 27. 27© Copyright 2016 Dell . All rights reserved. JOIN THE CONVERSATION! #MMTM16 Take the LEAP personality quiz and win! Connect with us ECD SERVICES Genius Labs Garden Level Foyer
- 28. 28© Copyright 2016 Dell . All rights reserved. MOMENTUM BARCELONA APP AND WIN! 28 http://bit.ly/mmtm16BCN © Copyright 2016 Dell . All rights reserved. BEYOND SILOS Play the BEYOND Game and win a Raspberry Pi pre-loaded with InfoArchive
- 29. 29© Copyright 2016 Dell . All rights reserved.
Editor's Notes
- You may have seen this text in other sessions, but it is worth displaying again: this session includes forward looking statements, and anticipated product features, and while EMC makes every attempt for these to be accurate, they are subject to change and should be used for the purposes of discussion. Also, please note that all of this information is subject to the EMC Non-Disclosure Agreements in place with your organizations.
- TOP AREAS OF CUSTOMER CONCERN DRIVING DEVELOPMENT Effort, Risk, Disruption of Upgrades / Patches Total Cost of Ownership within SDDC Trust and Security New User Engagement Analytics
- Started with what customers were asking for Optimizations for the current installers And Best Practrices to prepare and modify repositories No big changes, no disruption
- Platform releases are 18 to 24 months. Where would customers need to be in two years? Could we go beyond current expectations? RE-INDEXING CHALLENGE Each Database change requires re-indexing usually blocking database Sequential scripts adds up the hours quickly The answer: ELIMINATE FORCED CHANGES No Changes forced during an upgrade; anything for new features can be post upgrade No disruption due to big Architectural changes Enables: STATELESS DOCUMENTUM Decouple from Repository for Binary-Only updates Upgrade = Point Content Server 7.3 to D7.2 Repository Eliminates Downtime due to Reindexing Upgrade Time is independent of Repository size
- CHALLENGES COMPLEX PLANNING to REDUCE DOWNTIME ROLLBACK PRODUCT INSTALLERS CONFIGURATION PORTABILITY UNIFORM ACROSS STACK (UPGRADES and PATCHES) DEPLOYMENT OF NEW STATELESS DOCUMENTUM Benefits of CONTAINERS Virtual Application Container Production Ready – No Installers, PreConfigured Quick deployment to any cloud system or OnPrem System-as-is with various deployment strategy Quick deployment and rollback
- Proper selection of containers is necessary for: Separation of concerns Automation Efficiency Broad ecosystem Containers are much more efficient than VMs: Containers are isolated but share OS and where appropriate bins and Libraries. No OS is necessary Fewer resources Less restart time Many apps and app variations can be supported by the same runtime engine
- Uniform upgrade and patch process across all Documentum solution stack Very easy to understand and implement according to established container paradigms
- Developer/POC: All-in-One Container for Functional Investigations – quickly get to try out the next release – replacing our Developer Edition Service Images: Individual Service Containers for Agile Expansion and Load Balancing Xplore, Rest, DA, etc. Stateless Documentum External Content, Database & Isolated Configuration for Fast Patching & Upgrades We’re also working on High Availability setups Migration from On Premise Container creation via silent installers
- Note that we aren’t limiting Docker certification to the Content Server and a few platform components. We will be releasing reference images across the Documentum stack. You can build out your solution or wait until our Value Office Solution (LS, EPFM, AO, etc) support for Docker post Bedrock. Note that our references will be based on Linux since Microsoft just certified Docker in WS2016 for Production last week. We’ve been using the beta in our labs, so expect more information on for Documentum and Docker for Windows-SQL Server in the future. Also note that we will be providing information on how you can develop and a grown at home container solution.
- Add Docker containers along side existing Documentum (co-exist) Deploy extra Docker containers to manage high volumes Migrate to Docker by turning off original non-Docker instances
- 1) What are the planned features and improvements in xPlore 1.6 as part of DCTM 7.3 release in November? I list all features on Bedrock with brief after my signature. 2) Does xPlore 1.6 support Linux RHEL 6.7? Yes. It has been certified. 3) Does xPlore 1.6 on RHEL 6.7 support Content Server 7.1 on RHEL? Yes. We had tested xPlore 1.6 and CS 7.1 on Windows during compatiblity testing. We are confidence it works on RHEL as well because the most implementetions are in Java and platform independent. 4) Currently we deployed xPlore 1.5 on Linux RHEL 6.7 with Content Server 7.1 on RHEL. Is there a direct, in-place upgrade path from xPlore 1.5 to xPlore 1.6 on Linux RHEL? Yes. Pfizer can refer to in-place upgrade steps listed in admin guide. 5) Do we need to reindex the docbases to deploy xPlore 1.6, or xPlore 1.6 can reuse the xPlore 1.5 index? Do we still receive the new features and improvements of xPlore 1.6 if we reuse xPlore 1.5 index? Reindex the whole docbase is not mandatory. Upgrading from 1.5/1.4 to 1.6 doesn’t require customer to re-index their docbase. The old index can still be used by 1.6. Some features can benefit customer directly, including some query optimization, metadata highlighting (customer has to change their xquery to highlight fields they desire), thesaurus improvements. But below 2 feature requires user to reindex data if they want to get benefit. They have to turn on them manually via modifying indexserverconfig.xml. By default, those features are turned off. If customer turns on those features, it’s highly recommended customer cleaning their existing data and re-index their docbase to guarantee their data consistency. • Make the position information in index as optional • CPS indexes Multilingual content Thanks, Dingmeng Xue • Trust: o Non-Admin users can run reports There is typically a need for non-admin users to run and view reports, and system status. The current version of admin interface restricts the xDB admin to have access to admin interface. With this new feature, an access management console is setup that will allow for users with different privileges; access different resources. o Support user authentication in Admin Console Follow up above feature. Admin Console can use Documentum content server to do authentication. Admin Console uses white list to store all empowered user but their password would be in Content Server even LDAP. When user login Admin Console, the user credential will be sent to CS. It will allow Admin Console to leverage CS’s SSO capability. • Improved Content Management o CPS indexes Multilingual content In the current offering, CPS identifies the language of the content, file-by-file. So where there are files with multiple language, then such files yield a no match, when the search-key is of a quoted language. Say for instance, if a file was identified as english, and there was french text in that file, then a search for a French key word will not yield a match. With this feature, we can now search on multi-lingual file English and French would not be a good example, because their tokenization would be very similar. You can mention the content has English and Japanese. Since Japanese has totally different tokenization method. In xPlore 1.5, we will process this document only using one language. Then another language will be ignored and cannot be hit. o Flexible object routing mechanism: Offer a new approach that user can store the document to specific collection according to their configuration. Such as user can store the document according to its content type, create date, user name or any other attribute. o Pause and resume rebuilding index Indexing of content requires a fair share of the CPU power and it helps to have control as to when to ask for a bigger share of the CPU power and when to let-go of the CPU share; like in giving away processing capability to serve the user needs. This feature - Rebuild index on Admin Console, help users manage rebuild index task on each collection. User can continue previous work to process multipath index instead of redo it. A progress bar in the admin interface, will show the statistics of indexing process. o Support SKOS format two-way expansion With a two-way expansion, it is possible to use "animals" to find "creatures" and also use "creatures" to find "animals” o Re-feed specific data set in doc repository via index agent: In xPlore 1.5, user can upload a txt file containing the list of object ids to IndexAgent and IndexAgent reads this file and do re-feed (loading the data from content server and send them to xPlore Index Agent) one by one. User also can specify the id list through one DQL. This function can help user easily re-feed those objects and fix their content in xPlore Index Server. There would still be failed object because environment issue and customer would want to retry. The shortage was user can trigger a re-feed process but cannot see the failed objects. Another critical design issue was IndexAgent doesn’t store the status of each re-feed item. If customer restarts IndexAgent, the whole process will start from the beginning. It’s unacceptable to customer if they submit a list with thousands of ids. Since Bedrock, IndexAgent will store the status of the list. Once user restarts the system, IndexAgent resume the process from the breakpoint. End user can see the status and export the list of failed ids during re-feed. • Performance and scalability: o Optimize multiple term phrase search: User sometimes uses multiple terms to do the query such as querying “architecture diagram”. The search terms have diverse frequency in whole document set. Some would be very selective but some would be not. So we optimize the search logic and search selective query with higher priority. o Improve performance of folder descend query: Original folder descendent query needs to load all its descendant folders which is very expensive operation if parent folder has many descendant folders. So we optimize the process in this release and use cache to speed up folder navigation. o Make the position information in index as optional Position information needs additional storage in full-text index. We offer an option to turn off it. The benefit is index size will reduce to one fifth. Smaller index file, faster search speed. The sacrifice is phrase match query cannot be supported. Such as querying “enterprise content management”, we only return document which contains exactly 3 words together with same order. If no position information, it will return any document as long as it contains those 3 words no matter their position. o Import and update large volume of thesaurus file Import large thesaurus file is very heavy option in old xPlore version even making system to be out-of-memory. We optimize file parser in this version and it can handle the big file smoothly. o Queries derived from cache: ACL is using cache to speed up calculation. However customer would have no idea to adjust the size of cache. We will log the cache hit ratio. Administrator can check the log to understand whether the performance is impacted by the cache. o Cut-off notification for wildcard execution Wildcard search has internal cut-off mechanism to mitigate risk of unselective query. We expose new API on DFC level to tell user whether cut-off applies for this query and how many terms are selected for this query. • Reduced TCO: o Configure multiple CPS instances via Admin Console uniformly This feature provides an easy way to apply and keep all CPS instance configuration keep consistently. Configuration will be pushed to different cps instance after click “save” button. These CPS instances have to be registered on Admin Console. o Preserve configuration profiles during upgrades During upgrade, all customer’s configuration in index server, xdb, Index agent, admin console, and CPS will be preserved. o Certify Docker Deployment Generate docker image contains xPlore out-of-box configuration. and certify its quality running in Docker container
- How many people are using or have used CMIS with Documentum? Browser Binding, bulkUpdate properties and Append to a Content Stream Content Management Interoperability Services 1.1 : Browser Binding JSON Payload. A binding is the protocol a client uses to talk to a CMIS server. CMIS 1.0 supported two bindings, Web Services (SOAP) and AtomPub (RESTful XML), the latter being the most performant and the most popular. But if you’ve ever looked at the XML that comes back from a CMIS AtomPub call you know how verbose it can be. The Browser Binding is based on JSON, so the payloads that go between client and server are smaller, making it the fastest of the three bindings. The original purpose of the Browser Binding was to make it easy for those building “single page” web apps or doing other work with CMIS via client-side JavaScript, but I think apps of all types will move to the Browser Binding as quickly as possible simply because it is easier to work with Bulk Updates CMIS 1.1 adds a new feature that makes mass changes more performant. Instead of iterating over a list of objects, changing and saving each one, you can define a set of property changes and make those against an entire collection, which is much more efficient. Append to Content Stream A challenge with any ECM project is how to move large files into the repository. The new append to content stream feature in CMIS 1.1 allows you to send files to the repository in chunks which could be a key to addressing that challenge.
- REST services are fundamental to most new client development. How many people have used or are using our REST Services today? Are there any Services you have found fundamentally missing for your needs? Three main areas of focus for new features have gone into the Bedrock release: Advanced Search, User Management & Access, Advanced type support. Our plan is increase the frequency of REST service releases (disengage from the Platform releases) to meet internal and external customer demands after Bedrock. We will continue to align major releases with the platform, however more agile incremental services will be made available. Some of the areas we are looking at include Workflow Services, RPS, Content Transformation Services and collaboration. The Vision for REST is to not only provide what is fundamentally provided by DFS today, but to exceed DFS capabilities. While EMC is committed to REST development; DFC,DFS,CMIS is not going away
- I’m certain most of you are aware of the major upheaval in the browser world. Java: JRE Security Fixes force continuous pressure on EMC Certification and Customer IT teams Browsers: NPAPI removed from top Web Browsers eliminates application to UCF bridge HTML5: Modern HTML language prohibits advanced interaction with user file system over NPAPI being removed and we are all too painfully aware of what this means for clients leveraging advanced content transfer capabilities.
- The fundamental problem is security, giving a Web Browser capability to read and write files on the client machine. The solution today is either to force the user to save files/select them for checkin or involve browser extensions/helper objects and native client that must be installed/trusted on the client machine. Our solution: UCF stays and depending on the client will be UCF Java or .NET, but the clients will be modified to leverage the new Java Applet Free download manager…which means …no NPAPI browser requirements. For UCF java there is still the need for client side java, however it is an embedded JRE. The UCF itself did not have issues with the version of Java installed on the users machine, it was actually the applet technology to download the UCF that had all the issues reportedly.
- Best practices to direct maintenance releases Sustain Certifications and Security Backwards compatibility & fast low risk upgrades Webtop to D2, xCP functional gaps (unexposed Platform features like federated search) Support for Oauth and external Trust providers Windows Docker & Complete Stack Dockerization Auto-provisioning and scaling Health check console (syslog collection for support, etc). Stability: Service Packs REST & CMIS 1.1 (full) China and Russia (encryption rules) Tighter Cloud Services feature support Native Support for Cloud laas (AWS, Azure, CloudFoundry, Compute) Industry/Government Standards Compliance (508, ITAR, FEDRAMP, Common Criteria, FSTEC, IL3, ISO, PCI, PrivacyShield, SEC) XML Apps (JSON)