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.5 and 1.6

version 1.5, 2004/03/10 19:24:13

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

Line 1

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

<html>

<head>

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

<title>OpenPegasus</title>

</head>

<body>

Pegasus Enhancement Proposal (PEP)

PEP #: 103

PEP #: 103

Title: OpenPegasus Version 2.3

Title: OpenPegasus

Release Readme file

Version 2.3 Release Readme file

Version: 1.1

Version: 1.1

Created: 12 November 2003

Created: 12

Authors: Karl Schopmeyer, Konrad Rzeszutek

November 2003

Status:  draft

Authors: Karl

Version History:

Schopmeyer, Konrad Rzeszutek

Status: draft

Version History:

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

bordercolorlight="#CCCCCC" width=100%

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

style='font-size=10.0pt;font-family:Arial'>

<tbody>

<tr>

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

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

<th bgcolor="#CAE6CA">Author</th>

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

<th bgcolor="#CAE6CA">Change Description</th>

<th bgcolor="#cae6ca">Change Description</th>

</tr>

<tr>

Line 40

Line 41

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

</tr>

<tr>

</tr>

</tbody>

</table>

<hr>

Abstract:  Installation, build, operation information on the

Abstract: Installation, build, operation information on the

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

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

the documentation in the release notes or interface definition documents for a

with the documentation in the release notes or interface definition

particular release, those documents should be considered authorative. This is a

documents for a particular release, those documents should be

simplified overview to act as an introduction to Pegasus.

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

introduction to Pegasus.

<hr>

OpenPegasus - A Manageability

OpenPegasus - A Manageability Services Broker

Services Broker for the DMTF CIM/WBEM Standards

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

STATUS: Revised November 2003 for Pegasus

release version 2.3.0

Table of Contents

Tagline: OpenPegasus is an object manager for DMTF CIM objects written in C++

<a

and supported by The Open Group

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

<a

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

<a

STATUS: Revised November 2003 for  Pegasus release version 2.3.0

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

<a

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

<a

Table of Contents

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

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

<a

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

Structure</a>

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

<a

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

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

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

<a

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

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

<a

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

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

<a

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

Providers</a>

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

<a

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

<a

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

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

Building Pegasus on Linux</a>

<a

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

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

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

<a

<a href="#Registering Providers in the Pegasus Environment">Registering

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

Providers</a>

building Pegasus with SSL</a>

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

<a

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

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

<a

<a href="#Notes about Building Pegasus on Linux">Notes about Building Pegasus on Linux</a>

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

the Pegasus HTML Test Client </a>

<a

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

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

with Pegasus and Pegasus Tools</a>

<a

<a href="#Building Pegasus on Windows 2000 or Windows XP With Microsoft Visual C++">Building Pegasus on Windows 2000 or Windows XP With Microsoft Visual C++</a>

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

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

<a

</a>

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

<a

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

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

<a

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

<a

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

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

<a

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

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

<a

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

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

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

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

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

<a href="#Participate!">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

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

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

implemenation of the CIMOperations over HTTP operations and their cimxml

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

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

implemenation of the CIMOperations over HTTP operations and their cimxml HTTP

It is maintained consistent with the DMTF CIM and WBEM specifications

encodings, and

except for exceptions noted in the documentation.

Interface libraries

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

for both client and providers. It is maintained

license.

consistent with the DMTF CIM and WBEM specifications except for  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

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

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

Pegasus is being developed and maintained under the auspices of The Open

users.

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

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

(LICENSE) of this release. This licensing is intended to support as wide a

documentation on Pegasus are available from the OpenGroup WEB site.

distribution as possible with minimal demands on the users.

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

There are a number of separate documents representing the status and

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

each release of Pegasus

Pegasus are available from the OpenGroup WEB site.

<ul>

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

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

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

There are a number of separate documents representing the status and each

the source top level directory</li>

release of Pegasus

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

<ul>

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

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

</ul>

release notes on the Pegasus web site and duplicated in the source top level

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

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

documents and in the CVS for each release.

the web site as a Pegasus PEP.</ul>

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

in the CVS for each release.

<tbody>

<tr>

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

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

Line 186

