IBM Integration Bus, Version 9.0.0.8 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

JDBCProviders configurable service

Select the objects and properties that you want to change for the JDBCProviders configurable service.

For JDBCProviders configurable services, you must stop and start the integration server for a change of property value to take effect.

Supplied configurable services that are created for each broker	Properties for each configurable service that is defined	Description of properties
DB2 Informix Informix_With_Date_Format Microsoft_SQL_Server Oracle Sybase_JConnect6_05	connectionUrlFormat	A pattern that represents the connection URL definition, which is specific to a particular database type. For example, the pattern for DB2® is defined with the following fixed content: `jdbc:db2://[serverName]:[portNumber]/[databaseName] :user=[user];password=[password];` Do not use the mqsichangeproperties command to change the pattern itself; changes made to the pattern might cause unpredictable results. This situation is due to the behavior at run time when the broker substitutes any parts of the URL found between square brackets (such as `[serverName]` or `[portNumber]`) with the corresponding values found in a configurable service property that matches the name of that URL part. The connectionUrlFormat `[user]` and `[password]` parameters are a special case. These parameters are substituted with user identity and encrypted password values derived using the securityIdentity property.
	connectionUrlFormatAttr1 connectionUrlFormatAttr2 connectionUrlFormatAttr3 connectionUrlFormatAttr4 connectionUrlFormatAttr5	If the specified URL format contains non-standard JDBC data source properties, such as a server identifier, specify one of five general-purpose connection attributes to define these additional properties. For example, if `connectionURLFormat = jdbc:oracle:thin:[user]/[password]@[serverName]:[portNumber]:[connectionUrlFormatAttr1]`, connectionUrlFormatAttr1 must contain an Oracle server identifier, which you must supply by defining the value for the property connectionUrlFormatAttr1 on the mqsicreateconfigurableservice or mqsichangeproperties command. The integration node can then substitute all the required values into the required pattern.
	databaseName	The name of the database to which the data source entry enables connections; for example, employees.
	databaseSchemaNames	The name of the database schema to include in SQL statements created by message flow nodes. This property is used only by the Mapping node, and only when calling a graphical data map that contains a database transform. Valid values are: An empty string. This is the default value, and indicates that your nodes do not include a database schema name in the SQL statements that they create. The name of a single database schema. Your nodes include this schema name in all SQL statements that they create. One or more database table and database schema name pairs, in the form: `tableA:schema01;tableB:schema02` . If a table has a `table`:`schema` name pair defined in this way, your nodes include the corresponding database schema name in the SQL statements that they create. If a table does not have a `table`:`schema` pair defined, your nodes do not include a database schema name in the SQL statements that they create. The name of a database schema to use as a default, followed by one or more database table and database schema name pairs, in the form: `defaultschema;tableA:schema01;tableB:schema02` For tables that have a `table`:`schema` pair, your nodes include the corresponding database schema name in the SQL statements that they create. If a table does not have a `table`:`schema` pair defined, your nodes include the default database schema name in the SQL statements that it creates. The string `useProvidedSchemaNames`, to use the schema name provided in the map (the schema name used at design time).
	databaseType	The database type, for example, DB2.
	databaseVersion	The database version; for example, 9.1.
	description	An optional property to describe the data source definition.
	environmentParms	DB2 and Informix® only. An optional property specifying a list of data source properties of the form `name=value` each separated by a semicolon.
	jarsURL	The local directory path on the system on which the integration node is running, where the JAR file that contains the type 4 driver class is located.
	portNumber	The port number on which the database server is listening; for example, 50000.
	securityIdentity	A unique security key to perform a second broker registry lookup to find an entry under the broker DSN entries, which store the encrypted password for the user identity for connection logon authentication on their associated host system; for example, jdbc::mysecurityIdentity. Use the mqsisetdbparms command to create a DSN entry, as described in Securing database connections. At run time, the broker uses the security credentials to substitute for the strings `[user]` and `[password]` that might occur in the connectionUrlFormat, connectionUrlFormatAttr or environmentParms properties. There are cases where an alternative authentication method is required. For instance, when a database server takes the user identity and password from an SSL certificate to obtain a secure JDBC connection. In this case, the security key must be set to `jdbc::none`, which disables connection logon authentication.
	serverName	The name of the server; for example, `host1`.
	type4DatasourceClassName	The name of the JDBC type 4 data source class name that is used to establish a type 4 connection to a remote database and for coordinated transaction support; for example, `com.ibm.db2.jcc.DB2XADataSource`.
	type4DriverClassName	The name of the JDBC driver class name that is used to establish a connection; for example, `com.ibm.db2.jcc.DB2Driver`.
	jdbcProviderXASupport	This property is optional. Setting this property to true, indicates that the selected JDBC provider supports XA coordinated transactions, and the database server is enabled to use the XA transaction protocol. Setting this property to false, indicates that the selected JDBC provider either does not support XA coordinated transactions, or the database server is not enabled to use the XA transaction protocol. The default value for this property is true. If you set this property to true, and the selected JDBC provider does not support XA transactions, an exception is raised. If you set this property to false, but the Coordinated Transaction message flow property is selected, an exception is raised.
	maxConnectionPoolSize	Connection pooling is switched on for a JDBCProviders configurable service when the value for this attribute is non-zero and within the range 1 - 100000. The connection pool limits the number of connections for that configurable service for each integration server. Note that, after you have set a value for this attribute, you must stop and restart the integration server for the changes to take effect. The default value for this attribute is zero and this value turns connection pooling off for the integration server. All message flows in an integration server that use the same JDBCProviders configurable service share the same connection pool. Multiple JDBCProviders configurable services that refer to the same database have their own pool of independently controlled connections to that database

bn28734_.htm |

Last updated Friday, 21 July 2017