• Save
Eniac – Lotus Consolidation   2009
Upcoming SlideShare
Loading in...5

Eniac – Lotus Consolidation 2009



Presentation about Lotus Notes and Domino email and collaboration consolidation.

Presentation about Lotus Notes and Domino email and collaboration consolidation.



Total Views
Views on SlideShare
Embed Views



6 Embeds 64

http://collaborationfactory.blogspot.com 40
http://planetlotus.org 14
http://www.collaboration4business.eu 7
http://collaborationfactory.blogspot.com.es 1
http://collaborationfactory.blogspot.nl 1
http://collaborationfactory.blogspot.co.uk 1



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.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

    Eniac – Lotus Consolidation   2009 Eniac – Lotus Consolidation 2009 Presentation Transcript

    • Consolidate messaging & groupware platform What does it mean and how to approach. Author: Edwin Kanis
    • Why consolidate messaging and groupware platform
      • Reducing the TCO by:
        • Building a less complex environment
        • Easier administration and systems management (bundle competences)
        • Sharing complementing services (IM, anti-spam, anti-virus etc)
        • Reduce server license costs
        • Standardize your environment
      • Gain more control, create flexibility and improve security
      • Creating high availability
      • Improving back-up and restore operations
      • Creating opportunities for future compliancy reasons
      • Creating opportunities for archiving and data offload reasons
    • Statement
      • “ Lotus Domino is a great and flexible platform, it is scalable for every organization and the technology can handle full consolidation”
    • Why Domino is a good messaging platform for consolidation
      • Why Advantage
      • Scalable and platform independent -> CPU and Memory
      • Support for 32 and 64bit platforms -> CPU and Memory
      • Domino clustering is proven to be excellent -> High availability, maintenance
      • Network compression / streaming replication -> Bandwidth savings
      • Storage compression / Single attachment -> Storage savings
      • Transactional logging -> IO, back-up, rebuilt
      • Multi language support -> Maintenance
      • Mixed versions and backward compatibility -> Maintenance
      • Multi client support (Notes, Browser, Pop etc) -> Maintenance
    • Steps to follow for consolidation
      • Define desired and future services
      • Define your requirements and describe company standards
      • Describe a logical and physical infrastructure architecture
      • Built the new technical environment
      • Transition from the current to new environment
      • Support services
    • 1) Define your desired and future services (examples)
      • Messaging and Calendaring services
        • Mobile, Web Access, Archiving?
        • Instant messaging?
      • Directory and security services
        • LDAP, SSO, SSL
      • Application service
        • Browser Notes apps?
        • Integration?
      • Development service
        • Apps dev and test?
      • Remote location service
    • 2) Define your requirements and describe company standards
      • Organizational ( ! )
      • Service level requirements
      • Company policies and standards (conventions etc)
      • Consolidation level: Local versus regional versus global
      • Technical
      • Working local replica’s (LBC) andor increase networking bandwidth
      • Level of Redundancy required
      • Server platform and operating systems
      • Storage and back-up requirements
      • Archiving andor data offload
      • User management (Global or delegated)
    • 3) Describe a logical and physical infrastructure architecture
      • Architect a logical environment
        • Domains, organizations
        • Security and access layers
        • Functional ‘clusters’
      • Architect a physical environment
        • # users #mailboxes per server
        • Locations and data centers
        • Server CPU and Memory
        • Storage amount and speed (IOPS)
        • Clustering and fail-over components
        • Anti-virus and spam
        • Networking (users, storage, back-up, cluster)
    • 4) Built the new technical environment
      • Building needs project management and communications
      • Stick to the design plans, use your architects
      • Test individual solutions and load test your total solution
      • Use your architect for reviews
    • 5) Transition from the current to new environment
      • Cleaning the current environment (garbage out – garbage in)
      • How to transition from current to new central defined standards?
      • How to move mailboxes from local to central (large amount of data)?
      • How to move from online to Local but Connected (LBC)?
      • How to move applications from local to central?
        • Do application integrate in other systems?
      • How to switch into new user management situation?
    • 6) Support services
      • Support organization and support roles
      • Monitoring the environment on several levels
      • Tools to make administration easier
      • Support and maintenance contracts 3 rd parties.
    • What else is important
      • Politics
      • Involve highest level management (due to politics).
      • Think of an chargeback model up-front (impact on local budgets)
      • Design
      • Make use of experienced architect(s) in design phase.
      • Bring Domino architect together with storage and networking architects.
      • Built-in review moments for architect(s)
      • Project
      • Create a solid project organization
      • Separate project tasks from maintenance tasks
    • Conclusions
      • The technology is there and is ready for consolidations
      • Do not over promise your services, start small and let your service grow.
      • Make your environment more simple.
      • Make use of experts, this saves time and makes later operations more simple.
      • Consolidation not only a technical project, this about your governance.
    • First steps into consolidation
      • We advice to plan the following first steps towards consolidation:
      • Workshop (0,5 - 1 day): one level deeper into consolidation and architecture scope.
      • Built a business case (when required) around costs savings, simplification, administrative control and data management.
      • Built a consolidation approach, create planning and budget estimations.
      • Eniac Essentials can help every customer through this process.
    • Reference projects
    • The End
      • Eniac BV Hogeweg 41 Postbus 2065 5300 CB Zaltbommel
      • TEL. +31 (0)418 57 07 00 FAX. +31 (0)418 57 07 66
      • www.eniac.nl
      • Eniac is part of Imtech ICT