Line 170

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

Pegasus is distributed as open source under the MIT open-source license. The distribution is available via

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

CVS and snapshot images in tar and zip file formats on the web site.

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

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

be found at the following Open Group CVS server;

cvs.opengroup.org:/cvs/MSB

using the password authenticating server option (pserve).

cvs.opengroup.org:/cvs/MSB

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

follows:

using the password authenticating server option (pserve).

<font

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

face="Courier New">%export

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

<font

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

face="Courier New">%cvs login

</blockquote>

%cvs login

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

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

</blockquote>

type:

cvs co pegasus

When requested, enter the password "anon".

A Pegasus directory will be created under the current directory and

The source tree is in the directory pegasus. To check out the complete Pegasus

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

source tree just type:

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

cvs update -d

Active contributors to Pegasus have write access to the CVS

cvs co pegasus

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

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

A Pegasus directory will be created under the current directory and populated

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

with the complete source tree and documentation. To get the latest updates

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

after a checkout just type this from Pegasus root:

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

The major components of Pegasus are:

<ul>

cvs update -d

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

providers and clients </li>

<li>Pegasus Repositories - Today Pegasus provides a defined

Active contributors to Pegasus have write access to the CVS repository.

class repository interface and a simple file based class repository.

If you are interested in contributing back to the Pegasus project,

It also includes an instance repository. Note that these repository

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

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

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

they will be replaced with other implementations of the respository

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

function as the need arises. </li>

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

<h1>

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

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

protocols or directly interfacing with Pegasus. </li>

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

The major components of Pegasus are:

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

<ul>

src/Clients directory and its subdirectories </li>

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

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

</li>

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

<li>Pegasus Repositories - Today Pegasus provides a defined class repository

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

interface and a simple file based class repository. It also includes

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

an instance repository. Note that these repository were created for

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

functionality, not efficieny. It is expected that they will be replaced

variety of demonstrations. </li>

with other implementations of the respository function as the need arises.

<li>Pegasus Provider Library - Tools for building Pegasus

</li>

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

<li>Pegasus Client Library - Tools for building Pegasus clients based on the Pegasus

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

C++ interfaces and using the WBEM HTTP/XML protocols or directly

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

interfacing with Pegasus.

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

</li>

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

<li>Pegasus Test Clients - Simple test clients being developed as part of the

<li>Pegasus MOF Compiler - There standalone compiler

Pegasus development process. These can be seen in the src/Clients directory and

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

its subdirectories

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

</li>

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

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

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

Pegasus that uses a WEB server (ex. Apache) with a set of CGI modules and

</ul>

HTML to allow the entry of Pegasus operations from a WEB browser as forms

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

and the receipt of the response as WEB pages. This has proven useful as a

Pegasus is regularly tested against a variety of platforms by the

test tool and can be used for a wide variety of demonstrations.

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

</li>

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

<li>Pegasus Provider Library - Tools for building Pegasus providers using the Pegasus

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

C++ interfaces.

ReleaseNotes for any particular release).

</li>

Generally Pegasus is supported on the following Platforms and

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

Compilers.

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="169" bgcolor="#99ff99">Platform and OS</td>

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

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

</tr>

<tr>

Line 309

Line 268

</tr>

<tr>

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

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

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

Version 7</td>

compiler Version 7</td>

</tr>

<tr>

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

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

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

Version 7</td>

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>

<h1>

We have worked to minimize the dependence of Pegasus on other

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

software packages and tools. Currently Pegasus has the following

dependencies:

1. GNUMAKE - To simplify the building of Pegasus across

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

multiple platforms we have standardized on a set of build tools

packages and tools. Currently Pegasus has the following dependencies:

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

Windows and Linux environments.

1. GNUMAKE - To simplify the building of Pegasus across multiple platforms we

GNUMAKE is available from :

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

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

GNUMAKE 3.79.1 successfully both in Windows and Linux environments.

available on the openpegasus web site.

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

GNUMAKE is available from :

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

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

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

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

       NOTE: A set of the required tools for

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

windows platforms is available on the openpegasus web site.

UNIX or LINUX platforms.

2. MU.EXE - To minimize the difference between Linux and Windows for GNUMAKE,

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

