MyST Studio 6.5.0-rc6

New Features

  • FC-5293 - Pipeline templates now support defining post-deployment jobs against stages

Improvements

Usability Enhancements

  • FC-5739 - Improved response time for loading pages that have to display a large number of artifacts
  • 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 pipeline 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-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-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

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-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-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

MyST Studio 6.4.3

Bug Fixes

  • 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

MyST Studio 6.4.2

Bug Fixes

  • FC-5769 - Resolved a regression where application configuration, WSM policies and OSB custom xpath libraries failed to deploy for MyST CLI

MyST Studio 6.4.1

Improvements

  • FC-5568 - Temporary directory can now be set for silent installations of .bin files

Bug Fixes

  • FC-5682 - Release Pipeline deployment after approval will now only allow the approved version
  • FC-5705 - Resolved occasional timeout issue in MyST CLI during execution of the update action
  • FC-5708 - Resolved a regression in 6.4.1 where the artifact fails to deploy when there is no MyST Configuration Plan

MyST Studio 6.4.0

New Features

  • FC-5276 - MyST will now email notify Release Pipeline participants on approval steps
  • FC-5352/FC-5583 - Platform Blueprint editor enhancements
    • Managed Servers are now allowed to be defined in Platform Blueprints so that repeated configuration can be avoided within the Platform Models. The reduced configuration overhead saves time and reduces the risk of making mistakes.
    • Vertical scaling is now supported for vanilla WebLogic Managed Servers. This means that on a single host and within a cluster there can be multiple Managed Servers.
    • Additional vanilla WebLogic Managed Servers and Machines can now be manually added directly within Platform Blueprints after the wizard has completed.
  • FC-5267 - Axway API Gateway automated platform provisioning support
  • FC-5628 - Lifecycle Management for Axway: Start, Stop, Restart, Terminate

Improvements

  • FC-5354 - When doing a Bulk Edit in the Blueprint/Model an auto-save is now performed to prevent an accidental loss of properties when a user navigating away from the component view
  • FC-5376 - Resolved the unwarranted display of safe warn messages in the log that were causing undue alarm
  • FC-5464 - Platform Instance will now display more than 15 pending actions
  • FC-5390 - Platform Blueprints can now be created for Oracle Business Intelligence Enterprise Edition 12c with the Oracle Webtier fronting the inbound requests
  • FC-5048 - It is now possible to target a Foreign Server to a Sub-deployment under Messaging Configuration.
  • FC-5250 - MyST now allows for a Custom Product Catalog when defining a Platform Blueprint. This is useful when needing to extend MyST to support a target deployment environment that is not already supported out-of-the-box. When used in combination with the Deployment SDK, this feature allows Application Release Automation for any type of change be it on-prem/cloud, oracle/non-oracle, infra/app etc.
  • FC-5266 - A new backup-database-minimal.sh script is provided to allow for easily generating a minified and redacted copy of user data in the case of raising a MyST support ticket.
  • FC-5398 - Managed Server original name has been set to read-only as it should never need to be changed by the end user.
  • FC-5298 - Infrastructure Provider SSH connection tests can be run without having to first save the host details
  • FC-5415 - Security Provider now supports Max Group Membership Search Level, Max Group Hierarchies In Cache, and Group Hierarchy Cache TTL
  • FC-5565 - Server groups for Managed Servers can now be defined in the Platform Blueprint
  • FC-5582 - Reintroduce pre-6.2.0 support for deployment of application configuration, WSM policies and OSB custom xpath libraries
  • FC-5590 - The JNDI name is marked as mandatory for JCA Adapters
  • FC-5621 - Connection Factory Interface is auto-calculated for each given JCA Adapter type when it is saved
  • FC-5664 - Integration Cloud Deployment Automatic Retry
  • FC-5630 - Security Enhancements for Axway Provisioning
  • FC-5629 - Axway Reprovisioning without needing to do a Terminate first
  • FC-4695 - Deployment will halt if MyST Configuration Plan is set but does not exist (unless ignore-missing-myst-config-plan=true)
  • FC-5684 - Addressed an issue with Axway termination in 6.4.0-rc8

Bug Fixes

  • FC-5462 - Addressed an issue with the security action when there is another provider which returns more than 1000 results
  • FC-5537 - Addressed an issue caused by FC-5250 which lead to a deployment failure in the pre-validation connectivity check
  • FC-5494 - Fixed an issue with Deploy SDK and OIC/PCS/ICS deploys being unable to use an embedded settings.xml from the CDP
  • FC-5473 - Fixed an issue where MyST agent was creating world readable log files in some instances
  • FC-5298 - Infrastructure Provider SSH connection tests now work with SSH keys
  • FC-5540 - MyST configure-wcc action no longer assumes server names and machine IDs are always sorted in same order.
  • FC-5583 - Fixed issue where it was not possible to have a standalone admin server for a purely vanilla WebLogic domain.
  • FC-5588 - Fixed a false positive for managed server arguments in a check for drift. This happened occasionally after an introspection of complex arguments.
  • FC-5576 - Resolved a 6.3.0 regression which impacted the connectivity between MyST CLI and MyST Studio
  • FC-5643 - Resolved introspection issue introduced on prior 6.4 release candidate
  • FC-5643 - Resolved regression in SSH functionality during pack/unpack for advanced cipher settings
  • FC-5592 - Resolved a defect related to Global Transaction Support for JCA Adapters
  • FC-5322 - Resolved an issue where certain OSB customisation file names did not work

Breaking Changes to Oracle Cloud APIs

  • FC-5652 - Fixed issue in OIC connection retrieval caused by a breaking change to the API on Oracle’s side

Notice

As of 6.4.0, MyST configuration plan is enabled by default for deployments.

To retain the previous behaviour, in the pom.xml set ignore-missing-myst-config-plan=true or disable apply explictly with myst-config-plan-apply=false

MyST Studio 6.3.1

Bug Fixes

  • FC-5418 - Resolved 6.3.0 limitation related to SSH using key pair

MyST Studio 6.3.0

New Features

  • FC-5243 - Artifact Retirement Support
    • Artifacts can now be retired from the Application Blueprint editor.
    • Retired Artifacts are undeployed when the Application Blueprint is promoted through stages of a Release Pipeline
  • FC-5153 - Oracle Communications Order and Service Management (OSM) 7.3.5 can now be provisioned with MyST

Improvements

  • FC-5054 - Usability improvements to the Platform Instance Report
    • Topology View has been introduced
    • MyST Properties (aka name/value pairs) are now shown
    • Addressed an issue where some tables were rendering off the page in a case of long strings (FC-5345)
    • MyST Web is no longer required by customers
  • FC-5326 - Usability improvements to the Artifact Property Registry
    • Significant improvements to performance through pagination
    • The lesser used description has been moved from the default columns to free up space for the property name
  • FC-5336 - MyST now redirects to the originally queried URL after login in a case where the session has timed out.
  • FC-5278 - MyST now provides a REST API for querying artifact build metadata such as Git SHA.
  • FC-5319 - MyST now allows the deletion of blueprint versions as long as they are not associated with an existing Platform Model version.

Bug Fixes

  • FC-5340 - Addressed an issue where a new version of the Platform Blueprint could not be saved following a commit
  • FC-5389 - Fixed an issue where sub deployment could not be selected from the dropdown until saving after a JMS module is selected for a given topic/queue.
  • FC-5342 - Fixed an issue where the ‘run as user’ option could not be unset for a given infrastructure provider host.
  • FC-5383 - Addressed an issue where a WebCenter driver was not being set correctly.
  • FC-5265 - Fixed a regression where the value for oracle base was being incorrectly altered in the case of ExaLogic enablement.
  • FC-4488 - Addressed the issue with passphrases shown in MyST web properties. The solution is to use the new Platform Instance Report for MyST properties, instead of MyST web.
  • FC-5346 - Fixed an issue where long property values were causing the table to render outside of the box for the schedule, approve and deploy screens.
  • FC-5349 - Fixed an issue where Startup and Shutdown classes were not rendering correctly in the Platform Instance Report.

MyST Studio 6.2.5

Bug Fixes

  • FC-5348 - Fixed a regression introduced in the 6.2.2 stream model performance improvements where the same property used by multiple artifacts causes the pre-deployment step to throw an error.

MyST Studio 6.2.4

Bug Fixes

  • FC-5344 - Fixed an issue where RCU was showing up with a duplicate configuration in the platform editor for blueprints introspected using MyST Studio 6.2.3.

MyST Studio 6.2.3

Improvements

  • FC-5330 - MyST now provides the option to de-activate release pipelines from the dashboard view

Bug Fixes

  • FC-5339 - Fixed an issue where since version 6.2.2, MyST was not properly working when accessed over HTTPS. This issue occured due to an upgrade to the underlying Tomcat version. The configuration has been updated to work with the latest version of Tomcat.
  • FC-5312 - Fixed an issue where removing an artifact from an application blueprint version was not decrementing the deployment sequence of subsequent artifacts.
  • FC-5324 - Fixed an issue where system artifacts did not render properly on the user interface.
  • FC-5338 - Fixed an issue introduced in 6.0.0 where values for platform configuration properties could not be overriden to blank from the editor.

Known Issues

Platform Introspection has issues which are resolved by an upgrade to 6.2.4.

MyST Studio 6.2.2

Improvements

  • FC-5211 - Deployed Artifacts can now be viewed against a given Platform Instance. Previously, this was only possible to see within a Release Pipeline Stage.
  • FC-5212 - For each currently deployed artifact, it now shows the user that did the deployment and the date/timestamp.
  • FC-5247 - Improved performance of stream model editing in a case where there is a large number of properties
  • FC-5215 - Artifacts that have changed in a given release are now highlighted.

Bug Fixes

  • FC-5331 - Fixed an issue introduced in 6.2.0 where pipelines that were locked prior to a shutdown were no longer being unlocked when the server restarted
  • FC-5148 - SSL is now correctly configured for WebTier version 12.2.x
  • FC-4984 - MyST now displays an error message if invalid characters are used in a user password
  • FC-5269 - Resolved an issue where artifact introspection was erroneously introspecting values from the pom.xml such as project.basedir
  • FC-5320 - Fixed issue where a non-admin user was being directed to the login screen when downloading support artifacts from the platform instance action history dialog

Known Issues

Affects MyST running on HTTPS and results in users no longer being able to log into MyST Studio. After upgrading and going to the MyST Studio URL a MYST0000 - Service Unavailable error is displayed. This can be resolved by an upgrade to 6.2.3 or by adjusting the Nginx configuration.

MyST Studio 6.2.1

New Features

  • FC-5179 - MyST Studio now supports the creation of OES 11.1.2.3.0 configurations and will provision an OES domain automatically from an OES model.

Improvements

  • FC-4694 - MyST Studio now shows action histories in a paginated fashion, thereby improving the overall user experience and reducing response time considerably.

Bug Fixes

  • FC-5314 - Bug fix: Fixed a regression bug due to which non - administrator user of MyST Studio was denied of access to see the relevant part of the application.
  • FC-5235 - Bug fix: Fixed an issue due to which 11g environment was no longer showing hostnameVerificationIgnored property in the drift report since 6.x.
  • FC-5288 - Bug fix: Fixed an issue with FMW volume mounts for MyST Build Server that were introduced in 6.2.
  • FC-5304 - Bug fix: Fixed an issue due to which OPaaS deployment had stopped working in MyST Studio.
  • FC-5251 - Bug fix: Fixed an issue where all system components were being actioned irrespective of the node they were on even while explicitly limiting the action such as start / stop to run on only specific nodes.

