InfoCenter Home >
3: Migration overview >
3.3: Migrating APIs and specifications >
3.3.10: Migrating to supported XML configuration

3.3.10: Migrating to supported XML configuration

The composition of almost all of the existing elements has changed. In some cases, these pre-existing elements have children of a different type. In other cases, these pre-existing elements have a completely new set of child elements. For details, see xmlconfig.dtd.

Changes for some elements are summarized in the following table:

Element Changed syntax
container No longer exists; attributes of <container> are now part of <application-server>
jdbc-driver Now supports <install-info/> and <uninstall-info/> elements (optional)
model No longer exists; <model> has been replaced with <server-group>
session-manager This configuration is now part of <application-server>
data-source <data-source> is now contained in <jdbc-driver> and is no longer a direct child of <websphere-sa-config>

Changes from Version 3.x

For programmatic access:

  • The XMLConfig constructor now throws NamingException and InvalidArgumentException.
  • The XMLConfig tools now supports variable substitution and variable Hashtable setter.

The XMLConfig command line now supports the -substitute option for variable replacement.

Go to previous article: Migrating to supported transaction support Go to next article: Switching administrative databases

 

 
Go to previous article: Migrating to supported transaction support Go to next article: Switching administrative databases