we have created a utility called MU.exe. This utility is required for

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

Pegasus make with ONLY Windows environment. It is provided as an alternative to

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

requiring a number of UNIX utilities (SH, RM, etc.) on the windows platform

must compile MU before you initiate the Pegausu make.

and effectively provides the functions of these utilities that GNUMAKE

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

needs. MU is not required on UNIX or LINUX platforms.

Pegasus WEB site.

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

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

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

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

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

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

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

before you initiate the Pegausu make.

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

compiling.

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

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

WEB site.

library for Mac OS X/Darwin.

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

NOTE: The dlcompat is not distributed with pegasus

source.

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

dlcomapt is available from :

parser. Anybody intending to recompile the compiler or parser from scratch

will be required to have these tools. They are only required if changes need

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

to be made to the files for parsing and compiling.

4. DOC++ - The Pegasus documentation is taken from a combination of text files

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

and the Pegasus header files themselves. This documentation is formatted

X/Darwin.

with DOC++ and GAWK. These tools are required if the documentation is to

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

be recreated but we expect that only the core team will be recreating

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

documentation.

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

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

5. ICU Internationalization libraries - These libraries are used as

core team will be recreating documentation.

the basis for message catalogs for message internationalization. See the ICU

6. ICU Internationalization libraries - These libraries are

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

used as the basis for message catalogs for message internationalization.

libraries6. OpenSSL - If it is intended to use SSL on the

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

communication protocol, the OpenSSL libraries are required.<h1>

information on these libraries

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

7. OpenSSL - If it is intended to use SSL

on the communication protocol, the OpenSSL libraries are required.

Pegasus is distributed as a complete source directory structure that should be

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

installed either from one of the snapshots or from CVS.

Structure</a></h1>

Pegasus is distributed as a complete source directory structure that

This structure is generally as follows:

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

Pegasus Source Structure

This structure is generally as follows:

Pegasus Root directory (PEGASUS_ROOT environment

Pegasus Source Structure

variable)<ul>

Pegasus Root directory (PEGASUS_ROOT

<li>cgi Source for the Pegasus WEB Based Test client

environment variable)

<ul>

<li>cgi Source for the Pegasus WEB

<li>cgi-bin CGI Directories for WEB demonstration.

Based Test client

This directory is normally empty but can

<ul>

be populated from the runtime with the make

<li>cgi-bin CGI Directories for WEB

from cgi.

demonstration. This directory is normally empty but can be

</li>

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

<li>htdocs HTML Pages for Pegasus WEB demonstration

<li>htdocs HTML Pages for Pegasus WEB

</li>

demonstration </li>

</ul>

</li>

<li>doc Miscellaneous Pegasus Documents.

<li>doc Miscellaneous Pegasus

Documents.

<ul>

<li>apidoc - Source for the public api

documentation.</li>

<li>DevManual Source and build files for developers' manual

<li>DevManual Source and build files for

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

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

</ul>

</li>

<li>mak - Common make files for Pegasus

<li>mak - Common make files for

compilation</li>

Pegasus compilation</li>

<li>Dummy -</li>

<li>InterfaceArchive -</li>

<li>rpm - files for rpm installation for Linux</li>

<li>rpm - files for rpm installation

<li>Schemas - Schemas used in the installation

for Linux</li>

of Pegasus. This includes currently released versions of the DMTF schemas in

<li>Schemas - Schemas used in the

