Overview

This resource allows you to manage a multi datasource in an WebLogic domain.

Here is an example on how you should use this:

wls_multi_datasource { 'myMultiDatasource':
  ensure        => 'present',
  algorithmtype => 'Failover',
  datasources   => ['myJDBCDatasource'],
  jndinames     => ['myMultiDatasource'],
  target         => ['ManagedServer1', 'WebCluster'],
  targettype     => ['Server', 'Cluster'],
  testfrequency => '120',
}

In this example you are managing a multi datasource in the default domain. When you want to manage a multi datasource in a specific domain, you can use:

wls_multi_datasource { 'my_domain/myMultiDatasource':
  ensure        => 'present',
  algorithmtype => 'Failover',
  datasources   => ['myJDBCDatasource'],
  jndinames     => ['myMultiDatasource'],
  target         => ['ManagedServer1', 'WebCluster'],
  targettype     => ['Server', 'Cluster'],
  testfrequency => '120',
}

Attributes

Attribute Name Short Description
algorithmtype The algorithm determines the connection request processing for the multi data source
   
compatibility_name This is only set for beans created as a result of conversion from an 8.1 application configured using ApplicationMBean and ComponentMBean.
datasources The datasources that are part of the multi datasource
   
deployment_order An integer value that indicates when this unit is deployed, relative to other deployable units on a server, during startup.
deployment_principal_name A string value that indicates the principal that should be used when deploying the file or archive during startup and shutdown.
domain With this parameter, you identify the domain, where your objects is in.
driver_name The full package name of JDBC driver class used to create the physical database connections in the connection pool in the data source.
driver_password The password attribute passed to the JDBC driver when creating physical database connections.
driver_url The URL of the database to connect to.
driver_use_password_indirection Specifies whether the database credentials are to be obtained from the credential mapper using the “user” property as the key.
driver_use_xa_data_source_interface Specifies that WebLogic Server should use the XA interface of the JDBC driver.
ds_algorithm_type The algorithm determines the connection request processing for the multi data source.
ds_connection_pool_failover_callback_handler The name of the application class to handle the callback sent when a multi data source is ready to failover or fail back connection requests to another data source within the multi data source.
ds_data_source_list The list of data sources to which the multi data source will route connection requests.
ds_failover_request_if_busy For multi data sources with the failover algorithm, enables the multi data source to failover connection requests to the next data source if all connections in the current data source are in use.
ds_global_transactions_protocol Determines the transaction protocol (global transaction processing behavior) for the data source.
ds_jndi_names The JNDI path to where this Data Source is bound.
ds_keep_conn_after_global_tx Enables WebLogic Server to keep the physical database connection associated with the logical connection when committing a global transaction instead releasing it and getting another physical connection when needed.
ds_keep_conn_after_local_tx Enables WebLogic Server to keep the physical database connection associated with the logical connection when committing a local transaction instead releasing it and getting another physical connection when needed.
ds_proxy_switching_callback The name of the switching callback class for a Proxy data source.
ds_proxy_switching_properties Specifies the switching properties passed to the switching callback method for a Proxy data source.
ds_row_prefetch Enables multiple rows to be “prefetched” (that is, sent from the server to the client) in one server access.
ds_row_prefetch_size If row prefetching is enabled, specifies the number of result set rows to prefetch for a client.
ds_scope Specifies the scoping of the data source.
ds_stream_chunk_size Specifies the data chunk size for steaming data types.
ensure The basic property that the resource should be in.
jndinames The datasource jndi names.
module_type The values match those defined by jsr88.
multi_datasource_name The multi atasource name
   
name The name.
notes Optional information that you can include to describe this configuration.
oracle_active_gridlink Indicates a configured Active GridLink datasource.
oracle_affinity_policy Specifies the affinity policy for the datasource.
oracle_connection_initialization_callback The name of the Connection Initialization Callback class.
oracle_enable_java_net_fast_path Deprecated.
oracle_fan_enabled Enables the data source to subscribe to and process Oracle FAN events.
oracle_ons_node_list A comma-separate list of ONS daemon listen addresses and ports to which connect to for receiving ONS-based FAN events.
oracle_ons_wallet_file The location of the Oracle wallet file in which the SSL certificates are stored.
oracle_ons_wallet_password The wallet password attribute that is included as part of the ONS client configuration string.
oracle_optimize_utf8_conversion Enables the Oracle JDBC optimize UTF-8 conversion option.
oracle_proxy_session Enables Oracle JDBC Proxy Authentication.
oracle_replay_initiation_timeout The amount of time, in seconds, a data source allows for Application Continuity replay processing before timing out and ending a replay session context.
oracle_use_database_credentials If enabled, Oracle database credentials are used in getConnection instead of application server credentials.
pool_capacity_increment The increment by which this JDBC connection pool’s capacity is expanded.
pool_connection_creation_retry_frequency_seconds The number of seconds between attempts to establish connections to the database.
pool_connection_harvest_max_count The maximum number of connections that may be harvested when the connection harvesting occurs.
pool_connection_harvest_trigger_count Specifies the number of available connections (trigger value) used to determine when connection harvesting occurs.
pool_connection_labeling_callback The class name of the connection labeling callback.
pool_connection_reserve_timeout_seconds The number of seconds after which a call to reserve a connection from the connection pool will timeout.
pool_count_of_refresh_failures_till_disable Specifies the number of reconnect failures allowed before WebLogic Server disables a connection pool to minimize the delay in handling the connection request caused by a database failure.
pool_count_of_test_failures_till_flush Specifies the number of test failures allowed before WebLogic Server closes all unused connections in a connection pool to minimize the delay caused by further database testing.
pool_credential_mapping_enabled Enables Set Client ID on connection for the data source.
pool_driver_interceptor Specifies the absolute name of the application class used to intercept method calls to the JDBC driver.
pool_fatal_error_codes Specifies a comma-separated list of error codes that are treated as fatal errors.
pool_highest_num_waiters The maximum number of connection requests that can concurrently block threads while waiting to reserve a connection from the data source’s connection pool.
pool_identity_based_connection_pooling_enabled Enables identity-based-connection-pooling for the data source.
pool_ignore_in_use_connections_enabled Enables the data source to be shutdown even if connections obtained from the pool are still in use.
pool_inactive_connection_timeout_seconds The number of inactive seconds on a reserved connection before WebLogic Server reclaims the connection and releases it back into the connection pool.
pool_init_sql SQL statement to execute that will initialize newly created physical database connections.
pool_initial_capacity The number of physical connections to create when creating the connection pool in the data source.
pool_jdbcxa_debug_level Specifies level of JDBC debugging for XA drivers, where larger values in the range provide more debugging information.
pool_login_delay_seconds The number of seconds to delay before creating each physical database connection.
pool_max_capacity The maximum number of physical connections that this connection pool can contain.
pool_min_capacity The minimum number of physical connections that this connection pool can contain after it is initialized.
pool_pinned_to_thread Enables an option to improve performance by enabling execute threads to keep a pooled database connection even after the application closes the logical connection.
pool_profile_connection_leak_timeout_seconds The number of seconds that a JDBC connection needs to be held by an application before triggering a connection leak diagnostic profiling record.
pool_profile_harvest_frequency_seconds The number of seconds between when WebLogic Server harvests profile data.
pool_profile_type Specifies that type of profile data to be collected for the JDBC subsystem.
pool_remove_infected_connections Specifies whether a connection will be removed from the connection pool after the application uses the underlying vendor connection object.
pool_seconds_to_trust_an_idle_pool_connection The number of seconds within a connection use that WebLogic Server trusts that the connection is still viable and will skip the connection test, either before delivering it to an application or during the periodic connection testing process.
pool_shrink_frequency_seconds The number of seconds to wait before shrinking a connection pool that has incrementally increased to meet demand.
pool_statement_cache_size The number of prepared and callable statements stored in the cache.
pool_statement_cache_type The algorithm used for maintaining the prepared statements stored in the statement cache.
pool_statement_timeout The time after which a statement currently being executed will time out.
pool_test_connections_on_reserve Enables WebLogic Server to test a connection before giving it to a client.
pool_test_frequency_seconds The number of seconds a WebLogic Server instance waits between attempts when testing unused connections.
pool_test_table_name The name of the database table to use when testing physical database connections.
pool_wrap_jdbc By default, SQL objects for CallableStatement, PreparedStatement, ResultSet, Statement, and DatabaseMetaData are wrapped with a WebLogic wrapper.
pool_wrap_types By default, data type objects for Array, Blob, Clob, NClob, Ref, SQLXML, and Struct, plus ParameterMetaData and ResultSetMetaData objects are wrapped with a WebLogic wrapper.
provider resource.
source_path  
   
