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.11

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

version 1.11, 2006/02/18 03:27:11

Line 1

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

//%2006////////////////////////////////////////////////////////////////////////

// Company, L.P.; IBM Corp.; The Open Group; Tivoli Systems.

// IBM Corp.; EMC Corporation, The Open Group.

// IBM Corp.; EMC Corporation; VERITAS Software Corporation; The Open Group.

// EMC Corporation; VERITAS Software Corporation; The Open Group.

// EMC Corporation; Symantec Corporation; The Open Group.

// Permission is hereby granted, free of charge, to any 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.

//==============================================================================

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

<html>

<head>

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

Line 9

Line 39

</head>

<body>

Pegasus Enhancement Proposal (PEP)

PEP #: 103

PEP #: 235

Title: OpenPegasus

Version 2.3 Release Readme file

Version 2.5 Release Readme file

Version: 1.1

Version: <span

Created: 12

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

November 2003

Authors: Karl

Created: 6 Sept

Schopmeyer, Konrad Rzeszutek

2005

Status: draft

Authors: Warren

Grunbok

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 64

</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 style="vertical-align: top; text-align: center;">1.1

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

</td>

</tr>

<td style="vertical-align: top; text-align: center;"> 13,

<tr>

Sept 2005

</td>

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

Grunbok/Roger Kumpf

</td>

<td style="vertical-align: top; text-align: center;">Updates

based on Architecture team review

</td>

</tr>

<tr>

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

</td>

<td style="vertical-align: top;">22, Sept 2005

</td>

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

</td>

<td style="vertical-align: top;">Updates from posted comments to

1.1

</td>

</tr>

<tr>

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

</td>

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

</td>

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

Grunbok

</td>

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

to -

</td>

</tr>

<tr>

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

</td>

<td style="vertical-align: top;">26, Sept 2005

</td>

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

</td>

<td style="vertical-align: top;">Cleanup on example lists

</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 OpenPegasus Version 2.5.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.

introduction to OpenPegasus.

<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 hosted by The Open Group

release version 2.3.0

Table of Contents

STATUS: Revised Sept 2005 for  Pegasus release version

<a

2.5.0 

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

- Draft

<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_sup_plat">Pegasus Supported Platforms</a>

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

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

<a

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

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

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

<a

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

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

</blockquote>

Structure</a>

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

<a

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

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

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

<a

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

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

software</a>

<a

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

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

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

<a

and repository</a>

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

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

Providers</a>

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

<a

<a href="#note_bld_peg_lnx">Notes

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

about Building Pegasus on Linux</a>

<a

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

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

<a href="#bld_peg_win">Building

Building Pegasus on Linux</a>

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

<a

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

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

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

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

</blockquote>

<a

</blockquote>

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

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

building Pegasus with SSL</a>

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

<a

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

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

</blockquote>

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

<hr>

<a

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

the Pegasus HTML Test Client </a>

<a

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

with Pegasus and Pegasus Tools</a>

<a

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

<a

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

<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 implementation 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

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

consistent with the DMTF CIM and WBEM specifications except for 

license.

exceptions

Pegasus is being developed and maintained under the auspices of The

noted in the documentation.

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

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

OpenPegasus includes components for:

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

<ol>

users.

<li>DMTF compliant CIMServer that processes CIM operations, CIM

Indications, and

includes class and instance repositories and interfaces for creating

CIM

Providers and CIM Clients.</li>

<li>Provider interfaces so that providers may be build in multiple

languages (i.e.

C++, C, Java).</li>

<li>A number of CIM providers.</li>

<li>A mof compiler.</li>

<li>A number of CIM CLients to provide usage examples, CIMServer

test functions,

and administration functions.</li>

<li>More complete information on the exact functions

and their functional state is available from the release notes for each

OpenPegasus release.</li>

</ol>

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

license.

OpenPegasus is being developed and maintained under the auspices of

The

Open

Group.  OpenPegasus is maintained under the license defined in the

doc

directory of this release.  The specific file is: <font

style="color: rgb(0, 0, 0);">pegasus/doc/license.txt.

