11

Administration and DeploymentWhat’s New for 5.3And TutorialJenny Dormoy, Director Customer Deployability

Developer Conference 2004San Ramon, CA

October 2004

22

AGENDA

IntroductionsDeployability and Customer Deployability5.3 Installation ArchitectureSilent CapabilitiesSilent Installation Lab/BreakTroubleshootingHA and 5.3 Deployability InitiativesTime Saving Tips and TricksBeyond 5.3HA Lab

33

What is deployability and why is it important

Deployability is the ability for software to be deployed quickly and predictably

– into many different environments– at low cost– meeting customer requirements.– Starts with the first impression INSTALLATION– Needs to be considered in architecture

44

• Collect and Analyze Results• Identify High Priority/Payback items• Drive corrective actions

Customer Deployability CharterEnhance Customer Success and Accelerate Customer Deployments by driving “Pre

and Post-release customer programs”, “Championing Deployability” in product architecture and design, developing “Tools and Systems” which speed deployment of

Documentum Products by our Global customers.

• Unified Installer Platform• Installer Standards• Deployment Utilities• Unified Suite Installers

• Alpha• Early Access• Beta / Focused Beta• Early Deployment• Rapid Success

Customer Programs

Tools and Systems

Deployability

55

5.3 Installation ArchitectureTool – Macrovision’s InstallshieldMulti-Platform (ISX)Projects - stored in XMLJava-based GUI installer technology

– Common UI for Windows and Unix– customizable using java beans– Rich class library available (ICL)

Supports multiple platforms

66

5.3 Installation Architectural

Component ModelAll installable units are deployed as “subinstallers” Units encapsulate all information they need for installation success Units can be installed by themselves or in SuitesSuites of any combination of existing units as “subinstallers” can be created in just minutes.

77

5.3 Installation Architectural

Subinstallers contain information on: version controlexternal dependency validationpanel suppression UI logicdata validationall install, upgrade, reinstall, and uninstall logic.

88

5.3 Installer Architecture - Component Library

Documentum’s collection of abstract classes, java beans and services that extend the functionality of ISMP

– 150+ Java beans and classes

Any functionality required by two or more individual installers is ‘shared’

– dmcl.ini, dbor, dctm.jar, and properties file handling

– XML transform– OS services, security, and other

native functionality

Designed for re-use by Documentum installer developers

99

Configurable Installers

Wdk-based configurable installers

– WDK, Webtop, Web Publisher, DAM, DA, DCM, RM and more to come

BOF Services installers– Workflow, Subscription,

Ci, Collaboration, Xforms

Based on a common underlying framework Configurable via XSL

1010

5.3 Architectural HighlightsApplication Server Automation Library

Extensive library for J2EE application servers for– Querying– Configuring– Deploying applications– undeploying applications

Uses abstraction layer to simplify use from various installer projects.Includes support for several portal servers too

1111

5.3 Installation Architecture Global Context

Memory-based system of gathering inputs during install

– Inter/intra product data communication mechanism

Allows for sharing of information across products in suitesAids in panel suppression and pre-population of panelsCan be ‘flushed’ to a persistent storage 3 types of variables

– Temp– Secured– Persistent

1212

5.3 Installation Architecture Panel Suppression FrameworkInstaller rules:

Never ask for the same bit of information twiceUse the global context and/or a properties file to gather infoPrompt only if a value is not found or fails validationImplemented with abstract methods and interfacesHide underlying complexity from the end user

1313

5.3 Installation ArchitecturalPanel Suppression Framework

1414

5.3 Installation ArchitectureProperties Driven Installs

Allows for pre-population of infoGives us the ability to install with minimal user inputNow we can record an install and ‘replay’ multiple times

– Automated nightly install/test process made possible

Much more flexible than in the old installers

– Machines don’t need to be ‘cookie-cutter’

1515

Record and Playback