MyST Studio 6.2.0

Improvements

  • FC-5019 - Performance Improvements
    • Significant improvement to the response time for UI when listing Platform Blueprints, Platform Models, Platform Instances, Artifacts, Application Blueprints and Release Pipelines
    • Release Pipelines revision updates are now delivered through an event-driven architecture rather than a polling mechanism
  • FC-5257 - Installer Improvements
    • The MyST Jenkins Plugin and SDK Jar are now bundled in the MyST Build Server.
    • The MyST Build Server is now pulled from the Repository rather than being built from scratch.
  • FC-5261 - WebLogic domain templates can now be overriden in the platform configuration editor
  • FC-4962 - MyST now supports registration of multi-module maven projects where each sub-module is discovered and registered independently
  • FC-5220 - Made a few properties such as passwords and listen addresses editable even at the blueprint level but in advanced mode.
  • FC-4878 - Error messages are displayed when a non-administrative user tries to kick off any of the deployment actions and the deployer role is not set for the pipeline stage.
  • FC-5217 - MyST now supports copying of Global Variable property references for use in other parts of the Blueprint or Model
  • FC-5111 - Improved usability of custom action selection screen

Bug Fixes

  • FC-5246 - Fixed an issue where the run-as user configuration for the MyST agent remote SSH access does not work when the remote workspace location is not accessible to the actual SSH user.
  • FC-5263 - Fixed an issue where introspection was failing when log configuration was set for the admin server
  • FC-5260 - Fixed an issue where the selected compute definition was not getting applied to all the compute groups when creating a blueprint through introspection
  • FC-5262 - Fixed an issue where MyST Studio was not starting up without having an access to internet.
  • FC-5230 - Fixed an issue where MyST was not allowing addition or removal of ABPs from a release pipeline without having to deactivate first
  • FC-5268 - Fixed an issue where Service Console was not showing up correctly in the summary when registering OPAAS instances

Known Issues

  • Fresh MyST Studio installs fail due to the 6.2.0 installer using latest mysql docker image.
    • Workaround is to update /opt/myst-studio/conf/docker-compose.yml:16 from mysql to mysql:5 for example:
      image: mysql:5
    • This issue does not affect existing users who are doing an upgrade.sh
  • MyST Studio users under Role Based Access Control can no longer see Platform Models, Templates, and Instances.
    • There is currently no workaround unless you login as a user with System Administrator privileges

MyST Studio 6.1.0

New Features

  • FC-4916 - Oracle Integration Cloud and Process Cloud artifacts can now be deployed through a MyST Studio Release Pipeline
  • FC-4897 - Improved rendering of the Release Pipeline in a case where there are Multiple versions of an Application Blueprint
  • FC-5177 - Maven classifier is now a supported artifact attribute in MyST Studio
  • FC-5115 - Webtier 11.1.1.7.0 can now be provisioned standalone
  • FC-5210 - An API call can now be made to refresh certain configuration under conf/fusioncloud without needing to restart MyST Studio as was previously the case.

Bug Fixes

  • FC-5222 - Fixed an issue introduced in 6.0.0 where the MyST agent debug log was writing an excessive amount of records
  • FC-5223 - Fixed an issue that was causing NPE when invoking Jenkins via post-deployment job under certain conditions
  • FC-5216 - Fixed an issue where since 6.0.0, any global variables containing a ‘]’ sign were not being properly set while running agent actions
  • FC-5195 - Fixed an issue in WebCenter Content 12.2.1.3 where not all data sources were being computed correctly in the blueprint
  • FC-5209 - Fixed an issue where since 6.0.0 MyST CLI was attempting to perform introspection of domain configuration even when not called from Studio

MyST Studio 6.0.2

Bug Fix

  • FC-5203 - Fixed issue where MyST provisioning fails since 6.0.0 due to Java 1.6 compatibility issues

MyST Studio 6.0.1

Bug Fixes

  • FC-5196 - Fixed issue in 6.0.0 where keystore name was not being handled properly by MyST
  • FC-5197 - Fixed migration issue with respect to data migration of artifact metadata

MyST Studio 6.0.0

New Features

  • FC-4706 - MyST now has a newly designed platform editor for platform configuration which significantly enhances user experience

Known Issues

  • There is an issue with data migration of artifacts in this release. If using release management, it is recommended to avoid this release in favour of a 6.0.1+ release
  • Browser caching may cause the platform editor to render incorrectly. Press CTRL+F5 to force a browser cache refresh

MyST Studio 5.9.1.2

Bug Fixes

  • FC-5223 - Resolved an NPE issue that affected some post-deployment jobs

MyST Studio 5.9.1.1

Bug Fixes

  • FC-5197 - Fixed migration issue with respect to data migration of artifact metadata

MyST Studio 5.9.1

New Features

  • FC-5123 - MyST now supports configuration of the Oracle Virtual Directory authentication provider.
  • FC-4622 - MyST now shows the name of the user who executed an action in Action History UI
  • FC-4028 - MyST now allows user to test the connectivity of hosts while configuring pre-existing infrastructure providers
  • FC-4959 - MyST now visually indicates when deployments in specific stages of a release pipeline are behind the latest revisions of either the previous stage or the latest build in case it is the first stage.
  • FC-4770 - MyST now provides an option to redeploy a stream revision which has failed at pre - validation stage

Improvements

  • FC-5134 - For MyST extensions, the logging for resources that did not have a name has been improved so that troubleshooting is easier
  • FC-5114 - Stream model UI now closes once save or save + commit buttons are pressed
  • FC-4520 - MyST now shows date indicating when a platform model is provisioned/reprovisioned in the model overview page. It is also possible to sort based on this date.

Bug Fixes

  • FC-5130 - Fixed an issue where the user interface was caching role data, hence rendering wrong privileges for roles on the screen.
  • FC-5126 - Fixed an issue due to which name and description were not getting saved from EDIT view of Application Blueprint (Version).
  • FC-5109 - Fixed an issue due to which useful debug information was not getting printed on log when MyST has faced an exception during OSB deployment.
  • FC-5132 - Fixed an issue due to which MyST was not creating a new “build” for Third Party artifacts, even in a valid scenario, where metadata for the artifact is updated.
  • FC-5125 - Fixed an issue where MyST used to allow deployment of a release candidate despite the user explicitly rejecting it.
  • FC-5139 - Fixed data upgrade issue with respect to artifact build metadata. This issue was causing user to successfully upgrade to 5.9.0 version.
  • FC-5157 - Fixed an issue due to which “packaging” field in Artifact detail UI was always showing default packaging (for the artifact type) instead of user entered value.
  • FC-5175 - Fixed an issue where BPM was being erroneously introspected on 11g
  • FC-5120 - Fixed an issue around configuring of JKS keystores in 12c FMW environment. Now, MyST configures JKS keystores correctly in 12c FMW environments to support OWSM security configuration. JKS keystores are available within the Enterprise Manager control, and can be selected when configuring OWSM security to support signing and encrypting.

Known Issues

  • There is an issue with data migration of artifacts in this release. If using release management, it is recommended to avoid this release in favour of the 5.9.1.1 release or a 6.0.1+ release.

MyST Studio 5.9.0

New Features

  • FC-4631 - Application Blueprint editor has been revamped to allow for toggling between revisions of a given version
  • FC-4769 - Application Blueprints marked as FINAL now show the build numbers of given artifacts
  • FC-4836 - Release Pipelines can now be displayed in a list view
  • FC-5044 - Stream Model now has the ability to reset all properties to the default values
  • FC-5078 - Stream Model allows reset of individual properties to defaults. This field only shows when default properties are overriden so can be used as a visual indication for showing default properties that have changed.
  • FC-5034 - Provisioning of B2B 12.2.1.3.0 is now supported by MyST

Improvements

  • FC-4892 - Artifact metadata is now version-controlled against each artifact build
  • FC-5017 - Default tags can now be set for the AWS Infrastructure Provider
  • FC-4877 - Added support for setting the Coherence Cluster listener address
  • FC-4821 - Added support for setting the Coherence Cluster target
  • FC-5088 - Added support for setting coherence-port and coherence-log-basepath for 11g platforms
  • FC-5089 - Added support for setting java tuning parameter for managed servers including weblogic-stdout-basepath, heap-dump-basepath, verbose-log-basepath

Bug Fixes

  • FC-4826 - Fixed an issue where an empty popup menu was being shown in the release pipeline
  • FC-5107 - Fixed an issue where OBIEE 12c with standalone admin server provisions with an incorrect number of system component instances.
  • FC-4829 - Fixed a NPE that occurred when release pipeline promotion scheme was not selected
  • FC-4975 - Unsorted artifacts in an application blueprint are now sorted according to the default rules
  • FC-5102 - Resolved an issue where cleanup on remote hosts was failing when SSH keys were used
  • FC-5091 - Fixed an issue where stream model was failing on older browsers
  • FC-5105 - Fixed an issue with BAM provisioning on a cluster for 12c

Known Issues

  • There is an issue with data migration of artifacts in this release. If using release management, it is recommended to avoid this release in favour of the 5.9.1.1 release or a 6.0.1+ release.

MyST Studio 5.8.8

New Features

  • FC-5032 - MyST Studio has been certified for OTD 12.2.1.3.0 in a standalone (non-database) configuration.

Bug Fixes

  • FC-4933 - Bug fix: Fixed an issue where OSB session is getting discard on deployment failure. This feature can be overridden by adding property in global variables by the name “discard.osb.session” and value “true/false”.
  • FC-5092 - Bug fix: Fixed configure-wcc runtime error and fixed intradoc.cfg not updating on a managed server collocated with an adminserver

MyST Studio 5.8.7

Improvements

  • FC-5067 - While activating release pipeline, the validation process now shows Application Blueprint Name apart from ID, as part of the validation failed error message

Bug Fixes

  • FC-5081 - Fixed an issue where Release Pipeline was raising NullPointerException when attempting to deploy an Application Blueprint Revision whose parent Application Blueprint Version is now retired.
  • FC-5084 - Bug fix: WCC 12c provisioning on environments with a standalone admin server fails when processing wcc_servern_intradoc.cfg which does not exist.
  • FC-5050 - Fixed an issue where deployment of BAM artifacts were failing

MyST Studio 5.8.6

New Features

  • FC-4977 - ODI and OEDQ 12.2.1.3.0 configurations can now be created in MyST Studio. Software installation and domain creation is supported.
  • FC-4752 - WCC, WCC UI and IBR 12.2.1.3.0 configurations can now be created in MyST Studio. Software installation and domain creation is supported.

Improvements

  • FC-4881 - Improvement: Now MyST will provide an option to disable version conflict validation for a Release Pipeline
  • FC-5039 - Added 12.2.1.3.0 support for MyST Build Extensions

Bug Fixes

  • FC-5015 - Bug fix: Fixed issue where the SSH private keys could be accessed through the file system and the support artifact, thus leading to a security vulnerability
  • FC-4858 - Bug fix: Fixed a synchronization issue around Stream Model Properties
  • FC-4891 - Bug Fix: Fixed an issue due to which failed stream revisions from previous stage were appearing as available for deployment in current stage. It has been ensured if a stream revision fails to deploy at 1st stage, it won’t appear in the 2nd stage as a valid deployment candidate.
  • FC-5021 - Fixed an regression originally caused by fix

MyST Studio 5.8.5