This licensing is intended to support as

wide a

distribution as possible with minimal demands on the users.

More information on this project, access to the CVS, and

documentation on Pegasus are available from the OpenGroup WEB site.

documentation on

<a href="http://www.opengroup.org">http://www.openpegaus.org</a>

Pegasus are available from the OpenGroup WEB site.

There are a number of separate documents representing the status and

each release of Pegasus

<a target="blank"

<ul>

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

<li>What's new for this release - See the PEPs (Pegasus Enhancement

<h2><a name="avail_of_peg">Availability of Pegasus</a></h2>

Procedures) release notes on the Pegasus web site and duplicated in

the source top level directory</li>

<li>What's Broken - BUGS - See the ReleaseNotes for this release in

<ol>

the CVS and the web site as a Pegasus PEP.</li>

Pegasus can be obtained via any of the following:

</ul>

<ol>

The release notes are available on the WEB site as Pegasus PEP

<li>Released tarballs (see <a

documents and in the CVS for each release.

href="http://www.openpegasus.org/protected/page.tpl?CALLER=index.tpl&ggid=392">Relase

tarballs link</a>)</li>

<tbody>

<li>CVS (See <a

<tr>

href="http://www.openpegasus.org/protected/page.tpl?CALLER=index.tpl&ggid=667">CVS

<td width="42%">Release</td>

code repository</a> for

<td width="58%">Release Notes PEP</td>

more information.)</li>

</tr>

<li>Linux RPMs. See

<tr>

(<a

href="http://www.openpegasus.org/protected/page.tpl?CALLER=index.tpl&ggid=667">RPM

link</a> for

</tr>

more information

<tr>

)</li>

</ol>

</ol>

</tr>

NOTE: The Linux RPM reference is for 2.4.1 because that is all we

<tr>

have. We

need a general page to get to the RPMs, not one per release.

</tr>

<tr>

</tr>

</tbody>

</table>

<h1><a name="Availability of Pegasus">Availability of Pegasus</a></h1>

Pegasus is distributed as open source under the MIT open-source

license. The distribution is available via CVS and snapshot images in

tar and zip file formats on the web site. The source code from CVS can

tar and zip file formats on the web site.

be found at the following Open Group CVS server;

The source code from CVS can be found at the following Open Group CVS

cvs.opengroup.org:/cvs/MSB

server;

using the password authenticating server option (pserve).

Anonymous access for read is with the name and password "anon" as

CVS

follows:

write accounts are managed by Martin Kirk of The Open Group

(<a href="mailto:%28k.m.kirk@opengroup.org">m.kirk@opengroup.org</a>)

<font

face="Courier New">%export

CVSROOT=:pserver:anon@cvs.opengroup.org:/cvs/MSB

<h2><a name="peg_sup_plat">Pegasus Supported Platforms</a></h2>

<font

face="Courier New">%cvs login

Pegasus is regularly tested against a variety of platforms by the

</blockquote>

development group.  The results of the nightly tests can be found

When requested, enter the password "anon". The source tree is in the

here: <a

directory pegasus. To check out the complete Pegasus source tree just

href="http://cvs.opengroup.org/cgi-bin/pegasus-build-status.cgi">Nightly

type:

test status</a> .  The Release notes provides additional details

cvs co pegasus

regarding the platforms. <a

A Pegasus directory will be created under the current directory and

href="http://www.openpegasus.org/pp/protected/revdoc.tpl?CALLER=revdocuments.tpl&grid=1692">

populated with the complete source tree and documentation. To get the

PEP 230</a> is the release notes PEP for 2.5.

latest updates after a checkout just type this from Pegasus root:

cvs update -d

<h2><a name="peg_dep">Pegasus Dependencies</a></h2>

Active contributors to Pegasus have write access to the CVS

repository. If you are interested in contributing back to the Pegasus

We have worked to minimize the dependence of Pegasus on other software

project, (i.e. write (checkin) access to CVS) please request access from

packages and tools. Currently Pegasus has the following dependencies:

