The document provides an overview of the WDK (Web Development Kit) and compares versions 4.2 and 5.0. It discusses using WDK 4.2 to re-engineer a desktop client application for the web, highlighting challenges faced and lessons learned. It also previews new features and architectural changes in the upcoming WDK 5.0 release.

2. Ralf Klappert
WDK Do’s and Don'ts
ELCA Informatique SA
Senior Manager

3. Agenda
• WDK 4.2 – an overview
• A real life example
• WDK 5.0 – the road ahead
• Conclusions
• Q & A

4. Presentation Goals
• Allow you to understand the WDK
• Provide you with a real life project
experience
• Highlight the advantages / challenges
of WDK 4.2
• Show you a sneak preview of WDK5

5. WDK 4.2 Conceptual View
J2EE
Configurable Framework
Documentum Java API
Presentation Components
D
F
C
W
D
K
WDK = Web Development Kit

6. WDK 4.2 Architecture
Web-ServerTier
JSP
DFC interface
WDK
Web-
server
Layer
JSP
Java
code
DFC layer
DMCL layer
Servlet
Java code
ThinClient
Tier
E-content
Server
Tier
E-Content
Server Database
JavaScript
JavaScript
WDK Browser
Layer
XML
config
XML
config
Generated
HTML
+
DHTML
DMCL interface
Business Logic
J2EE
Configurable Framework
W
D
K
D
F
C

7. WDK 4.2 Features
• WDK is J2EE compliant
Servlets, JSP
• Provides ready-to-use components
• Extensible through WDK classes
• Rapid development cycles
• Multiple levels of customisation
XML – JSP – Java
Business Logic
J2EE
Configurable Framework
W
D
K
D
F
C

8. Real life example
Re-engineering a DTC application
• Goals
Optimise for WAN operation
Reduce deployment cost
• Opportunities
Align with Documentum web strategy
Future integration with web-based business
applications

9. From DTC …

10. Optimise for WAN operation
Desktop Client
• Network intense
• Synchronous operation
• Client-side logic
LAN/WAN Performance comparison
40
200
280
25
130
80
0
50
100
150
200
250
300
Login Scan & Import Complete Indexing
Timeinseconds
DTC LAN DTC WAN

11. Functional Scope
DTC WDK
Custom attributes;
validation rules
Rewrite from scratch
Lifecycles No change required
Smartlists Not Supported
Customised search Limited supported
Configurable result display Not supported
Annotations Not supported
Scanning integration Rewrite from scratch

12. Project Challenges
• User expectations
DTC Look & feel
DTC functionality
• Time to production
Staffing & skillset
• WDK 4.2
Maturity
Functional coverage

13. Design Decisions
• Use WDKspace
• Limit Browser support to IE
Use advanced DHTML
• Limit client – server communication
Improve response time
• Create re-usable component library
GUI components

14. Project Configuration
• MS IE 5.5
• WDKspace 4.2
• WDK 4.2
• DFC 4.2
• Project
customisations
• eContent Server 4.1
Wep App Server
Business Logic
J2EE
Configurable Framework
W
D
K
D
F
C
• Windows NT
• Oracle 8
• Sun Solaris
• Tomcat 3.2
• Sun Solaris

15. WDK 4.2 Customisations
Web-ServerTier
JSP
DFC interface
WDK
Web-
server
Layer
JSP
Java
code
DFC layer
DMCL layer
Servlet
Java code
ThinClient
Tier
E-content
Server
Tier
E-Content
Server Database
JavaScript
JavaScript
WDK Browser
Layer
XML
config
XML
config
Generated
HTML
+
DHTML
DMCL interface

16. … To WDK

17. Functional Scope Revisited
DTC WDK
Custom attributes;
validation rules
Implemented: Customised
code using JavaScipt / DHTML
Lifecycles No change required
Smartlists Implemented: Execution &
result display only
Customised search WDK configuration ; some
limitations remain
Configurable result display Implemented: customised
code
Annotations Not implemented
Scanning integration Implemented

18. Optimise for WAN operation
WDK client
• Limit network traffic
• Operations executed asynchronously
• Server-side logic
LAN/WAN Performance comparison
40
200
280
35
150
190
130
25
80
0
50
100
150
200
250
300
Login Scan & Import Complete Indexing
Timeinseconds
DTC LAN DTC WAN WDK WAN

19. Lessons Learned (I)
• Project management
Plan for technology related showstoppers
Include users to soften paradigm shift
• Staffing
WDK training by itself is not sufficient
Required skillset
– Administrator: Documentum + J2EE app server
– Web developer: Experience with JSP, DHTML,
Servlet, HTML and XML
– Enterprise Java Developer: JSP, Servlet, EJB and
other J2EE Services

20. Lessons Learned (II)
• WDK 4.2 Technology Limitations
Modification of WDK components
needed to cover project requirements
JavaScript handles user events
– Difficult to test
JSP is not extensible
– Redundant JSP code

21. Lessons Learned (III)
• Infrastructure
Anticipate side-effects due to WDK
required infrastructure updates
WDK product cycle may require updates
during the project
• Deployment
Configuration management to
accommodate multiple WDK-based
applications

22. WDK 5.0 Architecture
Web-ServerTier
Thin
Client
Tier
JavaScript
WDK Browser
Layer
Generated
HTML
Controller
XML contract
WDK Component
JSP
Java
Server-side
event
Taglib file
Java tag
implementation
WDK
services:
- application
server (EJB),
-data access
(JDBC),
- session
pooling,
etc.
E-content
Server
Tier
E-Content
Server DBMS
DFC

23. Conclusion: Do’s
• Consider migrating from DTC to
WDK if performance / deployment is
an issue
• Plan to use WDK5
• Staff your project with DCTM / Web /
J2EE developers
• Include key users to soften the
paradigm shift

24. Conclusion: Don’ts
• Stay clear of core WDK code
Avoid maintenance and update issues
• Avoid implementing business logic
on the client-side
• Do not underestimate the human and
technological impact of the paradigm
shift from Windows to Web
• Do not try to achieve 100%
Settle for 80/20

25. For further information
ralf.klappert@elca.ch
http://www.elca.ch
Thank you for your attention

26. WDK 4.2 vs 5.0
WDK 4.2
• Client-side
event
handling
(JavaScript)
• XML configuration of
properties and advanced
search only
• JSP use JavaBeans and
mainly scriptlet
WDK 5.0
• Server-side
event
handling
• XML contracts for
components, that are
extensible
• JSP rely on taglibs
Web-ServerTierThinClientTier
JavaScript
WDK
Browser
Layer
Gen
erate
d
HTM
L
Controller
XML contract
WDK
Component
JSP
(no
scriptle
t)
Java
Server
-side
event
Taglib
file
Java tag
impleme
ntation
WDK
services
:
-
applicati
on
server
(EJB),
-data
access
(JDBC),
- session
pooling,
etc.
E-contentServer
Tier
E-Content
Server
DBMS
DFC & API
Web-ServerTier
J
S
P
DFC interface
WDK
Web-
server
Layer
JSP
J
a
v
a
c
o
d
e
DFC layer
DMCL layer
S
e
r
v
l
e
t
Java code
ThinClientTierE-contentServerTier
E-Content Server
Database
JavaSc
ript
JavaSc
ript
WDK Browser
Layer
X
M
L
c
o
n
f
i
g
X
M
L
c
o
n
f
i
g
Generat
ed
HTML
+
DHTML
DMCL interface