Rubicon Red MyST uses a declarative approach to automation, meaning users simply define the target state of the Oracle Middleware infrastructure to be deployed; which, at the push of a button, is automatically provisioned by MyST.
Within MyST, the target state is captured in the platform definition, which is divided into two layers. First, the Platform Blueprint defines an environment agnostic specification used to define the platform topology and configuration of your Oracle Middleware. Second, the Platform Model, overlays the environment specific configurations.
Splitting the platform definition into two layers, provides infrastructure independence; enabling you to provision consistent middleware platforms across all environments regardless of infrastructure type, on premise and on cloud.
One way to create a Platform Blueprint is to use the Platform Wizard, this guides the user through a simple process to capture the key design decisions for the Oracle Middleware topology and configuration and creates a corresponding Platform Blueprint.
Alternatively MyST allows you to introspect and capture the configuration of an existing WebLogic domain and use that to generate an equivalent Platform Blueprint. This is the topic of this blog.
To create a Platform Blueprint based on an existing WebLogic domain, we simply point MyST at the servers hosting the WebLogic domain; MyST will introspect the domain and create a corresponding Platform Blueprint. This supports a number of use cases, including: Read the complete article here.
For regular information on Oracle SOA Suite become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.