Bug Fixes

  • FC-5037 - Bug fix: Fixed an issue due to which MyST was throwing exception while deploying an artifact due to referencing a property which was used by a previously retired artifact
  • FC-4889 - Bug fix: Fixed an issue due to which Release Pipeline would stay locked surviving a server restart. Due to this issue, if user inactivates a release pipeline, while it’s processing is still in progress, and also restarts MyST Application docker container, when Application comes back, the release pipeline stays locked showing “Execution in progress” which is not happening in reality.
  • FC-5022 - Bug fix: Fixed issue where the custom RCU component, WLSDSTORE is not cleaned up properly when the RCU schema prefix has been provided in lower case
  • FC-5014 - Bug fix: Fixed issue where multiple authentication providers could not be configured for a domain
  • FC-5007 - Bug fix: Fixed issue where the WLSDStore data source was not being targeted to the Admin Server for FMW version 12.2.1.3.0

MyST Studio 5.8.4

New Features

  • FC-4986 - OBIEE 12.2.1.3.0 configurations are now supported in MyST Studio.

Bug Fixes

  • FC-5018 - Bug fix: Fixed issue where application deployments started failing since 5.8.2
  • FC-5000 - Bug fix: Fixed an issue with the script used for doing offline upgrade of MyST to honour versions properly.
  • FC-5008 - Bug fix: Fixed issue where users were not able to trigger post-deployment actions and view logs despite having the permissions to do so.
  • FC-5021 - Bug fix: Fixed issue where the coherence cluster listen port is failing since version 5.8.3 for FMW version 12.1.3.0
  • FC-5029 - Bug fix: Fixed an issue due to which PKI credential mapper was not getting introspected

MyST Studio 5.8.3

New Features

  • FC-4976 - MyST now supports provisioning and configuration of WebTier 12.2.1.3.0

Bug Fixes

  • FC-5001 - Bug fix: Fixed issue where additional servers were not getting properly cleaned up when multiple products such as ESS and OSB were targeted to the same managed server.
  • FC-4973 - Bug fix: Addressed an issue introduced by 5.8.2 for customers that use the feature for running custom SQL pre or post RCU.
  • FC-4990 - Bug fix: Fixed issue where users were being mislead by the rollback message shown during update. Changed the message to indicate that rollback may not be possible under certain scenarios.
  • FC-4798 - Bug fix: Fixed issue where the coherence listen port was not being applied for OFMW versions 12c and above.
  • FC-4972 - Bug fix: Fixed an issue where the supervisor-password and work-repository-password were not auto-computed for Oracle Data Integrator (ODI) 12c

MyST Studio 5.8.2

Improvements

  • FC-4927 - MyST now allows one to control the exact lifecycle phase during which system artifacts (those defined as part of the platform) are deployed as part of provisioning.

Bug Fixes

  • FC-4875 - Bug fix: Fixed issued where for version 12.2.1.3, the WLSSchemaDataSource was not getting auto-computed for all product combinations
  • FC-4957 - Bug fix: Fixed issue where the MyST support artifacts could not be downloaded when the web console was accessed through an SSL port
  • FC-4930 - Bug fix: Fixed an issue due to which some configuration parameters such as ‘config-backup-enabled’, ‘archive-configuration-count’ and ‘configuration-audit-type’ were getting set incorrectly during platform introspection
  • FC-4961 - Bug fix: Introspection is improved for 11g environment that has the 11.1.1.9 patch applied

MyST Studio 5.8.1

Improvements

  • FC-4861 - Quite a few bug fixes and enhancements around the platform introspection capability in order to support the complete set of configuration properties supported by MyST
  • FC-4865 - Fixed regression and brought back older version of Stream Model editor, to stay side by side of the new Bulk Update editor
  • FC-4862 - MyST now supports setting of the deployed version for WebLogic shared libraries by allowing the libSpecVersion and libImplVersion parameters to be specified in the artifact metadata

Bug Fixes

  • FC-4890 - MyST now allows one to re-target the Admin Server component on to another compute group and node to fix issues with topologies but does not do any proactive validation, hence is left to the user’s discretion
  • FC-4823 - Bug Fix: Fixed an issue, due to which Platform Blueprint Version could not be deleted, even when behavior is set to NONE, at Stream level
  • FC-4889 - Bug fix: Fixed an issue due to which Release Pipeline would stay locked surviving a server restart. Due to this issue, if user inactivates a release pipeline, while it’s processing is still in progress, and also restarts MyST Application docker container, when Application comes back, the release pipeline stays locked showing “Execution in progress” which is not happening in reality.
  • FC-4887 - Bug Fix: Fixed issue where the license details do not show up in the footer on a few screens
  • FC-4834 - Bug Fix: Fixed issue where the SOA EJB timeouts were not being correctly applied in those clustered environments where the file system for hosting the soa-infra deployment plans were not hosted on a shared file system
  • FC-4872 - Bug Fix: Fixed a bug due to which ‘sca.composite.overwrite’ property is not being taken into account while MyST deploys SCA artifact in version 5.8.0
  • FC-4873 - Bug Fix: Fixed issue where SOA extensions were failing to deploy to multi-node environments which use SSH keys for authentication

MyST Studio 5.8.0

New Features

  • FC-4548 - MyST now deploys artifacts following the sequence in which they are configured inside Application Blueprint Version. Note, this mechanism makes deployment within a session for all artifacts, wherever found necessary.
  • FC-4818 - MyST now supports provisioning of SOA, OSB, ESS, BAM, WSM & BPM for OFMW version 12.2.1.3.0

Improvements

  • FC-4840 - MyST now allows role based access control to be configured for triggering post deployment actions for a release pipeline stage.
  • FC-4859 - MyST now allows one to override the deployment names for Java EE EARs, WARs and JARs through the ‘j2ee.name’ metadata property. Also, all of them can now deployed as shared libraries or applications based on the ‘library’ metadata flag
  • FC-4813 - For all application deployments, MyST now allows a consistent format ‘(EMBEDDED)/' to be used while specifying the MyST configuration plan
  • FC-4825 - During artifact property introspection, the MyST Jenkins plugin now ignores those properties which are escaped using a double dollar (e.g. ${ignoreme})
  • FC-4832 - MyST now allows one to escape property values within the MyST model itself using double dollars, (e.g. ‘key=${retainme}’)

Bug Fixes

  • FC-4853 - Bug Fix: Fixed an issue due to which MyST was not persisting new property of an artifact from Stream Model UI
  • FC-4857 - Bug Fix: Fixed an issue due to which MyST was not allowing to use default value of a property in Stream Model UI
  • FC-4860 - Bug Fix: Fixed an issue to support property introspection of OWSM policy and J2EE JAR artifacts
  • FC-4842 - Bug Fix: Fixed issue where setting a WebLogic cluster target explicitly for UMS configuration was failing.
  • FC-4850 - Bug Fix: MyST does not try to set the deployment order for shared libraries and also properly cleans up the edit session in case of deployment failures
  • FC-4847 - Bug Fix: Fixed an issue where MyST was re-deploying JCA adapters even when their configuration has not been changed.

MyST Studio 5.7.3

Improvements

  • FC-4751 - Improved user interface performance while editing release pipelines.

Bug Fixes

  • FC-4819 - Bug fix: Fixed issue where the Jenkins plugin stopped introspecting properties since 5.6.2.0 if running on a slave node.
  • FC-4812 - Bug fix: Fixed issue where under some conditions, wrong metadata properties show up on the user interface while clicking on an artifact in the list view.
  • FC-4779 - Bug fix: Fixed issue where, for LDAP authentication providers, the ‘IgnoreDuplicateMembership’ flag was not getting set correctly.

MyST Studio 5.7.2

Bug Fixes

  • FC-4814 - Bug fix: Fixed an edge case data migration issue in release tags which could affect versions 5.7.0 and 5.7.1
  • FC-4797 - Bug fix: Fixed issue where the platform blueprint / model configuration broke if the port for the default coherence cluster was changed.

MyST Studio 5.7.1

New Features

  • FC-4541 - MyST now allow users to add properties inside properties registry & stream model in bulk.
  • FC-4539 - MyST now allows provisioning of fresh Platform Instance based on release tags of an existing Platform Blueprint Version.

Improvements

  • FC-4748 - MyST Jenkins Plugin now raises error if type of an already registered artifacts is attempted to be changed.
  • FC-4637 - MyST now allows redeployment of applications by anyone irrespective of their role for those release pipeline stages which have the scheme set to ‘Automatic’.
  • FC-4476 - One can now escape variable substitutions inside configuration files by using an extra $ sign. So to retain a text such as ${var}, one should use ${var}.
  • FC-4529 - The MyST Configuration Plan now allows one to remove elements from XML files based on XPath search expressions by specifying the value to be replaced as ‘REMOVE’.
  • FC-4672 - MyST now has better support while introspecting properties for MDS artifacts.

Bug Fixes

  • FC-4750 - Bug fix: Fixed issue with invalid variable references in the ‘install-fmw.sh’ script which is shipped along with the MyST installer.
  • FC-4780 - Bug fix: Fixed issue where deployment of artifacts stopped working for CLI customers who are not using Maven.
  • FC-4747 - Bug fix: Fixed issue where resources were not being properly cleaned up when more than one product are targeted to the same cluster.
  • FC-4791 - Bug fix: Fixed regression (which resurfaced since 5.6.1.0) where the application blueprint description was only allowing 255 characters instead of the expected number of 1000.
  • FC-4739 - Bug fix: Fixed issue with respect to provisioning of WebCenter 12c components.
  • FC-4596 - Bug fix: Fixed the issue where MyST was failing to invoke Post Deployment Job on Jenkins CI server, when CSRF is enabled.
  • FC-4796 - Hot fix: Fixed regression in 5.7.0 where action history was showing up full payload text instead of appropriate text

MyST Studio 5.6.6

Improvements

  • FC-4745 - MyST now loads the Application Blueprint user interface significantly faster than it used to do.

Bug Fixes

  • FC-4771 - Bug fix: Fixed issue where release pipeline creation fails sometimes with a NullPointerException.

MyST Studio 5.6.5

New Features

  • FC-4580 - MyST now allows artifact properties to be marked as nullable in Property Registry and therefore ensures that activities like commit, approval, and deployment happen seamlessly, even when the property has a null value

Improvements

  • FC-4633 - MyST splash screen image has been updated

Bug Fixes

  • FC-4759 - Bug fix: Fixed issue where SSH connectivity was broken in version 5.6.4 if the Java version used by the MyST agent is 1.6.x
  • FC-4592 - Bug fix: Fixed issue where the MyST license could not be uploaded in a ‘tar.gz’ format
  • FC-4696 - Bug fix: Fixed issue where MyST Jenkins Plugin was throwing error while attempting to introspect SOA Extension artifacts.
  • FC-4502 - Bug fix: Fixed issues where the deployed artifacts were being shown incorrectly under certain circumstances against the Platform Instance in the Release Pipeline dashboard

MyST Studio 5.6.4

New Features

  • FC-4503 - MyST now allows administrators to compare artifact property values between platform instances.

Bug Fixes

  • FC-4712 - Bug fix: Fixed issue where SSH connectivity to Solaris based compute nodes stopped working since 5.6.2.0.

MyST Studio 5.6.3

New Features

  • FC-4426 - MyST now supports provisioning of Oracle Data Integrator - 12.2.1.2.6

