Orca 3.5, Part 2: New Capabilities Provide New Control and Insights.
Orca version 3.5 has so many new time-saving notifications, automations, interfaces and new capabilities we had to break the listing into two parts. This is part 2. (Click here for Part 1)
The Orca team is very excited about this release, which provides more efficiencies, easier debugging, new workflow functionality, and more. We think you’ll like it!
New Linux/Unix Interfaces
- Easily inventory cron configurations to see how and which cron jobs have been configured. Instantly know if an unexpected cron job has been added.
- Check running processes and quickly see if process thresholds have exceeded their limitations.
- Always know which filesystems have been mounted and if unexpected mounts have been added.
IBM MQ Interface
- You asked and we listened! New to 3.5 is the IBM MQ interface to inventory and change IBM MQ configurations. Click here for a listing of Orca’s DevOps tool chain integrations.
With Orca you can now manage IBM MQ:
- queues (local, alias, model, remote)
You can also:
- Create and delete queue managers
- Stop and start queue managers
- Create and delete queues
- Create and delete topics
- Create and delete subscriptions
- Create and delete channels
- Create and delete listeners
“One-Click” Application Updates
In the 3.4 release, we added a Compare Results section where you can create recurring comparison jobs. These reports are readily available and show you environment or point-in-time comparisons. With “One-Click” you can now use these comparison results to apply configurations from one environment to another.
This is a major convenience and MTTR (mean time to recovery) improvement! Right from the “Compare Results” page, you can kick off a workflow if something has changed and needs to be quickly remediated.
Oracle Support for Orca Backend
You can now connect Orca to a backend Oracle database. This is a great option for organizations where Oracle is the standard, supported database.
Nodes can now have multiple Compliance Rule Sets
Prior to the 3.5 release, users could assign one set of compliance rules to a node. Now in 3.5, Orca users can assign multiple compliance rulesets to a node. This allows users to create one ruleset for security policy, one for performance, etc. and be able to add them all to the same node!
Token Separation on Nodes
Tokens are now logically separated on the Details tab within each node. Now it’s easier to see which tokens are deployment properties, which are node tokens created from compliance rules, and which are server tokens created from compliance rules.
Reminder, this is just only a partial listing of what’s new in Orca version 3.5. Make sure to read about Orca 3.5 part 1 to learn more about the new WAS status interface, workflow promotion, deployed applications tab, and helpful updates to existing Linux/Unix interfaces.