MyST 5.5 brings Application Release Automation to Oracle Middleware

Rubicon Red MyST is the most advanced and intuitive DevOps solution for Oracle Middleware. MyST 5.5 is a major release specifically focused around Application Release Automation, Role-based Access Control and Event Auditing. It also comes with additional installation options making it easier than ever to get a fully functional DevOps for Oracle Middleware stack up and running. In this blog, we will dive into the new features of MyST 5.5.

The MyST 5.5 release comes with Source Code Introspection and a built-in Artifact Property Registry allowing the automatic discovery and management of properties from a single role-based management control console. At deploy-time service endpoints can be discovered by querying the Artifact Property Registry.

Source Code Introspection

Whether you're using MyST's Automated Build Server or a third party CI server, MyST now performs source code introspection during automated build allowing for customisable settings to be automatically discovered.

The MyST Plugin for Jenkins auto-discovers property references within the source code where a property is an expression following the common property-reference syntax; e.g ${some.property}. These properties are reported for each automated build from the CI server so that MyST will automatically manage the association between given versions of an artifact and it's customisable properties.

Artifact Property Registry

Through the MyST console, we can see the relationships between Artifacts and the common properties which they share. This can provide some powerful insight. We can ask question such as "if we change the Production Siebel Endpoint which Artifacts will be impacted?".

In addition to the property relationships, we can provide meaningful descriptions and defaults values for properties directly from within the console.

Promotion Stage Models

At deploy-time MyST will automatically determine which properties need to be defined for the artifacts in a given deployment. This will generate a Stage Model which can be updated with the environment-specific values. This model is persisted at the platform instance-level so we only need to enter the values for the first deployment and they will be reused for subsequent deployments (unless of course you want to change them).

Application Release Approvals

At deploy-time users can be granted Approver and Deployer role permissions for manual promotion stages within a Release Pipelines. These role permissions integrate seamlessly with the existing Role Based Access Control framework.

Role Based Access Control 2.0

In addition to the Application Release Automation enhancements, MyST 5.5 ships with a complete overhaul to the new Role Based Account Control capabilities including:

  • New Intuitive User Experience for managing role permissions.
  • Role Based Access Control for Application Release Automation including Release Pipelines, Pipeline Templates, Artifacts and Application Blueprints.
  • Finer-grained Role Based Access Control for resources such as the Platform Instance to allow for the design of roles at a much more granular level with restricted permissions.
  • Clearer and more consistent User Experience so that only controls which are operational for the given users role are displayed. Previously, users who were prevented from executing certain controls based on their role could still see the controls even though they would disallowed from choosing them.
  • Simple request of necessary grants due to improvements to the authorization failure message in the case of insufficient permissions.
  • Focus on value-added capabilities through the removal of unused capabilities such as Bulk Activation and Deactivation of Roles where the old approach is no longer needed due to the new user experience.
  • Removed Obsolete Role Permissions such as the ability to create and delete Continuous Delivery Profiles.
  • Application Release Automation resources can be grouped into Workspaces allowing for Multi-tenancy.

Comprehensive Event Auditing

As organisations continue to manage all automated tasks from the MyST Studio console, it can be used as a powerful tool for change auditing. MyST 5.5 comes with a number of enhancements including:

  • Complete audit of all events including failed events irrespective of whether it was due to a data retrieval or a manipulation.
  • Authorised users can see which user performed which action including each login and logout operation.
  • Comprehensive troubleshooting information by capturing the complete error details in the audit log for all failed requests.
  • Drill down on each event to see low-level HTTP interactions for complete traceability.
  • Search filters for tracking specific audit types such as event status, resources type and action type to assist with log analysis.

Simplified installation

MyST supports direct integration with an organisation's existing Version Control System, Continuous Integration (CI) Server and Artifact Repository to provide a seamless release management experience across a best-of-breed landscape.

But what if an organisation does not have an existing CI Server or Artifact Repository?

In MyST 5.5, the installer now has options to include an embedded MyST Build Server for Continuous Integration and a Maven-compliant Artifact Repository for storing and managing Artifacts built on the MyST Build Server so organisations have everything they need in one place. Simply, we can run the installer and at the click of a button we will have a fully functional and self-sufficient MyST Stack ready for Automated Platform Lifecycle Management and Application Release Automation.

Summary of MyST 5.5 features

As we have shown, MyST 5.5 is a major release with many exciting new features including:

  • Application Release Automation 2.0
    • Release Management Approvals
    • Auto-discovery of properties from code
    • Dynamic lookup of service endpoints and operation settings
    • Centrally managed Artifact Property Registry with the ability to discover all artifacts that use common properties (and vice-versa).
  • Role Based Access Control 2.0
    • Usability First
    • Finer-grained control
  • Comprehensive Event Auditing
    • Search, filter and drill down on all events
  • MyST Studio Installer 2.0
    • Batteries included for a fully functional DevOps for Middleware stack.

Want to learn more about MyST?
Why not take our free MyST TestDrive for a spin?

Craig Barr

I am a Software Engineer with a decade of experience empowering Enterprises in Banking, Logistics, Manufacturing with Service-Oriented Architecture, Microservices and Cloud Computing.

Brisbane, Australia https://twitter.com/craigbarrau