tags Return all tags on this Configuration MBean
   
target An array of target names.
targettype An array of target types.
testfrequency The number of seconds a WebLogic Server instance waits between attempts when testing unused connections.
xa_end_only_once Specifies that XAResource.end() is called only once for each pending XAResource.start().
xa_keep_logical_conn_open_on_release Enables WebLogic Server to keep the logical JDBC connection open for a global transaction when the physical XA connection is returned to the connection pool.
xa_keep_xa_conn_till_tx_complete Enables WebLogic Server to associate the same XA database connection from the connection pool with a global transaction until the transaction completes.
xa_need_tx_ctx_on_close Specifies whether the XA driver requires a distributed transaction context when closing various JDBC objects (result sets, statements, connections, and so forth).
xa_new_xa_conn_for_commit Specifies that a dedicated XA connection is used for commit and rollback processing for a global transaction.
xa_recover_only_once Specifies that the transaction manager calls recover on the resource only once.
xa_resource_health_monitoring Enables JTA resource health monitoring for an XA data source.
xa_retry_duration_seconds Determines the duration in seconds for which the transaction manager will perform recover operations on the resource.
xa_retry_interval_seconds The number of seconds between XA retry operations if XARetryDurationSeconds is set to a positive value.
xa_rollback_local_tx_upon_conn_close Enables WebLogic Server to call rollback() on the connection before returning the connection to the connection pool.
xa_set_transaction_timeout Enables WebLogic Server to set a transaction branch timeout based on the value for XaTransactionTimeout.
xa_transaction_timeout The number of seconds to set as the transaction branch timeout.

algorithmtype

The algorithm determines the connection request processing for the multi data source

Valid values are absent, Load-Balancing, Failover. Back to overview of wls_multi_datasource

compatibility_name

This is only set for beans created as a result of conversion from an 8.1 application configured using ApplicationMBean and ComponentMBean. Standalone modules in 8.1 have both an ApplicationMBean name and ComponentMBean name. This attribute stores the name of the latter, to be used when the server creates the transient ComponentMBean for backward compatibility.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   compatibility_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_multi_datasource:compatibility_name']
   ...
}

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

Back to overview of wls_multi_datasource

datasources

The datasources that are part of the multi datasource

Back to overview of wls_multi_datasource

deployment_order

An integer value that indicates when this unit is deployed, relative to other deployable units on a server, during startup. Units with lower values are deployed before those with higher values.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   deployment_order => '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_multi_datasource:deployment_order']
   ...
}

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

Back to overview of wls_multi_datasource

deployment_principal_name

A string value that indicates the principal that should be used when deploying the file or archive during startup and shutdown. This principal will be used to set the current subject when calling out into application code for interfaces such as ApplicationLifecycleListener. If no principal name is specified, then the anonymous principal will be used.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   deployment_principal_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_multi_datasource:deployment_principal_name']
   ...
}

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

Back to overview of wls_multi_datasource

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_multi_datasource

driver_name

The full package name of JDBC driver class used to create the physical database connections in the connection pool in the data source. For example: oracle.jdbc.OracleDriver The driver must be the name of a class that implements the java.sql.Driver interface. Check the driver documentation to find the full pathname. Note that the driver class must be in the classpath of any server to which the data source is deployed.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   driver_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_multi_datasource:driver_name']
   ...
}

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

Back to overview of wls_multi_datasource

driver_password

The password attribute passed to the JDBC driver when creating physical database connections. The value is stored in an encrypted form in the descriptor file and when displayed in an administration console.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   driver_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_multi_datasource:driver_password']
   ...
}

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

Back to overview of wls_multi_datasource

driver_url

The URL of the database to connect to. The format of the URL varies by JDBC driver. The URL is passed to the JDBC driver to create the physical database connections.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   driver_url => '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_multi_datasource:driver_url']
   ...
}

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

Back to overview of wls_multi_datasource

driver_use_password_indirection

Specifies whether the database credentials are to be obtained from the credential mapper using the “user” property as the key. When true, the credentials are obtained from the credential mapper. When false, the database user name and password are obtained from the “user” property and Password element, respectively.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   driver_use_password_indirection => '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_multi_datasource:driver_use_password_indirection']
   ...
}

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

Valid values are absent, 0, 1. Back to overview of wls_multi_datasource

driver_use_xa_data_source_interface

Specifies that WebLogic Server should use the XA interface of the JDBC driver. If the JDBC driver class used to create database connections implements both XA and non-XA versions of a JDBC driver, you can set this attribute to indicate that WebLogic Server should treat the JDBC driver as an XA driver or as a non-XA driver.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   driver_use_xa_data_source_interface => '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_multi_datasource:driver_use_xa_data_source_interface']
   ...
}

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