subdirectories (ex. CIM27) and Pegasus local Schemas (ex. </li>

installation of Pegasus. This includes currently released versions

<li>src All Pegasus Source Files

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

Schemas (ex. </li>

<ul>

<li>src All Pegasus Source Files

<li>ACEExample Test directrory with examples of the use of ACE (obsolete).

<ul>

</li>

<li>ACEExample Test directrory

<li>Clients Source for various test

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

clients and demonstration clients.</li>

<li>Clients Source for various

<li>CGICLIENT Pegasus test client that uses a WEB browser

test clients and demonstration clients.</li>

JAVA Java Client support modules

<li>CGICLIENT Pegasus test client

</li>

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

<li>Pegasus - Core pegasus modules.

<li>Pegasus - Core pegasus

modules.

<ul>

<li>Client Pegasus Client API Tests

<li>Client Pegasus Client API

depends tests </li>

Tests depends tests </li>

<li>Common Pegasus Common Functions (C++ source and headers

<li>Common Pegasus Common

tests Test programs for the common functions</li>

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

<li>Compiler Pegasus MOF compiler

the common functions</li>

</li>

<li>Compiler Pegasus MOF

<li>Config Pegasus Configuration

compiler </li>

functions</li>

<li>Config Pegasus

<li>Consumer Indication Consumer class

Configuration functions</li>

header</li>

<li>Consumer Indication

<li>ControlProviders Implementation of Pegasus internal providers

Consumer class header</li>

</li>

<li>ControlProviders

<li>ExportClient Client connect code

Implementation of Pegasus internal providers </li>

for export of indications</li>

<li>ExportClient Client

<li>ExportServer Server code for

connect code for export of indications</li>

import of indications</li>

<li>ExportServer Server code

<li>Handler Indication handlers. Today

for import of indications</li>

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

<li>Handler Indication

<li>HandlerService Common code for

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

indication handler service</li>

<li>HandlerService Common code

<li>IndicationService Common service

for indication handler service</li>

functions for indication subscription processing</li>

<li>IndicationService Common

<li>Listener Common code that allows

service functions for indication subscription processing</li>

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

<li>Listener Common code that

<li>Protocol Pegasus Client HTTP/XML Protocol Modules

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

depends </li>

<li>Protocol Pegasus Client

<li>Provider Pegasus Provider interface functions

HTTP/XML Protocol Modules depends </li>

</li>

<li>Provider Pegasus Provider

<li>ProviderManager Provider Manager service that manages providers

interface functions </li>

</li>

<li>ProviderManager Provider

<li>ProviderManager2 Pluggable Provider Manager service.

Manager service that manages providers </li>

Today this is not enabled by default It will become the Pegasus

<li>ProviderManager2 Pluggable

standard provider manager at some time in the future but for now, see

Provider Manager service. Today this is not enabled by

the release notes if you want to enable it.</li>

default It will become the Pegasus standard provider manager

<li>Repository Pegasus Repository

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

Interfaces and Simple Repository tests

want to enable it.</li>

<ul>

<li>Repository Pegasus

<li>Tests for Repository Functions

Repository Interfaces and Simple Repository tests

</li>

<ul>

</ul>

<li>Tests for Repository

</li>

Functions </li>

<li>Security Authentication and user

</ul>

support functions.</li>

</li>

<li>Server Pegasus Server Modules

<li>Security Authentication

</li>

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

<li>Providers Pegasus test and

required providers

<ul>

<li>generic A number of

cross-platform providers

cross-platform providers </li>

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

<li>slp - Provider for slp

service agent support</li>

<li>statistic - Providers for

Pegasus statistics.</li>

<li>sample Sample providers for the

<li>sample Sample providers for

major provider types.</li>

the major provider types.</li>

<li>testproviders </li>

</ul>

</li>

<li>Server Pegasus executable build

<li>Server Pegasus executable build </li>

</li>

<li>Standard Includes - </li>

<li>test - Directory of end-end

<li>test - Directory of end-end tests

tests that are regularly conducted on Pegasus</li>

that are regularly conducted on Pegasus</li>

<li>tools MU and other utilities written for Pegasus support

<li>tools MU and other utilities

</li>

written for Pegasus support </li>

<li>Unsupported Code that is made available but is not supported or included

<li>Unsupported Code that is made

in the normal make. </li>

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

<li>WMIMapper Pegasus implementation that

<li>WMIMapper Pegasus implementation

provides mapping to Microsoft WMI objects.

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

</ul>

</li>

Pegasus Run Time directory structure

</ul>

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

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

Pegasus Run Time directory structure (PEGASUS_HOME

<ul>

environment variable). Home directory for runtime. All compiler, linker

<li>bin - Destination for executable

documentation creation, etc. are put here.

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

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

<ul>

executed with minimum effort.</li>

<li>bin - Destination for executable and DLL modules from

<li>DevManualHTML - HTML output of the

Pegasus build. This directory should be make public so that the test functions,

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

clients, and cimserver can be executed with minimum effort.</li>

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

<li>DevManualHTML - HTML output of the Pegasus Manual.

representing the document.</li>

This is only created when the make file for this manual is

<li>apidochtml - HTML output of the

executed (doc/DevManual) and then contains the html representing

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

the document.</li>

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

<li>apidochtml - HTML output of

<li>lib - Destination for Pegasus LIB

the creation of the public API document.  This only exists

modules </li>

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

PEGASUS_HOME directory, not in the log directory if Pegasus internal

internal tracing is enabled.</li>

tracing is enabled.</li>

<li>repository - This Directory

contains the created repository </li>

</ul>

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

<h1>

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

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

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

releasing binaies.

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

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

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

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

binaies.

For the snapshot, the installation of Pegasus involves expanding the

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

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

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

test clients, and building the repository.

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

For the snapshot, the installation of Pegasus involves expanding the snapshot

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

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

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

building the repository.

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

<h1>

MOF compiler or WQL parser).

Be sure these are on the path.

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

2. Define the following three environment variables:

<ul>

</h1>

<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

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

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>

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

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

and Bison only required if changes will be made to the MOF compiler or WQL

identifier.</li>

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:

This identifier has the following form:

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

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

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

LINUX_IX86_GNU

For a complete list of platforms supported and platform support

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

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

LINUX_IX86_GNU

face="Courier New">pegasus/mak

</blockquote>

For a complete list of platforms supported and platform support keywords, refer to the platform make files found in directory 

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

pegasus/mak

setting PEGASUS_HOME to something like this:

$HOME/pegasus_home_LINUX_IX86_GNU

</blockquote>

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

directory.

3. Now place $PEGASUS_HOME/bin on your path

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

and

PEGASUS_HOME to something like this:

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"

$HOME/pegasus_home_LINUX_IX86_GNU

(where make refers to GNU make).

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

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

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

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

3. Now place $PEGASUS_HOME/bin on your path

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

and

are supported:

<ul>

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

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

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

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

<li>depend - Create the dependencies. </li>

<li>repository - Create the repository in $PEGASUS_HOME/repository </li>

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

<li>tests - Execute all tests (except client server tests). </li>

(where make refers to GNU make).

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

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

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

</ul>

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

The Pegasus Client server tests are executed separately from the

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

above because they require the initiation of separate process for the

6. To test the build type "make tests".

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

The following make targets are supported:

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

<UL>

and poststarttests.

<li><default> - Build everything.

For information on particular installation characteristics, tools,

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

etc. for each platform see the appropriate sections below:

<li>depend - Create the dependencies.

Generally the build commands are as follows:

<li>repository - Create the repository in $PEGASUS_HOME/repository

<li>tests - Execute all tests (except client server tests).

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

<li>world - depend, <default>

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

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

make in the Pegasus root directory will make everything. "make rebuild"

executing make in the Pegasus root directory will make everything.

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

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

the repository with the current CIM Schemas.

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

</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".

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

This will build dependencies, build binaries, and then run all

Client/Server tests. </li>

tests except the Client/Server tests.

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

</li>

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

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

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

"make tests". This also reinstalls the repository. 

directory messages. </li>

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

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

enter/leave directory messages.

structure. </li>

</li>

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

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

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

mak/BuildMakefile cleanbuild" </li>

</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 mak/BuildMakefile cleanbuild"

</li>

</ol>

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

<h1>

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

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

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.. The makefile

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

manually:

<ol>

<LI>Register the MOF (Managed Object Format) file describing the skeleton of the

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

object.

skeleton of the object. </li>

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

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

when a

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

specific object is activated.

</ol>

This is done automatically for the providers included in Pegasus by doing:

This is done automatically for the providers included in Pegasus by

make repository.

doing: make repository.

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

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

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

Runs MOF compiler (cimmofl) on:

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

-Schema v2.7

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

Generates the CIM Schema v2.7 in the repository (skeleton of CIM objects)

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

-PG_InterOp

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

Internal to Pegasus schema for operating (shutdown, add users, etc)

are located in src/Providers)

CIM_Indication’s (SNMP, Events, Alert, Threshold, etc)

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

-PG_ManagedSystem

manual on the openpegasus.org.

Registers included CIM Providers (libOSProvider.so, libDNSProvider.so, … )

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

in Pegasus (which are located in src/Providers)

Installation</a></h1>

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

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

CVS enviromentthat can be executed including:

<ul>

openpegasus.org.

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

built specifically to test Pegasus or parts of Pegasus including

<h1>

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

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

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

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

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

tests use classes and instances that are only installed with the

enviromentthat can be executed including:<ul>

"make testrepository" functions including test namespaces and extra

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

classes and instances in those namespaces and additional providers

specifically to test Pegasus or parts of Pegasus including TestClient, Client,

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

CLI, ipinfo, osinfo, WbemEsec, etc. See the src/Clients directory for more

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

information. These programs require a server complete with repository to be

major provider types in the providers/sample directories and the

running.  Note that some of these tests use classes and instances that

providers/testProviders directory</li>

are only installed with the "make testrepository" functions including test

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

namespaces and extra classes and instances in those namespaces and additional

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

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

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

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

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

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

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

directory</li>

test directories immediately below their corresponding source code

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

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

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

directory). Unit tests are executed without the server being