Improvements

  • FC-4591 - MyST now allows administrators to renew the license at any point of time from the user interface, even before it actually expires.
  • FC-4673 - MyST Jenkins Plugin now introspects properties considering file names in case insensitive fashion

Bug Fixes

  • FC-4675 - Bug fix: Fixed issue where Oracle Business Intelligence Enterprise Edition (OBIEE) was not being provisioned successfully.
  • FC-4685 - Bug fix: Fixed issue where applications and shared libraries were getting deployed with auto-generated IDs instead of the actual names

MyST Studio 5.6.2.0

New Features

  • FC-4463 - MyST now allows publishing of releases (which marks application blueprint versions and platform blueprint versions as FINAL) once a stream deployment has made its way up to the last stage in a release pipeline

Improvements

  • FC-4431 - The Jenkins plugin now introspects only those properties which are supported for customization by MyST during artifact deployment instead of scanning all .xml and .properties files
  • FC-4626 - For composite deployments MyST will no longer fail deployments stating that ‘they already exist’ when the ‘sca.composite.overwrite’ flag is set to ‘false’
  • FC-4590 - For JCA adapters, MyST now allows the transaction support parameter to be configured on a per connection instance level as well in addition to the connection factory level
  • FC-4589 - MyST now supports Oracle Unified Directory as an Authentication Provider (Use ‘OUD’ as the provider type to configure it).
  • FC-3999 - MyST now allows users to trigger the post-deployment job (if configured) for the last successfully completed deployment to a stage within a release pipeline
  • FC-3225 - MyST now applies transaction timeouts to most of the BPM EJBs as well (see documentation for exact beans supported).
  • FC-4297 - MyST now applies EJB timeouts to the CompositeMetaDataServiceBean and the BPELAuditTrailBean beans as well.
  • FC-4573 - MyST now supports the ‘hmac-sha2-512’ and ‘hmac-sha2-256’ MACs (Message Authentication Codes) while establishing SSH connections to remote compute nodes.

Bug Fixes

  • FC-4632 - Bug fix: Fixed issue where MyST was setting both the listen port and the public port of the Network Access Points to the same value as that of the listen port
  • FC-4604 - Bug fix: Fixed issue where the option to view the ‘Dry Run’ report does not appear even if the dry run completed successfully.
  • FC-4599 - Bug fix: Fixed issue where the ‘pull.sh’ provided as part of the MyST installer does not work for Docker version 17.06
  • FC-4581 - Bug fix: Fixed issue where adapter deployment plans are persisted even they fail validation resulting in the adapter going into a state where no further changes can be made without fixing the plan files manually.

MyST Studio 5.6.1.2

Improvements

  • FC-4416 - MyST now loads the platform model / instance list and detail screens significantly faster than it used to do.

Bug Fixes

  • FC-4543 - Bug fix: Fixed issue where the release pipeline was getting broken in some cases by making validations more robust.

MyST Studio 5.6.1.1

New Features

  • FC-4151 - System administrators can now apply / renew the MyST license from the console itself by uploading a valid license archive.

Improvements

  • FC-4348 - While reprovisioning platform instances, instead of automatically deploying previously deployed artifacts, MyST now lets the user control that behaviour from the user interface. Also, this fixes a bug present in 5.5.0.0 and above where MyST would not be able to deploy artifacts successfully on re-provision.
  • FC-4527 - Additional settings for LDAP based authentication providers can now be configured in the platform blueprint / model.
  • FC-4526 - Extended Logging Format fields can now be specified for WebLogic servers in the platform blueprint / model configuration.
  • FC-4525 - Log filters can now be configured and associated with WebLogic servers in the platform blueprint / model configuration.
  • FC-4461 - Configuration backup settings can now be specified against the Domain within the blueprint / model editor.
  • FC-4453 - MyST now supports out-of-the-box configuration for JMS Thresholds and Quotas.
  • FC-4452 - MyST now supports out-of-the-box configuration support for Foreign JMS Servers.
  • FC-4389 - MyST now supports configuration of network connection filters so that network level access can be controlled.
  • FC-3041 - The WebLogic Protocol Maximum Message Size can now be specified in the platform blueprint / model configuration.
  • FC-2305 - JMS Destination configuration now supports the TimeToLive parameter out-of-the-box.
  • FC-2240 - JDBC DataSource configuration now supports the StatementCacheSize parameter.
  • FC-2238 - WebLogic server configuration now supports the parameter ClientCertProxyEnabled out of the box.
  • FC-1985 - PKI based Credential Maps can now be configured in the platform blueprint / model configuration.
  • FC-4026 - The configuration drift and dry run reports can now be seen for historic platform actions as well along with the execution log.
  • FC-4437 - All modal dialogs can now be closed easily by using the newly provided ‘x’ button on the top right corner in addition to the existing ‘Close’ buttons.
  • FC-4009 - One can no longer delete streams and stages from release pipelines if corresponding deployment revisions have been generated against them.
  • FC-3497 - MyST now paginates the list of versions / revisions of a platform model in its summary view.
  • FC-4471 - MyST now allows 4000 characters to be entered for the application blueprint description which would enable a user to verbosely describe it.
  • NOTE: Introspection for all the above MyST configuration extensions are not yet supported and would be implemented shortly as part of future releases.

Bug Fixes

  • FC-4462 - Bug fix: Fixed issue where MyST was showing only 50 items on many screens even though more existed.
  • FC-4232 - Bug fix: Fix issue where MyST update actions from CLI had broken by ensuring that MyST will update to the latest committed revision of the current version in case the revision information is not set while running the action. Also provided the option to specify the exact version and revision to update to using the ‘update.version’ property.
  • FC-4460 - Bug fix: Fixed issue where Java shared libraries were being deployed as applications instead of libraries when initiated from MyST Studio.
  • FC-4209 - Bug fix: Fixed issue when wrong artifacts were getting deployed as a result of configuration overlap if more than one artifact inside an application blueprint share the same Maven Artifact ID.
  • FC-4422 - Bug fix: Fixed an issue where under certain conditions, duplicate resources were being generated inside the platform blueprint / model configuration.
  • FC-3437 - Bug fix: Unsupported MyST extensions have now been removed from the blueprint / model configuration.
  • FC-1866 - Bug fix: Fixed issue where the ‘weblogic-plugin-enabled’ attribute was not applied to the domain even if set in the configuration.
  • FC-4522 - Bug fix: Fixed issue where artifacts did not get downloaded due to missing Maven configuration when MyST CLI is used to manage MyST Studio.
  • FC-4504 - Bug fix: Fixed issue where clicking on ‘Cancel’ on the Application Blueprint detail screen broke the user interface under certain conditions.

MyST Studio 5.6.0.3

Improvements

  • FC-4472 - MyST artifact download is no longer dependent on WLST, thus enabling support for non-WebLogic deployments.

MyST Studio 5.6.0.2

Bug Fixes

  • FC-4475 - Bug fix: Fixed issue which caused a blueprint or model to be unable to be opened if application deployment for wsm-pm had no name set.

MyST Studio 5.6.0.1

Bug Fixes

  • FC-4413 - Bug fix: Fixed issue where some blueprints could not be upgraded due to missing options in the hard-coded version list. Changed this to choose the versions based on the product catalog definition.
  • FC-4420 - Bug fix: Fixed issue where the blueprint configuration broke if the user provided multiple source files for any product.

MyST Studio 5.6.0.0

New Features

  • FC-4415 - MyST now allows one to rollback an SQL change by providing a compensation script and indicating the intent of rolling back through a flag.

Improvements

  • FC-4417 - The restriction on deployment types has now been removed so that custom artifact packaging types such as ‘pol’ do not fail validation during deployment.
  • FC-4383 - The execution log dialog can now be maximized to make effective use of real estate where the user wants.
  • FC-3641 - MyST now clips potential long names on screens to show a limited number of characters. The entire text is now shown on hover as a tooltip.
  • FC-2527 - MyST now tries to create the agent installation directory (including missing parent directories) before installing the agent on the remote nodes.
  • FC-4382 - MyST now shows a default placeholder value for ONS nodes in the platform model wizard to guide the user towards entering a proper value for it.

Bug Fixes

  • FC-4396 - Bug fix: The release pipeline scheduled deployment times are now aware of the browser timezone and hence will deploy at the correct time even if the browser from where the request was made is in a different timezone from the server hosting MyST.
  • FC-4427 - Bug fix: MyST now checks for active artifacts before reporting duplicates while registering artifact builds without which previously deleted artifacts were being considered for validation at the time of build registration.
  • FC-4429 - Bug fix: Fixed bug where deployments were failing when the corresponding stream model has not been saved even once.

MyST Studio 5.5.2.2

Bug Fixes

  • FC-4418 - Hotfix: Fixed data migration issue when multiple platform models exist with same name

MyST Studio 5.5.2.1

New Features

  • FC-4370 - MyST now allows scheduling of release pipeline deployments for a future date / time. A previously scheduled deployment can be unscheduled as well if its execution time has not been reached yet.

Improvements

  • FC-4377 - Properties starting with ‘core.’ are no longer introspected by the MyST Jenkins Plugin so that conflicts can be avoided against the platform properties.
  • FC-4343 - MyST now allows the user to mark properties in the artifact property registry as encrypted (passwords etc.) and if so, masks the artifact property values on the UI and persists them in encrypted form as well
  • FC-4315 - For property keys containing the word ‘password’, MyST now automatically marks them as encrypted while registering them in the artifact property registry.
  • FC-4342 - It is now possible to override the default artifact packaging type which is auto-discovered by MyST using the POM property, ‘artifact.repository.type’.
  • FC-4387 - MyST now prints a deployment summary at the end of each deploy log listing the exact artifact builds that were deployed and also those that were undeployed.
  • FC-4381 - The Application Model CSV export now contains the Environment Type name as well for easier correlation while exporting / importing data into MyST.
  • FC-4375 - One can now bypass introspection of properties at the Job level while using the MyST Jenkins plugin. By default, the behaviour is to introspect the artifact properties and report to MyST.
  • FC-4309 - The application blueprint association with platform blueprints has been deprecated from the UI as it has no relevance any more.
  • FC-4345 - The MyST Jenkins plugin now has the ability perform a dry run whereby it will show the JSON payload that will be posted to MyST but will not actually send it, thereby allowing the user to validate the Job configuration without affecting the MyST instance.
  • FC-3970 - WebLogic resources such as File Stores and JDBC Data Sources can now be created without targeting them to any servers or clusters.
  • FC-4157 - MyST now captures the user who is committing configuration changes to platform blueprints and models in addition to the commit message.
  • FC-4349 - One can now commit platform blueprints and models from the list and summary screens itself without going into the detailed configuration view.
  • FC-3717 - MyST now validates if all products are already part of the blueprint or not before allowing to add more.

Bug Fixes

  • FC-4386 - Hotfix: Fixed a regression whereby MyST custom actions stopped working as of 5.5.0.0.
  • FC-4376 - Bug fix: Platform Blueprint versions are now ordered semantically based on the version numbers rather than in lexical order.
  • FC-4380 - Bug fix: For older configuration based on Gridlink data sources, the RCU Runtime URL is now based on the normal URL when the Host parameter is not set in order to ensure backward compatibility of configuration

MyST Studio 5.5.1.1

Bug Fixes

  • FC-4352 - Hotfix - Gridlink URL changes had broken the Platform Model Wizard in 5.5.1.0
  • FC-4353 - Hotfix - Fixed data migration issue for artifacts introduced in 5.5.0.0

MyST Studio 5.5.1.0

