Clone Platform Blueprints/Models
This guide covers the basics of creating a new Platform Blueprint and Platform Model based off an existing one.
Use Case
The use case is the user wants to create a parallel Oracle FMW domain because an Oracle Database 19c upgrade is required resulting in another upgrade of FMW 12.2.1.4.0.
Infrastructure Provider
Go to Infrastructure > Infrastructure Providers
Create the necessary provider and/or hosts. For example, if you are:
Reusing existing infrastructure then no action is required.
Using new infrastructure then select your provider (or create a new provider) and create new hosts IMPORTANT
There is a known bug with Compute Logical Definition where only OL6 should be selected. If any other option is selected you will not see the hosts when creating a new Platform Model.
Platform Blueprint
Creating a new Blueprint from a Template
Go to Platform Blueprints and click your blueprint
Fill in the new template information
Updating the Template
Go to Platform Templates and click your template
Here you can update your template as required. For example, you can update:
Middleware Settings > Catalog Version
Middleware Settings > Home Directory
WebLogic Domain Configuration > Name
Create a Blueprint
Fill in the new blueprint information and click Next and Finish
You are taken directly to the blueprint where you can Save & Commit the initial revision
You are now ready to create a model from the blueprint
Platform Model
Create a Model
Select the platform blueprint created earlier
Editing & Comparisons Tips
Due to the nature of 'environment specific' Platform Models, the clone feature in Myst does not yet exist. If your goal is to create a like-for-like model then here are some tips to compare the Myst properties.
Click Platform Model and select your model
Scroll down to Properties section
Repeat for the other environment you want to compare
Fix accordingly.
Update all passwords as required, especially if they were environment specific credentials.
NOTE: The Platform Blueprint was cloned so in theory most of the changes should be within the Platform Model.
Rest API Tip
If you have experience with Rest APIs then you can use that to post/put/get/etc via the Myst REST API. We have found a tool such as Postman is quite helpful.
Release Pipeline
Updating Application Source Code
In upgrade use cases you may find OSB servers only allow deployments of applications built on the same version (eg. 12.2.1.4.0
). Here is a guide to maintaining two application versions a. An application version for the old environment b. An application version for the new environment
Build your new application source code as usual but in the pom.xml use a different major version (eg.
2.0
)Use your previous version (eg.
1.0
) for your old environment's source code.In the next section we handle versioning via the Application Blueprint
Create the Application Blueprint
Go to Release Management > Application Blueprints
Select an existing Application Blueprint that is deployed to your environment
Create the Release Pipeline
Go to Release Management > Pipelines
Fill in and create the Release Pipeline information (stream/stages/etc) as per the standard process.
Defaulting Artifact Property Registry
Updating Stream Model Properties
Here we update the Stream Model Properties for each new stage (environment). In Myst you can use the 'Edit Bulk' button and copy+paste from the existing stream model to the new stream model.
Go to Release Management > Release Pipelines and select the old pipeline
Copy the contents to the clipboard (CTRL+C)
Go to your new release pipeline and open the Stream Model
Your Release Pipeline should be ready to go assuming you have provisioned the environment.
Last updated