InfoCenter Home >
6: Administer applications >
6.6: Tools and resources quick reference >
6.6.0: About user assistance >
6.6.0.2: Command line administration >
6.6.0.2.1: XMLConfig command line interface for XML configuration >
6.6.0.2.1.3: XMLConfig - Using the tool programmatically

6.6.0.2.1.3: XMLConfig - Using the tool programmatically

The XMLConfig class is structured so that you can use it programmatically to retrieve information as a TXDocument or Element. The import/export facility can thus be included in a Java program, as well as being operated from a command line.

Creating platform-neutral configurations

For import and partial export operations, a variable substitution operation is performed on the input XML document, allowing you to create platform-neutral XML documents. These variables are available:

$server_root$
Replace with the WebSphere Application Server installation directory, such as C:\WebSphere\AppServer on Windows NT.
$psep$
Replace with the path separator as specified by the operating system JDK.
  • On Windows NT, it is ; (semicolon)
  • On AIX and Solaris, it is : (colon)
$dsep$
Replace with the directory separator as specified by the operating system JDK.
  • On Windows NT, it is \ (backward slash)
  • On AIX and Solaris, it is / (forward slash)

Security XML configurations

When configuring security with XML, you should be familiar with the following two factors:

  1. Passwords and variable substitution
  2. Searches of the user registry

Javadoc for the tool

It is recommended that you refer to the Javadoc for the latest programmatic use of XMLConfig, and refer to the exported xml for the sample xml for repository objects.

Javadoc for com.ibm.websphere.xmlconfig class and all of the related object classes resides in the apidocs directory:

<installation_root>\web\apidocs\package and class name

See the package summary file for a list of the class names, such as ApplicationServerConfig. The Javadoc is labeled by the class name preceded by the package name, com.ibm.websphere.

Go to previous article: XMLConfig grammar Go to next article: XMLConfig - Passwords and variable substitution

 

 
Go to previous article: XMLConfig grammar Go to next article: XMLConfig - Passwords and variable substitution