Valid values are absent, 0, 1. Back to overview of wls_multi_datasource

ds_algorithm_type

The algorithm determines the connection request processing for the multi data source. You can specify one of the following algorithm types: <ul> <li>Failover Connection requests are sent to the first data source in the list; if the request fails, the request is sent to the next data source in the list, and so forth. The process is repeated until a valid connection is obtained, or until the end of the list is reached, in which case an exception is thrown. </li> <li>Load balancing The multi data source distributes connection requests evenly to its member data sources. With this algorithm, the multi data source also provides failover processing. That is, if a request fails, the multi data source sends the request to the next data source in the list until a valid connection is obtained, or until the end of the list is reached, in which case an exception is thrown. </li> </ul>

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   ds_algorithm_type => 'Failover'
   ...
}

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

wls_setting{'domain':
   ...
  extra_properties => ['wls_multi_datasource:ds_algorithm_type']
   ...
}

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

Back to overview of wls_multi_datasource

ds_connection_pool_failover_callback_handler

The name of the application class to handle the callback sent when a multi data source is ready to failover or fail back connection requests to another data source within the multi data source. The name must be the absolute name of an application class that implements the weblogic.jdbc.extensions.ConnectionPoolFailoverCallback interface.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   ds_connection_pool_failover_callback_handler => '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_multi_datasource:ds_connection_pool_failover_callback_handler']
   ...
}

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

Back to overview of wls_multi_datasource

ds_data_source_list

The list of data sources to which the multi data source will route connection requests. The order of data sources in the list determines the failover order.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   ds_data_source_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_multi_datasource:ds_data_source_list']
   ...
}

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

Back to overview of wls_multi_datasource

ds_failover_request_if_busy

For multi data sources with the failover algorithm, enables the multi data source to failover connection requests to the next data source if all connections in the current data source are in use.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   ds_failover_request_if_busy => '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_multi_datasource:ds_failover_request_if_busy']
   ...
}

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

Valid values are absent, 0, 1. Back to overview of wls_multi_datasource

ds_global_transactions_protocol

Determines the transaction protocol (global transaction processing behavior) for the data source. Options include: <ul> <li> TwoPhaseCommit - Standard XA transaction processing. Requires an XA driver. </li> <li> LoggingLastResource - A performance enhancement for one non-XA resource. </li> <li> EmulateTwoPhaseCommit - Enables one non-XA resource to participate in a global transaction, but has some risk to data. </li> <li> OnePhaseCommit - One-phase XA transaction processing using a non-XA driver. This is the default setting. </li> <li> None - Support for local transactions only. </li> </ul>

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   ds_global_transactions_protocol => 'OnePhaseCommit'
   ...
}

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

wls_setting{'domain':
   ...
  extra_properties => ['wls_multi_datasource:ds_global_transactions_protocol']
   ...
}

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

Back to overview of wls_multi_datasource

ds_jndi_names

The JNDI path to where this Data Source is bound. By default, the JNDI name is the name of the data source. Applications that look up the JNDI path will get a javax.sql.DataSource instance that corresponds to this data source.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   ds_jndi_names => '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_multi_datasource:ds_jndi_names']
   ...
}

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

Back to overview of wls_multi_datasource

ds_keep_conn_after_global_tx

Enables WebLogic Server to keep the physical database connection associated with the logical connection when committing a global transaction instead releasing it and getting another physical connection when needed. Setting this option to true may require additional connections to be configured on the database. Use this setting to work around specific problems with JDBC XA drivers.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   ds_keep_conn_after_global_tx => '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_multi_datasource:ds_keep_conn_after_global_tx']
   ...
}

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

Valid values are absent, 0, 1. Back to overview of wls_multi_datasource

ds_keep_conn_after_local_tx

Enables WebLogic Server to keep the physical database connection associated with the logical connection when committing a local transaction instead releasing it and getting another physical connection when needed. Setting this option to true may require additional connections to be configured on the database. Use this setting to work around specific problems with JDBC XA drivers.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   ds_keep_conn_after_local_tx => '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_multi_datasource:ds_keep_conn_after_local_tx']
   ...
}

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

Valid values are absent, 0, 1. Back to overview of wls_multi_datasource

ds_proxy_switching_callback

The name of the switching callback class for a Proxy data source. This class implements the weblogic.jdbc.extensions.DataSourceSwitchingCallback interface.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   ds_proxy_switching_callback => '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_multi_datasource:ds_proxy_switching_callback']
   ...
}

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

Back to overview of wls_multi_datasource

ds_proxy_switching_properties

Specifies the switching properties passed to the switching callback method for a Proxy data source.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   ds_proxy_switching_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_multi_datasource:ds_proxy_switching_properties']
   ...
}

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

Back to overview of wls_multi_datasource

ds_row_prefetch

Enables multiple rows to be “prefetched” (that is, sent from the server to the client) in one server access. When an external client accesses a database using JDBC through WebLogic Server, row prefetching improves performance by fetching multiple rows from the server to the client in one server access. WebLogic Server ignores this setting and does not use row prefetching when the client and WebLogic Server are in the same JVM.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   ds_row_prefetch => '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_multi_datasource:ds_row_prefetch']
   ...
}

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

Valid values are absent, 0, 1. Back to overview of wls_multi_datasource

ds_row_prefetch_size

If row prefetching is enabled, specifies the number of result set rows to prefetch for a client. The optimal prefetch size depends on the particulars of the query. In general, increasing this number will increase performance, until a particular value is reached. At that point further increases do not result in any significant performance increase. Very rarely will increased performance result from exceeding 100 rows. The default value should be reasonable for most situations.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   ds_row_prefetch_size => '48'
   ...
}

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

wls_setting{'domain':
   ...
  extra_properties => ['wls_multi_datasource:ds_row_prefetch_size']
   ...
}

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

Back to overview of wls_multi_datasource

ds_scope

Specifies the scoping of the data source. You can specify one of the following scopes: <ul> <li>Global Specifies that the data source is bound in the cluster-wide JNDI tree with the JNDIName specified so that the data source is available for use to any JDBC client across the cluster. This is the default setting. </li> <li>Application Specifies that the data source is bound in the application’s local namespace with the JNDIName specified so that the data source is available for use only by JDBC clients within the application. This can only be used for packaged datasources and is ignored for JDBC System resources. </li> </ul>

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   ds_scope => 'Global'
   ...
}

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

wls_setting{'domain':
   ...
  extra_properties => ['wls_multi_datasource:ds_scope']
   ...
}

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

Back to overview of wls_multi_datasource

ds_stream_chunk_size

