Back to Blog

MyST Studio 6.5.0

David Tran

Improvements

Usability Enhancements

  • Simplified navigation between modeling and apply actions
  • FC-5897 - Platform instance actions are now available from the Platform Model editor. Actions such as Update and Reprovision can be ran directly without needing to navigator away from the editor.
  • FC-5460 - Users can quickly return from the platform model editor to run an action by clicking the ‘Platform Models > (MODEL_NAME)’ breadcrumb which takes you back to the Platform Models page with the model already selected
  • FC-5293 - Pipeline templates now support defining post-deployment jobs against stages
  • FC-5264 - Platform Instance stop and restart actions now allow optional graceful shutdown and timeout values
  • FC-5248 - Role Based Access Control introduced for Stream Model, Artifact Property Registry and Custom Actions
  • FC-5681 - Release participants can now Approve/Reject directly from the email
  • FC-5748 - Tidied the organisation of the card display for platform blueprints/templates, application blueprints and release pipelines
  • FC-5787 - Improved the search bar to remain visible even when search result is empty
  • FC-5555 - Application blueprints list and the selection screen from release pipelines now support pagination
  • FC-5517 - Custom actions now support search & pagination
  • FC-5822 - The artifact classifier is now displayed in the deployment summary screen
  • FC-5010 - Stream model properties can be set against any stage before promotion occurs. This can be enabled by setting the flag release_management.stream.stream_model in fc-metadata.json.
  • FC-5739 - Performance improvements when displaying displaying a large number of artifacts
  • Error handling improvements
  • FC-5783 - Improved error message when artifact does not have a type defined
  • FC-5803 - MyST SDK Transport JAR logs the error returned from the MyST API instead of just the HTTP response code

Oracle Fusion Middleware Enhancements

  • FC-5821 - Added forcedefault support for SCA artifacts
  • FC-5051 - Added support to preserve security and operational values during OSB deployment time. See MyST Studio artifact documentation to set these properties.
  • FC-5727 - For 12.2.1.3.0 environments using database persistence, during create-domain the WLSDStore now targets to an adminserver name property instead of ‘AdminServer’. For 12.2.1.3.0 ESS environments, during create-domain the BamCQServiceJmsSystemModule now correctly targets to the BAM cluster instead of bam servers which resulted in the AdminServer failing to start
  • FC-5612 - JMS Templates time-to-live can now be configured directly
  • FC-5703 - Additional security providers have been made available in the dropdown: DefaultAuthenticator, DefaultIdentityAsserter, Trust Service Identity Asserter, ID Negotiator, and OAM Identity Asserter
  • FC-5771 - Improved BI Publisher to handle a non-default cluster name
  • FC-5776 - Added support for WebLogic ‘Cross Domain Security Enabled’
  • FC-5789 - Added None option to JDBC Transaction which effectively disables ‘Supports Global Transactions’ courtesy of Maarten Tijhof
  • FC-5828 - Added supported for JMS Topic Time-To-Live-Override
  • FC-5904 - Added support for JDBC InactiveConnectionTimeoutSeconds

Oracle Cloud Enhancements

  • FC-5584 - Deployment of OSB projects to SOA Cloud Service is supported
  • FC-5736 - Added Developer Cloud Service as an option in Continuous Delivery Profile

Axway Provisioning Enhancements

  • FC-5915-1 - Fixed regression requiring .group parameters to be reintroduced
  • FC-5915-2 - Now terminates node manager first time forcefully to allow later restarts
  • FC-5915-3 - Added optional <fqdn>.private=<Private Address> global variable for node indicating private address. See Axway documentation Private Listen or Host Addresses
  • FC-5845 - The updateEnvSettingsStore causing Axway Gateway instances to fail to boot after provisioning. This includes restart changes along with fix to duplicate primary key in ExtConnSettings.xml (was not incrementing PK after fetching).
  • FC-5813 - Corrected error in PK assignment in CertStore creation for admin node resulting in access to AAG console failing
  • FC-5813 - Corrected parameters for jvm.xml update to use group name instead of group ID
  • FC-5840 - Axway provisioning now kills both internal or external gateway processes instead of only one
  • FC-5499 - Support for provisioning of API Manager
  • FC-5798 - A number of required model fields are now autocomputed to a default value of ‘?’ if no meaningful value can be determined, in order to remove any guesswork around creating a fully functional model.
  • FC-5503 - Added remaining post installation tasks for Axway
  • FC-5706 - Improved ability to specify components to multiple groups using a global variable. See Provisioning Axway API Gateway for more information.
  • FC-5701 - Improved the shutdown of Axway processes to ensure the process has ended
  • FC-5651 - Pre-Install validation for Axway & Cassandra so provisioning can fail-fast
  • FC-5502 - Additional admin gateway post-installation tasks to handle certificates

