pegasus/Attic/readme.html - diff

Return to readme.html CVS log

Up to [Pegasus] / pegasus / Attic

Diff for /pegasus/Attic/readme.html between version 1.6 and 1.7

version 1.6, 2004/05/13 14:39:29

version 1.7, 2004/10/18 18:20:06

Line 1

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

<html>

<head>

content="text/html; charset=windows-1252">

Line 9

</head>

<body>

Pegasus Enhancement Proposal (PEP)

PEP #: 103

PEP #: 175

Title: OpenPegasus

Version 2.3 Release Readme file

Version 2.4 Release Readme file

Version: 1.1

Version: <span

Created: 12

style="color: rgb(0, 0, 0);">1.4

November 2003

Created: 24 June

Authors: Karl

2004

Schopmeyer, Konrad Rzeszutek

Authors: Warren

Status: draft

Grunbok, Mike Harris

Status:  draft

Version History:

<table border="1" cellspacing="1" bordercolordark="#666666"

<table bordercolordark="#666666" bordercolorlight="#cccccc"

bordercolorlight="#CCCCCC" width="100%" style="font-family: Arial;">

style="font-family: Arial;" border="1" cellspacing="1" width="100%">

<tbody>

<tr>

<th bgcolor="#cae6ca">Version</th>

Line 30

Line 32

</tr>

<tr>

<td align="center">12 November 2003</td>

<td align="center">Karl Schopmeyer</td>

<td align="center">Warren Grunbok

<td>Update from 2.2 Release notes. Converted to HTML</td>

</td>

</tr>

<td>Initial draft

<tr>

</td>

</tr>

<td align="center">March 10 2004</td>

<tr>

<td align="center">Konrad Rzeszutek</td>

<td>Added sections describing SSL and PAM configuration</td>

<td align="center">24,August 2004

</tr>

</td>

<tr>

<td align="center">Warren Grunbok

</td>

<td>Mostly spelling changes, adds to very last paragraph

</td>

</tr>

<tr>

<td style="vertical-align: top;">1.2

</td>

<td style="vertical-align: top;">31, August 2004

</td>

<td style="vertical-align: top;">Warren Grunbok

</td>

<td style="vertical-align: top;">Changes based on architecture

review.  Removed /Directory structure section and placed

into  seperate document.

</td>

</tr>

<tr>

<td style="vertical-align: top;">1.3

</td>

<td style="vertical-align: top;">???

</td>

<td style="vertical-align: top;">Warren Grunbok

</td>

<td style="vertical-align: top;">Removed Pegasus Directory

structure and placed in PEP 191, Added Copyright and End of Doc marker.

</td>

</tr>

<tr>

<td style="vertical-align: top; color: rgb(0, 0, 0);">1.4

</td>

<td style="vertical-align: top; color: rgb(0, 0, 0);">27,

Sept 2004

</td>

<td style="vertical-align: top; color: rgb(0, 0, 0);">Warren

Grunbok

</td>

<td style="vertical-align: top; color: rgb(0, 0, 0);">Corrected

Security changes as per Sterling.

</td>

</tr>

</tbody>

</table>

<hr>

Abstract: Installation, build, operation information on the

Abstract:  Installation, build, operation information on

Pegasus Platform Version 2.3 Release. Note that if this readme conflicts

the Pegasus Platform Version 2.4.0 Release. Note that if this readme

with the documentation in the release notes or interface definition

conflicts with the documentation in the release notes or interface

documents for a particular release, those documents should be

definition documents for a particular release, those documents should

considered authorative. This is a simplified overview to act as an

be considered authorative. This is a simplified overview to act as an

introduction to Pegasus.

<hr>

OpenPegasus - A Manageability

Services Broker for the DMTF CIM/WBEM Standards

Services Broker for the DMTF CIM/WBEM Standards

Tagline: OpenPegasus is an object manager for

DMTF CIM objects written in C++ and supported by The Open Group

DMTF CIM objects written in C++

STATUS: Revised November 2003 for Pegasus

and supported by The Open Group

release version 2.3.0

Table of Contents

STATUS: Revised Sept 2004 for  Pegasus release version

<a

2.4.0 

href="#Overview"> Overview</a>

- Approved

<a

href="#Availability%20of%20Pegasus">Availability of Pegasus</a>

<a href="#Overview">Overview</a>

<a

<blockquote style="margin-top: 0pt; margin-bottom: 0pt;"> <a

href="#Pegasus%20Major%20Components">Pegasus Major Components</a>

href="#avail_of_peg">Availability of Pegasus</a>

<a

<a href="#peg_maj_comp">Pegasus Major Components</a>

href="#Pegasus%20Supported%20Platforms">Pegasus Supported Platforms</a>

<a href="#avail_of_peg">Availability of Pegasus</a>

<a

<a href="#peg_sup_plat">Pegasus Supported Platforms</a>

href="#Pegasus%20Dependencies">Pegasus Dependencies </a>

<a href="#peg_dep">Pegasus Dependencies</a>

<a

<a href="#peg_dir_struc">The Pegasus Directory Structure</a>

href="#The%20Pegasus%20Directory%20Structure">The Pegasus Directory

<a href="#dev_with_peg">Development with Pegasus and Pegasus Tools</a>

Structure</a>

<a href="#cmnd">Commands</a>

<a

<a href="#docs">Documentation</a>

href="#Pegasus%20Installation">Installation</a>

<a href="#part">Participate</a>

<a

</blockquote>

href="#Building%20Pegasus">Building Pegasus </a>

<a href="#inst_peg">Install Pegasus</a>

<a

<blockquote style="margin-top: 0pt; margin-bottom: 0pt;"><a

href="#Populate%20the%20Repository">Populate the Repository</a>

href="#download">Download or checkout Pegasus</a>

<a

<a href="#vfy_req_sw">Verify that you have the required

href="#Registering%20Providers%20in%20the%20Pegasus%20Environment">Registering

software</a>

Providers</a>

<a href="#set_envt_var">Set the environment variables</a>

<a

<a href="#bld">Build the Pegasus runtime, test files, test clients,

href="#The%20MU%20Utility">The MU Utility</a>

and repository</a>

<a

<a href="#pop_peg_rep">Populate the Pegasus repository</a>

href="#Notes%20about%20Building%20Pegasus%20on%20Linux">Notes about

<a href="#reg_prov">Register providers in the Pegasus environment</a>

Building Pegasus on Linux</a>

