New Features
- MyST now has a continuous delivery release pipeline which allows you to apply and promote code and configuration changes from lower to higher environments
- MyST now has the ability to introspect an existing WebLogic domain and generate a platform blueprint and optionally a platform model from it
- MyST can now be used to generate a platform blueprint for a higher middleware version based on an existing blueprint which is at a lower middleware version
- MyST now supports provisioning of OBIEE 12c
- MyST now supports deployment of BAM 12.2.x artifacts
- MyST now supports deployment of MFT and B2B artifacts
- MyST now supports configuration of WebLogic Store-and-forward resources (agents, remote contexts, imported destinations and error handling)
- MyST now supports Archiva 2.2.x as a binary repository manager for artifacts
Improvements
- MyST now allows the user to explicitly commit platform blueprints and models and allows them to work on draft revisions until they are ready to be committed.
- MyST now allows only committed revisions to be used in platform provisioning, updates and also as part of a release pipeline
- One can no longer have multiple platform model versions for the same blueprint version. There can only be one model configuration per blueprint version
- MyST now shows more meaningful revision prefixes for platform blueprints / models, application blueprints / models as well as release pipeline stream and stage revisions
- MyST now shows revisions everywhere irrespective of the state of the platform blueprint / model so that it is less ambiguous to the user
- For on-demand AWS instance provisioning, one now has the option to retain the instances in case of provisioning failures. Previously we were auto-terminating instances but now this choice lies with the user
- For artifact configuration plans, the user now needs to specify less metadata and MyST discovers the plan automatically if configured with proper naming conventions
- For AWS RDS, MyST now handles dropping of connections more gracefully when the instance is terminated and does not report back errors in event of already closed connections
- MyST now allows users to define a custom Maven settings in MyST Studio, which will be used to retrieve artifacts at deployment time. Previously, the Maven settings had to be defined on the target host and was not controlled by MyST.
- WebLogic Authenticator for OpenLDAP can now be configured with MyST
- Migratable targets are now supported for Weblogic resources update
- Per-host Node Manager can now be enabled using MyST
- Custom nodemanager.properties can now be set using MyST
- SOA Mbeans can now be configured on 12.2.1.1.0
- MyST now allows one to configure SSL for OHS
- MyST now allows one to define a custom log format for OHS
Bug Fixes
- Fixed: RCU fails on 12.2.1 when the temp and default tablespaces are customised
- Fixed: Node Manager listen address does not get set for per host node manager
.png)
