The Aggregate Disk Usage pie chart on an Overview Report indicates how much disk storage is available on a device(s). It is an indicator of Free Space and Used Space.
ISOdx recommends daily snapshots of customer mission critical servers with the intent to provide a long, detailed history of the configuration. Additional snapshots may be taken via other means such as post-job execution program that may have determined the job ended with a bad exit code.
A report type, also referred to as a Dual Snapshot, that lists only changes between the two most recent Snapshots.
A Change Summary quickly identifies where the changes between snapshots can be found. A component of the dx Factor (or change indicator) which is the number of changes and an average of changes by snapshot for each data type collected on a device, this feature includes a query of all snapshot view Overview reports that taps into the existing information. The results of the query are displayed in a table format containing the following pieces of information: Data Type, number of Changes recorded, Trend, and Deviation From Trend indicator.
A checksum is a unique representation of a file or a string of characters or words. It is a quick way to determine if anything in a file is different from the original version. One way to calculate a checksum for a file is to run the MD5 algorithm on each file The checksum changes anytime anything in the file changes, even very simple changes like a space.
Common Internet File System (CIFS) is collector terminology meaning, the protocol used on Microsoft operating systems which map to file systems across a network. ISOdx uses this ubiquitous protocol to distribute the ISOdx Collector Software and manage the snapshot output.
The interface providing the means to compare any two command outputs or files from one or many systems, downloaded or emailed.
The Collector server passes “Snapshot” documentation (so called because of the single point-in-time nature of the collection) to the Portal for viewing thus collecting a Snapshot. See also Snapshot.
Software designed for the purpose of collecting configuration information from servers and properly formatting the output of each distributed on the ISOdx Collector Server.
The interface which provides a way to compare two snapshots for any one device. Displayed as a "Compare Mode" in the Enterpirse Tree. By default, the data provided will contain only items which have changed between the two snapshots.A compare provides a contract between two Snapshots, whether on the same device (i.e., two different points-in-time), or two different devices.
The interface which provides a way to compare two snapshots for any one device. Displayed as a “Compare Mode” in the Enterprise Tree. By default, the data provided will contain only items which have changed between the two snapshots. A Compare provides a contrast between two Snapshots, whether on the same device (i.e., two different points-in-time), or two different devices.
A utility that allows you to schedule job(s) on a UNIX machine.
The database or group of databases containing the customer snapshots. All customers have at least one database used to store the snapshot data and all customer databases are separate from each other.
Any ISOdx supported server or device
The Dashboard provides a quick “at-a-glance” view of the current status of your environment (ecosystem) components being analyzed for change by ISOdx. It appears on the launch page after login. The purpose of the dashboard is to give the user one click access to the latest snapshot of each device on the system along with an “at a glance” view of where and the amount of changes that have occurred across the ecosystem. The dashboard is refreshed every minute, so you will always have up-to-date data. The colored icon bubbles represent the data types from the Change Summary ordered by level of change: low, medium, high. Using the “hover over” feature displays the detail of the data type change.
The server or cluster of servers running the database processes containing snapshot data.
Any system or appliance ISOdx is capable of taking a snapshot of.
A documentation report type, also referred to as a Single Snapshot, that contains the “List All”/server information for the device according to the most recent Snapshot.
A mathematical formula for determining the amount of change from the baseline Snapshot to the current Snapshot. The baseline Snapshot always has a dx factor of 1.00, and as components are changed, the dx factor decreases. If components are added, the dx factor increases.
An ISOdx developed algorithm to help describe the number of changes in a snapshot with regard to the current average number of changes for a device. The changes for snapshot filestat, command output and registry data are placed on an equal scale and tracked over time as the device provides more snapshot data.
The java tree interface in the ISOdx Web Portal which organizes customer systems, groups, and reports.
ISOdx's proprietary collection tool used to capture object metadata on any file system, directory, or file. This metadata includes, but is not limited to, filename, file type, file size, permissions, date and timestamp of most recent change, and checksum MD5 hash. It collects files and determines if it should make a copy.
By default, Filestat gathers contents of files less than 32 KB, although this can be modified. Filestat can also be customized to gather contents of all files with a particular commonality, regardless of size, or can always exclude files based on other criteria.
A report that lists changes between the Gold Image and the most recent Snapshot. If not defined, a gold comparison report contains all changes that occurred between the most recent snapshot and the oldest snapshot. It is also referenced as a Dual Snapshot comparison.
A known good-state Snapshot. A Gold Image is kept permanently in the database until another Gold Image is designated.
A snapshot which best describes a device in its "perfect state" as determined by the customer. A snapshot marked as a Gold Image will not expire. Gold Image is analogous with "baseline."
The Host ID is generated by an ISOdx install. It is used to acquire a valid ISOdx license when sent to license@ISOdxSolutions.com along with the customer’s purchase order number.
HTTPS is the secure version of HTTP (encrypted), the communication protocol of the World Wide Web. It was invented by Netscape Communications Corporation to provide authentication and encrypted communication and is used in electronic commerce.
In the Help drop-down on the ISOdx menu bar, you will notice an Icon glossary. The Icon Glossary illustrates the various icons that you will need to become familiar with while working with ISOdx. These include Tree Menu icons, Table icons, User and Organization Management icons, and Report icons.
A collection of programs and processes which use raw snapshot data and save, or import, to the customer database.
The server delivered to a customer's data center for the purpose of distributing the ISOdx Collector Software, acting as a local queue for snapshot data, and communicating with the ISOdx Portal Server for the purpose of uploading snapshot data and executing daily maintenance processes.
The ISOdx Director is a Java Message Service (JMS) client that connects to the ActiveMQ messaging service via the Stomp protocol. The director’s primary function is to record work requests, facilitate the execution of work requests received from ActiveMQ and ensure each request executed is completed, recorded, and removed from the work queue. Only one director process may run on any one server; however, when looking at a process list there may be ten or more depending on the capabilities of the system hardware.
The binary file which is downloaded to each device that will participate in the ISOdx process. The role of this file is to securely facilitate the collection of information and send that information to the appropriate collector server.
An ISOdx Collector Server using enabling technologies to imitate the physical server within a customer's host server. This configuration will be used where a physical ISOdx Collector Server cannot be installed.
Java Message Service (JMS) client. JMS is a specification that describes a common way for Java programs to create, send, receive, and read distributed enterprise messages.
An ISOdx key is the product license file that tracks, for a given date range, the number of devices registered with ISOdx. The key delineates everything installed on the system and the features it contains. This information is used to enforce accurate billing.
An automated installation method used to install an operating system. Using the kickstart installation method, a system administrator can create a single file containing the answers to all the questions that would normally be asked during a typical Red Hat Linux installation. This file includes ISOdx customizations. The kickstart process is configured automatically based on information entered during a new server build.
The file used to complete an ISOdx software license installation. It is obtained by emailing the License Key ID to license@ISOdxSolutions.com. The license file is to be installed in the directory "/opt/ISOdx" with the file permissions 0644 {u=rw,go=r}. It is required to complete an ISOdx software license installation. This product license file tracks, for a given date range, the number of devices registered with ISOdx and delineates everything installed on the system.
An option provided via the snapshot View interface. This option provides a list of all items as they existed at that point in time. Commonly called a documentation query.
The queries used in the Compare interface which will provide a list of only those items which have changed and a means to compare the metadata or content data, if available.
An option provided via the snapshot View interface which provides a list of only those items that have changed since the most recent previous snapshot. Commonly called a change query.
Servers for which the customer has determined ISOdx should provide minimal history. These servers may take only 2 to roughly 14 snapshots per calendar month.
Cranel, Inc. provides the ISOdx Collector Server, access to the ISOdx portal, and full support via a monthly or contractual service charge. The rights to the ISOdx technology is retained by Cranel and licensed to their customers.
MD5 is an algorithm used to calculate a checksum (comparison of what has changed) in a file(s). Typically run on each file, it can be used as a verification key to check for code changes. The MD5 Hash Digest algorithm takes as input a message of arbitrary length and produces as output a 128-bit "fingerprint" or "message digest" of the input.
Every module comes in three sections: collector, importer, and portal. The collector section resides on the Collector Server and consists of the scripts, programs and configuration files used by the Collection Software to gather information on the device or application running on the device. The importer section resides on the Database Server and is responsible for taking the raw snapshot produced and copying the data to the customer's database. The portal section resides on the Portal Server and is the web interface to the customer's database.
By default, each user with a login has a “My Devices” directory in the Enterprise Tree. For ease of use, “My Devices” can be used to organize and set aside in one area the machines/systems/devices and reports a user may be responsible for.
By default, all newly created reports fall under the “My Reports” folder. The naming convention, “My” indicates only you have permission to see these reports.
A 32-bit value, similar to an IP address that determines how an IP address is separated into subnet address and host address.
Network File System, the protocol used on supported UNIX platforms to distribute the ISOdx Collector Software and manage the snapshot output.
All user accounts in ISOdx are directly related to an organization name in the portal. That organization name could also be an independent vendor (ISV). A device organization within the Portal display is determined by the suborg switch.
The web interface provided as part of the ISOdx service which is a front-end to the customer database and snapshot data.
The ISOdx server which provides the ISOdx Web Portal but is also the central server which all ISOdx Collector Servers report to.
PostgreSQL is a robust, stable, ACID compliant, open source relational database and has been the ISOdx database of choice since 2002. PostgreSQL 8.2 ships with ISOdx 4.0 and is currently the only supported database.
Full documentation for the PostgreSQL database can be found at http://www.postgresql.org/.
ISOdx is of great value even if you only have one Snapshot for a device and no later one to compare it to. A Quick Compare allows you to determine what the device contains, not having to dig for those details, so that you can more quickly determine which component of that device—be it a patch, module, or configuration—is causing the problem.
The ISOdx delivered binary which provides a copy of the Window server registry per the configuration file.
The java tree interface used to View and Compare registry data. The tree has the ability to illustrate the type and number of changes for each registry hive.
The interfaces permitting customers to create their own queries, specifying groups of or a list of individual devices, and additional customizations for the purpose of documenting devices and tracking changes. Reports can be used to document devices, show changes only, or compare the most recent snapshot to the Gold Image.
Stands for Red Hat package manager. The management system of tools, databases, and libraries that handle the installation and removal of RPM packages. Run the command rpm to use the program.
The name a customer's server is recognized by. In UNIX, uname -n is used and in Microsoft Windows the "Computer Name" found in the My Computer Properties is used.
A side-by-side comparison of two Snapshots (i.e., points in time) from two different devices. Performing a server-to-server comparison is extremely helpful when one device is working properly, but another one isn't.
Data collected describing a point in time on a customer's server. The snapshot time is taken from the customer server's local time and is represented as the seconds since the epoch (01-01-1970 at 00:00:00). The three primary components of a snapshot (filstat, commands, and registry) can capture virtually anything about any device within an enterprise.
The process by which the number of snapshots per system is kept to a maximum of 30, or 31 with a Gold Image, when new snapshots come in for any system.
The process by which raw snapshot output files are pulled into the customer database where change is initially identified, saved and duplicate information dropped.
The tree that you see in the user interface when you click on a snapshot for a file system, directory, or file. This tree contains all the reports contained within folders notating the module to which they belong that you can run for this snapshot.
Any ISOdx or customer delivered script or binary that is distributed via the collector server. Tools are basically bundled code that provides the ability to gather data any way you wish.
Located in the product licensing file, the verification-code is the "checksum" that validates that none of the product key information has been changed.
The interface which provides a way to any one snapshot for any one device. Also displayed as a "View Mode" in the Enterprise Tree. This interface varies from the Compare interface in that a version history is available for command output, filestat or registry. Only changes found in the import of this snapshot may be viewed, or the system can be viewed with the intent to see it as it is at that point in time. A single Snapshot view provides complete, standalone documentation.
Logic implemented in the collector code for each platform providing the means to "rename" the device on which the snapshot was generated. Through this option, two snapshots from different devices may assume the same name but ultimately be presented in the portal as a single device. Comparing the two snapshots for that device, or Virtual Server, in the portal is, in effect, comparing the two devices.
The Virtual Private Network connection capable of being enabled only by the customer for the explicit purpose of giving ISOdx support staff the means to login to the ISOdx Collector Server for diagnosing problems or making customer requested configuration changes.