New Features
- MyST Studio now supports authentication through API keys which can be selectively generated, enabled and disabled for particular users
- The application blueprint can now be configured to have an optional post deployment job on the CI server which is kicked off in a fire-and-forget manner by MyST Studio
- A new option is provided in the platform model whereby a platform update is automatically performed before a deployment happens against an instance
- It is now possible to specify most of the common logging configuration for the WebLogic servers
- It is now possible to configure mail sessions as part of blueprints / models
- It is now possible to specify JTA timeout as part of blueprints / models
Improvements
- Key-value style platform properties can now be edited in bulk through the UI
- The LDAP provider configuration has been extended to support additional configuration parameters
- The startup and shutdown class configuration has been extended to support additional configuration parameters
- The platform model now shows all actions taken against it irrespective of provisioning / termination to provide better traceability
Bug Fixes
- Bug fix: Node manager computation was incomplete when there is a customisation on the Admin Server properties
- Bug fix: The console URLs were not being computed correctly when SSL was enabled
- Bug fix: oui.inventory.loc default value /etc/oraInst.loc was not computed for MyST Studio, and was resulting in the instance configuration getting messed up
- Bug fix: Translation of key-value style params to the properties form does not work if it contains reserved characters (‘[’ or ‘]’)
- Bug fix: Reordering of LDAP providers was not working
- Bug fix: Persistence strategy for one data sources was affecting the setting for other data sources
- Bug fix: The node manager settings dont seem to get applied if previous changes are introduced in online mode which require a server restart
.png)