Specifies the data chunk size for steaming data types. Streaming data types (for example resulting from a call to getBinaryStream()) are sent in sized chunks from WebLogic Server to the client as needed.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   ds_stream_chunk_size => '256'
   ...
}

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

wls_setting{'domain':
   ...
  extra_properties => ['wls_multi_datasource:ds_stream_chunk_size']
   ...
}

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

Back to overview of wls_multi_datasource

ensure

The basic property that the resource should be in.

Valid values are present, absent. Back to overview of wls_multi_datasource

jndinames

The datasource jndi names.

Back to overview of wls_multi_datasource

module_type

The values match those defined by jsr88. This attribute may move to another MBean.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   module_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_multi_datasource:module_type']
   ...
}

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

Back to overview of wls_multi_datasource

multi_datasource_name

The multi atasource name

Back to overview of wls_multi_datasource

name

The name.

Back to overview of wls_multi_datasource

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 &lt;. 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_multi_datasource {a_wls_multi_datasource :
   ...
   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_multi_datasource:notes']
   ...
}

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

Back to overview of wls_multi_datasource

Indicates a configured Active GridLink datasource. This attributed is set to true when using the console to create an Active GridLink datasource. It is ignored if FanEnabled is true or OnsNodeList is a non-null string.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   oracle_active_gridlink => '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_multi_datasource:oracle_active_gridlink']
   ...
}

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

Valid values are absent, 0, 1. Back to overview of wls_multi_datasource

oracle_affinity_policy

Specifies the affinity policy for the datasource. Options include: <ul> <li>Transaction: Transaction affinity</li> <li>Session: Web-session affinity</li> <li>Data: Data affinity</li> </ul> The default value is Session.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   oracle_affinity_policy => 'Session'
   ...
}

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

wls_setting{'domain':
   ...
  extra_properties => ['wls_multi_datasource:oracle_affinity_policy']
   ...
}

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

Back to overview of wls_multi_datasource

oracle_connection_initialization_callback

The name of the Connection Initialization Callback class. This name is automatically passed to registerConnectionInitializationCallback when a data source is created. The class must implement oracle.ucp.jdbc.ConnectionInitializationCallback.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   oracle_connection_initialization_callback => '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_multi_datasource:oracle_connection_initialization_callback']
   ...
}

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

Back to overview of wls_multi_datasource

oracle_enable_java_net_fast_path

Deprecated.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   oracle_enable_java_net_fast_path => '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_multi_datasource:oracle_enable_java_net_fast_path']
   ...
}

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

Valid values are absent, 0, 1. Back to overview of wls_multi_datasource

oracle_fan_enabled

Enables the data source to subscribe to and process Oracle FAN events. This attribute is only applicable for RAC configurations that publish FAN notification events using the ONS protocol.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   oracle_fan_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_multi_datasource:oracle_fan_enabled']
   ...
}

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

Valid values are absent, 0, 1. Back to overview of wls_multi_datasource

oracle_ons_node_list

A comma-separate list of ONS daemon listen addresses and ports to which connect to for receiving ONS-based FAN events. It is required when connecting to Oracle 11g databases and optional when connecting to Oracle database releases 12c and higher.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   oracle_ons_node_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_multi_datasource:oracle_ons_node_list']
   ...
}

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

Back to overview of wls_multi_datasource

oracle_ons_wallet_file

The location of the Oracle wallet file in which the SSL certificates are stored. Only required when the ONS client is configured to communicate with ONS daemons using SSL.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   oracle_ons_wallet_file => '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_multi_datasource:oracle_ons_wallet_file']
   ...
}

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

Back to overview of wls_multi_datasource

oracle_ons_wallet_password

The wallet password attribute that is included as part of the ONS client configuration string. This attribute is only required when ONS is configured to use the SSL protocol. The value is stored in an encrypted form in the descriptor file and when displayed in an administration console.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   oracle_ons_wallet_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_multi_datasource:oracle_ons_wallet_password']
   ...
}

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

Back to overview of wls_multi_datasource

oracle_optimize_utf8_conversion

Enables the Oracle JDBC optimize UTF-8 conversion option.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   oracle_optimize_utf8_conversion => '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_multi_datasource:oracle_optimize_utf8_conversion']
   ...
}

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

Valid values are absent, 0, 1. Back to overview of wls_multi_datasource

oracle_proxy_session

Enables Oracle JDBC Proxy Authentication. <ul> <li>Only applicable for the Oracle driver.</li> <li>Requires WebLogic Server user IDs are mapped to database user IDs using credential mapping.</li> </ul>

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   oracle_proxy_session => '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_multi_datasource:oracle_proxy_session']
   ...
}

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

Valid values are absent, 0, 1. Back to overview of wls_multi_datasource

oracle_replay_initiation_timeout

The amount of time, in seconds, a data source allows for Application Continuity replay processing before timing out and ending a replay session context. <ul> <li>When set to zero (0) seconds, replay processing is disabled.</li> <li>The default value is 3600 seconds.</li> <li>See oracle.ucp.jdbc.ConnectionInitializationCallback.</ul>

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   oracle_replay_initiation_timeout => '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_multi_datasource:oracle_replay_initiation_timeout']
   ...
}

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

Back to overview of wls_multi_datasource

oracle_use_database_credentials

If enabled, Oracle database credentials are used in getConnection instead of application server credentials. The database credentials are used to get a proxy session without requiring any work in the credential mapper.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   oracle_use_database_credentials => '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_multi_datasource:oracle_use_database_credentials']
   ...
}

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

Valid values are absent, 0, 1. Back to overview of wls_multi_datasource

pool_capacity_increment

The increment by which this JDBC connection pool’s capacity is expanded. In WebLogic Server 10.3.1 and higher releases, the capacityIncrement is no longer configurable and is set to a value of 1. When there are no more available physical connections to service requests, the connection pool will create this number of additional physical database connections and add them to the connection pool. The connection pool will ensure that it does not exceed the maximum number of physical connections.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   pool_capacity_increment => '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_multi_datasource:pool_capacity_increment']
   ...
}

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

Back to overview of wls_multi_datasource

pool_connection_creation_retry_frequency_seconds

The number of seconds between attempts to establish connections to the database. If you do not set this value, data source creation fails if the database is unavailable. If set and if the database is unavailable when the data source is created, WebLogic Server will attempt to create connections in the pool again after the number of seconds you specify, and will continue to attempt to create the connections until it succeeds. When set to 0, connection retry is disabled.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   pool_connection_creation_retry_frequency_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_multi_datasource:pool_connection_creation_retry_frequency_seconds']
   ...
}

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

Back to overview of wls_multi_datasource

pool_connection_harvest_max_count

