What s New In DFC David Folk Product Manager 1 Agenda Quick Review Release 5.3 Q&A Post 5.3 plans 2 Quick Review 3 1
Everyone should know: DFC Documentum Foundation Classes Primary client API for platform BOF Business Object Framework Business logic that runs as part of DFC 4 DFC provides the client APIs for accessing the Documentum Repository Your s Your TBOs Business Objects Operations Content Pkgs Workflow Validation Virtual Document Core DFC layer Object-oriented access to server API layer Intrinsic Business Objects High-level Middle-level Low-level APIs DocumentumRepository 5 BOF Benefits Faster development Abstracts business logic from presentation layer code Encourages reuse Portable across applications 6 2
Background: DFC 5.1/BOF 1.0 Business Object Framework (BOF) Introduced Framework Version 1.0 Documentum 5.x applications Use BOF (out of the box) Can be customized through BOF BOF Object Types Introduced Type based Objects (TBO) Provide functionality that is specific to a repository object type (i.e. my_sop_document, ) and thus docbase specific Based Objects (SBO) Provide functionality that is object and docbase neutral (can be employed by any application AutoNumber ) 7 DFC 5.3 Summary 8 Goals for DFC 5.3 Deliver next generation content transfer (UCF) Expand BOF infrastructure Management Deployment Provide great Web infrastructure Support:.NET Webtop Collaboration Records Management ECI (askonce) Continue to remove dependencies on native libraries Continue performance improvements Maintain quality Maintain compatibility Note: DFC 5.3 requires a 1.4.x JVM 9 3
Unified Content Facilities (UCF) Overview A next generation facility for content transfer between client and application server Used by all Documentum 5.3 and later Web Clients (Webtop, Web Publisher, DAM Client, ) Desktop Application Integrations (Authoring integrations, etc.) Web s Fully-documented and supported part of the Developer SDK Likely future Designed for Documentum requirement Requires Java 1.4.2 Need not match the browser Java Plug-In setting Two downloads available one with JVM, one without JVM 10 UCF Functional Diagram (Web-environment) Browser UCF applet UCF Client Process Client File System HTTP Server Application Server Webtop, WDK UCF Server Component DFC Dctm Content Server Client Environment Application Server Content Server 11 UCF Architectural View Webtop, Digital Asset Manager, Documentum Administrator Web Publisher, Portal Content Manager Portlets Custom Applications UCF API UCF Runtime Platform s Content Registry OS Info MIME-type Recognizer Tracking/Logging Extension Points Custom Attachment Handlers Custom Request Handlers UCF Kernel Communication Tracing/Logging Component Registry Configuration Content Pkging Notification WDK-Based Apps Web s Custom Apps 12 4
UCF Platform s File System Brokers file reading/writing/removal to operating system Will offer accelerated file store reading/writing options (DAM) MIME-type Recognizer Provides analysis of contenttypes for both UCF requests and responses Does type and format analysis (compression options, etc.) Platform s Content Registry OS Info MIME-type Recognizer File System Content Registry Persists content meta-data on client when content is resident there Fully supports XML and VDM OS Info Provides OS identification information OS Info helps the modal operation of UCF based on unique client environments 13 UCF Kernel UCF Kernel s Communication Tracing/Logging Component Registry Configuration Content Pkging Notification Configuration Used to store UCF-specific and UCF-enabled client configuration settings Uses client-side XML file for storage Configuration settings will be associated with domain name settings of the application Uses domain com.documentum.ucf for global UCF settings Will preserve unique OS user settings (unique files) Documentum installer will be UCF-aware to preserve settings and preferences Communication Includes both Sender and Receiver interfaces Includes a request processor and an attachment processor Request processor dispatches to Request Handlers per request message Unique request handlers may be developed and plugged in Unique attachment (format) handlers can be developed and plugged in Includes a UCF Communication Manager to manage multiple threads of communications from various applications 14 UCF Kernel s Component Registry Used for registering optional UCF components such as handlers, processors, etc. Will have required, optional and skip registration scopes Tracing/Logging Very similar to existing DFC logging capabilities Will rely on Java 1.4 logging capabilities (java.util.logging.* APIs) Will only log client-side events, will not log any server-side information except communcation-related UCF Kernel Communication Tracing/Logging Component Registry Configuration Content Pkging Notification Notification Notifies on error conditions and progress feedback For rich-client notification will be delivered to end-user For wdk-client notification will be delivered to application Content Packaging Creates content packages for transfer between client and server 15 5
BOF 2.0 Next generation Business Object Framework Will ship with DFC 5.3 Focus: Administration Dynamic Deployment Requirement: Keep with BOF 1.0 programming model i.e. code fully compatible; slightly stricter packaging requirements (covered later in presentation) 16 BOF 2.0 Administration (summary) Business Objects Registered in repository No longer Properties file (DBOR) on client machine TBOs in repository corresponding to type SBOs in master repository Repository module stores: Version information Description Type (SBO, TBO) Dependencies Javadoc Documentum Repository 17 Modules in Documentum Application Builder (DAB) Module = one stop shop in repository for BOF code, description, dependencies, Javadoc, etc. 18 6
Module: Implementation Module: Name, Type, Version Interface & Implementation JARs 19 Module: General Name, Version Interfaces Min DFC and JVM Versions (for reference) Path to Javadoc 20 Module: Description Provider, Contact, Description Supporting documents: README, license, etc. 23 7
Organization in Repository mysbo mysbo.jar mysboimpl.jar javadoc.zip runtime environment.xml JDOM JDOM.JAR External Interfaces mytbo.jar Miscellaneous license.txt Named for service or type name. Contains JARs for Bus. Object. 3rd party JARs can be stored in repository. Interfaces to any used business object. Place to put readme.txt, license, etc. 24 BOF 2.0 Dynamic Deployment (summary) BOF objects dynamically deploy to client Requires separation of interface (shared classes) and implementation jars Supports 3 rd -party Java libraries Documentum Repository Dynamic Deployment 25 Web s Support Documentum Platform Release 5.3 DFC includes web services framework Leverages BOF SBOs Authoring Deployment Web SBO Programming Model Development Tools Web Runtime (Axis 1.2) Unified Content Framework (UCF).NET friendly WSDL 26 8
Web s Roadmap Documentum Platform Release post 5.3 Standard Web Based Objects included with platform Great opportunity to provide feedback Library Operations WSBOs Administration WSBOs Query WSBO Search WSBO Many More Web SBO Programming Model Development Web Content Tools Web s Runtime (Axis Framework 1.2) Transfer (UCF).NET friendly WSDL 28 Web s Roadmap Examples: Plugging into SOA Timeframes vary Some underway already (and some don t actually require WS framework) WSRP (Portlets) Authoring Integrations BPS EAI.NET Applications Library Operations WSBOs Administration Query Search WSBOs Web s WSBO Library WSBO Many More Web SBO Programming Model Development Web Content Tools Web s Runtime (Axis Framework 1.2) Transfer (UCF).NET friendly WSDL 29 Web Assumptions RPC-Style Interactions Achieved through wrapped document literal WSDL syntax Point-to-point Interactions Not involving complicated routing Intra-Corporate Bias Client-side Web Framework Neutrality At minimum, Java and.net Explicit non-goal: Dynamic provisioning of web services The publication of a BOF service as a web service requires deliberate design-time intervention and explicit manual publication. 30 9
Validation in Java instead of Docbasic Summary: Ability to compile existing Docbasic expressions into java classes and use them to evaluate validation expressions Improve performance Several times better than previously In particular, when thousands of objects need to be validated as in an XML application Reduce DFC s reliance on native code Necessary for eliminating global (shared) DFC installation on application server 31 Continued Support for.net (page 1 of 2) Seeking a native developer experience Building robust business logic support DFC Primary Interop Assembly (PIA) Shipped with Documentum Foundation Classes (DFC) 5.2.5 Documentum ADO.NET s (DAS) Built on DFC PIA Planned for 5.3 release Currently available in early access Web s.net friendly WSDL 32 Continued Support for.net (page 2 of 2) Leverage rich tools and standard frameworks Presentation: ASP.NET, Windows Forms Data: ADO.NET, System.Xml Logic: DFC and Business Objects Framework Integrate with Visual Studio.NET Provide guidance Examples PIA Documentation DAS Documentation ASP.NET examples at Developer Site Best Practices Invoking SBOs described at Developer Site 33 10
Storage Aware Out-of-box support for policy management Good example of configuration model rather than customization model. Less coding for developers than previous solutions required No special APIs, but requires licensing 34 Enterprise Content Integration (ECI) Overview Multi-repository search Multi-repository search + external sources (requires ECIS server) Query builder (new API) New Generation Smart Query + WDK 35 Enterprise Content Integration (ECI) Architecture Webtop Portal ECI Client 5.3 ECI Portal 5.3 WDK 5.3 DFC 5.3 Access to external content ECI s 5.3 WWW Docbases Lotus Domino Lexis Nexis Google 36 11
Enhanced Diagnostics Logs: Errors related to mismanaged sessions Non-released sessions (session leaks) Attempts to use objects after session release dfc.properties dfc.resources.diagnostics.enabled=true/false Default is False (to minimize overhead) Requires restart 37 Miscellaneous 5.3 features Login tickets No longer bound to one repository Multi use support Security model enhancements Access control features Enables MACL as a solution Changed way ACL evaluated Restricted access, inherited access (let s you define a ceiling in security) Dynamic groups (e.g. based on where user logs in from) DQL execution Faster full text query Supports content-less objects Single-box search Customization model for indexes (public post 5.3) New copy behavior for dm_relation Supports deep copy of related object Rich Text SBO VDM enhancements 38 Questions and Answers 39 12
Post 5.3 Plans 40 DFC Projects in the Works Additional Distributed Support Accelerated Content s Java DMCL Effort began before 5.3 Completed post-5.3 (migration, deployment, performance, etc.) Aspect Behaviors (infrastructure part of DFC 5.3) Attributes Native Windows UCF Client Web s Library Buildout Continued performance improvements XML Validation Possible Data Dictionary enhancements Dynamic types Performance Simplify APIs More qualifiers than only type & lifecycle 41 42 13