either Martin Kirk (m.kirk@opengroup.org) or Karl Schopmeyer <a

href="mailto:%28k.schopmeyer@opengroup.org">(k.schopmeyer@opengroup.org</a>).

<h1><a name="Pegasus Major Components">Pegasus Major Components</a></h1>

The major components of Pegasus are:

<ul>

<li>Pegasus Server - WBEM/CIM Server with interfaces for

providers and clients </li>

<li>Pegasus Repositories - Today Pegasus provides a defined

class repository interface and a simple file based class repository.

It also includes an instance repository. Note that these repository

were created for functionality, not efficieny. It is expected that

they will be replaced with other implementations of the respository

function as the need arises. </li>

<li>Pegasus Client Library - Tools for building Pegasus clients

based on the Pegasus C++ interfaces and using the WBEM HTTP/XML

protocols or directly interfacing with Pegasus. </li>

<li>Pegasus Test Clients - Simple test clients being developed

as part of the Pegasus development process. These can be seen in the

src/Clients directory and its subdirectories </li>

<li>Pegasus HTML Test Client - To aid in testing we created a

test client for Pegasus that uses a WEB server (ex. Apache) with a

set of CGI modules and HTML to allow the entry of Pegasus operations

from a WEB browser as forms and the receipt of the response as WEB

pages. This has proven useful as a test tool and can be used for a wide

variety of demonstrations. </li>

<li>Pegasus Provider Library - Tools for building Pegasus

providers using the Pegasus C++ interfaces. </li>

<li>Pegasus Providers - Providers to illustrate the use of

Pegasus services including providers for test and demonstration. </li>

<li>Pegasus Control Providers - Common services for use by

other Pegasus components to extend Pegasus capabilites. </li>

<li>Pegasus MOF Compiler - There standalone compiler

(cimmofl) for MOF files that can be used to install MOF into the

Pegasus schema repository and also to check syntax. There is also a

compiler that operates as a Pegasus client(cimmof) There is also a

tool to extract the MOF from the repository. </li>

</ul>

<h1><a name="Pegasus Supported Platforms">Pegasus Supported Platforms</a></h1>

Pegasus is regularly tested against a variety of platforms by the

development group. The set of platforms and exact set of compilers for

any given release is documented in the Release notes for that release

(see the CVS source tree root directory or the Pegasus PEP defining the

ReleaseNotes for any particular release).

Generally Pegasus is supported on the following Platforms and

Compilers.

<tbody>

<tr>

<td width="169" bgcolor="#99ff99">Platform and OS</td>

<td width="556" bgcolor="#99ff99">Compilers</td>

</tr>

<tr>

<td width="556">VisualAge C++ Version</td>

</tr>

<tr>

</tr>

<tr>

<td width="169">Linux Itanium</td>

</tr>

<tr>

<td width="169">Linux IA-32</td>

<td width="556">gcc (versions 2.9x and 3.xx)</td>

</tr>

<tr>

<td width="169">Windows 2000</td>

<td width="556">Microsoft Visual C++ Ver 6 and Microsoft .Net

compiler Version 7</td>

</tr>

<tr>

<td width="169">Windows XP</td>

<td width="556">Microsoft Visual C++ Ver. 6 and Microsoft .Net

compiler Version 7</td>

</tr>

<tr>

<td width="169">Mac OS X/Darwin PPC</td>

<td width="556">gcc (version 3.3)</td>

</tr>

</tbody>

</table>

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

We have worked to minimize the dependence of Pegasus on other

software packages and tools. Currently Pegasus has the following

dependencies:

1. GNUMAKE - To simplify the building of Pegasus across

multiple platforms we have standardized on a set of build tools

multiple platforms we

including: GNUMAKE. We are using GNUMAKE 3.79.1 successfully both in

have standardized on a set of build tools including: GNUMAKE. We are

Windows and Linux environments.

using GNUMAKE 3.79.1 successfully both in Windows and Linux

environments.

GNUMAKE is available from :

<a target="blank"

NOTE: A set of the required tools for windows platforms is

href="http://www.gnu.org/">http://www.gnu.org</a>

