James H. Zisch - Computer Services

Solutions : Site Management : Image Verifier

 

Image Verifier


Description
Requirements
Usage
FAQs

Description

JHZ-CS Solutions support defining image file references within the Item Information Dataset (IID), as well as within SQL RDBMS database tables. The need to verify those stored references is satisified using Image Verifier.

Image Verifier assists the webmaster by assuring image references correctly point to the path and filename where the image files reside on the server. It reports image referencing errors allowing the webmaster to identify missing images and to make corrections without having to manually test each dynamically generated page separately.

And, Image Verifier allows you to quickly add new items to the IID or database while deferring creation of item images at a later time while still making the new items available for viewing at the website. Later, simply use Image Verifier to quickly identify which images remain to be created. It permits getting new item information online fast for customers to locate and allowing webmasters to complete new item graphics at a later time.

Image Verifier is supported by configurations using either the flat file IID or SQL RDBMS data sources.

Web Server Requirements:

  • Operating Systems Supported: Unix, Linux, Macintosh OS X® and Windows®
  • HTTP 1.x with CGI (Common Gateway Interface) PERL 5.x (check with your ISP or Server Administrator; this requirement is typically supported on most systems)
  • Optional: SENDMAIL (supported on most all Unix/Linux platforms), or PERL NET:SMTP (available from CPAN) (commonly used on Windows® server platforms) with an SMTP system pre-installed and configured. This optional requirement supports automatic email notification to the webmaster when execution errors are detected.
  • Optional: For configurations using an RDBMS (Relational Database Management System) data source requires a supported RDBMS, the PERL DBI module and the RDBMS specific DBD module to be previously installed and configured

Image Verifier
Installation and Usage

FILENAME: iv.html

PURPOSE:

Describes Image Verifier dependencies, requirements, installation and usage.

DEPENDENCIES:

cm.pl - Configuration Management configuration and common logic modules (see: cm.html)
jhzcs.pl - JHZ-CS configuration and common logic modules (see: jhzcs.html)
IID (Item Information Dataset)

REQUIREMENTS:

Logic Modules

iv.cgi - logic module
db_tabs.pl - data mapping (required only for SQL RDBMS data source usage)

PACKING (PARTS) LIST

PACKING LIST
PRODUCT ID: IV
COMPONENT TYPE SIZE AUTH*
cgi-bin/cm/cm.incl TEXT 5198 700
cgi-bin/cm/cm.pl TEXT 1399 750
cgi-bin/cm/iv/iv.cgi TEXT 15765 750
cgi-bin/cm/iv/iv.incl TEXT 8164 700
cgi-bin/geog.pl TEXT 11750 750
cgi-bin/jhzcs.pl TEXT 47225 750
cgi-bin/license.incl TEXT 7565 700
images/JHZCS.gif BINARY 745 750
logs/errorlog.txt TEXT 91 750
*AUTH - Authorization/permissions octal equilvalents where:
7=RWX, 6=RW, 5=RX, 4=R (R=Read W=Write X=Executable)
1 char indicates Octal number
2 char Owner
3 char Group
4 char All Others

INSTALLATION:

It is strongly recommended that you read the entire installation process steps prior to performing any installations. Each solution has specific instruction that must be followed precisely.

The Installation Process

The installation process follows this order:

  1. Download solution to PC development platform and expand installation package (use any standard archive application such as WinZip®, StuffIt Expander® or TAR command)
  2. Modify configuration settings
  3. Upload to server
  4. Set access authorization permissions
  5. Test
  6. Customize Templates
  7. Test

Authorize non-Logic Components

Authorize non-logic components as follows:

  • authorized all images for read and execute access; see NOTE FOR NON-LOGIC COMPONENTS below
  • authorized all static HTML ".html" documents for read access; see NOTE FOR NON-LOGIC COMPONENTS below
  • authorized all HTML Templates ".htm" documents for read access at the logic level; see NOTE FOR LOGIC COMPONENTS below
  • authorized all images for read and execute access; see NOTE FOR NON-LOGIC COMPONENTS below.

NOTE FOR NON-LOGIC COMPONENTS: Use the minimum required permissions to achieve most secure configuration; permission requirements for non-logic modules are dependent on the server configuration whether authorization is required for group only or for both group and other.

Modify Logic Components

Modify all logic components "*.cgi" and "*.pl" logic modules as follows:

  • first line of code (#!) correctly points to the PERL executable on the server (use command "which perl" or consult your server administrator)
  • all "requires" statements contained in all "*.cgi" and "*.pl" logic modules must use absolute directory paths (beginning with a forward slash "/")

Authorize Logic Components

Authorize logic components and dependent components (HTML and Email templates, and others) as follows:

  • authorized as all "*.pl" logic modules for read access; see NOTE FOR LOGIC COMPONENTS below.
  • authorized as all "*.cgi" logic modules for read and execute access; see NOTE FOR LOGIC COMPONENTS below.
  • authorized all HTML and Email Templates documents for read access at the logic level; see NOTE FOR LOGIC COMPONENTS below

NOTE FOR LOGIC COMPONENTS: Use the minimum required permissions to achieve most secure configuration; permission requirements for logic modules are dependent on the server configuration whether authorization is required for owner only (i.e., Apache with SUExec active), or for both owner and group.

Set Configuration variables in iv.cgi; see embedded instructions.

Uploading to Web Server

All dependent and required components must be installed and successfully configured. All components, with the excpetion of images, must be FTP uploaded as TEXT. Images must be FTP uploaded as BINARY.

USAGE:

This is a back end administration utility invoked via the URL that points to it. The default install location would point to "http://yourdomain/cgi-bin/cm/vi/vi.cgi" where "yourdomain" would be replaced accordingly.

FAQs

Does Image Verifier correct erroneous URL references?

No. Image Verifier reports any URL references that do not point to a valid image file. You then, add the image, or correct the URL reference to correctly point to the image file.

JHZ-CS Solutions are distributed exclusively under terms and conditions of the JHZ-CS Software License Agreement.