Can Record “answers” from a GUI install<setup_file_name> -record <path to .ini file>For example: dfcWinSuiteSetup.exe –record C:\myFile.ini

Use .ini file to Playback install for a subsequent install<setup_file_name> -config <path to .ini file>For example:dfcWinSuiteSetup.exe –config C:\myFile.ini

To make the install silent add the –silent flagFor example:dfcWinSuiteSetup.exe –config C:\myFile.ini –silent

1616

Partially Suppressed and Scripted Installs

Note the Key/Value pairs in the .ini filesDelete any desired values from the .ini file Use .ini file to Playback install for a subsequent install

<setup_file_name> -config <path to .ini file>For example:dfcWinSuiteSetup.exe –config C:\myFile.ini

Note that you are prompted for the deleted valueBlowfish encryption and Base64 encoding of secure parameters available in 5.3

1717

5.3 Installation “Compliance Checklist”

Installers Must Meet Standards:Easy to installSelf-documenting panelsConsistent look, feel and functionality

– Both cross product and cross platform

Leverages the best of what the ICL has to offerUninstalls cleanlyMore than just an installer built with ISMP!

1818

Silent Installation Demo and Lab

1919

Questions??

2020

“Post Break” Agenda

Troubleshooting InstallationsHA and Other 5.3 Deployability ImprovementsTime Saving Deployment Tips and TricksBeyond 5.3HA Lab

2121

Troubleshooting Tips and Tricks

setupError.log– Usually located where installer is launched– Contains failure information, system information– May contain pointers to other log files

2222

Troubleshooting Tips and Tricks

Run Installer from Java Directly– java -verbose -Dis.debug=4 -cp

dfcWinSuiteSetup.jar:dfcWinSetup.jar:jdkwin131_04setup.jar:bofworkflowSetup.jar:bofsubscriptionSetup.jar:bofciSetup.jar run >> c:\traceOut.txt

– dfcWinSetup.bin -is:javaconsole

2323

Troubleshooting Tips and Tricks

Useful Flags– is:log “new logfile “– is:tempdir “new temp directory”

2424

Troubleshooting – Common Errors

NVIDIA display driver $DISPLAY environment variable Exceed and CDE

– Connect directly to machine you wish to install on

Java out of memory error - find and destroy log.txtJVM not found Permissions on Unix File System

On Application Servers:Temp Space > 512 MBMemory > 512 MB may be needed

2525

HA concepts

High Availability = redundancy – > uptime, load balancing, scalability (5.2.5 SP1,

BEA,WAS)– Failover (in 5.3)

Load Balancing - serves to evenly distribute the request load

Failover - when an application becomes unavailable, a copy continues transparently

systems that achieve HA through load balancing and failover typically achieve linear performance gains that can adequately scale over time

2626

HA concepts

Replication - The process of copying a session state from one server instance to another

– In memory replication - highest performance – Persistent storage (database, file, JDBC) – highest reliability

Managed Server Configuration – group of servers that can be centrally administered

– will support session failover in 5.3

Cluster – group of servers that can be remotely administered, support session failover

– some app server vendors support cluster as a virtual single deployment (post 5.3)

2727

Overview – Application Servers

Several app servers support clustering – WebLogic, WebSphere, Tomcat (5.1 +), Sun Java System,

Oracle AS etc.

App server specific configuration/setup– Somewhat complicated but lots of documentation

Configuration – Load balancer – Internal plug-in vs. external – Cluster topology – Single vs. Multiple Machine – Session replication mechanism – In memory vs.

Database/File

2828

Overview – A Simple HA Setup

DCTM repository

2929

5.3 WDK/Webtop Infrastructure Support

Transparent Failover detection and recovery All user preferences are preserved and restoredSupport for failover is configurableEnable components to recover and continue

3030

WDK Session Failover Support - Transactions

