Package com.ibm.datapower.wamt.dataAPI.local.filesystem

Local File System Implementation of the dataAPI Interface for the IBM WebSphere Appliance Management Toolkit

See:
          Description

Class Summary
RepositoryImpl The Repository object used for executing persistence operations such as reading and writing Stored objects to the local file system
StoredDeploymentPolicyImpl The deployment policy information includes the domain configuration blob, the policy type, the policy source, and the associated domain name.
StoredDeploymentPolicyVersionImpl Holds all information related to a deployment policy version that can be used during domain configuration deployment to a DataPower device.
StoredDeviceImpl It represents a DataPower device.
StoredDomainImpl The information that must be persisted for a StoredDomain on a DataPower device.
StoredDomainVersionImpl A version of Domain object persisted in the repository that can be deployed to a DataPower device.
StoredFirmwareImpl Persists all Firmware related information.
StoredFirmwareVersionImpl A persisted version of a Firmware i.e StoredFirmware.
StoredManagedSetImpl The StoredMangedSet writes and reads all information that must be maintained for ManagedSet including its managed device members.
StoredTagImpl  
 

Package com.ibm.datapower.wamt.dataAPI.local.filesystem Description

Local File System Implementation of the dataAPI Interface for the IBM WebSphere Appliance Management Toolkit

The local file system (LFS) implementation of the dataAPI persists relevant information in the local file system. It transforms the persistable objects defined by the dataAPI into XMLobjects before writing them to an XML file. Internally, the implementation uses XML Beans technology for accessing the XML by binding it to Java types. XMLBeans uses an XML Schema, in the LFS implementation, to compile Java interfaces and classes that you can then use to access and modify XML instance data. Firmware and domain configuration images are stored as BIN files. You can examine the WAMT.repository.xml file to see how the various elements can stand in relation to each other. There is an element that represents each stored object defined in the dataAPI.

Configuration of the Local File System base directory

When the Manager is initialized, it attempts to locate a repository directory configured on the Credential object. See Credential on how to set Credential properties. If one is not provided, it next attempts to locate the configured repository directory using the value in the WAMT_REPOS_HOME environment variable. This is the directory where the WAMT.repository.xml file is stored. The WAMT.repository.xml file contains all of the Manager's configuration meta-data. Configuration artifacts such as a domain configuration backups and device firmares are also stored under the directory. During manager initialization, if the specified directory does not exist, a new directory is created.

If WAMT_REPOS_HOME environment variable is not specified, the configured repository directory is resolved by using the path specified by the user.home property. This directory is automatically created if it does not already exist.

If the Manager locates an existing WAMT.repository.xml file, it loads data into the stored objects. If the Manager does not find WAMT.repository.xml file, it will start up without any data and prepare to write to a new file.

Manager shutdown events

When the Manager shutdowns gracefully, it will close down the repository and write all current data into the repository XML file. It will also clean up any obsolete bin files from the directory. For example, a bin file can become obsolete if the firmware version that referenced the file is deleted.

Saving configuration changes

The clientAPI saves data as it is modified. The Manager saves a backup copy of the repository file before it saves the current data. The backup copy is overwritten before each save.

Local File System use of the Credential object

The LFS implementation only uses the following properties from the Crendential object passed to it by the Manager: The Credential is passed to the Manager during initialization.



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