wls_profile
Version information
This version is compatible with:
- Puppet Enterprise 2023.8.x, 2023.7.x, 2023.6.x, 2023.5.x, 2023.4.x, 2023.3.x, 2023.2.x, 2023.1.x, 2023.0.x, 2021.7.x, 2021.6.x, 2021.5.x, 2021.4.x, 2021.3.x, 2021.2.x, 2021.1.x, 2021.0.x, 2019.8.x, 2019.7.x, 2019.5.x, 2019.4.x, 2019.3.x, 2019.2.x, 2019.1.x, 2019.0.x, 2018.1.x, 2017.3.x, 2017.2.x, 2017.1.x, 2016.5.x, 2016.4.x
- Puppet >= 4.7.0 < 9.0.0
- , , , , ,
Plans:
- apply_patches
Start using this module
Add this module to your Puppetfile:
mod 'enterprisemodules-wls_profile', '0.32.2'Learn more about managing modules with a PuppetfileDocumentation
Table of Contents
- Overview
- Experience the Power of Puppet for Oracle WebLogic
- License
- Description
- Setup
- Usage
- Reference
- Limitations
Overview
The wls_profile module allows an easy path from first simple installation to a fully customized Enterprise setup. It is part of our family of Puppet modules to install, manage and secure WebLogic and Fusion Middleware with Puppet. Besides the wls_profile module, this family also contains:
- wls_config For configuring an Oracle WebLogic and other Fusion products
- 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
Most of the Enterprise Modules modules are commercial modules. This one is NOT. It is an Open Source module. You are free to use it any way you like. It, however, is based on our commercial Puppet WebLogic modules.
Description
This module has a couple of convenient classes to help you setup your WebLogic environment:
wls_profile::weblogicEnsure WebLogic is installed and patchedwls_profile::basic_domainSame asweblogicand create an empty domain.wls_profile::admin_serverSame asbasic_domainand create some machines and servers, clusters and some other WebLogic object.wls_profile::nodeSame asweblogicand after that copy the domain from an admin server and load it.
All of these classes contain some steps. All of these stapes have default implementations, but you can add extra Puppet code to the catalog and remove or override the default implementation. This can all be done by adding values to your hiera files.
Check here to see the full documentation for this module.
Setup
Requirements
The wls_profile module requires:
- Puppet module
enterprisemodules-easy_typeinstalled. - Puppet module
enterprisemodules-wls_installinstalled. - Puppet module
enterprisemodules-wls_configinstalled. - Puppet version 4.10.8 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
This module uses some other public Puppet forge modules. Check the metadata to ensure you have all dependencies installed.
We support WebLogic versions:
- WebLogic 10g
- WebLogic 11g
- WebLogic 12.1.2
- WebLogic 12.1.3
- WebLogic 12.2.1
- WebLogic 12.2.1.1
- 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, 12.2.1.1, 12.2.1.2, 12.2.1.3, 12.2.1.4)
Installing the wls_profile module
To install these modules, you can use a Puppetfile
mod 'enterprisemodules/wls_profile' ,'0.1.0'
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_profile
Usage
To get started, include the wls_profile::admin_server class in your role, make sure you have a module called software that has a folder files and that directory contains the next files:
fmw_12.2.1.3.0_wls.jarWebLogic softwarejdk-8u152-linux-x64.tar.gzJava JDK softwarejce_policy-8.zipJava Encryption Policy
Run Puppet and you have a Server with WebLogic installed, a domain called MYDOMAIN and a cluster called main. Check the documentation for all the settings you can manage. Here is a list of the most basic stuff you'd probably want to change:
wls_profile::domain_name: MYDOMAIN # The domain name
wls_profile::cluster_name: main # Cluster name
wls_profile::weblogic_password: Welcome01 # Weblogic password
wls_profile::source: puppet:///modules/software # Location where the files are fetched from
wls_profile::weblogic::ssh_setup::public_key: AAAAB3N.....M43olbQ==
wls_profile::weblogic::ssh_setup::private_key: |
-----BEGIN RSA PRIVATE KEY-----
MIIJKQIBAAKCAgEA5zOPmOVSF3MFXaEoLlbZICXuG0q2uT5kW1BwRzDbzVdiJtuA
...
PsLoml7g3jpGkRb3xgW1N4N4Xt+Vkzp6qAB5aqvCZO3EoHfeOS5DE9O+XbSW
-----END RSA PRIVATE KEY-----
Reference
Here you can find some more information regarding this puppet module:
Here are 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 and most Linux versions. It requires a puppet version higher than 4.10.8. The module does NOT run on windows systems.
Reference
Table of Contents
Classes
wls_profile: wls_profilewls_profile::admin_server: This is a highly customizable Puppet profile class to define a WebLogic Admin Server on your system.wls_profile::admin_server::pack_domain: This class is the default implementation for packing a domain on the current server.wls_profile::admin_server::wls_cluster: This class is the default implementation for creating a WebLogic cluster on your system.wls_profile::admin_server::wls_datasources: This class is the default implementation for defining WebLogic datasources.wls_profile::admin_server::wls_jms: This class is the default implementation for defining WebLogic JMS setup.wls_profile::admin_server::wls_servers: This class makes sure all te required WebLogic machines and servers are defined on your system.wls_profile::admin_server::wls_users_and_groups: This class is the default implementation for ensuring the correct WebLogic users and groups are available on the system.wls_profile::basic_domain: wls_profile::basic_domain This is a highly customizable Puppet profile class to define a basic WebLogic (empty) domain on your system. At itwls_profile::basic_domain::wls_domain: This class is the default implementation for defining a domain on your system.wls_profile::basic_domain::wls_startup: This class is the default implementation for making sure WebLogic gets started after a system reboot.wls_profile::node: wls_profile::node This is a highly customizable Puppet profile class to define a WebLogic node. At its core just adding:```contain wls_profiwls_profile::weblogic: wls_profile::weblogic This is a highly customizable Puppet profile class to install the WebLogic software and its requirements on your systwls_profile::weblogic::em_license: This class will deploy the Enterprise Modules license.wls_profile::weblogic::fmw_software: This class is the default implementation for creating the required OS users and groups for the installation of WebLogic.wls_profile::weblogic::java_software: This class is the default implementation for making sure the Java software is correctly installed on your system.wls_profile::weblogic::ssh_setup: This class is the default implementation for making sure the WebLogic account has ssh keys setup so it can passwordless copy files.wls_profile::weblogic::wls_opatch: This class is the default implementation for ensuring your WebLogic Opatch is up-to-date.wls_profile::weblogic::wls_patches: This class is the default implementation for ensuring your WebLogic software has all the required patches installed.wls_profile::weblogic::wls_software: This class is the default implementation for installing the WebLogic software on your system.
Defined types
wls_profile::admin_server::managed_server: This defined type is the default implementation for defining a managed server in your WebLogic domain.wls_profile::weblogic::private::start_managed_serverswls_profile::weblogic::private::stop_managed_servers
Plans
wls_profile::weblogic::apply_patches: Apply the in hiera specified WebLogic patches to the specified target
Classes
wls_profile
wls_profile
Parameters
The following parameters are available in the wls_profile class:
adminserver_addressadminserver_portcluster_namedomain_namedomains_dirdownload_dirjava_full_versionjava_versionjdk_homelog_dirmiddleware_homenodemanager_addressnodemanager_portoracle_baseos_groupos_userserverssourcetemp_dirweblogic_homeweblogic_passwordweblogic_userweblogic_versioninstall_type
adminserver_address
Data type: String[1]
adminserver_port
Data type: Integer
cluster_name
Data type: String[1]
domain_name
Data type: String[1]
domains_dir
Data type: Stdlib::Absolutepath
download_dir
Data type: Stdlib::Absolutepath
java_full_version
Data type: String[1]
java_version
Data type: String[1]
jdk_home
Data type: Stdlib::Absolutepath
log_dir
Data type: Stdlib::Absolutepath
middleware_home
Data type: Stdlib::Absolutepath
nodemanager_address
Data type: String[1]
nodemanager_port
Data type: Integer
oracle_base
Data type: Stdlib::Absolutepath
os_group
Data type: String[1]
os_user
Data type: String[1]
servers
Data type: Hash
source
Data type: String[1]
temp_dir
Data type: Stdlib::Absolutepath
weblogic_home
Data type: Stdlib::Absolutepath
weblogic_password
Data type: Easy_type::Password
weblogic_user
Data type: String[1]
weblogic_version
Data type: Wls_install::Versions
install_type
Data type: Enum[ 'standard', 'forms', 'ohs_standalone', 'adf_restricted', 'osb', 'osb_soa', 'osb_soa_bpm', 'soa', 'soa_bpm', 'bam', 'adf', 'oim', 'oud', 'wc', 'wc_wcc_bpm']
Default value: 'standard'
wls_profile::admin_server
wls_profile::admin_server
At its core just adding:
contain wls_profile::admin_server
Is enough to get a WebLogic domain running on your system.
But sometimes you have specific uses cases that are not handled well by the standard classes. This profile class allows you to add your own code to the execution.
Stages
Defining and starting a WebLogic Admin Server on your system goes through several stages(These are not puppet stages):
basic_domainInstall the WebLogic software and create a basic (empty) domainwls_serversCreate the WebLogic machines, servers you want in your domainwls_clusterCreate the WebLogic cluster you want in your domainwls_datasourcesCreate the WebLogic datasources you want in your domainwls_jmsSetup your JMS configuration for your domainwls_users_and_groupsThe WebLogic users and groupspack_domainPack the domain for transportation to an other WebLogic server
All these stages have a default implementation. This implementation is suitable to get started with. These classed all have parameters you can customize through hiera values. The defaults are specified in the module's data/default.yaml file.
before classes
But sometimes this is not enough, and you would like to add some extra definitions, you can, for example, add a Puppet class to be executed after the wls_datasources stage is done and before the wls_jms is done. You can do this by adding the next line to your yaml data:
wls_profile::admin_server::before_wls_jms: my_profile::my_extra_class
after classes
You can do the same when you want to add code after one of the stage classes:
wls_profile::admin_server::after_wls_users_and_groups: my_profile::my_extra_class
Skipping
Sometimes organizations use different modules and mechanisms to implement a feature, and you want to skip the class:
wls_profile::admin_server::pack_domain: skip
Replacing
Or provide your own implementation:
wls_profile::admin_server::wls_datasources: my_profile::my_own_implementation
This mechanism can be used for all named stages and makes it easy to move from an easy setup with a running standard WebLogic Admin server to a fully customized setup using a lot of your own classes plugged in.
Look at the description of the stages and their properties.
See the file "LICENSE" for the full license governing this code.
Parameters
The following parameters are available in the wls_profile::admin_server class:
basic_domainwls_serverswls_clusterwls_datasourceswls_jmswls_users_and_groupspack_domainbefore_basic_domainbefore_wls_serversbefore_wls_clusterbefore_wls_datasourcesbefore_wls_jmsbefore_wls_users_and_groupsbefore_pack_domainafter_basic_domainafter_wls_serversafter_wls_clusterafter_wls_datasourcesafter_wls_jmsafter_wls_users_and_groupsafter_pack_domain
basic_domain
Data type: Optional[String]
Use this value if you want to skip or use your own class for stage basic_domain.
Use your own class
You can use hiera to set this value. Here is an example:
wls_profile::admin_server::basic_domain: my_module::my_class
Skip
You can use hiera to set this value. Here is an example:
wls_profile::admin_server::basic_domain: skip
Default value: undef
wls_servers
Data type: Optional[String]
Use this value if you want to skip or use your own class for stage wls_servers.
Use your own class
You can use hiera to set this value. Here is an example:
wls_profile::admin_server::wls_servers: my_module::my_class
Skip
You can use hiera to set this value. Here is an example:
wls_profile::admin_server::wls_servers: skip
Default value: undef
wls_cluster
Data type: Optional[String]
Use this value if you want to skip or use your own class for stage wls_cluster.
Use your own class
You can use hiera to set this value. Here is an example:
wls_profile::admin_server::wls_cluster: my_module::my_class
Skip
You can use hiera to set this value. Here is an example:
wls_profile::admin_server::wls_cluster: skip
Default value: undef
wls_datasources
Data type: Optional[String]
Use this value if you want to skip or use your own class for stage wls_datasources.
Use your own class
You can use hiera to set this value. Here is an example:
wls_profile::admin_server::wls_datasources: my_module::my_class
Skip
You can use hiera to set this value. Here is an example:
wls_profile::admin_server::wls_datasources: skip
Default value: undef
wls_jms
Data type: Optional[String]
Use this value if you want to skip or use your own class for stage wls_jms.
Use your own class
You can use hiera to set this value. Here is an example:
wls_profile::admin_server::wls_jms: my_module::my_class
Skip
You can use hiera to set this value. Here is an example:
wls_profile::admin_server::wls_jms: skip
Default value: undef
wls_users_and_groups
Data type: Optional[String]
Use this value if you want to skip or use your own class for stage wls_users_and_groups.
Use your own class
You can use hiera to set this value. Here is an example:
wls_profile::admin_server::wls_users_and_groups: my_module::my_class
Skip
You can use hiera to set this value. Here is an example:
wls_profile::admin_server::wls_users_and_groups: skip
Default value: undef
pack_domain
Data type: Optional[String]
Use this value if you want to skip or use your own class for stage pack_domain.
Use your own class
You can use hiera to set this value. Here is an example:
wls_profile::admin_server::pack_domain: my_module::my_class
Skip
You can use hiera to set this value. Here is an example:
wls_profile::admin_server::pack_domain: skip
Default value: undef
before_basic_domain
Data type: Optional[String]
The name of the class you want to execute directly before the basic_domain class.
You can use hiera to set this value. Here is an example:
wls_profile::admin_server::before_basic_domain: my_module::my_class
Default value: undef
before_wls_servers
Data type: Optional[String]
The name of the class you want to execute directly before the wls_servers class.
You can use hiera to set this value. Here is an example:
wls_profile::admin_server::before_wls_servers: my_module::my_class
Default value: undef
before_wls_cluster
Data type: Optional[String]
The name of the class you want to execute directly before the wls_cluster class.
You can use hiera to set this value. Here is an example:
wls_profile::admin_server::before_wls_cluster: my_module::my_class
Default value: undef
before_wls_datasources
Data type: Optional[String]
The name of the class you want to execute directly before the wls_datasources class.
You can use hiera to set this value. Here is an example:
wls_profile::admin_server::before_wls_datasources: my_module::my_class
Default value: undef
before_wls_jms
Data type: Optional[String]
The name of the class you want to execute directly before the wls_jms class.
You can use hiera to set this value. Here is an example:
wls_profile::admin_server::before_wls_jms: my_module::my_class
Default value: undef
before_wls_users_and_groups
Data type: Optional[String]
The name of the class you want to execute directly before the wls_users class.
You can use hiera to set this value. Here is an example:
wls_profile::admin_server::before_wls_users: my_module::my_class
Default value: undef
before_pack_domain
Data type: Optional[String]
The name of the class you want to execute directly before the pack_domain class.
You can use hiera to set this value. Here is an example:
wls_profile::admin_server::before_pack_domain: my_module::my_class
Default value: undef
after_basic_domain
Data type: Optional[String]
The name of the class you want to execute directly after the basic_domain class.
You can use hiera to set this value. Here is an example:
wls_profile::admin_server::basic_domain: my_module::my_class
Default value: undef
after_wls_servers
Data type: Optional[String]
The name of the class you want to execute directly after the wls_servers class.
You can use hiera to set this value. Here is an example:
wls_profile::admin_server::after_wls_servers: my_module::my_class
Default value: undef
after_wls_cluster
Data type: Optional[String]
The name of the class you want to execute directly after the wls_cluster class.
You can use hiera to set this value. Here is an example:
wls_profile::admin_server::after_wls_cluster: my_module::my_class
Default value: undef
after_wls_datasources
Data type: Optional[String]
The name of the class you want to execute directly after the wls_datasources class.
You can use hiera to set this value. Here is an example:
wls_profile::admin_server::after_wls_datasources: my_module::my_class
Default value: undef
after_wls_jms
Data type: Optional[String]
The name of the class you want to execute directly after the wls_jms class.
You can use hiera to set this value. Here is an example:
wls_profile::admin_server::after_wls_jms: my_module::my_class
Default value: undef
after_wls_users_and_groups
Data type: Optional[String]
The name of the class you want to execute directly after the wls_users_and_groups class.
You can use hiera to set this value. Here is an example:
wls_profile::admin_server::after_wls_users_and_groups: my_module::my_class
Default value: undef
after_pack_domain
Data type: Optional[String]
The name of the class you want to execute directly after the pack_domain class.
You can use hiera to set this value. Here is an example:
wls_profile::admin_server::after_pack_domain: my_module::my_class
Default value: undef
wls_profile::admin_server::pack_domain
wls_profile::admin_server::pack_domain
The packed domain can be used to create other WebLogic nodes in the same domain. When you are creating just a single node WebLogic server, you can skip this class.
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::admin_server for an explanation on how to do this.
See the file "LICENSE" for the full license governing this code.
Parameters
The following parameters are available in the wls_profile::admin_server::pack_domain class:
domain_name
Data type: String[1]
The name of the WebLogic domain.
This will be used both as the REAL WebLogic domain name, and also be used by Puppet as a designator for Puppet resources. (e.g. the name before the slash my_domain/wls_queue1).
The change the domain name, use the hiera key: wls_profile::domain_name. This will make sure the correct domain name gets used in all classes.
The default value is: MYDOMAIN
middleware_home
Data type: Stdlib::Absolutepath
The Oracle middleware home directory.
This value is used in multiple places. To make sure in all classed the correct value is used, use the hiera key wls_profile::middleware_home to change it to your requested value.
Default value: /opt/oracle/middleware12
weblogic_home
Data type: Stdlib::Absolutepath
The directory used as WebLogic home
This value is used in multiple places. To make sure in all classed the correct value is used, use the hiera key wls_profile::weblogic_home to change it to your requested value.
Default value: /opt/oracle/middleware12/wlserver
jdk_home
Data type: Stdlib::Absolutepath
The location where the JDK is installed.
This value is used in multiple places. To make sure in all classed the correct value is used, use the hiera key wls_profile::jdk_home to change it to your requested value.
The default value is: /usr/java/jdk1.8.0_152
domains_dir
Data type: Stdlib::Absolutepath
The top-level directory where the domain directories will reside in.
This value is used in multiple places. To make sure in all classed the correct value is used, use the hiera key wls_profile::domains_dir to change it to your requested value.
The default value is: /opt/oracle/domains
os_user
Data type: String[1]
The os user to use for WebLogic.
This value is used in multiple places. To make sure in all classed the correct value is used, use the hiera key wls_profile::basic_domain::os_user to change it to your requested value.
Default value: oracle
os_group
Data type: String[1]
The os group to use for WebLogic.
This value is used in multiple places. To make sure in all classed the correct value is used, use the hiera key wls_profile::basic_domain::os_group to change it to your requested value.
Default value: dba
wls_profile::admin_server::wls_cluster
wls_profile::admin_server::wls_cluster
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::admin_server for an explanation on how to do this.
See the file "LICENSE" for the full license governing this code.
Parameters
The following parameters are available in the wls_profile::admin_server::wls_cluster class:
domain_name
Data type: String[1]
The name of the WebLogic domain.
This will be used both as the REAL WebLogic domain name, and also be used by Puppet as a designator for Puppet resources. (e.g. the name before the slash my_domain/wls_queue1).
The change the domain name, use the hiera key: wls_profile::domain_name. This will make sure the correct domain name gets used in all classes.
The default value is: MYDOMAIN
cluster_name
Data type: String[1]
The name to use for the cluster.
The change the domain name, use the hiera key: wls_profile::cluster_name. This will make sure the correct domain name gets used in all classes.
Default value is: main
servers
Data type: Hash
A Hash of machine-servers defining all servers that need to be part of the cluster.
The default implementations reads these values from the hiera key wls_profile::admin_server::wls_servers::servers
Default value: $wls_profile::servers
cluster_defaults
Data type: Hash
A Hash of default values used when creating a wls_cluster resource.
The default value is:
wls_profile::admin_server::wls_cluster::cluster_defaults:
messagingmode: unicast
migrationbasis: consensus
wls_profile::admin_server::wls_datasources
wls_profile::admin_server::wls_datasources
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.
See the file "LICENSE" for the full license governing this code.
Parameters
The following parameters are available in the wls_profile::admin_server::wls_datasources class:
list
Data type: Hash
A list of datasources 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.
wls_profile::admin_server::wls_jms
wls_profile::admin_server::wls_jms
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.
See the file "LICENSE" for the full license governing this code.
Parameters
The following parameters are available in the wls_profile::admin_server::wls_jms class:
module_list
Data type: Hash
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.
queue_list
Data type: Hash
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.
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.
topic_list
Data type: Hash
wls_profile::admin_server::wls_servers
wls_profile::admin_server::wls_servers
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.
See the file "LICENSE" for the full license governing this code.
Parameters
The following parameters are available in the wls_profile::admin_server::wls_servers class:
domain_name
Data type: String[1]
The name of the WebLogic domain.
This will be used both as the REAL WebLogic domain name, and also be used by Puppet as a designator for Puppet resources. (e.g. the name before the slash my_domain/wls_queue1).
The change the domain name, use the hiera key: wls_profile::domain_name. This will make sure the correct domain name gets used in all classes.
The default value is: MYDOMAIN
servers
Data type: Hash
Default value: $wls_profile::servers
server_defaults
Data type: Hash
machine_defaults
Data type: Hash
wls_profile::admin_server::wls_users_and_groups
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.
Parameters
The following parameters are available in the wls_profile::admin_server::wls_users_and_groups class:
group_list
Data type: Hash
A list of WebLogic groups 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.
user_list
Data type: Hash
A list of WebLogic users 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.
wls_profile::basic_domain
wls_profile::basic_domain
This is a highly customizable Puppet profile class to define a basic WebLogic (empty) domain on your system. At its core just adding:contain wls_profile::basic_domainIs enough to get an empty WebLogic domain running on your system. But sometimes you have specific uses cases that are not handled well by the standard classes. This profile class allows you to add your own code to the execution.## StagesDefining and starting an empty basic WebLogic domain on you system goes through several stages(These are not puppet stages):- weblogic Install and patch the WebLogic software- wls_domain Create an empty WebLogic domain- wls_startup Make sure the domain restarts after a system reboot.All these stages have a default implementation. This implementation is suitable to get off to an easy start. These classed all have parameters you can customize through hiera values. The defaults are specified in the module's data/default.yaml file. ## before classesBut sometimes this is not enough, and you would like to add some extra definitions, you can, for example, add a Puppet class to be executed after the weblogic stage is done and before the wls_domain is done. You can do this by adding the next line to your yaml data:yamlwls_profile::basic_domain::before_wls_domain: my_profile::my_extra_class## after classesYou can do the same when you want to add code after one of the stage classes:yamlwls_profile::basic_domain::after_wls_domain: my_profile::my_extra_class## SkippingSometimes organizations use different modules and mechanisms to implement a feature, and you want to skip the class:yamlwls_profile::basic_domain::wls_startup: skip## ReplacingOr provide your own implementation:yamlwls_profile::basic_domain::wls_domain: my_profile::my_own_implementationThis mechanism can be used for all named stages and makes it easy to move from an easy setup with a running standard WebLogic installation to a fully customized setup using a lot of your own classes plugged in.Look at the description of the stages and their properties.
See the file "LICENSE" for the full license governing this code.
Parameters
The following parameters are available in the wls_profile::basic_domain class:
weblogicwls_domainwls_startupbefore_weblogicbefore_wls_domainbefore_wls_startupafter_weblogicafter_wls_domainafter_wls_startup
weblogic
Data type: Optional[String]
Use this value if you want to skip or use your own class for stage weblogic.
Use your own class
You can use hiera to set this value. Here is an example:
wls_profile::basic_domain::weblogic: my_module::my_class
Skip
You can use hiera to set this value. Here is an example:
wls_profile::basic_domain::weblogic: skip
Default value: undef
wls_domain
Data type: Optional[String]
Use this value if you want to skip or use your own class for stage wls_domain.
Use your own class
You can use hiera to set this value. Here is an example:
wls_profile::basic_domain::wls_domain: my_module::my_class
Skip
You can use hiera to set this value. Here is an example:
wls_profile::basic_domain::wls_domain: skip
Default value: undef
wls_startup
Data type: Optional[String]
Use this value if you want to skip or use your own class for stage wls_startup.
Use your own class
You can use hiera to set this value. Here is an example:
wls_profile::basic_domain::wls_startup: my_module::my_class
Skip
You can use hiera to set this value. Here is an example:
wls_profile::basic_domain::wls_startup: skip
Default value: undef
before_weblogic
Data type: Optional[String]
The name of the class you want to execute directly before the weblogic class.
You can use hiera to set this value. Here is an example:
wls_profile::basic_domain::before_weblogic: my_module::my_class
Default value: undef
before_wls_domain
Data type: Optional[String]
The name of the class you want to execute directly before the wls_domain class.
You can use hiera to set this value. Here is an example:
wls_profile::basic_domain::before_wls_domain: my_module::my_class
Default value: undef
before_wls_startup
Data type: Optional[String]
The name of the class you want to execute directly before the wls_startup class.
You can use hiera to set this value. Here is an example:
wls_profile::basic_domain::before_wls_startup: my_module::my_class
Default value: undef
after_weblogic
Data type: Optional[String]
The name of the class you want to execute directly after the weblogic class.
You can use hiera to set this value. Here is an example:
wls_profile::basic_domain::after_weblogic: my_module::my_class
Default value: undef
after_wls_domain
Data type: Optional[String]
The name of the class you want to execute directly after the wls_domain class.
You can use hiera to set this value. Here is an example:
wls_profile::basic_domain::after_wls_domain: my_module::my_class
Default value: undef
after_wls_startup
Data type: Optional[String]
The name of the class you want to execute directly after the wls_startup class.
You can use hiera to set this value. Here is an example:
wls_profile::basic_domain::after_wls_startup: my_module::my_class
Default value: undef
wls_profile::basic_domain::wls_domain
wls_profile::basic_domain::wls_domain
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::basic_domain for an explanation on how to do this.
See the file "LICENSE" for the full license governing this code.
Parameters
The following parameters are available in the wls_profile::basic_domain::wls_domain class:
domain_namedomain_aliasversionweblogic_homedomains_dirlog_dirtemplate_namenodemanager_addressnodemanager_portadminserver_addressadminserver_portadministration_port_enabledadministration_portadminserver_ssl_portjava_update_windowos_useros_groupweblogic_userweblogic_passwordbam_enabledb2b_enabledess_enableddevelopment_modenodemanager_waitadminserver_settingscustom_identitycustom_identity_aliascustom_identity_keystore_filenamecustom_trustextra_propertiesjdk_homejsse_enabledmiddleware_hometrust_keystore_filecustom_identity_keystore_passphrasecustom_identity_privatekey_passphrasercu_database_urlrepository_database_urlrepository_passwordrepository_prefixrepository_sys_passwordtrust_keystore_passphrase
domain_name
Data type: String[1]
The name of the WebLogic domain.
This will be used both as the REAL WebLogic domain name, and also be used by Puppet as a designator for Puppet resources. (e.g. the name before the slash my_domain/wls_queue1).
The change the domain name, use the hiera key: wls_profile::domain_name. This will make sure the correct domain name gets used in all classes.
The default value is: MYDOMAIN
domain_alias
Data type: String[1]
The domain alias.
This is the name puppet uses to identify this domain. When you leave this parameter undefined, it will default to the current WebLogic domain name. When you specify the string 'default', Puppet will use this domain by default when you don't specify a resource for all of the wls_config resources.
Default value: $domain_name
version
Data type: Wls_install::Versions
The version of WebLogic you want to use.
This value is used in multiple places. To make sure in all classed the correct value is used, use the hiera key wls_profile::version to change it to your requested value.
Valid values are:
103611111112121112121213122112211122121221312214Default value:12213
Default value: $wls_profile::weblogic_version
weblogic_home
Data type: Stdlib::Absolutepath
The directory used as WebLogic home
This value is used in multiple places. To make sure in all classed the correct value is used, use the hiera key wls_profile::weblogic_home to change it to your requested value.
Default value: /opt/oracle/middleware12/wlserver
domains_dir
Data type: Stdlib::Absolutepath
The top-level directory where the domain directories will reside in.
This value is used in multiple places. To make sure in all classed the correct value is used, use the hiera key wls_profile::domains_dir to change it to your requested value.
The default value is: /opt/oracle/domains
log_dir
Data type: Stdlib::Absolutepath
The directory used for log files.
This value is used in multiple places. To make sure in all classed the correct value is used, use the hiera key wls_profile::log_dir to change it to your requested value.
Default value: /opt/oracle/domains/log
template_name
Data type: Enum[ 'standard', 'forms', 'ohs_standalone', 'adf_restricted', 'osb', 'osb_soa', 'osb_soa_bpm', 'soa', 'soa_bpm', 'bam', 'adf', 'oim', 'oud', 'wc', 'wc_wcc_bpm']
The domain template to use when creating the domain.
The default value is standard.
Valid values are:
standardohs_standaloneadf_restrictedosbosb_soaosb_soa_bpmsoasoa_bpmbamadfoimoudwcwc_wcc_bpm
nodemanager_address
Data type: String[1]
The IP address the nodemanager will run and listen on.
This value is used in multiple places. To make sure in all classed the correct value is used, use the hiera key wls_profile::basic_domain::wls_domain::log_dir to change it to your requested value.
Default value: ::fqdn
nodemanager_port
Data type: Integer
The IP port the nodemanager listens on.
This value is used in multiple places. To make sure in all classed the correct value is used, use the hiera key wls_profile::nodemanager_port to change it to your requested value.
Default value: 5556
Default value: $wls_profile::nodemanager_port
adminserver_address
Data type: String[1]
The address the admin server process will run and listen on.
This value is used in multiple places. To make sure in all classed the correct value is used, use the hiera key wls_profile::adminserver_address to change it to your requested value.
The default value is: The fact fqdn
adminserver_port
Data type: Integer
The IP port the admin server process will run and listen on.
This value is used in multiple places. To make sure in all classed the correct value is used, use the hiera key wls_profile::adminserver_port to change it to your requested value.
The default value is: 7001
Default value: $wls_profile::adminserver_port
administration_port_enabled
Data type: Boolean
Specifies whether the domain-wide administration port should be enabled for this WebLogic Server domain. Because the administration port uses SSL, enabling the administration port requires that SSL must be configured for all servers in the domain. The domain-wide administration port enables you to start a WebLogic Server instance in STANDBY state. It also allows you to separate administration traffic from application traffic in your domain. Because all servers in the domain must enable or disable the administration port at once, you configure the default administration port settings at the domain level. If you enable the administration port: The administration port accepts only connections that specify administrator credentials. Connections that specify administrator credentials can use only the administration port. The command that starts managed servers must specify a secure protocol and the administration port: -Dweblogic.management.server=https://admin_server:administration_port
administration_port
Data type: Optional[Integer]
The common secure administration port for this WebLogic Server domain. (Requires you to enable the administration port.)
adminserver_ssl_port
Data type: Optional[Integer]
SSL port to use for the Admin server.
java_update_window
Data type: Optional[String[1]]
The time frame in which any required java updates will be applied to your domain by Puppet.
Puppet will apply any detected java updates immediately if the value is undef, which is the default.
Default value: undef
os_user
Data type: String[1]
The os user to use for WebLogic.
This value is used in multiple places. To make sure in all classed the correct value is used, use the hiera key wls_profile::basic_domain::os_user to change it to your requested value.
Default value: oracle
os_group
Data type: String[1]
The os group to use for WebLogic.
This value is used in multiple places. To make sure in all classed the correct value is used, use the hiera key wls_profile::basic_domain::os_group to change it to your requested value.
Default value: dba
weblogic_user
Data type: String[1]
The WebLogic user account to bear all administration rights.
This value is used in multiple places. To make sure in all classed the correct value is used, use the hiera key wls_profile::weblogic_user to change it to your requested value.
Default value: weblogic
weblogic_password
Data type: Easy_type::Password
The password for the WebLogic account.
This value is used in multiple places. To make sure in all classed the correct value is used, use the hiera key wls_profile::weblogic_password to change it to your requested value.
Default value: Welcome01
bam_enabled
Data type: Boolean
A boolean value specifying if you want to enable bam.
Default value: false
b2b_enabled
Data type: Boolean
A boolean value specifying if you want to enable b2b.
Default value: false
ess_enabled
Data type: Boolean
A boolean value specifying if you want to enable ess.
Default value: false
development_mode
Data type: Boolean
A boolean value specifying if you want to enable development mode.
Default value: false
nodemanager_wait
Data type: Integer
The time in seconds Puppet waits for the nodemanager to start before declaring an error.
Default value: 20
adminserver_settings
Data type: Hash
A Hash containing settings (of type wls_server) to define for the Admin server.
The default value is: {}
custom_identity
Data type: Boolean
custom_identity_alias
Data type: Optional[String[1]]
custom_identity_keystore_filename
Data type: Optional[String[1]]
custom_trust
Data type: Boolean
extra_properties
Data type: Array
jdk_home
Data type: Stdlib::Absolutepath
jsse_enabled
Data type: Boolean
middleware_home
Data type: Stdlib::Absolutepath
trust_keystore_file
Data type: Optional[String[1]]
custom_identity_keystore_passphrase
Data type: Optional[Easy_type::Password]
Default value: undef
custom_identity_privatekey_passphrase
Data type: Optional[Easy_type::Password]
Default value: undef
rcu_database_url
Data type: Optional[String[1]]
Default value: undef
repository_database_url
Data type: Optional[String[1]]
Default value: undef
repository_password
Data type: Optional[Easy_type::Password]
Default value: undef
repository_prefix
Data type: Optional[String[1]]
Default value: undef
repository_sys_password
Data type: Optional[Easy_type::Password]
Default value: undef
trust_keystore_passphrase
Data type: Optional[Easy_type::Password]
Default value: undef
wls_profile::basic_domain::wls_startup
wls_profile::basic_domain::wls_startup
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.
See the file "LICENSE" for the full license governing this code.
Parameters
The following parameters are available in the wls_profile::basic_domain::wls_startup class:
domain_nameversionweblogic_homedomains_dirlog_diros_usercustom_trustjsse_enabledtrust_keystore_filetrust_keystore_passphrase
domain_name
Data type: String[1]
The name of the WebLogic domain.
This will be used both as the REAL WebLogic domain name, and also be used by Puppet as a designator for Puppet resources. (e.g. the name before the slash my_domain/wls_queue1).
The change the domain name, use the hiera key: wls_profile::domain_name. This will make sure the correct domain name gets used in all classes.
The default value is: MYDOMAIN
version
Data type: Wls_install::Versions
The version of WebLogic you want to use.
This value is used in multiple places. To make sure in all classed the correct value is used, use the hiera key wls_profile::version to change it to your requested value.
Valid values are:
103611111112121112121213122112211122121221312214Default value:12213
Default value: $wls_profile::weblogic_version
weblogic_home
Data type: Stdlib::Absolutepath
The directory used as WebLogic home
This value is used in multiple places. To make sure in all classed the correct value is used, use the hiera key wls_profile::weblogic_home to change it to your requested value.
Default value: /opt/oracle/middleware12/wlserver
domains_dir
Data type: Stdlib::Absolutepath
The top-level directory where the domain directories will reside in.
This value is used in multiple places. To make sure in all classed the correct value is used, use the hiera key wls_profile::domains_dir to change it to your requested value.
The default value is: /opt/oracle/domains
log_dir
Data type: Stdlib::Absolutepath
The directory used for log files.
This value is used in multiple places. To make sure in all classed the correct value is used, use the hiera key wls_profile::log_dir to change it to your requested value.
Default value: /opt/oracle/domains/log
os_user
Data type: String[1]
The os user to use for WebLogic.
This value is used in multiple places. To make sure in all classed the correct value is used, use the hiera key wls_profile::basic_domain::os_user to change it to your requested value.
Default value: oracle
custom_trust
Data type: Boolean
jsse_enabled
Data type: Boolean
trust_keystore_file
Data type: Optional[String[1]]
trust_keystore_passphrase
Data type: Optional[Easy_type::Password]
Default value: lookup('wls_profile::basic_domain::wls_domain::trust_keystore_passphrase', { 'default_value' => undef })
wls_profile::node
wls_profile::node
This is a highly customizable Puppet profile class to define a WebLogic node. At its core just adding:contain wls_profile::nodeIs enough to get the WebLogic software nstalled, fetch the domain definition from the Admin Server and start the node manager.But sometimes, you have specific uses cases that are not handled well by the standard classes. This profile class allows you to add your own code to the execution.## StagesDefining and starting a WebLogic Admin Server on your system goes through several stages(These are not puppet stages):- weblogic Setup the OS and install the WebLogic software- copy_domain Copy the packed domain from the AdminServer and start the Nodemanager- wls_startup Ensure WebLogic gets started after a reboot.All these stages have a default implementation. This implementation is suitable to get started with. These classed all have parameters you can customize through hiera values. The defaults are specified in the module's data/default.yaml file. ## before classesBut sometimes this is not enough, and you would like to add some extra definitions, you can, for example, add a Puppet class to be executed after the weblogic stage is done and before the copy_domain is done. You can do this by adding the next line to your yaml data:yamlwls_profile::node::before_copy_domain: my_profile::my_extra_class## after classesYou can do the same when you want to add code after one of the stage classes:yamlwls_profile::node::wls_startup: my_profile::my_extra_class## SkippingSometimes organizations use different modules and mechanisms to implement a feature, and you want to skip the class:yamlwls_profile::node::pack_domain: skip## ReplacingOr provide your own implementation:yamlwls_profile::admin_server::copy_domain: my_profile::my_own_implementationThis mechanism can be used for all named stages and makes it easy to move from an easy setup with a running standard WebLogic node server to a fully customized setup using a lot of your own classes plugged in.Look at the description of the stages and their properties.
See the file "LICENSE" for the full license governing this code.
Parameters
The following parameters are available in the wls_profile::node class:
weblogiccopy_domainwls_startupbefore_weblogicbefore_copy_domainbefore_wls_startupafter_weblogicafter_copy_domainafter_wls_startup
weblogic
Data type: Optional[String]
Use this value if you want to skip or use your own class for stage weblogic.
Use your own class
You can use hiera to set this value. Here is an example:
wls_profile::node::weblogic: my_module::my_class
Skip
You can use hiera to set this value. Here is an example:
wls_profile::node::weblogic: skip
Default value: undef
copy_domain
Data type: Optional[String]
Use this value if you want to skip or use your own class for stage copy_domain.
Use your own class
You can use hiera to set this value. Here is an example:
wls_profile::node::copy_domain: my_module::my_class
Skip
You can use hiera to set this value. Here is an example:
wls_profile::node::copy_domain: skip
Default value: undef
wls_startup
Data type: Optional[String]
Use this value if you want to skip or use your own class for stage wls_startup.
Use your own class
You can use hiera to set this value. Here is an example:
wls_profile::node::wls_startup: my_module::my_class
Skip
You can use hiera to set this value. Here is an example:
wls_profile::node::wls_startup: skip
Default value: undef
before_weblogic
Data type: Optional[String]
The name of the class you want to execute directly before the weblogic class.
You can use hiera to set this value. Here is an example:
wls_profile::node::before_weblogic: my_module::my_class
Default value: undef
before_copy_domain
Data type: Optional[String]
The name of the class you want to execute directly before the copy_domain class.
You can use hiera to set this value. Here is an example:
wls_profile::node::before_copy_domain: my_module::my_class
Default value: undef
before_wls_startup
Data type: Optional[String]
The name of the class you want to execute directly before the wls_startup class.
You can use hiera to set this value. Here is an example:
wls_profile::node::before_wls_startup: my_module::my_class
Default value: undef
after_weblogic
Data type: Optional[String]
The name of the class you want to execute directly after the weblogic class.
You can use hiera to set this value. Here is an example:
wls_profile::node::after_weblogic: my_module::my_class
Default value: undef
after_copy_domain
Data type: Optional[String]
The name of the class you want to execute directly after the copy_domain class.
You can use hiera to set this value. Here is an example:
wls_profile::node::after_copy_domain: my_module::my_class
Default value: undef
after_wls_startup
Data type: Optional[String]
The name of the class you want to execute directly after the wls_startup class.
You can use hiera to set this value. Here is an example:
wls_profile::node::after_wls_startup: my_module::my_class
Default value: undef
wls_profile::weblogic
wls_profile::weblogic
This is a highly customizable Puppet profile class to install the WebLogic software and its requirements on your system. At its core, just adding:contain wls_profile::weblogicis enough to get the WebLogic software installed on your system. But sometimes, you have specific uses cases that are not handled well by the standard classes. This profile class allows you to add your own code to the execution.## StagesDefining and starting a WebLogic Admin Server on your system goes through several stages(These are not puppet stages):- sysctl Set required sysctl parameters- limits Set OS security limits- packages Install required packages- groups_and_users Create required OS users and groups- ssh_setup Setup SSH for accounts- firewall Setup the firewall- java_software Install the java software- wls_software Install the WebLogic software- wls_patches Install the WebLogic patchesAll these stages have a default implementation. This implementation is suitable to get started with. These classed all have parameters you can customize through hiera values. The defaults are specified in the module's data/default.yaml file. ## before classesBut sometimes this is not enough, and you would like to add some extra definitions, you can, for example, add a Puppet class to be executed after the packages stage is done and before the groups_and_users is done. You can do this by adding the following line to your yaml data:yamlwls_profile::weblogic::groups_and_users: my_profile::my_extra_class## after classesYou can do the same when you want to add code after one of the stage classes:yamlwls_profile::weblogic::firewall: my_profile::my_extra_class## SkippingSometimes organizations use different modules and mechanisms to implement a feature, and you want to skip the class:yamlwls_profile::weblogic::java_software: skip## ReplacingOr provide your own implementation:yamlwls_profile::weblogic::wls_datasources: my_profile::my_own_implementationThis mechanism can be used for all named stages and makes it easy to move from an easy setup with a running standard WebLogic software installation to a fully customized setup using a lot of your own classes plugged in.Look at the description of the stages and their properties.
See the file "LICENSE" for the full license governing this code.
Parameters
The following parameters are available in the wls_profile::weblogic class:
sysctllimitspackagesgroups_and_usersssh_setupfirewalljava_softwarewls_softwarewls_patchesbefore_sysctlbefore_limitsbefore_packagesbefore_groups_and_usersbefore_ssh_setupbefore_firewallbefore_java_softwarebefore_wls_softwarebefore_wls_patchesafter_sysctlafter_limitsafter_packagesafter_groups_and_usersafter_ssh_setupafter_firewallafter_java_softwareafter_wls_softwareafter_wls_patchesafter_em_licenseafter_fmw_softwareafter_wls_opatchbefore_em_licensebefore_fmw_softwarebefore_wls_opatchem_licensefmw_softwarewls_opatch
sysctl
Data type: Optional[String]
Use this value if you want to skip or use your own class for stage sysctl.
Use your own class
You can use hiera to set this value. Here is an example:
wls_profile::weblogic::sysctl: my_module::my_class
Skip
You can use hiera to set this value. Here is an example:
wls_profile::weblogic::sysctl: skip
Default value: undef
limits
Data type: Optional[String]
Use this value if you want to skip or use your own class for stage limits.
Use your own class
You can use hiera to set this value. Here is an example:
wls_profile::weblogic::limits: my_module::my_class
Skip
You can use hiera to set this value. Here is an example:
wls_profile::weblogic::limits: skip
Default value: undef
packages
Data type: Optional[String]
Use this value if you want to skip or use your own class for stage packages.
Use your own class
You can use hiera to set this value. Here is an example:
wls_profile::weblogic::packages: my_module::my_class
Skip
You can use hiera to set this value. Here is an example:
wls_profile::weblogic::packages: skip
Default value: undef
groups_and_users
Data type: Optional[String]
Use this value if you want to skip or use your own class for stage groups_and_users.
Use your own class
You can use hiera to set this value. Here is an example:
wls_profile::weblogic::groups_and_users: my_module::my_class
Skip
You can use hiera to set this value. Here is an example:
wls_profile::weblogic::groups_and_users: skip
Default value: undef
ssh_setup
Data type: Optional[String]
Use this value if you want to skip or use your own class for stage ssh_setup.
Use your own class
You can use hiera to set this value. Here is an example:
wls_profile::weblogic::ssh_setup: my_module::my_class
Skip
You can use hiera to set this value. Here is an example:
wls_profile::weblogic::ssh_setup: skip
Default value: undef
firewall
Data type: Optional[String]
Use this value if you want to skip or use your own class for stage firewall.
Use your own class
You can use hiera to set this value. Here is an example:
wls_profile::weblogic::firewall: my_module::my_class
Skip
You can use hiera to set this value. Here is an example:
wls_profile::weblogic::firewall: skip
Default value: undef
java_software
Data type: Optional[String]
Use this value if you want to skip or use your own class for stage java_software.
Use your own class
You can use hiera to set this value. Here is an example:
wls_profile::weblogic::java_software: my_module::my_class
Skip
You can use hiera to set this value. Here is an example:
wls_profile::weblogic::java_software: skip
Default value: undef
wls_software
Data type: Optional[String]
Use this value if you want to skip or use your own class for stage wls_software.
Use your own class
You can use hiera to set this value. Here is an example:
wls_profile::weblogic::wls_software: my_module::my_class
Skip
You can use hiera to set this value. Here is an example:
wls_profile::weblogic::wls_software: skip
Default value: undef
wls_patches
Data type: Optional[String]
Use this value if you want to skip or use your own class for stage wls_patches.
Use your own class
You can use hiera to set this value. Here is an example:
wls_profile::weblogic::wls_patches: my_module::my_class
Skip
You can use hiera to set this value. Here is an example:
wls_profile::weblogic::wls_patches: skip
Default value: undef
before_sysctl
Data type: Optional[String]
The name of the class you want to execute directly before the sysctl class.
You can use hiera to set this value. Here is an example:
wls_profile::weblogic::before_sysctl: my_module::my_class
Default value: undef
before_limits
Data type: Optional[String]
The name of the class you want to execute directly before the limits class.
You can use hiera to set this value. Here is an example:
wls_profile::weblogic::before_limits: my_module::my_class
Default value: undef
before_packages
Data type: Optional[String]
The name of the class you want to execute directly before the packages class.
You can use hiera to set this value. Here is an example:
wls_profile::weblogic::before_packages: my_module::my_class
Default value: undef
before_groups_and_users
Data type: Optional[String]
The name of the class you want to execute directly before the groups_and_users class.
You can use hiera to set this value. Here is an example:
wls_profile::weblogic::before_groups_and_users: my_module::my_class
Default value: undef
before_ssh_setup
Data type: Optional[String]
The name of the class you want to execute directly before the ssh_setup class.
You can use hiera to set this value. Here is an example:
wls_profile::weblogic::before_ssh_setup: my_module::my_class
Default value: undef
before_firewall
Data type: Optional[String]
The name of the class you want to execute directly before the firewall class.
You can use hiera to set this value. Here is an example:
wls_profile::weblogic::before_firewall: my_module::my_class
Default value: undef
before_java_software
Data type: Optional[String]
The name of the class you want to execute directly before the java_software class.
You can use hiera to set this value. Here is an example:
wls_profile::weblogic::before_java_software: my_module::my_class
Default value: undef
before_wls_software
Data type: Optional[String]
The name of the class you want to execute directly before the wls_software class.
You can use hiera to set this value. Here is an example:
wls_profile::weblogic::before_wls_software: my_module::my_class
Default value: undef
before_wls_patches
Data type: Optional[String]
The name of the class you want to execute directly before the wls_patches class.
You can use hiera to set this value. Here is an example:
wls_profile::weblogic::before_wls_patches: my_module::my_class
Default value: undef
after_sysctl
Data type: Optional[String]
The name of the class you want to execute directly after the sysctl class.
You can use hiera to set this value. Here is an example:
wls_profile::weblogic::after_sysctl: my_module::my_class
Default value: undef
after_limits
Data type: Optional[String]
The name of the class you want to execute directly after the limits class.
You can use hiera to set this value. Here is an example:
wls_profile::weblogic::after_limits: my_module::my_class
Default value: undef
after_packages
Data type: Optional[String]
The name of the class you want to execute directly after the packages class.
You can use hiera to set this value. Here is an example:
wls_profile::weblogic::after_packages: my_module::my_class
Default value: undef
after_groups_and_users
Data type: Optional[String]
The name of the class you want to execute directly after the groups_and_usesr class.
You can use hiera to set this value. Here is an example:
wls_profile::weblogic::after_groups_and_usesr: my_module::my_class
Default value: undef
after_ssh_setup
Data type: Optional[String]
The name of the class you want to execute directly after the ssh_setup class.
You can use hiera to set this value. Here is an example:
wls_profile::weblogic::after_ssh_setup: my_module::my_class
Default value: undef
after_firewall
Data type: Optional[String]
The name of the class you want to execute directly after the firewall class.
You can use hiera to set this value. Here is an example:
wls_profile::weblogic::after_firewall: my_module::my_class
Default value: undef
after_java_software
Data type: Optional[String]
The name of the class you want to execute directly after the java_software class.
You can use hiera to set this value. Here is an example:
wls_profile::weblogic::after_java_software: my_module::my_class
Default value: undef
after_wls_software
Data type: Optional[String]
The name of the class you want to execute directly after the wls_software class.
You can use hiera to set this value. Here is an example:
wls_profile::weblogic::after_wls_software: my_module::my_class
Default value: undef
after_wls_patches
Data type: Optional[String]
The name of the class you want to execute directly after the wls_patches class.
You can use hiera to set this value. Here is an example:
wls_profile::weblogic::after_wls_patches: my_module::my_class
Default value: undef
after_em_license
Data type: Optional[String]
Default value: undef
after_fmw_software
Data type: Optional[String]
Default value: undef
after_wls_opatch
Data type: Optional[String]
Default value: undef
before_em_license
Data type: Optional[String]
Default value: undef
before_fmw_software
Data type: Optional[String]
Default value: undef
before_wls_opatch
Data type: Optional[String]
Default value: undef
em_license
Data type: Optional[String]
Default value: undef
fmw_software
Data type: Optional[String]
Default value: undef
wls_opatch
Data type: Optional[String]
Default value: undef
wls_profile::weblogic::em_license
This class will deploy the Enterprise Modules license.
wls_profile::weblogic::fmw_software
wls_profile::weblogic::fmw_software
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.
See the file "LICENSE" for the full license governing this code.
Parameters
The following parameters are available in the wls_profile::weblogic::fmw_software class:
file_name
Data type: Array[String[1]]
oracle_base
Data type: Stdlib::Absolutepath
The directory used as the base for all Oracle weblogic files.
This value is used in multiple places. To make sure in all classed the correct value is used, use the hiera key wls_profile::oracle_base to change it to your requested value.
Default value: /opt/oracle
middleware_home
Data type: Stdlib::Absolutepath
The Oracle middleware home directory.
This value is used in multiple places. To make sure in all classed the correct value is used, use the hiera key wls_profile::middleware_home to change it to your requested value.
Default value: /opt/oracle/middleware12
weblogic_home
Data type: Stdlib::Absolutepath
The directory used as WebLogic home
This value is used in multiple places. To make sure in all classed the correct value is used, use the hiera key wls_profile::weblogic_home to change it to your requested value.
Default value: /opt/oracle/middleware12/wlserver
jdk_home
Data type: Stdlib::Absolutepath
The location where the JDK is installed.
This value is used in multiple places. To make sure in all classed the correct value is used, use the hiera key wls_profile::jdk_home to change it to your requested value.
The default value is: /usr/java/jdk1.8.0_152
os_user
Data type: String[1]
The os user to use for WebLogic.
This value is used in multiple places. To make sure in all classed the correct value is used, use the hiera key wls_profile::basic_domain::os_user to change it to your requested value.
Default value: oracle
os_group
Data type: String[1]
The os group to use for WebLogic.
This value is used in multiple places. To make sure in all classed the correct value is used, use the hiera key wls_profile::basic_domain::os_group to change it to your requested value.
Default value: dba
source
Data type: String[1]
The location where the classes can find the software.
You can specify a local directory, a Puppet url or an http url.
This value is used in multiple places. To make sure in all classed the correct value is used, use the hiera key wls_profile::source to change it to your requested value.
The default is : puppet:///modules/software/
version
Data type: Wls_install::Versions
The version of WebLogic you want to use.
This value is used in multiple places. To make sure in all classed the correct value is used, use the hiera key wls_profile::version to change it to your requested value.
Valid values are:
103611111112121112121213122112211122121221312214Default value:12213
Default value: $wls_profile::weblogic_version
wls_profile::weblogic::java_software
wls_profile::weblogic::java_software
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.
See the file "LICENSE" for the full license governing this code.
Parameters
The following parameters are available in the wls_profile::weblogic::java_software class:
versionfull_versioncryptography_extension_filesourceurandom_fixrsa_key_size_fixx64alternatives_priority
version
Data type: String[1]
The version of java you want to use.
This value is used in multiple places. To make sure in all classed the correct value is used, use the hiera key wls_profile::java_version to change it to your requested value.
Default value: 8u152
full_version
Data type: String[1]
The full version of java you want to use.
This value is used in multiple places. To make sure in all classed the correct value is used, use the hiera key wls_profile::java_full_version to change it to your requested value.
Default value: jdk1.8.0_152
cryptography_extension_file
Data type: Optional[String[1]]
Cryptographic extension file to use.
Default value: jce_policy-8.zip
Default value: undef
source
Data type: String[1]
The location where the classes can find the software.
You can specify a local directory, a Puppet url or an http url.
This value is used in multiple places. To make sure in all classed the correct value is used, use the hiera key wls_profile::source to change it to your requested value.
The default is : puppet:///modules/software/
urandom_fix
Data type: Optional[Boolean]
Enable the urandom fix.
This parameter is deprecated and will be removed in a next version.
Default value: true
rsa_key_size_fix
Data type: Optional[Boolean]
Enable the RSA keysize fix.
Default value: true
x64
Data type: Boolean
Install x64 version of java.
Default value: true
alternatives_priority
Data type: Optional[Integer]
alternatives priority for jdk.
Default value is: 18001
wls_profile::weblogic::ssh_setup
wls_profile::weblogic::ssh_setup
This is required when copying the packed domain from an admin server to a WebLogic node. If you are building singles node WebLogic configurations, you can skip this class.
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::admin_server for an explanation on how to do this.
See the file "LICENSE" for the full license governing this code.
Parameters
The following parameters are available in the wls_profile::weblogic::ssh_setup class:
os_user
Data type: String[1]
The os user to use for WebLogic.
This value is used in multiple places. To make sure in all classed the correct value is used, use the hiera key wls_profile::basic_domain::os_user to change it to your requested value.
Default value: oracle
os_group
Data type: String[1]
The os group to use for WebLogic.
This value is used in multiple places. To make sure in all classed the correct value is used, use the hiera key wls_profile::basic_domain::os_group to change it to your requested value.
Default value: dba
private_key
Data type: String[1]
The private key to create for the os_user account.
The defaults contain a valid pair. It is recommended to specify your own values.
public_key
Data type: String[1]
The public key to create for the os_user account.
The defaults contain a valid pair. It is recommended to specify your own values.
wls_profile::weblogic::wls_opatch
wls_profile::weblogic::wls_opatch
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.
See the file "LICENSE" for the full license governing this code.
Parameters
The following parameters are available in the wls_profile::weblogic::wls_opatch class:
list
Data type: Hash
A Hash describing the WebLogic opatchupgrade you want be installed.
Default value is: {}
wls_profile::weblogic::wls_patches
wls_profile::weblogic::wls_patches
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.
The easiest and best way to specify your patches is to specify a level. An example of a patch level is JAN2021RU, meaning the JAN 2021 patch level update.
You can also add additional 'one-off's'. Use the list property to add these.
When you don't specify a patch windows, Puppet will never patch a running domain. It will however provide your installations with the specified patch level at the initial run or when the WebLogic domain is not running at the start of the Puppet run.
See the file "LICENSE" for the full license governing this code.
Parameters
The following parameters are available in the wls_profile::weblogic::wls_patches class:
levelversionmiddleware_homeorainst_dirjdk_homeos_userlistdomains_dirweblogic_homeos_groupweblogic_userweblogic_passwordadminserver_portnodemanager_portwait_for_nodemanagernodemanager_addressadminserver_addressjsse_enabledcustom_trusttrust_keystore_filepatch_windowlogoutputpatch_levels
level
Data type: String[1]
The specified patch level. The default value is 'NONE'.
version
Data type: Integer
The version of WebLogic you want to use.
This value is used in multiple places. To make sure in all classed the correct value is used, use the hiera key wls_profile::version to change it to your requested value.
Valid values are:
103611111112121112121213122112211122121221312214Default value:12213
middleware_home
Data type: String[1]
The Oracle middleware home directory.
This value is used in multiple places. To make sure in all classed the correct value is used, use the hiera key wls_profile::middleware_home to change it to your requested value.
Default value: /opt/oracle/middleware12
orainst_dir
Data type: String[1]
The directory where the orainst file is located.
jdk_home
Data type: String[1]
The location where the JDK is installed.
This value is used in multiple places. To make sure in all classed the correct value is used, use the hiera key wls_profile::jdk_home to change it to your requested value.
The default value is: /usr/java/jdk1.8.0_152
os_user
Data type: String[1]
The os user to use for WebLogic.
This value is used in multiple places. To make sure in all classed the correct value is used, use the hiera key wls_profile::basic_domain::os_user to change it to your requested value.
Default value: oracle
list
Data type: Hash
A Hash describing the WebLogic patches you want be installed.
Default value is: {}
domains_dir
Data type: Stdlib::Absolutepath
The top-level directory where the domain directories will reside in.
This value is used in multiple places. To make sure in all classed the correct value is used, use the hiera key wls_profile::domains_dir to change it to your requested value.
The default value is: /opt/oracle/domains
weblogic_home
Data type: Stdlib::Absolutepath
The directory used as WebLogic home
This value is used in multiple places. To make sure in all classed the correct value is used, use the hiera key wls_profile::weblogic_home to change it to your requested value.
Default value: /opt/oracle/middleware12/wlserver
os_group
Data type: String[1]
The os group to use for WebLogic.
This value is used in multiple places. To make sure in all classed the correct value is used, use the hiera key wls_profile::basic_domain::os_group to change it to your requested value.
Default value: dba
weblogic_user
Data type: String[1]
The WebLogic user account to bear all administration rights.
This value is used in multiple places. To make sure in all classed the correct value is used, use the hiera key wls_profile::weblogic_user to change it to your requested value.
Default value: weblogic
weblogic_password
Data type: Easy_type::Password
The password for the WebLogic account.
This value is used in multiple places. To make sure in all classed the correct value is used, use the hiera key wls_profile::weblogic_password to change it to your requested value.
Default value: Welcome01
adminserver_port
Data type: Integer
The IP port the admin server process will run and listen on.
This value is used in multiple places. To make sure in all classed the correct value is used, use the hiera key wls_profile::adminserver_port to change it to your requested value.
The default value is: 7001
nodemanager_port
Data type: Integer
The IP port the nodemanager listens on.
This value is used in multiple places. To make sure in all classed the correct value is used, use the hiera key wls_profile::nodemanager_port to change it to your requested value.
Default value: 5556
wait_for_nodemanager
Data type: Integer
The time in seconds we wait for the nodemanager to be started in the restart phase of the patching.
nodemanager_address
Data type: String[1]
The IP address the nodemanager will run and listen on.
This value is used in multiple places. To make sure in all classed the correct value is used, use the hiera key wls_profile::basic_domain::wls_domain::log_dir to change it to your requested value.
Default value: ::fqdn
adminserver_address
Data type: String[1]
The address the admin server process will run and listen on.
This value is used in multiple places. To make sure in all classed the correct value is used, use the hiera key wls_profile::adminserver_address to change it to your requested value.
The default value is: The fact fqdn
jsse_enabled
Data type: Boolean
Determine if you want to enable JSSE security.
custom_trust
Data type: Boolean
Determine if you want to use a custom trust or not.
trust_keystore_file
Data type: Optional[String[1]]
File specification of the trust keystore.
patch_window
Data type: Optional[String[1]]
The service window in which any patching will be executed.
Default value: undef
logoutput
Data type: Variant[Boolean,Enum['on_failure']]
log the outputs of Puppet exec and wls_exec or not.
When you specify true Puppet will log all output of exec types.
Valid values are:
truefalseon_failure
Default value: lookup( { name => 'logoutput', default_value => 'on_failure' })
patch_levels
Data type: Hash
wls_profile::weblogic::wls_software
wls_profile::weblogic::wls_software
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.
See the file "LICENSE" for the full license governing this code.
Parameters
The following parameters are available in the wls_profile::weblogic::wls_software class:
version
Data type: Wls_install::Versions
The version of WebLogic you want to use.
This value is used in multiple places. To make sure in all classed the correct value is used, use the hiera key wls_profile::version to change it to your requested value.
Valid values are:
103611111112121112121213122112211122121221312214Default value:12213
Default value: $wls_profile::weblogic_version
file_name
Data type: String[1]
The file name containing the Fusion middleware software to install.
This file is fetched from the location specified by the property source.
oracle_base
Data type: Stdlib::Absolutepath
The directory used as the base for all Oracle weblogic files.
This value is used in multiple places. To make sure in all classed the correct value is used, use the hiera key wls_profile::oracle_base to change it to your requested value.
Default value: /opt/oracle
middleware_home
Data type: Stdlib::Absolutepath
The Oracle middleware home directory.
This value is used in multiple places. To make sure in all classed the correct value is used, use the hiera key wls_profile::middleware_home to change it to your requested value.
Default value: /opt/oracle/middleware12
jdk_home
Data type: Stdlib::Absolutepath
The location where the JDK is installed.
This value is used in multiple places. To make sure in all classed the correct value is used, use the hiera key wls_profile::jdk_home to change it to your requested value.
The default value is: /usr/java/jdk1.8.0_152
os_user
Data type: String[1]
The os user to use for WebLogic.
This value is used in multiple places. To make sure in all classed the correct value is used, use the hiera key wls_profile::basic_domain::os_user to change it to your requested value.
Default value: oracle
os_group
Data type: String[1]
The os group to use for WebLogic.
This value is used in multiple places. To make sure in all classed the correct value is used, use the hiera key wls_profile::basic_domain::os_group to change it to your requested value.
Default value: dba
source
Data type: String[1]
The location where the classes can find the software.
You can specify a local directory, a Puppet url or an http url.
This value is used in multiple places. To make sure in all classed the correct value is used, use the hiera key wls_profile::source to change it to your requested value.
The default is : puppet:///modules/software/
fmw_infra
Data type: Boolean
Boolean specifying if you want WebLogic Fusion Middleware Infra installed.
Default value: false
Defined types
wls_profile::admin_server::managed_server
wls_profile::admin_server::managed_server
It is called once for every machine server combination you passed to wls_profile::admin_server::wls_servers.
Using hiera, you can customize some of the aspects of this process.
See the file "LICENSE" for the full license governing this code.
Parameters
The following parameters are available in the wls_profile::admin_server::managed_server defined type:
machine_name
Data type: String[1]
The machine name to create for this managed server
listenaddress
Data type: String[1]
The listen address for the managed server
domain_name
Data type: String[1]
The name of the WebLogic domain.
This will be used both as the REAL WebLogic domain name, and also be used by Puppet as a designator for Puppet resources. (e.g. the name before the slash my_domain/wls_queue1).
The change the domain name, use the hiera key: wls_profile::domain_name. This will make sure the correct domain name gets used in all classes.
The default value is: MYDOMAIN
server_arguments
Data type: Array
An Array containing the server startup arguments.
Default value is : []
server_defaults
Data type: Hash
a Hash describing the defauls to use when creating WebLogic servers.
Default value : {}
machine_defaults
Data type: Hash
a Hash describing the defauls to use when creating WebLogic machines.
Default value : {}
log_dir
Data type: Stdlib::Absolutepath
Default value: lookup('wls_profile::log_dir')
wls_profile::weblogic::private::start_managed_servers
The wls_profile::weblogic::private::start_managed_servers class.
Parameters
The following parameters are available in the wls_profile::weblogic::private::start_managed_servers defined type:
schedule_namedomains_dirweblogic_homemiddleware_homejdk_homeos_useros_groupweblogic_userweblogic_passwordadminserver_portnodemanager_portadminserver_addressjsse_enabledcustom_trustwait_for_nodemanagertrust_keystore_filelogoutput
schedule_name
Data type: String[1]
domains_dir
Data type: Stdlib::Absolutepath
weblogic_home
Data type: Stdlib::Absolutepath
middleware_home
Data type: Stdlib::Absolutepath
jdk_home
Data type: Stdlib::Absolutepath
os_user
Data type: String[1]
os_group
Data type: String[1]
weblogic_user
Data type: String[1]
weblogic_password
Data type: Easy_type::Password
adminserver_port
Data type: Integer
nodemanager_port
Data type: Integer
adminserver_address
Data type: String[1]
jsse_enabled
Data type: Boolean
custom_trust
Data type: Boolean
wait_for_nodemanager
Data type: Integer
trust_keystore_file
Data type: Optional[String[1]]
Default value: undef
logoutput
Data type: Variant[Boolean,Enum['on_failure']]
Default value: lookup( { name => 'logoutput', default_value => 'on_failure' })
wls_profile::weblogic::private::stop_managed_servers
What are plans?
Modules can contain plans that take action outside of a desired state managed by Puppet. It’s perfect for troubleshooting or deploying one-off changes, distributing scripts to run across your infrastructure, or automating changes that need to happen in a particular order as part of an application deployment.
Changelog
All notable changes to this project will be documented in this file.
Release 0.32.2
Bug fixes
- [fmw_cluster] Fix when using SSL ports
Release 0.32.1
Bug fixes
[fmw_cluster] Fix for clusters other than SOA
Release 0.32.0
Features
- [fmw_cluster] Initial implementation
Maintenance
- [release] Update saz/limits version dependency
Release 0.31.0
Features
- [wls_domain] expose domain parameter rcu_honor_omf
Release 0.30.0
Features
- [wls_domain] Expose repository_sys_user from domain
Release 0.29.1
Bug fixes
- [wls_patches] Fix waiting for started nodemanager
Release 0.29.0
Features
- [copy_domain] Allow control over the way the packed domain is fetched
Release 0.28.0
Features
- [wls_domain] Export the rcu_soa_profile parameter from wls_install::domain
Bug fixes
- [release] Update version dependencies
Release 0.27.0
Features
- [wls_startup] Add support for Environment file
- [wls_domain] Add support for providing wlst_args
- [release] Remove support for RedHat and OracleLinux 6
Bug fixes
- [docs] Fix some documentation issues
Release 0.26.2
Bug fixes
- [release] Update dependencies for augeasproviders_core en firewall
- [wls_patches] Remove dependency on new stdlib
Release 0.26.1
Bug fixes
- [release] Update version of dependencies
- [wls_patches] Replace deprecated functions
Release 0.26.0
Features
- [core] Add support for Puppet 8
- [copy_domain] Exposed the nodemanager properties as nodemanager_properties
- [wls_domain] Exposed the nodemanager properties as nodemanager_properties
Release 0.25.0
Features
- [core] Add support for EL9
- [release] Update dependencies
Release 0.24.0
Features
- [data] Add OCT2022 PSU’s
Release 0.23.0
Features
- [wls_domain,copy_domain] Add support for java_update_window
Bug fixes
- [docs] Re-add documentation to puppet source
Release 0.22.0
Bug fixes
- [em_license] Fix for using EM profile classed together
Release 0.21.0
Features
- [wls_patches] Warn when patchlevel not defined
- [data] Added JUL2022RU patchlevels for 12.2.1.3, 12.2.1.4
- [data] Added APR2022RU patchlevels for 12.2.1.3, 12.2.1.4 and 14.1
- [stop_managed_servers] Removed debugging notice
Release 0.20.0
Features
- [wls_patches] Only stop the managed servers on current node for patching
- [copy_domain] Also add the basic wls_setting information to the node
Bugs
- [wls_domain] Remove hard coded machine name
- [wls_servers] Change default port for nodemanager from 7001 to 5556
- [managed_server] Pass the log directory when defining server
- [release] update required version of easy_type
Release 0.19.0
Features
-[release] Add support for AlmaLinux and RockyLinux
Bugs
- [em_license] Use license::activate instead of license::available
Release 0.18.0
Features
- [data] Add January 2022 PSU patch levels for 1.2.1.3, 12.2.1.4 and 14.1
Bugs
- [wls_patches] Remove unused variable
Release 0.17.1
Bugs
- [weblogic] ADF doesn’t need additional fmw software
Release 0.17.0
Features
- [core] Add fact caching
- [wls_patches] Adjust for new fact structure of wls_install
Bugs
- [core] Fix installation and creation of ADF
Release 0.15.3
Bugs
- [copy_domain] Add support for different adminserver ports
- [wls_patches] Fix stopping nodemanager
Release 0.15.2
Bugs
- [plan/apply_patches] Fix typo
Release 0.15.1
Bugs
- [wls_patches] Stop the wlst daemon for sane restarts
Release 0.15.0
Features
- [wls_domain] Add support for administration_port_enabled
Release 0.14.0
Features
- [copy_domain] Add support for custom identities
Release 0.13.0
Features
- [java_software] Support skipping JCE installation
Release 0.12.1
Bugs
- [groups_and_users] Use defined os_user for directory too
Release 0.12.0
Features
- [wls_domain] Add support for specifying a puppet domain alias
Bugs
- [wls_domain] Use domain alias for identifying Adminserver
Release 0.11.1
Chore
- [data] Remove default managed servers
Release 0.11.0
Features
- [apply_patches] Add initial bolt plan to apply WebLogic patches from bolt
- [wls_patches] Add patchlevel functionality
Release 0.10.3
Bugs
- [groups_and_users] Fix OS password generation
Release 0.10.2
Bugs
- [groups_and_users] Leave hashing of os passwords to class
Release 0.10.1
Bugs
- [release] Add WebLogic 14.1.1.0 support to rhe README
- [basic_domain] replace deprecated staged_contain for ordered_steps
Release 0.10.0
Features
- [release] Add support for puppet 7 to the metadata
Release 0.9.0
Features
- [weblogic] Automaticaly fetch EM licenses
Release 0.8.1
Bugfixes
- [wls_startup] Use custom trusts for startup
- [java_software] Add entropy fix
Release 0.8.0
Features
- [java_software] Start using module puppetlabs-java
Release 0.7.0
Features
- [wls_domain] Add support for ssl communication
Bugfixes
- [core] Remove hardcoded passwords
Release 0.6.1
Bugfixes
- [wls_domain] Add repo_sys_password to list of keys to convert to Sensitive
Release 0.6.0
Features
- [core] Generated password added
- [core] Add support for Sensitive data
- [weblogic] Don’t install fusion software when install_type is ADF
Bugfixes
- [core] Also include original lookups of Sensitive passwords in lookup options
Release 0.5.1
Features
- [wls_domain] Add support for more fusion domain types
- [release] Update readme to indicate support for WebLogic 12.2.1.4
Release 0.5.0
Features
[core] Add basic support for Solaris
Release 0.4.0
Features
- [core] Add AIX support
Release 0.3.3
Bugfixes
- [wls_domain] Add extra properties parameter
Release 0.3.2
Bugfixes
- [core] Export the download_dir and temp_dir parameters
- [copy_domain] Fix directory issues
Release 0.3.1
Features
None
Bugfixes
-[copy_domain] Fix used app dir
Release 0.3.0
Features
- [wls_opatch] Initial implementation
Bugfixes
None
Release 0.2.1
Features
None
Bugfixes
- [wls_patches] Fix puppet type for the patches
- [weblogic] Add missing fmw_software variables
- [core] Add support for Sensitive data
- [packages] Use Hash, like other profiles
Release 0.2.0
Features
- Add basic support for Fusion Middleware
- Make ready for Puppet 6
Bugfixes
None
Release 0.1.4
Features
None
Bugfixes
- Fix used resource types in wls_jms
Release 0.1.3
Features
- Manage firewall ports on both RHEL5 and RHEL > 5 systems
- Add unit and acceptance tests
- Remove reliance on old defauts
- implement EM Quality control
Bugfixes
None
Known Issues
None
Release 0.1.2
Features
None
Bugfixes
Fix README
Known Issues
None
Release 0.1.1
Features
None
Bugfixes
Fix README
Known Issues
None
Release 0.1.0
Features
- Install basic Weblogic systems
Bugfixes
None
Known Issues
- No good firewall implementation
- No good wls_patches implementation
Dependencies
- enterprisemodules/easy_type (>= 2.39.0 < 4.0.0)
- enterprisemodules/wls_config (>= 3.14.0 < 4.0.0)
- enterprisemodules/wls_install (>= 4.12.7 < 5.0.0)
- ipcrm-echo (>= 0.1.7 < 1.0.0)
- puppet-augeasproviders_core (>= 2.1.4 < 5.0.0)
- puppet-augeasproviders_sysctl (>= 2.2.0 < 4.0.0)
- saz-limits (>= 3.0.2 < 6.0.0)
- puppetlabs-firewall (>= 1.12.0 < 9.0.0)
- puppet-firewalld (>= 4.0.0 < 6.0.0)
- puppetlabs-java (>= 6.3.0 < 12.0.0)
- puppet-archive (>= 1.1.0 < 8.0.0)
- puppetlabs-sshkeys_core (>= 1.0.1 < 3.0.0)
- puppetlabs-stdlib (>= 4.25.0 < 10.0.0)