wls_config
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, 2016.4.x
- Puppet >=4.10.8 < 9.0.0
- , , , , , , , , , ,
Tasks:
- start_managed_servers
- stop_adminserver
- stop_managed_servers
Start using this module
Add this module to your Puppetfile:
mod 'enterprisemodules-wls_config', '3.23.0'
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
This module allows you to configure and manage an Oracle WebLogic or Fusion middleware stack. It is part of our family of Puppet modules to install, manage and secure Oracle WebLogic and Fusion Middleware with Puppet. Besides the wls_config
module, this family also contains:
- wls_install For installing an Oracle WebLogic and other Fusion products
Experience the Power of Puppet for Oracle WebLogic
Installing Oracle WebLogic and/or Fusion software and managing your WebLogic domain configuration can be hard. With Puppet at your side, you get super-powers when installing and managing Oracle WebLogic. If you want to play and experiment with this please take a look at our playgrounds.
License
This is a commercially licensed module. But you can use the module on VirtualBox based development systems for FREE. You can request a FREE trial license here
Check the License for details.
Description
The wls_config
module extends the Puppet language to contain types needed to create and manage the lifecycle of objects within your Oracle Weblogic and Fusion Middleware installation. Instead of writing complex WLST scripts, using this module, you can now define your WebLogic configuration in an easy declarative way.
The puppet wls_config
module allows you to manage almost everything that is manageable in a WebLogic domain. For queue's and topics to datasources clusters and security policies. Here is a list of some of the objects you can manage with puppet when using this module:
wls_setting
wls_domain
wls_deployment
wls_domain
wls_user
wls_authentication_provider
wls_identity_asserter
wls_machine
wls_server
wls_server_channel
wls_cluster
wls_singleton_service
wls_coherence_cluster
wls_coherence_server
wls_server_template
wls_dynamic_cluster
wls_virtual_host
wls_workmanager_constraint
wls_workmanager
wls_datasource
wls_file_persistence_store
wls_jdbc_persistence_store
wls_jmsserver
wls_safagent
wls_jms_module
wls_jms_quota
wls_jms_subdeployment
wls_jms_queue
wls_jms_topic
wls_jms_connection_factory
wls_jms_template
wls_saf_remote_context
wls_saf_error_handler
wls_saf_imported_destination
wls_saf_imported_destination_object
wls_foreign_server
wls_foreign_server_object
wls_mail_session
wls_multi_datasource
wls_jms_bridge_destination
wls_messaging_bridge
Check here to see the full documentation for this module.
Setup
Requirements
The wls_config
module requires:
- Puppet module
enterprisemodules-easy_type
installed. - Puppet version 3.0 or higher. Can be Puppet Enterprise or Puppet Open Source
- WebLogic 10g or higher
- A valid Oracle Weblogic or Fusion license
- A valid Enterprise Modules license for usage.
- Runs on most Linux systems.
- Runs on Solaris
- Windows systems are NOT supported
We support WebLogic versions:
- WebLogic 10g
- WebLogic 11g
- WebLogic 12.1.2
- WebLogic 12.1.3
- WebLogic 12.2.1.2
- WebLogic 12.2.1.3
- WebLogic 12.2.1.4
- WebLogic 14.1.1.0
And Fusion versions:
- WebLogic 10g
- WebLogic 11g
- WebLogic 12c ( 12.1.1, 12.1.2, 12.1.3, 12.2.1.2 12.2.1.3, 12.2.1.4)
Installing the wls_config module
To install these modules, you can use a Puppetfile
mod 'enterprisemodules/wls_config' ,'3.0.x'
Then use the librarian-puppet
or r10K
to install the software.
You can also install the software using the puppet module
command:
puppet module install enterprisemodules-wls_config
Usage
Building a total WebLogic or Fusion setup requires quite some work. To help you, we have built some examples. The repo contains a demonstration of a simple WebLogic installation.
Reference
Here you can find some more information regarding this puppet module:
Here are a related blog posts:
- Introducing version 3 of wls_config
- Know thy WebLogic configuration using Puppet
- Manage your WebLogic JMS config with Puppet
- Using Puppet to install and manage your WebLogic infrastructure
Some example code:
Limitations
This module runs on Solaris, AIX and most Linux versions. It requires a puppet version higher than 4. The module does NOT run on windows systems.
Reference
Table of Contents
Defined types
Resource types
wls_authentication_provider
: This resource allows you to manage authentication providers in a WebLogic domain. Here is an example on how you should use this: wls_auwls_cluster
: Allows you to manage a WebLogic cluster in a WebLogic domain. Here is an example on how you should use this: wls_cluster { 'WlsCluster'wls_coherence_cluster
: This resource allows you to manage a coherence cluster in a WebLogic domain. Here is an example on how you should use this: wls_coherenwls_coherence_server
: This resource allows you to manage a coherence server in an WebLogic domain. Here is an example on how you should use this: wls_coherenwls_datasource
: This resource allows you to manage a datasource in an WebLogic domain. Here is an example on how you should use this: # this will use dwls_default_role_mapper
: This resource allows you to manage Role Mappers in weblogic.wls_deployment
: This resource allows you to manage a cluster in an WebLogic domain. Here is an example on how you should use this: # 'jersey-bundle' wiwls_domain
: This resource allows you to manage domain options. This resource allows you to make changes to the existing WebLogic domain. You cannot creawls_domain_partition
: This resource allows you to manage domain partitions in an WebLogic 12.2.1 domain.wls_domain_partition_resource_group
: This resource allows you to manage resource group in an WebLogic 12.2.1 domain.wls_domain_partition_resource_group_deployment
: This resource allows you to manage deployments in a resource group of a domain partition in an WebLogic 12.2.1 domain.wls_dynamic_cluster
: This resource allows you to manage a dynamic cluster in an WebLogic domain. Here is an example on how you should use this: wlsdynamicwls_exec
: This resource allows you to execute a wlst command or script in the context. This is a fallback resource. This means you should use it withwls_file_persistence_store
: This resource allows you to manage a file persistence stores in an WebLogic domain. Here is an example on how to use the `wls_file_persistenwls_foreign_jndi_provider
: This resource allows you to manage a foreign jndi provider in an WebLogic domain. Here is an example on how you should use this: wls_fowls_foreign_jndi_provider_link
: This resource allows you to manage a datasource in an WebLogic domain. Here is an example on how you should use this: wlsforeign_jndiwls_foreign_server
: This resource allows you to manage foreign servers in a JMS Module of a WebLogic domain. Here is an example on how you should use this:wls_foreign_server_object
: This resource allows you to manage a foreign server object in a JMS Module of a WebLogic domain. Here is an example on how you should use thwls_group
: This resource allows you to manage group in a WebLogic Security Realm. Here is an example on how you should use this: wls_group { 'Supewls_identity_asserter
: This resource allows you to manage Identity Asserters in an WebLogic domain. Here is an example on how you should use this: wls_authentwls_jdbc_persistence_store
: This resource allows you to manage a JDBC persistence stores in an WebLogic domain. Here is an example on how you should use this: wls_wls_jms_bridge_destination
: This resource allows you to manage a jms bridge destination in an WebLogic domain. Here is an example on how you should use this: wls_jwls_jms_connection_factory
: This resource allows you to manage a connection factory in a JMS Module of a WebLogic domain. Here is an example on how you should use this:wls_jms_module
: This resource allows you to manage a JMS module in an WebLogic domain. Here is an example on how you should use this: wls_jms_module {wls_jms_queue
: This resource allows you to manage a Queue in a JMS Module of a WebLogic domain. Here is an example on how you should use this: wls_jmswls_jms_quota
: This resource allows you to manage a Quota in a JMS module of a WebLogic domain. Here is an example on how you should use this: wls_jmswls_jms_security_policy
: This resource allows you to manage security authorization policies in an WebLogic Security Realm.wls_jms_sort_destination_key
: This resource allows you to manage the sort destination key in a JMS module of a WebLogic domain. Here is an example on how you should use twls_jms_subdeployment
: This resource allows you to manage a JMS subdeployment in a JMS module of a WebLogic domain. Here is an example on how you should use this:wls_jms_template
: This resource allows you to manage a template in a JMS Module of a WebLogic domain. Here is an example on how you should use this: wls_wls_jms_topic
: This resource allows you to manage a Tpoic in a JMS Module of a WebLogic domain. Here is an example on how you should use this: wls_jmswls_jmsserver
: This resource allows you to manage a jmsserver in an WebLogic domain. Here is an example on how you should use this: wls_jmsserver { 'jwls_jndi_security_policy
: This resource allows you to manage jndi security authorization policies in an WebLogic Security Realm. Here is an example on how you shouldwls_machine
: This resource allows you to manage machine in an WebLogic domain. Here is an example on how you should use this: wls_machine { 'test2':wls_mail_session
: This resource allows you to manage a mail_session in an WebLogic domain. Here is an example on how you should use this: wls_mail_sessiowls_managed_executor_service_template
: Weblogic Server provides a preconfigured, default ManagedExecutorService for each application, and applications can easily use it in web or Ewls_managedserver
: control a managed server or cluster state like running,stop,restart Type for managed server control like start, running, abort and stop a mawls_messaging_bridge
: This resource allows you to manage a messaging bridge in an WebLogic domain. Here is an example on how you should use this: wls_messagiwls_migratable_target
: This resource allows you to managed migratable targets in a WebLogic domain. Here is an example on how you should use this: wls_migratawls_multi_datasource
: This resource allows you to manage a multi datasource in an WebLogic domain. Here is an example on how you should use this: wls_multi_dwls_opatch
: This resource allows you to manage opatch patches on a specific middleware home. wls_opatch {'/opt/oracle/middleware12c:16175470': ensurewls_path_service
: This resource allows you to manage path servers Here is an example on how you should use this: wls_path_service { 'jmy_service':wls_rcu
: This is the Oracle WebLogic RCU ( Repository creation utility) installer typewls_resource_group_template
: This resource allows you to manage resource group template in an WebLogic 12.2.1 domain.wls_resource_group_template_deployment
: TThis resource allows you to manage deployments in a resource group template in an WebLogic 12.2.1 domain.wls_role
: This resource allows you to manage roles an WebLogic Secuirty Realm.wls_saf_error_handler
: This resource allows you to manage a SAF Error Handler in a JMS Module of a WebLogic domain. Here is an example on how you should use this:wls_saf_imported_destination
: This resource allows you to manage a SAF imported destinations in a JMS Module of a WebLogic domain. Here is an example on how you should uswls_saf_imported_destination_object
: This resource allows you to manage a SAF imported destinations object in a JMS Module of a WebLogic domain. Here is an example on how you shwls_saf_remote_context
: This resource allows you to manage a SAF remote contexts in a JMS Module of a WebLogic domain. Here is an example on how you should use thiswls_safagent
: This resource allows you to manage a SAF agent in an WebLogic domain. Here is an example on how you should use this: wls_safagent { 'jmwls_security_policy
: This resource allows you to manage security authorization policies in an WebLogic Security Realm.wls_security_realm
: This resource allows you to manage an existing security realm. Here is an example on how you can do this: wls_security_realm { 'my_domaiwls_server
: This resource allows you to manage server in an WebLogic domain. Here is an example on how you should use this: wls_server { 'wlsServerwls_server_channel
: This resource allows you to manage a server channel in an WebLogic domain. Here is an example on how you should use this: wls_server_chwls_server_template
: This resource allows you to manage server templates in an WebLogic domain. Here is an example on how you should use this: wls_server_tewls_server_tlog
: This resource allows you to manage server tlog in an WebLogic domain. Here is an example on how you should use this: wls_server_tlog {wls_setting
: This resource allows you to set the defaults for all other wls types. All wls types needs awls_setting
definition. This is a pointer towls_singleton_service
: This resource allows you to managed singleton services in a WebLogic domain. Here is an example on how you should use this: wls_singletwls_user
: This resource allows you to manage user in an WebLogic Security Realm. Here is an example on how you should use this: wls_user { 'Oraclwls_virtual_host
: This resource allows you to manage virtual host in an WebLogic domain. Here is an example on how you should use this: wls_virtual_hostwls_virtual_target
: This resource allows you to manage virtual targets in an WebLogic 12.2.1 domain.wls_workmanager
: This resource allows you to manage workmanagers in an WebLogic domain. Here is an example on how you should use this: wls_workmanager {wls_workmanager_constraint
: This resource allows you to manage work manager constraints in an WebLogic domain. Here is an example on how you should use this: wls_w
Tasks
start_managed_servers
: Start all managed servers in a specified domain except the servers on the skip liststop_adminserver
: Stop the admin server in a specified domain expect the Admin Server and the servers on the skip liststop_managed_servers
: Stop all managed servers in a specified domain except the Admin Server and the servers on the skip list
Defined types
wls_config::resourceadapter
The wls_config::resourceadapter class.
Parameters
The following parameters are available in the wls_config::resourceadapter
defined type:
middleware_home_dir
weblogic_home_dir
jdk_home_dir
wls_domains_dir
domain_name
adapter_name
adapter_path
adapter_plan_dir
adapter_plan
adapter_entry
adapter_entry_property
adapter_entry_value
adminserver_address
adminserver_port
userConfigFile
userKeyFile
weblogic_user
weblogic_password
os_user
os_group
download_dir
log_output
middleware_home_dir
Data type: Any
Default value: hiera('wls_middleware_home_dir')
weblogic_home_dir
Data type: Any
Default value: hiera('wls_weblogic_home_dir')
jdk_home_dir
Data type: Any
Default value: hiera('wls_jdk_home_dir')
wls_domains_dir
Data type: Any
Default value: hiera('wls_domains_dir' , undef)
domain_name
Data type: Any
Default value: hiera('domain_name' , undef)
adapter_name
Data type: Any
Default value: undef
adapter_path
Data type: Any
Default value: undef
adapter_plan_dir
Data type: Any
Default value: undef
adapter_plan
Data type: Any
Default value: undef
adapter_entry
Data type: Any
Default value: undef
adapter_entry_property
Data type: Any
Default value: undef
adapter_entry_value
Data type: Any
Default value: undef
adminserver_address
Data type: Any
Default value: hiera('domain_adminserver_address', 'localhost')
adminserver_port
Data type: Any
Default value: hiera('domain_adminserver_port' , 7001)
userConfigFile
Data type: Any
Default value: hiera('domain_user_config_file' , undef)
userKeyFile
Data type: Any
Default value: hiera('domain_user_key_file' , undef)
weblogic_user
Data type: Any
Default value: hiera('wls_weblogic_user' , 'weblogic')
weblogic_password
Data type: Any
Default value: hiera('domain_wls_password' , undef)
os_user
Data type: Any
Default value: hiera('wls_os_user')
os_group
Data type: Any
Default value: hiera('wls_os_group')
download_dir
Data type: Any
Default value: hiera('wls_download_dir')
log_output
Data type: Any
Default value: false
Resource types
wls_authentication_provider
This resource allows you to manage authentication providers in a WebLogic domain.
Here is an example on how you should use this:
wls_authentication_provider { 'ldap':
ensure => 'present',
control_flag => 'SUFFICIENT',
providerclassname => 'weblogic.security.providers.authentication.LDAPAuthenticator',
attributes: => 'Principal;Host;Port;CacheTTL;CacheSize;MaxGroupMembershipSearchLevel;SSLEnabled',
attributesvalues => 'ldapuser;ldapserver;389;60;1024;4;1',
order => '0'
}
To manage Weblogic's DefaultIdentityAsserter use the wls_identity_asserter type. In this example you are managing a provider in the default domain. When you want to manage a provider in a specific domain, you can use:
wls_authentication_provider { 'MyDomain/MyAuthenticationProvider':
ensure => 'present',
}
Check the Oracle Weblogic documentation for more documentation about setting up and managing a WebLogic cluster.
Properties
The following properties are available in the wls_authentication_provider
type.
ensure
Valid values: present
, absent
The basic property that the resource should be in.
Default value: present
Parameters
The following parameters are available in the wls_authentication_provider
type.
provider
The specific backend to use for this wls_authentication_provider
resource. You will seldom need to specify this ---
Puppet will usually discover the appropriate provider for your platform.
wls_cluster
Allows you to manage a WebLogic cluster in a WebLogic domain.
Here is an example on how you should use this:
wls_cluster { 'WlsCluster':
ensure => 'present',
messagingmode => 'unicast',
migrationbasis => 'consensus',
servers => ['wlsServer3','wlsServer4'],
multicastaddress => '239.192.0.0',
multicastport => '7001',
}
In this example you are managing a server in the default domain. When you want to manage a cluster in a specific domain, you can use:
wls_cluster { 'MuDomain/WlsCluster':
ensure => 'present',
messagingmode => 'unicast',
migrationbasis => 'consensus',
servers => ['wlsServer3','wlsServer4'],
multicastaddress => '239.192.0.0',
multicastport => '7001',
}
Check the Oracle Weblogic documentation for more documentation about setting up and managing a WebLogic cluster.
Properties
The following properties are available in the wls_cluster
type.
ensure
Valid values: present
, absent
The basic property that the resource should be in.
Default value: present
Parameters
The following parameters are available in the wls_cluster
type.
provider
The specific backend to use for this wls_cluster
resource. You will seldom need to specify this --- Puppet will
usually discover the appropriate provider for your platform.
wls_coherence_cluster
This resource allows you to manage a coherence cluster in a WebLogic domain.
Here is an example on how you should use this:
wls_coherence_cluster { 'WebCoherenceCluster':
ensure => 'present',
clusteringmode => 'unicast',
multicastport => '33389',
target => ['WebCluster'],
targettype => ['Cluster'],
unicastport => '9999',
storage_enabled => '1',
}
In this example you are managing a cluster in the default domain. When you want to manage a coherence cluster in a specific domain, you can use:
wls_coherence_cluster { 'my_domain/defaultCoherenceCluster':
ensure => 'present',
clusteringmode => 'unicast',
multicastport => '33387',
unicastport => '8888',
}
Check the Oracle Weblogic documentation for more documentation about setting up and managing a coherence cluster.
Properties
The following properties are available in the wls_coherence_cluster
type.
ensure
Valid values: present
, absent
The basic property that the resource should be in.
Default value: present
Parameters
The following parameters are available in the wls_coherence_cluster
type.
provider
The specific backend to use for this wls_coherence_cluster
resource. You will seldom need to specify this --- Puppet
will usually discover the appropriate provider for your platform.
wls_coherence_server
This resource allows you to manage a coherence server in an WebLogic domain.
Here is an example on how you should use this:
wls_coherence_server { 'default':
ensure => 'present',
server => 'LocalMachine',
unicastaddress => 'localhost',
unicastport => '8888',
}
In this example you are managing a server in the default domain. When you want to manage a coherence server in a specific domain, you can use:
wls_coherence_server { 'my_domain/default':
ensure => 'present',
server => 'LocalMachine',
unicastaddress => 'localhost',
unicastport => '8888',
}
Check the Oracle Weblogic documentation for more documentation about setting up and managing a coherence server.
Properties
The following properties are available in the wls_coherence_server
type.
ensure
Valid values: present
, absent
The basic property that the resource should be in.
Default value: present
Parameters
The following parameters are available in the wls_coherence_server
type.
provider
The specific backend to use for this wls_coherence_server
resource. You will seldom need to specify this --- Puppet
will usually discover the appropriate provider for your platform.
wls_datasource
This resource allows you to manage a datasource in an WebLogic domain.
Here is an example on how you should use this:
# this will use default as wls_setting identifier, no XA properties
wls_datasource { 'hrDS':
ensure => 'present',
connectioncreationretryfrequency => '0',
drivername => 'oracle.jdbc.xa.client.OracleXADataSource',
extraproperties => ['SendStreamAsBlob=true', 'oracle.net.CONNECT_TIMEOUT=10001'],
fanenabled => '0',
globaltransactionsprotocol => 'TwoPhaseCommit',
initialcapacity => '2',
initsql => 'None',
jndinames => ['jdbc/hrDS', 'jdbc/hrDS2'],
maxcapacity => '15',
mincapacity => 1,
rowprefetchenabled => '0',
rowprefetchsize => '48',
secondstotrustidlepoolconnection => '10',
statementcachesize => '10',
target => ['wlsServer1', 'wlsServer2'],
targettype => ['Server', 'Server'],
testconnectionsonreserve => '0',
testfrequency => '120',
testtablename => 'SQL SELECT 1 FROM DUAL',
url => 'jdbc:oracle:thin:@dbagent2.alfa.local:1521/test.oracle.com',
user => 'hr',
usexa => '0',
}
In this example you are managing a datasource in the default domain. When you want to manage a datasource in a specific domain, you can use:
# this will use default as wls_setting identifier, no XA properties
wls_datasource{'mydomain/hrDS':
...
ensure => 'present',
connectioncreationretryfrequency => '0',
drivername => 'oracle.jdbc.xa.client.OracleXADataSource',
...
}
Check the WebLogic documentation for more information about configuring and managing datasources.
Properties
The following properties are available in the wls_datasource
type.
ensure
Valid values: present
, absent
The basic property that the resource should be in.
Default value: present
Parameters
The following parameters are available in the wls_datasource
type.
provider
The specific backend to use for this wls_datasource
resource. You will seldom need to specify this --- Puppet will
usually discover the appropriate provider for your platform.
wls_default_role_mapper
This resource allows you to manage Role Mappers in weblogic.
Properties
The following properties are available in the wls_default_role_mapper
type.
ensure
Valid values: present
, absent
The basic property that the resource should be in.
Default value: present
Parameters
The following parameters are available in the wls_default_role_mapper
type.
provider
The specific backend to use for this wls_default_role_mapper
resource. You will seldom need to specify this --- Puppet
will usually discover the appropriate provider for your platform.
wls_deployment
This resource allows you to manage a cluster in an WebLogic domain.
Here is an example on how you should use this:
# 'jersey-bundle' will use default as wls_setting identifier
wls_deployment{'jersey-bundle':
ensure => 'present',
deploymenttype => 'Library',
stagingmode => 'nostage',
remote => "1",
upload => "1",
target => ['AdminServer', 'WebCluster'],
targettype => ['Server', 'Cluster'],
versionidentifier => '1.18@1.18.0.0',
}
In this example you are managing a deployment in the default domain. When you want to manage a deployment in a specific domain, you can use:
wls_deployment{'my_domain/webapp':
ensure => 'present',
deploymenttype => 'AppDeployment',
stagingmode => 'nostage',
remote => "1",
upload => "1",
target => ['WebCluster'],
targettype => ['Cluster'],
versionidentifier => '1.1@1.1.0.0',
require => Wls_deployment['jersey-bundle']
}
Check the WebLogic documentation for more information about application deployment.
Properties
The following properties are available in the wls_deployment
type.
ensure
Valid values: present
, absent
The basic property that the resource should be in.
Default value: present
Parameters
The following parameters are available in the wls_deployment
type.
provider
The specific backend to use for this wls_deployment
resource. You will seldom need to specify this --- Puppet will
usually discover the appropriate provider for your platform.
wls_domain
This resource allows you to manage domain options.
This resource allows you to make changes to the existing WebLogic domain. You cannot
create a domain with this resource. If you want to create a domain, use wls_install::domain
.
Here is an example on how you should use this:
# In this case it will use default as wls_setting identifier
wls_domain { 'Wls1036':
ensure => 'present',
jmx_platform_mbean_server_enabled => 1,
jmx_platform_mbean_server_used => 1,
jpa_default_provider => 'org.eclipse.persistence.jpa.PersistenceProvider',
jta_max_transactions => '20000',
jta_transaction_timeout => '35',
log_file_min_size => '5000',
log_filecount => '10',
log_filename => '/var/log/weblogic/Wls1036.log',
log_number_of_files_limited => 1,
log_rotate_logon_startup => 1,
log_rotationtype => 'bySize',
security_crossdomain => '0',
web_app_container_show_archived_real_path_enabled => 1,
}
In this example you are managing a domain in the default domain. When you want to manage a domain in a specific domain, you can use:
wls_domain { 'Wls11gSetting/Wls11g':
ensure => 'present',
jmx_platform_mbean_server_enabled => '0',
jmx_platform_mbean_server_used => 1,
jpa_default_provider => 'org.apache.openjpa.persistence.PersistenceProviderImpl',
jta_max_transactions => '10000',
jta_transaction_timeout => '30',
log_file_min_size => '5000',
log_filecount => '5',
log_filename => '/var/log/weblogic/Wls11g.log',
log_number_of_files_limited => '0',
log_rotate_logon_startup => '0',
log_rotationtype => 'byTime',
security_crossdomain => 1,
web_app_container_show_archived_real_path_enabled => '0',
}
Properties
The following properties are available in the wls_domain
type.
ensure
Valid values: present
, absent
The basic property that the resource should be in.
Default value: present
Parameters
The following parameters are available in the wls_domain
type.
provider
The specific backend to use for this wls_domain
resource. You will seldom need to specify this --- Puppet will usually
discover the appropriate provider for your platform.
wls_domain_partition
This resource allows you to manage domain partitions in an WebLogic 12.2.1 domain.
Properties
The following properties are available in the wls_domain_partition
type.
ensure
Valid values: present
, absent
The basic property that the resource should be in.
Default value: present
Parameters
The following parameters are available in the wls_domain_partition
type.
provider
The specific backend to use for this wls_domain_partition
resource. You will seldom need to specify this --- Puppet
will usually discover the appropriate provider for your platform.
wls_domain_partition_resource_group
This resource allows you to manage resource group in an WebLogic 12.2.1 domain.
Properties
The following properties are available in the wls_domain_partition_resource_group
type.
ensure
Valid values: present
, absent
The basic property that the resource should be in.
Default value: present
Parameters
The following parameters are available in the wls_domain_partition_resource_group
type.
provider
The specific backend to use for this wls_domain_partition_resource_group
resource. You will seldom need to specify
this --- Puppet will usually discover the appropriate provider for your platform.
wls_domain_partition_resource_group_deployment
This resource allows you to manage deployments in a resource group of a domain partition in an WebLogic 12.2.1 domain.
Properties
The following properties are available in the wls_domain_partition_resource_group_deployment
type.
ensure
Valid values: present
, absent
The basic property that the resource should be in.
Default value: present
Parameters
The following parameters are available in the wls_domain_partition_resource_group_deployment
type.
provider
The specific backend to use for this wls_domain_partition_resource_group_deployment
resource. You will seldom need to
specify this --- Puppet will usually discover the appropriate provider for your platform.
wls_dynamic_cluster
This resource allows you to manage a dynamic cluster in an WebLogic domain.
Here is an example on how you should use this:
wls_dynamic_cluster{'DynamicCluster':
ensure => 'present',
calculated_listen_port => '0', # '0' or '1'
maximum_server_count => '2',
nodemanager_match => 'Node1,Node2',
server_name_prefix => 'DynCluster-',
server_template_name => 'ServerTemplateWeb',
}
In this example you are managing a dynamic cluster in the default domain. When you want to manage a dynamic cluster in a specific domain, you can use:
wls_dynamic_cluster{'my_domain/DynamicCluster':
ensure => 'present',
calculated_listen_port => '0', # '0' or '1'
maximum_server_count => '2',
nodemanager_match => 'Node1,Node2',
server_name_prefix => 'DynCluster-',
server_template_name => 'ServerTemplateWeb',
}
Check the WebLogic documentation for more information about configuring and managing datasources.
Properties
The following properties are available in the wls_dynamic_cluster
type.
ensure
Valid values: present
, absent
The basic property that the resource should be in.
Default value: present
Parameters
The following parameters are available in the wls_dynamic_cluster
type.
provider
The specific backend to use for this wls_dynamic_cluster
resource. You will seldom need to specify this --- Puppet
will usually discover the appropriate provider for your platform.
wls_exec
This resource allows you to execute a wlst command or script in the context.
This is a fallback resource. This means you should use it with care and only if there are no other Puppet types available. Here is an example on how you can use this:
wls_exec{'@/tmp/set_some_configuration.py':
cwd => '/tmp',
refreshonly => true,
logoutput => true,
unless => '@/tmp/configuration_is_not_set.py',
}
This statement will first execute the /tmp/configuration_is_not_set.py
script. If this script returns
something, the main script (e.g. /tmp/set_some_configuration.py
) will not be executed. If it returns nothing,
the /tmp/set_some_configuration.py
script is executed.
Here is an example of a part of the unless script:
if resource_available:
print >>puppet, "true"
If the resource is available, you must write something to puppet
. If the resource is not available,
do nothing.
Formatting
Because Python is sensitive for formatting, you should take care the formatting of the main and the unless scripts. You MUST start both scripts at column 0.
You can also explicitly specify the domain:
wls_exec{'my_domain/@/tmp/set_some_configuration.py':
cwd => '/tmp',
refreshonly => true,
logoutput => true,
unless => '@/tmp/configuration_is_not_set.py',
}
Parameters
The following parameters are available in the wls_exec
type.
provider
The specific backend to use for this wls_exec
resource. You will seldom need to specify this --- Puppet will usually
discover the appropriate provider for your platform.
wls_file_persistence_store
This resource allows you to manage a file persistence stores in an WebLogic domain.
Here is an example on how to use the wls_file_persistence_store
:
# this will use default as wls_setting identifier
wls_file_persistence_store{'jmsFile1':
ensure => 'present',
directory => 'persistence1',
target => ['wlsServer1'],
targettype => ['Server'],
}
In this example you are managing a file persistence store in the default domain. When you want to manage a file persistence store in a specific domain, you can use:
wls_file_persistence_store{'mydomain/jmsFile2':
ensure => 'present',
directory => 'persistence2',
target => ['wlsServer2'],
targettype => ['Server'],
}
Properties
The following properties are available in the wls_file_persistence_store
type.
ensure
Valid values: present
, absent
The basic property that the resource should be in.
Default value: present
Parameters
The following parameters are available in the wls_file_persistence_store
type.
provider
The specific backend to use for this wls_file_persistence_store
resource. You will seldom need to specify this ---
Puppet will usually discover the appropriate provider for your platform.
wls_foreign_jndi_provider
This resource allows you to manage a foreign jndi provider in an WebLogic domain.
Here is an example on how you should use this:
wls_foreign_jndi_provider { 'DomainA':
ensure => 'present',
initial_context_factory => 'weblogic.jndi.WLInitialContextFactory',
provider_properties => ['bbb=aaaa', 'xxx=123'],
provider_url => 't3://10.10.10.100:7001',
target => ['WebCluster'],
targettype => ['Cluster'],
user => 'weblogic',
password => 'weblogic1',
}
In this example you are managing a foreign jndi provider in the default domain. When you want to manage a foreign jndi provider in a specific domain, you can use:
wls_foreign_jndi_provider { 'my_domain/LDAP':
ensure => 'present',
initial_context_factory => 'com.sun.jndi.ldap.LdapCtxFactory',
provider_properties => ['referral=follow'],
provider_url => 'ldap://:10.10.10.100:389',
target => ['AdminServer'],
targettype => ['Server'],
user => 'cn=orcladmin',
password => 'weblogic1',
}
Properties
The following properties are available in the wls_foreign_jndi_provider
type.
ensure
Valid values: present
, absent
The basic property that the resource should be in.
Default value: present
Parameters
The following parameters are available in the wls_foreign_jndi_provider
type.
provider
The specific backend to use for this wls_foreign_jndi_provider
resource. You will seldom need to specify this ---
Puppet will usually discover the appropriate provider for your platform.
wls_foreign_jndi_provider_link
This resource allows you to manage a datasource in an WebLogic domain.
Here is an example on how you should use this:
wls_foreign_jndi_provider_link { 'LDAP:aaaaa':
ensure => 'present',
local_jndi_name => 'aaaaa',
remote_jndi_name => 'bbbbb',
}
In this example you are managing a foreign jndi provider link in the default domain. When you want to manage a foreign jndi provider link in a specific domain, you can use:
wls_foreign_jndi_provider_link { 'my_domain/LDAP:ccccc':
ensure => 'present',
local_jndi_name => 'ccccc',
remote_jndi_name => 'ddddd',
}
Properties
The following properties are available in the wls_foreign_jndi_provider_link
type.
ensure
Valid values: present
, absent
The basic property that the resource should be in.
Default value: present
Parameters
The following parameters are available in the wls_foreign_jndi_provider_link
type.
provider
The specific backend to use for this wls_foreign_jndi_provider_link
resource. You will seldom need to specify this ---
Puppet will usually discover the appropriate provider for your platform.
wls_foreign_server
This resource allows you to manage foreign servers in a JMS Module of a WebLogic domain.
Here is an example on how you should use this:
wls_foreign_server { 'jmsClusterModule:AQForeignServer':
ensure => 'present',
defaulttargeting => 1,
extraproperties => 'datasource=jdbc/hrDS',
initialcontextfactory => ['oracle.jms.AQjmsInitialContextFactory'],
}
In this example you are managing a foreign server in the default domain. When you want to manage a foreign server in a specific domain, you can use:
wls_foreign_server { 'my_domain/jmsClusterModule:Jboss':
ensure => 'present',
connectionurl => 'remote://10.10.10.10:4447',
defaulttargeting => '0',
extraproperties => ['java.naming.security.principal=jmsuser'],
initialcontextfactory => 'org.jboss.naming.remote.client.InitialContextFactory',
subdeployment => 'wlsServers',
}
Properties
The following properties are available in the wls_foreign_server
type.
ensure
Valid values: present
, absent
The basic property that the resource should be in.
Default value: present
Parameters
The following parameters are available in the wls_foreign_server
type.
provider
The specific backend to use for this wls_foreign_server
resource. You will seldom need to specify this --- Puppet will
usually discover the appropriate provider for your platform.
wls_foreign_server_object
This resource allows you to manage a foreign server object in a JMS Module of a WebLogic domain.
Here is an example on how you should use this:
wls_foreign_server_object { 'jmsClusterModule:Jboss:CF':
ensure => 'present',
localjndiname => 'jms/jboss/CF',
object_type => 'connectionfactory',
remotejndiname => 'jms/Remote/CF',
}
In this example you are managing a foreign server object in the default domain. When you want to manage a foreign server object in a specific domain, you can use:
wls_foreign_server_object { 'my_domain/jmsClusterModule:Jboss:JBossQ': ensure => 'present', localjndiname => 'jms/jboss/Queue', object_type => 'destination', remotejndiname => 'jms/Remote/Queue', }
Properties
The following properties are available in the wls_foreign_server_object
type.
ensure
Valid values: present
, absent
The basic property that the resource should be in.
Default value: present
Parameters
The following parameters are available in the wls_foreign_server_object
type.
provider
The specific backend to use for this wls_foreign_server_object
resource. You will seldom need to specify this ---
Puppet will usually discover the appropriate provider for your platform.
wls_group
This resource allows you to manage group in a WebLogic Security Realm.
Here is an example on how you should use this:
wls_group { 'SuperUsers':
ensure => 'present',
authenticationprovider => 'DefaultAuthenticator',
description => 'SuperUsers',
realm => 'myrealm',
users => ['testuser2'],
}
In this example you are managing a group in the default domain. When you want to manage a group in a specific domain, you can use:
wls_group { 'my_domain/TestGroup':
ensure => 'present',
authenticationprovider => 'DefaultAuthenticator',
description => 'TestGroup',
realm => 'myrealm',
users => ['testuser1','testuser2'],
}
Properties
The following properties are available in the wls_group
type.
ensure
Valid values: present
, absent
The basic property that the resource should be in.
Default value: present
Parameters
The following parameters are available in the wls_group
type.
provider
The specific backend to use for this wls_group
resource. You will seldom need to specify this --- Puppet will usually
discover the appropriate provider for your platform.
wls_identity_asserter
This resource allows you to manage Identity Asserters in an WebLogic domain.
Here is an example on how you should use this:
wls_authentication_provider { 'DefaultIdentityAsserter':
ensure => 'present',
providerclassname => 'weblogic.security.providers.authentication.DefaultIdentityAsserter',
attributes: => 'DigestReplayDetectionEnabled;UseDefaultUserNameMapper',
attributesvalues => '1;1;',
activetypes => 'AuthenticatedUser::X.509',
defaultmappertype => 'CN',
}
In this example you are managing a identity asserter in the default domain. When you want to manage a identity asserter in a specific domain, you can use:
wls_authentication_provider { 'my_domain/DefaultIdentityAsserter':
ensure => 'present',
providerclassname => 'weblogic.security.providers.authentication.DefaultIdentityAsserter',
attributes: => 'DigestReplayDetectionEnabled;UseDefaultUserNameMapper',
attributesvalues => '1;1;',
activetypes => 'AuthenticatedUser::X.509',
defaultmappertype => 'CN',
}
Properties
The following properties are available in the wls_identity_asserter
type.
ensure
Valid values: present
, absent
The basic property that the resource should be in.
Default value: present
Parameters
The following parameters are available in the wls_identity_asserter
type.
provider
The specific backend to use for this wls_identity_asserter
resource. You will seldom need to specify this --- Puppet
will usually discover the appropriate provider for your platform.
wls_jdbc_persistence_store
This resource allows you to manage a JDBC persistence stores in an WebLogic domain.
Here is an example on how you should use this:
wls_jdbc_persistence_store { 'JDBCStoreX':
ensure => 'present',
datasource => 'jmsDS',
prefix_name => 'dev_',
target => ['wlsServer1'],
targettype => ['Server'],
}
In this example you are managing a JDBC persistance store in the default domain. When you want to manage a JDBC persistance store in a specific domain, you can use:
wls_jdbc_persistence_store { 'my_domain/JDBCStoreX':
ensure => 'present',
datasource => 'jmsDS',
prefix_name => 'dev_',
target => ['wlsServer1'],
targettype => ['Server'],
}
Properties
The following properties are available in the wls_jdbc_persistence_store
type.
ensure
Valid values: present
, absent
The basic property that the resource should be in.
Default value: present
Parameters
The following parameters are available in the wls_jdbc_persistence_store
type.
provider
The specific backend to use for this wls_jdbc_persistence_store
resource. You will seldom need to specify this ---
Puppet will usually discover the appropriate provider for your platform.
wls_jms_bridge_destination
This resource allows you to manage a jms bridge destination in an WebLogic domain.
Here is an example on how you should use this:
wls_jms_bridge_destination { 'myBridgeDest':
ensure => 'present',
adapter => 'eis.jms.WLSConnectionFactoryJNDINoTX',
classpath => 'myClasspath',
connectionfactoryjndi => 'myCFJndi',
connectionurl => 'myConnUrl',
destinationjndi => 'myDestJndi',
destinationtype => 'Queue',
initialcontextfactory => 'weblogic.jndi.WLInitialContextFactory',
}
In this example you are managing a bridge destination in the default domain. When you want to manage a bridge destination in a specific domain, you can use:
wls_jms_bridge_destination { 'my_domain/myBridgeDest':
ensure => 'present',
adapter => 'eis.jms.WLSConnectionFactoryJNDINoTX',
classpath => 'myClasspath',
connectionfactoryjndi => 'myCFJndi',
connectionurl => 'myConnUrl',
destinationjndi => 'myDestJndi',
destinationtype => 'Queue',
initialcontextfactory => 'weblogic.jndi.WLInitialContextFactory',
}
Here you can find more information about JMS bridge desitinations.
Properties
The following properties are available in the wls_jms_bridge_destination
type.
ensure
Valid values: present
, absent
The basic property that the resource should be in.
Default value: present
Parameters
The following parameters are available in the wls_jms_bridge_destination
type.
provider
The specific backend to use for this wls_jms_bridge_destination
resource. You will seldom need to specify this ---
Puppet will usually discover the appropriate provider for your platform.
wls_jms_connection_factory
This resource allows you to manage a connection factory in a JMS Module of a WebLogic domain.
Here is an example on how you should use this:
wls_jms_connection_factory { 'jmsClusterModule:cf':
ensure => 'present',
attachjmsxuserid => '0',
clientidpolicy => 'Restricted',
defaulttargeting => '0',
jndiname => 'jms/cf',
loadbalancingenabled => 1,
messagesmaximum => '10',
reconnectpolicy => 'producer',
serveraffinityenabled => 1,
subdeployment => 'wlsServers',
subscriptionsharingpolicy => 'Exclusive',
transactiontimeout => '3600',
xaenabled => '0',
}
In this example you are managing a connection factory in the default domain. When you want to manage a connection factory in a specific domain, you can use:
wls_jms_connection_factory { 'my_domain/jmsClusterModule:cf2':
ensure => 'present',
attachjmsxuserid => '0',
clientidpolicy => 'Restricted',
defaulttargeting => 1,
jndiname => 'jms/cf2',
loadbalancingenabled => 1,
messagesmaximum => '10',
reconnectpolicy => 'producer',
serveraffinityenabled => 1,
subscriptionsharingpolicy => 'Exclusive',
transactiontimeout => '3600',
xaenabled => 1,
}
Properties
The following properties are available in the wls_jms_connection_factory
type.
ensure
Valid values: present
, absent
The basic property that the resource should be in.
Default value: present
Parameters
The following parameters are available in the wls_jms_connection_factory
type.
provider
The specific backend to use for this wls_jms_connection_factory
resource. You will seldom need to specify this ---
Puppet will usually discover the appropriate provider for your platform.
wls_jms_module
This resource allows you to manage a JMS module in an WebLogic domain.
Here is an example on how you should use this:
wls_jms_module { 'jmsClusterModule':
ensure => 'present',
target => ['WebCluster'],
targettype => ['Cluster'],
}
In this example you are managing a JMS module in the default domain. When you want to manage a JMS module in a specific domain, you can use:
wls_jms_module { 'my_domain/jmsClusterModule':
ensure => 'present',
target => ['WebCluster'],
targettype => ['Cluster'],
}
Properties
The following properties are available in the wls_jms_module
type.
ensure
Valid values: present
, absent
The basic property that the resource should be in.
Default value: present
Parameters
The following parameters are available in the wls_jms_module
type.
provider
The specific backend to use for this wls_jms_module
resource. You will seldom need to specify this --- Puppet will
usually discover the appropriate provider for your platform.
wls_jms_queue
This resource allows you to manage a Queue in a JMS Module of a WebLogic domain.
Here is an example on how you should use this:
wls_jms_queue { 'jmsClusterModule:ErrorQueue':
ensure => 'present',
defaulttargeting => '0',
distributed => 1,
expirationpolicy => 'Discard',
jndiname => 'jms/ErrorQueue',
redeliverydelay => '-1',
redeliverylimit => '-1',
subdeployment => 'jmsServers',
timetodeliver => '-1',
timetolive => '-1',
templatename => 'Template',
messagelogging => 1,
consumptionpaused => '0',
insertionpaused => '0',
productionpaused => '0',
}
Properties
The following properties are available in the wls_jms_queue
type.
ensure
Valid values: present
, absent
The basic property that the resource should be in.
Default value: present
Parameters
The following parameters are available in the wls_jms_queue
type.
provider
The specific backend to use for this wls_jms_queue
resource. You will seldom need to specify this --- Puppet will
usually discover the appropriate provider for your platform.
wls_jms_quota
This resource allows you to manage a Quota in a JMS module of a WebLogic domain.
Here is an example on how you should use this:
wls_jms_quota { 'jmsClusterModule:QuotaBig':
ensure => 'present',
bytesmaximum => '9223372036854775807',
messagesmaximum => '9223372036854775807',
policy => 'FIFO',
shared => 1,,
}
In this example you are managing a JMS quota in the default domain. When you want to manage a JMS quota in a specific domain, you can use:
wls_jms_quota { 'my_domain/jmsClusterModule:QuotaLow':
ensure => 'present',
bytesmaximum => '20000000000',
messagesmaximum => '9223372036854775807',
policy => 'FIFO',
shared => '0',
}
Properties
The following properties are available in the wls_jms_quota
type.
ensure
Valid values: present
, absent
The basic property that the resource should be in.
Default value: present
Parameters
The following parameters are available in the wls_jms_quota
type.
provider
The specific backend to use for this wls_jms_quota
resource. You will seldom need to specify this --- Puppet will
usually discover the appropriate provider for your platform.
wls_jms_security_policy
This resource allows you to manage security authorization policies in an WebLogic Security Realm.
Properties
The following properties are available in the wls_jms_security_policy
type.
ensure
Valid values: present
, absent
The basic property that the resource should be in.
Default value: present
Parameters
The following parameters are available in the wls_jms_security_policy
type.
provider
The specific backend to use for this wls_jms_security_policy
resource. You will seldom need to specify this --- Puppet
will usually discover the appropriate provider for your platform.
wls_jms_sort_destination_key
This resource allows you to manage the sort destination key in a JMS module of a WebLogic domain.
Here is an example on how you should use this:
wls_jms_sort_destination_key { 'jmsClusterModule:JMSPriority':
ensure => 'present',
key_type => 'Int',
property_name => 'JMSPriority',
sort_order => 'Descending',
}
In this example you are managing a JMS sort destination key in the default domain. When you want to manage a JMS sort destination key in a specific domain, you can use:
wls_jms_sort_destination_key { 'my_domain/jmsClusterModule:JMSRedelivered':
ensure => 'present',
key_type => 'Boolean',
property_name => 'JMSRedelivered',
sort_order => 'Ascending',
}
Properties
The following properties are available in the wls_jms_sort_destination_key
type.
ensure
Valid values: present
, absent
The basic property that the resource should be in.
Default value: present
Parameters
The following parameters are available in the wls_jms_sort_destination_key
type.
provider
The specific backend to use for this wls_jms_sort_destination_key
resource. You will seldom need to specify this ---
Puppet will usually discover the appropriate provider for your platform.
wls_jms_subdeployment
This resource allows you to manage a JMS subdeployment in a JMS module of a WebLogic domain.
Here is an example on how you should use this:
wls_jms_subdeployment { 'jmsClusterModule:jmsServers':
ensure => 'present',
target => ['jmsServer1','jmsServer2'],
targettype => ['JMSServer','JMSServer'],
}
In this example you are managing a JMS subdeployment in the default domain. When you want to manage a JMS subdeployment in a specific domain, you can use:
wls_jms_subdeployment { 'my_domain/jmsClusterModule:wlsServers':
ensure => 'present',
target => ['WebCluster'],
targettype => ['Cluster'],
}
Properties
The following properties are available in the wls_jms_subdeployment
type.
ensure
Valid values: present
, absent
The basic property that the resource should be in.
Default value: present
Parameters
The following parameters are available in the wls_jms_subdeployment
type.
provider
The specific backend to use for this wls_jms_subdeployment
resource. You will seldom need to specify this --- Puppet
will usually discover the appropriate provider for your platform.
wls_jms_template
This resource allows you to manage a template in a JMS Module of a WebLogic domain.
Here is an example on how you should use this:
wls_jms_template { 'jmsClusterModule:Template-0':
ensure => 'present',
redeliverydelay => '-1',
redeliverylimit => '-1',
}
In this example you are managing a JMS template in the default domain. When you want to manage a JMS template in a specific domain, you can use:
wls_jms_template { 'my_domain/jmsClusterModule:Template-0':
ensure => 'present',
redeliverydelay => '-1',
redeliverylimit => '-1',
}
Properties
The following properties are available in the wls_jms_template
type.
ensure
Valid values: present
, absent
The basic property that the resource should be in.
Default value: present
Parameters
The following parameters are available in the wls_jms_template
type.
provider
The specific backend to use for this wls_jms_template
resource. You will seldom need to specify this --- Puppet will
usually discover the appropriate provider for your platform.
wls_jms_topic
This resource allows you to manage a Tpoic in a JMS Module of a WebLogic domain.
Here is an example on how you should use this:
wls_jms_topic { 'jmsClusterModule:Topic1':
ensure => 'present',
balancingpolicy => 'Round-Robin',
defaulttargeting => '0',
deliverymode => 'No-Delivery',
destination_keys => ['JMSPriority', 'JmsMessageId'],
distributed => 1,
expirationpolicy => 'Discard',
forwardingpolicy => 'Replicated',
jndiname => 'jms/Topic1',
redeliverydelay => '2000',
redeliverylimit => '2',
subdeployment => 'jmsServers',
timetodeliver => '-1',
timetolive => '300000',
consumptionpaused => '0',
insertionpaused => '0',
productionpaused => '0',
}
WARNING When you want to absent
a topic. you must ensure that
the distributed
parameter is specified.
wls_jms_topic { 'jmsClusterModule:ErrorTopic':
ensure => 'absent',
distributed => 1,
}
Failure to specify the correct value for distributed
, will result
in an error on removal of the topic.
Properties
The following properties are available in the wls_jms_topic
type.
ensure
Valid values: present
, absent
The basic property that the resource should be in.
Default value: present
Parameters
The following parameters are available in the wls_jms_topic
type.
provider
The specific backend to use for this wls_jms_topic
resource. You will seldom need to specify this --- Puppet will
usually discover the appropriate provider for your platform.
wls_jmsserver
This resource allows you to manage a jmsserver in an WebLogic domain.
Here is an example on how you should use this:
wls_jmsserver { 'jmsServer1':
ensure => 'present',
persistentstore => 'jmsFile1',
persistentstoretype => 'FileStore',
target => ['wlsServer1'],
targettype => ['Server'],
allows_persistent_downgrade => '0',
bytes_maximum => '-1',
}
In this example you are managing a JMS server in the default domain. When you want to manage a JMS server in a specific domain, you can use:
wls_jmsserver { 'my_domain/jmsServer2':
ensure => 'present',
target => ['wlsServer2'],
targettype => ['Server'],
}
Properties
The following properties are available in the wls_jmsserver
type.
ensure
Valid values: present
, absent
The basic property that the resource should be in.
Default value: present
Parameters
The following parameters are available in the wls_jmsserver
type.
provider
The specific backend to use for this wls_jmsserver
resource. You will seldom need to specify this --- Puppet will
usually discover the appropriate provider for your platform.
wls_jndi_security_policy
This resource allows you to manage jndi security authorization policies in an WebLogic Security Realm.
Here is an example on how you should use this:
wls_jndi_security_policy { 'domain/managed_server:javax.jms.TopicConnectionFactory:modify':
ensure => 'present',
policyexpression => 'Role(Admin) | Role(Deployer)',
}
This puppet snippit set's the security policy for modify
operation of the the JNDI object
javax.jms.TopicConnectionFactory
on server managed_server
in the domain domain
to: Role(Admin) | Role(Deployer)
.
Properties
The following properties are available in the wls_jndi_security_policy
type.
ensure
Valid values: present
, absent
The basic property that the resource should be in.
Default value: present
Parameters
The following parameters are available in the wls_jndi_security_policy
type.
provider
The specific backend to use for this wls_jndi_security_policy
resource. You will seldom need to specify this ---
Puppet will usually discover the appropriate provider for your platform.
wls_machine
This resource allows you to manage machine in an WebLogic domain.
Here is an example on how you should use this:
wls_machine { 'test2':
ensure => 'present',
listenaddress => '10.10.10.10',
listenport => '5556',
machinetype => 'UnixMachine',
nmtype => 'SSL',
}
In this example you are managing a machine in the default domain. When you want to manage a machine in a specific domain, you can use:
wls_machine { 'my_domain/test2':
ensure => 'present',
listenaddress => '10.10.10.10',
listenport => '5556',
machinetype => 'UnixMachine',
nmtype => 'SSL',
}
Properties
The following properties are available in the wls_machine
type.
ensure
Valid values: present
, absent
The basic property that the resource should be in.
Default value: present
Parameters
The following parameters are available in the wls_machine
type.
provider
The specific backend to use for this wls_machine
resource. You will seldom need to specify this --- Puppet will
usually discover the appropriate provider for your platform.
wls_mail_session
This resource allows you to manage a mail_session in an WebLogic domain.
Here is an example on how you should use this:
wls_mail_session { 'myMailSession':
ensure => 'present',
jndiname => 'myMailSession',
target => ['ManagedServer1', 'WebCluster'],
targettype => ['Server', 'Cluster'],
mailproperty => ['mail.host=smtp.hostname.com', 'mail.user=smtpadmin'],
}
In this example you are managing a mail session in the default domain. When you want to manage a mail session in a specific domain, you can use:
wls_mail_session { 'my_domain/myMailSession':
ensure => 'present',
jndiname => 'myMailSession',
target => ['ManagedServer1', 'WebCluster'],
targettype => ['Server', 'Cluster'],
mailproperty => ['mail.host=smtp.hostname.com', 'mail.user=smtpadmin'],
}
Properties
The following properties are available in the wls_mail_session
type.
ensure
Valid values: present
, absent
The basic property that the resource should be in.
Default value: present
Parameters
The following parameters are available in the wls_mail_session
type.
provider
The specific backend to use for this wls_mail_session
resource. You will seldom need to specify this --- Puppet will
usually discover the appropriate provider for your platform.
wls_managed_executor_service_template
Weblogic Server provides a preconfigured, default ManagedExecutorService for each application, and applications can easily use it in web or EJB components without any configuration.
This resource allows you to manage a ManagedExecutorService in an WebLogic domain.
Here is an example on how you should use this:
wls_managed_executor_service_template { 'default/ManagedExecutorServiceTemplate-0':
ensure => 'present',
deployment_order => '1000',
long_running_priority => '5',
max_concurrent_long_running_requests => '10',
target => ['ClusterJMS'],
targettype => ['Cluster'],
}
Properties
The following properties are available in the wls_managed_executor_service_template
type.
ensure
Valid values: present
, absent
The basic property that the resource should be in.
Default value: present
Parameters
The following parameters are available in the wls_managed_executor_service_template
type.
provider
The specific backend to use for this wls_managed_executor_service_template
resource. You will seldom need to specify
this --- Puppet will usually discover the appropriate provider for your platform.
wls_managedserver
control a managed server or cluster state like running,stop,restart
Type for managed server control like start, running, abort and stop a managed server or a cluster.
Also supports subscribe
with refreshonly
when you only want to execute the restart when something
has changed.
Here is an example on how you should use this:
wls_managedserver{'JMSServer1_Wls1036:':
ensure => 'running', #running|start|abort|stop
target => 'Server', #Server|Cluster
server_name => 'JMSServer1',
domain_name => hiera('domain_name'),
os_user => hiera('wls_os_user'),
weblogic_home_dir => hiera('wls_weblogic_home_dir'),
weblogic_user => hiera('wls_weblogic_user'),
weblogic_password => hiera('domain_wls_password'),
jdk_home_dir => hiera('wls_jdk_home_dir'),
adminserver_address => hiera('domain_adminserver_address'),
adminserver_port => hiera('domain_adminserver_port'),
}
Here is an example with refreshonly
. In this example, the restart will only be executed
when the domain Wls1036
is changed. A restart will be executed.
wls_managedserver{'JMSServer1_Wls1036':
ensure => 'restart', #running|start|abort|stop
target => 'Server', #Server|Cluster
server_name => 'JMSServer1',
domain_name => hiera('domain_name'),
os_user => hiera('wls_os_user'),
weblogic_home_dir => hiera('wls_weblogic_home_dir'),
weblogic_user => hiera('wls_weblogic_user'),
weblogic_password => hiera('domain_wls_password'),
jdk_home_dir => hiera('wls_jdk_home_dir'),
adminserver_address => hiera('domain_adminserver_address'),
adminserver_port => hiera('domain_adminserver_port'),
refreshonly => true,
subscribe => Wls_domain['Wls1036'],
}
Properties
The following properties are available in the wls_managedserver
type.
ensure
Valid values: start
, stop
, running
, abort
Aliases: "running"=>"start", "abort"=>"stop"
Whether to do something.
Parameters
The following parameters are available in the wls_managedserver
type.
adminserver_address
adminserver_port
domain_name
jdk_home_dir
name
os_user
provider
refreshonly
server_name
target
weblogic_home_dir
weblogic_password
weblogic_user
adminserver_address
The adminserver address.
adminserver_port
The adminserver port.
domain_name
The weblogic domain name.
jdk_home_dir
The jdk home dir.
name
namevar
The title.
os_user
The weblogic operating system user.
provider
The specific backend to use for this wls_managedserver
resource. You will seldom need to specify this --- Puppet will
usually discover the appropriate provider for your platform.
refreshonly
Valid values: true
, false
The command should only be run as a refresh mechanism for when a dependent object is changed.
Default value: false
server_name
The adminserver name.
target
The weblogic type.
weblogic_home_dir
The weblogic home folder.
weblogic_password
The weblogic user password.
weblogic_user
The weblogic user.
wls_messaging_bridge
This resource allows you to manage a messaging bridge in an WebLogic domain.
Here is an example on how you should use this:
wls_messaging_bridge { 'myBrigde':
ensure => 'present',
asyncenabled => 1,
batchinterval => '-1',
batchsize => '10',
durabilityenabled => 1,
idletimemax => '60',
qos => 'Exactly-once',
reconnectdelayincrease => '5',
reconnectdelaymax => '60',
reconnectdelaymin => '15',
selector => 'sel',
transactiontimeout => '30',
sourcedestination => 'mySourceBrigdeDest',
targetdestination => 'MyDestBridgeDest',
target => ['ManagedServer1', 'WebCluster'],
targettype => ['Server', 'Cluster'],
}
In this example you are managing a message bridge in the default domain. When you want to manage a message bridge in a specific domain, you can use:
wls_messaging_bridge { 'my_domain/myBrigde':
ensure => 'present',
asyncenabled => 1,
batchinterval => '-1',
batchsize => '10',
durabilityenabled => 1,
idletimemax => '60',
qos => 'Exactly-once',
reconnectdelayincrease => '5',
reconnectdelaymax => '60',
reconnectdelaymin => '15',
selector => 'sel',
transactiontimeout => '30',
sourcedestination => 'mySourceBrigdeDest',
targetdestination => 'MyDestBridgeDest',
target => ['ManagedServer1', 'WebCluster'],
targettype => ['Server', 'Cluster'],
}
Check the documentation for valid messaging bridge properties.
Properties
The following properties are available in the wls_messaging_bridge
type.
ensure
Valid values: present
, absent
The basic property that the resource should be in.
Default value: present
Parameters
The following parameters are available in the wls_messaging_bridge
type.
provider
The specific backend to use for this wls_messaging_bridge
resource. You will seldom need to specify this --- Puppet
will usually discover the appropriate provider for your platform.
wls_migratable_target
This resource allows you to managed migratable targets in a WebLogic domain.
Here is an example on how you should use this:
wls_migratable_target { 'wlsServer1 (migratable)':
ensure => 'present',
cluster => 'WebCluster',
migration_policy => 'manual',
number_of_restart_attempts => '6',
seconds_between_restarts => '30',
user_preferred_server => 'wlsServer1',
}
In this example you are managing a migratable target in the default domain. When you want to manage a migratable target in a specific domain, you can use:
wls_migratable_target { 'my_domain/wlsServer2 (migratable)':
ensure => 'present',
cluster => 'WebCluster',
migration_policy => 'manual',
number_of_restart_attempts => '6',
seconds_between_restarts => '30',
user_preferred_server => 'wlsServer2',
}
Here are some more examples:
wls_migratable_target { 'Wls11gSetting/wlsServer1 (migratable)':
ensure => 'present',
cluster => 'WebCluster',
migration_policy => 'manual',
number_of_restart_attempts => '6',
seconds_between_restarts => '30',
user_preferred_server => 'wlsServer1',
}
wls_migratable_target { 'Wls11gSetting/wlsServer2 (migratable)':
ensure => 'present',
cluster => 'WebCluster',
migration_policy => 'manual',
number_of_restart_attempts => '6',
seconds_between_restarts => '30',
user_preferred_server => 'wlsServer2',
}
Properties
The following properties are available in the wls_migratable_target
type.
ensure
Valid values: present
, absent
The basic property that the resource should be in.
Default value: present
Parameters
The following parameters are available in the wls_migratable_target
type.
provider
The specific backend to use for this wls_migratable_target
resource. You will seldom need to specify this --- Puppet
will usually discover the appropriate provider for your platform.
wls_multi_datasource
This resource allows you to manage a multi datasource in an WebLogic domain.
Here is an example on how you should use this:
wls_multi_datasource { 'myMultiDatasource':
ensure => 'present',
algorithmtype => 'Failover',
datasources => ['myJDBCDatasource'],
jndinames => ['myMultiDatasource'],
target => ['ManagedServer1', 'WebCluster'],
targettype => ['Server', 'Cluster'],
testfrequency => '120',
}
In this example you are managing a multi datasource in the default domain. When you want to manage a multi datasource in a specific domain, you can use:
wls_multi_datasource { 'my_domain/myMultiDatasource':
ensure => 'present',
algorithmtype => 'Failover',
datasources => ['myJDBCDatasource'],
jndinames => ['myMultiDatasource'],
target => ['ManagedServer1', 'WebCluster'],
targettype => ['Server', 'Cluster'],
testfrequency => '120',
}
Properties
The following properties are available in the wls_multi_datasource
type.
ensure
Valid values: present
, absent
The basic property that the resource should be in.
Default value: present
Parameters
The following parameters are available in the wls_multi_datasource
type.
provider
The specific backend to use for this wls_multi_datasource
resource. You will seldom need to specify this --- Puppet
will usually discover the appropriate provider for your platform.
wls_opatch
This resource allows you to manage opatch patches on a specific middleware home.
wls_opatch {'/opt/oracle/middleware12c:16175470': ensure => "present", jdk_home_dir => "/usr/java/jdk1.7.0_45", os_user => "oracle", source => "/vagrant/p16175470_121200_Generic.zip", }
Properties
The following properties are available in the wls_opatch
type.
ensure
Valid values: present
, absent
The basic property that the resource should be in.
Default value: present
Parameters
The following parameters are available in the wls_opatch
type.
provider
The specific backend to use for this wls_opatch
resource. You will seldom need to specify this --- Puppet will usually
discover the appropriate provider for your platform.
wls_path_service
This resource allows you to manage path servers
Here is an example on how you should use this:
wls_path_service { 'jmy_service':
ensure => 'present',
target => ['MyCluster'],
targettype => ['Cluster'],
persistentstore => 'mystore',
persistentstoretype => 'JDBCStore',
}
Properties
The following properties are available in the wls_path_service
type.
ensure
Valid values: present
, absent
The basic property that the resource should be in.
Default value: present
Parameters
The following parameters are available in the wls_path_service
type.
provider
The specific backend to use for this wls_path_service
resource. You will seldom need to specify this --- Puppet will
usually discover the appropriate provider for your platform.
wls_rcu
This is the Oracle WebLogic RCU ( Repository creation utility) installer type
Properties
The following properties are available in the wls_rcu
type.
ensure
Valid values: present
, absent
, create
, delete
Aliases: "create"=>"present", "delete"=>"absent"
Whether a Repository should be created.
Parameters
The following parameters are available in the wls_rcu
type.
check_script
jdbc_url
jdk_home_dir
name
oracle_home
os_user
provider
statement
sys_password
sys_user
check_script
The check_script py script for the RCU Repository.
jdbc_url
The jdbc url for the RCU check.
jdk_home_dir
The jdk_home_dir.
name
namevar
The prefix of the RCU.
oracle_home
The oracle_home for the WLST location.
os_user
The weblogic operating system user.
provider
The specific backend to use for this wls_rcu
resource. You will seldom need to specify this --- Puppet will usually
discover the appropriate provider for your platform.
statement
The RCU statement.
sys_password
The sys password for the RCU check/install.
sys_user
The sys user for the RCU check/install.
wls_resource_group_template
This resource allows you to manage resource group template in an WebLogic 12.2.1 domain.
Properties
The following properties are available in the wls_resource_group_template
type.
ensure
Valid values: present
, absent
The basic property that the resource should be in.
Default value: present
Parameters
The following parameters are available in the wls_resource_group_template
type.
provider
The specific backend to use for this wls_resource_group_template
resource. You will seldom need to specify this ---
Puppet will usually discover the appropriate provider for your platform.
wls_resource_group_template_deployment
TThis resource allows you to manage deployments in a resource group template in an WebLogic 12.2.1 domain.
Properties
The following properties are available in the wls_resource_group_template_deployment
type.
ensure
Valid values: present
, absent
The basic property that the resource should be in.
Default value: present
Parameters
The following parameters are available in the wls_resource_group_template_deployment
type.
provider
The specific backend to use for this wls_resource_group_template_deployment
resource. You will seldom need to specify
this --- Puppet will usually discover the appropriate provider for your platform.
wls_role
This resource allows you to manage roles an WebLogic Secuirty Realm.
Properties
The following properties are available in the wls_role
type.
ensure
Valid values: present
, absent
The basic property that the resource should be in.
Default value: present
Parameters
The following parameters are available in the wls_role
type.
provider
The specific backend to use for this wls_role
resource. You will seldom need to specify this --- Puppet will usually
discover the appropriate provider for your platform.
wls_saf_error_handler
This resource allows you to manage a SAF Error Handler in a JMS Module of a WebLogic domain.
Here is an example on how you should use this:
wls_saf_error_handler { 'jmsClusterModule:ErrorHandling-0':
ensure => 'present',
policy => 'Discard',
}
In this example you are managing a SAF error handler in the default domain. When you want to manage a SAF error handler in a specific domain, you can use:
wls_saf_error_handler { 'my_domain/jmsClusterModule:ErrorHandling-1':
ensure => 'present',
logformat => '%header%%properties%',
policy => 'Log',
}
Properties
The following properties are available in the wls_saf_error_handler
type.
ensure
Valid values: present
, absent
The basic property that the resource should be in.
Default value: present
Parameters
The following parameters are available in the wls_saf_error_handler
type.
provider
The specific backend to use for this wls_saf_error_handler
resource. You will seldom need to specify this --- Puppet
will usually discover the appropriate provider for your platform.
wls_saf_imported_destination
This resource allows you to manage a SAF imported destinations in a JMS Module of a WebLogic domain.
Here is an example on how you should use this:
wls_saf_imported_destination { 'jmsClusterModule:SAFImportedDestinations-0':
ensure => 'present',
defaulttargeting => 1,
errorhandling => 'ErrorHandling-0',
jndiprefix => 'saf_',
remotecontext => 'RemoteSAFContext-0',
timetolivedefault => '1000000000',
usetimetolivedefault => 1,,
}
In this example you are managing a SAF imported destination in the default domain. When you want to manage a SAF imported destination in a specific domain, you can use:
wls_saf_imported_destination { 'my_domain/jmsClusterModule:SAFImportedDestinations-1':
ensure => 'present',
defaulttargeting => '0',
jndiprefix => 'saf2_',
remotecontext => 'RemoteSAFContext-1',
subdeployment => 'safServers',
usetimetolivedefault => '0',
}
Properties
The following properties are available in the wls_saf_imported_destination
type.
ensure
Valid values: present
, absent
The basic property that the resource should be in.
Default value: present
Parameters
The following parameters are available in the wls_saf_imported_destination
type.
provider
The specific backend to use for this wls_saf_imported_destination
resource. You will seldom need to specify this ---
Puppet will usually discover the appropriate provider for your platform.
wls_saf_imported_destination_object
This resource allows you to manage a SAF imported destinations object in a JMS Module of a WebLogic domain.
Here is an example on how you should use this:
wls_saf_imported_destination_object { 'jmsClusterModule:SAFImportedDestinations-0:SAFDemoQueue':
ensure => 'present',
nonpersistentqos => 'Exactly-Once',
object_type => 'queue',
remotejndiname => 'jms/DemoQueue',
unitoforderrouting => 'Hash',
usetimetolivedefault => '0',
}
In this example you are managing a SAF imported destination object in the default domain. When you want to manage a SAF imported destination object in a specific domain, you can use:
wls_saf_imported_destination_object { 'my_domain/jmsClusterModule:SAFImportedDestinations-0:SAFDemoTopic':
ensure => 'present',
nonpersistentqos => 'Exactly-Once',
object_type => 'topic',
remotejndiname => 'jms/DemoTopic',
timetolivedefault => '100000000',
unitoforderrouting => 'Hash',
usetimetolivedefault => 1,
}
Properties
The following properties are available in the wls_saf_imported_destination_object
type.
ensure
Valid values: present
, absent
The basic property that the resource should be in.
Default value: present
Parameters
The following parameters are available in the wls_saf_imported_destination_object
type.
provider
The specific backend to use for this wls_saf_imported_destination_object
resource. You will seldom need to specify
this --- Puppet will usually discover the appropriate provider for your platform.
wls_saf_remote_context
This resource allows you to manage a SAF remote contexts in a JMS Module of a WebLogic domain.
Here is an example on how you should use this:
wls_saf_remote_context { 'jmsClusterModule:RemoteSAFContext-0':
ensure => 'present',
connect_url => 't3://10.10.10.10:7001',
weblogic_user => 'weblogic',
weblogic_password => 'weblogic1',
}
In this example you are managing a SAF remote contexts in the default domain. When you want to manage a SAF remote contexts in a specific domain, you can use:
wls_saf_remote_context { 'my_domain/jmsClusterModule:RemoteSAFContext-1':
ensure => 'present',
connect_url => 't3://10.10.10.10:7001',
}
Properties
The following properties are available in the wls_saf_remote_context
type.
ensure
Valid values: present
, absent
The basic property that the resource should be in.
Default value: present
Parameters
The following parameters are available in the wls_saf_remote_context
type.
provider
The specific backend to use for this wls_saf_remote_context
resource. You will seldom need to specify this --- Puppet
will usually discover the appropriate provider for your platform.
wls_safagent
This resource allows you to manage a SAF agent in an WebLogic domain.
Here is an example on how you should use this:
wls_safagent { 'jmsSAFAgent1':
ensure => 'present',
persistentstore => 'jmsFileSAFAgent1',
persistentstoretype => 'FileStore',
servicetype => 'Sending-only',
target => ['wlsServer1'],
targettype => ['Server'],
}
In this example you are managing a SAF agent in the default domain. When you want to manage a SAF agent in a specific domain, you can use:
wls_safagent { 'my_domain/jmsSAFAgent2':
ensure => 'present',
servicetype => 'Both',
target => ['wlsServer2'],
targettype => ['Server'],
}
Properties
The following properties are available in the wls_safagent
type.
ensure
Valid values: present
, absent
The basic property that the resource should be in.
Default value: present
Parameters
The following parameters are available in the wls_safagent
type.
provider
The specific backend to use for this wls_safagent
resource. You will seldom need to specify this --- Puppet will
usually discover the appropriate provider for your platform.
wls_security_policy
This resource allows you to manage security authorization policies in an WebLogic Security Realm.
Properties
The following properties are available in the wls_security_policy
type.
ensure
Valid values: present
, absent
The basic property that the resource should be in.
Default value: present
Parameters
The following parameters are available in the wls_security_policy
type.
provider
The specific backend to use for this wls_security_policy
resource. You will seldom need to specify this --- Puppet
will usually discover the appropriate provider for your platform.
wls_security_realm
This resource allows you to manage an existing security realm.
Here is an example on how you can do this: wls_security_realm { 'my_domain/myrealm': ensure => 'absent', auto_restart_on_non_dynamic_changes => 0, combined_role_mapping_enabled => 1, delegate_mbean_authorization => 1, deployable_provider_synchronization_enabled => 0, deployable_provider_synchronization_timeout => 60000, fully_delegate_authorization => 0, retire_timeout_seconds => 60, security_dd_model => 'DDOnly', }
At this point in type Puppet doesn't support creating a new security realm or removing an existing realm.
Properties
The following properties are available in the wls_security_realm
type.
ensure
Valid values: present
, absent
The basic property that the resource should be in.
Default value: present
Parameters
The following parameters are available in the wls_security_realm
type.
provider
The specific backend to use for this wls_security_realm
resource. You will seldom need to specify this --- Puppet will
usually discover the appropriate provider for your platform.
wls_server
This resource allows you to manage server in an WebLogic domain.
Here is an example on how you should use this:
wls_server { 'wlsServer2':
ensure => 'present',
arguments => '-XX:PermSize=256m -XX:MaxPermSize=256m -Xms752m -Xmx752m -Dweblogic.Stdout=/var/log/weblogic/wlsServer2.out -Dweblogic.Stderr=/var/log/weblogic/wlsServer2_err.out',
jsseenabled => '0',
listenaddress => '10.10.10.200',
listenport => '8001',
listenportenabled => 1,
log_file_min_size => '2000',
log_filecount => '10',
log_number_of_files_limited => 1,
log_rotate_logon_startup => 1,
log_rotationtype => 'bySize',
logfilename => '/var/log/weblogic/wlsServer2.log',
log_datasource_filename => 'logs/datasource.log',
log_http_filename => 'logs/access.log',
log_http_format => 'date time cs-method cs-uri sc-status',
log_http_format_type => 'common',
log_http_file_count => '10',
log_http_number_of_files_limited => '0',
log_redirect_stderr_to_server => '0',
log_redirect_stdout_to_server => '0',
logintimeout => '5000',
restart_max => '2',
machine => 'Node2',
sslenabled => 1,
sslhostnameverificationignored => 1,
ssllistenport => '8201',
two_way_ssl => '0',
client_certificate_enforced => '0',
default_file_store => '/path/to/default_file_store/',
max_message_size => '25000000',
weblogic_plugin_enabled => 1,
}
In this example you are managing a managed server in the default domain. When you want to manage a managed server in a specific domain, you can use:
wls_server { 'my_domain/wlsServer1':
ensure => 'present',
arguments => '-XX:PermSize=256m -XX:MaxPermSize=256m -Xms752m -Xmx752m -Dweblogic.Stdout=/var/log/weblogic/wlsServer1.out -Dweblogic.Stderr=/var/log/weblogic/wlsServer1_err.out',
jsseenabled => '0',
listenaddress => '10.10.10.100',
listenport => '8001',
listenportenabled => 1,
machine => 'Node1',
sslenabled => '0',
tunnelingenabled => '0',
max_message_size => '10000000',
}
Properties
The following properties are available in the wls_server
type.
ensure
Valid values: present
, absent
The basic property that the resource should be in.
Default value: present
Parameters
The following parameters are available in the wls_server
type.
provider
The specific backend to use for this wls_server
resource. You will seldom need to specify this --- Puppet will usually
discover the appropriate provider for your platform.
wls_server_channel
This resource allows you to manage a server channel in an WebLogic domain.
Here is an example on how you should use this:
What are tasks?
Modules can contain tasks 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.
Tasks in this module release
History
3.23.0
- [wls_rcu] Add support for optional sysdba on connecting
3.22.1
- [wls_server] Add state 'failed' to list of posible states
- [core] Handle empty target and targettype
- [wls_deployment] Allow modify without versionidentifier property
- [wls_workmanager,wls_demployment] Allow spaces in name
- [core] Fix when target is null and targettype is not null
3.22.0
- [core] Added extended properties generated from 12.2.1.4
- [wls_rcu] Quote password for use with special characters
3.21.0
- [core, wls_setting] Add support for providing extra wlst cmdline arguments
3.20.0
- [core] Add support for Ruby 3.2 and Puppet 8
3.19.0
- [wls_domain] Add webappcontainer and webappcompression extra properties
3.18.0
- [core] Add support for EL9
- [docs] Small update to the documentation
3.17.3
- [wls_opatch] Fix reinstall of remove_patches_before patches
3.17.2
- [wls_opatch] Fix reinstall of remove_patches_before patches
3.17.1
- [wls_opatch] Fix SPB patching patch locator
3.17.0
- [wls_server] Add support for restart managed on notify
3.16.4
- [wls_opatch] Add support for non-zipped spb subpatches
3.15.3
- [wls_foreign_server_object] Allow special characters in object(_name)
3.15.2
- [wls_deployment] Fix the way the timeout is passed to wlst
3.15.1
- [wls_opatch] Unzip files as oracle user
3.15.0
- [release] Add support for AlmaLinux and Rocky
3.14.5
- [core] Fix LocalJumpError when using disable_autorequire
3.14.4
- [wls_deployment] Fix refactoring error
3.14.3
- [wls_domain] Special implementation for security_remote_anonymous_rmi_t3_enabled
3.14.2
- [core] No reversal of relations on wls_domain and wls_setting
3.14.1
- [wls_exec] Fix logoutput on empty logs
3.14.0
- [wls_exec] Better implementation of the logoutput
- [wls_opatch] Add support for sub_patches and logoutput
3.13.2
- [wls_server] add domain_name parameter
3.13.1
- [wls_deployment] Fix indeting issue in template script
3.13.0
- [wls_domain] Add properties securityremote_anonymous_rmi(iiop|t3)_enabled
- [core] Remove the save() before activate() wlst actions
3.12.2
- [wls_opatch] Add support for parameter remove patches_before
3.12.1
- [wls_server] Remove warning about not set custom_identity
3.12.0
- [wls_domain] Implement security_connection_filter_rules
3.11.1
- [wls_deployment] Fix refacter errors
3.11.0
- [wls_daemon] Initial implementation
- [daemon] Add restart functionality
3.10.1
- [release] Add support for RHEL 8
- [core] Add posibility to override autorequire on wls_setting
3.10.0
- [core] Fix refacter errors
- [wls_log_filter] Initial implementation
- [wls_domain] Add console extended parameters
- [core] Allow an empty string on all extended string properties
- [core] Fix some errors from the refacter
- [core] Debug the full command for access wlst
- [wls_jdbc_persistence_store] Fix data type for prefix_name
- [wls_jms_topic] Fix data type for jndiname
- [wls_jms_queue] Fix data type for jndiname
- [wls_foreign_jndi_provider] Fix data type for provider_properties
3.9.0
[wls_server] Add properties for webserver and wbserver_log [wls_server] Remove default values for properties [wls_migratable_target] Remove defaults for properties [wls_machine] Remove defaults for multiple properties [wls_datasource] Remove defaults for multiple properties [wls_cluster] Remove default values for messagingmode and migration basis [doc] Updated docs and REFERENCE.md
3.8.2
- [core] Fix autorequire on wls_setting
3.8.1
- [wls_role] Fix error 'Invalid parameter disable_autorequire'
3.8.0
- [core] Add support to disable autorequire on a specific resource
- [core] Add time measurements to individual operations to aid debugging
3.7.1
- [wls_deployment] Fix identification of default version number [ch806]
- [documentation] Fix typo
3.7.0
- [release] Add puppet 7 to supported versions in metadata
3.6.1
- [wls_af_imported_destination_object] Fix internal error
- [wls_foreign_server_object] Fix internal error
3.6.0
- [core] Handle the difference between WebLogic 14 and older versions regarding numbered booleans
- [wls_multi_datasource] Fix for using nil values instead of empty strings
- [wls_datasource] Fix for using nil values instead of empty strings
- [core] Don’t change empty values to empty strings anymore. Use null values
- [wls_authentication_provide] Fix message when control_flag is not available
- [wls_group] Add prefetching provider
- [wls_user] Add prefetching provider
- [wls_setting] Encrypt weblogic_password and trust_keystore_passphrase for more security
- [wls_jmsserver] Fix issue with migratable targets
- [core] Fix error in weblogic access
- [task/stop_adminserver] Fix detection of running server
- [wls_rcu] Fix data types
- [wls_user] Add password_reset property
- [wls_jmsserver] Fix issue with migratable targets
- [core] Ensure compatibility between older and newer versions
- [wls_deployment] Fix versionidentifier on higher puppet versions
- [wls_mail_session] Fix data type for mailprperty
- [wls_deployment] Fix data type for targettype
- [wls_multi_datasource] Fix datatype for jndinames property
- [wls_foreign_server] Fix extraproperties property
- [wls_datasource] Fix format of jndinames and extraproperties properties
- [wls_authentication_provider] Fix case of allowed control_flag values
3.5.1
- [wls_jmsserver] Fix issue with migratable targets
3.5.0
- [core] Add support for AIX
3.4.2
- [wls_server] Fix custom_identity detection
- [docs] update documentation
3.4.1
- [daemon] Make timeout for initial connect longer and configurable
- [wls_server] Make the sync for started state more rubust.
3.4.0
- [wls_jms_connection_factory] Make delivery_default_unit_of_order accept any string
- [wls_path_service] Use persistentstoretpe to determine what type of store to user
- [wls_jms_security_policy] Fix when tunning under Puppet version 5
- [wls_path_service] Initial implementation
3.3.17
- [tasks] Add support for loading local libraries
- [wls_server] Add support for synced start and stop based on state property and synced_start_stop parameter
3.3.16
- [wls_server] Fix starting a newly created or modfied server
- [docs] Fix documentation issues
- [wls_opatch] Fix error when source doesn’t contain subdit with patch
- [wls_jms_queue] Fix errordestination for Puppet 6
- [wls_jms_topic] Fix errordestination for Puppet 6
- [wls_jmsserver] Fix persistentstore for Puppet 6
3.3.15
- [release] Fix release
3.3.14
- [core] Don’t fetch the properties when the resource tag leads to not including the resource
3.3.13
- [wls_jms_topic] handle case where messages_limit_override is not available
3.3.12
- [core] Make fetching values more robust
- [core] Don’t undo when just fetching value from wls daemon
3.3.11
- [acceptance] Move acceptance test for wls_dynamic_cluster to work queue
- [core] Better handle errounous returns from wlst
3.3.10
- [tasks] Harmonize timout of startup and shutdown tasks to 300 seconds
3.3.9
- [tasks] Fix timout of start_managed_servers
3.3.8
- [core] Make start and stop server more robust
- [tasks] Add unit tests and refacter code
3.3.7
- [tasks] Fix syntax error
3.3.6
- [tasks] Fix fetching of state
3.3.5
- [tasks] Better implementations of the stop and start tasks
- [core] Better error message when AdminServer doesn’t run
3.3.4
- [tasks] Make wait the default and accept also strings for booleans and Integers
- [start_managed_servers] Add option to wait for shutdown with a specified timeout
- [stop_adminserver] Add option to wait for shutdown with a specified timeout
- [stop_managed_servers] Add option to wait for shutdown with a specified timeout
- [acceptance] Use puppet 6 for acceptance tests
- [core] At puppet 6 unit tests
- [core] Update wls_server documentation (#26)
3.3.3
- [acceptance] Speedup acceptance tests
- [wls_datasource] Add test with quoted values
- [core] Fix quoted values
3.3.2
- [stop_managed_servere] Notice stopped managed server
- [wls_server] Fix getting state property
3.3.1
- [wls_coherence_cluster] Fix setting targets
- [core] Change implementation to get value from different runtimes
- [wls_server] Add state failed_not_restartable as shutdown state
- [stop_managed_servers] Add state FAILED_NOT_RESTARTABLE as shutdown state
3.3.0
- [stop_managed_server] Refactored. Check for non existing domain
- [stop_admin_server] Refactored. Check for non existing domain
- [start_managed_server] Refactored. Check for non existing domain
- [core] Add support fot getting name of the managed servers and the admin server
- [core] Fix issue with changing trees
- [stop_admin_server] Add initial implementation for the task
- [stop_managed_servers] Add initial implementation for the task
- [start_managed_servers] Add initial implementation for the task
- [wls_server] remove duplicate state
- [core] Fix error handling when starting and stopping servers
- [core] Add support for getting values in multiple runtimes
- [wls_server] refactered state property
- [devop] Add docker container voor easy development
- [wls_server] Add support for managing state
- [core] Add support for stopping and starting servers
- [core] Add support for fetching domain runtime values
- [core] Add support for absolute paths in property
3.2.4
- [core] domain validity check to type pre_run_check
3.2.3
- [wls_datasource] Fix sorting issues on idempotence of extraproperty
- [wls_server] Add migration_constrained_candidate_servers property
- [wls_security_policy] Fix setting policy for modules
3.2.2
- [core] Fix load order
3.2.1
- [core] Fix and enhance setting security policies
- [wls_jms_module] Fix removing security policy
- [wls_security_policy] Fix usage of operation for setting security policy
3.2.0
- [wls_jms_topic] Add property messages_limit_override
- [wls_jms_topic] Add extra properties for TopicSubscriptionParams in jms_topic
3.1.0
- [wls_exec] Fix type and add acceptance test
- [core] mediate error’s when using autorequire
- [wls_security_policy] Fix setting JMX security policies
- [wls_security_policy] Initial implementation
- [wls_migratable_target] fix user_preferred_server property
- [wls_migratable_target] Fix acceptance tests
- [wls_migratable_target] make user_prefered_server an array property
- [wls_server] Add basic JTA migration properties
- [wls_security_realm] First implementation of type
- [core] Change all numbered booleans to type
- [wls_deployment] Implement a refreshonly parameter
- [core] Add integer and float data types for properties
- [release] Fix easy_type version requirement
- [wls_managed_executor_service_template] Make max_concurrent_long_running_requests an integer
- [wsl_datasource] Handle special case when request min is higher than max and vice versa
- [wls_jms_topic] Skip acceptance test on template name for now
- [wls_managed_executor_service_template] Initial implementation
3.0.22
- [wls_datasource] Fix mapping of data_source_for_job_scheduler & data_source_for_session_persistence
3.0.21
- [core] Add support for MigratableTarget in targttype list
- [wls_opatch] Move output to debug
- [wls_rcu] Less output on regular run.
3.0.20
- [release] Prepare for release to forge
3.0.19
- [wls_opatch] Add support for remote files
- [wls_jms_security_policy] Fail when JMS resource doesn’t exist
3.0.18
- [wls_domain_partition_resource_group_deployment] Fix title attributes
- [wls_jms_security_policy] Fix title attributes
3.0.17
- [wls_jms_module] Fix typo in policyexpression
- [core] Allow empty strings in properties
3.0.16
- [core] Loosen requirements for easy_type
3.0.15
- [wls_deployment] Use specified timeout for wlst deploy and undeploy operations
3.0.14
- [wls_jms_module] Add property policyexpression
- [tree] Added support for getting and setting security policy
- [core] Add support for getting resource id to common
3.0.13
- [wls_authantication_provider] confine provide until wls running
- [wls_deployment] confine provide until wls running
- [wls_exec] Confine provider
- [wls_authentication_provider] Small performance fix
- [wls_deployment] Add support for purging
- [wls_jms_queue] Add support for purging
- [wls_jms_topic] Add support for purging
- [core] Add support for only fetching specified properties
- [core] Add support for prefetching only specified resources
- [wls_deployment] Better handling of validation
- [wls_jms_queue] Add path to error messages
- [wls_jms_topic[ Add path to error messages
- [wls_datasource] Add domain_name parameter
- [travis] Fix run on ruby 2.1
- [wls_jms_queue] No validation when we’re absenting
- [wls_datasource] use default on datasource_type when non-existend
- [wls_jms_queue] Add path to validation errors
- [core] Fix universal usage of to_hash
- [core] Fix auto purge in combination with manual absenting
- [wls_jms_topic] Support for auto purging
- [wls_jms_queue] Fix autopurging with errorque of type topic
- [wls_jms_topic] Fix autopurging with errorque of type queue
- [core] Fix autopurging of resources with a current relation
- [wls_datasource] Add support for datasource_type
- [wls_cluster] Fix template name
- [wls_setting] Not ensurable
- [wls_authentication_provider] Fix bug when absenting
- [core] Use templates in provider folder
- [wls_cluster] remove the autorequire
- [wls_settings] Fix ensurable property
- [core] Move templates into the providers
- [wls_datasource] Map data_source_for_automatic_migration to path istead of value
- [wls_cluster] remove the default on migration_table_name
- [core] Fix Error: no parameter named 'domain_name' error
- [wls_cluster] Fix autorequire for unicastbroadcastchannel
- [core] Add support for absenting in child_of
- [wls_cluster] Autorequire unicastbroadcastchannel
- [wls_server] Add overload protection properties. Closes #15
- [wls_cluster] Add overload protection properties
- [wls_cluster] Added JTA properties
- [meta] Use meta code on Vagrant box
- [wls_jms_topic] Remove defaults for all properties
- [wls_jms_queue] Remove default for all properties
- [wls_cluster] Add propery candidate_machines_for_migratable_servers
- [core] Fix autorequire for targets
- [wls_role] Add unit and acceptance test
- [core] Moved the parent_of method to access
- [core] make targets property code better understandable.
- [testing] Add more parallel unit tests
- [testing] Add simple jenkins file
- [core] Make sure the code only run’s when AdminServer is running
- [wls_jms_queue] Remove queue without specifying distribution
- [wls_deployment] Add autosubscribe to planpath
- [core] Fix usage of autobefore on puppet versions older then 4.0
- [wls_server] Fix removing servers part of a cluster. Closes #18
- [core] Add support for clearing values
- [core] Fix autorequires when ensuring absent
3.0.12
- [wls_deployment] Fix redeployments when new version is found
- [wls_jms_topic] Add templatename property
3.0.11
- [core] Fix error in creating WLS paths
3.0.10
- [wls_deployment] Synchronous deployments
- [wls_jndi_security_policy] Add extra diconnect from managed server
- [core] Rmove ora_install facts
- [core] Remove old source file
- [wls_server] Add property synchronous_write_policy
- [docs] Fixed link in the readme
- [core] Remove old template
3.0.9
- [docs] Updated documentation
- [core] Handle invalid weblogic names with an error
- [wls_server] log_rotationtype description fixed
- [wls_opatch] Fix error in index phase from provider
- [wls_jmsserver] Dont’ resturn a persistentstore type if no presistent store
- [wls_workmanager] Fix title parsing
- [wls_workmanager] Use correct domain_name for wlst path
- [core] extend type api to allow access to real domain name
- [wls_opatch] Name file was still empty
- [wls_opatch] Hanle spaces in product home dir
- [wls_jndi_security_policy] comment out some of the tests
- [acceptance] Speed up the tests
- [wls_server_tlog] tlog_datasource_prefix doesn’t support absent
- [wls_coherence_cluster] Don’t test storage_enabled for now
- [wls_saf_imported_destination_object] Fix acceptance test
- [wls_workmanager] Fix issue when real domain name is different then wls_setting domain name
- [core] Fix issue when real domain name is different then wls_setting domain name
- [wls_coherence_cluster] Make spec’s run without error
- [wls_opatch] Fix wrong number of arguments error
- [core] Make Vagrant file easier
- [unittest] Fix type tests
- [core] Rubular fixes
- [core] refacter autorequire_when
- [wls_settings] Fix acceptance test
- [wls_foreign_server] Fix acceptance test
- [wls_domain] Fix acceptance test
- [core] Update to new add_title_attributes
- [core] Fix autorequires to check for empty values
- [core] Fix way to set absent values
3.0.8
- [all] migrated to easy_type 2.1
- [wls_jndi_security_policy] Ensure reconnection to AdminServer
- [wls_deployment] Fix error in destroy
- [wls_jndi_security_policy] Add unit and acceptance tests
- [acceptance] Refactored all test to new box
- [wls_deployment] Fix NameError in error handler
- [wls_jndi_security_policy] Fix action all for non-root elements
- [wls_jndi_security_policy] Fix error on creation in other server
- [core] no more caching of the wls_settings. Fixes purging errors in run.
- [wls_jndi_security_policy] Add support for managing root entries
- [core] Improve even more on reconnect algorithm
- [core] Improve disconnection detection
- [wls_jms_queue] Use specified errordestinationtype for setting errordestination
- [wls_jms_topic] Use specified errordestinationtype for setting errordestination
- [wls_jndi_security_policy] Fixed the hang when creating the resources
- [wls_jndi_security_policy] Connect to listenaddress
- [wls_jndi_security_policy] Make policy per wls server
- [wls_jndi_security_policy] Add correct files
- [wls_jndi_security_policy] Initial implementation
- [wls_deployment] Handle when error is raised before deployment is started
- [wls_default_role_mapper] Initial implementation
- [wls_deploy] Improved error reporting on deployment errors
- [core] Sync on defintion of common methods
- [core] setting target doesn’t support absent
- [wls_jms_topic] Fix spec for expirationpolicy set to Redirect
- [wls_jms_queue] Fix spec for expirationpolicy set to Redirect
- [wls_cluster] Fix clusteraddress property. Is not an array
- [wls_deployment] No check on localpath when ensure=absent
- [core] Don’t get realm and realm_path on every type
- [core] Fix support on abseting for references and arrays
- [core] Make acceptance test wait for started Managed Server
- [core] Refacter success and error reporting from wlst to ruby
- [core] refacter wls code for error & success handling
- [core] Add vagrantfile for testing
- [wls_deployment] Added some validation checks. Closes #9
3.0.7
- [wls_server] remove server directory containing all files when destroying a server
- [wls_server] Add parameter create_boot_properties and deprecated it’s use
3.0.6
- [wls_server] Fix invalid group setting for boot.properties. Closes #6
- [core] Extract rake tesks to easy_type
- [wls_role] Fix implementation
- [wls_opatch] Fix working
3.0.5
- [wls_jms_jopic] Fix destroy action
- [wls_jms_queue] Fix destroy action
- [core] Make ruby load path more consistent
- [wls_deployment] Fixes in method for version identification
- [wls_server] Better secure the boot files
- [wls_deployment] Fix detection of current installed version
- [core] Change load procedure for ruby requires
3.0.4
- [wls_server] Fix puppet 3.6.8. issue on Arrays
- [core] Fix target setting on Puppet 3.6.8
- [core] Added werker.yml for CI
- [wls_datasource] Fix typo in help text
- [core] Add correct geppetto project file
- [wls_authentication_provider] Fiox fetching of secured properties
- [wls_authentication_provider] Fetch index from edit tree
- [core] Add geppetto project file
- [wls_authentication_provider] Fix getting security realm
- [wls_deploy] Make first deployments more robust
- [wls_deployment] Add extra check on file existence
- [wls_deployment] Added extra save when doing redeploy
- [wls_deployment] Add unit spec's
- [wls_deployment] Add deployment_order property
3.0.3
- [wls_datasource] Fix ruby 1.8.7 incompatibility
- [wls_server_channel] Allow -1 on property publicport
- [wls_af_imported_destination_object} Fix mapping of property usetimetolivedefault
- [wls_cluster] Fix index condition when templates do not exist
- [wls_server] Move creation of boot.proerties into ruby.
- [core] Fix ruby 1.8.7 incompatibilities
- [wls_setting] Fix when yaml file is not valid
- [wls_cluster] Allow array on clusteraddress
- [core] Fix issue with symbols versus strings in type processing
- [wls_datasource] Fix updating the user property.
3.0.2
- [wls_domain] Fix fetching name
- [core] Move some informational messages to debug
- [wls_deployment] Is not a standardized wls resource
- [core] Use correct path when fetching a top level variable from wls
3.0.1
- Filtering password information from debug and error log
3.0.0
- Adhere to the naming standards of Puppet.
- Use newest version of easy_type with better error reporting of the daemons
- Implement new WebLogic core with better error reporting
- implement extra properties so almast the full spectrum of properties is supported
- Add support for WebLogic 12.2.1
- Add Unit tests for
- Add Acceptance tests
2.1.0
- Added some extensive checks to the parameters
- Added better documentation
- Compatible with orawls version 1.0.46
2.0.0
- Renamed to enterprisemodule/wls_config
Dependencies
- enterprisemodules/easy_type (>=2.41.1 < 3.0.0)
Enterprise Modules License d.d. January 2018 This license (“License”) governs the terms and conditions under which wls_config module (“the Software”) is licensed by Enterprise Modules B.V, a limited liability company in the Netherlands, registered in the Dutch Chamber of Commerce: 63689537 (“Licensor”), to the user of the Software (“Licensee”). Article 1. Grant of license 1.1 Licensor hereby grants to Licensee the right to use the Software for its internal business purposes. 1.2 The license granted in the previous paragraph is limited to the use on VirtualBox Virtual machines. For further use a commercial license must be directly obtained from Licensor. Article 2. License limitations 2.1 All right, title and interest to the Software, the accompanying documentation and all modifications and extensions thereto rest and remain with Licensor. Licensee only has the rights and permissions explicitly granted by this License or granted in writing otherwise. Licensee shall not use, copy, modify, distribute or publish the Software in any other manner. Nothing in this License is intended to, and shall not be construed to, transfer to Licensee any rights in intellectual property developed by Licensor. 2.2 In particular, Licensee shall not: a) provide copies of the Software to third parties, including to entities controlling, controlled by or under common control with Licensee; b) sublicense the Software or otherwise make available the Software to such third parties, including by rental, Software-as-a-Service models or otherwise; c) remove indications of Licensor as copyright holder of the Software or to remove or render illegible any part thereof. 2.3 The Software comprises third-party open source software. The respective third-party rights holders grant Licensee the rights indicated in the applicable open source licenses. These licenses can be found in the documentation. The License does not apply to this open source software, and nothing in this License shall be construed as a limitation of any right granted under an open source license. Article 3. Trademark 3.1 This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Software. Article 4. Limitation of Liability 4.1 Licensor provides the Software on an "AS IS" basis, and expressly disclaims all conditions, representations or warranties, express or implied, including without limitation any implied warranties of merchantability, fitness for a particular purpose, and non-infringement of third party rights regarding the Software. Licensor is solely responsible for determining the appropriateness of using the Software and assume any risks associated arising out of or in connection with the Software and this License. 4.2 Licensor shall not be liable for any damages, including consequential, special, punitive and/or incidental damages or fines imposed by regulatory bodies, arising out of or in connection with the Software and this License. 4.3 Licensee shall release, defend, indemnify and hold harmless Licensor from and against any and all claims, damages and liability arising in connection with the Software, including from claims, damages or liability from customers of Licensee. Article 5. Miscellaneous 5.1 Licensor reserves the right to change any or all parts of this License without prior notice. 5.2 The law of the Netherlands governs this License and the terms and conditions therein. 5.3 Any disputes arising between Licensor and Licensee in connection with the License will be settled by the competent courts in the Netherlands for the principal place of business of the Licensor.