which can be executed at many different levels of the source tree from the top

operational and normally do not require the existence of a Class

level to execute all of the unit tests to 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

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

operations tests that cover the major CIM operations.  See the make file

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

TestMakefile in the PEGASUS_ROOT directory to execute these tests.  This

the make file TestMakefile in the PEGASUS_ROOT directory to execute

set of tests executes an extensive set of fixed tests and compares the results

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

against predefined results.</li>

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

</ul>

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

<h1>

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

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

Pegasus registers providers with a set of provider registration

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

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

Pegasus registers providers with a set of provider registration classes, not

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

using the provider qualifier as is done in most DMTF CIM CIMOM implementations

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

today. This set of classes is close to but not exactly the same as the current

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

DMTF definition (See the DMTF Interop schema, experimental versions starting

registration classes that represent the porvider module, providers,

with 2.6). This will be harmonized in the future when the DMTF scheme is moved

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

to final status.

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.

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

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

registration classes that represent the porvider module, providers, classes,

In order to provide a consistent build structure across multiple

etc. to be registered.  The easiest way to create a new registration today

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

is to copy from one of the existing registration MOFs.  See the

small utilities across these platforms. The MU utilityis a simple

providers/sample/load directory for examples of several registration instance

utility that contains many commands. For example:

implementations that do work with Pegasus today.

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

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