Bug Fixes

  • FC-5941 - Fixed regression where graceful shutdown required graceful.shutdown global variable to be set. This is no longer required.
  • FC-5938 - Removed plain text passwords from myst-diagnostic.log
  • FC-5877 - Fixed issue with wrong computation of Admin server machine resulting in unnecessary workarounds to rectify the configuration. See Help Center article
  • FC-5913 - Fixed regression where Check for Drift simply did not run
  • FC-5848 - Fixed regression where a Release Pipeline - Post Deployment parameters was not getting passed
  • FC-5881 - Fixed regression when editing an existing stage’s Post Deployment Action in the Release Pipeline
  • FC-5870 - Fixed regression where the add new artifacts to Application Blueprint page refreshes indefinitely
  • FC-5231 - Prevented the deletion of Infrastructure Provider that is associated to a Platform Model
  • FC-5458 - Fixed an issue viewing Platform Editor Commit History when historical user has been deleted
  • FC-5831 - Fixed regression where the Model wizard cannot be created with a standalone admin server when the Blueprint is initially configured to collocated admin server
  • FC-5581 - Platform Instance Report no longer gives authentication error for non-admin user
  • FC-5812 - Release Pipeline deployment errors with ‘Artifact Build Conflict validation failed’ when the same artifacts use different classifiers
  • FC-5774 - Fixed duplicate entry error when publishing metadata custom property which should be case sensitive
  • FC-3868 - Addressed issue where fix-stop-script does not preserve permissions when updating stopWebLogic.sh
  • FC-5683 - Integer properties (eg. JMS Time-to-Live Override) now reverts to ‘null’ instead of an empty string ‘’ when deleting the value from the UI text field which was throwing a NumberFormatException.
  • FC-5795 - Fixed dryrun and check-for-drift failing to handle changes to targets resulting in a failed weblogic session due to an Oracle bug
  • FC-5710 - Reinstated VERSION variable in backup-database.sh so the filename contains MyST version
  • FC-5395 - Fixed the sort/filter on platform instance artifacts
  • FC-5738 - Changed Oracle Entitlements Server domain template from AdminServer to Managed Server template. Resources now target to the cluster instead of just the AdminServer.
  • FC-5769 - Resolved a regression where application configuration, WSM policies and OSB custom xpath libraries failed to deploy for MyST CLI
  • FC-5567 - Fixed Oracle BI Publisher 12.2.1.3.0 catalog so a blueprint can be created
  • FC-5784 - Added BI Publisher 12.2.1.3 WLSSchemaDataSource datasource to the Platform Blueprint
  • FC-5777 - Fixed email validation during user creation not allowing valid email addresses
  • FC-5775 - Error while downloading artifact upon OIC deployment

Known Issues

  • In 6.5.0, 6.5.1, and 6.5.2 a regression was identified where the Release Pipeline dashboard view page load times increased significantly. The increa se is relative to the number of Stages configured in the pipeline. Each Stage will increase the total page load time by around 2-3 seconds. A fix is expected to be released in 6.6.0-rc1.

Share on social media: 

More from our Blog

Myst Studio 7.1.0

Announcing 7.1.0 - a cumulation of release notes from `7.1.0-rc1` to `7.1.0-rc15`

Read Story

Connect with the myst community on our slack channel.

Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa.
We will never share your email address with third parties.
Join Community