LYCOS RETRIEVER Beta Retriever Home  |  What is Lycos Retriever?   
Configuration
built 178 days ago
Configuration Items are a very personal issue. Each customer has a unique environment. The exact physical attributes of a computer may be needed by one customer, but may just represent meaningless data to another. Service-now.com therefore provides a mechanism to easily define new "classes" of Configuration Items and new relationships that may exist between CI's. New classes can be defined that extend other classes. For example, a "laptop" class exists that extends the "computer" class.
Configuration management is a vital first step to efficient database management. Clarity enables users to discover and inventory all aspects of the database infrastructure, providing a comprehensive list of all databases across multiple platforms including all configuration and utilization information in an easy-to-view database landscape. By centralizing all database configurations and by tracking changes to configurations, users can vastly improve database management, taking timely actions to maximize efficiency throughout the infrastructure and ensure uniformity. Moreover, Clarity configuration management enables users to create reports that instantly account for licenses, server inventory, and storage utilization across all of your databases.
Source:
Since version 4.1, each Configuration node has a namespace associated with it, in the form of a string, accessible through getNamespace(). If no namespace is present, getNamespace will return blank (""). See DefaultConfigurationBuilder for details on how XML namespaces are mapped to Configuration namespaces.
Configuration items or CI[S] form the basis of configuration management solutions. Typically a CI is a collection of objects related to the specific functionality of a larger system. Examples of these objects may be requirements, code, documentation, models and other files. Configuration Management systems oversee the life of the CIs through a combination of process and tools. The objective of these systems is to avoid the introduction of errors related to lack of testing or incompatibilities with other CIs.
Configuration management begins with establishing configuration baselines. The statement of project requirements should be put under configuration control. Then a configuration control system should be employed to collect, evaluate, decide, and implement proposed changes to the project scope or the product specifications and design. Configuration baseline identification should be applied to functional, allocated, and product baselines.
Source:
About: System Configuration Collector (SCC) is yet another configuration collector. It consists of a client and a server part. The client collects configuration data in a structured snapshot, compares the new snapshot with the previous one, and adds differences to a logbook. Then the snapshot and the logbook are converted to HTML for local inspection. Optionally, the data can be sent to a system running the server software. On the server, summaries of the data are generated, and search/compare operations on the snapshots and logbooks are available via a Web interface.
SEARCH
MORE ABOUT
  Configuration