<a href="#bld_rpms">Build an RPM for Pegasus</a>

<a

<a href="#note_bld_peg_lnx">Notes

href="#Notes%20about%20Building%20Pegasus%20on%20Mac%20OS%20X/Darwin">Notes

about Building Pegasus on Linux</a>

about Building Pegasus on Mac OS X/Darwin</a>

<a href="#note_bld_peg_ssl">Notes on building Pegasus with SSL</a>

<a

<blockquote style="margin-top: 0pt; margin-bottom: 0pt;"> <a

href="#Notes%20about%20Building%20Pegasus%20with%20SSL">Notes on

href="#crt_ssl_cert">Creating SSL

building Pegasus with SSL</a>

certifications</a>

<a

</blockquote>

href="#Building%20Pegasus%20on%20Windows%202000%20or%20Windows%20XP%20With%20Microsoft%20Visual%20C++">Building

<a href="#bld_peg_win">Building

Pegasus on Windows 2000 or Windows XP With Microsoft Visual C++</a>

Pegasus on Windows 2000 or Windows XP With Microsoft Visual C++</a>

<a

<blockquote style="margin-top: 0pt; margin-bottom: 0pt;"> <a

href="#Installing%20the%20Pegasus%20HTML%20Test%20Client">Installing

href="#mu_utility">The MU Utility</a>

the Pegasus HTML Test Client </a>

</blockquote>

<a

</blockquote>

href="#Development%20with%20Pegasus%20and%20Pegasus%20Tools">Development

<a href="#test">Test the Pegasus installation</a>

with Pegasus and Pegasus Tools</a>

<blockquote style="margin-top: 0pt; margin-bottom: 0pt;"> <a

<a

href="#inst_peg_html"> Installing the Pegasus HTML Test Client</a>

href="#Commands">Commands</a>

<a href="#test_icu">Testing with ICU enabled</a>

<a

</blockquote>

href="#Creating%20SSL%20certifications">Creating SSL certifications</a>

<hr>

<a

href="#Configuring%20SSL">Configuring Pegasus to use SSL</a>

<a

href="#Configuring%20PAM">Configuring Pegasus to use PAM</a>

<a

href="#Testing%20with%20ICU%20enabled">Testing with ICU enabled </a>

<a

href="#Pegasus%20Documentation">Documentation</a>

<a

href="#Participate%21">Participate</a>

<h1><a name="Overview">Overview</a> </h1>

OpenPegasus (also referred to as Pegasus): Pegasus is an

OpenPegasus (also referred to as Pegasus):

open-source CIM Server for DMTF CIM objects. It is written in C++ and

Pegasus is an open-source CIM Server for DMTF CIM objects. It is

includes the Object manager (CIMOM), a set of defined interfaces, an

written

implemenation of the CIMOperations over HTTP operations and their cimxml

in C++ and includes the Object manager (CIMOM), a set of defined

HTTP encodings, and Interface libraries for both client and providers.

interfaces, an implemenation of the CIMOperations over HTTP operations

It is maintained consistent with the DMTF CIM and WBEM specifications

and their cimxml HTTP encodings, and Interface libraries

except for exceptions noted in the documentation.

for both client and providers. It is maintained

consistent with the DMTF CIM and WBEM specifications except for 

exceptions

noted in the documentation.

Pegasus is open source and is covered under the MIT open-source

license.

Pegasus is being developed and maintained under the auspices of The

Open Group. Pegasus is maintained under the license defined in the doc

Open

directory (LICENSE) of this release. This licensing is intended to

Group. Pegasus is maintained under the license defined in the doc

support as wide a distribution as possible with minimal demands on the

more complete documentation.

<h1><a name="cmnd">Commands</a></h1>

The manpages for each of the commands are in rpm/manLinux/man1.Z

directory (on CVS)

To see simple help for each of the commands, use the "-h" flag.

<pre>Examples: bin/cimserver –s (Shuts it down) bin/cimserver traceLevel=4 traceComponents=ALL (starts server with config flags) bin/cimprovider –l –s (lists providers and their status) bin/cimprovider –e –m OperatingSystemModule (enables the OperatingSystem provider) bin/cimuser –a –u guest –w ThePassword bin/cimuser –l (lists the users) bin/tomof CIM_Config (extract CIM_Config from repository and present it in MOF type) </pre>

</blockquote>

<h1><a name="docs">Pegasus Documentation</a></h1>

The documentation is currently in preparation.  Much of Pegasus

is documented in the PEGASUS PEPs which are the basis for approval of

Pegasus functionality, changes, plans, etc.  These documents are

openly available on the PEGASUS web site.  The preliminary

documentation

is not provided with this release. The current documentation is

maintained both as a manual created

under the tool DOC++ in the runtime subdirectory manual/html (see

doc/devManual to create), as an api document also creatable from the

source tree (see doc/apidoc) and as other miscellaneous documentation

in the doc directory. Also there is a set of release notes. Normally

the release notes for the current release are available in the root

source directory of CVS.

Note that the Pegasus WEB site at The Open Group will be the source

of most

documentation in the future and today is the source of most discussion

and

design documentation.

<h1><a name="part">Participate!</a></h1>

We are looking for people who want to join the Pegasus work group

and

contribute to effort of getting this Pegasus off the ground. Please

join the mailing list by visiting www.openpegasus.org, and click on

Mailing Lists.

<h1>

<a name="inst_peg">Install Pegasus</a> </h1>

You can install and run Pegasus on any of the supported platforms. The

installation process includes the following steps:

<ol>

<li>Download or checkout Pegasus. </li>

<li>Verify that you have the required software. </li>

<li>Set environment variables. </li>

<li>Build the Pegasus runtime, test files, test clients and

repository. </li>

</ol>

<a name="download">Step 1: Download or checkout Pegasus</a>

Pegasus is freely available from the open group's Pegasus home page: <a

target="blank" href="http://www.openpegasus.org">http://www.openpegasus.org</a>.

obtain Pegasus, you can either check it out using CVS or download a

snapshot image of the soruce distribution. For more information about

checking out Pegasus using CVS, see: <a href="#avail_of_peg">Availability

of Pegasus</a>.

Pegasus is not currently releasing binaries, but you can create RPMs

using a script included with the source distribution. See <a

href="#bld_rpms">Building RPMs for Pegasus</a> for more information.

<a name="vfy_req_sw">Step 2: Verify that you have

the required software</a>

Refer to the section <a href="#peg_dep">Pegasus

Dependencies</a> and verify that you have the software required for

