New Features
- Patches can be applied in a rolling manner to selective nodes with the option to restart the servers running on the nodes as well once they are patched
- One can now execute different post deployment jobs per environment even while using the same Application Blueprint.
- MyST Studio computation simplifies Exalogic EDG compliance
- MyST Studio now reports exceptions in a consistent manner with proper error codes and debug information, allowing end users to contact support with much more concrete information about an issue.
- MyST now supports selection of RDS as the data source type in the platform model wizard along with Gridlink and Generic. It auto-computes the SYS user name based on the data source type
- MyST now supports an additional flag argument, ‘limit-nodes’ which can be set to limit the action to specific nodes. All actions which manage start / stop lifecycle of servers / machines honor this (patch, stop, stop-all, start-all, restart-all, start-nm, stop-nm, etc.)
Improvements
- Platform Blueprint and model improvements. We display now only the fields related to the selected components. So if no WebLogic domain or RCU exists, those componets do not appear in all screens, nor in the tree view
- MyST Studio now supports start, stop and terminate operations for OAG configurations.
- MyST Studio now ensures that OAG instances are assigned with an ordering consistent with the ordering of nodes in a configuration.
- DNS lookup to create fully qualified domain names for hosts must now be enabled via the -Ddns.domain-name.generation=on parameter, and does not happen by default.
- MyST Studio allows deletion of a specific version of an artifact (as long as the version is not already part of any application blueprint)
- Note - The update action no longer applies patches. To apply it, one would have to first update the instance to the version of blueprint / model which has patches and then explicitly apply them using the patch command from the control menu
- The memory settings in the Advanced configuration step of the platform model wizard now show MFT, BAM and ESS
- For pre-existing infrastructure, MyST now only establishes connectivity with the Admin node. For on-demand, it establishes connectivity with all the nodes as before.
- Security improvement: RCU system password can be used only by RCU actions
- MyST Studio UI was performing slower than desired as it was making a lot of redundant API calls to the backend
- You can now add additional parameters to be taken by the OFMW installation. e.g: -Doui.additional.args=-ignoreSysPrereqs
- You can now specify the RCU property for OFMW 12.2.1: soa-profile-type=LARGE, which will use partitioning on the SOA schemas
- MyST now allows one to have composite actions as part of pre / post of other actions
Bug Fixes
- Bug Fixed: Patches under fmw-common can now be applied. e.g: For OWSM
- Bug fix: MyST Studio was not looking for the license under conf/fusioncloud/license when the user logs in
- Bug fix: MyST Studio now reports errors for an invalid / missing license correctly rather than saying that the user id / password are invalid
- Bug fix: If a blueprint version is finalized without making any changes, the instance prompts one to update to the latest version though it is already up to date
- Bug fix: When a blueprint version is finalized, the instances start showing out-of-date even though they are at the latest version / revision
- Bug fix: The start-nm command honours the -Dmachines override now
- Bug fix: Provisioning was failing when one has OSB, SOA, BAM, BPM, ESS and ADF 12.2.1
- Bug fix: On session expiry, the user is now automatically redirected to the login screen with the error message shown in-place
- Bug fix: Deleted users were causing exceptions when trying to configure users within a workspace.
- Bug fix: MyST Studio does not allow deletion of platform blueprint version if it is associated with any application blueprint versions
.png)
