A marketing-free, engineering-led webinar: What was “state of the art” in configuration management has changed a lot in just a few years. It is about to change a lot more. Hear DevOps and IT automation practitioners and visionaries outline recent configuration management evolution and contrast that to the coming revolution which includes automatic drift detection, automatic config comparisons and auto-remediation of out-of-compliance configurations. Q&A afterwards.

1. Trifectix, Inc. Confidential
The Coming Earthquake in
WebSphere Application Server
Configuration Management
There were scripts.
And they were good. Mostly.

2. Trifectix, Inc. Confidential
Robin Fuller is a co-founder of Trifectix and Chief Software Architect of Orca,
the company’s application release and configuration automation solution.
Prior to Trifectix, Robin co-founded VaraLogix which was later acquired by
BMC Software as part of their application deployment and DevOps portfolio.
Earlier in his career, Robin was a Senior Software Engineer for IBM/
BuildForge.
Robin holds degrees in Mathematics and Engineering from Trinity College in
Dublin.
Kristy McDougal is a co-founder of Trifectix where she leads Product
Engineering for Orca, an application release and configuration automation
solution for DevOps teams. Prior to launching Orca, Kristy was a Senior Pre-
Sales Consultant within BMC Software’s world-wide DevOps specialist team.
Before BMC, Kristy held technical positions at VaraLogix, Virtual Bridges,
Global Foundries, and Advanced Micro Devices. Her experience includes
Unix systems administration, systems engineering, pre-sales consulting, and
post-sales services.
Kristy is ITIL Foundation certified and is an Electrical Engineering graduate of
the University of Texas at Austin.
Robin Fuller
Kristy McDougal
@orcaconfig
www.orcaconfig.com

3. Trifectix, Inc. Confidential
In the beginning…
There were scripts.
And they were good. Mostly.

4. Trifectix, Inc. Confidential
In the beginning…
There were scripts.
And they were good. Mostly.

5. Trifectix, Inc. Confidential
In the beginning…
There were scripts.
And they were good. Mostly.

6. Trifectix, Inc. Confidential
In the beginning…
There were scripts.
And they were good. Mostly.

7. Trifectix, Inc. Confidential
Are Scripts…?
Fragile?
Easily broken
Bulls in a china closet?
Charging ahead and

8. Trifectix, Inc. Confidential
Are Scripts…?
Fragile?
Easily broken
Bulls in a china closet?
Charging ahead and
changing everything in
their path
Yes!
o Agile
o Lean

9. Trifectix, Inc. Confidential
Are Scripts…?
Fragile?
Easily broken
Bulls in a china closet?
Charging ahead and
changing everything in
their path
Yes!
o Agile
o Lean

10. Trifectix, Inc. Confidential
Are Scripts…?
Fragile?
Easily broken
Bulls in a China shop?
Charging ahead and
changing everything in
their path
Yes!
o Agile
o Lean

11. Trifectix, Inc. Confidential
Are Scripts…?
Fragile?
Easily broken
Bulls in a China shop?
Charging ahead and
changing everything in
their path
Yes!
o Agile
o Lean

12. Trifectix, Inc. Confidential
Are Scripts…?
Fragile?
Easily broken
Bulls in a China shop?
Charging ahead and
changing everything in
their path
Yes!
o Agile

13. Trifectix, Inc. Confidential
Deplyoing a
typo
• Break-fix or “Break-Worse”
• Performance problems
• Outages

14. Trifectix, Inc. Confidential
• Break-fix or “Break-Worse”
• Performance problems
• Outages
Deplyoing a
typo

15. Trifectix, Inc. Confidential
• Break-fix or “Break-Worse”
• Performance problems
• Outages
Deplyoing a
typo

16. Trifectix, Inc. Confidential
• Break-fix or “Break-Worse”
• Performance problems
• Outages
Deplyoing a
typo

17. Trifectix, Inc. Confidential
• Break-fix or “Break-Worse”
• Performance problems
• Outages
Deplyoing a
typo

18. Trifectix, Inc. Confidential
Deploying a
tyop
• Break-fix or “Break-Worse”
• Performance problems
• Outages

19. Trifectix, Inc. Confidential
Deploying a
tyop
• Break-fix or “Break-Worse”?
• Performance problems?
• Outages?

20. Trifectix, Inc. Confidential
Deploying a
tyop
• Break-fix or “Break-Worse”?
• Performance problems?
• Outages?

21. Trifectix, Inc. Confidential
Scripting is Not Free

22. Trifectix, Inc. Confidential
Scripting is Not Risk-Free Either

23. Trifectix, Inc. Confidential
Summary:
Scripting was the best
available option
OF ITS DAY

24. Trifectix, Inc. Confidential
Summary:
Scripting was the best
available option
of the 20th Century

25. Trifectix, Inc. Confidential
Summary:
Scripting was the best
available option
of the 20th Century
(assuming you were lucky enough to have scripted it correctly)

26. Trifectix, Inc. Confidential
Today:
The Semi-Automated Era!
Or is it the Semi-Manual Era?

27. Trifectix, Inc. Confidential
Today:
The Semi-Automated Era!
Or is it the Semi-Manual Era?

28. Trifectix, Inc. Confidential
Today: To deploy a change
1. Search for modules from the open source community
pages that appear to meet their needs
2. Select the best fitting module.
3. Check for any module updates.
4. Investigate support options if the module does not work
perfectly.
5. Check environment dependencies for the module to work
correctly.
6. Inspect each line of the scripting module to ensure it is
safe.
7. Edit the module if it will not work off the shelf. (This might
require knowledge of RUBY).
8. Script the solution.
9. Test it.
10. Deploy it.
11. Document the process and the rationale behind it (for
future users and auditors).

29. Trifectix, Inc. Confidential
Today: To deploy a change
1. Search for modules from the open source community
pages that appear to meet your needs
2. Select the best fitting module.
3. Check for any module updates.
4. Investigate support options if the module does not work
perfectly.
5. Check environment dependencies for the module to work
correctly.
6. Inspect each line of the scripting module to ensure it is
safe.
7. Edit the module if it will not work off the shelf. (This might
require knowledge of RUBY).
8. Script the solution.
9. Test it.
10. Deploy it.
11. Document the process and the rationale behind it (for
future users and auditors).

30. Trifectix, Inc. Confidential
Today: To deploy a change
1. Search for modules from the open source community
pages that appear to meet your needs
2. Select the best fitting module.
3. Check for any module updates.
4. Investigate support options if the module does not work
perfectly.
5. Check environment dependencies for the module to work
correctly.
6. Inspect each line of the scripting module to ensure it is
safe.
7. Edit the module if it will not work off the shelf. (This might
require knowledge of RUBY).
8. Script the solution.
9. Test it.
10. Deploy it.
11. Document the process and the rationale behind it (for
future users and auditors).

31. Trifectix, Inc. Confidential
Today: To deploy a change
1. Search for modules from the open source community
pages that appear to meet your needs
2. Select the best fitting module.
3. Check for any module updates.
4. Investigate support options if the module does not work
perfectly.
5. Check environment dependencies for the module to work
correctly.
6. Inspect each line of the scripting module to ensure it is
safe.
7. Edit the module if it will not work off the shelf. (This might
require knowledge of RUBY).
8. Script the solution.
9. Test it.
10. Deploy it.
11. Document the process and the rationale behind it (for
future users and auditors).

32. Trifectix, Inc. Confidential
Today: To deploy a change
1. Search for modules from the open source community
pages that appear to meet your needs
2. Select the best fitting module.
3. Check for any module updates.
4. Investigate support options if the module does not work
perfectly.
5. Check environment dependencies for the module to work
correctly.
6. Inspect each line of the scripting module to ensure it is
safe.
7. Edit the module if it will not work off the shelf. (This might
require knowledge of RUBY).
8. Script the solution.
9. Test it.
10. Deploy it.
11. Document the process and the rationale behind it (for
future users and auditors).

33. Trifectix, Inc. Confidential
Today: To deploy a change
1. Search for modules from the open source community
pages that appear to meet your needs
2. Select the best fitting module.
3. Check for any module updates.
4. Investigate support options if the module does not work
perfectly.
5. Check environment dependencies for the module to work
correctly.
6. Inspect each line of the scripting module to ensure it is
safe.
7. Edit the module if it will not work off the shelf. (This might
require knowledge of RUBY).
8. Script the solution.
9. Test it.
10. Deploy it.
11. Document the process and the rationale behind it (for
future users and auditors).

