• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
2009-04-21 - Alfresco and Maven NXP case study
 

2009-04-21 - Alfresco and Maven NXP case study

on

  • 1,639 views

A introduction to Maven based development and lifecycle management for Alfresco architectures, based on the real life case study, NXP, ex Philips semi-conductors, which switched his complete ECM ...

A introduction to Maven based development and lifecycle management for Alfresco architectures, based on the real life case study, NXP, ex Philips semi-conductors, which switched his complete ECM landscape to an open stack.

Statistics

Views

Total Views
1,639
Views on SlideShare
1,619
Embed Views
20

Actions

Likes
1
Downloads
44
Comments
0

4 Embeds 20

http://www.slideshare.net 9
http://coderwall.com 8
http://www.lmodules.com 2
http://www.linkedin.com 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • 10/21/08 21/10/08
  • 10/21/08 So, I guess a bit of background is necessary as I’m pretty new here ;) My name’s Gabriele Columbro, and I’ve been working for more than 3 years for Sourcesense (IT-NL) on big Alfresco implementations, ranging from Big semiconductors companies like NXP (case study) to e-Government projects like GovUnited.
  • 10/21/08 500+ paying support customers in less than 3 years and growing. By way of comparison it took Filenet over 12 years to achieve the same number!
  • 10/21/08 Customizations range to easy model/taxonomy, to new custom workflows/actions/UI configurations, to new feature development. Typical enterprise version customization are integration with proprietary/legacy systems.
  • 10/21/08 Extension is your war container (alfresco.war) in which multiple AMPs gets deployed into. One AMP Typical side effect is: web.xml overwriting due to multiple customizations
  • 10/21/08 What’s application
  • 10/21/08 Basic content services and CIFS, as well as check/in/out, versioning and document metadata support Advanced content manag e ment so workflows, custom business processes support, more specific custom developments.Also publishing and later web content management seemed to be in the scope of Alfresco. More in general what it’s important to underline is that this is the typical ECM landscape of a modern large company which business processes are fully dependent on IT services and ECM technologies (and lately on concepts like knowledge workers social collaboration). This is the reason for such complex and highly integrated architectures, and often enterprises are not yet ready to embrace/implement such complex architecture due to lack of basic Application Lifecycle management.
  • 10/21/08 The situation was exactly growing as in the early Lotus notes times, W ith application redundancy in both different geographic locations or different departments for the same functionality. Reproducibility is definitely the first important feature of an highly complex architecture, as manual composition / integration of our application is simply not possible. Testing and release (meaning clear versioning and distribution) are also mandatory when such a high number of customizations have to coexist and avoid side effects o n other bits of functionality. A dependency is not only a technical concept. I t’s much more: in an organization a dependency between two projects is actually identifying a prioritization and serialization Separate Business processes, separate business cases and separate owners. lifecycle management? It’s the bridge between software engineering and business processes, as it clarify communication to the business by the means of a clearly defined application lifecycle and standard procedures around it.
  • 10/21/08 Define processes means writing huge but digestable procedural document, but that’s the price we have to pay to have a clear business understanding of concepts like ECM and ALM. So for ECM it means a common model and taxonomy, which can be arbitrarily complex. For this we defines clear ALM processes based on maven to have standardization of project creation, development, release and deployment.
  • 10/21/08 Conceptual scheme of the integration @NXP. You can see as Custom business applications so separate business processes are developed as separate AMPs, that in the end get deployed on top of an alfresco repository Extension project (the ECM Foundation). Multiple applications and libraries (AMPs) are deployed into the repository extension. As Having a commons AMP package is
  • 10/21/08 Being a standard raises the possibility of enter major open source communities (especially for integrators). AMPS are non standard j2ee artifact so we developed and contributed A custom Maven plug-in capable of building AMPs and have a WAR dewas contributed
  • 10/21/08 My expertise is that Archetyping or prototyping reduces drastically the Time to market of an application both in a complex enterprise environment, b ut also and especially to speed up the prototyping and reuse of achievements for system integrators
  • 10/21/08 I don’t ask you to go into the details of this , but the interesting bits are from an organization POV, despite all rectangles represents different project locations and so separete business projects, by the means of dependency, inheritance and agggregation Project inheritance, used can centralize key common enterprise project features Project aggregation, to be able to manage multiple project at once We are also 100% open source ready as the AMP produced b
  • 10/21/08 -Team or community is under control and have to motivate why being out of standard (push rather than QA based pull) Scales pretty fine Alfresco 3.0 – > 3.1 took no more than 3 days and they are pretty different products - J i be Rationale: H aving a strong lifecycle management foundation (alongside with your ECM processes) allows to cope with complexity and easily adds new features. This means longevity for your architecture either if your are an enterprise architect or an integrator solution engineer.
  • 10/21/08 As I said Maven allows you to abstract
  • 10/21/08 As I said Maven allows you to abstract
  • 10/21/08 As I said Maven allows you to abstract
  • 10/21/08
  • 10/21/08 As mentioned in previous slide, Alfresco retains the control over the software versions and can therefore commit to levels of service for support. Add to this, UK support are in close physical proximity to Software Engineering which enables effective exchange of knowledge. The SLA’s are annual agreements and their price calculation is based on the project size / system architecture for the business solution. 
  • 10/21/08 As I said Maven allows you to abstract