available on the openpegasus web site.

2. MU.EXE - To minimize the difference between Linux and

2. FLEX and BISON - These tools were used to develop the

Windows for GNUMAKE, we have created a utility called MU.exe. This

MOF

utility is required for Pegasus make with ONLY Windows environment. It

compiler and WQL

is provided as an alternative to requiring a number of UNIX utilities

parser.  <font

(SH, RM, etc.) on the windows platform and effectively provides the

style="color: rgb(0, 0, 0);">These tools are required only for

functions of these utilities that GNUMAKE needs. MU is not required on

development of the parsers, not for building Pegasus.

UNIX or LINUX platforms.

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

NOTE: The binary for MU.EXE is not distributed in the Pegasus bin

combination of text files

directory. You must build it separately. MU source code is part of the

and the Pegasus header files themselves. This documentation is

distribution in the directory src/utils/MU with its own make file. You

formatted with DOC++ and GAWK.   <font

must compile MU before you initiate the Pegausu make.

style="color: rgb(0, 0, 0);">These tools are required to build the

NOTE: A copy of the binary is made available as a zip file on the

interface documentation set.

Pegasus WEB site.

Again, MU is used ONLY if you are using Windows.

4. ICU Internationalization libraries - These libraries are

3. FLEX and BISON - These tools were used to develop the MOF

used as the basis for message catalogs for message

compiler and WQL parser. Anybody intending to recompile the compiler or

internationalization. See the ICU website

parser from scratch will be required to have these tools. They are only

(http://oss.software.ibm.com/icu/) for more information on these

required if changes need to be made to the files for parsing and

libraries

compiling.

5. OpenSSL - If it

4. DLCOMPAT - dlcompat is a dlopen(3) et.al. compatibility

is intended to use SSL on the

library for Mac OS X/Darwin.

communication protocol, the OpenSSL libraries are required.

NOTE: The dlcompat is not distributed with pegasus

NOTE: A set of the required

source.

tools for windows platforms is available on the openpegasus web

site.  <a href="../Pegasus24/www.openpegasus.org">www.openpegasus.org</a>

dlcomapt is available from :

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

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

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 "--help" flag.

Here is a list of useful

commands:

<span

style="font-family: times new roman; font-weight: bold;"><span

class="norm">Some of

the basic commands:

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

NOTE: Refer to the admin guide in pegasus/doc/Admin_Guide_Release.pdf

X/Darwin.

for

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

more information about administering the Pegasus CIMServer.

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

<ul>

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

<li>cimserver daemon=true  (Start the server

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

cimserver)</li>

core team will be recreating documentation.

<li>cimserver -s  (Shuts down the cimserver)</li>

6. ICU Internationalization libraries - These libraries are

<li>cimserver traceLevel=4 traceComponents=ALL  (Starts server

used as the basis for message catalogs for message internationalization.

with

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

config flags)</li>

information on these libraries

<li>cimprovider -l -s  (Lists providers and their status)</li>

7. OpenSSL - If it is intended to use SSL

<li>cimprovider -e -m OperatingSystemModule  (Enables the

on the communication protocol, the OpenSSL libraries are required.

OperatingSystem provider)</li>

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

<li>cimuser -a -u guest _w <ThePassword> (Adds the user <span

Structure</a></h1>

style="font-style: italic;">guest with specified password)

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

<li>cimuser -l  (Lists the users )

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

Tests depends tests </li>

<li>Common Pegasus Common

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

the common functions</li>

<li>Compiler Pegasus MOF

compiler </li>

<li>Config Pegasus

Configuration functions</li>

<li>Consumer Indication

Consumer class header</li>

<li>ControlProviders

Implementation of Pegasus internal providers </li>

<li>ExportClient Client

connect code for export of indications</li>

<li>ExportServer Server code

for import of indications</li>

<li>Handler Indication

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

<li>HandlerService Common code

for indication handler service</li>

<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

Functions </li>

</ul>

</li>

<li>Security Authentication

and user support functions.</li>

<li>Server Pegasus Server

Modules </li>

<li>WQL the WQL query language

interpreter.</li>

</ul>

</li>

</ul>

</li>

<li>Providers Pegasus test and

required providers

<ul>

<li>generic A number of

cross-platform providers </li>

<li>IndicationConsumer - Provider that

consumes indications</li>

<li>Linux - A number of linux

providers</li>

<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>

<li>Standard Includes - </li>

<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>

Note:  there are some differences between windows and other

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

platforms in

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

starting the server as a daemon/service. Whereas most supported

releasing binaies.

platforms use

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

the configuration option daemon to start the server as a service, on

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

windows it

For the snapshot, the installation of Pegasus involves expanding the

must be specifically installed as a service (ex. cimserver -install)

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

and then

test clients, and building the repository.

started as a service (cimserver -start). The cimserver --h option

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

explains the

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

exact format of the start and stop options.<br

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

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

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

<br

MOF compiler or WQL parser).

