Table of Contents
- Overview
- Experience the Power of Puppet for Oracle WebLogic
- License
- Description
- Setup
- Usage
- Reference
- Limitations
Overview
This module allows you to configure and manage an Oracle WebLogic or Fusion middleware stack. It is part of our family of Puppet modules to install, manage and secure Oracle WebLogic and Fusion Middleware with Puppet. Besides the wls_config
module, this family also contains:
- wls_install For installing an Oracle WebLogic and other Fusion products
Experience the Power of Puppet for Oracle WebLogic
Installing Oracle WebLogic and/or Fusion software and managing your WebLogic domain configuration can be hard. With Puppet at your side, you get super-powers when installing and managing Oracle WebLogic. If you want to play and experiment with this please take a look at our playgrounds.
License
This is a commercially licensed module. But you can use the module on VirtualBox based development systems for FREE. You can request a FREE trial license here
Check the License for details.
Description
The wls_config
module extends the Puppet language to contain types needed to create and manage the lifecycle of objects within your Oracle Weblogic and Fusion Middleware installation. Instead of writing complex WLST scripts, using this module, you can now define your WebLogic configuration in an easy declarative way.
The puppet 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
wls_domain
wls_deployment
wls_domain
wls_user
wls_authentication_provider
wls_identity_asserter
wls_machine
wls_server
wls_server_channel
wls_cluster
wls_singleton_service
wls_coherence_cluster
wls_coherence_server
wls_server_template
wls_dynamic_cluster
wls_virtual_host
wls_workmanager_constraint
wls_workmanager
wls_datasource
wls_file_persistence_store
wls_jdbc_persistence_store
wls_jmsserver
wls_safagent
wls_jms_module
wls_jms_quota
wls_jms_subdeployment
wls_jms_queue
wls_jms_topic
wls_jms_connection_factory
wls_jms_template
wls_saf_remote_context
wls_saf_error_handler
wls_saf_imported_destination
wls_saf_imported_destination_object
wls_foreign_server
wls_foreign_server_object
wls_mail_session
wls_multi_datasource
wls_jms_bridge_destination
wls_messaging_bridge
Check here to see the full documentation for this module.
Setup
Requirements
The wls_config
module requires:
- Puppet module
enterprisemodules-easy_type
installed. - Puppet version 3.0 or higher. Can be Puppet Enterprise or Puppet Open Source
- WebLogic 10g or higher
- A valid Oracle Weblogic or Fusion license
- A valid Enterprise Modules license for usage.
- Runs on most Linux systems.
- Runs on Solaris
- Windows systems are NOT supported
We support WebLogic versions:
- WebLogic 10g
- WebLogic 11g
- WebLogic 12.1.2
- WebLogic 12.1.3
- WebLogic 12.2.1.2
- WebLogic 12.2.1.3
- WebLogic 12.2.1.4
- WebLogic 14.1.1.0
And Fusion versions:
- WebLogic 10g
- WebLogic 11g
- WebLogic 12c ( 12.1.1, 12.1.2, 12.1.3, 12.2.1.2 12.2.1.3, 12.2.1.4)
Installing the wls_config module
To install these modules, you can use a Puppetfile
mod 'enterprisemodules/wls_config' ,'3.0.x'
Then use the librarian-puppet
or r10K
to install the software.
You can also install the software using the puppet module
command:
puppet module install enterprisemodules-wls_config
Usage
Building a total WebLogic or Fusion setup requires quite some work. To help you, we have built some examples. The repo contains a demonstration of a simple WebLogic installation.
Reference
Here you can find some more information regarding this puppet module:
Here are a related blog posts:
- Introducing version 3 of wls_config
- Know thy WebLogic configuration using Puppet
- Manage your WebLogic JMS config with Puppet
- Using Puppet to install and manage your WebLogic infrastructure
Some example code:
Limitations
This module runs on Solaris, AIX and most Linux versions. It requires a puppet version higher than 4. The module does NOT run on windows systems.