34. Trifectix, Inc. Confidential
Today: To deploy a change
1. Search for modules from the open source community
pages that appear to meet your needs
2. Select the best fitting module.
3. Check for any module updates.
4. Investigate support options if the module does not work
perfectly.
5. Check environment dependencies for the module to work
correctly.
6. Inspect each line of the scripting module to ensure it is
safe.
7. Edit the module if it will not work off the shelf. (This might
require knowledge of RUBY).
8. Script the solution.
9. Test it.
10. Deploy it.
11. Document the process and the rationale behind it (for
future users and auditors).

35. Trifectix, Inc. Confidential
Today: To deploy a change
1. Search for modules from the open source community
pages that appear to meet your needs
2. Select the best fitting module.
3. Check for any module updates.
4. Investigate support options if the module does not work
perfectly.
5. Check environment dependencies for the module to work
correctly.
6. Inspect each line of the scripting module to ensure it is
safe.
7. Edit the module if it will not work off the shelf. (This might
require knowledge of RUBY).
8. Script the solution.
9. Test it.
10. Deploy it.
11. Document the process and the rationale behind it (for
future users and auditors).

36. Trifectix, Inc. Confidential
Today: To deploy a change
1. Search for modules from the open source community
pages that appear to meet your needs
2. Select the best fitting module.
3. Check for any module updates.
4. Investigate support options if the module does not work
perfectly.
5. Check environment dependencies for the module to work
correctly.
6. Inspect each line of the scripting module to ensure it is
safe.
7. Edit the module if it will not work off the shelf. (This might
require knowledge of RUBY).
8. Script the solution.
9. Test it.
10. Deploy it.
11. Document the process and the rationale behind it (for
future users and auditors).

37. Trifectix, Inc. Confidential
Today: To deploy a change
1. Search for modules from the open source community
pages that appear to meet your needs
2. Select the best fitting module.
3. Check for any module updates.
4. Investigate support options if the module does not work
perfectly.
5. Check environment dependencies for the module to work
correctly.
6. Inspect each line of the scripting module to ensure it is
safe.
7. Edit the module if it will not work off the shelf. (This might
require knowledge of RUBY).
8. Script the solution.
9. Test it.
10. Deploy it.
11. Document the process and the rationale behind it (for
future users and auditors).

38. Trifectix, Inc. Confidential
Today: To deploy a change
1. Search for modules from the open source community
pages that appear to meet your needs
2. Select the best fitting module.
3. Check for any module updates.
4. Investigate support options if the module does not work
perfectly.
5. Check environment dependencies for the module to work
correctly.
6. Inspect each line of the scripting module to ensure it is
safe.
7. Edit the module if it will not work off the shelf. (This might
require knowledge of RUBY).
8. Script the solution.
9. Test it.
10. Deploy it.
11. Document the process and the rationale behind it (for
future users and auditors).

39. Today: To deploy a change
1. Search for modules from the open source community
pages that appear to meet your needs
2. Select the best fitting module.
3. Check for any module updates.
4. Investigate support options if the module does not work
perfectly.
5. Check environment dependencies for the module to work
correctly.
6. Inspect each line of the scripting module to ensure it is
safe.
7. Edit the module if it will not work off the shelf. (This might
require knowledge of RUBY).
8. Script the solution.
9. Test it.
10. Deploy it.
11. Document the process and the rationale behind it.

40. Today: To deploy a change
1. Search for modules from the open source community
pages that appear to meet your needs
2. Select the best fitting module.
3. Check for any module updates.
4. Investigate support options if the module does not work
perfectly.
5. Check environment dependencies for the module to work
correctly.
6. Inspect each line of the scripting module to ensure it is
safe.
7. Edit the module if it will not work off the shelf. (This might
require knowledge of RUBY).
8. Script the solution.
9. Test it.
10. Deploy it.
11. Document the process and the rationale behind it.
12. Hope the author doesn’t leave the company.