your Operating System and planned usage of Pegasus.

<a name="set_envt_var">Step 3: Set the environment

variables</a>

Before installing or running Pegasus, ensure that the following

environment variables have been defined or updated:

<dl>

<dt>PEGASUS_ROOT </dt>

<dd>Defines the path to the "pegasus" directory you've pulled from

CVS, for example: <tt>/opt/pegasus/pegasus-2.3.2</tt>

</dd>

<dt>PEGASUS_HOME </dt>

<dd>Defines the directory that will contain the output binary files.

For example, if you set this to <tt>$HOME/pegasus_home</tt>, then the

output will go into <tt>$HOME/pegasus_home/bin</tt> and <tt>$HOME/pegasus_home/lib.</tt>

<a href="http://www.opendarwin.org/projects/dlcompat/">http://www.opendarwin.org/projects/dlcompat/</a>

If you plan on doing parallel builds, you may want to define a unique

PEGASUS_HOME value for each build you need, that way the output of each

build will be placed in its own directory, for example: <tt>$HOME/pegasus_home_LINUX_IX86_GNU.</tt>

Again, dlcomapt needs to be installed ONLY if you are using Mac OS

</dd>

X/Darwin.

<dt>PEGASUS_PLATFORM </dt>

5. DOC++ - The Pegasus documentation is taken from a

<dd>Identifies the platform to be built. Each supported platform has

combination of text files and the Pegasus header files themselves. This

a unique identifier with the following form:

documentation is formatted with DOC++ and GAWK. These tools are required

if the documentation is to be recreated but we expect that only the

The following values are tested for the OpenPegasus release:

core team will be recreating documentation.

6. ICU Internationalization libraries - These libraries are

used as the basis for message catalogs for message internationalization.