style="color: rgb(0, 0, 0); font-weight: bold;">

Be sure these are on the path.

Makefile commands

2. Define the following three environment variables:

<ul>

Pegasus includes several make files that enable

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

you to quickly build or

you've pulled from CVS </li>

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

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

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

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

supplied targets.

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

The following list contains some of the make targets that are

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

supported:

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 371

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

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

</ul>

The Pegasus Client server tests are executed separately from the

<span

above because they require the initiation of separate process for the

style="color: rgb(0, 0, 0); font-weight: bold;"><span

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

style="color: rgb(0, 0, 0);">For a comprehensive list of  the

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

make targets, refer to the make files.

and poststarttests.

For information on particular installation characteristics, tools,

TestMakefile

etc. for each platform see the appropriate sections below:

commands

Generally the build commands are as follows:

<ol>

<font

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

color="RED"> TestMakefile is a

executing make in the Pegasus root directory will make everything.

make file

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

that in the top level Pegasus source directory that defines

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

functionality to

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

initiate the Pegasus tests. The targets defined in this makefile allow

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

the

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

user to run the various tests and test suites that are included in the

Client/Server tests. </li>

Pegasus

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

source package.

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

Example:

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

From the $PEGASUS_ROOT directory.

directory messages. </li>

make -f TestMakefile [testoption]

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

structure. </li>

## rebuild -

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

Rebuild

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

mak/BuildMakefile cleanbuild" </li>

## build - Build

</ol>

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

## prestarttests - Execute

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

functional tests

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

to do it manually:

## poststarttests - Execute

poststarttests (No security, No SSL)

## tests - Execute prestarttests and

poststarttests

## standardtests - Execute

poststarttests and a series of

## posstarttests using multiple

options.

##

Some examples:

make -f TestMakefile prestarttests

- runs the unit tests, builds

the repositories.

make -f TestMakefile poststarttests

- starts the server, runs

the poststarttest suites

(make poststarttests plus

more)

make -f TestMakefile tests -

combines prestarttests and

poststarttests

make -f TestMakefile standardtests -

runs the basic poststarttests (make

poststarttests) multiple

times with various options.

BuildMakefile

commands

Some examples:<br

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

make -f pegasus/mak/BuildMakefile

cleanbuild - Remove the existing pegasus <span

style="color: rgb(0, 0, 0);">directory, perform a CVS

checkout of the pegasus

source,

build, and run tests.

make -f pegasus/mak/BuildMakefile

removeall

- Remove the existing pegasus

directory.

<span

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

-f pegasus/mak/BuildMakefile

recheckout - Remove the existing pegasus

directory and perform a CVS

checkout of the pegasus

source.

The following sequence builds the

tree, the repository, the testrepository,

starts the server and runs

the server tests suites.

make world

make testrepository

make -f TestMakefile poststarttests

<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">How to Participate</a></h1>

Contributors

are welcome to participate in the OpenPegasus development effort. Join

the mailing list by visiting www.openpegasus.org and clicking on

Mailing Lists.

<h1>

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

RPM installation instructions can be found here: <a

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

Verify  Dependencies

Before

you install Pegasus be sure you have the proper set of  software

