wls jms
Overview
This class is the default implementation for defining WebLogic JMS setup.
Using hiera, you can customize some of the aspects of this process.
When these customizations aren’t enough, you can replace the class with your own class. See wls_profile::weblogic for an explanation on how to do this.
Attributes
| Attribute Name | Short Description |
|---|---|
| module_list | A list of modules to define. |
| queue_list | A list of JMS queues to define. |
| topic_lis | A list of JMS topics to define. |
module_list
A list of modules to define.
The default value is: {}
This is a simple way to get started. It is easy to get started, but soon your hiera yaml become a nightmare. Our advice is when you need to let puppet manage your Oracle profiles, to override this class and add your own puppet implementation. This is much better maintainable and adds more consistency.
Type: Hash
queue_list
A list of JMS queues to define.
The default value is: {}
This is a simple way to get started. It is easy to get started, but soon your hiera yaml become a nightmare. Our advice is when you need to let puppet manage your Oracle profiles, to override this class and add your own puppet implementation. This is much better maintainable and adds more consistency.
Type: Hash
topic_lis
A list of JMS topics to define.
The default value is: {}
This is a simple way to get started. It is easy to get started, but soon your hiera yaml become a nightmare. Our advice is when you need to let puppet manage your Oracle profiles, to override this class and add your own puppet implementation. This is much better maintainable and adds more consistency.