<h1>

them:

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

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

depend

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

In order to provide a consistent build structure across multiple platforms, we

do things like this:

developed a small utility to provide a consistent set of small utilities

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

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

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

commands. For example:

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

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

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

defintion of PEGASUS_PLATFORM is normally LINUX_IX86_GNU.

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

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

of them:

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

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

defination of PEGASUS_PLATFORM is

DARWIN_PPC_GNU.

The MU utility supports globing (expansion of wildcards) so

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

you can do things like this:

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

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

installation is.

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

MU is required to build under the Windows environment. MU is available as part

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

of the distribution of Pegasus.

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

SSL.

<h1>

<h1><a

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

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

Linux </a></h1>

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

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

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

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

PEGASUS_ROOT, PEGASUS_PLATFORM.  For 32 bit linux, the defintion of

compilers.

PEGASUS_PLATFORM is normally LINUX_IX86_GNU.

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

contained in the source distribution, the Microsoft compilers (DevStudio

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

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

</a></h1>

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

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

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

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

distributed with Pegasus. Make sure

following is the basic setup steps for the environment.

you have them in a standard directory so Pegasus can find them. If that's not

Setup the environment variables and path for the Micrososft Visual C

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

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

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

OpenSSL

cl.exe).

installation is.

For Windows, try the following for an example environment:

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

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

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

</blockquote>

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

certificates" for more information of how to use SSL.

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

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

<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

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

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

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

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

tested on both Windows 2000 and Windows XP using the Microsoft compilers.

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

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