2009-04-21 - Alfresco and Maven NXP case study 2009-04-21 - Alfresco and Maven NXP case study Presentation Transcript

  • Enterprise Development with Alfresco and Maven Prepared by [email_address] Hilversum, 21 st April 2009
  • A bit of introduction
    • Gabriele Columbro
      • ECM Architect on Alfresco for 2+ years with Sourcesense IT&NL
      • 2 nd day in Alfresco as EMEA Field Consultant for Professional Services
    • Focus
      • ECM enterprise integration
      • Application Development best practices with Apache Maven
    • Clients
      • NXP, GovUnited, Banca Popolare di Milano
  • Why Alfresco?
    • Scales to Enterprise Wide Repository
      • Benchmarks up to 100 million objects
      • Multi-tenancy and REST front-ends
    • Reduces vendor lock-in
      • Best of breed open source components
      • Integrate in rather than impose your stack
    • Grows outstandingly in feature and support
      • First CIFS Java implementation
      • Sharepoint protocol support
      • Social collaboration platform
    • Biggest Open Source ECM player
      • 70,000 Community members
      • 30,000+ Active installations
      • 75 countries, 20 languages
    It’s open source… we can customize it!
  • Alfresco customizations
    • Custom Modelling
      • Custom content model
      • Custom space taxonomy
    • Custom User capabilities
      • Custom UI configurations
      • Custom workflows
    • New feature development
      • Custom webscripts
      • Custom JSF components
      • Custom SURF components (as of 3.x)
    • Integration with 3 rd party products
      • LDAP/CAS
      • Liferay
  • Customization packaging
    • 2 approaches with different purposes:
      • Alfresco extension (WAR): environment dependent builds with core configurations ( classpath:alfresco/extension/* )
      • Alfresco Module Package (AMP) AMPs should be (almost 100%) :
        • mutually non intrusive (software module)
        • relocable
        • reusable with repository version limitations
        • self-contained in ( classpath:alfresco/module/*/** )
  • NXP Case study
    • 40k employees global semiconductors enterprise disentangling from Philips
    • Alfresco as key building block of C3, enterprise content repository for the new redesigned architecture
    • Content and code reuse main driver of the C3
    • Several parties involved in the huge migration and (up to) 800 customization projects
  • NXP C3 Architecture
    • Alfresco as Basic Content Services (Versioning, Editing)
    • Alfresco as Advanced Content Management
  • Straighten your processes first
    • NXP Goals:
      • Get to the ultimate single sourcing enterprise content repository
      • Have multiple customizations being automatically packaged, tested, released and deployed to application servers
      • Manage a reproducible build aware of multiple environments (build and runtime configurations)
      • Dependency management versioning and centralized repository
    • Early phases (2007)
      • Multiple parties developing in isolation
      • Content silo high risk
      • Growing complexity (so TCO) of Alfresco production environment (multiple Alfresco WARs)
    • NO design and processes in place for ECM and Application Lifecycle Management (Application Lifecycle
  • Alfresco SDK Enterprise limitations
    • Project approach:
      • Define ECM processes (ECM Foundation)
      • Define ALM processes (Application Lifecycle Document)
      • Use enabling ALM technologies to support ECM complex architectural integration challenges
    • Alfresco SDK Limitations:
      • The Alfresco SDK + MMT approach would have required a large amount of scripting and manual configuration
      • No explicit support to scale up and cope with enterprise complexity
    • Apache Maven was chosen as reference technology for coping with complexity of modern ECM architectures
  • The Idea
  • What is Apache Maven?
    • Is the standard de facto in open source Java based application lifecycle management
    • Allows to use standard commands to manage all software lifecycle phases from creation to release
    • Support project inter-dependencies (and dependency on the officially released Alfresco) and project binary repository
    • Maven AMP Plugin
      • Packages AMPs
      • Allows an Extension WAR to depend on AMP (alternative to the MMT, done at build time)
    • Real enabler for the growingly complex NXP architecture
  • Maven Enterprise Added value
    • Maven Alfresco archetypes
      • Provide easy project templates to standardize AMPs and Extensions development
      • Have your project up and running in few standard commands
    • Dependency management
      • You can express your runtime requirements
      • Enable complex inter-dependent project to be developed in isolation but deployed in integration
    • Project inheritance and aggregation
      • Centralize control of libraries
      • Centralize environments
      • Centralize release/versioning/documentation
    • Nexus Enterprise Repository
      • Searchable repository of your code assets gears reuse
      • Proxying multiple partners deliverables makes teams distributable
  • Ideas come true
  • NXP Main Benefits
    • Lower TCO: ~10 AMPs deployed on 1 Foundation repository
    • Fast upgrade with Alfresco versions, rolling out 3.1 in May (SHARE build and SharePoint protocol)
    • Multiple parties to cooperate under one standard controlled application development
    • Ready to use GA open source AMPs (Alfresco and 3 rd party)
    • Enforced per project documentation
    • Commons reusable model/customizations library
    • Automated testing w/Selenium and continuous integration
    • Maven integrates with Eclipse, NXP reference IDE
  • The Alfresco community side
    • Maven Alfresco Archetypes http://repository.sourcesense.com/maven2-sites/maven-alfresco-archetypes
      • Alfresco community versions based project templates
      • Alfresco Dependencies deployed at http://repository.sourcesense.com/maven2
    • Maven AMP Plugin http://repository.sourcesense.com/maven2-sites/maven-amp-plugin
      • Used to package and depend on AMPs
    • First release in July 2007, hype in downloads in January 2009 (contributor of the month)
    • Archetype v.3.x already supporting SHARE and centralized dependency control
    • Enable your work to be 100% open source ready and contributable!!!
  • Demo
    • Run Alfresco in less than 5 minutes:
      • Open Maven Alfresco Extension Archetype website: http://repository.sourcesense.com/maven2-sites/maven-alfresco-extension-archetype/
      • Run the featured command:
        • mvn archetype:generate -DarchetypeCatalog=http://repository.sourcesense.com/maven2/archetype-catalog.xml
      • As described in the README-m2.txt , run : MAVEN_OPTS="-Xms256m -Xmx512m -XX:PermSize=128m mvn integration-test
      • Point your browser to: http://localhost:8080/alfresco/faces/jsp/dashboards/container.jsp
    • Advantages: standard, reproducible, environment aware, no manual download
  • The power of open source http://www.mindthegab.com
  • Q/A
    • Any question?
  • Conclusions
    • Maven can be used as glue to scale out enterprise processes by technologies integration
    • Integrators can benefit as well of easy prototyping
    • A fool with a tool is still a fool. Focus on your ECM/ALM processes first
    • Understand what development approach fits you better ( Maven requires expertise but it’s open source )
    • Get open source under control a with open source technologies ;)
  • The end!
    • References:
      • Gabriele Columbro: http://www.mindthegab.com
      • Sourcesense: http://www.sourcesense.com
      • Apache Maven: http://maven.apache.org
      • Maven Alfresco support: http://wiki.alfresco.com/wiki/Managing_Alfresco_Lifecyle_with_Maven
      • Nxp: http://www.nxp.com