The maximum number of connections that may be harvested when the connection harvesting occurs. The range of valid values is 1 to MaxCapacity.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   pool_connection_harvest_max_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_multi_datasource:pool_connection_harvest_max_count']
   ...
}

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

Back to overview of wls_multi_datasource

pool_connection_harvest_trigger_count

Specifies the number of available connections (trigger value) used to determine when connection harvesting occurs.

  • Harvesting occurs when the number of available connections is below the trigger value for a connection pool.
  • The range of valid values is -1 to MaxCapacity.
  • Default value is -1.
  • Setting the value to -1 disables connection harvesting.

An example on how to use this:

wls_datasource {a_wls_datasource :
   ...
   pool_connection_harvest_trigger_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_datasource:pool_connection_harvest_trigger_count']
   ...
}

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

Back to overview of wls_multi_datasource

pool_connection_labeling_callback

The class name of the connection labeling callback. This is automatically passed to registerConnectionLabelingCallback when the datasource is created. The class must implement oracle.ucp.ConnectionLabelingCallback.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   pool_connection_labeling_callback => '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_multi_datasource:pool_connection_labeling_callback']
   ...
}

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

Back to overview of wls_multi_datasource

pool_connection_reserve_timeout_seconds

The number of seconds after which a call to reserve a connection from the connection pool will timeout. When set to 0, a call will never timeout. When set to -1, a call will timeout immediately.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   pool_connection_reserve_timeout_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_multi_datasource:pool_connection_reserve_timeout_seconds']
   ...
}

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

Back to overview of wls_multi_datasource

pool_count_of_refresh_failures_till_disable

Specifies the number of reconnect failures allowed before WebLogic Server disables a connection pool to minimize the delay in handling the connection request caused by a database failure. Zero means it is disabled.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   pool_count_of_refresh_failures_till_disable => '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_multi_datasource:pool_count_of_refresh_failures_till_disable']
   ...
}

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

Back to overview of wls_multi_datasource

pool_count_of_test_failures_till_flush

Specifies the number of test failures allowed before WebLogic Server closes all unused connections in a connection pool to minimize the delay caused by further database testing. Zero means it is disabled.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   pool_count_of_test_failures_till_flush => '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_multi_datasource:pool_count_of_test_failures_till_flush']
   ...
}

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

Back to overview of wls_multi_datasource

pool_credential_mapping_enabled

Enables Set Client ID on connection for the data source. When an application requests a database connection, WebLogic Server sets a light-weight client ID on the database connection. By default, it uses the credential mapping to map WebLogic Server user IDs to database user IDs. However, if use-database-credentials is set to true, then the credential mapping is not done and the ID is used directly as a database user ID. It is currently supported for IBM DB2 driver and Oracle thin driver. Support for this feature will be dropped in a future Oracle thin driver release. Oracle recommends using proxy authentication instead of this feature.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   pool_credential_mapping_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_multi_datasource:pool_credential_mapping_enabled']
   ...
}

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

Valid values are absent, 0, 1. Back to overview of wls_multi_datasource

pool_driver_interceptor

Specifies the absolute name of the application class used to intercept method calls to the JDBC driver. The application specified must implement the weblogic.jdbc.extensions.DriverInterceptor interface. Weblogic Server will invoke the preInvokeCallback(), postInvokeExceptionCallback(), and postInvokeCallback() methods of the registered application before and after invoking any method inside the JDBC driver. You can use this feature to profile JDBC driver usage and monitor: <ul> <li>Methods being executed</li> <li>Any exceptions thrown</li> <li>Time spent inside the driver executing methods</li> </ul>

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   pool_driver_interceptor => '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_multi_datasource:pool_driver_interceptor']
   ...
}

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

Back to overview of wls_multi_datasource

pool_fatal_error_codes

Specifies a comma-separated list of error codes that are treated as fatal errors. These errors include deployment errors that cause a server to fail to boot and connection errors that prevent a connection from being put back in the connection pool. This optional attribute is used to define fatal error codes, that when specified as the exception code within a SQLException (retrieved by sqlException.getErrorCode()), indicate that a fatal error has occurred and the connection is no longer usable. For Oracle databases the following fatal error codes are predefined within WLS and do not need to be placed in the configuration file: <ul><li>3113: “end-of-file on communication channel” </li> <li>3114: “not connected to ORACLE” </li> <li>1033: “ORACLE initialization or shutdown in progress” </li> <li>1034: “ORACLE not available” </li> <li>1089: “immediate shutdown in progress - no operations are permitted”</li> <li>1090: “shutdown in progress - connection is not permitted” </li> <li>17002: “I/O exception” </li> </ul>

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   pool_fatal_error_codes => '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_multi_datasource:pool_fatal_error_codes']
   ...
}

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

Back to overview of wls_multi_datasource

pool_highest_num_waiters

The maximum number of connection requests that can concurrently block threads while waiting to reserve a connection from the data source’s connection pool.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   pool_highest_num_waiters => '2147483647'
   ...
}

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

wls_setting{'domain':
   ...
  extra_properties => ['wls_multi_datasource:pool_highest_num_waiters']
   ...
}

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

Back to overview of wls_multi_datasource

pool_identity_based_connection_pooling_enabled

Enables identity-based-connection-pooling for the data source. When an application requests a database connection, WebLogic Server picks or creates a physical connection with requested DBMS identity based on a map of WebLogic user IDs and database IDs. You must also specify the map of WebLogic Server user IDs to database user IDs (credential mapping).

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   pool_identity_based_connection_pooling_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_multi_datasource:pool_identity_based_connection_pooling_enabled']
   ...
}

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

Valid values are absent, 0, 1. Back to overview of wls_multi_datasource

pool_ignore_in_use_connections_enabled

Enables the data source to be shutdown even if connections obtained from the pool are still in use.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   pool_ignore_in_use_connections_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_multi_datasource:pool_ignore_in_use_connections_enabled']
   ...
}

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

Valid values are absent, 0, 1. Back to overview of wls_multi_datasource

pool_inactive_connection_timeout_seconds

The number of inactive seconds on a reserved connection before WebLogic Server reclaims the connection and releases it back into the connection pool. You can use the Inactive Connection Timeout feature to reclaim leaked connections - connections that were not explicitly closed by the application. Note that this feature is not intended to be used in place of properly closing connections. When set to 0, the feature is disabled.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   pool_inactive_connection_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_multi_datasource:pool_inactive_connection_timeout_seconds']
   ...
}

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

Back to overview of wls_multi_datasource

pool_init_sql

