Difference between revisions of "GVDataSources"
Line 159: | Line 159: | ||
Might contain the mbean element. | Might contain the mbean element. | ||
+ | |||
+ | ===local-tx-datasource=== | ||
+ | |||
+ | Specify a jca-jdbc non-XADatasource (local) wrapper, using local transactions. | ||
+ | The local-tx-datasource Element is used by: GVDataSources. | ||
+ | |||
+ | Its subelements are: | ||
+ | * jndi-name | ||
+ | * use-java-context | ||
+ | * connection-url | ||
+ | * driver-class | ||
+ | * transaction-isolation | ||
+ | * connection-property | ||
+ | * user-name | ||
+ | * password | ||
+ | * (application-managed-security | security-domain | security-domain-and-application) | ||
+ | * min-pool-size | ||
+ | * max-pool-size | ||
+ | * blocking-timeout-millis | ||
+ | * idle-timeout-minutes | ||
+ | * no-tx-separate-pools | ||
+ | * new-connection-sql | ||
+ | * check-valid-connection-sql | ||
+ | * valid-connection-checker-class-name | ||
+ | * exception-sorter-class-name | ||
+ | * track-statements | ||
+ | * prepared-statement-cache-size | ||
+ | * depends | ||
+ | * type-mapping |
Revision as of 16:12, 13 February 2012
Contents
Description
GVDataSources GreenVulcano® ESB element is the root of the jdbc datasource configuration.
VulCon Configuration
GVDataSources element is present in the Adapter view and used by GVAdapters.
The following table shows the GVDataSources element's attributes:
Attribute | Type | Description |
---|---|---|
type | fixed | This attribute must assume the value module. |
name | fixed | This attribute must assume the value DATASOURCES. |
Might contain one of the following elements:
mbean
The mbean element defines a JBoss MBean service. This includes the mbean class, attributes and dependencies.
The mbean Element is used by: depends, depends-list-element and GVDataSources.
The following table shows the mbean element's attributes:
Attribute | Type | Description |
---|---|---|
code | required | The code attributes gives the fully qualified name of the MBean implementation class. |
name | required | The name attribute gives the JMX ObjectName string to use when registering the MBean.
This must be a unique and valid JMX name. |
interface | optional | The optional interface attribute gives the full qualified name of the class uses to construct the management interface of the mbean.
In absence of it an interface with the name ending by MBean will be looked in the implementation class. When used this interface is defined explicitely. |
Its subelements are:
constructor
The constructor element defines a non-default constructor to use when instantiating the mbean.
The constructor Element is used by: mbean.
Contains the subelemets: arg
arg
The arg element specifies the constructor arguments in the order of the ctor signature.
The following tables show the arg element's attributes:
Attribute | Type | Description |
---|---|---|
type | optional | The type attribute gives the type of the argument as defined in the ctor signature.
If not defined java.lang.String is assumed. The attribute's value can't be null. |
value | required | The value attribute provides the string representation of the ctor argument.
It is converted from a string to type using Java PropertyEditor or a ctor taking a single string as its argument. The attribute's value can't be null. |
xmbean
The xmbean element specifies a nested JBoss XMBean descriptor fragment.
Its supported content model is the same as the mbean element of the jboss_xmbean_1_0.dtd Ex: <xmbean> ... </xmbean>
The element value can't be null.
attribute
The attribute element specifies the initial value for a management attribute of the enclosing mbean.
Typically the value of the attribute element is the string representation of the attribute, but it can be an arbitrary xml fragment that is parsed by the mbean.
The following table shows the attribute element's attributes:
Attribute | Type | Description |
---|---|---|
name | required | The required name attribute gives the name of the attribute.
This is the name exposed by the mbean to the MBeanServer for the attribute. The attribute's value can't be null. |
replace | optional | The optional replace attribute indicates whether references of the form ${x} in the attribute element content should be replaced with the corresponding System.getProperty(x) value.
The attribute's default value is: true. |
trim | optional | The optional trim attribute specifies whether the attribute element content should be trimmed of whitespace.
The attribute's default value is: true. |
attributeClass | optional | The attributeClass attribute specifies the type of object that should be created.
This is needed for non-concrete attribute types like interfaces and abstract classes. The attribute's value can't be null. |
serialDataType | optional | The serialDataType defines how the content of the attribute element is interpreted by the ServiceConfigurator.
The possible values are:
PropertyEditor registered for the attribute type.
The attribute's default value is: text. |
depends
The depends element specifies the JMX ObjectName string of a service that the connection manager services depend on or a JMX ObjectName string for a mbean on which the enclosing mbean depends.
The depends Element is used by: local-tx-datasource, mbean, no-tx-datasource, xa-datasource.
The following table shows the depends element's attributes:
Attribute | Type | Description |
---|---|---|
optional-attribute-name | optional | The optional-attribute-name attribute specifies the attribute name which should be populated with the JMX ObjectName of the depends element.
This allows an mbean to have access to the name of the mbean on which it depends. The attribute's value can't be null. |
proxy-type | optional | The proxy-type attribute specifies the interface name that should be exposed on an MBeanProxy pointing at the dependent MBean specified by the JMX ObjectName.
The special value proxy-type="attribute" will use the class declared in the MBeanAttributeInfo as the interface for MBeanProxy. The attribute's value can't be null. |
depends-list
The depends-list element specifies a series of JMX ObjectName strings for a mbeans on which the enclosing mbean depends. This is done using
The following table shows the depends-list element's attributes:
Attribute | Type | Description |
---|---|---|
optional-attribute-name | optional | The optional-attribute-name attribute specifies the attribute name which should be populated with the JMX ObjectName[] array of the depends-list elements.
This allows an mbean to have access to the names of the mbean on which it depends. The attribute's value can't be null. |
Contains the depends-list-element elements. Might contain the mbean element.
depends-list-element
The depends-list-element element specifies a JMX ObjectName string for a mbean on which the enclosing mbean depends. The depends-list-element Element is used by: depends-list.
Might contain the mbean element.
local-tx-datasource
Specify a jca-jdbc non-XADatasource (local) wrapper, using local transactions. The local-tx-datasource Element is used by: GVDataSources.
Its subelements are:
- jndi-name
- use-java-context
- connection-url
- driver-class
- transaction-isolation
- connection-property
- user-name
- password
- (application-managed-security | security-domain | security-domain-and-application)
- min-pool-size
- max-pool-size
- blocking-timeout-millis
- idle-timeout-minutes
- no-tx-separate-pools
- new-connection-sql
- check-valid-connection-sql
- valid-connection-checker-class-name
- exception-sorter-class-name
- track-statements
- prepared-statement-cache-size
- depends
- type-mapping