Your SlideShare is downloading. ×
Midnight Cowboy
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Introducing the official SlideShare app

Stunning, full-screen experience for iPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Midnight Cowboy

2,745
views

Published on

Published in: Technology

0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
2,745
On Slideshare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
0
Comments
0
Likes
2
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide







  • Transcript

    • 1. How to avoid being the Midnight Cowboy! Pitfalls of Enterprise Java Application Deployment
    • 2. Anthony Shortland DTO Solutions Professional Services anthony@dtosolutions.com
    • 3. Don’t lose the plot ... • Many times things are broken because you’ve got the wrong files deployed • Do you know where every file deployed to your production environment comes from? • Do you know which packages should be deployed to which boxes? • Can you identify which package a particular file belongs to and how that package was built? • Can you check that the correct files are installed?
    • 4. ... maintain full-lifecycle traceability • Development build process starts with code committed to a version control system • Repositories of version controlled packages • Resource model tracks node/package assignments • Package formats are verifiable Development Operations
    • 5. Don’t try to mix oil and water ... • Changes to environment specific configuration are often hacked on the fly since doing it properly is too difficult • Can you make a traceable configuration change without re-releasing the application? • Does operations need to tell development about infrastructure changes that affect applications?
    • 6. ... establish formal separation of concerns • Maintain a separate repository of environment- specific infrastructure and application configuration data • Provide mechanisms for default configuration values be overridden externally to the application • Formally describe how the application is to be configured
    • 7. People, process and tools Development Operations Release Management Framework Resource Resource Model Resource Model Resource Model Environment repository repository Release repository Build Build Development environment Source base Build Deploy Build environment Deploy Source base Build QA environment Deploy Package repository Staging Deploy environment Source base Build Deploy Production environment