The wls_config module contains all classes, defined types, and custom types to manage the lifecycle of objects within your database. It allows you to create, update and delete objects in your WebLogic environment using the Puppet descriptive language. Checkout our full documentation of this module at our documentation site To install the Weblogic software, you’ll need the wls_install module. With the purchase, you are entitled to run this module on one node and get support and maintenance. The entitlement period lasts for twelve months. To use the Oracle software you need a separate license provided by Oracle Inc. Check the Oracle price list to buy a valid license for your system(s).
wls_config module allows you to manage almost everything that is manageable in a WebLogic domain. For queue’s and topics to datasources clusters and security policies. Here is a list of some of the objects you can manage with puppet when using this module:
wls_setting, set the default wls parameters for the other types and also used by puppet resource
wls_adminserver control the adminserver or subscribe to changes
wls_managedserver control the managed server,cluster or subscribe to changes
Check here to see the full documentation for this module.
To install the WebLogic or other Fusion products, check out
Our modules are based on an annual subscription(an entitlement). When you purchase an entitlement:
We will make sure the modules keep working with the latest versions of Puppet en the supporting products like Oracle IBM MQ or WebLogic.
We currently have the following licensing methods for you:
1) Free when used on VirtualBox
2) Per node per year subscription
3) Pay per Use
4) Custom licensing
This module is Free when used on a VirtualBox testing machine. The software checks if you are using VirtualBox and allows usage. No need to get any licenses from us to get going. Just download the module from our own forge and get going. To download the module use:
puppet module install --module_repository=http://forge.enterprisemodules.com enterprisemodules-modulename
Our basic licensing model requires a subscription per node. The subscription is valid for a year. To make this work, we need you to send us the node name of the system you want to use the module on. (Not the puppetmaster, but the system where the agent is running.). Based on this information we will send you a file containing the entitlement for your node(s). You can purchase the entitlement in the shop or you can contact us. After you have ordered this module, you will receive an entitlement file. This file contains the information needed to run the software on your Puppet machine (agents).
When you want to use this module in Docker containers, or on Cloud infrastructure where you have no control over the node name, the Pay per use licensing method can be used. This means you’ll purchase a base subscription per month and in addition to that get charged for every time you activate the module. At the end of the month, or when you stop the subscription, the amount due is charges to your credit card. For the activations, it doesn’t matter if puppet makes any changes to your system or not. Whenever the module is called, an activation is added to your list. You can purchase a Pay per use subscription here
When you want to use Pay per use, purchase a single Pay per use license in the store. You can then download the entitlement file on your systems and use ALL of our puppet modules like this.
Our license manager is very flexible. If you have special requirements, please contact us so we can discuss other options.
ora_config module requires:
Here you can find some more information regarding this puppet module:
Here are a related blog posts:
Some example code: