Orca Saves Time, Money and Hassle in Automating WebSphere workflows
Essential but difficult WebSphere use cases now automated. DevOps Delivered.
Automating WebSphere Workflows: Common “Compare” Scenarios
Compare the configuration of two different ecosystems (WAS cells)
You come back from lunch and a bunch of developers are at your desk waiting for you. They deployed an application update to production that is running slowly and since it ran okay in staging they want to know what is different in WAS between the two environments. The typical way of comparing the two environments is to open a console session for each cell and compare all the configuration parameters page by page, parameter by parameter which can take hours.
With Orca, you just inventory both environments and run a comparison to identify any parameters that are different.
Compare ecosystem configurations (WAS cell) from two different time periods
You walk into the office on Monday morning and the Availability Manager is at your desk waiting for you. He says the ABC application worked fine on Friday but is now failing. He wants to know what changed in WAS over the weekend. You could spend hours going through the WAS console trying to identify parameters that had changed and you could check the time stamps on all the configuration files looking for changes.
Or with Orca you simply run an inventory of the environment and then do a comparison to the inventory that was automatically run Friday.
Automating WebSphere Workflows: Common Automation Scenarios
Up to 2 days
You have a set of WAS cells (Dev, Staging, Production,Training) that support application XYZ. The development team says they need additional Dev and staging cells to support parallel development streams. You then have to spend potentially days manually creating new profiles, deploying applications and configuring application resources.
With Orca, you can create the new dmgr and application profiles, federate the application nodes and then export the resources from the existing cells and import them into the new cells. And with Orca, you just inventory both environments and run a comparison to identify any parameters that are different.
Build a new environment
The development team has developed a new application that has been tested in staging and now they want a production environment built. So you will have to identify all the resources in the staging environment (clusters, cluster members, JDBC and JMS resources, Resource Environment entries, authentication aliases, etc.) and configure them manually in the new production cell hoping you don’t miss anything or mistype a value.
With Orca you would just export the configuration from staging and import it into production. Then modify the parameters that need to be changed (i.e. authentication alias passwords, database URLs).
Click here to learn more about WebSphere Application Server ND Configuration Management.
With Orca, WebSphere Admins 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.
New white paper: 6 Big, Bad WebSphere Application Server Config Management Mistakes