instructed by: ece - university of waterlooltahvild/courses/ece... · our goal: `address the...

Instructed by: Prof. Ladan Tahvildari

Presented by:Hasan, Salman

Jiang, NingGroup 7, ECE 751 – T11, S’10

IntroductionProblems to be resolvedProposed solutionApproachDesign Decisions/Criteria Expected Results/ContributionReferences

7/6/2010A Mobile-Based Enterprise Content Management System 2

Our goal:

address the usability issues associated with enterprise content management systems access via mobile devices.

deliver scalable architecture and a prototype of Enterprise Document Management system based on OpenText Livelink© and BlackBerry©.

*If time permits, the prototype will also support Android‐based phone and Microsoft SharePoint)


What is ECM

The strategies, methods and tools used to capture, manage, store, preserve, and deliver content and documents related to organizational processes.

‐ Source: AIIM (Association for Information and Image Management) 2008

7/6/2010A Mobile‐Based Enterprise Content Management System 4

Why mobile?

As the enterprise moves away from a fixed and location‐centric work setting to a dispersed mobile world, the ability to interconnect people, processes and core content becomes a necessity.

Livelink: an ECM system from OpenTextJSP: (Java Server Page) A web based application development languageJ2ME: a “Micro Edition” of Java for mobile and embedded devicesAPI: (Application Program Interface) A set of interfaces used to access application servicesWebservice: Service offered via the standard HyperText protocol

ECM products are not optimized for mobile access

◦ Browser‐based client lacks of functionality

Mobile clients are ECM product‐specific

Maintainability of various ECM mobile clients in one organization becomes

problematic

Open source‐based tools exist (MindTouch)

◦ …but they are not geared toward content creation*

◦ …and companies may already use commercial ECMs

This is a project that embodies many of the theoretical material studied in class


Build a middleware layer to standardize ECM access

A loosely coupled system involving 3 layers

◦ Possible through the use of LiveLink APIs, Java and .NET services

Multiple tiers developed as follows:

◦ Presentation: J2ME (initially) BlackBerry applications

◦ Business Logic: .NET‐based web services

◦ Backend: LiveLink base system

A mobile client specially designed for each type of handheld device

A standardized mobile client for multiple ECM systems.


Development based on several Key Phases:◦ Requirements – Collection and Analysis

Select a suitable topic, problem and scope to addressDefine possible tools and options

◦ Design – Analyze options and design architectureMap system design and architectureDesign webserver and client software systems

◦ ImplementationImplement ECM backend system , handheld client and middleware

◦ VerificationRigorous product testing and comparative analysis


JSP

◦ Better suited to dynamic web applications

◦ Greater level of compatibility

◦ Runs on the server

J2ME

◦ Geared towards embedded/mobile systems

◦ More specialized (especially in terms of BlackBerry development)

◦ Has the ability to function off‐line*


*Source: Overview Advantages of J2me@ http://www.articlesbase.com/software-articles/overview-advantages-of-j2me-286725.html by Kamlesh Patel

◦ Both multi‐tiered, similar computing technologies

◦ Both support “standards”

◦ Both offer different tools & ways to achieve the same goal.

◦ A lot of parallelism can be seen.

◦ Very difficult to compare and qualify the comparison because each has its own

advantages & disadvantages.

◦ Fully supported by the vendors (i.e. OpenText)


API

◦ Offers interfaces for calling functions

◦ May be simpler in design but more closed

Available functionality dependent on software developer

Webservices

◦ A form of API built using HTTP/SMTP etc

◦ Based on remote procedural calls

◦ Can be implemented by developer


7/6/2010 12

Source: Magic Quadrant for Enterprise Content Management by Gartner • Top 5 player in ECM market• Open platform - support Java and .Net• We have the knowledge!

A Mobile-Based Enterprise Content Management System

End User: JSP vs. Java Micro Edition

◦ JSP is more compatible while J2ME is more specialized

◦ J2ME provides more benefits and customizability

Middle Tier: Java vs. .NET Webservices

◦ Both are technically capable to meet the requirements

◦ Developing webservices based on .NET technology is easier

Backend: LiveLink ECM system

◦ Provides all of the desired functionality in a generic package


Results

◦ To build a fully functional and capable mobile ECM access solution

Contribution

◦ Provide a proof of concept utilizing a wide variety of tools

◦ Gain experience in utilizing Component Based Software Engineering processes

Evaluation

◦ Compare to existing solutions among several dimensions: usability, accessibility


[1] Ladan Thavildari , Component‐Based Software Systems S’10, 2010, Courseware

[2] OpenText Corporation , Livelink ECM ‐ Enterprise Server Installation Guide, 2008

[3] OpenText Corporation, Livelink ECM – Enterprise server 9.7.1 Administration Guide, 2008

[4] OpenText Corporation, Livelink ECM – Enterprise Web Services 9.7.1 Programmer’s Guide, 2009

[5] Qusay H. Mahmoud, Programming the BlackBerry With J2ME, 2005

[6] Oracle Corporation, Tutorial ‐ JavaServer Pages Technoglogy ver. 2.0 , 2008

[7] Oracle Corporation, Tutorial ‐ Build Stateless Session Bean ,1999


7/6/2010 16A Mobile-Based Enterprise Content Management System

Questions?

instructed by: ece - university of waterlooltahvild/courses/ece... · our goal: `address the...

Documents