SQL statement to execute that will initialize newly created physical database connections. Start the statement with SQL followed by a space. If the Init SQL value begins with "SQL ", then the rest of the string following that leading token will be taken as a literal SQL statement that will be used to initialize database connections. If the Init SQL value does not begin with “SQL “, the value will be treated as the name of a table and the following SQL statement will be used to initialize connections:
"select count(*) from InitSQL"
The table InitSQL must exist and be accessible to the database user for the connection. Most database servers optimize this SQL to avoid a table scan, but it is still a good idea to set InitSQL to the name of a table that is known to have few rows, or even no rows.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   pool_init_sql => '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_multi_datasource:pool_init_sql']
   ...
}

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

Back to overview of wls_multi_datasource

pool_initial_capacity

The number of physical connections to create when creating the connection pool in the data source. If unable to create this number of connections, creation of the data source will fail.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   pool_initial_capacity => '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_multi_datasource:pool_initial_capacity']
   ...
}

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

Back to overview of wls_multi_datasource

pool_jdbcxa_debug_level

Specifies level of JDBC debugging for XA drivers, where larger values in the range provide more debugging information.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   pool_jdbcxa_debug_level => '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_multi_datasource:pool_jdbcxa_debug_level']
   ...
}

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

Back to overview of wls_multi_datasource

pool_login_delay_seconds

The number of seconds to delay before creating each physical database connection. This delay supports database servers that cannot handle multiple connection requests in rapid succession. The delay takes place both during initial data source creation and during the lifetime of the data source whenever a physical database connection is created.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   pool_login_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_multi_datasource:pool_login_delay_seconds']
   ...
}

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

Back to overview of wls_multi_datasource

pool_max_capacity

The maximum number of physical connections that this connection pool can contain.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   pool_max_capacity => '15'
   ...
}

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

wls_setting{'domain':
   ...
  extra_properties => ['wls_multi_datasource:pool_max_capacity']
   ...
}

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

Back to overview of wls_multi_datasource

pool_min_capacity

The minimum number of physical connections that this connection pool can contain after it is initialized.

  • Default: InitialCapacity
  • Used only for connection pool shrinking calculations.
  • For compatibility, InitialCapacity is used if MinCapacity is not configured.
  • Once a data source has gone through a suspend/resume, the larger value of either MinCapacity or InitialCapacity is used.

An example on how to use this:

wls_datasource {a_wls_datasource :
   ...
   pool_min_capacity => '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_datasource:pool_min_capacity']
   ...
}

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

Back to overview of wls_multi_datasource

pool_pinned_to_thread

Enables an option to improve performance by enabling execute threads to keep a pooled database connection even after the application closes the logical connection. When enabled: <ul><li> WebLogic Server pins a database connection from the connection pool to an execution thread the first time an application uses the thread to reserve a connection. When the application finishes using the connection and calls connection.close(), WebLogic Server keeps the connection with the execute thread and does not return it to the connection pool. When an application subsequently requests a connection using the same execute thread, WebLogic Server provides the connection already reserved by the thread.</li> <li>There is no locking contention on the connection pool that occurs when multiple threads attempt to reserve a connection at the same time. There is no contention for threads that attempt to reserve the same connection from a limited number of database connections.</li> <li>If an application concurrently reserves more than one connection from the connection pool using the same execute thread, WebLogic Server creates additional database connections and pins them to the thread.</li> </ul>

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   pool_pinned_to_thread => '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_multi_datasource:pool_pinned_to_thread']
   ...
}

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

Valid values are absent, 0, 1. Back to overview of wls_multi_datasource

pool_profile_connection_leak_timeout_seconds

The number of seconds that a JDBC connection needs to be held by an application before triggering a connection leak diagnostic profiling record. When set to 0, the timeout is disabled. This attribute only applies when the connection leak diagnostic profiling option is enabled.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   pool_profile_connection_leak_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_multi_datasource:pool_profile_connection_leak_timeout_seconds']
   ...
}

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

Back to overview of wls_multi_datasource

pool_profile_harvest_frequency_seconds

The number of seconds between when WebLogic Server harvests profile data. When set to 0, harvesting of data is disabled.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   pool_profile_harvest_frequency_seconds => '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_multi_datasource:pool_profile_harvest_frequency_seconds']
   ...
}

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

Back to overview of wls_multi_datasource

pool_profile_type

Specifies that type of profile data to be collected for the JDBC subsystem. You can specify combinations of the following profile types: <ul> <li>weblogic.jdbc.common.internal.JDBCConstants.PROFILE_TYPE_CONN_USAGE - Profile threads currently using connections from the pool of connections in the data source. </li> <li>weblogic.jdbc.common.internal.JDBCConstants.PROFILE_TYPE_CONN_RESV_WAIT - Profile threads currently waiting to reserve a connection from the data source.</li> <li>weblogic.jdbc.common.internal.JDBCConstants.PROFILE_TYPE_CONN_LEAK - Profile threads that have reserved a connection from the data source and the connection leaked (was not properly returned to the pool of connections).</li> <li>weblogic.jdbc.common.internal.JDBCConstants.PROFILE_TYPE_CONN_RESV_FAIL - Profile threads that attempt to reserve a connection from the data source but fail.</li> <li>weblogic.jdbc.common.internal.JDBCConstants.PROFILE_TYPE_STMT_CACHE_ENTRY - Profile prepared and callable statements added to the statement cache, and profile the threads that originated the cached statements.</li> <li>weblogic.jdbc.common.internal.JDBCConstants.PROFILE_TYPE_STMT_USAGE - Profile threads currently executing SQL statements from the statement cache.</li> <li>weblogic.jdbc.common.internal.JDBCConstants.PROFILE_TYPE_CONN_LAST_USAGE - Profile the previous thread that last used the connection. This information is useful when debugging problems with connections infected with pending transactions that cause subsequent XA operations on the connections to fail.</li> <li>weblogic.jdbc.common.internal.JDBCConstants.PROFILE_TYPE_CONN_MT_USAGE - Profile threads that erroneously use a connection previously obtained by a different thread.</li> <li>weblogic.jdbc.common.internal.JDBCConstants.PROFILE_TYPE_NONE - Disable profiling for the data source.</li> <li>weblogic.jdbc.common.internal.JDBCConstants.PROFILE_TYPE_ALL - Enable all profile types for the data source.</li> </ul>

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   pool_profile_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_multi_datasource:pool_profile_type']
   ...
}

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

Back to overview of wls_multi_datasource

pool_remove_infected_connections

Specifies whether a connection will be removed from the connection pool after the application uses the underlying vendor connection object. If you disable removing infected connections, you must make sure that the database connection is suitable for reuse by other applications. When set to true (the default), the physical connection is not returned to the connection pool after the application closes the logical connection. Instead, the physical connection is closed and recreated. When set to false, when the application closes the logical connection, the physical connection is returned to the connection pool and can be reused by the application or by another application.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   pool_remove_infected_connections => '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_multi_datasource:pool_remove_infected_connections']
   ...
}

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

Valid values are absent, 0, 1. Back to overview of wls_multi_datasource

pool_seconds_to_trust_an_idle_pool_connection

The number of seconds within a connection use that WebLogic Server trusts that the connection is still viable and will skip the connection test, either before delivering it to an application or during the periodic connection testing process. This option is an optimization that minimizes the performance impact of connection testing, especially during heavy traffic.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   pool_seconds_to_trust_an_idle_pool_connection => '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_multi_datasource:pool_seconds_to_trust_an_idle_pool_connection']
   ...
}

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

Back to overview of wls_multi_datasource

pool_shrink_frequency_seconds

The number of seconds to wait before shrinking a connection pool that has incrementally increased to meet demand. When set to 0, shrinking is disabled.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   pool_shrink_frequency_seconds => '900'
   ...
}

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

wls_setting{'domain':
   ...
  extra_properties => ['wls_multi_datasource:pool_shrink_frequency_seconds']
   ...
}

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

Back to overview of wls_multi_datasource

pool_statement_cache_size

The number of prepared and callable statements stored in the cache. (This may increase server performance.) WebLogic Server can reuse statements in the cache without reloading the statements, which can increase server performance. Each connection in the connection pool has its own cache of statements. Setting the size of the statement cache to 0 turns off statement caching.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   pool_statement_cache_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_multi_datasource:pool_statement_cache_size']
   ...
}

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

Back to overview of wls_multi_datasource

pool_statement_cache_type

The algorithm used for maintaining the prepared statements stored in the statement cache. Options are: <ul> <li>LRU - when a new prepared or callable statement is used, the least recently used statement is replaced in the cache.</li> <li>FIXED - the first fixed number of prepared and callable statements are cached.</li> </ul>

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   pool_statement_cache_type => 'LRU'
   ...
}

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

wls_setting{'domain':
   ...
  extra_properties => ['wls_multi_datasource:pool_statement_cache_type']
   ...
}

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

Back to overview of wls_multi_datasource

pool_statement_timeout

The time after which a statement currently being executed will time out. StatementTimeout relies on underlying JDBC driver support. WebLogic Server passes the time specified to the JDBC driver using the java.sql.Statement.setQueryTimeout() method. If your JDBC driver does not support this method, it may throw an exception and the timeout value is ignored. A value of -1 disables this feature. A value of 0 means that statements will not time out.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   pool_statement_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_multi_datasource:pool_statement_timeout']
   ...
}

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

Back to overview of wls_multi_datasource

pool_test_connections_on_reserve

Enables WebLogic Server to test a connection before giving it to a client. (Requires that you specify a Test Table Name.) The test adds a small delay in serving the client’s request for a connection from the pool, but ensures that the client receives a viable connection.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   pool_test_connections_on_reserve => '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_multi_datasource:pool_test_connections_on_reserve']
   ...
}

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

Valid values are absent, 0, 1. Back to overview of wls_multi_datasource

pool_test_frequency_seconds

The number of seconds a WebLogic Server instance waits between attempts when testing unused connections. (Requires that you specify a Test Table Name.) Connections that fail the test are closed and reopened to re-establish a valid physical connection. If the test fails again, the connection is closed. In the context of multi data sources, this attribute controls the frequency at which WebLogic Server checks the health of data sources it had previously marked as unhealthy. When set to 0, the feature is disabled.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   pool_test_frequency_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_multi_datasource:pool_test_frequency_seconds']
   ...
}

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

Back to overview of wls_multi_datasource

pool_test_table_name

The name of the database table to use when testing physical database connections. This name is required when you specify a Test Frequency and enable Test Reserved Connections. The default SQL code used to test a connection is select count(*) from TestTableName Most database servers optimize this SQL to avoid a table scan, but it is still a good idea to set the Test Table Name to the name of a table that is known to have few rows, or even no rows. If the Test Table Name begins with SQL, then the rest of the string following that leading token will be taken as a literal SQL statement that will be used to test connections instead of the standard query. For example: SQL BEGIN; Null; END; For an Oracle database, you can reduce the overhead of connection testing by setting Test Table Name to SQL PINGDATABASE which uses the pingDatabase() method to test the Oracle connection. For any JDBC 4.0 database, it is possible to use “SQL ISVALID” to use the isValid() method on the connection.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   pool_test_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_multi_datasource:pool_test_table_name']
   ...
}

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

Back to overview of wls_multi_datasource

pool_wrap_jdbc

By default, SQL objects for CallableStatement, PreparedStatement, ResultSet, Statement, and DatabaseMetaData are wrapped with a WebLogic wrapper. Wrapping allows features like debugging and connection usage to be performed by the server. When false, wrapping is disabled. This improves performance, in some cases significantly, and allows for the application to use the native driver objects directly. A value of false also disables data type wrapping.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   pool_wrap_jdbc => '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_multi_datasource:pool_wrap_jdbc']
   ...
}

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

Valid values are absent, 0, 1. Back to overview of wls_multi_datasource

pool_wrap_types

By default, data type objects for Array, Blob, Clob, NClob, Ref, SQLXML, and Struct, plus ParameterMetaData and ResultSetMetaData objects are wrapped with a WebLogic wrapper. This allows for features like debugging and connection usage to be done by the server. The wrapping can be turned off by setting this value to false. This improves performance, in some cases significantly, and allows for the application to use the native driver objects directly.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   pool_wrap_types => '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_multi_datasource:pool_wrap_types']
   ...
}

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

Valid values are absent, 0, 1. Back to overview of wls_multi_datasource

provider

The specific backend to use for this wls_multi_datasource resource. You will seldom need to specify this — Puppet will usually discover the appropriate provider for your platform.Available providers are:

simple
Manage a multi datasource in an WebLogic domain via regular WLST

Back to overview of wls_multi_datasource

source_path

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   source_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_multi_datasource:source_path']
   ...
}

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

Back to overview of wls_multi_datasource

tags

Return all tags on this Configuration MBean

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   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_multi_datasource:tags']
   ...
}

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

Back to overview of wls_multi_datasource

target

An array of target names.

The array of targets for this resource. A target can be a WebLogic Server, a WebLogic cluster, or a JMS Server. When specifying a target, you’ll also have to specify targettype. Here is an example on how you can specify a target.

..{ 'aResource':
  ...
  target     => ['myServer','myCluster'],
  targettype => ['Server','Cluster'],
  ...
}

here is an example on specifying the target and targettype for a regular WebLogic cluster:

wls_cluster{ 'aCluster':
  ...
  target     => ['myServer','myCluster'],
  targettype => ['Server','Cluster'],
  ...
}

Back to overview of wls_multi_datasource

