How I Stopped Worrying and Learned to Love Open Source
summary
Progress replaces a legacy native broker/agent stack with a Tomcat-based application server built on Tomcat, Spring, Camel, CXF, and a custom management layer called TCMan. The team creates per-instance Tomcat deployments, externalized server.xml values into properties, and integrates Spring Security (digest/LDAP/AD, form/basic, SSO) so multiple web apps share auth. Upgrades and logging bridges cause surprising classloader and commons-logging conflicts, but the Tomcat-based server ships and runs in production across Linux/Windows/AIX/Solaris.
AI-written summary · about
chapters (20)
- 0:00Intro
- 1:38What is a Progress Application Server
- 2:49Who are we
- 3:24First Progress Version
- 3:43Timeline
- 4:31App Server Architecture
- 7:27Why Develop a New App Server
- 8:52Choosing a Platform
- 9:57Tomcat
- 11:11Concat
- 14:55Features
- 16:23Extensions
- 18:28Windows Services
- 19:49TCMan
- 29:02Development Server
- 30:38Tomcat Architecture
- 32:12Tomcat Instance Runtime
- 34:50Spring Security
- 42:35Challenges
- 43:01Compatibility
related talks
49mSecurity Vulnerabilities in OpenSource Java Libraries
51mWhy Companies Hesitate to Use Open Source — And How We Can Change That
32mMastering Enterprise Open Source for Cloud and Vendor Independence
27mHow to Build an Integration Platform using Open Source
36mIt´s Easy! Contributing to Open Source
37mManaging the API lifecycle with Open Source technologies
16mThe Crucial Role of Openness in Modern Software Development
42mOpen Source in the Age of Cloud and Microservices