WAS v8.5 > Reference > Developer detailed usage information

Configuration differences between full and Liberty profile

• Data source properties with different names...

  Liberty profile	Full profile
  ifxIFX_LOCK_MODE_WAIT	informixLockModeWait
  supplementalJDBCTrace	supplementalTrace

• Data source properties with different values...

  	Liberty default	Full default
  beginTranForResultSetScrollingAPIs	true	false
  beginTranForVendorAPIs	true	false
  connectionSharing	MatchOriginalRequest	1
  statementCacheSize	10

  Both Liberty and full profiles can be matched based on either MatchOriginalRequest or MatchCurrentState.

  In the full profile individual connection properties can be matched based on the current state of the connection.

  0	match all properties based on the original connection request
  -1	match all properties based on the current state of the connection.
  1	Default. The isolation level is matched based on the current state of the connection and all other properties are matched based on the original connection request.

• Time duration properties can optionally be specified with units in the Liberty profile. For example,

  <dataSource id="informix" jndiName="jdbc/informix" queryTimeout="5m"  ...>     < properties.informix ifxIFX_LOCK_MODE_WAIT="120s" .../> </dataSource>

  Omitting the units in the Liberty profile is equivalent to the default units used in the full profile.

• Configuration for JDBC drivers

  • In the Liberty profile, we can configure different jdbcDriver elements for XA capable and non-XA capable data source implementation classes.

    Alternatively, we can use a single jdbcDriver element for both.

    Define multiple jdbcDriver elements does not cause different class loaders to be used. Liberty jdbcDriver elements always use the class loader of the shared library with which they are configured.

  • In the full profile, a JDBC provider is defined to point to the JDBC driver JARs, compressed files, and native files.

    Define separate JDBC providers for XA capable and non-XA capable data source implementation classes.

  For some of the commonly used JDBC drivers, the Liberty profile infers the data source implementation class names based on the names the driver JARs. Therefore, we can omit the implementation class names. For example:

  <jdbcDriver id="Derby" libraryRef="DerbyLib"/> 
  < library id="DerbyLib"> 
      < fileset dir="C:/Drivers/derby" 
               includes="derby.jar" /> 
  </library>

  Use the optional properties of the default implementation classes to override these classes such as javax.sql.DataSource, javax.sql.ConnectionPoolDataSource, and javax.sql.XADataSource.

  The following example shows how to override the default javax.sql.XADataSource and javax.sql.ConnectionPoolDataSource implementations the Liberty profile selects

  <jdbcDriver id="Derby" libraryRef="DerbyLib" 
        javax.sql.XADataSource="org.apache.derby.jdbc.EmbeddedXADataSource" 
        javax.sql.ConnectionPoolDataSource="org.apache.derby.jdbc.EmbeddedConnectionPoolDataSource"/>    < library id="DerbyLib"> 
        < fileset dir="C:/Drivers/derby" includes="derby.jar" />    </library>

  See Liberty profile: Configuration elements in server.xml for more information about the jdbcDriver element.

Parent topic: Migrate data access applications to the Liberty profile

|