WebSphere Application Server configuration management: Traditional Approaches lead to Traditional Challenges
Today admins are currently forced to do one of three things to configure their WebSphere Application Server (WAS):
- Use the WAS admin console to manually view configurations
- Write and maintain wsadmin scripts, or
- Maintain wsadmin scripts through an automation tool.
30 min – 2 hours
A Common Scenario: comparing WebSphere configurations
A WebSphere Admin is often managing and comparing multiple WAS cells for different environments and applications, going back and forth between different admin consoles.
In order to keep all WAS cells configured consistently, the admin will, therefore keep multiple separate user interfaces open and then manually check, edit and save every single one. There is an easier way to do this.
WAS ND is a powerful, yet notoriously complex application server.
WebSphere Application Server ND configuration management is a particularly difficult, thankless, time-consuming and error-prone task that is yet another of those areas in IT that has stubbornly resisted automation…
Until Orca. Here’s how.
WebSphere Application Server configuration management and automation from Orca.
With its out of the box integrations to WebSphere Application Server, Orca automatically inventories WAS ND configurations. This inventory involves automatically detecting, capturing, storing and displaying configurations. These settings are then immediately normalized into a human readable map for birds-eye and granular views of configurations and comparisons across cells and environments.
With Orca you visually model WebSphere ecosystems (including related applications, databases and operating systems) so that it’s easy to separately manage different sets of configuration data. An example would be delineating between Dev and UAT cells or managing cell level configurations, cluster configurations, applications, etc. from different views and hierarchies.
View and compare configuration changes
Using Orca, you can view configuration settings between points in time in just a few clicks – rather than rely on fragile scripting or point solutions.
And instead of forcing you to look through 30,000 configuration items to find that “needle in a haystack”, you can easily, visually find and compare configuration settings across different environments using Orca’s powerful and intuitive search and drift detection capabilities.
Orca also supports tokenization for returned configuration data for finer control over multiple environments. A major time saver.
Orca provides powerful WebSphere Application Server configuration management, compliance and automation options including:
- Simply view the configuration data
- Detect drift your way. For instance, you can compare your normalized configurations to a reference point in time.
- Apply custom compliance rules for performance, availability and regulatory policies including:
- Apply Rules such as
- =, ≠, <, >, or value range
- “Same as”, “Different than” or even “Similar to (config data on another node)”.
** This powerful tool is what helps relate application ecosystems to one another, which in turn helps you to know beforehand that “changing this will break that”.
Configuration change audit and reporting:
Orca tells you what changed, when it changed, and where changes were applied.
Using Orca, WebSphere Admins now have unprecedented speed and power in drift detection and configuration management. Contact Orca now to schedule a demo walk-through of WebSphere Application Server configuration management.