Improvements

  • FC-4169 - MyST now prompts the user for the Database Host, Port and Service Name rather than requiring to enter the complete URL
  • FC-4179 - While reverse registering artifacts, the MyST Jenkins plugin now raises a ‘Conflict Detected’ exception if a duplicate build is posted to the target MyST Studio instance. (A very likely cause of this would be a missing step in the Job to bump the artifact version)
  • FC-4369 - While reverse registering artifacts, the MyST Jenkins Plugin now considers the MyST Config Plan by default when introspecting artifact properties
  • FC-4324 - All modal dialogs in the MyST user interface can now be maximized to occupy full screen width and height so that overflowing content can be easily visualized

Bug Fixes

  • FC-4169 - Bug fix: For RAC databases, MyST now computes the correct DataSource URLs when the type is set to GridLink

MyST Studio 5.5.0.0

New Features

  • FC-4277 - The MyST Plugin for Jenkins has added support for introspecting property references within the source code to simplify deploy-time customisation.
  • FC-4279 - There is now an Artifact Property Registry which shows introspected properties and the Artifacts which reference them as well as allowing the definition of meaningful descriptions and defaults values
  • FC-4292 - Properties can be referenced by multiple artifacts so that if the property changes it will apply to all Artifacts which reference that property.
  • FC-4291 - MyST will automatically determine which properties need to be defined based on the artifacts in a given deployment. This will generate a Stage Model which can be updated with the environment-specific values for deploy-time
  • FC-4282 - The Stage Model is persisted at the platform instance-level so you only need to enter the values for the first deployment and when they need to change
  • FC-4290 - MyST will show the exact Artifact version and build number in the deploy-time prompt for the Approver and Deployer
  • FC-4281 - A CSV file of Application Models grouped by Application Blueprint Versions can be exported through the API
  • FC-4276 - There is now a read-only view of all properties associated with a Platform Instance
  • FC-4294 - It is now possible to easily change the version of a single artifact once even when it is listed within multiple application blueprints
  • FC-4286 - Users can be granted�Approver�and�Deployer�role permissions per Stage in a Release Pipelines
  • FC-4269 - The Approver and Deployer�roles�integrate seamlessly�with the existing Role Based Access Control framework
  • FC-4260 - Role Based Access Control for�Application Release Automation�including Release Pipelines, Pipeline Templates, Artifacts and Application Blueprints�
  • FC-4261 - 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
  • FC-4262 - 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.
  • FC-4272 - Comprehensive troubleshooting information�by capturing the complete error details in the audit log for all failed requests
  • FC-4273 - Drill down on each event�to see low-level HTTP interactions for complete traceability
  • FC-4273 - The MyST installer now comes with options to install a pre-configured MyST Build Server and MyST Artifact Repository to significantly reduce the installation effort especially when an existing CI server or Artifact Repository is not already available within an organisation
  • FC-4273 - MyST now comes with an installation option to automatically setup a CI server to support automated Oracle Middleware builds using Maven

Improvements

  • FC-4284 - MyST verifies that two identical versions of the same Artifact do not exist across Release Pipelines that have stages pointing to the same platform instance
  • FC-4259 - New�Intuitive User Experience�for managing role permissions
  • FC-4263 - Simpler to�requesting the necessary grants�due to improvements to the authorization failure message in the case of insufficient permissions
  • FC-4264 - 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.
  • FC-4265 - Removed Obsolete Role Permissions�such as the ability to create and delete Continuous Delivery Profiles
  • FC-4266 - Workspaces �Application Release Automation resource types that can be associated to a workspace are now shown in thee workspace list and detail views
  • FC-4271 - Complete audit of all events�including failed events irrespective of whether it was due to a data retrieval or a manipulation.�
  • FC-4270 - Authorised users can�see which user performed which action�including each login and logout operation
  • FC-4274 - Search filters for tracking specific audit types�such as event status, resources type and action type to assist with log analysis
  • FC-4274 - MyST Studio and associated components are now configured to automatically restart on system boot

MyST Studio 5.4.2.1

Bug Fixes

  • FC-4203 - Fixed an issue that was impacting introspection of 11.1.1.7 and 11.1.1.6 domains

MyST Studio 5.4.2.0

Improvements

  • FC-4172 - Multiple role expressions can now �be assigned against a JMS module
  • FC-3537 - The default transaction support option can now be configured for JCA adapters�within the Model and Blueprint editor
  • FC-4124 - Improved�robustness of artifact conflict checks by incorporating the group:artifactId:version combination
  • FC-4047 - After an Application Blueprint (ABP)�is deleted, you can now�use the same ABP name again for a new ABP
  • FC-3719 - Validation errors are now raised if different builds of the same artifact are found in a release pipeline but targeted to the same platform instance even across multiple streams

Bug Fixes

  • FC-4156 - Fixed an issue when setting�Gridlink datasource�via the Platform Model wizard
  • FC-4176 - Fixed an issue introduced in 5.4.1.0 which caused the legacy deploy-offline and deploy-online actions to failed
  • FC-4166 - Fixed an issue where Jar library redeployment fails when there is no managed server (single admin server)

MyST Studio 5.4.1.0

New Features

  • FC-4089 - MyST CLI platforms in XML and Properties notation are now compatible with MyST Studio. Users�can easily push them to�MyST Studio and start performing automated operations against the�Platform Instances�such as�Deployment, 11g to 12c Upgrade, Cloud Migration, Patching, Configuration Management and Drift Detection.
  • FC-4089 - MyST CLI platforms in XML and Properties notation are now compatible with MyST Studio. Users�can easily push them to�MyST Studio and start performing automated operations against the�Platform Instances�such as�Deployment, 11g to 12c Upgrade, Cloud Migration, Patching, Configuration Management and Drift Detection.

Improvements

  • FC-3264 - For JAR deployments, the existing version is now removed and overwritten with the new one rather than two versions co-existing, as was the case before
  • FC-4046 - The�WebLogic�machine special character rules in MyST Studio have changed to only convert space characters to “_” and leave “.” and “-“ in tact. This allows for hostnames to be specified for WebLogic machines in the wizard without a need to later alter�these names in the subsequent editor�to be the original hostname.
  • FC-4001 - The WebLogic and SOA Catalogues�within MyST Studio now have options to choose 11.1.1.4.0 and 11.1.1.5.0.
  • FC-4032 - Deploy operation no longer has a mandatory dependency on a WebLogic server instance to allow for deployment of non-WebLogic artifacts.
  • FC-3322 - Node Manager Passphrase is masked on the file-system for added security.
  • FC-4113 - Improved robustness during WebLogic Introspection when JMS configuration settings have been tinkered with outside of the Admin Console - i.e. if a user removes a reference from JMS in config.xml but keeps the JMS module xml hanging around on the file system. Previously this behaviour caused an introspection failure, now, it just ignores the orphaned JMS module.
  • FC-3264 - For JAR deployments, the existing version is now removed and overwritten with the new one rather than two versions co-existing, as was the case before
  • FC-4046 - The�WebLogic�machine special character rules in MyST Studio have changed to only convert space characters to “_” and leave “.” and “-“ in tact. This allows for hostnames to be specified for WebLogic machines in the wizard without a need to later alter�these names in the subsequent editor�to be the original hostname.
  • FC-4001 - The WebLogic and SOA Catalogues�within MyST Studio now have options to choose 11.1.1.4.0 and 11.1.1.5.0.
  • FC-4032 - Deploy operation no longer has a mandatory dependency on a WebLogic server instance to allow for deployment of non-WebLogic artifacts.
  • FC-3322 - Node Manager Passphrase is masked on the file-system for added security.
  • FC-4113 - Improved robustness during WebLogic Introspection when JMS configuration settings have been tinkered with outside of the Admin Console - i.e. if a user removes a reference from JMS in config.xml but keeps the JMS module xml hanging around on the file system. Previously this behaviour caused an introspection failure, now, it just ignores the orphaned JMS module.

MyST Studio 5.4.0.0

New Features

  • FC-3565 - Platform Blueprints can now be created for use with SOA Cloud Service.
  • FC-3994 - A new utility is now available for migrating existing MyST CLI customers to MyST Studio based on their workspace configuration.

Improvements

  • FC-4017 - WebLogic introspection now supports earlier 11g versions and vanilla WebLogic clusters.
  • FC-2817 - MyST TestDrive now has self service automation for start, stop and terminate.
  • FC-4024 - Coherence clusters are now configurable through the user interface.
  • FC-3990 - The MyST Configuration Plan can now be configured to have different behaviour for unresolved variables encountered during substitution. We can now choose to ignore the replacement, fail it (default) or replace anyway with the variable itself.
  • FC-3988 - Update against an OAG model is now supported for OAG custom actions.
  • FC-4025 - If there is an issue with the dry run it shows a more specific error message.
  • FC-4023 - Relaxed the RCU database password validation for 12c and above.
  • FC-3801 - Added validation around post-deployment jobs and changed deployment options to exclude post-deployment job options if no post-deployment job is set.
  • FC-3873 - For SOA Composites, the MyST Jenkins plugin now reports back the ‘composite.revision’ metadata whenever the Maven property, ‘composite.revision’ is set.

Bug Fixes

  • FC-3571 - The release pipeline pre-refresh display now shows the correct revisions after a deployment has completed without the need to refresh.
  • FC-4029 - Fixed an issue to allow the Platform Model Name and Description to be modifiable in all cases.
  • FC-3979 - Fixed an issue where the upgrade blueprint wizard was hanging indefinitely.
  • FC-3714 - The SCA revision is now correctly applied to SOA composite deployments instead of defaulting to ‘1.0’.
  • FC-4048 - Fixed issue with Artifact property updates not being published to MyST Studio in some cases

MyST Studio 5.3.2.0

Improvements

  • MyST installer is available for download from the MyST web site to enable quick and easy installations to be done.
  • The majority of Release Pipeline updates can now be performed without needing to deactivate the Release Pipeline first.
  • MyST performs reachability checks for a given�platform instance before�triggering any update or deploy actions from a Release Pipeline.
  • Stages can be added to a new Release Pipeline without the need to�first create�a Release Pipeline Template.
  • Advanced SOA and BPM composite deploy-time customisation can now be supported through a MyST Configuration Plan.
  • MyST Studio generates a diagnostic artifact when a failure occurs which can be provided to support to assist with problem resolution. It is available for the last 5 failures for a platform instance.
  • MyST now prevents a user from saving a Blueprint or Model with validation errors and provides more meaningful error messages with a stack trace to facilitate easier analysis.
  • Application Roles can now be assigned to other Application Roles.
  • Improved hover text for platform status in the Release Pipeline Dashboard when no action has been taken such as a dry-run.
  • Improvements to the MFT introspection capability

Bug Fixes

  • Fixed an issue with MyST Jenkins plugin persisting MyST host and port values.
  • Fixed an issue related to JCA adapter�ID being�able to be defined incorrectly from the Blueprint editor.
  • Fixed an issue relating to Work Manager Max Threads not being correctly discovered during introspection.
  • Fixed an�issue with updating Release Pipelines�where�earlier removed Application Blueprints were resurfacing in some edge cases.
  • Fixes an issue with MFT and SOA having conflicting port values when present in the same domain, from 12.2.1.2.0 the default MFT port is different to SOA.

MyST Studio 5.3.1.0