targettype

An array of target types.

The array of target types for this resource. A target can be a WebLogic Server, a WebLogic cluster, or a JMS Server. When specifying a targettype, you’ll also have to specify a target. Here is an example on how you can specify a target.

...{ 'aResource':
  ...
  target     => ['myServer','myCluster'],
  targettype => ['Server','Cluster'],
  ...
}

here is an example on specifying the target and targettype for a regular WebLogic cluster:

wls_cluster{ 'aCluster':
  ...
  target     => ['myServer','myCluster'],
  targettype => ['Server','Cluster'],
  ...
}

Back to overview of wls_multi_datasource

testfrequency

The number of seconds a WebLogic Server instance waits between attempts when testing unused connections.

Back to overview of wls_multi_datasource

xa_end_only_once

Specifies that XAResource.end() is called only once for each pending XAResource.start(). This option prevents the XA driver from calling XAResource.end(TMSUSPEND) and XAResource.end(TMSUCCESS) successively. Only applies to data sources that use an XA driver. Use this setting to work around specific problems with JDBC XA drivers.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   xa_end_only_once => '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_multi_datasource:xa_end_only_once']
   ...
}

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

Valid values are absent, 0, 1. Back to overview of wls_multi_datasource

xa_keep_logical_conn_open_on_release

Enables WebLogic Server to keep the logical JDBC connection open for a global transaction when the physical XA connection is returned to the connection pool. Select this option if the XA driver used to create database connections or the DBMS requires that a logical JDBC connection be kept open while transaction processing continues (although the physical XA connection can be returned to the connection pool). Only applies to data sources that use an XA driver. Use this setting to work around specific problems with JDBC XA drivers.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   xa_keep_logical_conn_open_on_release => '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_multi_datasource:xa_keep_logical_conn_open_on_release']
   ...
}

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

Valid values are absent, 0, 1. Back to overview of wls_multi_datasource

xa_keep_xa_conn_till_tx_complete

Enables WebLogic Server to associate the same XA database connection from the connection pool with a global transaction until the transaction completes. Only applies to connection pools that use an XA driver. Use this setting to work around specific problems with JDBC XA drivers.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   xa_keep_xa_conn_till_tx_complete => '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_multi_datasource:xa_keep_xa_conn_till_tx_complete']
   ...
}

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

Valid values are absent, 0, 1. Back to overview of wls_multi_datasource

xa_need_tx_ctx_on_close

Specifies whether the XA driver requires a distributed transaction context when closing various JDBC objects (result sets, statements, connections, and so forth). Only applies to connection pools that use an XA driver. When enabled, SQL exceptions that are thrown while closing the JDBC objects without a transaction context will be suppressed. Use this setting to work around specific problems with JDBC XA drivers.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   xa_need_tx_ctx_on_close => '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_multi_datasource:xa_need_tx_ctx_on_close']
   ...
}

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

Valid values are absent, 0, 1. Back to overview of wls_multi_datasource

xa_new_xa_conn_for_commit

Specifies that a dedicated XA connection is used for commit and rollback processing for a global transaction. Only applies to data sources that use an XA driver. Use this setting to work around specific problems with JDBC XA drivers.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   xa_new_xa_conn_for_commit => '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_multi_datasource:xa_new_xa_conn_for_commit']
   ...
}

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

Valid values are absent, 0, 1. Back to overview of wls_multi_datasource

xa_recover_only_once

Specifies that the transaction manager calls recover on the resource only once. Only applies to data sources that use an XA driver. Use this setting to work around specific problems with JDBC XA drivers.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   xa_recover_only_once => '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_multi_datasource:xa_recover_only_once']
   ...
}

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

Valid values are absent, 0, 1. Back to overview of wls_multi_datasource

xa_resource_health_monitoring

Enables JTA resource health monitoring for an XA data source. When enabled, if an XA resource fails to respond to an XA call within the period specified in MaxXACallMillis, WebLogic Server marks the data source as unhealthy and blocks any further calls to the resource. This property applies to XA data sources only, and is ignored for data sources that use a non-XA driver.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   xa_resource_health_monitoring => '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_multi_datasource:xa_resource_health_monitoring']
   ...
}

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

Valid values are absent, 0, 1. Back to overview of wls_multi_datasource

xa_retry_duration_seconds

Determines the duration in seconds for which the transaction manager will perform recover operations on the resource. A value of zero indicates that no retries will be performed.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   xa_retry_duration_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_multi_datasource:xa_retry_duration_seconds']
   ...
}

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

Back to overview of wls_multi_datasource

xa_retry_interval_seconds

The number of seconds between XA retry operations if XARetryDurationSeconds is set to a positive value.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   xa_retry_interval_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_multi_datasource:xa_retry_interval_seconds']
   ...
}

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

Back to overview of wls_multi_datasource

xa_rollback_local_tx_upon_conn_close

Enables WebLogic Server to call rollback() on the connection before returning the connection to the connection pool. Enabling this attribute will have a performance impact as the rollback call requires communication with the database server. This option is deprecated. Its value is currently ignored.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   xa_rollback_local_tx_upon_conn_close => '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_multi_datasource:xa_rollback_local_tx_upon_conn_close']
   ...
}

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

Valid values are absent, 0, 1. Back to overview of wls_multi_datasource

xa_set_transaction_timeout

Enables WebLogic Server to set a transaction branch timeout based on the value for XaTransactionTimeout. When enabled, the WebLogic Server Transaction Manager calls XAResource.setTransactionTimeout() before calling XAResource.start, and passes either the XA Transaction Timeout value or the global transaction timeout. You may want to set a transaction branch timeout if you have long-running transactions that exceed the default timeout value on the XA resource. Note: To use this feature, the resource manager (typically, the JDBC driver) must support the javax.transaction.xa.XAResource.setTransactionTimeout() method.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   xa_set_transaction_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_multi_datasource:xa_set_transaction_timeout']
   ...
}

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

Valid values are absent, 0, 1. Back to overview of wls_multi_datasource

xa_transaction_timeout

The number of seconds to set as the transaction branch timeout. If set, this value is passed as the transaction timeout value in the XAResource.setTransactionTimeout() call on the XA resource manager, typically the JDBC driver. When this value is set to 0, the WebLogic Server Transaction Manager passes the global WebLogic Server transaction timeout in seconds in the method. If set, this value should be greater than or equal to the global WebLogic Server transaction timeout. Note: You must enable XaSetTransactionTimeout to enable setting the transaction branch timeout.

An example on how to use this:

wls_multi_datasource {a_wls_multi_datasource :
   ...
   xa_transaction_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_multi_datasource:xa_transaction_timeout']
   ...
}

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

Back to overview of wls_multi_datasource