Pegasus is dependent on.  <a href="#peg_dep">See Dependencies

section.</a>

<a name="set_envt_var">Set the environment

variables

</a>

Before installing or running OpenPegasus, environment variables may

have to be defined or updated.

<a

href="http://www.openpegasus.org/pp/uploads/40/8502/PEP200_RecommendedReleaseOptions.htm">PEP

200</a> contains the list of environment variables and setup necessary

to use OpenPegasus.

<ul>

</ul>

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

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

is done during the build 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 the  pegasus directory does three things:

are located in src/Providers)

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

<ul>

manual on the openpegasus.org.

<li> Removes the existing repository if one

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

exists.</li>

Installation</a></h1>

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

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

objects).  </li>

CVS enviromentthat can be executed including:

<li>Loads

schema for CIM Server functions (shutdown, add users, etc) and

CIM indications

(SNMP, Events, Alert, Threshold, etc)

internal to the Pegasus. </li>

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

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

src/Providers)  </li>

</ul>

<h2>

<a name="reg_prov">Registering

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

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 experimental 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.

Registration

is performed by creating instances of the

registration classes that represent the provider module, providers,

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 registration instance implementations that do work with

OpenPegasus

today.

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

Building OpenPegasus on Linux </a></h2>

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

variables set (PEGASUS_HOME, PEGASUS_ROOT, PEGASUS_PLATFORM.  For

32 bit linux, the definition of PEGASUS_PLATFORM is normally

LINUX_IX86_GNU).

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

on building OpenPegasus on Windows 2k or Windows XP with Microsoft

Visual

C++ </a></h2>

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

regularly tested on both Windows 2000 and Windows XP using the

Microsoft compilers.

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

contained

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

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

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

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

before trying to compile OpenPegasus on the normal windows platform.

The

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 supplied

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 (Note: <span

class="norm">The '/' characters are intentional and required by the OpenPegasus 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>

</blockquote>

<h3>

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

In order to provide a consistent build structure across multiple

platforms, we

developed a small utility to provide a consistent set of small

utilities

across these platforms. The MU utility is a simple utility that

contains

many

commands. For example:

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 OpenPegasus.

NOTE: The binary for MU.EXE is not distributed in the OpenPegasus bin

directory.

You must build it separately. MU source code is part of the

distribution

in the directory src/utils/MU with its own make file. You must compile

before you initiate the OpenPegasus make.

A copy of the binary is made available as a zip file on the OpenPegasus

WEB site.

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

Building OpenPegasus with SSL

</a></h2>

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

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

standard

directory so OpenPegasus 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 OpenPegasus with SSL enabled. See "Creating

SSL

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

Refer to the SSL Admin guide found in the doc directory for details on

using OpenPegasus with SSL.

<h1>

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

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

CVS

environment, including:

<ul>

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

built specifically to test Pegasus or parts of Pegasus including

built specifically to test OpenPegasus, or parts of OpenPegasus,

including

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

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

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

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

tests use classes and instances that are only installed with the

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

"make testrepository" functions including test namespaces and extra

classes and instances in those namespaces and additional providers

classes and instances in those namespaces and additional providers from

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

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

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

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

major provider types in the providers/sample directories and the

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

providers/testProviders directory</li>

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

<li>Unit Tests - Most OpenPegasus functions include unit tests

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

for

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

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

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

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

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

test directories immediately below their corresponding source code

directories immediately below their corresponding source code

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

(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

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

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.

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

registration today is to copy from one of the existing registration

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

registration instance implementations that do work with Pegasus today.

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

In order to provide a consistent build structure across multiple

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

small utilities across these platforms. The MU utilityis a simple

utility that contains many commands. For example:

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.

<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

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

defintion of PEGASUS_PLATFORM is normally LINUX_IX86_GNU.

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

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

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

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

DARWIN_PPC_GNU.

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

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

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

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

SSL.

<h1><a

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

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

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

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

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

href="#The%20MU%20Utility">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.

Setup the environment variables and path for the Micrososft Visual C

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

supplied 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>

</blockquote>

<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