See the ICU website (http://oss.software.ibm.com/icu/) for more

information on these libraries

7. OpenSSL - If it is intended to use SSL

on the communication protocol, the OpenSSL libraries are required.

<h1><a name="The Pegasus Directory Structure">The Pegasus Directory

Structure</a></h1>

Pegasus is distributed as a complete source directory structure that

should be installed either from one of the snapshots or from CVS.

This structure is generally as follows:

Pegasus Source Structure

Pegasus Root directory (PEGASUS_ROOT

environment variable)

<ul>

<li>cgi Source for the Pegasus WEB

Based Test client

<ul>

<li>cgi-bin CGI Directories for WEB

demonstration. This directory is normally empty but can be

populated from the runtime with the make from cgi. </li>

<li>htdocs HTML Pages for Pegasus WEB

demonstration </li>

</ul>

</li>

<li>doc Miscellaneous Pegasus

Documents.

<ul>

<li>apidoc - Source for the public api

documentation.</li>

<li>DevManual Source and build files for

developers' manual mak General make files (used by other makes)</li>

</ul>

</li>

<li>mak - Common make files for

Pegasus compilation</li>

<li>Dummy -</li>

<li>InterfaceArchive -</li>

<li>rpm - files for rpm installation

for Linux</li>

<li>Schemas - Schemas used in the

installation of Pegasus. This includes currently released versions

of the DMTF schemas in subdirectories (ex. CIM27) and Pegasus local

Schemas (ex. </li>

<li>src All Pegasus Source Files

<ul>

<li>ACEExample Test directrory

with examples of the use of ACE (obsolete). </li>

<li>Clients Source for various

test clients and demonstration clients.</li>

<li>CGICLIENT Pegasus test client

that uses a WEB browser JAVA Java Client support modules </li>

<li>Pegasus - Core pegasus

modules.

<ul>

<li>Client Pegasus Client API

<li>AIX_RS_IBMCXX </li>

Tests depends tests </li>

<li>Common Pegasus Common

<li>HPUX_PARISC_ACC </li>

Functions (C++ source and headers tests Test programs for

<li>LINUX_IA64_GNU </li>

the common functions</li>

<li>LINUX_IX86_GNU </li>

<li>Compiler Pegasus MOF

<li>LINUX_PPC_GNU </li>

compiler </li>

<li>LINUX_ZSERIES_GNU </li>

<li>Config Pegasus

<li>NSK_NONSTOP_NMCPLUS </li>

Configuration functions</li>

<li>SOLARIS_SPARC_CC </li>

<li>Consumer Indication

<li>SOLARIS_SPARC_GNU </li>

Consumer class header</li>

<li>TRU64_ALPHA_DECCXX </li>

<li>ControlProviders

Implementation of Pegasus internal providers </li>

<li>ZOS_ZSERIES_IBM </li>

<li>ExportClient Client

</ul>

connect code for export of indications</li>

<li>ExportServer Server code

</dd>

for import of indications</li>

<li>Handler Indication

<dd>Add $PEGASUS_HOME/bin to your path.</dd>

handlers. Today this includes cimxml, SNMP and email handlers</li>

</dl>

<li>HandlerService Common code

for indication handler service</li>

Additional configuration:

<li>IndicationService Common

service functions for indication subscription processing</li>

<li>Listener Common code that

allows CIM Listeners to be created and connected.</li>

<li>Protocol Pegasus Client

HTTP/XML Protocol Modules depends </li>

<li>Provider Pegasus Provider

interface functions </li>

<li>ProviderManager Provider

Manager service that manages providers </li>

<li>ProviderManager2 Pluggable

Provider Manager service. Today this is not enabled by

default It will become the Pegasus standard provider manager

at some time in the future but for now, see the release notes if you

want to enable it.</li>

<li>Repository Pegasus

Repository Interfaces and Simple Repository tests

<ul>

<li>Tests for Repository

<li>For Unix builds, place $PEGASUS_HOME/lib on your LD_LIBRARY_PATH.

Functions </li>

</ul>

</li>

<li>Security Authentication

<li>For RedHat/SuSE/UL, edit /etc/ld.so.conf and add

and user support functions.</li>

$PEGASUS_HOME/lib.</li>

<li>Server Pegasus Server

Modules </li>

<li>WQL the WQL query language

interpreter.</li>

</ul>

<a name="bld">Step 4: Build the Pegasus runtime, test

files, test clients and repository</a>

Pegasus includes several make files that enable you to quickly build or

refresh the Pegasus runtime, test files, test client and the

repository. To use these make files, type "make" followed by one of the

supplied targets.

To build Pegasus, run the following commands from the root directory of

the Pegasus distribution:

<ol>

<li>Enter <tt>make</tt>

This builds all of Pegasus.

</li>

</ul>

<li>Enter <tt>make repository</tt>

This creates the repository, which is needed to serve data.

To create the additional namespaces that represent the test support you

can also execute "make testrepository".

</li>

<li>Providers Pegasus test and

<li> Enter <tt>make tests</tt>

required providers

This executes all the tests included with the Pegasus

<ul>

distribution, except the client/server tests. The client/server tests

<li>generic A number of

are executed separately from the above because

cross-platform providers </li>

they require the initiation of separate process for the Pegasus server

<li>IndicationConsumer - Provider that

and

consumes indications</li>

Pegasus client. To execute these tests, refer to the scripts in

<li>Linux - A number of linux

pegasus/mak/BuildMakefile. Refer to the prestarttests and

providers</li>

poststarttests in this file.

<li>ManagedSystem Providers

associated with managing the Pegasus System</li>

<li>slp - Provider for slp

service agent support</li>

<li>statistic - Providers for

Pegasus statistics.</li>

<li>sample Sample providers for

the major provider types.</li>

<li>testproviders </li>

</ul>

</li>

<li>Server Pegasus executable build </li>

</ol>

<li>Standard Includes - </li>

The following make targets are supported:

<li>test - Directory of end-end tests

that are regularly conducted on Pegasus</li>

<li>tools MU and other utilities

written for Pegasus support </li>

<li>Unsupported Code that is made

available but is not supported or included in the normal make. </li>

<li>WMIMapper Pegasus implementation

that provides mapping to Microsoft WMI objects. </li>

</ul>

Pegasus Run Time directory structure

(PEGASUS_HOME environment variable). Home directory for runtime. All

compiler, linker documentation creation, etc. are put here.

<ul>

<li>bin - Destination for executable

and DLL modules from Pegasus build. This directory should be make

public so that the test functions, clients, and cimserver can be

executed with minimum effort.</li>

<li>DevManualHTML - HTML output of the

Pegasus Manual. This is only created when the make file for this

manual is executed (doc/DevManual) and then contains the html

representing the document.</li>

<li>apidochtml - HTML output of the

creation of the public API document. This only exists when the make

file for the api document is executed (see doc/apidoc/Makefile)</li>

<li>lib - Destination for Pegasus LIB

modules </li>

<li>log - Standard location for

Pegasus Logs</li>

<li>obj - Destination for object

modules. Note that today, the trace file is located in the

PEGASUS_HOME directory, not in the log directory if Pegasus internal

tracing is enabled.</li>

<li>repository - This Directory

contains the created repository </li>

</ul>

<h1><a name="Pegasus Installation">Pegasus Installation</a> </h1>

Pegasus today is provided only as a source distribution. Note that

there is code for a Linux RPM distribution but the project is not yet

releasing binaies.

To install Pegasus, you must check it out using CVS (Common Version

System) or download a snapshot. You download, compile, and use it.

For the snapshot, the installation of Pegasus involves expanding the

snapshot distribution files, building the runtime, the test files and

test clients, and building the repository.

<h1><a name="Building Pegasus">Building Pegasus </a></h1>

1. Check that you have requisite programs (listed in Pegasus

Dependencies). These include GNU Make, MU.EXE (if using Windows), Flex,

and Bison (Flex and Bison only required if changes will be made to the

MOF compiler or WQL parser).

Be sure these are on the path.

2. Define the following three environment variables:

<ul>

<li>PEGASUS_ROOT - this should be the "pegasus" directory

you've pulled from CVS </li>

<li>PEGASUS_HOME - to point to a directory to contain output

binary files (e.g., set it to $HOME/pegasus_home). Then the output

will go into $HOME/pegasus_home/bin and $HOME/pegasus_home/lib </li>

<li>PEGASUS_PLATFORM - this must be set to a supported platform

identifier.</li>

</ul>

This identifier has the following form:

<Operating-System>_<Architecture>_<Compiler>

For example (Linux on IA32 platform using the GNU Compiler):

LINUX_IX86_GNU

For a complete list of platforms supported and platform support

keywords, refer to the platform make files found in directory <font

face="Courier New">pegasus/mak

</blockquote>

Note: if you plan on doing parallel builds, you might consider

setting PEGASUS_HOME to something like this:

$HOME/pegasus_home_LINUX_IX86_GNU

That way, the output of each build will be placed in its own

directory.

3. Now place $PEGASUS_HOME/bin on your path

and

Place $PEGASUS_HOME/lib on your LD_LIBRARY_PATH (for Unix only).

For RedHat/SuSE/UL, edit /etc/ld.so.conf and add $PEGASUS_HOME/lib

4. Change to the root of the Pegasus distribution and type "make"

(where make refers to GNU make).

5. Then create the repository, which is needed to serve data. "make

repository". Note that to create the additional namespaces, etc. that

represent the test support you can also execute "make testrepository:

6. To test the build type "make tests". The following make targets

are supported:

<ul>

<li><default> - Build everything. </li>

<li>clean - Clean out all objects, libs, and executables. </li>

Line 556

Line 557

<li>rebuild - clean, depend, <default> </li>

<li>world - depend, <default> </li>

</ul>

The Pegasus Client server tests are executed separately from the

above because they require the initiation of separate process for the

Pegasus server and Pegasus client. To execute these tests please refer

Generally the build commands are as follows:

to the scripts in pegasus/mak/BuildMakefile - refer to the prestarttests

and poststarttests.

For information on particular installation characteristics, tools,

etc. for each platform see the appropriate sections below:

Generally the build commands are as follows:

<ol>

<li>There is a Makefile in the Pegasus root directory. Simply

executing make in the Pegasus root directory will make everything.

"make rebuild" will clean and rebuild everything. The "make rebuild"

will also populate the repository with the current CIM Schemas. </li>

<li>To test a fresh release, go to the pegasus root and type "<font

<li>To test a fresh release, go to the pegasus root and type

face="Courier New">make world". This will build

"make world".  This will build

dependencies, build binaries, and then run all tests except the

Client/Server tests. </li>

<li>To execute the basic test suite that is shipped with pegasus

type "make tests". This also reinstalls the repository. Running

type  "make tests". This also reinstalls the repository. 

"make -s tests" suppresses extraneous output such as the enter/leave

Running "make -s tests" suppresses extraneous output such as the

directory messages. </li>

enter/leave directory messages. </li>

<li>"make clean" removes all object and library files from the

structure. </li>

<li>A new build system has been added to Pegasus where a new CVS

checkout is done, built, and tests are run. Do it by: "make -f

checkout is done,

mak/BuildMakefile cleanbuild" </li>

built, and tests are run. Do it by: "make -f mak/BuildMakefile

cleanbuild" </li>

</ol>

<h1><a name="Populate the Repository">Populating the Pegasus Repository</a> </h1>

<h2>

Before using Pegasus you must populate the repository.. The makefile

<a name="pop_peg_rep">Populate the Pegasus repository</a> </h2>

does it all for you, but in case you are wondering what it does or how

to do it manually:

Before using Pegasus you must populate the repository. Typically, this

is done during the buld process when you run the makefile. However, you

can also do it manually after the Pegasus has been built.

<ol>

<li>Register the MOF (Managed Object Format) file describing the

skeleton of the object. </li>

<li>Register a second MOF which only points out which lib*.so file to

be loaded when a specific object is activated. </li>

</ol>

This is done automatically for the providers included in Pegasus by

doing: make repository.

The 'make repository' in pegasus/Schemas does three things Runs MOF

The providers included with Pegasus are automatically entered into the

compiler (cimmofl) on: -Schema v2.7 Generates the CIM Schema v2.7 in the

repository

repository (skeleton of CIM objects) -PG_InterOp Internal to Pegasus

by running the following command: <tt>make repository</tt>

schema for operating (shutdown, add users, etc) CIM_Indication’s (SNMP,

Events, Alert, Threshold, etc) -PG_ManagedSystem Registers included CIM

Providers (libOSProvider.so, libDNSProvider.so, … ) in Pegasus (which

The 'make repository' in pegasus/Schemas does three things:

are located in src/Providers)

For more information about using the MOF compiler, refer to user's

manual on the openpegasus.org.

<h1><a name="Testing a Pegasus Installation">Testing a Pegasus

Installation</a></h1>

Pegasus includes an extensive set of test facilities as part of the

CVS enviromentthat can be executed including:

<ul>

<li>Test Clients - There are several clients that have been

<li>Generates the CIM Schema v2.8 in the repository (skeleton of CIM

built specifically to test Pegasus or parts of Pegasus including

objects). To do this, it runs the MOF compiler on the CIM schema: <tt>cimmofl

TestClient, Client, CLI, ipinfo, osinfo, WbemEsec, etc. See the

-Schema v2.8</tt> </li>

src/Clients directory for more information. These programs require a

<li>Sets up operations (shutdown, add users, etc) and CIM indications

server complete with repository to be running. Note that some of these

(SNMP, Events, Alert, Threshold, etc)

tests use classes and instances that are only installed with the

internal to the Pegasus schema by running the following command: <tt>cimmofl

"make testrepository" functions including test namespaces and extra

-PG_InterOp</tt> </li>

classes and instances in those namespaces and additional providers

<li>Registers included CIM Providers (libOSProvider.so,

from the providers/sample and proviers/testproviders directories.</li>

libDNSProvider.so, … ) in Pegasus (which are located in src/Providers)

<li>Sample and test providers - Test providers exist for the

by running: <tt>cimmofl -PG_ManagedSystem</tt> </li>

major provider types in the providers/sample directories and the

</ul>

providers/testProviders directory</li>

<h2>

<li>Unit Tests - Most Pegasus functions include unit tests for

<a name="reg_prov">Registering

the functions. These are normally executed with the "make tests"

Providers in the Pegasus Environment</a></h2>

command which can be executed at many different levels of the source

tree from the top level to execute all of the unit tests to

Pegasus registers providers with a set of provider registration

individual directories. Usually the unit test functions can be found in

test directories immediately below their corresponding source code

(i.e common/tests is the unit test functions for the common

directory). Unit tests are executed without the server being

operational and normally do not require the existence of a Class

repository.</li>

<li>An end-to-end Test Suite - the directory "test" contains a

set of operations tests that cover the major CIM operations. See

the make file TestMakefile in the PEGASUS_ROOT directory to execute

these tests. This set of tests executes an extensive set of fixed

tests and compares the results against predefined results.</li>

</ul>

<h1><a name="Registering Providers in the Pegasus Environment">Registering

Providers in the Pegasus Environment</a></h1>

Pegasus registers providers with a set of provider registration

classes, not using the provider qualifier as is done in most DMTF CIM

CIMOM implementations today. This set of classes is close to but not

exactly the same as the current DMTF definition (See the DMTF Interop

schema, experimental versions starting with 2.6). This will be

harmonized in the future when the DMTF scheme is moved to final status.

harmonized in the future when the DMTF scheme is moved to final

Registration is performed by defining a MOF for the instances of the

status.

Registration is performed by defining a MOF for the instances of the

registration classes that represent the porvider module, providers,

classes, etc. to be registered. The easiest way to create a new

classes, etc. to be registered.  The easiest way to create a new

registration today is to copy from one of the existing registration

MOFs. See the providers/sample/load directory for examples of several

MOFs.  See the providers/sample/load directory for examples of

registration instance implementations that do work with Pegasus today.

several registration instance implementations that do work with Pegasus

<h1><a name="The MU Utility">The MU Utility </a></h1>

today.

In order to provide a consistent build structure across multiple

<h2>

platforms, we developed a small utility to provide a consistent set of

<a name="bld_rpms">Building RPMs for Pegasus</a>

small utilities across these platforms. The MU utilityis a simple

</h2>

utility that contains many commands. For example:

C:\> mu rm myfile.cpp yourfile.cpp

The source distribution includes a script you can use to create an RPM

You may type "mu" to get a list of valid commands. Here are some of

for Pegasus. To do this, your environment must meet the following

them:

requirements:

rm, rmdirhier, mkdirhier, echo, touch, pwd, copy, move, compare

depend

<ul>

The MU utility supports globing (expansion of wildcards) so you can

<li>The root directory for Pegasus must be "/Pegasus-1.0" </li>

do things like this:

<li>Your environment variables must be set, as described in <a

C:\> mu rm *.obj *.exe

href="#set_envt_var">Set evironment variables</a>. </li>

MU is required to build under the Windows environment. MU is

<li>You must be logged in as the root user.</li>

available as part of the distribution of Pegasus.

</ul>

<h1><a name="Notes about Building Pegasus on Linux">Notes about

Building Pegasus on Linux </a></h1>

No problem. Just make sure you have the environment variables set

To create the RPMs, run the script <tt>rpmBuild</tt> from the root

(PEASUS_HOME, PEGASUS_ROOT, PEGASUS_PLATFORM. For 32 bit linux, the

directory of the source distribution. For example: <tt>.

defintion of PEGASUS_PLATFORM is normally LINUX_IX86_GNU.

/usr/source/pegasus-1.0/rpmBuild</tt>

<h1><a name="Notes about Building Pegasus on Mac OS X/Darwin">Notes

about Building Pegasus on Mac OS X/Darwin</a><a

This will result in and RPM file names <tt>pegasus<version

name="Notes about Building Pegasus on Linux"> </a></h1>

number>.rpm</tt>.

No problem. Just make sure you have the environment variables set

(PEASUS_HOME, PEGASUS_ROOT, PEGASUS_PLATFORM. For Mac OS X/Darwin, the

defination of PEGASUS_PLATFORM is

Note: After you install using the install using the

DARWIN_PPC_GNU.

PRM, you must crate and populate teh repository manually.

<h1><a name="Notes about Building Pegasus with SSL">Notes about

Question: I'm still working on this procedure (I haven't gotten

Building Pegasus with SSL </a></h1>

it to work yet).

To build with SSL you need the OpenSSL libraries and header files.

They are NOT distributed with Pegasus. Make sure you have them in a

standard directory so Pegasus can find them. If that's not the case, set

<h2><a name="note_bld_peg_lnx">Notes about

the environment variable OPENSSL_HOME= to point where your OpenSSL

Building

installation is.

Pegasus on Linux </a></h2>

Also have the PEGASUS_HAS_SSL=yes variable set. Then just run 'make'

in Pegasus directory and you will have Pegasus with SSL enabled. See

Pegasus supports many distributions of Linux. Refer to <a

section "Creating SSL certificates" for more information of how to use

href="#peg_sup_plat">Pegasus Supported Platforms</a>

SSL.

for more information.

<h1><a

name="Building Pegasus on Windows 2000 or Windows XP With Microsoft Visual C++">Building

To build Pegasus on Linux, ensure that you you have the environment

Pegasus on Windows 2k or Windows XP with Microsoft Visual C++ </a></h1>

variables set (PEGASUS_HOME, PEGASUS_ROOT, PEGASUS_PLATFORM.  For

Use of Windows 2000 SP3 or later is recommended. Pegasus is

32 bit linux, the definition of PEGASUS_PLATFORM is normally

regularly tested on both Windows 2000 and Windows XP using the Microsoft

LINUX_IX86_GNU.

compilers.

<h2><a name="bld_peg_win">Notes

on building Pegasus on Windows 2k or Windows XP with Microsoft Visual

C++ </a></h2>

Use of Windows 2000 SP3 or later is recommended.  Pegasus is

regularly tested on both Windows 2000 and Windows XP using the

Microsoft compilers.

Today we build Pegasus on Windows using a set of make files

contained in the source distribution, the Microsoft compilers (DevStudio

contained

5.x is not supported, Visual Studio 6.0, SP5 is supported) and the

in the source distribution, the Microsoft compilers (DevStudio 5.x is

GNUMAKE make utility. Note that you MUST have the Pegasus <a

not supported, Visual Studio 6.0, SP5 is supported) and the GNUMAKE

href="#The%20MU%20Utility">mu.exe </a>utility compiled and available

make utility.  Note that you MUST have the Pegasus <a

href="#mu_utility">mu.exe </a>utility compiled and available

before trying to compile Pegasus on the normal windows platform. The

following is the basic setup steps for the environment.

following is the basic setup steps for the environment.

Setup the environment variables and path for the Micrososft Visual C

compiler. Typically this can be done by running the VCVARS32.BAT file

compiler.

supplied with Microsoft Visual C++. (contained in the same directory as

Typically this can be done by running the VCVARS32.BAT file supplied

cl.exe).

with Microsoft Visual C++. (contained in the same directory as cl.exe).

For Windows, try the following for an example environment:

<pre>REM call the standard Microsoft .bat for VC 6 setup. call 'C:/Program Files/Microsoft Visual Studio/VC98/Bin/Vcvars32.bat' REM Set debug to something if you want compile in debug mode set PEGASUS_DEBUG=true REM set PEGASUS_ROOT to top of source tree set PEGASUS_ROOT=C:/cimom/pegasus REM set PEGASUS_HOME to where you want repository and executables set PEGASUS_HOME=%PEGASUS_ROOT% REM setup the path to the runtime files. set path=%path%;%PEGASUS_HOME%/bin </pre>

<pre>REM call the standard Microsoft .bat for VC 6 setup. call 'C:/Program Files\Microsoft Visual Studio\VC98\Bin\Vcvars32.bat' REM Set debug to something if you want compile in debug mode set PEGASUS_DEBUG=true REM set PEGASUS_ROOT to top of source tree set PEGASUS_ROOT=C:/cimom/pegasus (Note: <span

</blockquote>

class="norm">The '/' characters are intentional and required by the Pegasus build system) REM set PEGASUS_HOME to where you want repository and executables set PEGASUS_HOME=%PEGASUS_ROOT% REM setup the path to the runtime files. set path=%path%;%PEGASUS_HOME%\bin </pre>

<h1><a name="Installing the Pegasus HTML Test Client">Installing the

Pegasus HTML Test Client</a></h1>

This is a separate test tool that allows Pegasus requests to be

initiated from any WEB browser and that uses a WEB browser, CGI scripts

and HTML pages for the formatting and connections. It requires a WEB

server, etc. The instructions for setting up this environment are

maintained in a separate readme in the CGI directory.

<h1><a name="Development with Pegasus and Pegasus Tools">Development

with Pegasus and Pegasus Tools</a></h1>

ATTN: This section needs to be completed. It should reference the

more complete documentation.

<h1><a name="Commands">Commands</a></h1>

The manpages for each of the commands are in rpm/manLinux/man1.Z

directory (on CVS)

To see simple help for each of the commands, use the "-h" flag.

</blockquote>

<h1><a name="Creating SSL certifications">Creating SSL certifications </a></h1>

Please follow section <a

href="#Notes%20about%20Building%20Pegasus%20with%20SSL">Notes on

building Pegasus with SSL</a> before embarking on this endeavour.

Type these commands in your shell to create the SSL certifications. The

PEGASUS_ROOT and PEGASUS_HOME have to be set to your respective

installation and source directory.

<pre>CN="Common Name" EMAIL="test@email.address" HOSTNAME=`uname -n` sed -e "s/$CN/$HOSTNAME/" \ -e "s/$EMAIL/root@$HOSTNAME/" $PEGASUS_ROOT/ssl.cnf \ > $PEGASUS_HOME/ssl.cnf chmod 644 $PEGASUS_HOME/ssl.cnf chown bin $PEGASUS_HOME/ssl.cnf chgrp bin $PEGASUS_HOME/ssl.cnf /usr/bin/openssl req -x509 -days 365 -newkey rsa:512 \ -nodes -config $PEGASUS_HOME/ssl.cnf \ -keyout $PEGASUS_HOME/key.pem -out $PEGASUS_HOME/cert.pem cat $PEGASUS_HOME/key.pem $PEGASUS_HOME/cert.pem > $PEGASUS_HOME/server.pem rm $PEGASUS_HOME/key.pem $PEGASUS_HOME/cert.pem cp $PEGASUS_HOME/cert.pem $PEGASUS_HOME/client.pem </pre>

</blockquote>

<h1><a name="Configuring SSL">Configuring Pegasus to use SSL</a></h1>

Please follow section <a

href="#Notes%20about%20Building%20Pegasus%20with%20SSL">Notes on

building Pegasus with SSL</a> and <a

href="#Creating%20SSL%20certifications">Creating SSL certifications</a>

before embarking on this endeavour.

To configure Pegasus to take advantage of SSL, configure CIMServer to

have the following configuration options set to:

<pre> sslTrustFilePath=client.pem sslCertificateFilePath=server.pem sslKeyFilePath=file.pem httpsPort=5989 enableHttpsConnection=true </pre>

</blockquote>

using the cimconfig utility:

<pre> cimconfig -p -s enableHttpsConnection=true </pre>

</blockquote>

(The client.pem and server.pem are the certifications files created per

the steps in the earlier section). For good riddance you might consider

closing down the cleartext 5988 port. Modify your CIMServer

configuration to include:

<pre> enableHttpConnection=false </pre>

</blockquote>

using cimconfig.

<h3>

<h1><a name="Configuring PAM">Configuring Pegasus to use PAM</a></h1>

<a name="mu_utility">The MU Utility </a></h3>

In order to use PAM Authentication you have to compile Pegasus with

one extra enviroment flags:

In order to provide a consistent build structure across multiple

platforms, we

<pre> PEGASUS_PAM_AUTHENTICATION=1 </pre>

developed a small utility to provide a consistent set of small

</blockquote>

utilities

You can also set the PEGASUS_ALWAYS_USE_PAM=1 flag to disable

across these platforms. The MU utilityis a simple utility that contains

Pegasus password authentication using a flag text-file (recommended).

many

After compiling (refer to section <a href="#Building%20Pegasus">Building

commands. For example:

Pegasus </a>for details), follow these two important steps:

C:\> mu rm myfile.cpp yourfile.cpp

You may type "mu" to get a list of valid commands. Here are some

of them:

rm, rmdirhier, mkdirhier, echo, touch, pwd, copy, move, compare depend

The MU utility supports globing (expansion of wildcards) so

you can do things like this:

C:\> mu rm *.obj *.exe

MU is required to build under the Windows environment. MU is

available as part

of the distribution of Pegasus.

<h2><a name="note_bld_peg_ssl">Notes about

Building Pegasus with SSL

</a></h2>

To build with SSL you need the OpenSSL libraries and header files. They

are NOT distributed with Pegasus. Make sure you have them in a standard

directory so Pegasus can find them. If that's not

the case, set the environment variable OPENSSL_HOME= to point where

your OpenSSL

installation is.

Also have the PEGASUS_HAS_SSL=yes variable set. Then just run 'make'

in Pegasus

directory and you will have Pegasus with SSL enabled. See "Creating SSL

certificates" below for more information on how to use SSL.

<h3><a name="crt_ssl_cert">Creating SSL certifications </a></h3>

Type these commands in your shell to create the SSL certifications.

The PEGASUS_ROOT and PEGASUS_HOME have to be set to your respective

installation and source directory.

Set the sslKeyFilePath to

key.pem.  Set the sslCertificateFilePath to cert.pem.  To

create a client truststore to validate the server against, copy the

server's certificate into the client truststore, client.pem.

<pre

style="font-style: italic; font-family: courier new,courier,monospace; margin-left: 40px;">CN="Common Name" EMAIL="test@email.address" HOSTNAME=`uname -n` sed -e "s/$CN/$HOSTNAME/" \ -e "s/$EMAIL/root@$HOSTNAME/" $PEGASUS_ROOT/ssl.cnf \ > $PEGASUS_HOME/ssl.cnf chmod 644 $PEGASUS_HOME/ssl.cnf chown bin $PEGASUS_HOME/ssl.cnf chgrp bin $PEGASUS_HOME/ssl.cnf /usr/bin/openssl req -x509 -days 365 -newkey rsa:512 \ -nodes -config $PEGASUS_HOME/ssl.cnf \ -keyout $PEGASUS_HOME/key.pem -out $PEGASUS_HOME/cert.pem cp $PEGASUS_HOME/cert.pem $PEGASUS_HOME/client.pem</pre>

Note:  key.pem is

sslKeyFilePath. cert.pem is sslCertificateFilePath

<h1>

<a name="test">Testing a Pegasus Installation</a></h1>

Pegasus includes an extensive set of test facilities as part of the CVS

enviroment, including:

<ul>

<li>Test Clients - There are several clients that have been

a). Copy the rpm/wbem file in-to /etc/pam.d directory. This

built specifically to test Pegasus, or parts of Pegasus, including

notifies PAM what kind of libraries to use when authenticating

TestClient, Client, CLI, ipinfo, osinfo, WbemEsec, etc. See the

Pegasus.

src/Clients directory for more information. These programs require a

</ul>

server complete with repository to be running.  Note that some of

<ul>

these tests use classes and instances that are only installed with the

b). Modify CIMServer configuration options:

"make testrepository" functions including test namespaces and extra

classes and instances in those namespaces and additional providers from

<pre> usePAMAuthentication=true enableAuthentication=true </pre>

the providers/sample and proviers/testproviders directories. </li>

</blockquote>

<li>Sample and test providers -  Test providers exist for

And if you want to allow 'root' to login (*not recommended*)

the major provider types in the providers/sample directories and the

providers/testProviders directory </li>

<pre> enableRemotePrivilegedUserAccess=true </pre>

<li>Unit Tests - Most Pegasus functions include unit tests for

</blockquote>

the functions.  These are normally executed with the "make tests"

using the cimconfig utility, such as:

command which can be executed at many different levels of the source

tree from the top level to execute all of the unit tests to individual

<pre> cimconfig -p -s usePAMAuthentication=true </pre>

directories.  Usually the unit test functions can be found in test

</blockquote>

directories immediately below their corresponding source code

</ul>

(i.e  common/tests is the unit test functions for the common

directory). Unit tests are executed without the server being

operational and normally do not require the existence of a Class

repository. </li>

<li>An end-to-end Test Suite - the directory "test" contains a

set of operations tests that cover the major CIM operations.  See

the make file TestMakefile in the PEGASUS_ROOT directory to execute

these tests.  This set of tests executes an extensive set of fixed

tests and compares the results against predefined results.</li>

</ul>

The user is authenticated using HTTP Basic method, thererfore it is

strongly suggested you use SSL connection instead of normal HTTP

<h2><a name="inst_peg_html">Installing the

connection. Refer to section <a href="#Configuring%20SSL">Configuring

Pegasus HTML Test Client</a></h2>

Pegasus to use SSL</a> for more details on creating and using SSL keys.

This is a separate test tool that allows Pegasus requests to be

<h1><a name="Testing with ICU enabled">Testing with ICU enabled</a></h1>

initiated from

any WEB browser and that uses a WEB browser, CGI scripts and HTML pages

for

the formatting and connections. It requires a WEB server, etc. The

instructions for setting up this environment are maintained in a

separate readme in the CGI directory.

<h2><a name="test_icu">Testing with ICU enabled</a></h2>

ICU (International Components for Unicode) refers to the set of

libraries that Pegasus uses to run globalized. For example: these

libraries that

libraries are used to load messages in different languages, format

Pegasus uses to run globalized. For example: these libraries are used

currency and numbers according to a specific locale etc. In order to

enable globalization in Pegasus, Pegasus must be built with ICU enabled,

load messages in different languages, format currency and numbers

ie. the right environment variables must be set prior to running

according to

"make". Refer to the GlobalizationHOWTO.htm in the docs directory for

a specific locale etc. In order to enable globalization in Pegasus,

details. That said, when users run "make poststarttests" to verify the

Pegasus

integrity of a Pegasus download, a series of tests are run that require

must be built with ICU enabled, ie. the right environment variables

the cimserver to be running. These tests currently depend on specific

must be

set prior to running "make". Refer to the GlobalizationHOWTO.htm in the

docs

directory for details.

When users run "make poststarttests"

to verify the integrity of a Pegasus download, a series of tests are

run that

require the cimserver to be running. These tests currently depend on

specific

messages returned from the server. When ICU is enabled, all messages

come from the resource bundles and these usually do not match the

hardcoded default messages within Pegasus. These hardcoded default

messages are what the various test programs expect in order to complete

successfully. If the ICU enabled server is started without disabling

successfully. If the ICU enabled server is started without

message loading from the bundles, "make poststartests" will fail. In

disabling message loading from the bundles, "make poststartests" will

order to run "make poststarttests" successfully with ICU enabled, an

fail.

In order to run "make poststarttests" successfully with ICU enabled, an

environment variable called PEGASUS_USE_DEFAULT_MESSAGES must exist

prior to starting the server. Once this is defined, when the cimserver

prior to

starts, all messages generated will be the default hardcoded messages.

starting the server. Once this is defined, when the cimserver starts,

This will enable "make poststarttests" to complete successfully. Once

all

"make poststarttests" is complete, you should stop the cimserver and

messages generated will be the default hardcoded messages. This will

then undefine PEGASUS_USE_DEFAULT_MESSAGES. If this variable is left

enable

defined, Pegasus will not be able to load messages using ICU resource

"make poststarttests" to complete successfully. Once "make

bundles.

poststarttests" is

<h1><a name="Pegasus Documentation">Pegasus Documentation</a></h1>

complete, you should stop the cimserver and then undefine

The documentation is currently in preparation. Much of Pegasus is

PEGASUS_USE_DEFAULT_MESSAGES. If this variable is left defined, Pegasus

documented in the PEGASUS PEPs which are the basis for approval of

will not be able to load messages

Pegasus functionality, changes, plans, etc. These documents are openly

using ICU resource bundles.

available on the PEGASUS web site. The preliminary documentation is not

provided with this release. The current documentation is maintained

When

both as a manual created under the tool DOC++ in the runtime

running the make tests command with ICU enabled, the PEGASUS_MSG_HOME

subdirectory manual/html (see doc/devManual to create), as an api

environment variable must be set to the home directory where the ICU

document also creatable from the source tree (see doc/apidoc) and as

resource bundles are built. By default the resource bundles are built

other miscellaneous documentation in the doc directory. Also there is a

into directories below PEGASUS_HOME/msg, so that should be the setting

set of release notes. Normally the release notes for the current release

for PEGASUS_MSG_HOME.

are available in the root source directory of CVS.

Note that the Pegasus WEB site at The Open Group will be the source

-------------------------------------------------------------------------------------------------------------------------------------

of most documentation in the future and today is the source of most

discussion and design documentation.

<h1><a name="Participate!">Participate!</a></h1>

Hewlett-Packard Development Company, L.P.; IBM Corp.; The Open Group;

We are looking for people who want to join the Pegasus work group

VERITAS Software Corporation

and contribute to effort of getting this Pegasus off the ground. Please

join the mailing list by visiting www.openpegasus.org, and click on

Permission is hereby granted, free of charge, to any

Mailing Lists.

person obtaining a copy  of this software and associated

documentation files (the "Software"), to deal in the Software without

restriction, including without limitation the rights to use, copy,

modify, merge, publish, distribute, sublicense, and/or sell copies of

the Software, and to permit persons to whom the Software is furnished

to do so, subject to the following conditions:

THE ABOVE COPYRIGHT NOTICE AND THIS PERMISSION NOTICE

SHALL BE INCLUDED IN ALL COPIES OR SUBSTANTIAL PORTIONS OF THE

SOFTWARE. THE SOFTWARE IS PROVIDED  "AS IS", WITHOUT WARRANTY OF

ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE

WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND

NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE

LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION

OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION

WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

<big><big>------------------------End

Document-------------------------

</big></big>

</body>

</html>

Legend:

Removed from v.1.6
changed lines
	Added in v.1.7

No CVS admin address has been configured