How to determine configuration settings automatically

Automatically create configuration snapshots of current configuration settings

Orca helps you determine configuration settings by capturing all configurations for your infrastructure including your applications, databases, middleware and operating systems.

How is Orca different?

Orca captures infrastructure configurations for all your environments and displays the captured configurations in a human readable map in Orca’s management console. We call this an “inventory”, but you may know it as a configuration snapshot or configuration collection.

 Why is this important?

Many tools, including scripts, homegrown tools, or other open source or commercial tools allow you to set a desired state for a configuration (DSC), but you never actually get to see what the configurations are and how they relate to one another. With Orca you can log into a console and within seconds being able to see all your detailed middleware, database, application, and OS configurations. You can also view the configurations from any point in time in the past. Your team immediately becomes more efficient because you know what changed, when it changed, and how it changed, and you instantly know what configurations have changed between application releases, or even as the result of a release.

With Orca you do not have to write scripts to determine your current infrastructure configurations. Orca already knows what configurations need to be gathered and immediately starts gathering them for you without any scripting or detailed knowledge needed.

Configuration visibility example: How to determine configuration settings in IIS
How to automatically determine configuration settings in IIS using Orcaconfig

Click image to enlarge

Example: Determining configuration settings in WebSphere Application Server
How to automatically determine configuration settings in WebSphere Application Server using Orcaconfig

Click image to enlarge

You need visibility first!

Other configuration automation tools force you to determine (and script) up front what you want your configurations to look like before you apply them. But sometimes all you’re really looking for is visibility that gets you to the core issues at hand right now and also lets you see what’s been going on in the past.

Beyond just viewing your configuration inventory, you can also compare configurations, store your configurations, and view out of compliance configurations.

How powerful would it be to instantly know what configurations have changed between application releases, or even as the result of a release?

Example Video: Automatically determining configuration settings in WebSphere Application Server and in IIS

How to determine configurations

Powerful simplicity.

Request a demo walk-through.