Myst's approach of using Platform Blueprints / Models to define the target state of our Oracle Middleware infrastructure allows us to automate not just the initial provisioning of the Oracle Middleware platform instance, but also its configuration.
This configuration can be applied, either as part of the initial provisioning of the platform instance or later by modifying Platform Blueprints / Model and performing an update action against the Platform Instances.
This section details how to define some of the more common Oracle Middleware configurations, such as:
- WebLogic Servers - For example, JTA Timeout, Server Startup Arguments and Classes.
- Oracle Patches - To guarantee correct patch-levels
- JDBC Data Sources - With examples for Oracle RAC, Microsoft SQL Server and IBM DB2
- Java Messaging Service (JMS):
- JCA Adapters - Such as DB, JMS and File Adapters
- Work Managers - Such as constraint and request classes
- Load Balancer Frontends - To ensure correct rewriting of server URLs
- Webtier Routing Rules - To define Oracle HTTP Server routings
- Users, Groups, Roles and Policies - For advanced setting such as Role Conditions and Credential Maps
- Keystore Certificates - For apply certificates to keystores
- Startup and Shutdown Classes - To trigger custom startup or shutdown operations
- WebLogic Deployment Targeting - For targeting of default resources
This section only covers a subset of the configurations that can be performed by Myst. If the configuration you need to apply is not documented here, please raise a ticket at support.rubiconred.com to ask for assistance.