wls server

Overview

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',
}

When the resource receives a notify, it will check if the managed server is currently running. If it is, it will force a restart of the managed server. This will reload any new configuration.

Experience the Power of Puppet for WebLogic

If you want to play and experiment with Puppet and WebLogic, please take a look at our playgrounds. At our playgrounds, we provide you with a pre-installed environment, where you experiment fast and easy.

For WebLogic   here at our playground...

Attributes

accept_backlog

The number of backlogged, new TCP connection requests that should be allowed for this server’s regular and SSL ports. Setting the backlog to 0 may prevent this server from accepting any incoming connection on some operating systems.

An example on how to use this:

wls_server {a_wls_server :
   ...
   accept_backlog => '300'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:accept_backlog']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

add_work_manager_threads_by_cpu_count

Enables increased efficiency of the self-tuning thread pool by aligning it with the Exalogic processor architecture threading capabilities. Use only when configuring a WebLogic domain for Oracle Exalogic. <ul> <li>Enabling this attribute increases efficiency during I/O in environments with high network throughput.</li> <li>Disabling this attribute allows the thread pool to self-tune to match the demand of the workload at the expense of longer ramp up time.</li> </ul>

An example on how to use this:

wls_server {a_wls_server :
   ...
   add_work_manager_threads_by_cpu_count => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:add_work_manager_threads_by_cpu_count']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

admin_reconnect_interval_seconds

The number of seconds between reconnection attempts to the admin server. When the admin server fails the managed server will periodically try to connect back to it.

An example on how to use this:

wls_server {a_wls_server :
   ...
   admin_reconnect_interval_seconds => '10'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:admin_reconnect_interval_seconds']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

administration_port

The secure administration port for the server. This port requires that you enable the domain’s administration port and that SSL is configured and enabled. By default, the server uses the administration port that is specified at the domain level. To override the domain-level administration port for the current server instance, set this server’s administration port.

An example on how to use this:

wls_server {a_wls_server :
   ...
   administration_port => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:administration_port']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

administration_protocol

Returns the protocol to be used for administrative connections when none is specified.

An example on how to use this:

wls_server {a_wls_server :
   ...
   administration_protocol => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:administration_protocol']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

allow_shrinking_priority_request_queue

Whether the self-tuning should allow shrinking of its priority based queue for pending requests after it has grown in size due to busy workload. Setting this to true would help reduce memory footprint after the busy work period has ended, at the expense of the overhead of growing the request queue again at the next period of busy workload.

An example on how to use this:

wls_server {a_wls_server :
   ...
   allow_shrinking_priority_request_queue => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:allow_shrinking_priority_request_queue']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

arguments

The server start arguments of the server.

Can be specified as an array or a space separated string’

Back to overview of wls_server

auto_kill_if_failed

This is the equivalent of setting the OverloadProtectionMBean failureAction to “force-shutdown” and the panicAction to “system-exit”.

An example on how to use this:

wls_server {a_wls_server :
   ...
   auto_kill_if_failed => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:auto_kill_if_failed']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

auto_migration_enabled

Specifies whether Node Manager can automatically restart this server and its services on another machine if the server fails.

An example on how to use this:

wls_server {a_wls_server :
   ...
   auto_migration_enabled => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:auto_migration_enabled']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

auto_restart

Specifies whether the Node Manager can automatically restart this server if it crashes or otherwise goes down unexpectedly.

An example on how to use this:

...{...:
   ...
   autorestart => 1,
   ...
}

Help text generated from MBEan text.

Valid values are absent, 1, 0.

Back to overview of wls_server

autokillwfail

This is the equivalent of setting the OverloadProtectionMBean failureAction to “force-shutdown” and the panicAction to “system-exit”.

An example on how to use this:

...{...:
   ...
   autokilliffailed => 1,
   ...
}

Help text generated from MBEan text.

Valid values are absent, 1, 0.

Back to overview of wls_server

bea_home

The BEA home directory (path on the machine running Node Manager) to use when starting this server.

Back to overview of wls_server

buzz_address

Buzz endpoint address.

An example on how to use this:

wls_server {a_wls_server :
   ...
   buzz_address => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:buzz_address']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

buzz_enabled

Enables Buzz for sending/receiving messages with peers. Enabling this attribute increases efficiency during I/O in environments with high network throughput and should be used only when configuring a WebLogic domain for Oracle Exalogic.

An example on how to use this:

wls_server {a_wls_server :
   ...
   buzz_enabled => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:buzz_enabled']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

buzz_port

Buzz endpoint port. A value of 0 means system-allocated (dynamic) port.

An example on how to use this:

wls_server {a_wls_server :
   ...
   buzz_port => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:buzz_port']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

classpath

The classpath (path on the machine running Node Manager) to use when starting this server. At a minimum you will need to specify the following values for the class path option: WL_HOME/server/lib/weblogic_sp.jar;WL_HOME/server/lib/weblogic.jar where WL_HOME is the directory in which you installed WebLogic Server on the Node Manager machine. The shell environment determines which character you use to separate path elements. On Windows, you typically use a semicolon (;). In a BASH shell, you typically use a colon (:).

Back to overview of wls_server

classpath_servlet_disabled

The ClasspathServlet will serve any class file in the classpath and is registered by default in every Web application (including management). It does not need to be turned on for many applications though, and represents a security hole if unchecked.

An example on how to use this:

wls_server {a_wls_server :
   ...
   classpath_servlet_disabled => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:classpath_servlet_disabled']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

client_cert_proxy_enabled

Specifies whether the HttpClusterServlet proxies the client certificate in a special header. By default (or if you specify false), the weblogic.xml deployment descriptor for each web application that is deployed on this server determines whether the web application trusts certificates sent from the proxy server plugin. By default (or if the deployment descriptor specifies false), users cannot log in to the web application from a proxy server plugin. A value of true causes proxy-server plugins to pass identity certifications from clients to all web applications that are deployed on this server instance. A proxy-server plugin encodes each identify certification in the WL-Proxy-Client-Cert header and passes the header to WebLogic Server instances. A WebLogic Server instance takes the certificate information from the header, trusting that it came from a secure source, and uses that information to authenticate the user. If you specify true, use a weblogic.security.net.ConnectionFilter to ensure that this WebLogic Server instance accepts connections only from the machine on which the proxy-server plugin is running. Specifying true without using a connection filter creates a security vulnerability because the WL-Proxy-Client-Cert header can be spoofed. A cluster can also specify whether the HttpClusterServlet proxies the client certificate in a special header. The cluster-level setting overrides the setting in individual servers that are part of the cluster.

An example on how to use this:

wls_server {a_wls_server :
   ...
   client_cert_proxy_enabled => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:client_cert_proxy_enabled']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

client_certificate_enforced

Indicates whether or not clients must present digital certificates from a trusted certificate authority to WebLogic Server.

An example on how to use this:

...{...:
   ...
   clientcertificateenforced => 1,
   ...
}

Help text generated from MBEan text.

Valid values are absent, 1, 0.

Back to overview of wls_server

cluster_weight

The proportion of the load that this server will bear, relative to other servers in a cluster. If all servers have the default weight or the same weight, each bears an equal proportion of the load. If one server has weight 50 and all other servers have weight 100, the 50-weight server will bear half as much load as any other server.

An example on how to use this:

wls_server {a_wls_server :
   ...
   cluster_weight => '100'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:cluster_weight']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

coherence_cluster_system_resource

The system-level Coherence cluster resource associated with this server.

An example on how to use this:

wls_server {a_wls_server :
   ...
   coherence_cluster_system_resource => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:coherence_cluster_system_resource']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

com_enabled

Specifies whether COM support is enabled on the regular (non-SSL) port. COM is not supported on the SSL port. (The remaining fields on this page are relevant only if you check this box.)

An example on how to use this:

wls_server {a_wls_server :
   ...
   com_enabled => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:com_enabled']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

complete_com_message_timeout

The maximum number of seconds spent waiting for a complete COM message to be received. This setting does not apply to any network channels that you have configured for this server. This timeout helps guard against a denial of service attack in which a caller indicates that they will be sending a message of a certain size which they never finish sending.

An example on how to use this:

wls_server {a_wls_server :
   ...
   complete_com_message_timeout => '-1'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:complete_com_message_timeout']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

complete_http_message_timeout

The maximum number of seconds spent waiting for a complete HTTP message to be received. If you configure network channels for this server, each channel can override this HTTP message timeout. This timeout helps guard against a denial of service attack in which a caller indicates that it will be sending a message of a certain size which it never finishes sending. A value of -1 indicates that this value should be obtained from network channels configured for this server.

An example on how to use this:

wls_server {a_wls_server :
   ...
   complete_http_message_timeout => '-1'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:complete_http_message_timeout']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

complete_iiop_message_timeout

The maximum number of seconds spent waiting for a complete IIOP message to be received. This timeout helps guard against denial of service attacks in which a caller indicates that they will be sending a message of a certain size which they never finish sending.

An example on how to use this:

wls_server {a_wls_server :
   ...
   complete_iiop_message_timeout => '-1'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:complete_iiop_message_timeout']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

complete_message_timeout

The maximum number of seconds that this server waits for a complete message to be received. If you configure network channels for this server, each channel can override this message timeout. This timeout helps guard against a denial of service attack in which a caller indicates that it will be sending a message of a certain size which it never finishes sending. CompleteMessageTimeout affects the HTTP Response, such that if WebLogic Server discovers sockets inactive for longer than the CompleteMessageTimeout, the server will close these sockets.

An example on how to use this:

wls_server {a_wls_server :
   ...
   complete_message_timeout => '60'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:complete_message_timeout']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

complete_t3_message_timeout

The maximum number of seconds spent waiting for a complete T3 message to be received. If you configure network channels for this server, each channel can override this T3 message timeout. This timeout helps guard against a denial of service attack in which a caller indicates that it will be sending a message of a certain size which it never finishes sending.

An example on how to use this:

wls_server {a_wls_server :
   ...
   complete_t3_message_timeout => '-1'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:complete_t3_message_timeout']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

complete_write_timeout

The maximum number of seconds that this server waits for a complete HTTP response to be sent. A value of 0 disables the complete write timeout. The default value is derived from the CompleteHTTPMessageTimeout. If it is -1, then the CompleteMessageTimeout value is used for the default value.

An example on how to use this:

wls_server {a_wls_server :
   ...
   complete_write_timeout => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:complete_write_timeout']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

connect_timeout

The amount of time that this server should wait to establish an outbound socket connection before timing out. A value of 0 disables server connect timeout.

An example on how to use this:

wls_server {a_wls_server :
   ...
   connect_timeout => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:connect_timeout']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

create_boot_properties

Specifies if you want puppet to create a boot.properties file. (deprecated)

The default value is false. You don’t need a boot.properties file for a managed server when you are planning to have it started by a nodemanager. This is a boolean parameter.

This is a deprecated method. In future versions of the type, we will remove the ability to create a boot.properties file.

Valid values are true, false, yes, no.

Back to overview of wls_server

custom_identity

The custom_identity true or false.

Valid values are 1, 0.

Back to overview of wls_server

custom_identity_alias

The custom identity alias.

Back to overview of wls_server

custom_identity_key_store_file_name

The source of the identity keystore. For a JKS keystore, the source is the path and file name. For an Oracle Key Store Service (KSS) keystore, the source is the KSS URI. If using a JKS keystore, the keystore path name must either be absolute or relative to where the server was booted. If using a KSS keystore, the keystore URI must be of the form:
"kss://system/keystorename"
where "keystorename" is the name of the keystore registered in KSS. The value in this attribute is only used if KeyStores is CUSTOM_IDENTITY_AND_JAVA_STANDARD_TRUST, CUSTOM_IDENTITY_AND_CUSTOM_TRUST or CUSTOM_IDENTITY_AND_COMMAND_LINE_TRUST.

An example on how to use this:

wls_server {a_wls_server :
   ...
   custom_identity_key_store_file_name => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:custom_identity_key_store_file_name']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

custom_identity_key_store_pass_phrase

The encrypted custom identity keystore’s passphrase. If empty or null, then the keystore will be opened without a passphrase. This attribute is only used if KeyStores is CUSTOM_IDENTITY_AND_JAVA_STANDARD_TRUST, CUSTOM_IDENTITY_AND_CUSTOM_TRUST or CUSTOM_IDENTITY_AND_COMMAND_LINE_TRUST. When you get the value of this attribute, WebLogic Server does the following: <ol><li>Retrieves the value of the CustomIdentityKeyStorePassPhraseEncrypted attribute.</li> <li>Decrypts the value and returns the unencrypted password as a String.</li> </ol> When you set the value of this attribute, WebLogic Server does the following: <ol><li>Encrypts the value.</li> <li>Sets the value of the CustomIdentityKeyStorePassPhraseEncrypted attribute to the encrypted value.</li> </ol> Using this attribute (CustomIdentityKeyStorePassPhrase) is a potential security risk because the String object (which contains the unencrypted password) remains in the JVM’s memory until garbage collection removes it and the memory is reallocated. Depending on how memory is allocated in the JVM, a significant amount of time could pass before this unencrypted data is removed from memory. Instead of using this attribute, use CustomIdentityKeyStorePassPhraseEncrypted.

An example on how to use this:

wls_server {a_wls_server :
   ...
   custom_identity_key_store_pass_phrase => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:custom_identity_key_store_pass_phrase']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

custom_identity_key_store_type

The type of the keystore. Generally, this is JKS. If using the Oracle Key Store Service, this would be KSS If empty or null, then the JDK’s default keystore type (specified in java.security) is used. The custom identity key store type is only used if KeyStores is CUSTOM_IDENTITY_AND_JAVA_STANDARD_TRUST, CUSTOM_IDENTITY_AND_CUSTOM_TRUST or CUSTOM_IDENTITY_AND_COMMAND_LINE_TRUST.

An example on how to use this:

wls_server {a_wls_server :
   ...
   custom_identity_key_store_type => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:custom_identity_key_store_type']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

custom_identity_keystore_filename

The custom identity keystore filename.

Back to overview of wls_server

custom_identity_keystore_passphrase

The custom identity keystore passphrase.

Back to overview of wls_server

custom_identity_privatekey_passphrase

The custom identity privatekey passphrase.

Back to overview of wls_server

custom_trust_key_store_file_name

The source of the custom trust keystore. For a JKS keystore, the source is the path and file name. For an Oracle Key Store Service (KSS) keystore, the source is the KSS URI. If using a JKS keystore, the keystore path name must either be absolute or relative to where the server was booted. If using a KSS keystore, the keystore URI must be of the form:
"kss://system/keystorename"
where "keystorename" is the name of the keystore registered in KSS. The value in this attribute is only used if KeyStores is CUSTOM_IDENTITY_AND_CUSTOM_TRUST.

An example on how to use this:

wls_server {a_wls_server :
   ...
   custom_trust_key_store_file_name => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:custom_trust_key_store_file_name']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

custom_trust_key_store_pass_phrase

The custom trust keystore’s passphrase. If empty or null, then the keystore will be opened without a passphrase. This attribute is only used if KeyStores is CUSTOM_IDENTITY_AND_CUSTOM_TRUST. When you get the value of this attribute, WebLogic Server does the following: <ol><li>Retrieves the value of the CustomTrustKeyStorePassPhraseEncrypted attribute.</li> <li>Decrypts the value and returns the unencrypted password as a String.</li> </ol> When you set the value of this attribute, WebLogic Server does the following: <ol><li>Encrypts the value.</li> <li>Sets the value of the CustomTrustKeyStorePassPhraseEncrypted attribute to the encrypted value.</li> </ol> Using this attribute (CustomTrustKeyStorePassPhrase) is a potential security risk because the String object (which contains the unencrypted password) remains in the JVM’s memory until garbage collection removes it and the memory is reallocated. Depending on how memory is allocated in the JVM, a significant amount of time could pass before this unencrypted data is removed from memory. Instead of using this attribute, use CustomTrustKeyStorePassPhraseEncrypted.

An example on how to use this:

wls_server {a_wls_server :
   ...
   custom_trust_key_store_pass_phrase => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:custom_trust_key_store_pass_phrase']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

custom_trust_key_store_type

The type of the keystore. Generally, this is JKS. If using the Oracle Key Store Service, this would be KSS If empty or null, then the JDK’s default keystore type (specified in java.security) is used. This keystore type is only used if KeyStores is CUSTOM_IDENTITY_AND_CUSTOM_TRUST.

An example on how to use this:

wls_server {a_wls_server :
   ...
   custom_trust_key_store_type => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:custom_trust_key_store_type']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

default_file_store

The path name to the file system directory where the file store maintains its data files.

Back to overview of wls_server

default_iiop_password

The password for the default IIOP user. (Requires you to enable IIOP.) As of 8.1 sp4, when you get the value of this attribute, WebLogic Server does the following: <ol><li>Retrieves the value of the DefaultIIOPPasswordEncrypted attribute.</li> <li>Decrypts the value and returns the unencrypted password as a String.</li> </ol> Using this attribute (DefaultIIOPPassword) is a potential security risk because the String object (which contains the unencrypted password) remains in the JVM’s memory until garbage collection removes it and the memory is reallocated. Depending on how memory is allocated in the JVM, a significant amount of time could pass before this unencrypted data is removed from memory. Instead of using this attribute, use DefaultIIOPPasswordEncrypted.

An example on how to use this:

wls_server {a_wls_server :
   ...
   default_iiop_password => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:default_iiop_password']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

default_iiop_user

The user name of the default IIOP user. (Requires you to enable IIOP.)

An example on how to use this:

wls_server {a_wls_server :
   ...
   default_iiop_user => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:default_iiop_user']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

default_internal_servlets_disabled

Specifies whether all default servlets in the servlet engine are disabled. This includes: weblogic.servlet.ClasspathServlet weblogic.servlet.utils.iiop.GetIORServlet weblogic.rjvm.http.TunnelSendServlet weblogic.rjvm.http.TunnelRecvServlet weblogic.rjvm.http.TunnelLoginServlet weblogic.rjvm.http.TunnelCloseServlet If set to true, this property overrides the ClasspathServletDisabled property.

An example on how to use this:

wls_server {a_wls_server :
   ...
   default_internal_servlets_disabled => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:default_internal_servlets_disabled']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

default_protocol

The protocol to use for connections when none is specified.

An example on how to use this:

wls_server {a_wls_server :
   ...
   default_protocol => 't3'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:default_protocol']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

default_secure_protocol

The protocol to use for secure connections when none is specified.

An example on how to use this:

wls_server {a_wls_server :
   ...
   default_secure_protocol => 't3s'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:default_secure_protocol']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

default_tgiop_password

The password for the default user associated with the Tuxedo GIOP (TGIOP) protocol. (Requires you to configure WebLogic Tuxedo Connector (WTC) for this server.) As of 8.1 sp4, when you get the value of this attribute, WebLogic Server does the following: <ol><li>Retrieves the value of the DefaultTGIOPPasswordEncrypted attribute.</li> <li>Decrypts the value and returns the unencrypted password as a String.</li> </ol> When you set the value of this attribute, WebLogic Server does the following: <ol><li>Encrypts the value.</li> <li>Sets the value of the DefaultTGIOPPasswordEncrypted attribute to the encrypted value.</li> </ol> Using this attribute (DefaultTGIOPPassword) is a potential security risk in because the String object (which contains the unencrypted password) remains the JVM’s memory until garbage collection removes it and the memory is reallocated. Depending on how memory is allocated in the JVM, a significant amount of time could pass before this unencrypted data is removed from memory. Instead of using this attribute, use DefaultTGIOPPasswordEncrypted.

An example on how to use this:

wls_server {a_wls_server :
   ...
   default_tgiop_password => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:default_tgiop_password']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

default_tgiop_user

The default user associated with the Tuxedo GIOP (TGIOP) protocol. (Requires you to configure WebLogic Tuxedo Connector (WTC) for this server.)

An example on how to use this:

wls_server {a_wls_server :
   ...
   default_tgiop_user => 'guest'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:default_tgiop_user']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

dgc_idle_periods_until_timeout

The number of idle periods allowed before object is collected.

An example on how to use this:

wls_server {a_wls_server :
   ...
   dgc_idle_periods_until_timeout => '5'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:dgc_idle_periods_until_timeout']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

disable_autorequire

Puppet supports automatic ordering of resources by autorequire. Sometimes, however, this causes issues. Setting this parameter to true, disables autorequiring for this specific resource.

USE WITH CAUTION!!

Here is an example on hopw to use this:

...{'domain_name/...':
  disableautorequire => true,
  ...
}

Back to overview of wls_server

disable_corrective_change

Disable the modification of a resource when Puppet decides it is a corrective change.

(requires easy_type V2.11.0 or higher)

When using a Puppet Server, Puppet knows about adaptive and corrective changes. A corrective change is when Puppet notices that the resource has changed, but the catalog has not changed. This can occur for example, when a user, by accident or willingly, changed something on the system that Puppet is managing. The normal Puppet process then repairs this and puts the resource back in the state as defined in the catalog. This process is precisely what you want most of the time, but not always. This can sometimes also occur when a hardware or network error occurs. Then Puppet cannot correctly determine the current state of the system and thinks the resource is changed, while in fact, it is not. Letting Puppet recreate remove or change the resource in these cases, is NOT wat you want.

Using the disable_corrective_change parameter, you can disable corrective changes on the current resource.

Here is an example of this:

crucial_resource {'be_carefull':
  ...
  disable_corrective_change => true,
  ...
}

When a corrective ensure does happen on the resource Puppet will not modify the resource and signal an error:

    Error: Corrective change present requested by catalog, but disabled by parameter disable_corrective_change
    Error: /Stage[main]/Main/Crucial_resource[be_carefull]/parameter: change from '10' to '20' failed: Corrective change present requested by catalog, but disabled by parameter disable_corrective_change. (corrective)

Back to overview of wls_server

disable_corrective_ensure

Disable the creation or removal of a resource when Puppet decides is a corrective change.

(requires easy_type V2.11.0 or higher)

When using a Puppet Server, Puppet knows about adaptive and corrective changes. A corrective change is when Puppet notices that the resource has changed, but the catalog has not changed. This can occur for example, when a user, by accident or willingly, changed something on the system that Puppet is managing. The normal Puppet process then repairs this and puts the resource back in the state as defined in the catalog. This process is precisely what you want most of the time, but not always. This can sometimes also occur when a hardware or network error occurs. Then Puppet cannot correctly determine the current state of the system and thinks the resource is changed, while in fact, it is not. Letting Puppet recreate remove or change the resource in these cases, is NOT wat you want.

Using the disable_corrective_ensure parameter, you can disable corrective ensure present or ensure absent actions on the current resource.

Here is an example of this:

crucial_resource {'be_carefull':
  ensure                    => 'present',
  ...
  disable_corrective_ensure => true,
  ...
}

When a corrective ensure does happen on the resource Puppet will not create or remove the resource and signal an error:

    Error: Corrective ensure present requested by catalog, but disabled by parameter disable_corrective_ensure.
    Error: /Stage[main]/Main/Crucial_resource[be_carefull]/ensure: change from 'absent' to 'present' failed: Corrective ensure present requested by catalog, but disabled by parameter disable_corrective_ensure. (corrective)

Back to overview of wls_server

domain

With this parameter, you identify the domain, where your objects is in.

The domain name is part of the full qualified name of any WebLogic object on a system. Let’s say we want to describe a WebLogic server. The full qualified name is:

wls_server{'domain_name/server_name':
  ensure => present,
  ...
}

When you don’t specify a domain name, Puppet will use default as domain name. For every domain you want to manage, you’ll have to put a wls_settings in your manifest.

Back to overview of wls_server

domain_name

Back to overview of wls_server

eager_thread_local_cleanup

Specifies whether to clean up all ThreadLocals storage from self-tuning thread pool threads after they have finished processing each work request. By default, the self-tuning thread pool only cleans up ThreadLocal storage in its threads after an application is undeployed to avoid ClassLoader memory leak.

An example on how to use this:

wls_server {a_wls_server :
   ...
   eager_thread_local_cleanup => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:eager_thread_local_cleanup']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

ensure

The basic property that the resource should be in.

Valid values are present, absent.

Back to overview of wls_server

external_dns_name

The external IP address or DNS name for this server. This address will be sent with HTTP session cookies and with dynamic server lists to HTTP proxies. It will also be used by external application clients to enable the propagation of RMI traffic through network address translating (NAT) firewalls. You must specify an external DNS name for configurations in which a firewall is performing network address translation, unless clients are accessing WebLogic Server using t3 and the default channel. For example, define the external DNS name for configurations in which a firewall is performing network address translation, and clients are accessing WebLogic Server using HTTP via a proxy plug-in.

An example on how to use this:

wls_server {a_wls_server :
   ...
   external_dns_name => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:external_dns_name']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

extra_ejbc_options

The options passed to the EJB compiler during server-side generation. Each EJB component can override the compiler options that you specify here. The following options are valid: <dl> <dt>-forcegeneration</dt> <dd>Forces generation of wrapper classes. Without this flag the classes may not be regenerated if it is determined to be unnecessary.</dd> <dt>-disableHotCodeGen</dt> <dd>Generate ejb stub and skel as part of ejbc. Avoid HotCodeGen to have better performance. </dd> <dt>-keepgenerated</dt> <dd>Keep the generated .java files.</dd> <dt>-compiler javac</dt> <dd>Java compiler to exec. If not specified, the -compilerclass option will be used.</dd> <dt>-compilerclass com.sun.tools.javac.Main</dt> <dd>Specifies the compiler class to invoke.</dd> <dt>-g</dt> <dd>Compile debugging info into class file.</dd> <dt>-normi</dt> <dd>Passed through to Symantec’s sj.</dd> <dt>-classpath path</dt> <dd>Classpath to use.</dd> <dt>-source source</dt> <dd>Source version.</dd> <dt>-Joption</dt> <dd>Flags passed through to java runtime.</dd> </dl>

An example on how to use this:

wls_server {a_wls_server :
   ...
   extra_ejbc_options => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:extra_ejbc_options']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

extra_rmic_options

The options passed to the RMIC compiler during server-side generation. Each EJB component can override the compiler options that you specify here.

An example on how to use this:

wls_server {a_wls_server :
   ...
   extra_rmic_options => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:extra_rmic_options']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

frontendhost

The frontendhost of this cluster. You can use an ip address like this: wls_cluster { ‘aCluster’: … frontendhost => ‘10.10.10.30’, … } or use a host name like this: wls_cluster { ‘aCluster’: … frontendhost => ‘myhost.exaqmple.com’, … } For more information checkout the documentation of propery ClusterMBean.FrontendHost in the WebLogic documentation.

Back to overview of wls_server

frontendhttpport

The frontendhttpport of this cluster. Here is an example on how to use this: wls_cluster { ‘aCluster’: … frontendhttpport => ‘9000’, … } For more information checkout the documentation of propery ClusterMBean.FrontendHTTPPort in the WebLogic documentation.

Back to overview of wls_server

frontendhttpsport

The frontendhttpsport of this cluster. Here is an example on how to use this: wls_cluster { ‘aCluster’: … frontendhttspport => ‘9000’, … } For more information checkout the documentation of propery ClusterMBean.FrontendHTTPSPort in the WebLogic documentation.

Back to overview of wls_server

gathered_writes_enabled

Enables gathered writes over NIO socket channels. Enabling this attribute increases efficiency during I/O in environments with high network throughput and should be used only when configuring a WebLogic domain for Oracle Exalogic.

An example on how to use this:

wls_server {a_wls_server :
   ...
   gathered_writes_enabled => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:gathered_writes_enabled']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

graceful_shutdown_timeout

Number of seconds a graceful shutdown operation waits before forcing a shut down. A graceful shutdown gives WebLogic Server subsystems time to complete certain application processing currently in progress. If subsystems are unable to complete processing within the number of seconds that you specify here, then the server will force shutdown automatically. A value of 0 means that the server will wait indefinitely for graceful shutdown to complete. The graceful shutdown timeout applies only to graceful shutdown operations.

An example on how to use this:

wls_server {a_wls_server :
   ...
   graceful_shutdown_timeout => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:graceful_shutdown_timeout']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

health_check_interval_seconds

The number of seconds that defines the frequency of this server’s self-health monitoring. The server monitors the health of it’s subsystems every HealthCheckIntervalSeconds and changes the Server’s overall state if required.

An example on how to use this:

wls_server {a_wls_server :
   ...
   health_check_interval_seconds => '180'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:health_check_interval_seconds']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

health_check_start_delay_seconds

The number of seconds the Node Manager should wait before starting to monitor the server.

An example on how to use this:

wls_server {a_wls_server :
   ...
   health_check_start_delay_seconds => '120'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:health_check_start_delay_seconds']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

health_check_timeout_seconds

The number of seconds the Node Manager should wait before timing out its health query to this server. If the timeout is reached, Node Managed assumes the Managed Server has failed.

An example on how to use this:

wls_server {a_wls_server :
   ...
   health_check_timeout_seconds => '60'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:health_check_timeout_seconds']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

hosts_migratable_services

Gets the hostsMigratableServices attribute of the ServerMBean object

An example on how to use this:

wls_server {a_wls_server :
   ...
   hosts_migratable_services => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:hosts_migratable_services']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

http_trace_support_enabled

Returns the HttpTraceSupportEnabled value

An example on how to use this:

wls_server {a_wls_server :
   ...
   http_trace_support_enabled => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:http_trace_support_enabled']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

httpd_enabled

Whether or not HTTP support is enabled on the regular port or SSL port.

An example on how to use this:

wls_server {a_wls_server :
   ...
   httpd_enabled => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:httpd_enabled']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

idle_connection_timeout

The maximum number of seconds that a connection is allowed to be idle before it is closed by the server. The T3 and T3S protocols ignore this attribute. If you configure network channels for this server, each channel can override this idle connection message timeout. This timeout helps guard against server deadlock through too many open connections.

An example on how to use this:

wls_server {a_wls_server :
   ...
   idle_connection_timeout => '65'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:idle_connection_timeout']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

idle_iiop_connection_timeout

The maximum number of seconds an IIOP connection is allowed to be idle before it is closed by the server. This timeout helps guard against server deadlock through too many open connections.

An example on how to use this:

wls_server {a_wls_server :
   ...
   idle_iiop_connection_timeout => '-1'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:idle_iiop_connection_timeout']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

idle_periods_until_timeout

The number of idle periods until peer is considered unreachable

An example on how to use this:

wls_server {a_wls_server :
   ...
   idle_periods_until_timeout => '4'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:idle_periods_until_timeout']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

ignore_sessions_during_shutdown

Indicates whether a graceful shutdown operation drops all HTTP sessions immediately. If this is set to false, a graceful shutdown operation waits for HTTP sessions to complete or timeout.

An example on how to use this:

wls_server {a_wls_server :
   ...
   ignore_sessions_during_shutdown => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:ignore_sessions_during_shutdown']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

iiop_enabled

Specifies whether this server has IIOP support enabled for both the regular (non-SSL) and SSL ports.

An example on how to use this:

wls_server {a_wls_server :
   ...
   iiop_enabled => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:iiop_enabled']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

iiop_tx_mechanism

Configures IIOP propagate transactions using either WebLogic-specific JTA or the OMG-specified OTS. It is not possible to use both because it affects the way transactions are negotiated.

An example on how to use this:

wls_server {a_wls_server :
   ...
   iiop_tx_mechanism => 'ots'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:iiop_tx_mechanism']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

instrument_stack_trace_enabled

Specifies whether the server returns stack traces for RMI calls that generate exceptions. With RMI stack tracking enabled, if a client issues an RMI call to a server subsystem or to a module running within the server, and if the subsystem or module generates an exception that includes a stack trace, the server will return the exception as well as the stack trace. With it disabled, the server will return the exception without the stack trace details.

An example on how to use this:

wls_server {a_wls_server :
   ...
   instrument_stack_trace_enabled => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:instrument_stack_trace_enabled']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

interface_address

The IP address of the NIC that this server should use for multicast traffic.

An example on how to use this:

wls_server {a_wls_server :
   ...
   interface_address => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:interface_address']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

java_compiler

The Java compiler to use for all applications hosted on this server that need to compile Java code.

An example on how to use this:

wls_server {a_wls_server :
   ...
   java_compiler => 'javac'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:java_compiler']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

java_compiler_post_class_path

The options to append to the Java compiler classpath when compiling Java code.

An example on how to use this:

wls_server {a_wls_server :
   ...
   java_compiler_post_class_path => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:java_compiler_post_class_path']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

java_compiler_pre_class_path

The options to prepend to the Java compiler classpath when compiling Java code.

An example on how to use this:

wls_server {a_wls_server :
   ...
   java_compiler_pre_class_path => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:java_compiler_pre_class_path']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

java_standard_trust_key_store_pass_phrase

The password for the Java Standard Trust keystore. This password is defined when the keystore is created. If empty or null, then the keystore will be opened without a passphrase. This attribute is only used if KeyStores is CUSTOM_IDENTITY_AND_JAVA_STANDARD_TRUST or DEMO_IDENTITY_AND_DEMO_TRUST. When you get the value of this attribute, WebLogic Server does the following: <ol><li>Retrieves the value of the JavaStandardTrustKeyStorePassPhraseEncrypted attribute.</li> <li>Decrypts the value and returns the unencrypted password as a String.</li> </ol> When you set the value of this attribute, WebLogic Server does the following: <ol><li>Encrypts the value.</li> <li>Sets the value of the JavaStandardTrustKeyStorePassPhraseEncrypted attribute to the encrypted value.</li> </ol> Using this attribute (JavaStandardTrustKeyStorePassPhrase) is a potential security risk because the String object (which contains the unencrypted password) remains in the JVM’s memory until garbage collection removes it and the memory is reallocated. Depending on how memory is allocated in the JVM, a significant amount of time could pass before this unencrypted data is removed from memory. Instead of using this attribute, use JavaStandardTrustKeyStorePassPhraseEncrypted.

An example on how to use this:

wls_server {a_wls_server :
   ...
   java_standard_trust_key_store_pass_phrase => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:java_standard_trust_key_store_pass_phrase']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

jdbc_logging_enabled

Specifies whether this server maintains a JDBC log file.

An example on how to use this:

wls_server {a_wls_server :
   ...
   jdbc_logging_enabled => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:jdbc_logging_enabled']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

jdbc_login_timeout_seconds

The JDBC Login Timeout value. Specified value is passed into java.sql.DriverManager.setLoginTimeout(). Note that this DriverManager setting will impact all JDBC drivers loaded into this JVM. Feature is disabled by default.

An example on how to use this:

wls_server {a_wls_server :
   ...
   jdbc_login_timeout_seconds => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:jdbc_login_timeout_seconds']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

jdbcllr_table_name

The table name for this server’s Logging Last Resource (LLR) database table(s). WebLogic Server creates the table(s) and then uses them during transaction processing for the LLR transaction optimization. This setting must be unique for each server. The default table name is WL_LLR_SERVERNAME. This setting only applies if this server hosts one or more LLR-enabled JDBC data sources. The format for the tables that WebLogic Server creates is [[[catalog.]schema.]name.] Each “.” in the table name is significant, and schema generally corresponds to username in many databases. IMPORTANT: If this value is changed but the LLR table already exists in the database, you must preserve the existing table’s data. Consequently, when changing the table name, the existing database table must be renamed by a database administrator to match the new configured table name. Otherwise, transaction records may be lost, resulting in heuristic failures that aren’t logged. IMPORTANT: Each server’s table name must be unique. Multiple LLR-enabled data sources within the same server may share the same table, but multiple servers must not share the same table. If multiple same-named servers share a table, the behavior is undefined and it is likely that transactions will not recover properly after a crash, creating heuristic hazards.

An example on how to use this:

wls_server {a_wls_server :
   ...
   jdbcllr_table_name => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:jdbcllr_table_name']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

jms_connection_factory_unmapped_res_ref_mode

Use this unmapped resource reference mode to specify the behavior of any resource reference to a Connection Factory when the resource reference does not directly specify a JNDI name by a lookup attribute, or by a mappedName attribute, or by a jndi-name in a descriptor file. If a JNDI name is specified, the resource reference either resolves to the specified object in the JNDI tree or generates a javax.naming.NameNotFoundException. Following are the available unmapped resource reference modes: <ul> <li> FailSafe : In this mode, an application JMS connection factory resource reference that does not specify a JNDI name resolves to an object bound to the JNDI tree with the same name as the resource reference name if one can be found in JNDI tree. Otherwise, it throws a javax.naming.NameNotFoundException. A resource reference without a JNDI name never returns a Java EE 7 Default Connection Factory in this mode. This mode yields pre-12.2.1 WebLogic Server behavior. This mode is Java EE compliant, but the Java EE 7 specification disallows it from being the default mode. </li> </ul> <ul> <li> ReturnDefault : This policy is a Java EE compliant mode and it is the default mode. It complies with Java EE 7 while doing a best effort to try delivering FailSafe behavior when it is expected. (a) If the resource reference name matches the local JNDI name of a configured foreign JMS provider mapping, then WebLogic Server returns the remote JNDI entry from the mapping if it can be resolved, or it throws a javax.naming.NameNotFoundException. (b) If the resource reference does not match with a foreign JMS provider mapping, and if the resource reference name matches the name of an object that is already bound to the JNDI tree, WebLogic Server returns the JNDI tree object. (c) If neither (a) nor (b) apply, then WebLogic Server returns “java:comp/DefaultJMSConnectionFactory”. In addition, it adds an ‘Info’ message in the server log indicating that a special behavior has occurred. This log message will occur at most once per application per server boot. </li> </ul>

An example on how to use this:

wls_server {a_wls_server :
   ...
   jms_connection_factory_unmapped_res_ref_mode => 'ReturnDefault'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:jms_connection_factory_unmapped_res_ref_mode']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

jms_default_connection_factories_enabled

Specifies whether this server uses JMS default connection factories. WebLogic Server provides the following JMS default connection factories: <ul> <li> weblogic.jms.ConnectionFactory </li> <li> weblogic.jms.XAConnectionFactory An XA factory is required for JMS applications to use JTA user-transactions, but is not required for transacted sessions. All other preconfigured attributes for the default connection factories are set to the same default values as a user-defined connection factory. If the preconfigured settings of the default factories are appropriate for your application, you do not need to configure any additional factories for your application. </li> </ul> Note: When using the default connection factories, you have no control over targeting the WebLogic Server instances where the connection factory may be deployed. However, you can disable the default connection factories on a per-server basis. To deploy a connection factory on independent servers, on specific servers within a cluster, or on an entire cluster, you need to configure a connection factory and specify the appropriate server targets.

An example on how to use this:

wls_server {a_wls_server :
   ...
   jms_default_connection_factories_enabled => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:jms_default_connection_factories_enabled']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

jndi_transportable_object_factory_list

List of factories that create transportable objects.

An example on how to use this:

wls_server {a_wls_server :
   ...
   jndi_transportable_object_factory_list => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:jndi_transportable_object_factory_list']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

jsseenabled

Determines whether the SSL implementation in Weblogic Server is JSSE based.

An example on how to use this:

...{...:
   ...
   jsseenabled => 1,
   ...
}

Help text generated from MBEan text.

Valid values are absent, 1, 0.

Back to overview of wls_server

key_stores

Which configuration rules should be used for finding the server’s identity and trust keystores?

An example on how to use this:

wls_server {a_wls_server :
   ...
   key_stores => 'DemoIdentityAndDemoTrust'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:key_stores']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

listen_address

The IP address or DNS name this server uses to listen for incoming connections. Servers can be reached through the following URL:
protocol://listen-address:listen-port Any network channel that you configure for this server can override this listen address. If a server’s listen address is undefined, clients can reach the server through an IP address of the computer that hosts the server, a DNS name that resolves to the host, or the localhost string. The localhost string can be used only for requests from clients that are running on the same computer as the server. If you want to limit the valid addresses for a server instance, specify one of the following: <ul> <li> IP address. If you provide an IP address, clients can specify either the IP address or a DNS name that maps to the IP address. Clients that specify an IP address and attempt to connect through an SSL port must disable hostname verification. </li> <li> DNS name. If you provide a DNS name, clients can specify either the DNS name or the corresponding IP address. </li> </ul> Do not leave the listen address undefined on a computer that uses multiple IP address (a multihomed computer). On such a computer, the server will bind to all available IP addresses. <dl> <dt>Notes:</dt> <dd> To resolve a DNS name to an IP address, WebLogic Server must be able to contact an appropriate DNS server or obtain the IP address mapping locally. Therefore, if you specify a DNS name for the listen address, you must either leave a port open long enough for the WebLogic Server instance to connect to a DNS server and cache its mapping or you must specify the IP address mapping in a local file. If you specify an IP address for ListenAddress and then a client request specifies a DNS name, WebLogic Server will attempt to resolve the DNS name, but if it cannot access DNS name mapping, the request fails. Note also that if you are using the demo certificates in a multi-server domain, Managed Server instances will fail to boot if you specify the fully-qualified DNS name. For information about this limitation and suggested workarounds, see “Limitation on CertGen Usage” in Administering Security for Oracle WebLogic Server. </dd> </dl>

An example on how to use this:

wls_server {a_wls_server :
   ...
   listen_address => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:listen_address']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

listen_delay_secs

Perpetuated for compatibility with 6.1 only.

An example on how to use this:

wls_server {a_wls_server :
   ...
   listen_delay_secs => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:listen_delay_secs']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

listen_port

The default TCP port that this server uses to listen for regular (non-SSL) incoming connections. Administrators must have the right privileges before binding to a port or else this operation will not be successful and it will render the console un-reachable. If this port is disabled, the SSL port must be enabled. Additional ports can be configured using network channels. The cluster (multicast) port is configured separately.

An example on how to use this:

wls_server {a_wls_server :
   ...
   listen_port => '7001'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:listen_port']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

listen_port_enabled

Specifies whether this server can be reached through the default plain-text (non-SSL) listen port. If you disable this listen port, you must enable the default SSL listen port. You can define additional listen ports for this server by configuring network channels.

An example on how to use this:

wls_server {a_wls_server :
   ...
   listen_port_enabled => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:listen_port_enabled']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

listen_thread_start_delay_secs

Returns the maximum time that the server will wait for server sockets to bind before starting a listen thread. Properties to consider for removal

An example on how to use this:

wls_server {a_wls_server :
   ...
   listen_thread_start_delay_secs => '60'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:listen_thread_start_delay_secs']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

listenaddress

The IP address or DNS name this server uses to listen for incoming connections. Servers can be reached through the following URL:
protocol://listen-address:listen-port Any network channel that you configure for this server can override this listen address. If a server’s listen address is undefined, clients can reach the server through an IP address of the computer that hosts the server, a DNS name that resolves to the host, or the localhost string. The localhost string can be used only for requests from clients that are running on the same computer as the server. If you want to limit the valid addresses for a server instance, specify one of the following: <ul> <li> IP address. If you provide an IP address, clients can specify either the IP address or a DNS name that maps to the IP address. Clients that specify an IP address and attempt to connect through an SSL port must disable hostname verification. </li> <li> DNS name. If you provide a DNS name, clients can specify either the DNS name or the corresponding IP address. </li> </ul> Do not leave the listen address undefined on a computer that uses multiple IP address (a multihomed computer). On such a computer, the server will bind to all available IP addresses. <dl> <dt>Notes:</dt> <dd> To resolve a DNS name to an IP address, WebLogic Server must be able to contact an appropriate DNS server or obtain the IP address mapping locally. Therefore, if you specify a DNS name for the listen address, you must either leave a port open long enough for the WebLogic Server instance to connect to a DNS server and cache its mapping or you must specify the IP address mapping in a local file. If you specify an IP address for ListenAddress and then a client request specifies a DNS name, WebLogic Server will attempt to resolve the DNS name, but if it cannot access DNS name mapping, the request fails. Note also that if you are using the demo certificates in a multi-server domain, Managed Server instances will fail to boot if you specify the fully-qualified DNS name. For information about this limitation and suggested workarounds, see “Limitation on CertGen Usage” in Administering Security for Oracle WebLogic Server. </dd> </dl>

An example on how to use this:

...{...:
   ...
   listenaddress => None
   ...
}

Help text generated from MBEan text.

Back to overview of wls_server

listeners_bind_early

Determines whether the server should bind server sockets early. Early binding detects port conflicts quickly and also gives user feedback on the default listen port as to the server state.

An example on how to use this:

wls_server {a_wls_server :
   ...
   listeners_bind_early => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:listeners_bind_early']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

listenport

The listenport of the server

Back to overview of wls_server

listenportenabled

Specifies whether this server can be reached through the default plain-text (non-SSL) listen port. If you disable this listen port, you must enable the default SSL listen port. You can define additional listen ports for this server by configuring network channels.

An example on how to use this:

...{...:
   ...
   listenportenabled => 1,
   ...
}

Help text generated from MBEan text.

Valid values are absent, 1, 0.

Back to overview of wls_server

log_buffer_size_kb

Gets the underlying log buffer size in kilobytes

An example on how to use this:

wls_server {a_wls_server :
   ...
   log_buffer_size_kb => '8'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:log_buffer_size_kb']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

log_datasource_filename

The datasource log file name of the server.

Back to overview of wls_server

log_date_format_pattern

The date format pattern used for rendering dates in the log. The DateFormatPattern string conforms to the specification of the java.text.SimpleDateFormat class.

An example on how to use this:

wls_server {a_wls_server :
   ...
   log_date_format_pattern => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:log_date_format_pattern']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

log_date_pattern

The date format pattern used for rendering dates in the log. The DateFormatPattern string conforms to the specification of the java.text.SimpleDateFormat class.

Back to overview of wls_server

log_domain_log_broadcast_filter

The filter configuration for log events being sent to the domain log.

An example on how to use this:

wls_server {a_wls_server :
   ...
   log_domain_log_broadcast_filter => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:log_domain_log_broadcast_filter']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

log_domain_log_broadcast_severity

The minimum severity of log messages going to the domain log from this server’s log broadcaster. Messages with a lower severity than the specified value will not be published to the domain log.

An example on how to use this:

wls_server {a_wls_server :
   ...
   log_domain_log_broadcast_severity => 'Notice'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:log_domain_log_broadcast_severity']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

log_domain_log_broadcaster_buffer_size

Broadcasts log messages to the domain log in batch mode. The size of the buffer for log messages that are sent to the domain log. The buffer is maintained on the Managed Server and is broadcasted to the domain log when it is full. If you notice performance issues due to a high rate of log messages being generated, set this value higher. This will cause the buffer to be broadcasted less frequently from the Managed Server to the domain log. In production environments, it is not recommended to set the buffer size lower than the production default of 10.

An example on how to use this:

wls_server {a_wls_server :
   ...
   log_domain_log_broadcaster_buffer_size => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:log_domain_log_broadcaster_buffer_size']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

log_file_count

The maximum number of log files that the server creates when it rotates the log. This number does not include the file that the server uses to store current messages. (Requires that you enable Number of Files Limited.)

An example on how to use this:

wls_server {a_wls_server :
   ...
   log_file_count => '7'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:log_file_count']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

log_file_filter

The filter configuration for the server log file. A filter configuration defines simple filtering rules to limit the volume of log messages written to the log file.

An example on how to use this:

wls_server {a_wls_server :
   ...
   log_file_filter => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:log_file_filter']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

log_file_min_size

The log file min size of a domain or server.

Back to overview of wls_server

log_file_name

The name of the file that stores current log messages. Usually it is a computed value based on the name of the parent of this MBean. For example, for a server log, it is SERVER_NAME.log. However, if the name of the parent cannot be obtained, the file name is weblogic.log. If you specify a relative pathname, it is interpreted as relative to the server’s root directory. To include a time and date stamp in the file name when the log file is rotated, add java.text.SimpleDateFormat variables to the file name. Surround each variable with percentage (%) characters. For example, if the file name is defined to be myserver_%yyyy%_%MM%_%dd%_%hh%_%mm%.log, the log file will be named myserver_yyyy_mm_dd_hh_mm.log. When the log file is rotated, the rotated file name contains the date stamp. For example, if the log file is rotated for the first time on 2 April, 2003 at 10:05 AM, the log file that contains the old messages will be named myserver_2003_04_02_10_05.log00001. If you do not include a time and date stamp, the rotated log files are numbered in order of creation. For example, myserver.log00007.

An example on how to use this:

wls_server {a_wls_server :
   ...
   log_file_name => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:log_file_name']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

log_file_rotation_dir

The directory where the rotated log files will be stored. By default the rotated files are stored in the same directory where the log file is stored.

An example on how to use this:

wls_server {a_wls_server :
   ...
   log_file_rotation_dir => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:log_file_rotation_dir']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

log_file_severity

The minimum severity of log messages going to the server log file. By default all messages go to the log file.

An example on how to use this:

wls_server {a_wls_server :
   ...
   log_file_severity => 'Trace'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:log_file_severity']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

log_file_time_span

The interval (in hours) at which the server saves old log messages to another file. (Requires that you specify a file rotation type of TIME.)

An example on how to use this:

wls_server {a_wls_server :
   ...
   log_file_time_span => '24'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:log_file_time_span']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

log_filecount

The maximum number of log files that the server creates when it rotates the log. This number does not include the file that the server uses to store current messages. (Requires that you enable Number of Files Limited.)

An example on how to use this:

...{...:
   ...
   log_filecount => 7
   ...
}

Help text generated from MBEan text.

Back to overview of wls_server

log_http_file_count

The log http file name of the server.

Back to overview of wls_server

log_http_filename

The log http file name of the server.

Back to overview of wls_server

log_http_format

The log http format of the file name of the server.

Back to overview of wls_server

log_http_format_type

The log format type of the http file name of the server.

Valid values are absent, common, extended.

Back to overview of wls_server

log_http_number_of_files_limited

The number of http log files to keep.

Valid values are absent, 1, 0.

Back to overview of wls_server

log_log4j_logging_enabled

Specifies whether the server logging is based on a Log4j implementation. By default, WebLogic logging uses an implementation based on the Java Logging APIs which are part of the JDK. Applications that use the WebLogic Message Catalog framework or the NonCatalogLogger will not be affected by the underlying Logging implementation.

An example on how to use this:

wls_server {a_wls_server :
   ...
   log_log4j_logging_enabled => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:log_log4j_logging_enabled']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

log_logger_severity

The minimum severity of log messages going to all log destinations. By default all messages are published.

An example on how to use this:

wls_server {a_wls_server :
   ...
   log_logger_severity => 'Info'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:log_logger_severity']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

log_logger_severity_properties

The configuration of the different logger severities keyed by name. The values are one of the predefined Severity strings namely Emergency, Alert, Critical, Error, Warning, Notice, Info, Debug, Trace.

An example on how to use this:

wls_server {a_wls_server :
   ...
   log_logger_severity_properties => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:log_logger_severity_properties']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

log_memory_buffer_filter

The filter configuration for messages that are stored in the log memory buffer. By default, all log messages are cached.

An example on how to use this:

wls_server {a_wls_server :
   ...
   log_memory_buffer_filter => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:log_memory_buffer_filter']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

log_memory_buffer_severity

The minimum severity of log messages going to the memory buffer of recent log events. Messages with a lower severity than the specified value will not be cached in the buffer.

An example on how to use this:

wls_server {a_wls_server :
   ...
   log_memory_buffer_severity => 'Trace'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:log_memory_buffer_severity']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

log_memory_buffer_size

The size of the memory buffer that holds the last n log records. This is used to support viewing the most recent log record entries (tail viewing) from the WebLogic Administration Console.

An example on how to use this:

wls_server {a_wls_server :
   ...
   log_memory_buffer_size => '10'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:log_memory_buffer_size']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

log_monitoring_enabled

Enable or disable log monitoring.

An example on how to use this:

wls_server {a_wls_server :
   ...
   log_monitoring_enabled => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:log_monitoring_enabled']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

log_monitoring_interval_secs

Timer interval in seconds to check the counts of messages logged during the interval.

An example on how to use this:

wls_server {a_wls_server :
   ...
   log_monitoring_interval_secs => '30'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:log_monitoring_interval_secs']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

log_monitoring_throttle_message_length

Cut-off length of the log message for evaluation during throttle period. The log message length is truncated to this length for evaluation of repeated logging events.

An example on how to use this:

wls_server {a_wls_server :
   ...
   log_monitoring_throttle_message_length => '50'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:log_monitoring_throttle_message_length']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

log_monitoring_throttle_threshold

The threshold number of messages logged during the evaluation period which enables or disables the throttling.

An example on how to use this:

wls_server {a_wls_server :
   ...
   log_monitoring_throttle_threshold => '1500'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:log_monitoring_throttle_threshold']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

log_notes

Optional information that you can include to describe this configuration. WebLogic Server saves this note in the domain’s configuration file (config.xml) as XML PCDATA. All left angle brackets (<) are converted to the XML entity <. Carriage returns/line feeds are preserved. <dl> <dt>Note:</dt> <dd> If you create or edit a note from the Administration Console, the Administration Console does not preserve carriage returns/line feeds. </dd> </dl>

An example on how to use this:

wls_server {a_wls_server :
   ...
   log_notes => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:log_notes']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

log_number_of_files_limited

Limited log number of files of a domain or server.

Valid values are absent, 1, 0.

Back to overview of wls_server

log_platform_logger_levels

Specifies the platform logger and the associated level names set through the WebLogic Server configuration. Note the following behavior: <ul> <li>The configuration is applicable for java.util.logging.Logger instances in the JDK’s default global LogManager.</li> <li>WebLogic Server loggers are configured in terms of weblogic.logging.Severities through the LoggerSeverities attribute. These loggers are not available in the JDK’s default global LogManager.</li> </ul>

An example on how to use this:

wls_server {a_wls_server :
   ...
   log_platform_logger_levels => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:log_platform_logger_levels']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

log_redirect_stderr_to_server

When enabled, this redirects the stderr of the JVM in which a WebLogic Server instance runs, to the WebLogic logging system.

Valid values are absent, 1, 0.

Back to overview of wls_server

log_redirect_stderr_to_server_log_enabled

Specifies whether the stderr of the JVM in which a WebLogic Server instance runs is redirected to the WebLogic Logging system. When this attribute is enabled, the stderr content is published to all the registered log destinations, such as the server terminal console and log file. Note that JVM messages are redirected asynchronously. In the event of an overload situation, these messages may be dropped. As a best practice, Oracle recommends using one of the supported logging APIs instead.

An example on how to use this:

wls_server {a_wls_server :
   ...
   log_redirect_stderr_to_server_log_enabled => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:log_redirect_stderr_to_server_log_enabled']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

log_redirect_stdout_to_server

When enabled, this redirects the stdout of the JVM in which a WebLogic Server instance runs, to the WebLogic logging system.

Valid values are absent, 1, 0.

Back to overview of wls_server

log_redirect_stdout_to_server_log_enabled

Specifies whether the stdout of the JVM in which a WebLogic Server instance runs is redirected to the WebLogic logging system. When this attribute is enabled, the stdout content is published to all the registered log destinations, such as the server terminal console and log file. Note that JVM messages are redirected asynchronously. In the event of an overload situation, these messages may be dropped. As a best practice, Oracle recommends using one of the supported logging APIs instead.

An example on how to use this:

wls_server {a_wls_server :
   ...
   log_redirect_stdout_to_server_log_enabled => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:log_redirect_stdout_to_server_log_enabled']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

log_remote_exceptions_enabled

Specifies whether the server message log includes exceptions that are raised in remote systems.

An example on how to use this:

wls_server {a_wls_server :
   ...
   log_remote_exceptions_enabled => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:log_remote_exceptions_enabled']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

log_rotate_log_on_startup

Specifies whether a server rotates its log file during its startup cycle. The default value in production mode is false.

An example on how to use this:

wls_server {a_wls_server :
   ...
   log_rotate_log_on_startup => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:log_rotate_log_on_startup']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

log_rotate_logon_startup

log rotate Logon at startup of a domain or server.

Valid values are absent, 1, 0.

Back to overview of wls_server

log_rotation_time

Determines the start time (hour and minute) for a time-based rotation sequence. At the time that this value specifies, the server renames the current log file. Thereafter, the server renames the log file at an interval that you specify in File Time Span. Note that WebLogic Server sets a threshold size limit of 500 MB before it forces a hard rotation to prevent excessive log file growth. Use the following format: H:mm, where <ul><li>H is Hour in day (0-23). <li>mm is the minute in hour </ul>

An example on how to use this:

wls_server {a_wls_server :
   ...
   log_rotation_time => '00:00'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:log_rotation_time']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

log_rotation_type

Criteria for moving old log messages to a separate file. <ul> <li>NONE Messages accumulate in a single file. You must erase the contents of the file when the size is too large. Note that WebLogic Server sets a threshold size limit of 500 MB before it forces a hard rotation to prevent excessive log file growth. <li>SIZE When the log file reaches the size that you specify in FileMinSize, the server renames the file as SERVER_NAME.lognnnnn. <li>TIME At each time interval that you specify in TimeSpan, the server renames the file as SERVER_NAME.lognnnnn. </ul> After the server renames a file, subsequent messages accumulate in a new file with the name that you specified as the log file name.

An example on how to use this:

wls_server {a_wls_server :
   ...
   log_rotation_type => 'bySize'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:log_rotation_type']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

log_rotationtype

Criteria for moving old log messages to a separate file.

• NONE Messages accumulate in a single file. You must erase the contents of the file when the size is too large. Note that WebLogic Server sets a threshold size limit of 500 MB before it forces a hard rotation to prevent excessive log file growth.
• SIZE When the log file reaches the size that you specify in FileMinSize, the server renames the file as SERVER_NAME.lognnnnn.
• TIME At each time interval that you specify in TimeSpan, the server renames the file as SERVER_NAME.lognnnnn.

After the server renames a file, subsequent messages accumulate in a new file with the name that you specified as the log file name.

An example on how to use this:

...{...:
   ...
   log_rotationtype => bySize
   ...
}

Help text generated from MBEan text.

Valid values are absent, bySize, byTime, none.

Back to overview of wls_server

log_server_logging_bridge_use_parent_loggers_enabled

Specifies whether application log messages are propagated to the parent node in the Logger tree or to the WebLogic Server log by means of the Logging Bridge. By default, this attribute is disabled, which results in application log messages being propagated to the WebLogic Server log. Note the following behavior: <ul> <li>If WebLogic Server is configured to be based upon the the Java Logging API (the default), the Logging Bridge is made available as a java.util.logging.Handler object.</li> <li>If WebLogic Server is configured to be based upon a Log4j implementation, the Logging Bridge is made available as a org.apache.log4j.Appender object.</li> <li>If the ServerLoggingBridgeUseParentLoggersEnabled is disabled, applications that use either the Java Logging API or Log4j have their log messages redirected by the Logging Bridge to the WebLogic Server log. <li>If the ServerLoggingBridgeUseParentLoggersEnabled is enabled, applications that use the Java Logging API have their log messages propagated to the parent node in the global Java Logging Logger tree.</li> <li>If the ServerLoggingBridgeUseParentLoggersEnabled is enabled, applications that use Log4j have their log messages propagated to the parent node in the Log4j Logger tree.</li> </ul>

An example on how to use this:

wls_server {a_wls_server :
   ...
   log_server_logging_bridge_use_parent_loggers_enabled => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:log_server_logging_bridge_use_parent_loggers_enabled']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

log_stdout_filter

The filter configuration for log events being sent to the standard out.

An example on how to use this:

wls_server {a_wls_server :
   ...
   log_stdout_filter => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:log_stdout_filter']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

log_stdout_format

The output format to use when logging to the console.

An example on how to use this:

wls_server {a_wls_server :
   ...
   log_stdout_format => 'standard'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:log_stdout_format']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

log_stdout_log_stack

Specifies whether to dump stack traces to the console when included in logged message.

An example on how to use this:

wls_server {a_wls_server :
   ...
   log_stdout_log_stack => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:log_stdout_log_stack']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

log_stdout_severity

The minimum severity of log messages going to the standard out. Messages with a lower severity than the specified value will not be published to standard out.

An example on how to use this:

wls_server {a_wls_server :
   ...
   log_stdout_severity => 'Notice'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:log_stdout_severity']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

log_tags

Return all tags on this Configuration MBean

An example on how to use this:

wls_server {a_wls_server :
   ...
   log_tags => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:log_tags']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

logfilename

The log file name.

Back to overview of wls_server

login_timeout_millis

The login timeout for this server’s default regular (non-SSL) listen port. This is the maximum amount of time allowed for a new connection to establish. A value of 0 indicates there is no maximum.

An example on how to use this:

wls_server {a_wls_server :
   ...
   login_timeout_millis => '5000'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:login_timeout_millis']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

logintimeout

The HTTP Login Timeout of the server in milliseconds.

Back to overview of wls_server

low_memory_gc_threshold

The threshold level (in percent) that this server uses for logging low memory conditions and changing the server health state to Warning. For example, if you specify 5, the server logs a low memory warning in the log file and changes the server health state to Warning after the average free memory reaches 5% of the initial free memory measured at the server’s boot time.

An example on how to use this:

wls_server {a_wls_server :
   ...
   low_memory_gc_threshold => '5'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:low_memory_gc_threshold']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

low_memory_granularity_level

The granularity level (in percent) that this server uses for logging low memory conditions and changing the server health state to Warning. For example, if you specify 5 and the average free memory drops by 5% or more over two measured intervals, the server logs a low memory warning in the log file and changes the server health state to Warning.

An example on how to use this:

wls_server {a_wls_server :
   ...
   low_memory_granularity_level => '5'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:low_memory_granularity_level']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

low_memory_sample_size

The number of times this server samples free memory during the time period specified by LowMemoryTimeInterval. Increasing the sample size can improve the accuracy of the reading.

An example on how to use this:

wls_server {a_wls_server :
   ...
   low_memory_sample_size => '10'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:low_memory_sample_size']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

low_memory_time_interval

The amount of time (in seconds) that defines the interval over which this server determines average free memory values. By default, the server obtains an average free memory value every 3600 seconds.

An example on how to use this:

wls_server {a_wls_server :
   ...
   low_memory_time_interval => '3600'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:low_memory_time_interval']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

machine

The machine of the server.

Back to overview of wls_server

managed_server_independence_enabled

Specifies whether this Managed Server can be started when the Administration Server is unavailable. In such a case, the Managed Server retrieves its configuration by reading a configuration file and other files directly.

An example on how to use this:

wls_server {a_wls_server :
   ...
   managed_server_independence_enabled => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:managed_server_independence_enabled']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

max_com_message_size

The maximum number of bytes allowed in messages that are received over the COM protocol. If you configure custom network channels for this server, each channel can override this maximum message size. This maximum message size helps guard against a denial of service attack in which a caller attempts to force the server to allocate more memory than is available thereby keeping the server from responding quickly to other requests. A value of -1 causes the COM protocol to use the maximums that are specified elsewhere along the order of precedence.

An example on how to use this:

wls_server {a_wls_server :
   ...
   max_com_message_size => '-1'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:max_com_message_size']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

max_concurrent_long_running_requests

The maximum number of running long-running requests that can be submitted to all the Managed Executor Services or Managed Scheduled Executor Services in the server.

An example on how to use this:

wls_server {a_wls_server :
   ...
   max_concurrent_long_running_requests => '100'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:max_concurrent_long_running_requests']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

max_concurrent_new_threads

The maximum number of running threads that can be created by all the Managed Thread Factories in the server.

An example on how to use this:

wls_server {a_wls_server :
   ...
   max_concurrent_new_threads => '100'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:max_concurrent_new_threads']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

max_http_message_size

The maximum number of bytes allowed in messages that are received over the HTTP protocol. If you configure custom network channels for this server, each channel can override this maximum message size. This maximum message size helps guard against a denial of service attack in which a caller attempts to force the server to allocate more memory than is available thereby keeping the server from responding quickly to other requests. A value of -1 causes the HTTP protocol to use the maximums that are specified elsewhere along the order of precedence.

An example on how to use this:

wls_server {a_wls_server :
   ...
   max_http_message_size => '-1'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:max_http_message_size']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

max_iiop_message_size

The maximum number of bytes allowed in messages that are received over the IIOP protocol. If you configure custom network channels for this server, each channel can override this maximum message size. This maximum message size helps guard against a denial of service attack in which a caller attempts to force the server to allocate more memory than is available thereby keeping the server from responding quickly to other requests. A value of -1 causes the IIOP protocol to use the maximums that are specified elsewhere along the order of precedence.

An example on how to use this:

wls_server {a_wls_server :
   ...
   max_iiop_message_size => '-1'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:max_iiop_message_size']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

max_message_size

The max message size of the server.

Back to overview of wls_server

max_open_sock_count

The maximum number of open sockets allowed in server at a given point of time. When the maximum threshold is reached, the server stops accepting new requests until the number of sockets drops below the threshold. A value less than 0 indicates an unlimited size.

An example on how to use this:

wls_server {a_wls_server :
   ...
   max_open_sock_count => '-1'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:max_open_sock_count']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

max_t3_message_size

The maximum number of bytes allowed in messages that are received over the T3 protocol. If you configure custom network channels for this server, each channel can override this maximum message size. This maximum message size helps guard against a denial of service attack in which a caller attempts to force the server to allocate more memory than is available thereby keeping the server from responding quickly to other requests. A value of -1 causes the T3 protocol to use the maximums that are specified elsewhere along the order of precedence.

An example on how to use this:

wls_server {a_wls_server :
   ...
   max_t3_message_size => '-1'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:max_t3_message_size']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

message_id_prefix_enabled

Indicates whether message IDs in logged messages will include a prefix. Message ids are 6 digit numeric strings that can be optionally presented in a log entry with a prefix. The prefix used by server messages is “BEA-“.

An example on how to use this:

wls_server {a_wls_server :
   ...
   message_id_prefix_enabled => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:message_id_prefix_enabled']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

messaging_bridge_thread_pool_size

Returns the size of the messaging bridge execute thread pool.

An example on how to use this:

wls_server {a_wls_server :
   ...
   messaging_bridge_thread_pool_size => '5'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:messaging_bridge_thread_pool_size']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

migration_additional_migration_attempts

A migratable service could fail to come up on every possible configured server. This attribute controls how many further attempts, after the service has failed on every server at least once, should be tried. Note that each attempt specified here indicates another full circuit of migrations amongst all the configured servers. So for a 3-server cluster, and a value of 2, a total of 4 additional migrations will be attempted. (the original server is never a valid destination)

An example on how to use this:

wls_server {a_wls_server :
   ...
   migration_additional_migration_attempts => '2'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:migration_additional_migration_attempts']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

migration_candidate_machines

Limits the list of candidate machines that the cluster specifies. (Requires you to enable this server for automatic migration and to configure the cluster with a set of candidate machines.)

If this server fails and if it is enabled for automatic migration, Node Manager automatically restarts it. By default, Node Manager restarts the server on any of the candidate machines that the cluster specifies (in order of preference that you configured in the cluster). To change the default, you use this server’s list of candidate machines to create a subset of the cluster-wide candidates. You can also change the order of preference. An example on how to use this:

wls_server {a_wls_server :
   ...
   migration_candidate_machines => ['machine_1','machine_2'],
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:migration_candidate_machines']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

migration_constrained_candidate_servers

The list of servers this JTA migratable target should be constrained to

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:migration_constrained_candidate_servers']
   ...
}

Back to overview of wls_server

migration_critical

Returns true if the MigratableTarget is critical to the overall health of the WLS Server

An example on how to use this:

wls_server {a_wls_server :
   ...
   migration_critical => '1'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:migration_critical']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

migration_millis_to_sleep_between_attempts

Controls how long of a pause there should be between the migration attempts described in getAdditionalMigrationAttempts(). Note that this delay only happens when the service has failed to come up on every server. It does not cause any sort of delay between attempts to migrate otherwise.

An example on how to use this:

wls_server {a_wls_server :
   ...
   migration_millis_to_sleep_between_attempts => '300000'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:migration_millis_to_sleep_between_attempts']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

migration_non_local_post_allowed

Specifies whether or not the post-deactivation script is allowed to run on a different machine. Normally, when auto migration occurs, the post-deactivation script will be run on the service’s current location, and the pre-activation script on the service’s new location. If the current location is unreachable for some reason, this value will be checked to see if it is safe to run it on the service’s new machine. This is useful if the post-deactivation script controls access to a networked resource and does not need any data from the current machine.

An example on how to use this:

wls_server {a_wls_server :
   ...
   migration_non_local_post_allowed => '1'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:migration_non_local_post_allowed']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

migration_notes

Optional information that you can include to describe this configuration. WebLogic Server saves this note in the domain’s configuration file (config.xml) as XML PCDATA. All left angle brackets (<) are converted to the XML entity <. Carriage returns/line feeds are preserved. Note: If you create or edit a note from the Administration Console, the Administration Console does not preserve carriage returns/line feeds.

An example on how to use this:

wls_server {a_wls_server :
   ...
   migration_notes => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:migration_notes']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

migration_number_of_restart_attempts

Specifies how many restart attempts to make before migrating the failed service. Note that these are consecutive attempts. If the value is set to 6, and the service restart fails 5 times before succeeding, but then fails again later, it will not instantly migrate. Each failure gets its own count of restart attempts. A value of 0 is identical to setting {@link #getRestartOnFailure} to false. A value of -1 indicates the service should never be migrated; instead, it will be restarted until it either works or the server shuts down.

An example on how to use this:

wls_server {a_wls_server :
   ...
   migration_number_of_restart_attempts => '6'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:migration_number_of_restart_attempts']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

migration_policy

An example on how to use this:

wls_server {a_wls_server :
   ...
   migration_policy => 'manual'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:migration_policy']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

migration_post_script

Specifies the path to the post-migration script to run after a migratable target is fully deactivated. The script must be in the MIDDLEWARE_HOME/user_projects/domains/mydomain/bin/service_migration directory. After the migratable target is deactivated, if there is a script specified, and Node Manager is available, then the script will run. Specifying a script without an available Node Manager will result in an error upon migration.

An example on how to use this:

wls_server {a_wls_server :
   ...
   migration_post_script => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:migration_post_script']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

migration_post_script_failure_fatal

Specifies whether or not a failure during execution of the post-deactivation script is fatal to the migration. If it is fatal, the migratable target will not be automatically migrated until an administrator manually migrates it to a server, thus reactivating it. Note: Enabling this value will result in weakening the exactly-once guarantee. It is provided to prevent more dangerous data corruption if the post-deactivation script fails. Also if this value is enabled, then the script may be called more than once by the migration framework after the Migratable Target is deactivated or the server or machine hosting the Migratable Target crashed or is network partitioned. The script is expected not to return different exit values when invoked multiple times in such scenarios.

An example on how to use this:

wls_server {a_wls_server :
   ...
   migration_post_script_failure_fatal => '1'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:migration_post_script_failure_fatal']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

migration_pre_script

Specifies the path to the pre-migration script to run before a migratable target is actually activated. The script must be in the MIDDLEWARE_HOME/user_projects/domains/mydomain/bin/service_migration directory. Before the migratable target is activated, if there is a script specified, and Node Manager is available, then the script will run. Specifying a script without an available Node Manager will result in an error upon migration. If the script fails or cannot be found, migration will not proceed on the current server, and will be tried on the next suitable server. This could be the next server in the candidate server list, or in the cluster, if there is no candidate server list.

An example on how to use this:

wls_server {a_wls_server :
   ...
   migration_pre_script => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:migration_pre_script']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

migration_restart_on_failure

Specifies whether or not a failed service will first be deactivated and reactivated in place, instead of being migrated. The number of restart attempts is controlled by {@link #getNumberOfRestartAttempts}. Once these restart attempts are exhausted, the service will migrate. A restarting migratable target will deactivate all services on it in order, then reactivate them all.

An example on how to use this:

wls_server {a_wls_server :
   ...
   migration_restart_on_failure => '1'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:migration_restart_on_failure']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

migration_seconds_between_restarts

Specifies how many seconds to wait in between attempts to restart the failed service.

An example on how to use this:

wls_server {a_wls_server :
   ...
   migration_seconds_between_restarts => '30'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:migration_seconds_between_restarts']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

migration_strict_ownership_check

Whether continue to boot if cannot find the current owner of TRS to do failback. This attribute is only meaningful for servers in cluster. If true: server will fail to boot under this situation. If false: server will continue to boot without trying to do failback.

An example on how to use this:

wls_server {a_wls_server :
   ...
   migration_strict_ownership_check => '1'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:migration_strict_ownership_check']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

migration_tags

Return all tags on this Configuration MBean

An example on how to use this:

wls_server {a_wls_server :
   ...
   migration_tags => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:migration_tags']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

msi_file_replication_enabled

Specifies whether the Administration Server replicates its configuration files to this Managed Server. With file replication enabled, the Administration Server copies its configuration file and SerializedSystemIni.dat into the Managed Server’s root directory every 5 minutes. This option does not replicate a boot identity file. Regardless of the name of the configuration file that you used to start the Administration Server, the replicated file is always named msi-config.xml. For example, if you specified -Dweblogic.ConfigFile=MyConfig.xml when you started the Administration Server, if you have enabled file replication, the Administration Server copies MyConfig.xml and names the copy msi-config.xml. Depending on your backup schemes and the frequency with which you update your domain’s configuration, this option might not be worth the performance cost of copying potentially large files across a network.

An example on how to use this:

wls_server {a_wls_server :
   ...
   msi_file_replication_enabled => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:msi_file_replication_enabled']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

muxer_class

Non-blocking IO is enabled by default on the server side. The default value is weblogic.socket.NIOSocketMuxer. The Certicom SSL implementation is not supported with NIOSocketMuxer. If you need to secure internet communication, Oracle recommends enabling JSSE (Java Secure Socket Extension).

An example on how to use this:

wls_server {a_wls_server :
   ...
   muxer_class => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:muxer_class']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

name

The name.

Back to overview of wls_server

native_io_enabled

Specifies whether native I/O is enabled for the server.

An example on how to use this:

wls_server {a_wls_server :
   ...
   native_io_enabled => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:native_io_enabled']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

nm_socket_create_timeout_in_millis

Returns the timeout value to be used by NodeManagerRuntime when creating a a socket connection to the agent. Default set high as SSH agent may require a high connection establishment time.

An example on how to use this:

wls_server {a_wls_server :
   ...
   nm_socket_create_timeout_in_millis => '180000'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:nm_socket_create_timeout_in_millis']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

notes

Optional information that you can include to describe this configuration. WebLogic Server saves this note in the domain’s configuration file (config.xml) as XML PCDATA. All left angle brackets (<) are converted to the XML entity <. Carriage returns/line feeds are preserved. <dl> <dt>Note:</dt> <dd> If you create or edit a note from the Administration Console, the Administration Console does not preserve carriage returns/line feeds. </dd> </dl>

An example on how to use this:

wls_server {a_wls_server :
   ...
   notes => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:notes']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

num_of_retries_before_msi_mode

Get the number of retries to contact admin server, before starting in Managed Server Independence Mode

An example on how to use this:

wls_server {a_wls_server :
   ...
   num_of_retries_before_msi_mode => '3'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:num_of_retries_before_msi_mode']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

outbound_enabled

Specifies whether new server-to-server connections may consider the default server channel when initiating a connection. This is only relevant if the connection needs to be bound to the default listen address. This will only work for binary protocols that support both outbound and inbound traffic. When this feature is not enabled, connections are initiated using a local address selected by the underlying hardware. For the default channel this is usually what is wanted for IP-routing to be effective. Note that since the default is false, other outbound channels will be considered in preference to the default channel. Default administration channels, created when the domain-wide administration port is turned on, are always considered and bound when initiating an administrative connection. To allow IP-routing for administration traffic create custom admin with {@link NetworkAccessPointMBean#isOutboundEnabled isOutboundEnabled} set to false instead of enabling the domain-wide ADMIN port.

An example on how to use this:

wls_server {a_wls_server :
   ...
   outbound_enabled => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:outbound_enabled']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

outbound_private_key_enabled

Specifies whether the SSL identity specified by {@link SSLMBean#getServerPrivateKeyAlias() getSSLMBean#ServerPrivateKeyAlias} for this server should be used for outbound SSL connections on the default server channel. In normal circumstances the outbound identity is determined by the caller’s environment.

An example on how to use this:

wls_server {a_wls_server :
   ...
   outbound_private_key_enabled => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:outbound_private_key_enabled']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

overload_failure_action

Enable automatic forceshutdown of the server on failed state. The server self-health monitoring detects fatal failures and mark the server as failed. The server can be restarted using NodeManager or a HA agent.

An example on how to use this:

wls_server {a_wls_server :
   ...
   overload_failure_action => 'no-action'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:overload_failure_action']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

overload_free_memory_percent_high_threshold

Percentage free memory after which the server overload condition is cleared. WorkManagers stop performing overloadActions and start regular execution once the overload condition is cleared.

An example on how to use this:

wls_server {a_wls_server :
   ...
   overload_free_memory_percent_high_threshold => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:overload_free_memory_percent_high_threshold']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

overload_free_memory_percent_low_threshold

Percentage free memory below which the server is considered overloaded. WorkManagers perform overloadAction once the server is marked as overloaded.

An example on how to use this:

wls_server {a_wls_server :
   ...
   overload_free_memory_percent_low_threshold => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:overload_free_memory_percent_low_threshold']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

overload_notes

Optional information that you can include to describe this configuration. WebLogic Server saves this note in the domain’s configuration file (config.xml) as XML PCDATA. All left angle brackets (<) are converted to the XML entity <. Carriage returns/line feeds are preserved. Note: If you create or edit a note from the Administration Console, the Administration Console does not preserve carriage returns/line feeds.

An example on how to use this:

wls_server {a_wls_server :
   ...
   overload_notes => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:overload_notes']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

overload_panic_action

Exit the server process when the kernel encounters a panic condition like an unhandled OOME. An unhandled OOME could lead to inconsistent state and a server restart is advisable if backed by node manager or a HA agent.

An example on how to use this:

wls_server {a_wls_server :
   ...
   overload_panic_action => 'system-exit'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:overload_panic_action']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

overload_server_failure_trigger

Configure a trigger that marks the server as failed when the condition is met. A failed server in turn can be configured to shutdown or go into admin state.

An example on how to use this:

wls_server {a_wls_server :
   ...
   overload_server_failure_trigger => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:overload_server_failure_trigger']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

overload_shared_capacity_for_work_managers

Total number of requests that can be present in the server. This includes requests that are enqueued and those under execution. The server performs a differentiated denial of service on reaching the shared capacity. A request with higher priority will be accepted in place of a lower priority request already in the queue. The lower priority request is kept waiting in the queue till all high priority requests are executed. Further enqueues of the low priority requests are rejected right away.

An example on how to use this:

wls_server {a_wls_server :
   ...
   overload_shared_capacity_for_work_managers => '65536'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:overload_shared_capacity_for_work_managers']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

overload_tags

Return all tags on this Configuration MBean

An example on how to use this:

wls_server {a_wls_server :
   ...
   overload_tags => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:overload_tags']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

period_length

The time interval in milliseconds of the heartbeat period. A value of 0 indicates that heartbeats are turned off.

An example on how to use this:

wls_server {a_wls_server :
   ...
   period_length => '60000'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:period_length']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

preferred_secondary_group

Defines secondary clustered instances considered for hosting replicas of the primary HTTP session states created on the server.

An example on how to use this:

wls_server {a_wls_server :
   ...
   preferred_secondary_group => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:preferred_secondary_group']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

print_stack_trace_in_production

Specifies whether the server message log includes exception stack trace that are raised in remote systems.

An example on how to use this:

wls_server {a_wls_server :
   ...
   print_stack_trace_in_production => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:print_stack_trace_in_production']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

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.Available providers are:

simple

Manage server in an WebLogic domain via regular WLST

Back to overview of wls_server

reliable_delivery_policy

The reliable delivery policy for web services.

An example on how to use this:

wls_server {a_wls_server :
   ...
   reliable_delivery_policy => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:reliable_delivery_policy']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

replication_group

Defines preferred clustered instances considered for hosting replicas of the primary HTTP session states created on the server.

An example on how to use this:

wls_server {a_wls_server :
   ...
   replication_group => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:replication_group']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

replication_ports

When WLS is running on Exalogic machines, cluster replication traffic could go over multiple replication channels. However multiple replication channels need not be configured on each clustered server instance. Only one replication channel with explicit IP-Address needs to be configured for each server and replicationPorts range can be specified for each server. For eg. range 7001-7010 will create 10 replication channels with ports 7001 to 7010 for the given server. These channels inherits all the properties of the configured replication channel except the listen port.Names of these channels will be derived from the configured replication channel with suffic {x} added where x could be 1,2.. as per the number of ports specified. Public ports are same as the listen port for these additional channels.

An example on how to use this:

wls_server {a_wls_server :
   ...
   replication_ports => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:replication_ports']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

resolve_dns_name

Resolve the listen address to use for all T3 communication

An example on how to use this:

wls_server {a_wls_server :
   ...
   resolve_dns_name => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:resolve_dns_name']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

restart_delay_seconds

The number of seconds the Node Manager should wait before restarting this server. After killing a server process, the system might need several seconds to release the TCP port(s) the server was using. If Node Manager attempts to restart the Managed Server while its ports are still active, the startup attempt fails. If AutoMigration is enabled and RestartDelaySeconds is 0, the RestartDelaySeconds is automatically set to the lease time. This prevents the server from failing to restart after migration when the previous lease is still valid.

An example on how to use this:

wls_server {a_wls_server :
   ...
   restart_delay_seconds => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:restart_delay_seconds']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

restart_interval_seconds

The number of seconds during which this server can be restarted, up to the number of times specified in RestartMax.

An example on how to use this:

wls_server {a_wls_server :
   ...
   restart_interval_seconds => '3600'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:restart_interval_seconds']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

restart_max

The number of times that the Node Manager can restart this server within the interval specified in Restart Interval.

Back to overview of wls_server

retry_interval_before_msi_mode

Get the number of seconds between the retries to contact admin server, before starting in Managed Server Independence Mode

An example on how to use this:

wls_server {a_wls_server :
   ...
   retry_interval_before_msi_mode => '5'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:retry_interval_before_msi_mode']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

reverse_dns_allowed

Specifies whether the kernel is allowed to perform reverse DNS lookups.

An example on how to use this:

wls_server {a_wls_server :
   ...
   reverse_dns_allowed => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:reverse_dns_allowed']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

scattered_reads_enabled

Enables scattered reads over NIO socket channels. Enabling this attribute increases efficiency during I/O in environments with high network throughput and should be used only when configuring a WebLogic domain for Oracle Exalogic.

An example on how to use this:

wls_server {a_wls_server :
   ...
   scattered_reads_enabled => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:scattered_reads_enabled']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

server_life_cycle_timeout_val

Number of seconds a force shutdown operation waits before timing out and killing itself. If the operation does not complete within the configured timeout seconds, the server will shutdown automatically if the state of the server at that time was SHUTTING_DOWN. A value of 0 means that the server will wait indefinitely for life cycle operation to complete.

An example on how to use this:

wls_server {a_wls_server :
   ...
   server_life_cycle_timeout_val => '30'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:server_life_cycle_timeout_val']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

server_name

The server name

Back to overview of wls_server

server_parameters

The names of the components the server should be a target of.

Back to overview of wls_server

server_template

The template used to configure this server.

An example on how to use this:

wls_server {a_wls_server :
   ...
   server_template => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:server_template']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

server_version

The release identifier for the server. Since this is a configured attribute it is only as accurate as the configuration. The form of the version is major.minor.servicepack.rollingpatch. Not all parts of the version are required. i.e. “7” is acceptable.

An example on how to use this:

wls_server {a_wls_server :
   ...
   server_version => 'unknown'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:server_version']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

socket_buffer_size_as_chunk_size

Specifies whether the server’s buffer size for sending or receiving data through a raw socket should be set to 4KB. Otherwise, the server does not impose a limit to the buffer size and defers to the operating system. This option is useful only on some operating systems for improving performance. It should be disabled in most environments.

An example on how to use this:

wls_server {a_wls_server :
   ...
   socket_buffer_size_as_chunk_size => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:socket_buffer_size_as_chunk_size']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

socket_readers

The number of socket reader threads

An example on how to use this:

wls_server {a_wls_server :
   ...
   socket_readers => '-1'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:socket_readers']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

ssl_accept_kss_demo_certs_enabled

An example on how to use this:

wls_server {a_wls_server :
   ...
   ssl_accept_kss_demo_certs_enabled => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:ssl_accept_kss_demo_certs_enabled']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

ssl_allow_unencrypted_null_cipher

Test if the AllowUnEncryptedNullCipher is enabled see setAllowUnencryptedNullCipher(boolean enable) for the NullCipher feature.

An example on how to use this:

wls_server {a_wls_server :
   ...
   ssl_allow_unencrypted_null_cipher => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:ssl_allow_unencrypted_null_cipher']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

ssl_cert_authenticator

The name of the Java class that implements the weblogic.security.acl.CertAuthenticator class, which is deprecated in this release of WebLogic Server. This field is for Compatibility security only, and is only used when the Realm Adapter Authentication provider is configured. The weblogic.security.acl.CertAuthenticator class maps the digital certificate of a client to a WebLogic Server user. The class has an authenticate() method that WebLogic Server calls after validating the digital certificate presented by the client.

An example on how to use this:

wls_server {a_wls_server :
   ...
   ssl_cert_authenticator => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:ssl_cert_authenticator']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

ssl_ciphersuites

Indicates the cipher suites being used on a particular WebLogic Server. The strongest negotiated cipher suite is chosen during the SSL handshake. The set of cipher suites used by default by JSEE depends on the specific JDK version with which WebLogic Server is configured. For a list of possible values, see Cipher Suites.

An example on how to use this:

wls_server {a_wls_server :
   ...
   ssl_ciphersuites => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:ssl_ciphersuites']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

ssl_client_cert_alias

Determines the alias of the client SSL certificate to be used as identity for outbound SSL connections. The certificate is assumed to be stored in the server configured keystore. <p/> Note that to use the client SSL certificate, {@link #setUseClientCertForOutbound} must be enabled.

An example on how to use this:

wls_server {a_wls_server :
   ...
   ssl_client_cert_alias => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:ssl_client_cert_alias']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

ssl_client_cert_private_key_pass_phrase

The passphrase used to retrieve the private key for the client SSL certificate specified in {@link #getClientCertAlias} from the server configured keystore. This passphrase is assigned to the private key when the private key is generated. <p/> Note that this attribute is usually used when outbound SSL connections specify a client SSL certificate identity. <p/> Note that when you get the value of this attribute, WebLogic Server does the following: <ol> <li>Retrieves the value of the ClientCertPrivateKeyPassPhraseEncrypted attribute. <li>Decrypts the value and returns the unencrypted passphrase. </ol>

An example on how to use this:

wls_server {a_wls_server :
   ...
   ssl_client_cert_private_key_pass_phrase => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:ssl_client_cert_private_key_pass_phrase']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

ssl_client_certificate_enforced

Indicates whether or not clients must present digital certificates from a trusted certificate authority to WebLogic Server.

An example on how to use this:

wls_server {a_wls_server :
   ...
   ssl_client_certificate_enforced => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:ssl_client_certificate_enforced']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

ssl_enabled

Indicates whether the server can be reached through the default SSL listen port. If the administration port is enabled for the WebLogic Server domain, then administrative traffic travels over the administration port and application traffic travels over the Listen Port and SSL Listen Port. If the administration port is disabled, then all traffic travels over the Listen Port and SSL Listen Port.

An example on how to use this:

wls_server {a_wls_server :
   ...
   ssl_enabled => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:ssl_enabled']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

ssl_export_key_lifespan

Indicates the number of times WebLogic Server can use an exportable key between a domestic server and an exportable client before generating a new key. The more secure you want WebLogic Server to be, the fewer times the key should be used before generating a new key.

An example on how to use this:

wls_server {a_wls_server :
   ...
   ssl_export_key_lifespan => '500'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:ssl_export_key_lifespan']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

ssl_hostname_verification_ignored

Specifies whether to ignore the installed implementation of the weblogic.security.SSL.HostnameVerifier interface (when this server is acting as a client to another application server).

An example on how to use this:

wls_server {a_wls_server :
   ...
   ssl_hostname_verification_ignored => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:ssl_hostname_verification_ignored']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

ssl_hostname_verifier

The name of the class that implements the weblogic.security.SSL.HostnameVerifier interface. This class verifies whether the connection to the host with the hostname from URL should be allowed. The class is used to prevent man-in-the-middle attacks. The weblogic.security.SSL.HostnameVerifier has a verify() method that WebLogic Server calls on the client during the SSL handshake.

An example on how to use this:

wls_server {a_wls_server :
   ...
   ssl_hostname_verifier => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:ssl_hostname_verifier']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

ssl_identity_and_trust_locations

Indicates where SSL should find the server’s identity (certificate and private key) as well as the server’s trust (trusted CAs). <ul> <li> If set to KEYSTORES, then SSL retrieves the identity and trust from the server’s keystores (that are configured on the Server). </li> <li> If set to FILES_OR_KEYSTORE_PROVIDERS, then SSL first looks in the deprecated KeyStore providers for the identity and trust. If not found, then it looks in the flat files indicated by the SSL Trusted CA File Name, Server Certificate File Name, and Server Key File Name attributes. </li> </ul> Domains created in WebLogic Server version 8.1 or later, default to KEYSTORES. Domains created before WebLogic Server version 8.1, default to FILES_OR_KEYSTORE_PROVIDERS.

An example on how to use this:

wls_server {a_wls_server :
   ...
   ssl_identity_and_trust_locations => 'KeyStores'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:ssl_identity_and_trust_locations']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

ssl_inbound_certificate_validation

Indicates the client certificate validation rules for inbound SSL. This attribute only applies to ports and network channels using 2-way SSL.

An example on how to use this:

wls_server {a_wls_server :
   ...
   ssl_inbound_certificate_validation => 'BuiltinSSLValidationOnly'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:ssl_inbound_certificate_validation']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

ssl_jsse_enabled

Determines whether the SSL implementation in Weblogic Server is JSSE based.

An example on how to use this:

wls_server {a_wls_server :
   ...
   ssl_jsse_enabled => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:ssl_jsse_enabled']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

ssl_listen_port

The TCP/IP port at which this server listens for SSL connection requests.

An example on how to use this:

wls_server {a_wls_server :
   ...
   ssl_listen_port => '7002'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:ssl_listen_port']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

ssl_login_timeout_millis

Specifies the number of milliseconds that WebLogic Server waits for an SSL connection before timing out. SSL connections take longer to negotiate than regular connections. If clients are connecting over the Internet, raise the default number to accommodate additional network latency.

An example on how to use this:

wls_server {a_wls_server :
   ...
   ssl_login_timeout_millis => '25000'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:ssl_login_timeout_millis']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

ssl_minimum_tls_protocol_version

Get the minimum SSL/TLS protocol version currently configured.

An example on how to use this:

wls_server {a_wls_server :
   ...
   ssl_minimum_tls_protocol_version => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:ssl_minimum_tls_protocol_version']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

ssl_notes

Optional information that you can include to describe this configuration. WebLogic Server saves this note in the domain’s configuration file (config.xml) as XML PCDATA. All left angle brackets (<) are converted to the XML entity <. Carriage returns/line feeds are preserved. <dl> <dt>Note:</dt> <dd> If you create or edit a note from the Administration Console, the Administration Console does not preserve carriage returns/line feeds. </dd> </dl>

An example on how to use this:

wls_server {a_wls_server :
   ...
   ssl_notes => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:ssl_notes']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

ssl_outbound_certificate_validation

Indicates the server certificate validation rules for outbound SSL. This attribute always applies to outbound SSL that is part of WebLogic Server (that is, an Administration Server talking to the Node Manager). It does not apply to application code in the server that is using outbound SSL unless the application code uses a weblogic.security.SSL.ServerTrustManager that is configured to use outbound SSL validation.

An example on how to use this:

wls_server {a_wls_server :
   ...
   ssl_outbound_certificate_validation => 'BuiltinSSLValidationOnly'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:ssl_outbound_certificate_validation']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

ssl_outbound_private_key_alias

The string alias used to store and retrieve the outbound private key in the keystore. This private key is associated with either a server or a client digital certificate. This attribute value is derived from other settings and cannot be physically set. The returned value is determined as follows: <ul> <li>If the {@link #isUseClientCertForOutbound} returns true, the value from {@link #getClientCertAlias} is returned. <li> Otherwise, the value from {@link #getServerPrivateKeyAlias} is returned. </ul>

An example on how to use this:

wls_server {a_wls_server :
   ...
   ssl_outbound_private_key_alias => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:ssl_outbound_private_key_alias']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

ssl_peer_validation_enforced

An example on how to use this:

wls_server {a_wls_server :
   ...
   ssl_peer_validation_enforced => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:ssl_peer_validation_enforced']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

ssl_rejection_logging_enabled

Indicates whether warning messages are logged in the server log when SSL connections are rejected.

An example on how to use this:

wls_server {a_wls_server :
   ...
   ssl_rejection_logging_enabled => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:ssl_rejection_logging_enabled']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

ssl_server_certificate_chain_file_name

The full directory location and name of the file containing an ordered list of certificate authorities trusted by WebLogic Server. The .pem file extension indicates that method that should be used to read the file. Note that as of WebLogic Server version 7.0, the digital certificate for WebLogic Server should not be stored in a file.

An example on how to use this:

wls_server {a_wls_server :
   ...
   ssl_server_certificate_chain_file_name => 'server-certchain.pem'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:ssl_server_certificate_chain_file_name']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

ssl_server_certificate_file_name

The full directory location of the digital certificate file (.der or .pem) for the server. The pathname should either be absolute or relative to the directory from which the server is booted. This field provides backward compatibility for security configurations that stored digital certificates in files. The file extension ( .der or .pem) tells WebLogic Server how to read the contents of the file.

An example on how to use this:

wls_server {a_wls_server :
   ...
   ssl_server_certificate_file_name => 'server-cert.der'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:ssl_server_certificate_file_name']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

ssl_server_key_file_name

The full directory location of the private key file (.der or .pem) for the server. The pathname should either be absolute or relative to the directory from which the server is booted. This field provides backward compatibility for security configurations that store private keys in files. For a more secure deployment, Oracle recommends saving private keys in keystores. The file extension (.der or .pem) indicates the method that should be used to read the file.

An example on how to use this:

wls_server {a_wls_server :
   ...
   ssl_server_key_file_name => 'server-key.der'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:ssl_server_key_file_name']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

ssl_server_private_key_alias

The string alias used to store and retrieve the server’s private key in the keystore. This private key is associated with the server’s digital certificate.

An example on how to use this:

wls_server {a_wls_server :
   ...
   ssl_server_private_key_alias => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:ssl_server_private_key_alias']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

ssl_server_private_key_pass_phrase

The passphrase used to retrieve the server’s private key from the keystore. This passphrase is assigned to the private key when it is generated.

An example on how to use this:

wls_server {a_wls_server :
   ...
   ssl_server_private_key_pass_phrase => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:ssl_server_private_key_pass_phrase']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

ssl_ss_lv2_hello_enabled

Indicate whether SSLv2Hello is enabled

An example on how to use this:

wls_server {a_wls_server :
   ...
   ssl_ss_lv2_hello_enabled => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:ssl_ss_lv2_hello_enabled']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

ssl_tags

Return all tags on this Configuration MBean

An example on how to use this:

wls_server {a_wls_server :
   ...
   ssl_tags => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:ssl_tags']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

ssl_trusted_ca_file_name

The full directory location of the file that specifies the certificate authorities trusted by the server. The pathname should either be absolute or relative to the directory from which the server is booted. This field provides backward compatibility for security configurations that store trusted certificate authorities in files. The file specified in this attribute can contain a single digital certificate or multiple digital certificates. The file extension ( .der or .pem) tells WebLogic Server how to read the contents of the file.

An example on how to use this:

wls_server {a_wls_server :
   ...
   ssl_trusted_ca_file_name => 'trusted-ca.pem'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:ssl_trusted_ca_file_name']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

ssl_two_way_ssl_enabled

The form of SSL that should be used. By default, WebLogic Server is configured to use one-way SSL (implied by the Client Certs Not Requested value). Selecting Client Certs Requested But Not Enforced enables two-way SSL. With this option, the server requests a certificate from the client, but the connection continues if the client does not present a certificate. Selecting Client Certs Requested And Enforced also enables two-way SSL and requires a client to present a certificate. However, if a certificate is not presented, the SSL connection is terminated.

An example on how to use this:

wls_server {a_wls_server :
   ...
   ssl_two_way_ssl_enabled => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:ssl_two_way_ssl_enabled']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

ssl_use_client_cert_for_outbound

Determines whether to use the configured client SSL certificate as identity for outbound SSL connections. <p/> Note that to use a client SSL certificate, one must be specified in {@link #setClientCertAlias}.

An example on how to use this:

wls_server {a_wls_server :
   ...
   ssl_use_client_cert_for_outbound => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:ssl_use_client_cert_for_outbound']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

ssl_use_server_certs

Sets whether the client should use the server certificates/key as the client identity when initiating an outbound connection over https.

An example on how to use this:

wls_server {a_wls_server :
   ...
   ssl_use_server_certs => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:ssl_use_server_certs']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

sslenabled

The ssl enabled on the server.

Valid values are absent, 1, 0.

Back to overview of wls_server

sslhostnameverificationignored

The ssl hostname verification ignored enabled on the server

Valid values are absent, 1, 0.

Back to overview of wls_server

sslhostnameverifier

The sslhostnameverifier of the server.

Back to overview of wls_server

ssllistenport

The TCP/IP port at which this server listens for SSL connection requests.

An example on how to use this:

...{...:
   ...
   ssllistenport => 7002
   ...
}

Help text generated from MBEan text.

Back to overview of wls_server

staging_directory_name

The directory path on the Managed Server where all staged (prepared) applications are placed. If an absolute directory name is not specified, the path is relative to the root directory “/”. Once configured, you cannot change the staging directory name. Remove all applications from the server prior to changing this attribute. The default staging directory is “stage”, relative to the server root.

An example on how to use this:

wls_server {a_wls_server :
   ...
   staging_directory_name => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:staging_directory_name']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

staging_mode

The mode that specifies whether an application’s files are copied from a source on the Administration Server to the Managed Server’s staging area during application preparation. During application preparation, the application’s files are copied from the source on the Administration Server to the Managed Server’s staging area. If you specify nostage or external_stage, the copy will not occur. This is useful when the staging area is a shared directory, already containing the application files, or if this is a single server domain. The administrator must ensure that the Managed Server’s staging directory is set appropriately. Deployment errors will result if the application is not available during the preparation or activation of the application. Each application can override the staging mode specified here.

An example on how to use this:

wls_server {a_wls_server :
   ...
   staging_mode => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:staging_mode']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

startup_mode

The state in which this server should be started. If you specify STANDBY, you must also enable the domain-wide administration port. In the RUNNING state, a server offers its services to clients and can operate as a full member of a cluster. In the ADMIN state, the server is up and running, but available only for administration operations, allowing you to perform server and application-level administration tasks without risk to running applications. In the STANDBY state, a server instance does not process any request; its regular Listen Port is closed. The Administration Port is open. It only accepts life cycle commands that transition the server instance to either the RUNNING or the SHUTDOWN state. Other Administration requests are not accepted. A STANDBY server’s only purpose is to resume into the RUNNING state quickly; it saves server startup time.

An example on how to use this:

wls_server {a_wls_server :
   ...
   startup_mode => 'RUNNING'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:startup_mode']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

startup_timeout

Timeout value for server start and resume operations. If the server fails to start in the timeout period, it will force shutdown. A value of 0 means that the server will wait indefinitely for the operation to complete.

An example on how to use this:

wls_server {a_wls_server :
   ...
   startup_timeout => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:startup_timeout']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

state

The state of the managed server.

The puppet type recognizes all possible states, but it can only manage a full start (e.g. move all the way to state running) and a full stop. (e.g moving all the way to state shutdown). When it is currently shutdown, setting it to state admin for example, will result in a full start.

Valid values are running, starting, standby, admin, resuming, shutting-down, suspening, force_suspend, failed_not_restartable, shutdown.

Back to overview of wls_server

stuck_thread_max_time

The number of seconds that a thread must be continually working before this server considers the thread stuck. For example, if you set this to 600 seconds, WebLogic Server considers a thread to be “stuck” after 600 seconds of continuous use. In Web Logic Server 9.x and later, it is recommended that you use the ServerFailureTriggerMBean in the OverloadProtectionMBean. The ServerFailureTriggerMBean transitions the server to a FAILED state after the specified number of stuck threads are detected. The OverloadProtectionMBean has options to suspend or shutdown a failed server.

An example on how to use this:

wls_server {a_wls_server :
   ...
   stuck_thread_max_time => '600'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:stuck_thread_max_time']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

stuck_thread_timer_interval

The number of seconds after which WebLogic Server periodically scans threads to see if they have been continually working for the configured maximum length of time.

An example on how to use this:

wls_server {a_wls_server :
   ...
   stuck_thread_timer_interval => '60'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:stuck_thread_timer_interval']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

synced_start_stop

Specifies if you want to sync the state of the managed server. This means that when a managed server is started, Puppet will only continue after the start of the managed servers is confirmed by WebLogic.

Valid values are true, false, yes, no.

Back to overview of wls_server

synchronous_write_policy

The disk write policy that determines how the file store writes data to disk.

This policy also affects the JMS file store’s performance, scalability, and reliability. Oracle recommends Direct-Write-With-Cache which tends to have the highest performance. The default value is Direct-Write. The valid policy options are:

• Direct-Write Direct I/O is supported on all platforms. When available, file stores in direct I/O mode automatically load the native I/O wlfileio driver. This option tends to out-perform Cache-Flush and tend to be slower than Direct-Write-With-Cache. This mode does not require a native store wlfileio driver, but performs faster when they are available.
• Direct-Write-With-Cache Store records are written synchronously to primary files in the directory specified by the Directory attribute and asynchronously to a corresponding cache file in the Cache Directory. The Cache Directory provides information about disk space, locking, security, and performance implications. This mode requires a native store wlfileiocode driver. If the native driver cannot be loaded, then the write mode automatically switches to Direct-Write. See Cache Directory.
• Cache-Flush Transactions cannot complete until all of their writes have been flushed down to disk. This policy is reliable and scales well as the number of simultaneous users increases.Transactionally safe but tends to be a lower performer than direct-write policies.
• Disabled Transactions are complete as soon as their writes are cached in memory, instead of waiting for the writes to successfully reach the disk. This is the fastest policy because write requests do not block waiting to be synchronized to disk, but, unlike other policies, is not transactionally safe in the event of operating system or hardware failures. Such failures can lead to duplicate or lost data/messages. This option does not require native store wlfileio drivers, but may run faster when they are available. Some non-WebLogic JMS vendors default to a policy that is equivalent to Disabled.

Notes:

• When available, file stores load WebLogic wlfileio native drivers, which can improve performance. These drivers are included with Windows, Solaris, Linux, and AIX WebLogic installations.
• Certain older versions of Microsoft Windows may incorrectly report storage device synchronous write completion if the Windows default Write Cache Enabled setting is used. This violates the transactional semantics of transactional products (not specific to Oracle), including file stores configured with a Direct-Write (default) or Direct-Write-With-Cache policy, as a system crash or power failure can lead to a loss or a duplication of records/messages. One of the visible symptoms is that this problem may manifest itself in high persistent message/transaction throughput exceeding the physical capabilities of your storage device. You can address the problem by applying a Microsoft supplied patch, disabling the Windows Write Cache Enabled setting, or by using a power-protected storage device. See http://support.microsoft.com/kb/281672 and http://support.microsoft.com/kb/332023.
• NFS storage note: On some operating systems, native driver memory-mapping is incompatible with NFS when files are locked. Stores with synchronous write policies Direct-Write-With-Cache or Disabled, and WebLogic JMS paging stores enhance performance by using the native wlfileio driver to perform memory-map operating system calls. When a store detects an incompatibility between NFS, file locking, and memory mapping, it automatically downgrades to conventional read/write system calls instead of memory mapping. For best performance, Oracle recommends investigating alternative NFS client drivers, configuring a non-NFS storage location, or in controlled environments and at your own risk, disabling the file locks (See Enable File Locking). For more information, see “Tuning the WebLogic Persistent Store” in Tuning Performance of Oracle WebLogic Server.

An example on how to use this:

wls_server {a_wls_server :
   ...
   synchronous_write_policy => 'Direct-Write'
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, Direct-Write, Direct-Write-With-Cache, Cache-Flush, Disabled.

Back to overview of wls_server

tags

Return all tags on this Configuration MBean

An example on how to use this:

wls_server {a_wls_server :
   ...
   tags => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:tags']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

tgiop_enabled

Specifies whether this server supports Tuxedo GIOP (TGIOP) requests. (Requires you to configure WebLogic Tuxedo Connector (WTC) for this server.)

An example on how to use this:

wls_server {a_wls_server :
   ...
   tgiop_enabled => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:tgiop_enabled']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

thread_pool_percent_socket_readers

The percentage of execute threads from the default queue that can be used as socket readers.

An example on how to use this:

wls_server {a_wls_server :
   ...
   thread_pool_percent_socket_readers => '33'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:thread_pool_percent_socket_readers']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

timeout

Timeout for applying a resource.

To be sure no Puppet operation, hangs a Puppet daemon, all operations have a timeout. When this timeout expires, Puppet will abort the current operation and signal an error in the Puppet run.

With this parameter, you can specify the length of the timeout. The value is specified in seconds. In this example, the timeout is set to 600 seconds.

wls_server{'my_server':
  ...
  timeout => 600,
}

The default value for timeout is 120 seconds.

Back to overview of wls_server

transaction_log_file_prefix

The path prefix for the server’s JTA transaction log files. If the pathname is not absolute, the path is assumed to be relative to the server’s root directory. For a clustered server, if you plan to be able to migrate the Transaction Recovery Service from this server if it fails to another server (backup server) in the same cluster, you must store transaction log files on persistent storage, such as a Storage Area Network (SAN) device or a dual-ported disk, available to both servers. Do not use an NFS file system to store transaction log files. Because of the caching scheme in NFS, transaction log files on disk may not always be current. Using transaction log files stored on an NFS device for recovery may cause data corruption.

An example on how to use this:

wls_server {a_wls_server :
   ...
   transaction_log_file_prefix => './'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:transaction_log_file_prefix']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

transaction_log_file_write_policy

The policy that determines how transaction log file entries are written to disk. This policy can affect transaction performance. (Note: To be transactionally safe, the Direct-Write policy may require additional OS or environment changes on some Windows systems.) WebLogic Server supports the following policies: <ul> <li> Cache-Flush. Flushes operating system and on-disk caches after each write. </li> <li> Direct-Write. Tells the operating system to write directly to disk with each write. Direct-Write performs better than Cache-Flush. </li> </ul> If Direct-Write is not supported on the host platform, the policy becomes Cache-Flush and a log message is printed. Note: On Windows, the “Direct-Write” policy may leave transaction data in the on-disk cache without writing it to disk immediately. This is not transactionally safe because a power failure can cause loss of on-disk cache data. For transactionally safe writes using “Direct-Write” on Windows, either disable all write caching for the disk (enabled by default), or use a disk with a battery-backed cache. The on-disk cache for a hard-drive on Windows can be disabled through system administration: Control-Panel -> System -> Hardware-tab -> Device-Manager-button -> Disk-Drives -> name-of-drive -> Policies-tab -> “Enable write caching on the disk” check-box. Some file systems do not allow this value to be changed. For example, a RAID system that has a reliable cache.

An example on how to use this:

wls_server {a_wls_server :
   ...
   transaction_log_file_write_policy => 'Direct-Write'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:transaction_log_file_write_policy']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

trust_keystore_file

The trust keystore file.

Back to overview of wls_server

trust_keystore_passphrase

The trust keystore passphrase

Back to overview of wls_server

tunneling_client_ping_secs

The interval (in seconds) at which to ping a tunneled client to see if it is still alive. If you create network channels for this server, each channel can override this setting.

An example on how to use this:

wls_server {a_wls_server :
   ...
   tunneling_client_ping_secs => '45'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:tunneling_client_ping_secs']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

tunneling_client_timeout_secs

The amount of time (in seconds) after which a missing tunneled client is considered dead. If you create network channels for this server, each channel can override this setting.

An example on how to use this:

wls_server {a_wls_server :
   ...
   tunneling_client_timeout_secs => '40'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:tunneling_client_timeout_secs']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

tunneling_enabled

Specifies whether tunneling for the T3, T3S, HTTP, HTTPS, IIOP, and IIOPS protocols should be enabled for this server. If you create network channels for this server, each channel can override this setting.

An example on how to use this:

wls_server {a_wls_server :
   ...
   tunneling_enabled => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:tunneling_enabled']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

tunnelingenabled

Specifies whether tunneling for the T3, T3S, HTTP, HTTPS, IIOP, and IIOPS protocols should be enabled for this server. If you create network channels for this server, each channel can override this setting.

An example on how to use this:

...{...:
   ...
   tunnelingenabled => 1,
   ...
}

Help text generated from MBEan text.

Valid values are absent, 1, 0.

Back to overview of wls_server

two_way_ssl

Should Two Way SSL be used on the server.

Valid values are absent, 1, 0.

Back to overview of wls_server

upload_directory_name

The directory path on the Administration Server where all uploaded applications are placed. If an absolute directory name is not specified, the path is relative to the root directory “/”. The default staging directory is “stage”, relative to the server root. On the Managed Server this returns null, and is not configurable.

An example on how to use this:

wls_server {a_wls_server :
   ...
   upload_directory_name => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:upload_directory_name']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

use81_style_execute_queues

Backward compatibility mode to switch to 8.1 execute queues instead of WorkManagers. Each of the WorkManagers is converted to an individual execute queue. Setting this attribute requires a server restart.

An example on how to use this:

wls_server {a_wls_server :
   ...
   use81_style_execute_queues => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:use81_style_execute_queues']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

use_concurrent_queue_for_request_manager

Reduces lock contention by using concurrent buffer queue to park incoming requests. Enabling this attribute increases throughput as requests are scheduled with out acquiring any locks.

An example on how to use this:

wls_server {a_wls_server :
   ...
   use_concurrent_queue_for_request_manager => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:use_concurrent_queue_for_request_manager']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

use_detailed_thread_name

Whether to includes detail information in self-tuning thread pool thread names. Setting this flag on would include additional information such as the name of the work manager that the execute thread is executing task for, but at the expense of overhead in keeping the thread name updated with such information.

An example on how to use this:

wls_server {a_wls_server :
   ...
   use_detailed_thread_name => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:use_detailed_thread_name']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

use_enhanced_increment_advisor

Whether the self-tuning should use the enhanced IncrementAdvisor implementation that uses a different algorithm to adjust the size of the self-tuning thread pool.

An example on how to use this:

wls_server {a_wls_server :
   ...
   use_enhanced_increment_advisor => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:use_enhanced_increment_advisor']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

use_enhanced_priority_queue_for_request_manager

Reduces lock contention by using the enhanced ConcurrentCalendarQueue as the priority based queue for pending requests that are waiting for a thread This attribute should be enabled only in an Oracle Exalogic environment.

An example on how to use this:

wls_server {a_wls_server :
   ...
   use_enhanced_priority_queue_for_request_manager => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:use_enhanced_priority_queue_for_request_manager']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

use_fusion_for_llr

Enables the use of the ADM_DDL store procedure for LLR. The default value is false (not enabled). When enabled, a WLS_ prefix and _DYD suffix is is automatically added to the LLR table name at runtime so the LLR table name in server configuration is not consistent with the actual table name in database.

An example on how to use this:

wls_server {a_wls_server :
   ...
   use_fusion_for_llr => 1,
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:use_fusion_for_llr']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

useservercerts

Sets whether the client should use the server certificates/key as the client identity when initiating an outbound connection over https.

An example on how to use this:

...{...:
   ...
   useservercerts => 1,
   ...
}

Help text generated from MBEan text.

Valid values are absent, 1, 0.

Back to overview of wls_server

verbose_ejb_deployment_enabled

Whether or not verbose deployment of EJBs is enabled.

An example on how to use this:

wls_server {a_wls_server :
   ...
   verbose_ejb_deployment_enabled => 'false'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:verbose_ejb_deployment_enabled']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

virtual_machine_name

When WLS is running on JRVE, this specifies the name of the virtual machine running this server

An example on how to use this:

wls_server {a_wls_server :
   ...
   virtual_machine_name => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:virtual_machine_name']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

weblogic_plugin_enabled

The Weblogic Plugin Enabled on the server.

Valid values are absent, 1, 0.

Back to overview of wls_server

webserver_auth_cookie_enabled

Whether authcookie feature is enabled or not.

An example on how to use this:

wls_server {a_wls_server :
   ...
   webserver_auth_cookie_enabled => '1'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:webserver_auth_cookie_enabled']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

webserver_charsets

Provides user defined mapping between internet and Java charset names.

An example on how to use this:

wls_server {a_wls_server :
   ...
   webserver_charsets => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:webserver_charsets']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

webserver_chunked_transfer_disabled

Indicates whether the use of Chunk Transfer-Encoding in HTTP/1.1 is enabled.

An example on how to use this:

wls_server {a_wls_server :
   ...
   webserver_chunked_transfer_disabled => '1'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:webserver_chunked_transfer_disabled']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

webserver_client_ip_header

Get the Client IP Header from WebSerevrMBean.

An example on how to use this:

wls_server {a_wls_server :
   ...
   webserver_client_ip_header => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:webserver_client_ip_header']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

webserver_default_web_app_context_root

Returns the original context-root for the default Web application for this Web server. Alternatively, you can use the context-root attributes in application.xml or weblogic.xml to set a default Web application. The context-root for a default Web application is /. If “” (empty string) is specified, the Web server defaults to /.

An example on how to use this:

wls_server {a_wls_server :
   ...
   webserver_default_web_app_context_root => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:webserver_default_web_app_context_root']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

webserver_deployment_order

A priority that the server uses to determine when it deploys an item. The priority is relative to other deployable items of the same type. For example, the server prioritizes and deploys all EJBs before it prioritizes and deploys startup classes. Items with the lowest Deployment Order value are deployed first. There is no guarantee on the order of deployments with equal Deployment Order values. There is no guarantee of ordering across clusters.

An example on how to use this:

wls_server {a_wls_server :
   ...
   webserver_deployment_order => '1000'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:webserver_deployment_order']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

webserver_frontend_host

The name of the host to which all redirected URLs will be sent. If specified, WebLogic Server will use this value rather than the one in the HOST header. Sets the HTTP frontendHost Provides a method to ensure that the webapp will always have the correct HOST information, even when the request is coming through a firewall or a proxy. If this parameter is configured, the HOST header will be ignored and the information in this parameter will be used in its place.

An example on how to use this:

wls_server {a_wls_server :
   ...
   webserver_frontend_host => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:webserver_frontend_host']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

webserver_frontend_http_port

The name of the HTTP port to which all redirected URLs will be sent. If specified, WebLogic Server will use this value rather than the one in the HOST header. Sets the frontendHTTPPort Provides a method to ensure that the webapp will always have the correct PORT information, even when the request is coming through a firewall or a proxy. If this parameter is configured, the HOST header will be ignored and the information in this parameter will be used in its place.

An example on how to use this:

wls_server {a_wls_server :
   ...
   webserver_frontend_http_port => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:webserver_frontend_http_port']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

webserver_frontend_https_port

The name of the secure HTTP port to which all redirected URLs will be sent. If specified, WebLogic Server will use this value rather than the one in the HOST header. Sets the frontendHTTPSPort Provides a method to ensure that the webapp will always have the correct PORT information, even when the request is coming through a firewall or a proxy. If this parameter is configured, the HOST header will be ignored and the information in this parameter will be used in its place.

An example on how to use this:

wls_server {a_wls_server :
   ...
   webserver_frontend_https_port => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:webserver_frontend_https_port']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

webserver_https_keep_alive_secs

The amount of time this server waits before closing an inactive HTTPS connection. Number of seconds to maintain HTTPS keep-alive before timing out the request.

An example on how to use this:

wls_server {a_wls_server :
   ...
   webserver_https_keep_alive_secs => '60'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:webserver_https_keep_alive_secs']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

webserver_keep_alive_enabled

Indicates whether there should be a persistent connection to this server. (This may improve the performance of your Web applications.) Gets the keepAliveEnabled attribute of the WebServerMBean object

An example on how to use this:

wls_server {a_wls_server :
   ...
   webserver_keep_alive_enabled => '1'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:webserver_keep_alive_enabled']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

webserver_keep_alive_secs

The amount of time this server waits before closing an inactive HTTP connection. Number of seconds to maintain HTTP keep-alive before timing out the request.

An example on how to use this:

wls_server {a_wls_server :
   ...
   webserver_keep_alive_secs => '30'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:webserver_keep_alive_secs']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

webserver_log_buffer_size_kb

Gets the underlying log buffer size in kilobytes

An example on how to use this:

wls_server {a_wls_server :
   ...
   webserver_log_buffer_size_kb => '8'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:webserver_log_buffer_size_kb']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

webserver_log_date_format_pattern

The date format pattern used for rendering dates in the log. The DateFormatPattern string conforms to the specification of the java.text.SimpleDateFormat class.

An example on how to use this:

wls_server {a_wls_server :
   ...
   webserver_log_date_format_pattern => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:webserver_log_date_format_pattern']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

webserver_log_elf_fields

Returns the list of fields specified for the extended logging format for access.log.

An example on how to use this:

wls_server {a_wls_server :
   ...
   webserver_log_elf_fields => 'date time cs-method cs-uri sc-status'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:webserver_log_elf_fields']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

webserver_log_file_count

The maximum number of log files that the server creates when it rotates the log. This number does not include the file that the server uses to store current messages. (Requires that you enable Number of Files Limited.)

An example on how to use this:

wls_server {a_wls_server :
   ...
   webserver_log_file_count => '7'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:webserver_log_file_count']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

webserver_log_file_min_size

The size (1 - 2097150 kilobytes) that triggers the server to move log messages to a separate file. The default is 500 kilobytes. After the log file reaches the specified minimum size, the next time the server checks the file size, it will rename the current log file as SERVER_NAME.lognnnnn and create a new one to store subsequent messages. (Requires that you specify a file rotation type of Size.)

An example on how to use this:

wls_server {a_wls_server :
   ...
   webserver_log_file_min_size => '500'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:webserver_log_file_min_size']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

webserver_log_file_name

The name of the log file.

An example on how to use this:

wls_server {a_wls_server :
   ...
   webserver_log_file_name => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:webserver_log_file_name']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

webserver_log_file_time_span

The interval (in hours) at which the server saves old log messages to another file. (Requires that you specify a file rotation type of TIME.)

An example on how to use this:

wls_server {a_wls_server :
   ...
   webserver_log_file_time_span => '24'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:webserver_log_file_time_span']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

webserver_log_log_file_format

The format of the HTTP log file. Both formats are defined by the W3C. With the extended log format, you use server directives in the log file to customize the information that the server records.

An example on how to use this:

wls_server {a_wls_server :
   ...
   webserver_log_log_file_format => 'common'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:webserver_log_log_file_format']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

webserver_log_log_file_rotation_dir

The directory where the rotated log files will be stored. By default the rotated files are stored in the same directory where the log file is stored.

An example on how to use this:

wls_server {a_wls_server :
   ...
   webserver_log_log_file_rotation_dir => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:webserver_log_log_file_rotation_dir']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

webserver_log_log_time_in_gmt

Specifies whether the time stamps for HTTP log messages are in Greenwich Mean Time (GMT) regardless of the local time zone that the host computer specifies. Use this method to comply with the W3C specification for Extended Format log files. The specification states that all time stamps for Extended Format log entries be in GMT. This method applies only if you have specified the extended message format.

An example on how to use this:

wls_server {a_wls_server :
   ...
   webserver_log_log_time_in_gmt => '1'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:webserver_log_log_time_in_gmt']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

webserver_log_logging_enabled

Indicates whether this server logs HTTP requests. (The remaining fields on this page are relevant only if you select this check box.) Gets the loggingEnabled attribute of the WebServerMBean object.

An example on how to use this:

wls_server {a_wls_server :
   ...
   webserver_log_logging_enabled => '1'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:webserver_log_logging_enabled']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

webserver_log_notes

Optional information that you can include to describe this configuration. WebLogic Server saves this note in the domain’s configuration file (config.xml) as XML PCDATA. All left angle brackets (<) are converted to the XML entity <. Carriage returns/line feeds are preserved. Note: If you create or edit a note from the Administration Console, the Administration Console does not preserve carriage returns/line feeds.

An example on how to use this:

wls_server {a_wls_server :
   ...
   webserver_log_notes => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:webserver_log_notes']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

webserver_log_number_of_files_limited

Indicates whether to limit the number of log files that this server instance creates to store old messages. (Requires that you specify a file rotation type of SIZE or TIME.) After the server reaches this limit, it deletes the oldest log file and creates a new log file with the latest suffix. If you do not enable this option, the server creates new files indefinitely and you must clean up these files as you require.

An example on how to use this:

wls_server {a_wls_server :
   ...
   webserver_log_number_of_files_limited => '1'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:webserver_log_number_of_files_limited']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

webserver_log_rotate_log_on_startup

Specifies whether a server rotates its log file during its startup cycle. The default value in production mode is false.

An example on how to use this:

wls_server {a_wls_server :
   ...
   webserver_log_rotate_log_on_startup => '1'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:webserver_log_rotate_log_on_startup']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

webserver_log_rotation_time

Determines the start time (hour and minute) for a time-based rotation sequence. At the time that this value specifies, the server renames the current log file. Thereafter, the server renames the log file at an interval that you specify in File Time Span. Note that WebLogic Server sets a threshold size limit of 500 MB before it forces a hard rotation to prevent excessive log file growth. Use the following format: H:mm, where <ul> <li>H is Hour in day (0-23)</li> <li>mm is the minute in hour</li> </ul>

An example on how to use this:

wls_server {a_wls_server :
   ...
   webserver_log_rotation_time => '00:00'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:webserver_log_rotation_time']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

webserver_log_rotation_type

Criteria for moving old log messages to a separate file. <ul> <li>NONE Messages accumulate in a single file. You must erase the contents of the file when the size is too large. Note that WebLogic Server sets a threshold size limit of 500 MB before it forces a hard rotation to prevent excessive log file growth.</li> <li>SIZE When the log file reaches the size that you specify in FileMinSize, the server renames the file as SERVER_NAME.lognnnnn.</li> <li>TIME At each time interval that you specify in TimeSpan, the server renames the file as SERVER_NAME.lognnnnn.</li> </ul> After the server renames a file, subsequent messages accumulate in a new file with the name that you specified as the log file name.

An example on how to use this:

wls_server {a_wls_server :
   ...
   webserver_log_rotation_type => 'bySize'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:webserver_log_rotation_type']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

webserver_log_tags

Return all tags on this Configuration MBean

An example on how to use this:

wls_server {a_wls_server :
   ...
   webserver_log_tags => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:webserver_log_tags']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

webserver_max_post_size

The maximum post size this server allows for reading HTTP POST data in a servlet request. A value less than 0 indicates an unlimited size. Gets the maxPostSize attribute of the WebServerMBean object

An example on how to use this:

wls_server {a_wls_server :
   ...
   webserver_max_post_size => '-1'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:webserver_max_post_size']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

webserver_max_post_time_secs

Max Post Time (in seconds) for reading HTTP POST data in a servlet request. MaxPostTime < 0 means unlimited Gets the maxPostTimeSecs attribute of the WebServerMBean object

An example on how to use this:

wls_server {a_wls_server :
   ...
   webserver_max_post_time_secs => '-1'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:webserver_max_post_time_secs']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

webserver_max_request_parameter_count

Max Request Parameter Count this server allows for reading maximum HTTP POST Parameters count in a servlet request. Gets the maxRequestParameterCount attribute of the WebServerMBean object

An example on how to use this:

wls_server {a_wls_server :
   ...
   webserver_max_request_parameter_count => '10000'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:webserver_max_request_parameter_count']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

webserver_notes

Optional information that you can include to describe this configuration. WebLogic Server saves this note in the domain’s configuration file (config.xml) as XML PCDATA. All left angle brackets (<) are converted to the XML entity <. Carriage returns/line feeds are preserved. Note: If you create or edit a note from the Administration Console, the Administration Console does not preserve carriage returns/line feeds.

An example on how to use this:

wls_server {a_wls_server :
   ...
   webserver_notes => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:webserver_notes']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

webserver_overload_response_code

Get the response code to be used when an application is overloaded. An application can get overloaded when the number of pending requests has reached the max capacity specified in the WorkManager or when the server is low on memory. The low memory condition is determined using {@link OverloadProtectionMBean#getFreeMemoryPercentLowThreshold()}.

An example on how to use this:

wls_server {a_wls_server :
   ...
   webserver_overload_response_code => '503'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:webserver_overload_response_code']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

webserver_post_timeout_secs

Timeout (in seconds) for reading HTTP POST data in a servlet request. If the POST data is chunked, the amount of time the server waits between the end of receiving the last chunk of data and the end of receiving the next chunk of data in an HTTP POST before it times out. (This is used to prevent denial-of-service attacks that attempt to overload the server with POST data.) Gets the postTimeoutSecs attribute of the WebServerMBean object

An example on how to use this:

wls_server {a_wls_server :
   ...
   webserver_post_timeout_secs => '30'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:webserver_post_timeout_secs']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

webserver_send_server_header_enabled

Indicates whether this server name is sent with the HTTP response. (This is useful for wireless applications where there is limited space for headers.) Indicates whether this server instance includes its name and WebLogic Server version number in HTTP response headers.

An example on how to use this:

wls_server {a_wls_server :
   ...
   webserver_send_server_header_enabled => '1'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:webserver_send_server_header_enabled']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

webserver_single_signon_disabled

Indicates whether the singleSignonDisabled attribute is enabled

An example on how to use this:

wls_server {a_wls_server :
   ...
   webserver_single_signon_disabled => '1'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:webserver_single_signon_disabled']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

webserver_tags

Return all tags on this Configuration MBean

An example on how to use this:

wls_server {a_wls_server :
   ...
   webserver_tags => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:webserver_tags']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

webserver_url_resource

Adds a URL connection factory resource into JNDI.

An example on how to use this:

wls_server {a_wls_server :
   ...
   webserver_url_resource => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:webserver_url_resource']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

webserver_use_header_encoding

An example on how to use this:

wls_server {a_wls_server :
   ...
   webserver_use_header_encoding => '1'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:webserver_use_header_encoding']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

webserver_use_highest_compatible_http_version

Enables use of the highest compatible HTTP protocol version-string in the response. E.g. HTTP spec suggests that HTTP/1.1 version-string should be used in response to a request using HTTP/1.0. This does not necessarily affect the response format.

An example on how to use this:

wls_server {a_wls_server :
   ...
   webserver_use_highest_compatible_http_version => '1'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:webserver_use_highest_compatible_http_version']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

webserver_wap_enabled

Indicates whether the session ID should include JVM information. (Checking this box may be necessary when using URL rewriting with WAP devices that limit the size of the URL to 128 characters, and may also affect the use of replicated sessions in a cluster.) When this box is selected, the default size of the URL will be set at 52 characters, and it will not contain any special characters. Gets the WAPEnabled attribute of the WebServerMBean object

An example on how to use this:

wls_server {a_wls_server :
   ...
   webserver_wap_enabled => '1'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:webserver_wap_enabled']
   ...
}

This help text generated from MBean text of the WebLogic server.

Valid values are absent, 1, 0.

Back to overview of wls_server

webserver_write_chunk_bytes

The default size of the blocks to be written to the network layer. Gets the writeChunkBytes attribute of the WebServerMBean object

An example on how to use this:

wls_server {a_wls_server :
   ...
   webserver_write_chunk_bytes => '512'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:webserver_write_chunk_bytes']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

xml_entity_cache

The server’s XML entity cache, which is used to configure the behavior of JAXP (Java API for XML Parsing).

An example on how to use this:

wls_server {a_wls_server :
   ...
   xml_entity_cache => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:xml_entity_cache']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server

xml_registry

The server’s XML registry, which is used to configure the behavior of JAXP (Java API for XML Parsing).

An example on how to use this:

wls_server {a_wls_server :
   ...
   xml_registry => 'a_value'
   ...
}

This is an extended property. Before you can use it add it to the wls_settings property extra_properties.

wls_setting{'domain':
   ...
  extra_properties => ['wls_server:xml_registry']
   ...
}

This help text generated from MBean text of the WebLogic server.

Back to overview of wls_server