41. Today: To deploy a change
But first…
Train your
staff on a new
declarative or
scripting
language
1. Search for modules from the open source community
pages that appear to meet your needs
2. Select the best fitting module.
3. Check for any module updates.
4. Investigate support options if the module does not work
perfectly.
5. Check environment dependencies for the module to work
correctly.
6. Inspect each line of the scripting module to ensure it is
safe.
7. Edit the module if it will not work off the shelf. (This might
require knowledge of RUBY).
8. Script the solution.
9. Test it.
10. Deploy it.
11. Document the process and the rationale behind it.
12. Hope the author doesn’t leave the company.

42. Today: To deploy a change
But first…
Train your
staff on a new
declarative or
scripting
language
1. Search for modules from the open source community
pages that appear to meet your needs
2. Select the best fitting module.
3. Check for any module updates.
4. Investigate support options if the module does not work
perfectly.
5. Check environment dependencies for the module to work
correctly.
6. Inspect each line of the scripting module to ensure it is
safe.
7. Edit the module if it will not work off the shelf. (This might
require knowledge of RUBY).
8. Script the solution.
9. Test it.
10. Deploy it.
11. Document the process and the rationale behind it.
12. Hope the author doesn’t leave the company.

43. Trifectix, Inc. Confidential
Tomorrow:
WebSphere Application Server
Configuration Management Earthquake

44. Trifectix, Inc. Confidential
Server Focus  Application Focus
Server
Operating System
Database
App
Middleware
Today’s tools
focus here

45. Trifectix, Inc. Confidential
Server Focus  Application Focus
Server
Operating System
Database
App
Middleware
Next generation
configuration
management will
focus on the
application
ecosystem
Today’s tools
focus here

46. Trifectix, Inc. Confidential
Server Focus  Application Focus
Server
Operating System
Database
App
Middleware
Next generation
configuration
management will
focus on the
application
ecosystem
Today’s tools
focus here

47. Trifectix, Inc. Confidential
Server Focus  Application Focus
Server
Operating System
Database
App
Middleware
Next generation
configuration
management will
focus on the
application
ecosystem
Today’s tools
focus here

48. Trifectix, Inc. Confidential
Scripting-centric  Modern, Intuitive interface

49. Trifectix, Inc. Confidential
Scripting-centric  Modern, Intuitive interface

50. Trifectix, Inc. Confidential
Scripting-centric  Modern, Intuitive interface

51. Trifectix, Inc. Confidential
Scripting-centric  Modern, Intuitive interface
Where the domain knowledge is built-in, tested, scalable and extendable.

52. Trifectix, Inc. Confidential
Why is this important?
Visibility Automation Control Audit-ready

53. Environment-Aware Releases

54. Environment-Aware Releases

55. Environment-Aware Releases
Application
Ecosystem

56. Environment-Aware Releases
Application
Ecosystem
Managing
Dependencies
& Relationships
Managing
Dependencies
& Relationships

57. Trifectix, Inc. Confidential
Image credit:
https://commons.wikimedia.org/wiki/File:View_into_chasm_known_as_Huntsman_Leap_-
_geograph.org.uk_-_2154831.jpg
Cloud
Containers
Legacy scripts
Homegrown tools
Point solutions
Technical debt

58. Trifectix, Inc. Confidential
Image credit:
https://commons.wikimedia.org/wiki/File:View_into_chasm_known_as_Huntsman_Leap_-
_geograph.org.uk_-_2154831.jpg
Legacy scripts
Homegrown tools
Point solutions
Technical debt
Mode 2
Operations

59. Trifectix, Inc. Confidential
Image credit:
https://commons.wikimedia.org/wiki/File:View_into_chasm_known_as_Huntsma
n_Leap_-_geograph.org.uk_-_2154831.jpg
Bridge to Modern Platforms
Bridge image credit:
https://commons.wikimedia.org/wiki/File:Suspension_bridge_icon.svg
Legacy scripts
Homegrown tools
Point solutions
Technical debt
Mode 2
Operations

60. Trifectix, Inc. Confidential
Demo
www.orcaconfig.com
@orcaconfig

61. Trifectix, Inc. Confidential
Q&A
www.orcaconfig.com
@orcaconfig