Improvements

  • MyST now allows additional compute nodes to be added to a model after creation so that clusters can be expanded without needing to create a new model. This will take effect through re-provision of the model.
  • Users can disable values that are auto-computed by MyST. Most of the time a user would not want to do this but it can be useful for introspecting an existing environment without applying MyST’s recommended changes. To support this the option to delete / reset a property to its original value is now explicitly provided through a delete button while hovering over each property
  • The Action History for an instance can now be filtered based on ‘Default’ (all actions), ‘This Release pipeline’ (actions related to the current pipeline) and ‘Other Release pipeline(s)’ (actions related to pipelines other than the current one.)
  • Additional deploy-time properties were added for the ADF artifact type so that it now supports all of the properties that are supported by the Java EAR artifact type.
  • MyST supports applying atypical patches that mandate ORACLE_HOME to be set at Patch time.
  • Embedded deployment plans are supported for J2EE applications
  • MyST Configuration Plan is supported for SOA and BPM composites
  • Bamboo v5.x is supported as a Continuous Integration server in the MyST Studio Continuous Delivery Profile.
  • Nexus 2.x is supported as a Binary Repository Manager in the MyST Studio Continuous Delivery Profile.
  • MyST now restricts post-deployment job configuration/invocation for Jenkins only.

Bug Fixes

  • Bug fix: The user can no longer create a custom action having a whitespace in the name as it eventually causes the action to error out during execution.

MyST Studio 5.3.0.3

Bug Fixes

  • Bug fix: The release pipeline stopped working when the platform behaviour was set to None

MyST Studio 5.3.0.2

Bug Fixes

  • Bug fix: The Agent to Studio integration was broken in 5.3.0.0

MyST Studio 5.3.0.1

Bug Fixes

  • Bug fix: Update with dry run was broken since 5.2.0.0. It was doing an actual update instead of a dry run.

MyST Studio 5.3.0.0

New Features

  • It is now possible to retrigger post deployment job for a deployment which got “verification failed”
  • It has been ensured that if sequence of Application Blueprints belonging to Streams are altered, new stream revision is generated

Improvements

  • A much improved version of the user guide is now available and the inline help from MyST Studio also refers to content from it.
  • ISO-8601 date format is now supported, for build.start.time parameter (which is required during reverse registration)
  • MyST now fails fast and does not retry for a long time if the on-demand compute nodes are not reachable even though they have been provisioned
  • MyST now supports optionally specifying an IP address or hostname to bind to for HTTP and HTTPS communication. This allows multiple OHS instances to be configured on the same machine using identical port configuration without resource clashes.
  • REST API changes to the Platform resources which allows the consumer to tailor-make the data that they want using smart filters
  • Performance improvements while rendering the Platform Blueprint, Model and Instance screens
  • When the user clicks on any other component in the platform blueprint / model while he is in the process of editing an existing one, he is prompted to either save or cancel his changes so that he does not accidentally lose them
  • Improved the way the user selects versions and revisions for platform provisioning and updates
  • Application Blueprint Version UI has been refactored to efficiently interact with backend, thereby improving response time
  • Tuned information set, what Release Pipeline logs at INFO level

Bug Fixes

  • Bug fix: Fixed the issue of Release Pipeline UI hanging
  • Bug fix: Fixed the issue, that caused failure in discovering sql properties
  • Bug fix: For on-demand AWS infrastructure providers, MyST does not use the right credentials to connect to AWS if the first provided credentials were wrong. A restart is required for MyST to pick up the right set
  • Miscellaneous improvement around Deploy / Redeploy feature in Release Pipeline
  • Ensured that user is redirected to specific version of Application / Platform Blueprint when s/he clicks the hyperlinks corresponding to Application / Platform Blueprint (corresponding to stream) from Release Pipeline dashboard
  • Bug fix: Fixed the issue, which was causing discovery of wrong SCA revision
  • Bug fix: Fixed the issue, which was causing j2ee properties not getting discovered appropriately
  • Bug fix: Fixed the issue, which was causing artifacts not getting corrected marked as deployed / not deployed, as part of the payload that is passed to post deployment job
  • Bug fix: Fixed the issue that caused, failed deployment to change everything to successful but not do an actual deployment, when redeployment is attempted
  • Bug fix: Since 5.1.1.0, MyST was showing all resources to a non-admin user irrespective of the workspaces he belongs to

MyST Studio 5.2.1.0

New Features

  • MyST now has sudo-rule support for OHS provisioning as well as OSB, SCA, MDS and BAM deployments
  • MyST now raises validation error prior to deployment if it identifies that the stream (whose deployment is in question) consists of Application Blueprints referring to same version & build number of artifact(s)
  • One can now add products and compute groups to existing blueprints using simple UI dialogs

Improvements

  • Explicit redeployment (undeploy followed by deploy) is now supported for SOA Composites, MDS and J2EE artifacts
  • MyST reverse registration utility now accepts command line arguments
  • MyST now provides options for user to select if they want platform instance properties & / or application model properties to be sent as part of the json payload which is passed to the post deployment job
  • MyST now checks “Enabled” checkbox for post deployment job by default
  • Improved the way the user selects versions and revisions for platform provisioning and updates
  • MyST now aborts any incomplete post deployment execution, when server reboots
  • MyST now shows selected ABPs at the top while editing stream definition
  • Improved logs when artifact download from maven repository fails.
  • When a platform instance action is aborted or when it goes to state indeterminate due to a system restart, the platform instance now also goes into a state of ‘Indeterminate’ if the action is a Provision, Update or Terminate. The user has to then override the state of the instance to something concrete before he can perform further actions.
  • One can now change the one-to-many associations for components in the platform blueprint / model. e.g. change the products for a compute node, etc.
  • SQL artifacts now get executed as part of standard deployment
  • The hosts of an infrastructure provider are now sorted in alphabetical order and can be filtered as well.

Bug Fixes

  • Bug fix: The complete agent execution log was being lost when a platform instance action was aborted.
  • Fixed the issue of wrong build of an artifact getting deployed in case the artifact was deleted and re - registered
  • Bug fix: One can clear the value of the location field without the text box disappearing while defining custom actions
  • Bug fix: When a user is assigned the same role twice, an error was being thrown while doing subsequent role assignment.
  • MyST now ensures that no actions can be taken on the release pipeline when its execution is in progress
  • Fixed the issue such that post deployment job definition can be persisted separately, than the stream definition to which it belongs
  • Fixed an issue due to which, Release Pipeline was throwing exception, if one deactivates it first, edit the stream definition to remove one or more ABPs, and try to reactivate it again
  • Fixed issue where MyST hangs if there is no java on the target host in the PATH
  • Fixed an issue due to which “SR” would appear on build column of Release Pipeline when there is no stream revision available

MyST Studio 5.2.0.2

Improvements

  • MyST now prohibits deployment of ABPs that incorporate different versions of the same artifact that are in the same stream

MyST Studio 5.2.0.1

Bug Fixes

  • Bug fix: Post deployment job wasn’t propagating the deployed flag correctly to Jenkins

MyST Studio 5.2.0.0

New Features

  • One can now ear-mark certain environments to allow provisioning of draft configuration. (These environments cannot be made a part of a release pipeline though)�
  • MyST is now certified against OFMW 12.2.1.2.0 for the following components: SOA,OSB,BAM,BPM,B2B,WSM,MFT,ESS,ADF,BI,OBIEE,OTD,WLS,OHS
  • MyST supports sudo-rule for platform provisioning where one can specify a run-as-user assuming whose identity MyST will perform all actions after connecting as the agent user.

Improvements

  • One can now delete the current draft of a blueprint / model in case it has not been provisioned to any instance
  • The deployment is now marked as ‘Verification failed’ if the post-deployment job fails
  • It has been ensured that Platform Instance properties (with sensitive information masked) are passed as part of the payload that post deployment job receives
  • It has been ensured that post deployment job only triggers on a successful completion of a deployment
  • Application model data is now passed to post deployment job
  • It has been ensured that post deployment job executes only when at least one artifact gets deployed
  • One can now independently choose the blueprint and model revisions to provision / update to rather than having to choose the latest configuration for each�
  • One can now choose any revision of the blueprint / model to provision starting from where the instance is at to the latest
  • We now show the latest stream revision in the Build column as well

Bug Fixes

  • Bug fix: RCU prefix was generating rogue global variables if it has property references
  • Bug fix: Values for the timestamp fields were not being formatted properly in the CSV output
  • Bug fix: The Audit fields were not being shown for the Compute definition
  • Bug fix: The Yes / No options to restart nodes on a patch action no longer render in the drop-down
  • It has been ensured that list of values appearing in “Deployed Artifact” modal windows are paginated in right order
  • The action history now shows the revision numbers with the correct prefix for deployments

MyST Studio 5.1.1.3

Bug Fixes

  • Fixed: The correct version numbers are now being shown in the deployed artifacts report.

MyST Studio 5.1.1.2

Improvements

  • A stream in the release pipeline now supports Different versions of Platform Blueprints per stage.
  • Improvement on the deployment artifacts list rendering when names are too long.

Bug Fixes

  • Fixed: View Actions log sometimes doesn’t show the log contents.

MyST Studio 5.1.1.1

Improvements

  • Application model bulk edit is now supported
  • Application model data is now passed to post deployment job
  • One can now see the streaming of logs from the Action history dialog as well

Bug Fixes

  • Issue with MyST Studio getting frozen when user access Deployed Artifact Report has been resolved

MyST Studio 5.1.1.0

New Features

  • The user can now view the revision history of platform blueprints and models and start editing from an older revision if required
  • When an action is infinitely stuck, MyST now allows to abort the action as well as the remote process on a best-effort basis
  • The release pipeline now allows one to configure post-deployment CI jobs and executes them

Improvements

  • MyST now alerts the customer after log in in case the license is about to expire within 15 days so that he can take necessary measures for renewal if required.
  • MyST now supports provisioning SOA Suite and OSB into Solaris SPARC and x86_64 infrastructure
  • MyST now supports introspection OFMW environments running on Solaris SPARC and x86_64 infrastructure
  • For newly discovered hosts (which are not part of the infrastructure provider), the user can now change the host name after the introspection is complete before saving his configuration
  • The option to re-provision as part of update is deprecated and instead the option is available from the Actions menu itself
  • The actions available to be performed on an instance are now restricted based on the state of the instance
  • An instance update action no longer gets executed if the provisioning fails
  • General improvements and bug fixes for Release pipeline editing

Bug Fixes

  • Bug fix - In the Action history and control dialogs, the state of the model was being shown as Draft even when it was committed. This is fixed now.
  • Bug fix - When a blueprint / model has invalid references, MyST does a validation before saving the configuration to prevent it from getting corrupted.
  • All screens of MyST are now functional and render properly on Internet Explorer 11

MyST Studio 5.1.0.2

Improvements

  • Sequence of application blueprints (within a stream) is now captured and it governs the order in which application blueprints are deployed to target environment
  • It is now possible to distinguish between platform and application blueprints inside release pipeline view
  • It is now possible to navigate to platform and application blueprints from release pipeline view, by clicking on corresponding hyperlinks that opens up detail page (of platform & application blueprints) into a new window
  • You can now define in your Release Pipeline if platform updates should be skipped. This is useful if you want to use MyST for deployments only
  • SVN URL has been made to wrap in case it exceeds horizontal width of the artifact detail pane
  • Most of the tables and drop-downs are now sorted by the name of the entity in question
  • When performing the action Patch, we now show an explicit message so that the user is better informed on how to properly run it.
  • It is possible now to view the details of deployed artifacts in a given stage of a release pipeline / stream.
  • When configuring the MyST Studio Jenkins plugin, you can now save the settings even if MyST Studio is unreachable
  • MyST can now stream the execution log for actions that run against an instance, thereby giving the user a richer user experience.
  • MyST now allows one to explicitly indicate that he wants to update passwords while performing an Update action and if so, updates all passwords for the Platform Instance
  • Performance improvements while rendering Platform Models and running actions against Platform Instances
  • You can explicitly define a listen address for OHS