Notion of transaction to maintain the data integrity - Similar to database transactionsKeeps track of request start (begin transaction), and request end (commit transaction)Session data is replicated only at the end of the transaction (i.e. at the end of the request)In case of a recovery, notify components to perform cleanup operations. WDK’s component’s responsibility to perform cleanup operationsTransaction are controlled by the framework, no customization.

3131

Background: DFC 5.1/BOF 1.0

Business Object Framework (BOF) IntroducedFramework 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 documentum repository specific

– Service Based Objects (SBO)Provide functionality that is object and docbase neutral (can be employed by any application – AutoNumber Service)

3232

BOF Benefits

Faster developmentAbstracts business logic from presentation layer codeEncourages reusePortable across applications

3333

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)

– Repository – registered modules take precedence over DBOR registered objects

3434

BOF 2.0 Administration (summary)

Business Objects Registered in Repository

– No longer in client machine Properties file (DBOR)

– TBOs in repository corresponding to type

– SBOs in master repository

Repository module stores:– Version information– Description– Type (SBO, TBO)– Dependencies– Javadoc

Documentum Repository

3535

BOF 2.0 Dynamic Deployment (summary)

BOF objects dynamically deploy to client

Requires Interfaces in separate JAR

Supports 3rd-party BOF objects

Documentum Repository

Dynamic DeploymentDynamic Deployment

3636

Packaging and Deployment

Creating a Documentum Business Object involves:1) Implement the business object.

a) Defining the interface and implementation. b) Implementing the IDfBusinessObject methods and its business

logic.

2) Package and deploy the business object. You can:a) Write the XML config file and execute the task as a command

prompt program ORb) Take advantage of the Documentum Application Builder (DAB) UI

3) Distribute the business object to multiple repositories through DAI.

3737

Take away points

BOF 2.0 objects dynamically deploy to client

Compatible with BOF 1.0– BOF 2.0 Requires Interfaces

in separate JAR– Your BOF1 objects can

coexist with BOF2

Supports 3rd-party BOF objects

Business objects registered in repository

– No longer in client machine Properties file (DBOR)

– TBOs in repository corresponding to type

– SBOs in “master” repository

Repository stores:– Version information– Description– Type (SBO, TBO)– Dependencies– Javadoc– Etc.

3838

Unified Content Facilities (UCF)

Updated Content Transfer Unified among Documentum ApplicationsNo client-side “Administrator” privileges requiredExpanded browser support on Unix, Windows and MAC

3939

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 Services– …

Fully-documented and supported part of the Developer SDKLikely future Designed for Documentum requirementRequires Java 1.4.2

– Need not match the browser Java Plug-In setting– Two downloads available – one with JVM, one without JVM

4040

DctmContentServer

HTTP Server

ApplicationServer

DFC

UCF Functional Diagram (Web-environment)

Browser

UCFClient Process

Client Environment Application Server Content Server

UCFServer

Component

WDK

Webtop, …

ClientFile System

UCF applet

4141

Timesaving Deployment Tips

Create “Crash and Burn” test boxesBackup or copy App Server installation directoriesUtilize scripted silent install for Content ServerRefer to Deployment Guides for WebLogic and WebSphere tipsBEA:

– Use configuration wizard– Create custom domain template

4242

Documentum 5 Installers

Q1 2005Q2 2003

Documentum 5.2

• More compliant D5 installers • BOF 2 Support• UCF • HA

• WDK Session fail-over• Limited cluster support

•BEA, IBM• Patch install• Silent Installation

•Server, DFC

2006 and beyond

Documentum 5.3 Documentum 5.Next

• Platform D5 compliant installers

• BOF 1 support• Configurable Installers introd• Common Infrastructure

• Java 1.31• Managed Servers

• BEA Weblogic• IBM Websphere• Server Failover

• MSI DTC

• Sandboxed dmcl/dfc• HA

• Full HA/cluster support for all app servers

• WDK based app – failover• Silent Installation continued

History and Roadmap

4343

Questions??

4444

HA Lab and Deployability Survey

4545