Design and Procedure for Native IBM DB2 Content Manager Storage Monitoring
Original Publication Date: 2004-Sep-21
Included in the Prior Art Database: 2004-Sep-21
This invention utilizes the internal architecture of CM to create native CM storage monitoring and provisioning capabilities. Storage monitoring and provisioning capabilities will be an integral part of the CM system administration console. The external storage will be viewed from the console as homogenous storage regardless of the storage hardware platforms.
Design and Procedure for Native IBM DB 2 Content Manager Storage Monitoring
This invention provides a unique way to map fixed content managed by IBM DB2 Content Manager (CM) to any CIM/SIM-S compliant storage devices or software including the virtualization machines.
The innovation of this invention is that
1.It uses a unique content identifier based on the attributes and meta data of the content to map the content to the storage.
2.It then enables policy driven storage provisioning through SIM-S based open standard interface to storage hardware /software for the IBM Content Manager. Both the "policy driven" and SIM-S aspects are new and novel for CM. By using content identifier and attributes, application no longer has to keep tracking of the physical location of the stored information. Instead, the internal mapping algorithm tracks the content to the storage. The removal or replication or transfer of the content is transparent to the application. This algorithm also provides the frame work and enablement for policy based automatic storage provisioning for CM. The content user will set the policy based on a variety of criteria. The CM system administrator will determine the level and type of storage for different policies. This invention enables full user control on how and where to store the content, but also ensures automation and federal regulatory compliant by hiding the storage complicity from user. It also ensures content storage is available to all SIM-S standard compliant storage devices and software.
The system consists of three components:
1. Client Component
The client component is called upon by the applications to serve as interface for the CM storage management functions. It serves as an interface for Storage Server Component to store the content and to track the content with the content identifier. It serves also to present the storage information for the particular content to the application and let user define any storage provisioning policies.
2. Storage Server Component.
The function of the Storage Server Component is to service the request for content and storage mapping, as well as associate the storage provisioning policies to the particular content. The storage server component resides on the Library Server of CM to utilize its database of meta data and attribute information for the content which may include, but not limited to Resource ID, Resource Manager ID, etc. It creates a unique identifier during the storage of the content to the Resource Manager of CM based on the attributes and meta data. It then stores the identifier and associated storage policy on Library Server's database.
3. Storage Agent Component.
The Storage Agent component is to discover the individual content's storage related information and return it to the request...