Bug Fixes

  • MyST now deploys MDS prior to Composites
  • Issue around having save button for third party artifacts has been fixed now
  • Fixed: Node Manager identity key store passphrases fail if there is a special character
  • Fixed: Dependent patches not rolled back in reverse order
  • Fixed: Issues related to some Workmanager mappings

MyST Studio 5.0.1.1

New Features

  • MyST Studio now supports Oracle BI Publisher 12.2.1
  • MyST Studio now supports managing Custom Actions (WLST and Jython Interpreters)

Improvements

  • Release Pipeline, Continuous Delivery Profile and Artifact usability improvements and fixes
  • You can now redeploy all artifacts against a Platform Instance. That’s useful in cases where you re-provision your platform.
  • You can now define in your Release Pipeline if platform updates should be skipped. This is useful if you want to use MyST for deployments only
  • Usability improvement: Properties under platform blueprint related to patching, which are not commonly used, are now shown only in the advanced view.
  • You can now define which order the Application Blueprints within a Stream will be deployed
  • AWS On-Demand provisioning now supports Mumbai, Ohio and Seoul Regions
  • MYST Studio installer provides clearer instructions on the post-install actions
  • SOA Extensions deployment are now supported for SOA 12.2.1
  • The MyST License details are now visible in MyST Studio
  • When configuring the MyST Studio Jenkins plugin, you can now save the settings even if MyST Studio is unreachable
  • MyST Studio Jenkins plugin now also supports building artifacts from a Jenkins slave
  • The MyST Jenkins plugin now resolves the Maven properties before reporting them to MyST Studio. You can now have property references such as ${project.artifactId}
  • Improvements on Weblogic Workmanager support

Bug Fixes

  • Fixed: Updating wsm-pm target used to cause a NullPointerException
  • Fixed: The NGINX routing rules was not redirecting HTTPS traffic for specific URL patterns
  • Fixed: In some circumstances MyST execution was hanging when the target nodes had Kerberos enabled

MyST Studio 5.0.0.3

Bug Fixes

  • Fixed: Issue when provisioning/updating an environment with Weblogic Mail Session

MyST Studio 5.0.0.2

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

MyST Studio 4.0.1.5

Improvements

  • Added support for Weblogic custom system policy

Bug Fixes

  • Bug fix: patch-domain action has fixes and improvements

MyST Studio 4.0.1.4

Bug Fixes

  • Bug fix: When JSSE is enabled MyST sets weblogic.security.SSL.minimumProtocolVersion property to TLSv1.0

MyST Studio 4.0.1.3

Bug Fixes

  • Bug fix: Fixed issue in the patch-domain action, which was introduced in 4.0.1.2

MyST Studio 4.0.1.2

Improvements

  • CD feature improvements related to third-party artifact registration

Bug Fixes

  • Bug fix: MyST now successfully configures multiple custom environment variables for a FMW domain in setUserOverrides.sh/cmd

MyST Studio 4.0.1.1

Improvements

  • Auditing feature improvements

Bug Fixes

  • Bug fix: Fixed issue where the dialog for creating a blueprint from a template was not opening due to a JavaScript issue

MyST Studio 4.0.1.0

New Features

  • MyST now audits changes and actions, providing reports available on the UI, as well as CSV export capability.
  • The Installation and associated RCU actions for OBIEE 12.2.1.1 are now supported.

Improvements

  • The end user can now see the post deployment job execution log along with the main execution log after deployment of an application blueprint revision.
  • If a password is a property reference, the reference gets shown in clear text rather than as ‘*****’
  • The end user can now skip the SCA 11g compilation phase during the build process.
  • The OTD listener is now part of the MyST platform lifecycle, supporting start/stop/terminate actions.
  • The Out of the box Derby database is not enabled as part of OSB 12c provisioning anymore.

Bug Fixes

  • Bug fix: Irrespective of the region chosen, when using Instance Profile as the authentication type, the US East region was being used for discovering resources.

MyST Studio 4.0.0.1

Bug Fixes

  • Bug fix: Third-party artifact registration stopped working after 4.0.0.0 was released
  • Bug fix: Promotion of application blueprint revisions stopped working after 4.0.0.0 was released

MyST Studio 4.0.0.0

New Features

  • Administrators can now override the status of a Platform Instance so they can manually reconcile and mark them according to the correct state
  • BPMN Mbeans can now be configured using MyST
  • For on-demand AWS infrastructure, one can now use the IAM role for authentication
  • RecurringScheduleConfig can now be configured through a MyST platform blueprint

Improvements

  • Additional JMS and Authentication Provider configuration parameters are available in the core model
  • Improvements in the way actions against an instance get executed concurrently
  • The properties popover now shows a textual description in addition to the reference expression
  • MyST Studio now supports retry of execution of successful latest deployment
  • For on-demand AWS infrastructure, MyST now allows one to specify whether or not the compute nodes need to be terminated in event of a failure during provisioning
  • MyST no longer shows stale platform instances which were associated with the workspaces
  • Actions pending for a platform instance can now be skipped from the UI
  • MySt now shows both the action history for an instance as well as all the pending (future) actions that have been lined up for it
  • Irrespective of however many actions are pending for an instance, a provision or a terminate action always takes precedence and skips the others which are pending
  • When MyST Studio crashes, the actions which are currently marked as in progress automatically move to the state of INDETERMINATE and the user can manually override the status of the instance to do the necessary reconcilliation
  • Validation errors inside the AMI section are now also indicated at the header level for the user to easily spot
  • For the on-demand AWS infrastructure provider, the Owner field is not relevant anymore and hence removed.
  • BAM and BPM routing rules for Oracle HTTP Server are now automatically computed by MyST Studio

Bug Fixes

  • Bug fix: If a property reference is made to the Host ID field of the Compute Node, the model view fails to render and renders in it becoming unusable
  • Bug fix: Made sure that browsers (IE 11 in particular) do not cache any data provided by the server
  • Bug fix: There was a bug which was throwing an error when creating a Blueprint with OTD 12.2.1.1.
  • Bug fix: Improved the performance while rendering the platform model list screen

MyST Studio 3.9.2.0

Improvements

  • Improvements to shutdown time for the WebLogic admin server for 12c products
  • The transaction recovery privilege can now be enabled for the SOAINFRA database as part of the RCU execution
  • MyST Studio can now successfully provision an OAG instance containing OAG Analytics
  • MyST Studio now supports execution of post deployment jobs, for ALL Application Blueprints which are affected by the build of an Artifact
  • MyST Studio can successfully provision a collocated OTD domain using WebLogic 12.2.1 with managed servers.
  • MyST Studio supports a new feature to view Application Blueprints in list / card layout. List layout provides search capability for each columns.

Bug Fixes

  • Bug fix: In Artifact UI even when number of builds are more than 15, it gets properly displayed now. A vertical scroll appears to accommodate rolling up / down the list
  • Bug fix: Fixed issue where the dialog for creating a blueprint from a template was not opening due to a JavaScript issue

MyST Studio 3.9.1.0

New Features

  • Ability to configure the WSM keystore
  • FMW version 12.2.1.1.0 is now supported by MyST Studio

Improvements

  • patch-domain now updates all servers in a platform and allows to customise the domain.home directory
  • Artifact build numbers are now numerically sorted in descending order
  • A user-friendly error message is displayed when deletion of application blueprints / application blueprint versions fail due to existence of cross-references to other entities
  • WLST security objects can now be automatically converted to myst-extension
  • Removed unnecessary targeting from mds-owsm for ESS
  • UI editor assistance is now available while constructing the post deployment job name using the pre-defined variables
  • The platform instance report view now shows JCA adapters, JMS configuration, Authentication providers and Startup / Shutdown classes
  • For Safari, the users are no longer presented with the Download option (as it does not work) and instead they can view the log and copy to clipboard using the icon provided
  • MyST now supports updating configuration via the ‘update’ action for OTD

Bug Fixes

  • Bug fix: When Exalogic was enabled in an MFT domain it was auto-computing SOA and OSB as products
  • Bug fix: The target URL for Java projects can now be stripped of the version when deployed through MyST Studio
  • Bug fix: Passwords are now hidden in dry run execution logs.
  • Bug fix: MyST now correctly provisions configurations using OHS 12.2.1.1.0
  • Bug fix: Start/Stop of OAG instances was not working in an Exalogic environment
  • Bug fix: Password fields were being shown in clear-text (even if encrypted) and the labels for the fields too were not being displayed properly
  • Bug fix: Deletion of an artifact having more than one version was failing

MyST Studio 3.9.0.3

Bug Fixes

  • Fixed an issue with passwords not hidden in dry run execution logs.

MyST Studio 3.9.0.2

New Features

  • Oracle Fusion Middleware (Integration) 12.2.1.1 is now supported (Preview).

MyST Studio 3.9.0.1

Improvements

  • OAG patches are now specified the same way as for OFMW products.

MyST Studio 3.9.0.0

New Features

  • B2B 12.1.3 and 12.2.1 are now supported in MyST Studio
  • OTD 12.2.1 installation is now supported

Improvements

  • The user can now change their own password in MyST Studio
  • If the admin server has JSSE Enabled specified as true, MyST now sets the correct JVM parameters
  • Exalogic Shared Deployment directory is aligned with EDG
  • We now prevent the user from clicking on the promote button multiple times

Bug Fixes

  • Bug fix: NGINX mappings to MyST Studio are correct now.

MyST Studio 3.8.2.3

Bug Fixes

  • Bug fix: RCU Post Create custom SQL couldnt be executed with the Sys password

MyST Studio 3.8.2.2

Improvements

  • Remote installation now performs a homogeneous installation of all products for 11g
  • Configuring Keystore Providers and Trusted SAML Issuers in a domain with SSL enabled is now supported

MyST Studio 3.8.2.1

Bug Fixes

  • Bug fix: In a Docker environment, the MyST license was not being picked up correctly though it was present in the right location

MyST Studio 3.8.2.0

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

MyST Studio 3.8.1.1

Improvements

  • Prerequisite patch IDs are now honoured by the update implementation
  • Patching during provisioning and re-provisioning happens in parallel.
  • Re-provisioning is significantly faster as it does not try to re-apply patches that already exist

MyST Studio 3.8.1.0

New Features

  • MyST now supports overriding the targeting of admin components in the platform model by either splitting to have a separate admin group & node or merging a standalone node into one of the other compute groups
  • OAG Patch 11g is now supported
  • You can now define multiple versions for Third Party artifacts
  • Source control details for SVN and GIT are now shown in the Artifact list view
  • MyST now allows DBAs to define pre and post SQL to be executed at schema creation-time during platform provisioning

Improvements

  • MyST now does default targeting for components in the platform blueprint wizard
  • MyST now allows to change the name and description of platform blueprints and models after they are created
  • MyST now allows to change the value of the auto-deploy flag for platform models after they are created
  • MyST now supports distribution of the JCA deployment plans to all nodes if the filesystem is not shared across hosts
  • MyST now generates IDs for all resources after sorting them in alphabetical order, thereby ensuring that relationship between resources don�t appear to be incorrect. e.g. Node 1 would now point to WebLogic machine 1 rather than 2 as was happening earlier
  • The popover for properties now auto-hides when one moves away. Also, there is now an option to copy the reference expression to clipboard by just clicking an icon besides the expression
  • MyST now supports the destroy action with a non-standard inventory location pointer file (identified via the oui.inventory.loc property)

