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.
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
wls_profile::weblogic::apply_patches: Apply the in hiera specified WebLogic patches to the specified target
wls_profile
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
Data type: String[1]
Data type: Integer
Data type: String[1]
Data type: String[1]
Data type: Stdlib::Absolutepath
Data type: Stdlib::Absolutepath
Data type: String[1]
Data type: String[1]
Data type: Stdlib::Absolutepath
Data type: Stdlib::Absolutepath
Data type: Stdlib::Absolutepath
Data type: String[1]
Data type: Integer
Data type: Stdlib::Absolutepath
Data type: String[1]
Data type: String[1]
Data type: Hash
Data type: String[1]
Data type: Stdlib::Absolutepath
Data type: Stdlib::Absolutepath
Data type: Easy_type::Password
Data type: String[1]
Data type: Wls_install::Versions
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
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.
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.
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_classYou 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_classSometimes organizations use different modules and mechanisms to implement a feature, and you want to skip the class:
wls_profile::admin_server::pack_domain: skipOr provide your own implementation:
wls_profile::admin_server::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 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.
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
Data type: Optional[String]
Use this value if you want to skip or use your own class for stage basic_domain.
You can use hiera to set this value. Here is an example:
wls_profile::admin_server::basic_domain: my_module::my_classYou can use hiera to set this value. Here is an example:
wls_profile::admin_server::basic_domain: skipDefault value: undef
Data type: Optional[String]
Use this value if you want to skip or use your own class for stage wls_servers.
You can use hiera to set this value. Here is an example:
wls_profile::admin_server::wls_servers: my_module::my_classYou can use hiera to set this value. Here is an example:
wls_profile::admin_server::wls_servers: skipDefault value: undef
Data type: Optional[String]
Use this value if you want to skip or use your own class for stage wls_cluster.
You can use hiera to set this value. Here is an example:
wls_profile::admin_server::wls_cluster: my_module::my_classYou can use hiera to set this value. Here is an example:
wls_profile::admin_server::wls_cluster: skipDefault value: undef
Data type: Optional[String]
Use this value if you want to skip or use your own class for stage wls_datasources.
You can use hiera to set this value. Here is an example:
wls_profile::admin_server::wls_datasources: my_module::my_classYou can use hiera to set this value. Here is an example:
wls_profile::admin_server::wls_datasources: skipDefault value: undef
Data type: Optional[String]
Use this value if you want to skip or use your own class for stage wls_jms.
You can use hiera to set this value. Here is an example:
wls_profile::admin_server::wls_jms: my_module::my_classYou can use hiera to set this value. Here is an example:
wls_profile::admin_server::wls_jms: skipDefault value: undef
Data type: Optional[String]
Use this value if you want to skip or use your own class for stage wls_users_and_groups.
You can use hiera to set this value. Here is an example:
wls_profile::admin_server::wls_users_and_groups: my_module::my_classYou can use hiera to set this value. Here is an example:
wls_profile::admin_server::wls_users_and_groups: skipDefault value: undef
Data type: Optional[String]
Use this value if you want to skip or use your own class for stage pack_domain.
You can use hiera to set this value. Here is an example:
wls_profile::admin_server::pack_domain: my_module::my_classYou can use hiera to set this value. Here is an example:
wls_profile::admin_server::pack_domain: skipDefault value: undef
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_classDefault value: undef
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_classDefault value: undef
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_classDefault value: undef
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_classDefault value: undef
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_classDefault value: undef
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_classDefault value: undef
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_classDefault value: undef
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_classDefault value: undef
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_classDefault value: undef
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_classDefault value: undef
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_classDefault value: undef
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_classDefault value: undef
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_classDefault value: undef
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_classDefault value: undef
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.
The following parameters are available in the wls_profile::admin_server::pack_domain class:
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
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
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
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
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
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
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
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.
The following parameters are available in the wls_profile::admin_server::wls_cluster class:
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
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
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
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: consensuswls_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.
The following parameters are available in the wls_profile::admin_server::wls_datasources class:
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
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.
The following parameters are available in the wls_profile::admin_server::wls_jms class:
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.
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.
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.
Data type: Hash
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.
The following parameters are available in the wls_profile::admin_server::wls_servers class:
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
Data type: Hash
Default value: $wls_profile::servers
Data type: Hash
Data type: Hash
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 following parameters are available in the wls_profile::admin_server::wls_users_and_groups class:
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.
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
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.
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
Data type: Optional[String]
Use this value if you want to skip or use your own class for stage weblogic.
You can use hiera to set this value. Here is an example:
wls_profile::basic_domain::weblogic: my_module::my_classYou can use hiera to set this value. Here is an example:
wls_profile::basic_domain::weblogic: skipDefault value: undef
Data type: Optional[String]
Use this value if you want to skip or use your own class for stage wls_domain.
You can use hiera to set this value. Here is an example:
wls_profile::basic_domain::wls_domain: my_module::my_classYou can use hiera to set this value. Here is an example:
wls_profile::basic_domain::wls_domain: skipDefault value: undef
Data type: Optional[String]
Use this value if you want to skip or use your own class for stage wls_startup.
You can use hiera to set this value. Here is an example:
wls_profile::basic_domain::wls_startup: my_module::my_classYou can use hiera to set this value. Here is an example:
wls_profile::basic_domain::wls_startup: skipDefault value: undef
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_classDefault value: undef
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_classDefault value: undef
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_classDefault value: undef
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_classDefault value: undef
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_classDefault value: undef
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_classDefault value: undef
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.
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
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
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
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
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
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
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
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
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
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
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
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
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
Data type: Optional[Integer]
The common secure administration port for this WebLogic Server domain. (Requires you to enable the administration port.)
Data type: Optional[Integer]
SSL port to use for the Admin server.
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
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
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
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
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
Data type: Boolean
A boolean value specifying if you want to enable bam.
Default value: false
Data type: Boolean
A boolean value specifying if you want to enable b2b.
Default value: false
Data type: Boolean
A boolean value specifying if you want to enable ess.
Default value: false
Data type: Boolean
A boolean value specifying if you want to enable development mode.
Default value: false
Data type: Integer
The time in seconds Puppet waits for the nodemanager to start before declaring an error.
Default value: 20
Data type: Hash
A Hash containing settings (of type wls_server) to define for the Admin server.
The default value is: {}
Data type: Boolean
Data type: Optional[String[1]]
Data type: Optional[String[1]]
Data type: Boolean
Data type: Array
Data type: Stdlib::Absolutepath
Data type: Boolean
Data type: Stdlib::Absolutepath
Data type: Optional[String[1]]
Data type: Optional[Easy_type::Password]
Default value: undef
Data type: Optional[Easy_type::Password]
Default value: undef
Data type: Optional[String[1]]
Default value: undef
Data type: Optional[String[1]]
Default value: undef
Data type: Optional[Easy_type::Password]
Default value: undef
Data type: Optional[String[1]]
Default value: undef
Data type: Optional[Easy_type::Password]
Default value: undef
Data type: Optional[Easy_type::Password]
Default value: undef
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.
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
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
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
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
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
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
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
Data type: Boolean
Data type: Boolean
Data type: Optional[String[1]]
Data type: Optional[Easy_type::Password]
Default value: lookup('wls_profile::basic_domain::wls_domain::trust_keystore_passphrase', { 'default_value' => undef })
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.
The following parameters are available in the wls_profile::node class:
weblogiccopy_domainwls_startupbefore_weblogicbefore_copy_domainbefore_wls_startupafter_weblogicafter_copy_domainafter_wls_startup
Data type: Optional[String]
Use this value if you want to skip or use your own class for stage weblogic.
You can use hiera to set this value. Here is an example:
wls_profile::node::weblogic: my_module::my_classYou can use hiera to set this value. Here is an example:
wls_profile::node::weblogic: skipDefault value: undef
Data type: Optional[String]
Use this value if you want to skip or use your own class for stage copy_domain.
You can use hiera to set this value. Here is an example:
wls_profile::node::copy_domain: my_module::my_classYou can use hiera to set this value. Here is an example:
wls_profile::node::copy_domain: skipDefault value: undef
Data type: Optional[String]
Use this value if you want to skip or use your own class for stage wls_startup.
You can use hiera to set this value. Here is an example:
wls_profile::node::wls_startup: my_module::my_classYou can use hiera to set this value. Here is an example:
wls_profile::node::wls_startup: skipDefault value: undef
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_classDefault value: undef
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_classDefault value: undef
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_classDefault value: undef
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_classDefault value: undef
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_classDefault value: undef
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_classDefault value: undef
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.
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
Data type: Optional[String]
Use this value if you want to skip or use your own class for stage sysctl.
You can use hiera to set this value. Here is an example:
wls_profile::weblogic::sysctl: my_module::my_classYou can use hiera to set this value. Here is an example:
wls_profile::weblogic::sysctl: skipDefault value: undef
Data type: Optional[String]
Use this value if you want to skip or use your own class for stage limits.
You can use hiera to set this value. Here is an example:
wls_profile::weblogic::limits: my_module::my_classYou can use hiera to set this value. Here is an example:
wls_profile::weblogic::limits: skipDefault value: undef
Data type: Optional[String]
Use this value if you want to skip or use your own class for stage packages.
You can use hiera to set this value. Here is an example:
wls_profile::weblogic::packages: my_module::my_classYou can use hiera to set this value. Here is an example:
wls_profile::weblogic::packages: skipDefault value: undef
Data type: Optional[String]
Use this value if you want to skip or use your own class for stage groups_and_users.
You can use hiera to set this value. Here is an example:
wls_profile::weblogic::groups_and_users: my_module::my_classYou can use hiera to set this value. Here is an example:
wls_profile::weblogic::groups_and_users: skipDefault value: undef
Data type: Optional[String]
Use this value if you want to skip or use your own class for stage ssh_setup.
You can use hiera to set this value. Here is an example:
wls_profile::weblogic::ssh_setup: my_module::my_classYou can use hiera to set this value. Here is an example:
wls_profile::weblogic::ssh_setup: skipDefault value: undef
Data type: Optional[String]
Use this value if you want to skip or use your own class for stage firewall.
You can use hiera to set this value. Here is an example:
wls_profile::weblogic::firewall: my_module::my_classYou can use hiera to set this value. Here is an example:
wls_profile::weblogic::firewall: skipDefault value: undef
Data type: Optional[String]
Use this value if you want to skip or use your own class for stage java_software.
You can use hiera to set this value. Here is an example:
wls_profile::weblogic::java_software: my_module::my_classYou can use hiera to set this value. Here is an example:
wls_profile::weblogic::java_software: skipDefault value: undef
Data type: Optional[String]
Use this value if you want to skip or use your own class for stage wls_software.
You can use hiera to set this value. Here is an example:
wls_profile::weblogic::wls_software: my_module::my_classYou can use hiera to set this value. Here is an example:
wls_profile::weblogic::wls_software: skipDefault value: undef
Data type: Optional[String]
Use this value if you want to skip or use your own class for stage wls_patches.
You can use hiera to set this value. Here is an example:
wls_profile::weblogic::wls_patches: my_module::my_classYou can use hiera to set this value. Here is an example:
wls_profile::weblogic::wls_patches: skipDefault value: undef
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_classDefault value: undef
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_classDefault value: undef
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_classDefault value: undef
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_classDefault value: undef
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_classDefault value: undef
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_classDefault value: undef
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_classDefault value: undef
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_classDefault value: undef
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_classDefault value: undef
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_classDefault value: undef
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_classDefault value: undef
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_classDefault value: undef
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_classDefault value: undef
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_classDefault value: undef
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_classDefault value: undef
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_classDefault value: undef
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_classDefault value: undef
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_classDefault value: undef
Data type: Optional[String]
Default value: undef
Data type: Optional[String]
Default value: undef
Data type: Optional[String]
Default value: undef
Data type: Optional[String]
Default value: undef
Data type: Optional[String]
Default value: undef
Data type: Optional[String]
Default value: undef
Data type: Optional[String]
Default value: undef
Data type: Optional[String]
Default value: undef
Data type: Optional[String]
Default value: undef
This class will deploy the Enterprise Modules license.
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.
The following parameters are available in the wls_profile::weblogic::fmw_software class:
Data type: Array[String[1]]
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
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
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
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
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
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
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/
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
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.
The following parameters are available in the wls_profile::weblogic::java_software class:
versionfull_versioncryptography_extension_filesourceurandom_fixrsa_key_size_fixx64alternatives_priority
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
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
Data type: Optional[String[1]]
Cryptographic extension file to use.
Default value: jce_policy-8.zip
Default value: undef
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/
Data type: Optional[Boolean]
Enable the urandom fix.
This parameter is deprecated and will be removed in a next version.
Default value: true
Data type: Optional[Boolean]
Enable the RSA keysize fix.
Default value: true
Data type: Boolean
Install x64 version of java.
Default value: true
Data type: Optional[Integer]
alternatives priority for jdk.
Default value is: 18001
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.
The following parameters are available in the wls_profile::weblogic::ssh_setup class:
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
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
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.
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
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.
The following parameters are available in the wls_profile::weblogic::wls_opatch class:
Data type: Hash
A Hash describing the WebLogic opatchupgrade you want be installed.
Default value is: {}
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.
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
Data type: String[1]
The specified patch level. The default value is 'NONE'.
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
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
Data type: String[1]
The directory where the orainst file is located.
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
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
Data type: Hash
A Hash describing the WebLogic patches you want be installed.
Default value is: {}
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
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
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
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
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
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
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
Data type: Integer
The time in seconds we wait for the nodemanager to be started in the restart phase of the patching.
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
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
Data type: Boolean
Determine if you want to enable JSSE security.
Data type: Boolean
Determine if you want to use a custom trust or not.
Data type: Optional[String[1]]
File specification of the trust keystore.
Data type: Optional[String[1]]
The service window in which any patching will be executed.
Default value: undef
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' })
Data type: Hash
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.
The following parameters are available in the wls_profile::weblogic::wls_software class:
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
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.
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
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
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
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
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
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/
Data type: Boolean
Boolean specifying if you want WebLogic Fusion Middleware Infra installed.
Default value: false
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.
The following parameters are available in the wls_profile::admin_server::managed_server defined type:
Data type: String[1]
The machine name to create for this managed server
Data type: String[1]
The listen address for the managed server
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
Data type: Array
An Array containing the server startup arguments.
Default value is : []
Data type: Hash
a Hash describing the defauls to use when creating WebLogic servers.
Default value : {}
Data type: Hash
a Hash describing the defauls to use when creating WebLogic machines.
Default value : {}
Data type: Stdlib::Absolutepath
Default value: lookup('wls_profile::log_dir')
The wls_profile::weblogic::private::start_managed_servers class.
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
Data type: String[1]
Data type: Stdlib::Absolutepath
Data type: Stdlib::Absolutepath
Data type: Stdlib::Absolutepath
Data type: Stdlib::Absolutepath
Data type: String[1]
Data type: String[1]
Data type: String[1]
Data type: Easy_type::Password
Data type: Integer
Data type: Integer
Data type: String[1]
Data type: Boolean
Data type: Boolean
Data type: Integer
Data type: Optional[String[1]]
Default value: undef
Data type: Variant[Boolean,Enum['on_failure']]
Default value: lookup( { name => 'logoutput', default_value => 'on_failure' })
The wls_profile::weblogic::private::stop_managed_servers class.
The following parameters are available in the wls_profile::weblogic::private::stop_managed_servers defined type:
Data type: String[1]
Data type: Variant[Boolean,Enum['on_failure']]
Default value: lookup( { name => 'logoutput', default_value => 'on_failure' })
This bolt plan applies the patches specified in the hieradata, to the node it is running on. Because the service window is set to ALWAYS (virtualy that is), the patching will start immediately. If the WebLogic domain is running, it will be stopped before the patches are applied and started after the patches are applied. It will only restart managed servers that were running before the patching started.#
See the file "LICENSE" for the full license governing this code.
bolt plan run wls_profile::weblogic::apply_patches targets=myserver1,myserver2The following parameters are available in the wls_profile::weblogic::apply_patches plan:
Data type: TargetSpec
The WebLogic node(s) you want to patch