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.