Bug Fixes

  • Bug fix: Unable to view CDP with View permissions assigned to Role
  • Bug fix: Application Blueprint post job invocation wasn’t working in some circumstances.

MyST Studio 3.8.0.1

Improvements

  • BSU is supported now as part of platform update
  • While doing “Save As New” for Application Blueprint Version, MyST Studio now validates that the user has not provided existing version number as input

Bug Fixes

  • Bug fix: The platform update was always updating password, hence requiring a server restart even if the password was not changed
  • Bug fix: configure-jca was setting the password parameters in encrypted form rather than clear text
  • Bug fix: Even when the configuration plan was not getting applied, the deployment was marked as successful
  • Bug fix: The security action in 12c was failing if credentials maps are defined as part of the model

MyST Studio 3.8.0.0

New Features

  • ADF 12.2.1 is now supported in MyST Studio
  • Webcenter Portal 12.2.1 is now supported in MyST Studio
  • Application blueprint versioning is now supported
  • The MyST Studio Jenkins plugin is now available for download in the MyST website

Improvements

  • MyST Studio Jenkins plugin does not depend on Artifactory plugin anymore
  • The Jenkins versions in the Continuous Delivery Profile are now being expressed as major version, rather than minor versions
  • Improved the support for SOA tuning parameters
  • The MyST agent and MyST workspace directories on the target hosts can now be customised in MyST Studio. The temporary files are now being saved under the MyST temporary workspace, and are deleted when MyST agent completes its execution.

Bug Fixes

  • Bug fix: Fixed URL parsing when invoking SQL action using Oracle native SQLPlus client
  • Bug fix: Custom XPath deployment failed after deploying OWSM Policies
  • Bug fix: The RCU prefix is now converted to upper case. That fixes issues when MyST rcu drop action wasn’t dropping the database schemas for JMS database persistence

MyST Studio 3.7.2.0

New Features

  • MyST now supports Solaris 11 as a supported operating system for provisioning

Improvements

  • The global connection pool parameters are now part of the JCA model and need not be specified as custom properties
  • The version and feature toggles for the product are now packaged inside the binary itself
  • ADF is now supported as part of WLS vanilla cluster
  • UMS Configuration is now supported in 12c
  • Application Blueprint and artifacts can now be deleted, as long as they are not associated with other resources or grants

Bug Fixes

  • Bug fix: The global connection pool parameters were not supported in the new JCA implementation
  • Bug fix: Some of the properties were lost during actual provisioning when multiple instances of a JCA adapter was being configured
  • Bug fix: SOA partitions could not be created when SSL was enabled. The issue still exists but now partitions can be created when the plain listen port is enabled in addition to SSL
  • Bug fix: Running a dry run for JCA updates was sometimes leaving the plan files in an inconsistent state
  • Bug fix: All 11g environments started failing whiling starting the managed servers as part of the provisioning
  • Bug fix: Fixed an issue with the api key not being able to be copied in Firefox
  • Bug fix: Configuration plan for composites were not being set as part of the reverse registration

MyST Studio 3.7.1.0

New Features

  • MyST Studio now supports deployment of either third party libraries, or artifacts not built by the CI Server
  • MyST Studio supports now the deployment of Jar libraries, ADF, Application Configuration and third party libraries
  • MyST now supports provisioning WCP 12.2.1 domains

Improvements

  • Artifacts list now shows all the versions for the artifacts
  • RCU JMS/TLOG persistent component WLSDSTORE now supports honor-OMF
  • Label changes to improve usability of the MyST Studio Jenkins plugin
  • SCM URL improvements as part of the artifact registration. The details provided by the CI server represent the source of truth now
  • Environment type can now be deleted. Enabling an disabling environment types is no longer supported
  • JCA adapter configuration is now supported as part of platform update

Bug Fixes

  • Bug fix: Fixed issue that prevented to specify the J2EE deployment order
  • Bug fix: Fixed issue that was causing intermittent network communication issues between MyST Studio and MyST Agent

MyST Studio 3.7.0.0

New Features

  • CD Reverse Registration Preview for OSB, SOA, MDS 12.2.1, J2EE, Application configuration, OWSM Policy

MyST Studio 3.6.2.1

New Features

  • MyST Studio now supports OWSM Policies in 12c

MyST Studio 3.6.2.0

New Features

  • MyST Studio now supports the definition of WebLogic vanilla clusters and servers
  • EM Credential Maps in 12c are now supported

Improvements

  • Improvements to the data validation for update and provision change messages
  • MyST now is able to co-ordinate deployment of multiple application blueprints sequentially when an artifact is part of more than one blueprints

Bug Fixes

  • Bug fix: The topology diagram was not rendering if there were clusters without products on them
  • Bug fix: The topology diagram was not re-rendering when components were added / removed or renamed
  • Bug fix: The topology diagram was not scrollable when both the horizontal and vertical scroll bars were simultaneously visible
  • Bug fix: MyST Studio jenkins plugins was losing the API key in the Jenkins config, whenever there was an update in the config other than the API key itself.

MyST Studio 3.6.1.0

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

MyST Studio 3.6.0.0

New Features

  • Continuous Delivery: OSB artifact reverse registration initiated by the CI Server
  • Continuous Delivery: Plugin to integrate Jenkins with MyST Studio reverse artifact registration

Improvements

  • Changing the Oracle inventory loc file is now supported in MyST Studio
  • Oracle inventory now defaults to the standard /etc/oraInst.loc if not specified
  • All sensitive platform properties (passwords, passphrases, etc.) now use password fields to accept input
  • A workspace cannot be deleted if it has resources and all resources have to be associated with at least one workspace

Bug Fixes

  • Bug fix: All wizards used to hang when the user did not have permissions to create the underlying resource. The fix allows the user to cancel the wizard if there are access errors

MyST Studio 3.5.1.0

Improvements

  • Patches can be applied now as part of the platform update.
  • You can now specify Identity store details and additional Java arguments to the node manager

Bug Fixes

  • The platform instance record was getting upgraded to a higher version after an update even if the update fails

MyST Studio 3.5.0.1

Bug Fixes

  • Bug fix: Added mystsystemuser as an out of the box user which is used for API calls from MyST CLI

MyST Studio 3.5.0.0

New Features

  • MyST now supports SSL configuration for WebLogic, including custom identity and trust stores
  • MyST now supports JMS resources as part of the blueprint and model configuration
  • MyST now supports LDAP, OID and Active Directory authentication providers as part of the blueprint and model configuration

MyST Studio 3.4.2.2

Bug Fixes

  • Bug fix: Form validation issues were preventing editing infrastructure provider data

MyST Studio 3.4.2.1

Bug Fixes

  • Bug fix: The user login was not working and was getting into an infinite loop
  • Bug fix: Whenever the memory arguments were overriden in the platform model wizard, the model creation was failing

MyST Studio 3.4.2.0

Improvements

  • MyST Studio now shows the installers under each product definition
  • MyST supports auto-installing Maven on the target host, which will assist on build/deploy tasks

Bug Fixes

  • The MyST license was not being loaded from the right location in 3.4.1.0, causing the access to get blocked when one tries to login
  • Bug fix: Whenever the memory arguments were overriden in the platform model wizard, the model creation was failing

MyST Studio 3.4.1.0

New Features

  • Oracle SOA Suite 12.2.1 is now supported

Bug Fixes

  • Bug fix: The provisioning used to hang when a large amount of log was generated by the background process

MyST Studio 3.3.1.0

New Features

  • Platform Instance Reporting is now available
  • Added contextual help links to the user guide and included the user guide as part of the MyST Studio distribution
  • Introduced the ability to start, stop and restart the domain as well as execute any custom MyST actions with arguments against an active platform instance
  • Introduced the ability to reset manual configuration drift that has happened for a platform instance
  • Oracle JCS is now supported (Preview)
  • Continuous Delivery support for Oracle Fusion Middleware (Preview)

Improvements

  • Check for drift and dry run views now show the original and changed values in addition to the property names

Bug Fixes

  • Fixed issue related to cloning nodes in the blueprint, such as datasources
  • Fixed the browser caching issue to ensure a hassle-free user experience while receiving version upgrades

MyST Studio 3.3.0.0

New Features

  • Ability to version platform blueprints and models to support the entire platform cycle
  • Ability to associate pre-provisioned platform instances with platform models

Improvements

  • Ability to switch between view and edit modes of platform blueprints and models without losing the context
  • The toggle buttons appearing in the platform blueprint, model and instance views have been removed and the user experience is now improved with the introduction of adjustable split panes

Bug Fixes

  • Bug fix: When pre-existing infrastructure is selected in the platform model wizard, the user names and key pairs were not appearing in the host summary view
  • Bug fix: Filtering by platform blueprint was not working and the model list view was rendering all the models irrespective of the chosen blueprint
  • Bug fix: User Guide in MyST Studio now links to the MyST website documentation.
  • Bug fix: MyST extension was not being saved in some situations where additional white spaces were set between two tags
  • Bug fix for: JCA Adapter is now set correctly during provisioning

MyST Studio 3.2.2.0

New Features

  • Infrastructure Provider deletion is now supported

Improvements

  • MyST Studio now takes care of the race condition when instance launch and tagging occur close to each other in time
  • AWS Ids are shown when managing the infrastructure provider, for: AMI, VPC, Subnet, Security Group
  • Can search by the AWS Ids when managing the AWS infrastructure provider
  • CIDR blocks are shown for VPC and subnets when managing AWS Infrastructure provider
  • AWS resources which are part of the infrastructure but removed from AWS are now shown as strikethrough on re-discovery

MyST Studio 3.2.1.0

Improvements

  • Allows for the WebLogic machines to be named based on the user-defined Compute Node Name in MyST Studio
  • MyST Studio now shows the required product installers
  • Improves the way that 12c webtier components are displayed in the blueprint and model view

MyST Studio 3.2.0.0

Improvements

  • Support for pagination, search and sorting for: AWS AMIs, Instance Types, Credentials

Bug Fixes

  • AWS SSH keys are not shown in the UI when doing the first infrastructure discovery
  • Browser keeps refreshing in all screens after accessing the Platform Instances

MyST Studio 3.1.5.0

New Features

  • Provides automated MyST agent setup on target nodes
  • Provides ability to update platform models from MyST Studio

Improvements

  • Provides ability for setting privileged and agent users from within MyST Studio
  • Provides MyST Studio with support for AWS EC2 instance type family m4

MyST Studio 3.1.4.0

New Features

  • Provides ability to seed data to MyST Studio on boot

Improvements

  • Improved validation in Platform Blueprint wizard

MyST Studio 3.1.3.0

Improvements

  • AWS credentials can be updated directly in MyST Studio

MyST Studio 3.1.2.0

New Features

  • Full support for AWS provisioning in MyST Studio

MyST Studio 3.1.1.0

New Features

  • Ability to manage pre-existing infrastructure providers through the user interface
  • Ability to manage compute definitions through the user interface
  • Ability to manage environment types through the user interface

MyST Studio 3.1.0.0

New Features

  • First major release, providing users the ability to design platform blueprints and models and provision them to pre-existing infrastructure