Package com.ibm.datapower.wamt

This package contains classes that are used by the clientAPI and amp packages.

See:
          Description

Class Summary
AbstractFactory A common implementation of a class factory, it can be extended to create specific factories.
AbstractPackageInfo Get the SCM (source code management, i.e., CVS metadata) information about all the classes in a package for debug purposes.
ComponentInfo A utility to get the SCM information (i.e., CVS revision) of all classes in all packages for this component (IBM WebSphere Appliance Management Toolkit) for debug purposes.
Constants Constants that are applicable across all of the IBM WebSphere Appliance Management Toolkit.
Credential The Credential provides data for access control to the Repository and its contents.
DeviceLogger A simple trace logger that accepts trace entries via HTTP and logs to the appropriate (specified) logger.
DeviceLogger_ClientThread A thread that will read events from an accepted socket and log them.
DeviceType This class provides a set of enumerated values for the device type, as opposed to using String values.
Messages Class for accessing NLS (National Language Support) enabled messages in the IBM WebSphere Appliance Management Toolkit.
ModelType This class provides a set of enumerated values for the model type, as opposed to using String values.
OperationStatus This class defines valid values tracking the operation status of elements such as domains, and containers to hold these values.
OperationStatus.Enumerated This holds the enumerated values that are allowed to be used with OperationStatus.
StringCollection A simple collection of Strings.
 

Enum Summary
AdminStatus  
OpStatus  
QuiesceStatus  
 

Exception Summary
DMgrException This is the root class for exceptions that are thrown from the DataPower Management Interface.
 

Package com.ibm.datapower.wamt Description

This package contains classes that are used by the clientAPI and amp packages. This package also serves as the topmost package in the hierarchy; all other packages and classes for the IBM WebSphere Appliance Management Toolkit are inside this namespace.

Logging

The manager uses JSR47 logging. When running standalone (i.e., JUnit), the logging properties may be adjusted by using a mechanism such as specifying -Djava.util.logging.config.file=myLogging.properties when invoking the Java runtime (JRE).

When the manager is packaged with a client, the mechanism for adjusting the logging properties will depend on which client is calling the clientAPI.

The manager uses chained loggers. This is because each class has its own logger and the name of each log is the fully-qualified class name (including the package). So for example, you can affect the logger with any of the following names:

All of the loggers also belong the group defined in clientAPI.Manager.getLoggerGroupName(). So you can also affect the loggers via that group name. Generally FINE or FINER should be sufficient to see the program flow. Using FINEST will give the greatest amount of detail.



© Copyright IBM Corp. 2006, 2010 All Rights Reserved.