MyST Studio 6.5.0

Improvements

Usability Enhancements

FC-5897 - Platform instance actions are now available from the Platform Model editor. Actions such as Update and Reprovision can be ran directly without needing to navigator away from the editor.

FC-5460 - Users can quickly return from the platform model editor to run an action by clicking the ‘Platform Models > (MODEL_NAME)’ breadcrumb which takes you back to the Platform Models page with the model already selected

FC-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-5845 - The updateEnvSettingsStore causing Axway Gateway instances to fail to boot after provisioning. This includes restart changes along with fix to duplicate primary key in ExtConnSettings.xml (was not incrementing PK after fetching).

FC-5813 - Corrected parameters for jvm.xml update to use group name instead of group ID

FC-5840 - Axway provisioning now kills both internal or external gateway processes instead of only one

FC-5499 - Support for provisioning of API Manager

FC-5798 - A number of required model fields are now autocomputed to a default value of ‘?’ if no meaningful value can be determined, in order to remove any guesswork around creating a fully functional model.

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

MyST Studio 6.4.0

New Features

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.

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

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.

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

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

New Features

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.

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

Bug Fixes

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

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

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

MyST Studio 5.6.0.3

Improvements

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.

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

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

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

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

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.

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

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

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

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

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

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 Fixes

MyST Studio 3.8.2.3

Bug Fixes

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

Improvements

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.