Overview of Command Central: goals, architecture, use cases.

1. COMMAND CENTRAL
UNIFIED MANAGEMENT
AND MONITORING FOR
WEBMETHODS
Jonathan Heywood
Senior Director, Product Management,
Product Marketing and Communities
Software AG
© 2015 Software AG. All rights reserved. For internal use only

2. 2 |
TWO MAIN DRIVERS
Large landscape
management:
• Reduce risk
• Reduce effort
• Increase agility
Cloud enablement:
• Scalability
• Automation
• Elastic
expansion
Command Central

3. 3 |
Deploy
Install Configure
Patch
Administer
Monitor
WHO IS COMMAND CENTRAL FOR?
Infrastructure engineers System administrators System operators

4. 4 |
CHALLENGES FOR TODAY’S WEBMETHODS ADMINS
Scale Risk Different
products
Segregation of
responsibilities

5. 5 |
KEY REQUIREMENTS
Centralized
Unified
Scalable
Automatable

6. 6 |
• Compare fix levels
• Install fixes
• Audit trail
COMMAND CENTRAL SCOPE
• Manage installations and instances
• Group into environments
• Monitor, start/stop
• Access log files
• Manage software repository
• Bootstrap servers
• Install product
Product
Installation
Fix
Management
Landscape Management
Web UIService APICommand Line
• Unified configuration
• Compare configuration
• Across multiple instances
Central
Configuration
• Deployment of assets
• Linked to environments
• Compare assets
Solution
Management
(Future)
• Define templates
• Product, Fixes, Config, Assets
• Manage substitution variables
• Apply templates to targets
Template-based Provisioning

7. 7 |
COMMAND CENTRAL ARCHITECTURE
Installation
Platform Manager
SPM
Plugin
SPM
Plugin
SPM
Plugin
Runtime A
Runtime B
Runtime C
Command
Central
Server
Web UI
Service API
Command Line

8. 8 |
BACKWARD COMPATIBILITY
• Command Central is backward compatible
– It can manage installations from 9.0 and higher
• Functionality may be limited when managing older
installations
– Dependent on the capabilities of that SPM/plugin version
– You cannot upgrade SPM/plugin for an old installation
• Always use the latest version of Command Central
CC
9.9
SPM
9.0
SPM
9.5
SPM
9.6
SPM
9.7
SPM
9.8
SPM
9.9

9. 9 |
USE-CASES
Elastic Expansion
New project/developer environments
Repro-environments
Scripted maintenance activities
Centralized management/monitoring

10. 10 |
USE CASE 1
© 2015 Software AG. All rights reserved. For internal use only
• Single, central view of your landscape
– Do everything from one console
– Manage all products in the same way
– Group servers into environments
• No need to log onto remote machines to…
– Start/stop components
– Install fixes
– Access log files
• Keep your landscape in shape by…
– Finding configuration discrepancies
– Spotting issues in time
– Checking license compliance
CENTRALIZED MANAGEMENT/MONITORING

11. 11 |
USE CASE 2
© 2015 Software AG. All rights reserved. For internal use only
• Everything in Command Central is
available through command-line (CLI)
• Prepare scripts for your sysadmins
– Stop/restart multiple components
– Install fixes
– Make a configuration change
• Less effort
– Write once
– Easily repeated on multiple components
• Less risk
– No human error from clicking through UI
SCRIPTED MAINTENANCE ACTIVITIES
> cc exec lifecycle stop prodis1
> cc list monitoring runtimestatus prodis1
--check-every 5 --wait 60 --expected-values
STOPPED
> cc exec lifecycle start prodis1
>
> cc exec provisioning fixes prodis1 Empower
install artifacts=wMFix.IS.IS9_8CoreFix1
>
> cc update configuration data prodis1 JDBC
-i jdbcupdate20151016.xml
> cc update configuration data prodis2 JDBC
-i jdbcupdate20151016.xml
> _

12. 12 |
USE CASE 3
© 2015 Software AG. All rights reserved. For internal use only
• Reproducing issues can be a big challenge
– Differences in behavior caused by
• Differences in configuration
• Differences in fix-level
• Compare environments to spot differences
- OR –
• Clone an environment using snapshot
templates
– Save problem environment as a
template
– Apply to a fresh machine to get an
identically installed, patched and
configured repro environment
REPRO-ENVIRONMENTS

13. 13 |
USE CASE 4
© 2015 Software AG. All rights reserved. For internal use only
• Automate the installation of new project
environments or developer workstations
– Composite templates
• Products and components
• Fixes
• Configuration
– Distribute in different ways
• Remote network installation
• Single downloadable ZIP file
– Installation with a single command/script
• Keep environments updated
– Update template with latest fixes/config
– Reapply to existing installations
NEW PROJECT/DEVELOPER ENVIRONMENTS

14. 14 |
USE CASE 5
© 2015 Software AG. All rights reserved. For internal use only
• Temporarily increase capacity
• Dynamically add a node to a cluster
• Detect performance degradation
– Command Central KPIs (basic)
– Optimize for Infrastructure (advanced)
– 3rd party monitoring tool (custom)
• Orchestrate provisioning of extra node
– Shell or Ant script
– webMethods Flow or BPM
– 3rd party tool like Chef or Puppet
ELASTIC EXPANSION

15. 15 |
COMMAND CENTRAL DELIVERS
Centralized
Unified
Scalable
Automatable

16. 16 | © 2015 Software AG. All rights reserved. For internal use only